ZynewaveZynewaveCould you guys explain why you don’t use the “load device setup” submenu in the project templates?
The way I see it, project templates are plugin databases, with the possibility to also include default arrangements etc. Granted, the database is included in your project file, but with the “load device setup” it’s easy to substitute the plugin database in your existing projects.
Maybe what is needed is making the project template available on the create new project page through a combobox. When a template is selected, the plugin scan options would then only import plugins that are not already found in the project template.
I’m open for suggestions.
ZynewaveHi,
@eincande wrote:
– I must be a little “slow” but i cannot manage to control play/record etc from my tranzport “mackie compatible” control surface. The green midi indicator flashes all right, but nothing moves. I made the necessary settings but it just don’t do anything at all ? 🙁
Just checking: In the interfaces dialog, enable the MIDI input AND the MIDI output that the tranzport is connected to. Select the tranzport MIDI output in the list, and then select the “Detect Mackie…” option for that output. If the device is 100% MCU compatible, then that should do it. I don’t have a Tranzport so I can’t test if this device behaves differently.
– I have red that Podium works flawlessy on window 7 x64 with x32 vst plugs. is that confimed ? as cubase doesn’t even do it, i would find that pretty cool 🙂
Podium is currently only available as a 32bit application, so it will work only with 32bit plugins. Once I’ve made a x64 version of Podium, then that will only work with 64bit plugins. I’ll probably integrate support for the jBridge converter, which then will allow any Podium version to use any 32/64 bit plugin:
http://jstuff.wordpress.com/jbridge/
– In your opinions, how can you compare CPU load with Podium over Cubase 5 ?
I haven’t compared with Cubase 5, but the user feedback I’ve received says that Podium does ok in CPU comparizon tests.
ZynewaveThis is implemented for the next 2.28 release. I didn’t change the zPitch plugin, as I suggested in the above post, but rather I shared the info from the integrated plugin editors. I had done some of this work earlier with the embedded rack/mixer editors, so it was easy to extend this to the curve editor and the mixer faders.
It applies to all other Zynewave plugin parameters as well, such as the zPEQ gain parameters.
ZynewaveZynewaveZynewaveZynewave@thcilnnahoj wrote:
Late-night bug report:
I’ve just released 2.27, and somehow I forgot to examine these bugs. I’ll look at them first thing for 2.28.
Zynewave@thcilnnahoj wrote:
I noticed something that could use a little thought:
Imagine you create a new group track and add a few child tracks to it. They of course all get tagged with, say the standard “Tracks” tag. This results in the child tracks not minimizing when you try to collapse the group, as not only the group track, but also the child tracks themselves are tagged, and thus always appear “expanded.”
I guess you can’t simply tell Podium not to tag child tracks, as we know all tracks except the master(s) are child tracks… :-k
New child tracks are assigned the same tags as the group track, so that when deleting the group track it won’t leave the child tracks without tags (i.e. invisible). I implemented that after you made this remark in the 2.26 preview topic:
Hmm, I experienced a moment of confusion yesterday, when I deleted a group track, and all child tracks disappeared along with it! Of course they were just invisible because only the group track had the selected tag.
So assuming the child tracks should still remain tagged, one solution is to allow tagged child tracks to be collapsed, if the parent group track is visible. Would that solve it? :-k
And something else that’s unrelated: Since the disabling of the sound name/filename naming capability in the sound properties dialog, all my projects end up being comprised of audio events with very undescriptive names (meaning “Track 1, 2, 3…”), as I tend to name the tracks at a later time.
With the ‘sound event name’ box, it seems you can only name each event separately, even if they’re all phantom copies. 🙁
The name of new sounds can be edited in the sound properties dialog until the first save of the project/sound file. Do you miss a possibility to rename the sound file, or to apply a name to all selected sound events?
Edit: Ah, what the heck. One more!
Would it theoretically be possible for a zoom snapshot to know it spans the whole length of the arrangement, and update accordingly? I always set up the first snapshot slot for this purpose, but as the arrangement grows, I regularly have to resize the zoomed area by hand. Just a small matter, of course.
Yes it’s possible. I’ll keep it in mind for a future update.
Zynewave@thcilnnahoj wrote:
Regarding tags…
Seeing as the “Tracks” tag is meant to provide a view of all tracks, don’t you think new tracks should always receive this tag, along with any and all tags that are selected at the time of track creation?
Bus tracks are now nicely tagged automatically unless you go the old-fashioned way of creating them, in which case it would make no difference which tags they get, as you’ll have to change it anyway (unless you select only the busses tag).I would even go as far as to suggest the master, busses and tracks tags should be non-removable, but maybe that’d take away a little too much freedom…
The default “tracks” tag was intended as a suggestion, to have at least one tag that when selected will hide the master and bus tracks. Personally, if I want to divide audio tracks into categories, I would rename/remove the “tracks” tag.
Zynewave@Malcolm Jacobson wrote:
@Zynewave wrote:
The template file seems ok to me. It imports like shown in the screenshot of your previous post. Can you give me more details about what is not working?
The VSTi does not load as part of the template. All of the tracks do, but no device. Isn’t the device definition meant to be saved as part of the template?
The device definition in your template file appears to be ok. Please describe how you experience that the VSTi does not load. Are the icons for the device mappings red? If so then the plugin dll file could not be located within the VST folders you have specified in the preferences. Your template refers to:
C:Program FilesVstpluginsGarritanARIA Player Multi VST_x86.dll
Is that still the location where you have installed the plugin?
ZynewaveBeta 8 is up.
The timing adjustments are now saved in the project file. Also fixed a plugin import bug with some synths supporting surround output.
If no bugs are found in this, I’ll release 2.27 tomorrow.
Zynewave@thcilnnahoj wrote:
Hey, I’m still up (yawn), and have just uploaded a new video, complementary to Frits’ side-chain video: http://www.youtube.com/watch?v=7F2B0_VwnJM (HD not ready yet at time of writing)
Favorited 🙂
If you keep this up, I may end up learning something about Podium that I didn’t know already 😆
ZynewaveIt could be an issue with your soundcard driver. Try to disable your MIDI/audio interfaces in the Interfaces dialog before exiting Podium. If it still hangs when you try to exit, then the problem could perhaps be related to antivirus tools.
There have been reports about slow closing times caused by antivirus tools:
Zynewave