acousmod.
acousmodHi,
I’m trying to simply assign a track output to a particular output of the interface.
I thought that I have understood how it works, but it seems that I was mistaken 😕
I have a 16 channels output mapping which is working on the top track.
I have made some mono to mono mappings (these are mono tracks) with a First Channel shift in the Source channels/speakers.
I thought that the sound of the track will go the this audio output, but it goes always to the first one, whatever the First channel value is.
I’ve choosen as the mapping type Mixer bus, since it is not a MIDI/Audio interface nor a Software plugin.
Where am I wrong ???
Is were a simpler way ?
Thanks !
edited : I need to have a master volume track, so I could not use 16 mono interface mappings…
ZynewaveHi,
I’m not entirely sure what you want to achieve. Could you email me a simplified version of your project?
acousmod– master out mapping with 16 outputs
– volume control of master out
– track 1 = mapping 1>1 (source first channel 1) to go through out 1
– track 2 = mapping 1>1 (source first channel 2) to go through out 2
– track 3 = mapping 1>1 (source first channel 3) to go through out 3
etc.
ZynewaveYou have set up your bus 1-3 mappings to be both source and target. You need to modify these bus mappings so they only send mono into the bus (and not return). These mono mappings can be offset to the desired channel number in the bus. Then you create a new bus return mapping configured to extract 16 channels of the bus, which then will be streamed correctly to the 16 channel master out. I have emailed a modified project back to you.
acousmodThanks Frits.
I see now.
But this bus routing remains very strange for me, since in other mappings the “Target” represents the source audio track and the “Source” represents the target upper track, here the “Target” represents the input of the bus return, not the audio track as usual…
For me, this is very confusing, because for the other mappings the signal goes always “from bottom to top”.
But OK, I think that I will no more make the mistake 😉
ZynewaveBut this bus routing remains very strange for me, since in other mappings the “Target” represents the source audio track and the “Source” represents the target upper track
You should view ‘target’ and ‘source’ from the point of view of the Podium engine. Source is always something that provides input to the mixer. When mapping soundcards, source is the soundcard inputs. When mapping plugins and busses, source is the plugin and bus outputs.
acousmodThank you Frits for trying to explain this engine’s point of view.
But my brain seems to be very different, and the more I try to understand, the more I am confused 😥
I think that I am too distorted by the “signal point of view”, where outputs go to inputs.
I will apply what I know is working, but it seems that my case is hopeless…
Thanks nevertheless !
ZynewaveIf anyone has a better way of naming the ‘source’ and ‘target’ settings in the mapping properties dialog, then I’m all ears. I originally named these input and output, but the problem is that when you map plugins and soundcards, input and output has opposite meanings. The soundcard provides audio to the host through the soundcard inputs, but plugins provides audio through the plugin outputs. Instead of mapping soundcard input, you should be mapping microphone output, and instead of soundcard output, you should be mapping speaker/headphone inputs. But when dealing with soundcards, people are accustomed to the input/output labeling on the actual soundcard.
acousmodHi,
I have recently spend some time with a friend to show him Podium, and I’m also trying to make a tutorial in French for my general site about multichannel sound.
Something that appears to me to be a possible solution for helping people with the inputs / outputs setup of mappings will be perhaps to name the function according to the position in the hierarchy, instead of having the standard source / target names.
The problem is that it will need different names according to the type of mapping : MIDI/Audio Interface, Mixer bus and Software plugin.
For example :
– MIDI/Audio Interface Output : From Tracks (To Audio Card) / …
– MIDI/Audio Interface Input : … / From Audio Card (To Track)
– Mixer Bus Send : From Current or Lower Track / …
– Mixer Bus Return : … / To Upper Track (or Level, or Lane ?)
– Software Plugin : From Current or Lower Track / To Upper Track
Perhaps also will it be possible to have the selections that have no sens greyed, like the Source in a MIDI/Audio Interface or a Bus Send mapping.
What do you think about ?
I suppose that most people use the pre-made mappings and have no need for custom mappings.
Does it will have some interest in other cases than multichannel mappings ???
ZynewaveI’ve added ‘Change target/source labels in device mapping properties dialog according to selected device type.’ to the list.
acousmodoh… well… nice… 🙂