Zynewave's Forum Page
Forum Replies Created
-
ZynewaveKeymasterFor simple fade-in/out, gain and pan, you can drag the handles in the upper left/right corners of each sound event. For precise adjustments, right-click an event and select “sound event properties”.
If you want more advanced curve automation of level and pan, then use the track right-click menu and select “automate parameter > level/pan”. After that you can use the pencil tool (or double click with the select tool) to draw curve sequences and use the curve editor, or you can use the parameter faders in the mixer to create the curve sequences.
ZynewaveKeymaster@druid wrote:
When just the files are listed right in the project arrangement view like in XT, I can choose which I want and as long as I’ve maintained the VST folders, and load it. If I’ve recently updated it, or added more, they are just listed automatically after the file is there, I don’t need to maintain any database within the host as well.
If the plugin dlls are not scanned, then it won’t be possible for the host to know whether a plugin is an instrument or an effect. That wouldn’t work well in Podium where the list of plugins are filtered depending on whether you click on an effect or a source selector.
ZynewaveKeymasterHi lalo,
In one of the next releases I’ll improve the MCU-compatible control surface support. That should at least be a step in the right direction. I can’t give you a deadline for when I’ll implement generic support for MIDI-learn in the Podium UI. It’s on the todo list, but there are a lot of essential features on that todo list 😉
ZynewaveKeymaster@andreariderelli wrote:
if it will be possible in the near future to have a global plugin cache/db and only then the possibility to choose the customized plugins setup for each new project.
i mean: to avoid to scan vst directory every time you start a new project, but “having multiple plugin setups for your different types of projects”
Yes, if I understand you correctly. The plugin cache/db you talk about will be stored in a project template file. I’m going to revise the way that you access this project template (i.e. plugin database) on the Create New Project page. If you only work with one plugin setup, then the result should be that you don’t need to scan for plugins every time, unless you have installed new plugins and want to update the plugin database.
ZynewaveKeymaster@eincande wrote:
Can i provide you with info (log file ?) that would make you track down the tranzport issue ? maybe record a midi track with midi message correspondig to start/stop/Etc ?
the control is MCU compatible but i don’t know if it is 100%. but start stop should work at least 😉
I’ve looked at my source code for the MCU support, and I think I’m going to revise it very soon. The problem is that it currently requires the MCU device to respond to MIDI SysEx messages to identify the device. I think that is why it won’t work with a lot of the so-called “MCU-compatible” devices. I’ve received reports that Kore2 and Zoom R16 doesn’t work either. These devices probably only support the non-sysex messages that are used for button presses and fader movements etc. The SysEx messages are primarily for updating the MCU LCD display etc. With a bit of luck, I’ll have this working for Podium 2.28 or 2.29.
– about x64 : does podium user multicore ? i need to handle large project if a close future and i would like to get rid of cubase + i need to adress more ram (samples banks, like always :).
Podium supports multicore. To make use of RAM beyond the 3GB limit (which is the limit for 32bit applications), you can use the jBridge converter. I haven’t yet tried jBridge myself, but from what I’ve read then EACH plugin wrapped in the converter can use up to 3GB.
– Can you export all tracks to indiviual wav file ? (sending all session to protools) with or without effects ?
You can by using the bounce feature. If you have bounced all the individual tracks, then there already are bounced wave files in the project folder. You also have an export option in the bonce menu. In the bounce menu you can also specify whether it should bounce before or after effects.
ZynewaveKeymasterHi Andrea,
Thanks for your feedback. It emphasizes the need to make the project template system more accessible on the create new project page, as discussed in the topic thcilnnahoj linked to.
you are telling me that it is better to save a project as a new template after i complete a vst scan and then start any new project with this template, aren’t you?
That is correct. The reason that the plugin setup is included in the project, and not in a single global database, is that it allows for having multiple plugin setups for your different types of projects. You may want to create custom plugin setups for working with surround sound, mastering, classical composition, etc.
I’m going to make some improvements to the project template system for the coming 2.28 release.
March 30, 2010 at 14:23 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.ZynewaveKeymasterCould 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.
ZynewaveKeymasterHi,
@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.
ZynewaveKeymasterThis 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.
March 29, 2010 at 18:42 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.March 29, 2010 at 13:36 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.ZynewaveKeymaster- New Adjust Timing dialog with quantization, randomization and swing options.
- Made several improvements to the plugin import, including automatic setup of sidechain mappings.
ZynewaveKeymaster@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.
ZynewaveKeymaster@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.