Zynewave's Forum Page

I tried the LP10 demo, and can confirm that Podium reports a high CPU usage. However if you open up the task manager you’ll see that the CPU usage is actually only a few percent. The Podium CPU indicator shows the percentage of time spent in the plugin processing, and not the actual CPU usage. If the plugin is programmed so that it needs to wait for some system resources to be available, it will not use CPU while waiting, but it will still block the audio processing and thus consume much of the time that is available before ASIO buffers will underflow.

Reaper is probably reporting the actual CPU usage of the plugin, but I suspect the plugin is behaving similarly. If you try to add extra plugins to push the CPU usage upwards in Reaper, I’m guessing you will notice overload long before you reach 100%. Please let me know if this is not the case.

It will be difficult for me to debug this. Maybe you could contact DDMF. They may have some prior experience with this issue.

Now that you’ve implemented drag and drop for .syx files, could you add them to the list of recognised files for the “List” window?

Done.

To be able to test your .syx file, I implemented support for dragging .syx files onto tracks. Coming up in release 2.04.

I could not provoke a crash with your syx file. I tried recording a sysex dump from my AN1x synth, and I found no problem here either. I’m thinking the crash problem must be related to how you have set up your devices/tracks. Please send me a project file saved just prior to the point where you would start recording the sysex.

This is not possible with sound files on Podium tracks. There may be some VSTi sampler plugins which support browsing through different samples using program change, CC or other MIDI messages.

If you don’t mind cheating a bit:

Using the param panel in the inspector, set up a Level (or Pan/Send) parameter track for your plugin. You should now have two parameter tracks under your plugin. Select the “Level” parameter track, locate the “WAH” parameter in the param list, right-click and select “Assign to this track”. You now have two WAH parameter tracks. You’ll notice that Podium automatically mutes the second WAH track because it would otherwise conflict with the first WAH track. But if you then manually mute the first WAH track, the second WAH track becomes active. You can use this procedure to switch between alternate automation tracks. Rather than muting/unmuting automation tracks, it may be easier to use the “move track” submenu and move the automation track you want to work with above the other automation tracks.

Some time in the future I may implement a dedicated multiple take option for parameter tracks.

Hi,

There’s some info on license transfer at the bottom right of the purchase page.

Transfer of a license is allowed for free only once.

Frits

You can increase the height of the timeline ruler region in the editor profile properties. That will give you more space to hit the cursor.