swayzak.
swayzakFrits
Midi Inputs (in browser of Arrangement window) first lists Midi Omni & 1 -16, followed by the actual hardware inputs.
What are these ?
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.
swayzak@Zynewave wrote:
Is 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.
Thanks, but I’m not sure I’m any the wiser 😕
In 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.
As I’ve mentioned before, this is done as per track focus, so you can audition different tracks one after t’other regardless of physical midi input.
With Podium, I have to run an “all midi inputs to Midi yoke 1” instance of MidiOx & enable this as the device midi input.
Be nice if Podium could enable any combination of hardware midi inputs & allow the focused track only to receive whatever was coming in.
This would allow track by track live auditioning without me having to use Midi Yoke (as I can in all other sequencers)…..
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.
swayzak@Zynewave wrote:
So you want to use e.g. two different MIDI input controllers and have them control the same track? That is not supported yet.
Exactly – AFAIK this is how most other hosts behave (Cubase SX2, FLS 6, Orion etc).
To do this live in Podium (e.g play some keys in loop recording, add parameter tweaks with BCR/F or Control Freak etc.) I have to run the “everything to Yoke 1” Midi Ox instance prior to launching Podium.
It’s not a show stopper I guess, just a bit of a pain…any chance of allowing this in future ?
swayzak@Zynewave wrote:
In 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.
No – I only have Yoke 1 enabled as an input so only the hardware midi inputs are listed (without associated ch 1-16)
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.
swayzak@Zynewave wrote:
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.
Hmm..now I’m even more confused 😕
I have only Yoke 1 checked in Midi Inputs (Midi/Audio interfaces setup).
Yet this doesn’t even appear in the available Inputs for a track.
Like I say, it lists Midi Ch’s Omni & 1 – 16 then my hardware interfaces (HDSP 1 & 2, sw1000 Midi In, BCR & BCF) without any assoc midi channels.
Maybe those Midi Ch’s refer to yoke 1 as Podium received midi ok with omni selected…
These 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 ?
swayzak
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.
swayzak@Zynewave wrote:
These 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.
OK – off to experiment now 🙂
But 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 ?
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.
swayzakthanks again Frits
I have to say that I’m beginning to feel very much out of my depth in Podium.
I had a go at setting up a new project – worked as you said, with correct inputs available (just the omni & 16 midi channels visible).
Scanned VSTi’s OK (although SynC Modular caused Podium to “poof”, so I added this manually afterwards…seemed to load in OK then).
But now I would like to “transfer” the track structure (and all the sw1000 / plugstation device definitions & Sysex parameters) into this “new” default project.
Is there an easy way to do this ?
And the windows / screens thing still leaves me utterly confused – before I’d just about managed to get a screen 1 – 3 setup (1 = sequencer arrangement left monitor, mixer right monitor 2 = sequencer left, part editor right 3 = sequencer left, main browser window right).
Tried to set this up in the New Project but can’t seem to do it…. 🙁
Podium is undoubtedly very powerful but is difficult to get in to (coming from other DAWs) – at least for me !
swayzakRight, getting somewhere now…
Have imported my default “Direct Monitoring” .pod as an Arrangement.
Then tidied up the Devices list (had 2 Devices folders, one from the new scan and the imported one) by moving the sw1000 / plugstation / Gigastudio / Audio Outputs folders over to the new Devices folder.
Then deleted the imported one.
Now I want arrange the windows / screens.
How do I open up the main mixer on the right monitor.
I’ve opened a New Browser window and moved it over to the right monitor – can I change this into a mixer ?
Actually, there’s no particular reason why I should have a separate “direct monitoring” & “mixdown” .pod’s – I can just have them as the 2 listed available arrangements in a single Project / Template file…
PodianerI’ve opened a New Browser window and moved it over to the right monitor – can I change this into a mixer ?
Yes! I have done that. Create a new profile for that, make sure the “sync browser” option is checked, and there you go! 😉 you can switch through profiles by pressing F8. Having selected the mixer profile then, Podium will remember that you used the browser window as a mixer.
@ Frits: Perhaps you could add a new profile by default? A mixer profile for those you do not want to mess with the profile editor?
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.