Hi Shields. I fixed some issues with the detection of free memory in 3.2.2, which I thought had solved the problem. Podium 3.2.2 will use up to half the available free memory for caching sound in memory, before it starts to write the cache to disk. You reported earlier that you saw memory usage up to +3 GB. That should be fixed in 3.2.2 to stay well below 2 GB on a PC with 4 GB.
For the upcoming Podium 3.2.3 I’ve added a “sound cache maximum memory usage” setting to the engine preferences page. I’ve set the default to 512 MB. This should further reduce the risk of plugins running out of memory during rendering.
Thanks for reporting this. This is fixed in the upcoming 3.2.3 release. The auto-assigned audio input will be assigned to the composite group track if any tracks within the composite group has focus.
Sorry, it’s still not clear to me. I’m curious as to why you wan’t to route all your normal and bus return tracks to a single submix track? If the only purpose of the submix track is to route the audio to the master track, and no other tracks are going to the master track, then why not go straight to the master?
I’m close to logging off for today, and I’ll be travelling to visit family tomorrow, so it may be a couple of days before I can reply again.
From your description, I’m not sure what you mean by submix. Do you just want one submix track, or several submix tracks? If you just want one, I can’t see what you want to achieve by inserting a separate submix group track. You can enable multiple gain faders on the master track, if you want to control gain both before and after the master effects.
If you don’t want any direct signal going through to the master, you could skip using send/returns, and instead just place the ten tracks in a group track. What effects you currently have on your bus return track would go on the group track.
If you still want the send/return mappings, you should move the track fader up above the send fader by using the track context menu -> Fader -> Set Fader After Sends. After that you can set the track gain to off.
Thanks for the bug report. I couldn’t provoke a crash on my machine, but I did find an issue with initialization of disconnected USB MIDI devices. I have uploaded a 3.2.2 beta with a fix on the My Downloads page. If you find the time to test this beta, please report whether the crash bug is gone.
I have Kontakt 4.2.4 full, and recently updated Kontakt Player to the latest 5.3.0 version. Is it possible for you to update to 5.3.0 so you can confirm that the issue is still present with the latest version?
I’m probably going to upgrade my Kontakt full version to 5, with the 50% deal that NI announced today. I’m going to spend much of December working with Kontakt. Before that I’m going to release a minor Podium update with various fixes.
The DDMF ColourEQ x64 has noisy clicks and occasional loud pops whenever I adjust any of the frequency parameters with sound playing. Anyone else notice this?
Edit: I’ve updated the page with what I have tested so far:
http://zynewave.com/recommended-freeware-plugins/
Thanks for the suggestions. I’m going through them right now.
@Pulse: AxTube?
I tried MauSynth x64: When the plugin editor is open, it intercepted some Podium key shortcuts (such as Ctrl+z), and changing presets in the track inspector did not work.
The purpose of the page is to give a good introduction to VST plugins for new users. This means that I’ll only include plugins where I can link to a download page that has clear download instructions. IMO, that disqualifies LinuxSampler and various others. I even had problems with the Voxengo pages, where I managed to download several demo versions of commercial plugins, before I noticed the actual download links were above the plugin description. It’s clearly written in the text, but I was just quickly looking for download link buttons.
I also have a problem with UVI Workstation. When installing, it asks to install the PACE license system. I’ve had plenty of bad experiences with this years ago, so I stay away from that. A shame, because the UI screenshots look beautiful.
I’m even considering removing Independence Free from the list, because it pops up an annoying dialog during Podium plugin scanning, asking for registration. Not a smooth user experience.
I’ve been going through the kvr database and the freeware suggestions made on this forum, and have compiled this list:
http://zynewave.com/recommended-freeware-plugins/
It’s been a while since I last checked out the available freeware plugins so I may have missed some obvious candidates for the list. Please check out the page, and let me know if you have suggestions for additions or if you have experienced problems with any of the listed plugins.
Eventually I will link to the page on the Podium and Podium Free product pages.
Does Podium have any issues with multiple copies of a plugin within the path? Or different plugins that have the same internal name?
That should not be an issue. Plugins are identified by their file path.
what is the point of “rebuild plugin database” if it keeps pointers to deleted folders / plugins? And how do I tell it to actually start clean?
Podium will try to reconfigure mappings of plugins that have moved location. If you have the same plugin filename in multiple folders, then this may cause the mappings to not be reassigned, and you’ll have to fix those mappings manually. The plugin combobox selectors in the arrangement editor should be highlighted in red if the referenced plugins are missing.
ZASF is absolutely NOT multi-processor safe (hence my surprise at discovering that Reaper had found a way to do it), so I have to run Podium with the VST multiprocessing option OFF.
I would guess Reaper uses a method where a plugin instance is designated to a specific thread. That can cure some of the weaknesses of plugins that are not multithread safe.
I have considered the scorched-earth “wipe it clean and reinstall from scratch” approach, on the thought that some file that didn’t get replaced by the 3.2.1 install may have become corrupted. Does Podium leave any droppings in the registry that I will need to go clean up after an uninstall?
The installer engine stores some settings in the registry, required for clean uninstallation, but the Podium app does not store anything in the registry. Rereading my first post, I see I forgot some important info: Before you delete the Podium.ini file, you should quit Podium. Otherwise, when you quit Podium, it will just rewrite the Podium.ini file with the old settings still loaded in memory.