...assigns odd midi channel numbers when adding and deleting channels
Noticed this a while back with the drum rack - got a whole heap of other stuff I noticed too but haven't gotten around to putting the new beta through it's paces, but this one still exists as far as I can see. and I have extensive use of most functions of orion.
if you have a load of samples loaded into the channels and you choose to delete a single channel, either off the bottom or above.
when you add another sample channel it doesn't always increment the midi channel number automatically properly
Say I delete the bottom one (midi 70) then add a new one it might automatically make the new sample channel allocated to (midi 68)
if I forget that orion does this what happens is, when I put a note in on the new bottom channel, it also adds a note onto two racks above in the original (midi 68) as I have two racks with the same midi channel number (which is a behaviour to be expected)
but orion does this automatically properly when no samples are loaded/no channels have been deleted,
Wouldn't it make more sense for it to use the highest midi channel number in use and increment from there when you add a channel at any point, whether before or after deleting one.
or is this is what it is supposed to do and is a bug?
Just saying
Orion 8.02 & 8.5 public beta - drumrack automatically....Moderators: Christophe, Mark
10 posts
• Page 1 of 1
Re: Orion 8.02 & 8.5 public beta - drumrack automatically...I think you're referring to Midi Note numbers and not channels...........I'll test this right now to see if I can reproduce it here.
Re: Orion 8.02 & 8.5 public beta - drumrack automatically...Ok I see what you're saying...If I load an empty Drumrack it defaults to 6 tracks with the Midi Note numbers of 60-65 (which is kind of odd since the GM spec has these as Bongos Congos and Timbales...should probably default to notes 36-41 which are Kick and Snares etc but that's a whole different subject). Now if I add a track at the bottom it is assigned note number 66....but if I then delete the top row and add a new row at the bottom it too is assigned note 66.........so you'll have two tracks triggered by the same note number which is a good thing if you want to layer sounds but not a good thing if you don't.......... So i guess the desired behavior would be for any added tracks to automatically be assigned a note number one higher than the row above? Does that sum it up?
Re: Orion 8.02 & 8.5 public beta - drumrack automatically...sounds confusing to me
don't really bother with gm mapping or specs really, just put samples in it and go as long as they have their own channels obviously. I'd imagine it should just increment one number up from the highest number you've got already, not a clone the same number already existing to avoid any confusion Last edited by BMS on Fri Jul 08, 2011 1:05 am, edited 1 time in total.
Re: Orion 8.02 & 8.5 public beta - drumrack automatically...What sounds confusing?
Re: Orion 8.02 & 8.5 public beta - drumrack automatically...
lol I'm tired, I thought you were suggesting something different not agreeing with me, sorry
Re: Orion 8.02 & 8.5 public beta - drumrack automatically...I said the highest number, cause really someone might have things mapped all funny innit and not in order,
so doing it by the highest number would avoid if you had the last row set to say (60) and the ones above it to higher numbers or not in any order.
Re: Orion 8.02 & 8.5 public beta - drumrack automatically...Yes I guess you're right......Let the new track be assigned a number one higher than the highest number already assigned. If that's possible from a coding standpoint. I said one higher than the row above since I assume everyone would want to keep the numbers in order of the rows whether triggering from a midi keyboard or just using the range feature in the Piano Roll......don't really see the advantage of having numbers out of sequence but I'm sure someone else will...........
Re: Orion 8.02 & 8.5 public beta - drumrack automatically...
I agree with all this, you know, I don't see the advantage of what you said either, it's possible that through no *known* fault of the user that things are not in order and the behaviour would be unexpected if not done the way I mention. I'm pretty sure it's doable in code, I'm no coder although I can pick up most coding languages in a couple of goes & trial and error, what I've seen it seems to be all the same things happening just the instructions are different - seems like you could have something simple like a conditional, (gonna grossly simplify this and very tired so might muck it up) on the condition that no matter what other numbers of a range exist, if a certain max number of a range exists (midi note number 70 for instance) then that certain max number(70*) a +1 value should be stored to be used in the part of the code where the adding the next track is executed (71*), if not I'll settle for this 10 print "im a blithering idiot" 20 "goto 10 :p right I'm going to bed 2:46 am and I'm talking stuff that I haven't thought through or even understand myself! *for example
Re: Orion 8.02 & 8.5 public beta - drumrack automatically...Welcome to the forums but you've dredged up a year old thread. What image are you talking about?
10 posts
• Page 1 of 1
Who is onlineUsers browsing this forum: No registered users and 466 guests |
© 2017 Synapse Audio Software. All Rights Reserved. |