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.
One thing I should perhaps mention is that there appear to be some defective VSTs in my collection – When rebuilding the VST database, I get several instances of a dialog saying something about attempting to load the C++ run time library without a manifest. This has been happening for as long as I can remember, and I just hit “Ignore” and it finishes scanning and everything *seems* normal (except the aforementioned OK and cancel button issues). I get the same notice in Reaper, but neither program seems inclined to tell me which files are causing the problem. It is NOT ZASF, I verified this by moving my whole ZASF development folder OUT of the plugins folder, and I still got the same number of “no manifest” errors. I have been assuming, hopefully correctly, that Podium just ignores the plugin’s existence after noting that error.
Can you check what plugin file name is written in the scanning dialog when the error dialog pops up?
This error dialog is probably popped up by the plugin, and so does not necessarily report as an error to Podium. If at the end of the scan, Podium does not report that plugins have been quarantined, then the plugin is accepted, but it may still have corrupted Podiums memory.
Hi,
Unfortunately, Podium does not yet support streaming MIDI from one VST plugin to another. It is a frequently requested feature, but I cannot give an estimate when it will be implemented. Other Podium users have worked around it by using a plugin that can host other VST plugins, such as energyXT.
Frits
You say it’s the Preferences dialog that causes problems with OK/Cancel buttons. How about the Audio/MIDI dialog. Is that working without problems?
I recommend that you try to delete the Podium.ini file. Use the Setup/Explore Setup Folder menu command to find the folder where the Podium.ini file is located. While you’re there, please check if the setup folder is at: C:\Users\[name]\AppData\Roaming\Zynewave\Podium
After you have deleted Podium.ini you need to reconfigure your audio/Midi devices, but before you do that, check if the Preferences dialog works without problems.
I’ve split your reply into a new topic. For future support requests: If you go to the ‘Podium – Support’ page (select from the Community menu in the header), there should be a ‘Create new topic’ form at the bottom of the page.
You need to bounce enable your track with the plugin to record the plugin output. If you want to record realtime performance, you need the ‘enable realtime record bouncing’ option in the Track/Bounce context menu. Check the popup help for the B button on the track header for help on the different bounce modes.
That should be possible. It should also be possible to use the MIDI interfaces of both the MOTU and the Focusrite at the same time. I would recommend that you install the Podium Demo version to verify that your setup works with Podium, before purchasing a license.
Hi,
I don’t have any experience with the devices you mention.
To limit yourself to one MIDI output, you would need to block/mute the two channels you use for your other gear in your PX330 multitimbral setup. But you would then be down to only 14 simultaneous instruments in your PX330.
Frits
Sorry, but currently Podium cannot map MIDI control changes to VST plugin parameters. The VST plugin needs to support this internally. It is on my plan, and the way Pulse described how he tried to do it, is how I imagined it could be implemented.
I can’t say for sure if this is a bug. The problem is that you split a sample based sound in a bpm arrangement. The sound file needs to be split at the closest sample, but this is most likely not at the precise bar/beat split position. Difficult to tell with the very simular sine waves in your screenshots. If you use the pencil tool to zero-value a single sample in the second split event, is this zero-value sample then time shifted compared to the original?
I don’t see why you need to go through the bus system. You can drag any number of audio output mappings onto the empty track area to create multiple master tracks. Then you place the audio files onto each master track, or create subtracks with your sources for each master track.
