Zynewave's Forum Page
Forum Replies Created
-
January 23, 2008 at 12:04 in reply to: Restricted to Podium license owners
ZynewaveKeymasterThis content is restricted to Podium license owners.January 23, 2008 at 12:03 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.January 22, 2008 at 19:52 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.January 22, 2008 at 19:42 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.January 22, 2008 at 15:38 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.ZynewaveKeymaster@acousmod wrote:
Do you have yet any idea how to implement it ?
I haven’t started yet. Still recuperating from the work on this release. But it won’t change anything in the UI. It will just enable streaming MIDI output from a plugin to the MIDI input of the next plugin in the chain.
ZynewaveKeymasterJust curious, what are the next new features/improvements on your list Frits?
Since I’ve been revisiting the whole VST support for this release, I was thinking that I ought to experiment with MIDI streaming between VST plugins, to make the VST support complete. If it turns out to require more work than I anticipate, I may decide to leave it for another time.
Adding the track template to compact mode is also on my todo list.
January 22, 2008 at 12:28 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.ZynewaveKeymasterI’ve found a small bug in zPitch. When you change between mono/stereo/surround mappings of zPitch, it mutes its output and you have to toggle monitoring off/on to get sound out of it. I’ll fix that for the next release.
ZynewaveKeymasterHi,
There are a number of key shortcuts that you can use to manipulate events and enter note events. I don’t know if they are sufficient for what you need for step editing. Check out the “common editor shortcuts” and “piano roll & drum map editor shortcuts” sections in the key shortcuts table:
http://www.zynewave.com/wiki/doku.php?id=guide:key_shortcuts
Frits
ZynewaveKeymaster- Extended the VST support to better handle surround plugins and the Waves waveshell.
ZynewaveKeymasterIf you havent’ already voted in the poll in the general chat forum, please vote in the “What OS do you use to run Podium? (2008)” topic:
ZynewaveKeymaster…”no feedback” may also mean that it might be better going back to doing internal testing
I still do plenty of internal testing, but in the case of VST support I do not have time to install hundreds of plugins and test them all. That’s why I were asking people if the plugins that they use are working ok still.
more frequent releases (4 weeks at most) would serve Podium better as recent release schedules are around 6 – 8 weeks
My excuse this time was the Christmas holiday, and my new Vista PC.
The full and interesting VST3 thread (if you have not seen it already) can be found…
Thanks, I have already posted in that topic.
ZynewaveKeymasterOther subject, concerning the final 1.97, do you confirm that the ZPitch plugin will be multichannel like the EQ ?
Yes, already done. I expect to release 1.97 this weekend.
On a sidenote, since this topic is about VST: I have briefly studied the VST3 SDK which was released by Steinberg yesterday. The VST3 spec is a completely new format that is not backward compatible with previous VST versions. So supporting VST3 is not just a matter of updating the VST support in Podium.
Of all the new features that Steinberg promotes in VST3, there is only one major feature that cannot be done already with VST 2.4 in Podium, and that’s the sample-accurate parameter automation. VST parameter automation in VST2.4 is batch processed at the start of each sample-block with the block-size defined by the ASIO driver. If you are using low-latency ASIO settings (i.e. small buffer sizes) then this is less critical, as the parameters will be updated with only a few milliseconds delay.
Other major VST3 features (silence-optimization, dynamic IO, side-chaining) are already doable with VST2.4, and is supported by Podium.
I expect that it is going to be a long time before (or even if) VST3 overtakes VST2 as the dominant format. So I won’t be looking at adding VST3 support to Podium in the near future.
ZynewaveKeymaster@Zynewave wrote:
The beta6 has a new “enable plugin processing during preset recall” option in the preferences dialog. This is disabled by default, and when disabled Podium will work as in previous versions. Enabling this option may reduce the CPU spikes that can occur when activating monitoring and when changing plugin programs/presets. Podium has so far always skipped processing while preset recall was in progress, due to the fact that there were some older plugins that would crash otherwise. This was years ago, and with a bit of luck there are not many plugins left that have problems with simultaneous processing/preset recall. Please try enabling the new option and let me know if you notice any change at all in CPU spikes, or if you find plugins that behave badly with the new option enabled.
My own tests do not show much improvement with this new option, so I’m going to remove it again and revert to the behaviour of previous Podium releases. No need to fix anything that is not broken, especially when it comes to VST support where the slightest change in host behaviour is almost certain to cause problems with some plugins. There were no feedback on the beta6, so I take it that noone saw an improvement with this option.