Hi. How far should I adjust buffer size, now that I can? Or would it be best to leave at 128 default? The benefit of smoother automation makes me want to lower it a lot, but are there drawbacks to low buffer size? Sorry if I ask too much—
If you set it to 128, then the bounced audio should be identical to previous Podium versions (unless you use an even lower ASIO buffer size). Since the buffer size can affect the generated audio, I recommend leaving it at the ‘Audio driver’ setting. That way the bounced audio should be identical to what you are hearing during normal playback. The drawback to lowering the buffer size is that Reaktor will crash 😉 Other plugins may have similar problems. The bounce rendering process should also take longer with smaller buffer sizes, since the overhead of handling the buffer changes will be larger.
… Song Position module isn’t enacted in Podium…
… 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.
Eek! Not sure where i went wrong, previously. The Song Position module works as expected now. It was likely an error on my part, for the particular instance within a particular ensemble.
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.
Thanks for the info mate!
Quick error report, don’t know if it’s related to the changes in this version.
“A plugin has performed an illegal action.
[…] Twin 2 […]
This may have caused memory corruption in Podium. […]”
Plugin: FabFilter Twin 2 version 2.27 (newest at this time), x64.
This happened while switching preset from “Keys – Other – FM Piano 1 DJM” to “Pad – Soft A-M – Afterglow O” during playback of just one track. Didn’t crash Podium, but killed all audio until I powered the arrangement off. Doesn’t seem easily reproducible.
Tested this, and I can provoke the crash too. It can also crash in the previous Podium 3.2.6 release, so it is not related to the new update of the plugin loading. It seems that if the preset switch is done while a note is playing, the plugin crash then occurs at the start of the next note. I don’t think I can do anything to prevent that.
Beta4 is up, which hopefully is the last beta before I release 3.2.7. This beta has a few more optimizations and code cleanup. If you test the beta, please let me know if you find any problems.
A little off topic with this, but could this update allow for multiple tracks to be selected & moved at the same time? If I import a bunch of, say, drum samples onto individual tracks, I then have to select them one by one to move to a drum group track. Not a big deal, until you have to repeat the same action 15 or 20 times. Just a workflow issue.
And maybe I’ve missed this, but a shortcut to select all events on one track would help the workflow too.
Multi-select of tracks won’t make it into this release. It’s on the roadmap, but I have a few other things I’d like to work on before that. A menu command for selecting all events on the focus track is one I’ve missed too, so I will put that in for the final 3.2.7 release.
Everything looks fine on my end. Running 32 bit on Win7 64
Same here, no problems running 32-bit Podium beta on Win8.1 64.
FWIW I can’t offline bounce rewired Reason 5 without hiccups in the audio, despite trying various settings in Preferences. But had the same issue in 3.2.6 also. (Other rewire hosts can do it, but… they’re not Podium.)
On a very trivial note, there was a UI issue I mentioned back in the 3.2.6 beta thread, about ‘dirty’ MIDI event list when making changes in a separate piano roll window. But again not a big deal.
Thanks for testing. The final 3.2.7 installer is now available.
All good with 64bit Podium 3.2.7 on Win10 x64, thanks Frits.
Since downloading 3.2.7, I haven’t had any issues with closing Podium. In prior versions I would have a random plugin crash when closing out the session, nothing specific. But now I haven’t had even one crash. I also had success running Rez vst, formerly quarantined. Now I need to go back and see if the other 4 or 5 quarantined plugs will run.
All in all I’m very pleased with this system! Thank you very much—
FR: Not necessary at all, but it would be neat to be able to use middle mouse click(not scroll) for some function, or perhaps to work into shortcut combos.
So far so good.
Podium 3.2.7 is definitely more stable and efficient then previous version.
Thank you for improvements (and I’m glad I got access to them).
Windows 8.1 64bit, old Wolfdale E7500 CPU, ASUS Xonar U3, 7GB of DDR2, ASIO4ALL with a bunch of VST’s (not much but still better then AMD-E350 platform) it works more then fine.
P.S. I’ve discovered a strange issue. When opening some old projects saved before with the Podium Free (3.x. – one of the first realases I guess) with problems I got the same problems with the project on full P.3.2.4-7. And the best part is that I’ve exchanged every VST in the projects, re-aranged the compositions and re-save them as a new files. Still buggy. Well it’s only a matter of 2 projects so no big deal. But still it’s pretty interesting on how did this happened.
You must be logged in to reply to this topic.