ZynewaveIt depends on how you merged the two projects. It is not enough to keep the mapping objects. You need the device definition object which contains all preset and parameter objects. If you still have these objects, then it’s possible that the link between the mapping objects and the device definition was somehow disconnected during the merge. Open the properties dialog for one of the SW1000 mappings and check if the SW1000 definition is selected in the ‘device definition’ combobox. If not, then you need to select it in the properties of all the SW1000 mappings.
Zynewave@swayzak wrote:
OT
Is there an error log for scanning the VST folder in project creation – Podium is *poofing* again.
No. The last plugin displayed in the scan progress dialog would be the one that causes problems.
Zynewave@ Frits: Perhaps you could a new profile by default? A mixer profile for those you do not want to mess with the profile editor?
In a recent release I added two new dual-monitor default profiles: “Split – timeline” and “Split – mixer”. To see these profiles you need to use the “Load default setup” menu. Note that this will overwrite your current setup file.
Zynewaveshould I have 1 ‘ CS1x ‘ global mapping for its audio output and 16 ‘ CS1x [**] ‘ midi channels which have ‘ Link to global instance’ activated
If the CS1x is multitimbral but only have a single stereo output, then that is the right setup. If you enabled the audio interface on your 16 MIDI mappings, then you would get the same stereo output of the CS1x mixed into each of the MIDI mapping tracks, which I assume is not what you want.
Zynewave@Max wrote:
@Podianer wrote:
Missing VSTs are showed by a red symbol in the devices list. Or is this not what you meant?
Well, not exactly… There was a button in old Podium wizard, after pressing it Podium has automatically searched in VST folder tree for missing dlls.
Select all the plugin mappings that are shown with a red icon, right click the selection and use the “search in file folder” menu. Podium will search in sub folders as well, so select your root VSTplugins folder unless you have several root VST folders.
ZynewaveYes, I’ll implement this at some point after you know what. Until then you can rename the folder with a windows explorer, and then relink the sound objects in Podium.
ZynewaveBut as I stated before, with the current project structure, it won’t be possible to copy the templates, I guess..
Correct. But it is possible it will support this in the future. I need to extend the .pod file format so that you can export part of the project (such as the template arrangement) and have it store references to objects outside the exported part such as mappings, presets and parameters. These references would be stored as a path/name text instead of the actual object. When you import this .pod file, Podium would then try to relink the path/name references to the objects that are already in the project.
ZynewaveBut I’m still unclear what the reason for the discrepancy between what I can see in the track inspector Midi Inputs & what is selected in the Audio/Midi interfaces dialogue…isn’t the latter automatically reflected in the former ?
No. The mapping objects encapsulate the configuration of the interfaces, allowing you to e.g. give the mapping a more meaningful name than the name of the interface it represents, and it also allows you to configure both the interface and a MIDI channel in one object, as I mentioned before. The downside to this flexibility is that you need to reconfigure these objects if you change your interface selections.
ZynewaveThese are my original default projects though, created some time ago. I didn’t really want to have to set them up again..but guess I might have to now ?
Not necessarily. Depends on what you want. When you originally created your project (using the wizard I guess), the MIDI input mappings were created based on the MIDI interfaces you had enabled at that time. Changing the selections in the interfaces dialog will not affect the MIDI input mappings already created in your project. To see what I mean with my descriptions above, you could try to create a new project with the start page.
Zynewaveany chance of allowing this in future ?
Yes, but my calendar is full for this year.
No – I only have Yoke 1 enabled as an input so only the hardware midi inputs are listed (without associated ch 1-16)
I don’t understand your description. You only have a single Yoke input enabled in the MIDI/audio interfaces setup dialog? If so, then you should only have 17 generic MIDI input mappings; One parent mapping (omni) and 16 channel child mappings. If you have selected more than one input interface in the setup dialog, then there will be 17 MIDI input mappings for each MIDI input interface you have enabled. This is provided that you created the project with the new project start page.
ZynewaveIn other apps (Cubase, FLS etc.). you only have the physical hardware Midi Inputs listed as “inputs” to a sequencer track (plus maybe “virtual” inputs like Midi Yoke).
Next on in the chain, you can then select omni/ch 1-16, depending on what you want the track to receive.
These two steps are combined in Podium when you select one of the 1-16 channel mappings. This mapping configures both the MIDI input interface as well as the MIDI channel. If you enabled multiple MIDI input interfaces before you created the new project, you should have a set of 1-16 channel mappings for each interface.
Be nice if Podium could enable any combination of hardware midi inputs & allow the focused track only to receive whatever was coming in.
So you want to use e.g. two different MIDI input controllers and have them control the same track? That is not supported yet.
ZynewaveHehe. I actually finished implementing this earlier today. Going up in 1.71.
ZynewaveThe “About Page” could need a few additions now.
The powerful track template feature for instance!
Done 😉 Thanks for reminding me.
ZynewaveHowever I can only manage to render channel 1 and not the channels further down the tree without having to assign another instance of kontakt for each channel
When you say “channel 1” I assume you are referring to MIDI channels. To make individual bounces of the instruments you have assigned to the 16 MIDI channels, you need to use the Kontakt multiple output feature. You need to configure the instruments in Kontakt so that each MIDI channel routes to different audio outputs. You should then assign these additional output mappings to tracks in Podium, and you can then bounce each of these tracks.
The last time I tried Kontakt, you needed to go to the setup screen to select how many outputs you wanted the plugin to support. If you change the number of outputs in the Kontakt setup, you may have to delete the Kontakt mappings in Podium and then reimport the plugin to make Podium create mappings for the new Kontakt outputs.
If you don’t want to mess around with Kontakt multiple outputs, you can also do it like this: Solo the Kontakt audio output and MIDI channel 1 tracks, bounce render, drag the bounced sound to a new track (the bounced recording then becomes a normal audio track), create a new bounce sound on the bounce track, unsolo MIDI channel 1 track, solo the Kontakt MIDI channel 2 track, bounce render, etc.
ZynewaveIs this a new project you created using the start page (instead of the wizard)?
The parent MIDI input mapping can be used for any MIDI channel. The child mappings named 1-16 can be used for specific MIDI input channels. Thus if you have a keyboard controller that allows you to change the MIDI channel, you can use that to control different tracks where you have assigned the 1-16 mappings.