Yes, Podium can do what you want.
If you had the “Scan and import surround VST plugins” option checked when you created the project on the start page, you should have a set of surround audio input and output mappings. They should be named something like “Audio In [5.1]”, “Audio Out [5.1]” etc. There should also be “Audio In [32]” and “Audio Out [32]” mapings if your ASIO driver supports 32 channels. If you don’t see these mappings, you can create your own variations by copying one of the mono/stereo mappings and modify the name and the audio configuration settings in the mapping properties dialog.
Depending on how you have implemented the speaker configuration support in your plugins, the project should have multiple I/O insert mappings for your plugins. If not, again you can set it up manually in Podium by modifying the audio configuration properties in the plugin mappings.
Frits
@Malcolm Jacobson wrote:
Hi Fritz,
Hi Malcolm, thanks for the bug-report.
• The MIDI data for “Sustain” does not appear to be getting through to the ReWire device. My controller passes sustain information correctly to VSTi’s within Podium, but the same data does not get through to Reason 4.
On closer inspection, I have found that when playing a MIDI keyboard in Podium routed through to a Reason instrument, Reason apparently does not respond as expected to note-on messages with zero-velocity. This is a standard method of sending note-offs and is used by most MIDI keyboards. So what to you seem as a non-responding sustain pedal, it’s actually because Reason never interprets any note-off messages. I’ll fix this by converting to true note-off messages when routing MIDI through to ReWire devices. Note that this is not an issue with sequenced notes in Podium, as these are sent out using true note-off messages.
• When I create a new Instrument in Reason, I get an error message in Podium that says “Reason ReWire error: Invalid parameter (GetControllerInfo)”.
Confirmed. I’ll fix that.
Most of my ReWire instruments are stereo. When I look at the list of returns the only stereo pair appears to be for channels 1 + 2 (Mix L+R). Is it possible to link a pair of returns from a ReWire device to a stereo track?
An example: Open the properties dialog for the Reason “Channel 3” mapping. Change “Mono” to “Stereo” in the plugin output combobox. Name the mapping “Channel 3+4” or something similar. If you always use stereo pairings, you can then delete the redundant “Channel 4” mono mapping object.
@Vonbrucken wrote:
FL Studio can’t find Podium as a Rewire client …
Podium only supports ReWire master/mixer mode. Implementing ReWire client support is a whole lot more work, so don’t expect to see that soon.
The first ReWire related bug has been reported. I’ll release a 2.03 bug-fix version in a few days time with this fix:
Fix: Podium would show a ReWire error message if the ReWire option was enabled in the preferences and no ReWire.dll was installed on the PC. Podium would also crash on exit if the ReWire.dll was not found.
Until then, if you don’t have any ReWire applications installed on your machine, installing 2.02 is not recommended.
You’re right that this does not give me that many clues on how to reproduce the bug.
When the error happens, does the UI freeze in any way? When you say that you need to kill the task, does that mean you can’t exit Podium normally?
If I press the power off it continues too !
That must mean that the power button remains lit, even if you try to disable it?
I managed to reproduce the bug. Fixed in next 2.03 release.
I managed to reproduce the crash with the demo. When I ran it in debugger mode, the crash appears to happen inside the plugin when Podium tries to unload the plugin dll from memory. I tried changing various things in the Podium plugin handling, but I could not create a situation where the plugin did not crash. I think this is one that Imageline has to look into. Try to contact Imageline support, and tell them that they can contact me for assistance with testing.
Podium 2.02 final is now released.
@Conquistador wrote:
Mentioned earlier but it’s has come up again…closing a Project (not Podium) before closing a Rewire slave (in this case Project 5) results in this error which might not provide enough information for a user. It also looked a bit vague.
I did not get this error with the P5 demo on Vista 32 bit. But I’ve changed the way Podium closes ReWire devices, so you shouldn’t see this error any longer.
Rewire Mappings are still labelled as FX in Beta 3.
In 2.02 final the ReWire audio output mappings are indicated by a small ReWire logo symbol instead of FX.
Beta3 is uploaded. There are a lot of bugfixes and extended error reporting. This hopefully is the last beta, and the final 2.02 will be released this week. Please let me know if you find problems with beta3.
@Conquistador wrote:
Hmmmm P5 does not start up automatically when using the “Import Rewire devices command” but it will auto start after dragging the mapping to a track in a new project.
The ReWire dlls are not opened when using the import command. It’s only when assigned to a track and power is on that the devices and their panels are opened.
Once imported into an existing project Reason and P5 both showed up instantly but…when I dragged P5 to a track in Podium it showed this error…
…again it had no bearing on the functionality of Podium, Reason or P5 but the error was there. I could and did open the Rewire devices succesfully.
I’m not getting that error with the P5 demo. Maybe the error only occurs on Vista 64 bit OS.
@UncleAge wrote:
Is there a way to send a Rewire slave an auto close command from the Rewire master?
Yes there is, and Podium is using it. The only ReWire device I’ve found that does not respond to host open/close commands is Ableton Live (7.07 demo). You need to start Live manually after starting Podium to run it in ReWire slave mode.