|
Post by david on May 30, 2018 3:10:31 GMT
i recorded a drumtrack for a song I’m working on by playing the drum parts on a Roland VDrums kit and recording the MIDI Out (while I was playing) to Auria Pro (an iOS DAW) on my iPad Pro.
Okay, so now all the drum hits for a 4 1/2 minute song are on one MIDI track, and I want to separate the hits already recorded for each drum surface to its own separate MIDI track (for editing and mixing purposes).
So, the recorded kick drum hits on my current one track would go to a new separate kick drum-only MIDI track, the recorded snare hits on the already recorded track would go to a new separate snare-only MIDI track, hi hats to a hi hats-only midi track and so on, for something like 10 different tracks or so once everything is separated (I could survive with somewhat fewer by say, grouping the toms together in one ‘toms-only’ midi track).
I used to do this in Cubebase on my desktop, but now I’m trying to go iOS-only and I don’t see how to do this right there in Auria Pro.
My questions: Could MidiFire help me do what I want (see above) with an already recorded track? I have Audiobus 2 that I could use to route the signal from Auria Pro through another app (such as MidiFire) and then record back to Auria Pro.
if MidiFire can’t help me do this with an already recorded track, could it enable me to record a new drum part using my vdrums and seperating the seperate pads of the drum kit to different midi tracks in real time as I record my playing on Auria Pro (i.e., record 10 or so MIDI tracks simultaneously [one track for each drum pad in the vDrums kit] as I play)?
|
|
nic
Soapbox Supremo
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on May 30, 2018 8:01:45 GMT
Hi david , Assuming Auria will record simultaneous MIDI tracks from virtual MIDI ports, then it should be possible but it might take a couple of passes to split/re-record depending upon how many unique notes make up the drum track. Bear in mind that I have not used Auria, but I figure it should be able to handle what we ask. Here's how you would do it (this same technique would work for live drums too, as long as there are not more than 9 unique notes) 1. In MidiFire, use the 'Setup' panel and set the number of virtual ports to 8. 2. Drop the 8 MidiFire output ports and Auria's own destination port onto the canvas. 3. Drop the first 'MidiFire' input port onto the canvas. We will receive the events on this port. 4. Drop 9 Stream Byters onto the canvas - we will use these to filter our note events. 5. Connect them up as follows: MidiFire -> Stream Byter 1 -> MidiFire +> Stream Byter 2 -> MidiFire 1 ... +> Stream Byter 9 -> Auria6. Now we have the Midifire input feeding 9 Stream Byters, each feeding to a separate virtual MIDI port 7. Use this table to lookup the note number of each of the drum notes you need to split over. 8. In each Stream Byter you need two rules to filter things so just the desired note goes through. If I wanted to filter Bass Drum (C1 = hex note number 24 in table) then enter these two rules and (important!) press the 'Install Rules' button: NX 24 = XX +C XX +BRepeat this step for each of the unique notes on the other 8 Stream Byters, replacing the '24' with the relevant hex note number from the table. We now should have the individual notes being split over the 9 virtual MIDI ports. Going back to Auria, send the original MIDI track to the 'MidiFire' and add 9 new armed MIDI tracks each receiving events from MidiFire to MidiFire 7 and Auria's own virtual. Play/record track from beginning and you should have 9 new tracks each with just the separate note. There might be some latency in this (probably not much over virtual MIDI), so you could of course quantise the new tracks to line everything up. Finally, you could of course split differently and have all tom notes going to the one track for example. Regards, Nic.
|
|
|
Post by david on May 30, 2018 8:51:55 GMT
Thanks for the detailed reply, Nic.
I’m no midi expert, so that leaves me with a bit to chew on.
Meanwhile, looking at my recorded midi drum track, it seems that there are 15 different notes involved (Roland has extra triggers for things like, besides a crash, a seperate trigger for the edge of the same crash) and generates corresponding extra MIDI data that I’m gonna have to figure out what to do with). However, some of these notes could be naturally grouped together, such as snare and snare rim, etc., so I should be able to get down to 9 and still be happy, I’m thinking.
Okay, so to reduce track count, if I were to, for example, group the toms together onto one track, say, a high tom (note: D2), a low-mid tom (note: B1) and a low floor tom (note: F1), and considering that your MIDI Note to Hex Table maps D2 to 32, B1 to 2F and F1 to 29, would I write my two rules as:
NX 32, 2F, 29 = XX +C XX +B
?
|
|
nic
Soapbox Supremo
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on May 30, 2018 8:57:22 GMT
Hi david , Pretty close. Rules need to be on separate lines: NX 32 = XX +C NX 2F = XX +C NX 29 = XX +C XX = XX +BIf the notes are contiguous, you can also specify a range; for example the two GM kick notes 35 and 36 (hex 23 and 24) can be done in one rule using a range: NX 23-24 = XX +C XX = XX +BSadly, toms in GM are not a contiguous range so you have to list those separately. Regards, Nic.
|
|
|
Post by david on May 30, 2018 9:17:06 GMT
Here's how you would do it (this same technique would work for live drums too, as long as there are not more than 9 unique notes)... Okay, so by "it might take a couple of passes...", I think you mean that I could first split my recorded track into 2 midi tracks (each with half of the original notes). And then each of the two resulting midi tracks could then be split into 8 further seperate tracks for a total of 16 tracks. For example. I could do a play/record run with one of the halves of the original MIDI track (into 8 new tracks), and then do a seperate play/record run with the other half of the original track for a second group of 8 tracks However, for playing/recording a new track live, I’d be limited to a maximum of 9 seperate resulting MIDI tracks. Do I have that right?
|
|
|
Post by david on May 30, 2018 9:19:49 GMT
"Pretty close. Rules need to be on separate lines:.." Okay, great info, thanks
|
|
nic
Soapbox Supremo
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on May 30, 2018 9:26:49 GMT
Hi david , Yeah, that's what I meant by multiple passes - you'd be able to split into max 9 tracks each pass, so if you had 15 notes, it would take two passes; one to split 9 notes and another to split the remaining 6. Yes, with live playing you'd be restricted to 9 tracks. I might increase the max. virtual ports to 16 or 32 in a future release of MidiFire but that doesn't help you right now. Regards, Nic.
|
|
|
Post by david on May 30, 2018 9:44:59 GMT
Hi david , "I might increase the max. virtual ports to 16 or 32 in a future release of MidiFire..." Regards, Nic. Sounds like that would at least be good for electronic drummers. The other issue is that the hi hat works with CC messages (at least for Roland — as I understand it, different manufactures use different implementations to deal with hi hats info), but I don’t even know enough to say anything further about that. Welp, that’s all for now. Regards, - david
|
|
nic
Soapbox Supremo
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on May 30, 2018 9:53:32 GMT
To filter in just a specific CC message would be similar:
BX 07 = XX +C XX = XX +B
Where 07 is the CC number in hex.
Regards, Nic.
|
|
|
Post by david2 on Jun 14, 2018 4:13:01 GMT
Hi, Nic.
It took me a while, but I went and got the MidiFire app.
You say there can be 9 tracks, and there are 8 MidiFire Outs. Each Out has a Stream Byter before it, filtering a note(s) from the original Auria midi track to be output back to Auria for its own track.
In your instructions above, you said to put 9 Stream Byters on the canvas. Why 9 when there are only 8 Outs to be filtered into Auria?
Won’t any remaining MIDI notes from the original track that weren’t filtered into an Out be left to pass through as a "Misc." group that doesn’t need a Stream Byter to filter anything out?
Meanwhile, just to make sure I’m doing this right, theMidiFire Input port should be hooked up to the 8 Outs in parallel, right? (I.e., not in series, not all in one line)?
|
|
|
Post by david2 on Jun 14, 2018 4:23:53 GMT
This is where I’m at:
I don’t see how to hook up the Outs to the Auria Pro In on the lower right (nor do I see what to do with the extra Stream Byter). Any help would be appreciated!
|
|
|
Post by david2 on Jun 14, 2018 4:26:56 GMT
This is where I’m at: I don’t see how to hook up the Outs to the Auria Pro In on the lower right (nor do I see what to do with the extra Stream Byter). Any help would be appreciated! Crap; can’t insert a picture...
|
|
nic
Soapbox Supremo
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on Jun 14, 2018 5:52:58 GMT
Hi david , The 9th virtual port is Auria's own port, which I believe it advertises. You should be able to (in theory) use this the same way in MidiFire (just drop onto canvas). In Auria Pro (which I am not familiar with) I would imagine that for each armed track you can select which MIDI port to use as the source for the track events. You would select MidiFire to MidiFire 7 on the first 8 tracks and Auria's own virtual port on the 9th track. If you need to show pictures, feel free to email them to me. Regards, Nic.
|
|
|
Post by david2 on Jun 16, 2018 14:38:42 GMT
To filter in just a specific CC message would be similar: BX 07 = XX +C XX = XX +BWhere 07 is the CC number in hex. Regards, Nic. Roland uses CC for hi hat position. All I found on that is, "Roland outputs the hi-hat pedal on CC4". What would that be in hex?
|
|
|
Post by david2 on Jun 16, 2018 14:40:48 GMT
Meanwhile, I’ve mapped all the pads and I’ll post that for everyone else after I’ve got it tested and MidiBridge filtering as planned...
|
|