Zynewave.
kagemushaHi,
Recently I conected my USB keystation (Radium M-Audio) to control some VSTis in Podium. I don’t use midi Outs but I use the external midi controller just on one channel.
A thing that wonders me; is there another way of playing/controlling certain VSTis then to have to change the device mapping of the USB midi Keyboard on the track you want to control/play. If you have some complex track structure changing in the device mappings is prone for doing something wrong.
As it is now the only way is to drag the input device mapping of the midiport to another track to play that one. I only use one channel (programmed in the keyboard) so it would be easy if I could set all tracks (initial) with that input device (ch1) to control them. But Podium doesn’t allow it because when I assign the input device to another track it is de-assigned in the previous one. In a way that is logical because I assume that’s the logical behaviour in Podiums concept >> otherwise all the tracks would play on channel 1. But it’s also a restriction.
I think it would make sense that you could assign
the same midi input mapping to all the tracks you want. but to make it active with a switch if you want to play/control it. Instead of having to drag or replace the input mapping the the track you want to play.
Also I tried to assign a midi mapping to a track to control a parent track (with a VSTi) but that doesn’t seem to work. I have to assign the midi input mapping on the VSTi track itself: is it intended that way? I assumed that in the concept of podium also midi would behave like the audio routings >> like a tree.
Also I’m missing a bit a way of global midi controller parameters. Now I have to create for every VSTi – in its own device defenition browser new parameter like for example controller 21. but it is only accesible via that particular VSTi. It would be great if you could make global parameters which are accesible for all VSTis (or other tracks) you make.
Also a way to make “Global” parameters via the project wizard would spare some time
I like the way you can choose between curves and parameter value blocks.
Is something changed in the stickies behaviour. I noticed they didn’t work but in Podium 0.91 only the devices in the project browser is able to attach some stickies but no other object can have a sticky.
Greetings
Kagemusha
ZynewaveHi,
I think it would make sense that you could assign the same midi input mapping to all the tracks you want. but to make it active with a switch if you want to play/control it. Instead of having to drag or replace the input mapping the the track you want to play.
This would require that when you’re dragging the input mapping you can use e.g. control key to drop a ‘duplicate’ assignment of the mapping. Furthermore it would require that I implement the input mapping on/off button (which is on the plan). When you want to change MIDI input to another track you would need to switch the mapping on the current track off and switch it on on the new track. A lot of work and a lot of things that can go wrong or be confusing. I have another suggestion:
I could implement a global input mapping mechanism. In the input panel list in the track inspector you would have an ‘Assign as global’ menu in the list popup menu. This would set a single MIDI input mapping as global indicated e.g. by a red pinhead image in the list. Whenever you select a track and this track does not have an input mapping assigned already, then the global mapping would be in effect. This could in theory be used with audio inputs as well (e.g. a microphone input), but unwary track selections could have more drastic consequences such as loud overload or disturbing ongoing bounce recordings etc. Let me know what you think of this idea.
Also I tried to assign a midi mapping to a track to control a parent track (with a VSTi) but that doesn’t seem to work. I have to assign the midi input mapping on the VSTi track itself: is it intended that way? I assumed that in the concept of podium also midi would behave like the audio routings >> like a tree.
It is sort of intended, but you’re right that one would expect that the MIDI input is flowing up to the VSTi track. The reason I have chosen that it must be assigned to the VSTi track, is that if you start recording the MIDI input it may result in the creation of new note or parameter sub tracks under the VSTi track. I thought it would be confusing that if the input was on a subtrack then recording could create tracks in a sibling branch of the tree.
I will consider your global parameter suggestions.
Stickies are working fine here with 0.91 on all object types. As I wrote in the release note they have been inoperational in 0.90. I need more details of how you observe this bug?
Frits
kagemusha.. When you want to change MIDI input to another track you would need to switch the mapping on the current track off and switch it on on the new track…
I had it mind that the switch would automaticly deactivate an active input on an other track …
I could implement a global input mapping mechanism. In the input panel list in the track inspector you would have an ‘Assign as global’ menu in the list popup menu. This would set a single MIDI input mapping as global indicated e.g. by a red pinhead image in the list. Whenever you select a track and this track does not have an input mapping assigned already, then the global mapping would be in effect. This could in theory be used with audio inputs as well (e.g. a microphone input), but unwary track selections could have more drastic consequences such as loud overload or disturbing ongoing bounce recordings etc. Let me know what you think of this idea.
Would be very usefull. I think a lot of people have migrated to softsynths and are using just midi keyboards/ controllers. so multiple midi channels are less important. Just one main channel (ch1) to controll the VSTis.
Yes some kind of reserved or a global mapping just to controll VSTi’s by selecting the track would be very good
It is sort of intended, but you’re right that one would expect that the MIDI input is flowing up to the VSTi track. The reason I have chosen that it must be assigned to the VSTi track, is that if you start recording the MIDI input it may result in the creation of new note or parameter sub tracks under the VSTi track. I thought it would be confusing that if the input was on a subtrack then recording could create tracks in a sibling branch of the tree.
I’m not sure if I understand it. Do you mean it gets confusing when the midi input track is part of other tracks where the real midi data is recorded?
In the context of what i mentioned above I tried it this way because it’s indeed the global behaviour of Podium, but also because I was trying to control two different tracks at the same time. By placing the midi input channel to connect both of them.
Stickies are working fine here with 0.91 on all object types. As I wrote in the release note they have been inoperational in 0.90. I need more details of how you observe this bug?
Hmm they don’t behave as before (on my system). I did some tests and I discovered that I only can attach them in the list browser and via clicking right in the project browser. I was sure that before when I highlighted an object and pressed the sticky button in the toolbar it was attached. If I press that button it only opens the one I attached to device folder.
ciao
ZynewaveI’m not sure if I understand it. Do you mean it gets confusing when the midi input track is part of other tracks where the real midi data is recorded?
Yes, I think that is what I mean 🙂
In the context of what i mentioned above I tried it this way because it’s indeed the global behaviour of Podium, but also because I was trying to control two different tracks at the same time. By placing the midi input channel to connect both of them.
So, am I assuming correct that the two track tracks you want to record with one MIDI input is the track you assigned the input to (which have no output mapping assigned) and the parent track with an output mapping? What would you expect would be the outcome of recording MIDI with this setup? Maybe you could send me the project file so I could get a clearer picture of what you want to achieve.
I was sure that before when I highlighted an object and pressed the sticky button in the toolbar it was attached. If I press that button it only opens the one I attached to device folder.
Hmm, the Properties and the Stickie note buttons at the top of the browser has always been shortcuts for the current page object, and not any selected objects inside the page object. So this new behaviour you have observed is the way I intended it to work. The stickie note bugs I recently fixed should have no effect on this.
kagemushaSo, am I assuming correct that the two track tracks you want to record with one MIDI input is the track you assigned the input to (which have no output mapping assigned) and the parent track with an output mapping? What would you expect would be the outcome of recording MIDI with this setup? Maybe you could send me the project file so I could get a clearer picture of what you want to achieve.
I wanted to control two different VSTis at the same time. I though (but it isn’t possible) that when I set one midi channel input track and sent it to two different VSTi tracks I could control them both. Like you could control different Hardware synth on one channel. But because this is not working ( the seperate midi input track to control another track) I didn’t found a way to control two VSTis at the same time.
The current system doesn’t allow it too because of the fact I can assign only one input mapping at the time (same channel)
Sorry to drag cubase into it but there, if I have two tracks with each its own VSTi, it is just possible to highligh both tracks and they will each play their VSTi output when I play the midi keyboard. So with one channel I can control different VSTis at the same time.
Is there a way to do that in Podium?
Hmm, the Properties and the Stickie note buttons at the top of the browser has always been shortcuts for the current page object, and not any selected objects inside the page object. So this new behaviour you have observed is the way I intended it to work. The stickie note bugs I recently fixed should have no effect on this.
It’s not that important but just to ease my mind to ensure myself I’m not completely a chaotic head 😕 :
So before it was not possible to attach a sticky at for example an arrangement object in the projectbrowser?
f.e.
When I highlight an object (any object) in the project browser (any page), and I press the sticky button (and write a note), should it attach to that object?
When I do it now it doesn’t, only to the device folder but not any other object. On the other hand when I do it wich right clicking “Sticky note” or Alt-N or via the list browser I can attach a sticky.
Doesn’t have the sticky button the same function?
Eli
ZynewaveA quick suggestion:
You could try creating two identical MIDI input mappings, and assign them to different synths. Don’t know if it will work as expected. I will be back in the lab tomorrow to check it out.
kagemushadoesn’t seem to work, I got an error message that the midi channel configuration of the assigned input mapping is conflicting with a mdi input on a previous track
I had duplicated a midi input device mapping for channel 1 and gave it another name.
Eli
Zynewave@kagemusha wrote:
doesn’t seem to work, I got an error message that the midi channel configuration of the assigned input mapping is conflicting with a mdi input on a previous track
Oops, that’s right. It’s only recently that I put that check in 😳
So the conclusion is that you cannot currently use one MIDI input to simultaneously control two or more synths. I will think about how it best can be done, but for the time being I need to concentrate on the few features stopping me from releasing 1.00.
ZynewaveIt’s not that important but just to ease my mind to ensure myself I’m not completely a chaotic head 😕 :
So before it was not possible to attach a sticky at for example an arrangement object in the projectbrowser?
The bug that appeared with stickie notes in 0.84 – 0.90 had to do with some broken Windows message handling. It had the effect that ANY text entered in a stickie note window was not notified to Podium.
In the browser you can attach stickie notes to any object you desire by selecting the object and using the shortcut menu or pressing Alt+N to open a stickie note for that object. Once a stickie note has been entered for an object it gets a stickie note button on the object card in the browser for easy access. The stickie note button in the top toolbar is a shortcut for the page object. So if you are on the main project page, the properties and stickie note buttons in the toolbar belongs to the project object. This is the way it has always worked, to the best of my knowledge. I had no idea it was that confusing :(. Maybe I should just remove the buttons in the toolbar to avoid any confusion?