ZynewaveZynewaveHello. Audio time stretching is currently not supported in Podium. I’m working towards doing an update of the plugin support in Podium, which likely will include support for VST3. Audio resampling/time-stretching is lower on my priority list.
ZynewaveZynewavePodium 3.4.4 is now released, which should have these bugs fixed. Sorry for taking so long with the release. The crashes were due to null-pointer references, which is the most frequently occurring type of bug I’ve had to deal with over the years. In an effort to avoid these kinds of crash bugs in the future I have adopted a new system of how pointers/references are handled across the entire Podium codebase. If you encounter further crashes please do email the crash dump file to me.
Zynewave3.4.4 is now released.
ZynewaveI’ve added a “Crossfade dragged overlapping sound events” option to the tracks region properties dialog. You can either toggle this option when you switch between editing podcasts and music projects, or you can create a dedicated podcast editor profile. Will be available in Podium 3.4.4.
ZynewaveCrossfade is currently always applied when you move sound events onto other sound events. The undo command is indeed the only way to revert that. The ctrl/alt/shift keys all have a function when dragging events, so there is no simple way to implement a key shortcut to prevent the crossfade.
One solution would be to add an option to the Tracks Region Properties dialog, but you would need to toggle that option if you want to change behavior. Do you need to avoid the crossfade consistently, or just occasionally?
ZynewaveAt some point I will have to look into either CLAP or VST3 support. I expect it will happen in 2023. From a development perspective I would prefer to start by adding support for CLAP, unless there are a substantial number of new plugins that will only support VST3.
ZynewaveHi. There is currently no option to include plugin setting changes as part of the arrangement undo history. At some point in the future I will do a revision of the plugin support in Podium, and this feature will be something I will try to incorporate. I don’t have a time frame.
ZynewaveHi. All Podium versions should still work. It’s possible that your editor setup in the Podium.ini file has been corrupted. If you can access the menus in the top menu bar, then select the “Setup/Restore Default Editor Profiles” menu.
ZynewaveThanks for the crash.dmp file. It seems this particular crash occurred when quitting Podium, so I wonder if this is a different type of crash than the one you describe. Does the crash happen as soon as you record arm the track? If either of you have more crash.dmp files from other crashes I would appreciate if you can send them to me.
ZynewavePlease send the dmp file to info @ zynewave.com.
ZynewaveNot supported yet, sorry. Over the years the feature priorities have shifted, and this feature is not there yet. At some point I’m going to work on supporting other plugin formats, either VST3 or the new Clap plugin format, and at that point the MIDI support will be revised as well. I can’t give you an estimate at this point.
ZynewaveThanks for the dmp file. The crash happens when Podium tries to access the “WaveformImageCache.db” file that should be located in your “Projects root folder” (as specified in Preferences).
I will fix Podium so that it doesn’t crash when the db access fails, but from the dmp file I cannot see what the specific error is. Could you check that your WaveformImageCache.db is not set as read-only and that it is not blocked by your firewall?
If you can’t find any issues with the WaveformImageCache.db file you could try to delete it. Podium should then regenerate all the waveform images when it starts up.
ZynewavePlease send me the dmp file to my email: info at zynewave.com