ZynewaveWould it be feasible to include MIDI Out devices in the track input selector menu?
Support for routing the MIDI output of a plugin into the input of the plugin above it in the chain is on the roadmap. It’s not a simple thing to implement, so it won’t make it into this release.
Does the fact that the Image-Line plugins have vectorial interfaces have an influence on the newly implemented threaded processing?
As you have Reaktor, would you mind confirming that its Song Position module isn’t enacted in Podium?
Right-click structure > Built-in Modules > MIDI In > Song Position
The output of it should count up every 96th note, when playback in Podium is engaged. i haven’t been successful in achieving so. Which is weird, because other plugins that have synced LFOs or step sequencers happily lock onto the timeline.
The Image-Line UI should not affect the threaded processing or the changes to the plugin loading system in this release. I have not worked with Reaktor before, so I’m not sure how the Song Position module is supposed to behave, but if I follow your instructions then I don’t see any animation on the module during playback.
ZynewaveBeta3 is up.
– (3.2.7 beta 2) Loading any color scheme disables my audio interface (deselects it as active ASIO device in the Audio/MIDI preferences). Doesn’t happen in 3.2.6.
– (3.2.6) Setting volume or pan via numeric entry on a track with post-effects metering disables the meter. The dialog in which you enter the value (Effect Track Properties) has a blank selection for “meter mode” no matter which track the meter is set on.
Fixed. Thanks for reporting these bugs.
In addition to bug-fixes, beta3 has a new “Offline bounce buffer size” option in the Preferences dialog. I was working on a bug-fix for NI Reaktor which would crash when doing an offline bounce. It turns out that Reaktor crashes with any buffer sizes below 160 samples, and previous Podium versions used a fixed buffer size of 128 for offline bouncing. I was not able to make NI Reaktor behave with lower than 160 sample buffer sizes, so therefore this new option. The new default is “Audio driver setting”, but you can select a buffer size as low as 16 samples. The only benefit from selecting a smaller buffer size is that VST parameter automation will be smoother, since VST parameters are updated only once at the start of each buffer.
ZynewaveThanks. Good to know.
ZynewaveHi Steve,
The main search form on the website searches both the normal pages as well as the forum topics. You can input a search either on https://zynewave.com/contact/ or by clicking the ‘+’ button at the top right of each page.
ZynewaveZynewaveThanks for testing. I’ve also encountered more plugins that won’t work with the background thread option, so I suggest you ignore this option from now on as I definitely will remove it for the final release.
Beta2 is up, with a couple of bug-fixes. While testing NI Reaktor I found that it could crash if the preset was loaded in the background thread. So now presets are also loaded in the main thread, like older Podium versions. I’ve found another crash issue with offline bouncing of NI reaktor tracks, which also was present in older Podium versions. I’ll continue to work on a fix for this.
ZynewaveHi Jan. Sorry for the late response.
1/ Podium can send MIDI timing clock and MTC messages, but you need to enable that with the checkbox options for each MIDI output in the Audio/MIDI dialog. Podium should also respond to MIDI start/continue/stop messages but it does not sync to incoming MIDI timing clock or MTC messages.
2/ There are some ‘rollback’ options on the metronome preferences page.
ZynewaveIf you look at the MIDI indicator in the Podium transport toolbar, does this also become unresponsive after two seconds of playback?
Do you have other MIDI inputs that you can try?
If it is the MIDI driver that gets disconnected, then you can restart it by opening the Audio/MIDI dialog and press ok. No need to restart Podium.
Also check that you don’t have other applications running that use the MIDI ports. If you have MIDI-OX open when running Podium there may be a conflict if they both try to open the MIDI driver.
ZynewaveInstalled the demo today and I get the same behavior. I debugged the window size messages received from the plugin but I cannot make sense of it 😕
I tried changing the Podium code for handling plugin window sizing but got the same behavior. The first time the plugin window is opened it requests the host to sets its size to width=2 and height=26. Immediately after that comes a second request to set the window to its proper size. When the plugin editor has been closed and is reopened, only the first request for a size of 2×26 is sent. I hope you can live with the workaround.
ZynewaveTransfer complete. If you see this message, it means you are loading zynewave.com from the new server. I have not yet activated the SSL certificate, as I first want to make sure the website is still working properly after the transfer. If you notice any problems with your account and download of files, please let me know.
ZynewaveHi Utpara,
Sorry for not responding sooner. Can you elaborate on what you mean with flat and dull? Is it simply a matter of audio volume difference, or does the frequency spectrum change?
Depending on the plugins you use, they could produce a different output if their processing is called faster than realtime. Also, the Podium offline rendering uses a buffer size of maximum 128 samples, which also could produce slightly different results compared to if you are monitoring with a higher ASIO buffer size. Plugin parameter automation is processed at the beginning of each buffer, so a smaller buffer size should result in smoother parameter automation.
ZynewaveIt is also worth mentioning that you can use the Track menu to configure at which point in the master effect chain that you want the bounce to be extracted. So if you have moved the master fader or effects above the bounce point, then the bounced audio file will not include these effects.
ZynewaveZynewaveZynewaveHi John,
How do you check the memory leaks? When do they occur?
What do you use to check the high resource usage; The Windows Task Manager or the Podium CPU indicator? The Podium CPU indicator is not a measurement of how much your total available CPU power is utilized, rather it is a measurement of how close you are to experiencing audio drop outs. Podium Free is limited to only one CPU core for plugins, so if you e.g. have a quad-core machine, when the Podium indicator hits 100% the Windows task manager will show ~25%. The full Podium version uses all available cores.
Which plugins are crashing for you in Podium Free? I’m currently working on a revision of the plugin loading, so newer Podium versions should be more stable when loading plugins, but I cannot guarantee that plugins that previously crashed will not crash with the newer versions.