Hello Miroslav. I’ve made some updates to the website during the last couple of days, and one thing I changed was I added an extension to upgrade periods expiring since the last release. If you check your download page you should see the download links again.
I added the upgrade extension as a compensation for the delayed release of the next 3.4 version. Podium has been in development for almost 30 years now, and I occasionally devote time to do a revision of the codebase to avoid the ‘legacy’ code syndrome. Release 3.4.0 is all about internal improvements and modernization of the entire codebase, which is why it is taking some time to finish.
Thanks for the crash file. The crash happens in the code for the mixer region, specifically on a track with an audio input that is armed for recording. It tries to display the meter before the engine is up and running. I’ll get that fixed.
The idea behind the support for having multiple arrangements in a project was indeed to enable making an entire album of songs in one project. It works fine for MIDI based arrangements. If you have a lot of audio tracks then the amount of wave files loaded can take up a lot of RAM. The actual wave files are streamed but Podium loads the miniature wave images into memory and that can add up as well. I intend to do a revision of the audio streaming support in Podium at some point and optimization of RAM usage will be a priority.
It could be a corrupt .pod file. Did you have a crash when saving a project file?
Ideally Podium should be able to detect and recover from a corrupt .pod file instead of just freezing. Please email the crash file to me.
The reason Podium freezes when booting must be because it tries to load the problematic project file. You can recover from this by opening the Podium.ini file in a text editor (with Podium closed) and remove the [OpenProjects] block.
Another option is to adjust the gain on the sound events. If there is a pause between your sections you could split the sound event and increase the gain on the solo part. Even if there isn’t a natural pause where you want to split the event, you could still do the split, overlap the events slightly and apply crossfade to fade in/out the gain change.
Hi Ted. Sidechain processing is an integral part of a compressor and you can’t really achieve the same thing within the Podium mixer. Your workaround suggestion with detecting a parameter automation curve from an audio signal could work in theory, but the Podium automation sequences is not optimized for fast changing curves which a sidechain signal requires.
I did a search for freeware sidechain compressors, and I found a couple of candidates that you could try out. I haven’t tested them myself:
https://www.meldaproduction.com/MCompressor/
Molot
Edit: Don’t know why the forum decided to format the links like a quote.
The way I would do it with the current Podium version 3.3.3 is to create a dedicated “Shapes” project containing my library of automation sequences laid out on tracks in an arrangement. The tracks could be named with the category of the shapes on each track. Since version 3.3.0 you can have multiple projects open, so when I need a shape I would switch to the Shapes project tab, select the curve sequence event, press copy, switch back to the work-in-progress project and paste it in.
Compared to your Inspector suggestion, this solution requires the extra step of switching between projects, but you get a very nice graphical overview of your shapes library when you view your Shapes arrangement.
This feature has not been implemented yet.
I just tried the Ample Percussion Cloudrum v1.01 freeware plugin and I did not experience any problems scanning the plugin and using it in an arrangement. I tested with Podium x64 v3.3.3.
Hi Andy. My own tests show that the download links are working again now. Let me know if you still have problems.
Give it another try. I found that the shopping-cart update had imposed restrictions on the download file paths. I’ve patched this now.
Hi Andy. Can you try again now? My shopping-cart plugin had updated overnight and I needed to manually initiate a database update.
Sorry for the late reply. If by sync you mean Podium should lock to the tempo of the drum machine, then no. Podium needs to be the clock master. You can enable MTC and/or Timing Clock for each MIDI output in the Interfaces dialog. This should enable the drum machine to lock to the tempo set in Podium.