kagemusha's Forum Page

Profile  |  Topics  |  Replies  |  Favorites

Forum Replies Created

Viewing 4 posts - 61 through 64 (of 64 total)
  • in reply to: midi mappings and behaviour #3091
    kagemusha
    Participant

    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

    I had duplicated a midi input device mapping for channel 1 and gave it another name.

    Eli

    in reply to: Level gets louder and louder with muted curve #3090
    kagemusha
    Participant

    8)

    in reply to: midi mappings and behaviour #3085
    kagemusha
    Participant

    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 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

    in reply to: midi mappings and behaviour #3081
    kagemusha
    Participant

    .. 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

Viewing 4 posts - 61 through 64 (of 64 total)
© 2021 Zynewave