ZynewaveI see the latest Podium 1.24 release has made some parts of your tutorial out of date 😳
Specifically it is the description of the ‘audio mixer mappings’ and the ‘audio input mappings’ panels in the wizard, that are now joined into one ‘audio mappings’ panel. The 1.24 release also creates audio output mappings for all enabled audio interface channels, instead of a single ‘master out’ mapping.
Other than that, it’s looking good 🙂
btw, for a lot of people (the ones used to using audio applications etc) a even quicker quickguide might come in handy. Something like:
Start Podium
Go thru the entire Project Wizard
Create a “preset arrangement” that you can copy when starting working on a new song.
Copy the preset arrangement and start making music.
This pretty much sums up the functionality of the new ‘quick setup’ button in the latest 1.24 release. Have you tried this yet?
Frits
ZynewaveHi,
I signed up for their developer kit, but I need to mail them a signed copy of the agreement before I can get hold of the kit. Currently there are 3-4 other frequently requested major features that have a higher priority. That includes generic UI for VST plugins without their own editor, count-in options for recording and auto-save options.
ZynewaveZynewavewill it be added to the list ?
It’s scribbled down on my notepad.
ZynewaveAdded to the plan.
ZynewaveHmm, I’m not sure that I understand this.
Global plugins can work in a multichannel way ?
Global plugins differ from insert plugins, in that there are several mappings that all refer to the same plugin instance. This is needed when you have multitimbral or multi-output plugins. You need the different mappings to be able to route separate MIDI channels and audio channels in the Podium mixer. The mappings are linked to the specific plugin instance with the ‘global instance’ number in the mapping properties dialog. With the project wizard you can import a definition file for a global plugin several times, and each time Podium will then duplicate the mappings but allocate a new global instance number, so that you can work with multiple instances of a global plugin.
ZynewaveI thought that Podium could count : “2 + 2 + 2 + 2 = 8, so I map 8 outputs”…
The problem is that the 2+2+2+2 for most of the plugins on the market are indicating that the plugin supports multiple stereo outputs. If I were to interpret this as an 8 channel mapping, then plugins like Battery, Kontakt, MicroTonic, RMIV, sfz+, etc. would not be imported correctly.
ZynewaveSince Podium finds that a plugin has x ins and x outs, I suppose that it will not be too difficult to set the mapping accordingly ?
The way Podium sets up mono or stereo mappings are according to the VST plugin GetInputProperties/GetOutputProperties calls, which has a flag for whether a channel is mono or stereo. This is why Podium can correctly set up multiple mono and stereo mappings for some (e.g. Native Instruments) plugins that support both. If Podium is to automatically set up surround mappings, the plugin will have to support the GetSpeakerArrangement call. Do you know if your plugins/SynthEdit support this function?
ZynewaveComments to your tutorial:
Very impressive. And this is now the second user-created tutorial that is appearing. I appreciate your efforts, as it hopefully will be a help for other users.
In the tutorial you describe how a user can use the ‘Import file’ menu to import device definitions. This will work in most cases, but the recommended way is to use the ‘import device definition’ command in the project wizard, because; The wizard will automatically search for the plugins in the VST root folder specified by the user, in case the plugins are not found at the default location indicated in the definition file. The wizard will also handle cases where you import a definition for a global plugin that already is imported, and will then assign a new instance number to the second import and reuse the old device definition object from the first import.
Your explanation of how to import a wave file onto a track could be done in fewer steps. You describe that you must go back in the browser to import the file and then back to the arrangement to open a list window to drag the imported object onto the track. Why not just open the list window in the arrangement, locate the file with the embedded file browser in the right hand side of the list window, and drag the file onto the track. This will then automatically import the file into the project.
ZynewaveHi Jean-Marc,
I’ve updated some of the info in the device definition forum: AcousModules
It would be nice if you could create a page on your site, which acts as a sort of portal for Podium related stuff. It could be your current mappings.htm added with download links for the plugins. Then I can just link to this page in the device definition forum, and skip showing download links for the plugins. You seem to update your plugins quicker than I update the links 😮
ZynewaveI assume you mean surround/multi-channel configurations. I’ll look into it.
ZynewaveI’ll add it to the plan, but currently I consider it a low priority.
Zynewavebut if it is a parameter track of a plugin for this audio track it can’t be at the same time a child of the audio, no ?
Not by default layout. If the child track containing the audio playing into the plugin does not have a mapping assigned, then it may work if you move the plugin parameter tracks as child tracks under the audio track. The audio may then show in the curve editor, but the track layout would be somewhat confusing.
ZynewaveOk, thanks. I’ll add it to the plan.
ZynewaveI’ll add it to the plan. Recently I updated the curve editor to show a translucent text field with the value of the currently edited event. A similar method could be used for notes, where info would be written in a translucent box next to the note event you’re dragging.