Recording Midi Data - Help Needed

Read the manual over. Tried differnt settings but still no luck.
Trying to record tracks 1-8 into a DAW.

Can confirm all channels in the DAW can recieve data on respective channels.

In midi channels track1 =1, track2 =2 etc. auto channel off.
In midi control audio cc out int+ext, audio note out int+ext.

Not sure what I am missing here?

1 Like

Audio tracks 1-8 or MIDI tracks 1-8?

I tried again today and it didn’t work…
Check out page 41 and 43 of the manual.
The midi out that gets transmitted from the audio tracks is only for trig presses and knob turning.

Page 41; Audio Note Out
" EXT will make [TRIG] key presses send out midi notes. "
and
page 43; Trig Channel
" Trig Channel sets which midi channels the audio tracks respond and send data to. … the track can at the same time when active, send out MIDI data on MIDi channel x. This occurs when the DATA ENTRY knobs are adjusted and when [TRIG] keys are pressed…"

No mention of the Audio sequencer sending out the midi patterns for each track, which is a huge bummer.

I would love it if I was wrong because this would be a nice feature to have!

Audio tracks 1-8 or MIDI tracks 1-8?[/quote]
Hi Peter. I am trying to record the midi data of the audio tracks to midi tracks in a daw. Encoder movements, mutes, sequencer data etc… This is so I can play the data back to the Octatrack from DAW (one at a time) for multitracking. Hope this makes sense.

Hi musicmagnus.
Audio note out = int+ext
Trig channels set 1-8 (corresponding to octas tracks)
This should be working?

Hi musicmagnus.
Audio note out = int+ext
Trig channels set 1-8 (corresponding to octas tracks)
This should be working?[/quote]
Don’t take my word for it, try it yourself… I was looking for confirmation too.
Audio note out is sending the notes out on the right ch. but only when you physically hit a trigger. Nothing gets sent out when the sequencer is playing a track. That seems to be what the manual is saying it should do as well.
Please try this and see if you get the same behavior though… I would love for this to be a problem with my machine only :slight_smile:

Hi Musicmagus.

Yup I tried this out before posting here. I am getting no data sending whatsoever with these settings. Knob turns, trig presses etc… nada

This is the last thing I need to sort out before I start multitracking. Really cooking my brain. If I can’t get this to work I am going to have to rethink my process and lose alot of the magic that comes with using the Octa live. :-1:

Do you need to record every note and knob setting?

Why don’t you just lay down some Program Changes so that the DAW will play the correct pattern on the OT?

So it seems my midi router was blocking info to the DAW. After plugging Octa midi out directly to the soundcards midi input the DAW was recognising tweaks.

I have discovered that the scenes do not send midi. The crossfader is not generating data and the parameters they effect do not send data (you need to physically turn the knobs for data to be generated.)

Rikrak sending prg messages to Octa is a good idea, but it means that I will still have to perform each track one at a time instead of performing all tracks in Octa at once to get each track into its’ own channel in the DAW?

Going to have to come back to making this work at a later date. Got a deadline coming up and I don’t have the time to troubleshoot this. Gotta get on with it…

Thanks for all the feedback. Will keep an eye in here in case any solutions come up.

Cheers,
AUX

1 Like

Audio tracks 1-8 or MIDI tracks 1-8?[/quote]
Hi Peter. I am trying to record the midi data of the audio tracks to midi tracks in a daw. Encoder movements, mutes, sequencer data etc… This is so I can play the data back to the Octatrack from DAW (one at a time) for multitracking. Hope this makes sense. [/quote]
OK, understood.
This is not really an intended use case for the OT. If audio tracks sequences were able to be sent out via MIDI, the OT would be billed as a 16-track MIDI sequencer, and this is definitely not the case. Its design (tracks, audio outputs, MIDI implementation, etc) indicates that it was intended to be used in spontaneous/live situations, rather than for tracking MIDI to a DAW.
If you want to workaround the OT’s design for your purpose, you could use the MIDI tracks to sequence your music, and use the established trick of routing OT MIDI Out to OT MIDI In so that the MIDI tracks sequence the audio tracks, but also using MIDI Thru to echo the MIDI data to your DAW.
You have to decide for yourself whether you want to go to all this trouble for what you want to achieve.

Audio tracks 1-8 or MIDI tracks 1-8?[/quote]
Hi Peter. I am trying to record the midi data of the audio tracks to midi tracks in a daw. Encoder movements, mutes, sequencer data etc… This is so I can play the data back to the Octatrack from DAW (one at a time) for multitracking. Hope this makes sense. [/quote]
OK, understood.
This is not really an intended use case for the OT. If audio tracks sequences were able to be sent out via MIDI, the OT would be billed as a 16-track MIDI sequencer, and this is definitely not the case. Its design (tracks, audio outputs, MIDI implementation, etc) indicates that it was intended to be used in spontaneous/live situations, rather than for tracking MIDI to a DAW.
If you want to workaround the OT’s design for your purpose, you could use the MIDI tracks to sequence your music, and use the established trick of routing OT MIDI Out to OT MIDI In so that the MIDI tracks sequence the audio tracks, but also using MIDI Thru to echo the MIDI data to your DAW.
You have to decide for yourself whether you want to go to all this trouble for what you want to achieve.[/quote]
Nice, Thanks for the tip!

1 Like

@Peterhanes, I think you might be misunderstanding what Aux is getting at here. Essentially, you can record all of your realtime performance data as “automation” into a DAW, and then play it back to the OT. This would allow fine tuning of realtime performance data or playback and recording of the individual tracks performances,

@Aux, my crossfader sends and receives MIDI CC #48 just fine so maybe a setting for you somewhere? Also, scene selection is MIDI selectable so playback of scene automation ought work fine. Some programs such as Ableton Live will not record Program Change messages tho, so some workaround is needed.

…i really see your point…capturing the realtime action mess up in single tracks is, indeed essential…

but that’s not where it’s at, i’m afraid…i hardly doubt, even if ot would be capable of sending a complete midi message sheet for ALL interaction it does internally (which is not the case), you would ever really get back what you played in first place, once the ot is running slave mode doin all that again on midi remote…

so i figured out for myself by now, i can work it out in two takes, by spliiting up in pre stems…

if you wanna get on with your music and final mixes, stop all that troubleshooting and try to split in a rhytm group only take…kik A, snare/clap B bass C hh/perc D

and one take with all the rest spliited they way you need it ftom track to track…fix the big breaks where it really all has to interact with each other in simple pre arrangements in the ot and let that run twice…the second along with monitoring the first… mute groups as needed…

little workaround but also helps a lot to become really sure with the final arrangement…
what about stereo?..forget about stereo…a mono signal is esier to be placed in panorama and if it get’s some stereo make up in the final mix, is way better to handle anyway…

or take the easy road, if you’re comfortable with your monitoring situation, and just twke separated kik and snare and the bass separated A/B and all the rest at once…

dubble bubble…again…

[quote=“” NRain""]
@Peterhanes, I think you might be misunderstanding what Aux is getting at here. Essentially, you can record all of your realtime performance data as “automation” into a DAW, and then play it back to the OT. This would allow fine tuning of realtime performance data or playback and recording of the individual tracks performances,

…
[/quote]

Maybe I misunderstood. I believed that Aux was trying to record MIDI data corresponding to the patterns on the audio tracks into a DAW, which is obviously not going to work simply. Hence my suggestion to use the MIDI tracks for the sequencing as a workaround.
If Aux is trying to record only CC data from knob turns into the DAW, then that should work providing that no MIDI tracks are active on the same channels as the audio tracks for which the tweaks are to be recorded. But it still seems like a convoluted approach, especially if there is any pattern switching during the performance.
[By the way, your old MD is still going strong, and says “hi”.]

Audio tracks 1-8 or MIDI tracks 1-8?[/quote]
Hi Peter. I am trying to record the midi data of the audio tracks to midi tracks in a daw. Encoder movements, mutes, sequencer data etc… This is so I can play the data back to the Octatrack from DAW (one at a time) for multitracking. Hope this makes sense. [/quote]
OK, understood.
This is not really an intended use case for the OT. If audio tracks sequences were able to be sent out via MIDI, the OT would be billed as a 16-track MIDI sequencer, and this is definitely not the case. Its design (tracks, audio outputs, MIDI implementation, etc) indicates that it was intended to be used in spontaneous/live situations, rather than for tracking MIDI to a DAW.
If you want to workaround the OT’s design for your purpose, you could use the MIDI tracks to sequence your music, and use the established trick of routing OT MIDI Out to OT MIDI In so that the MIDI tracks sequence the audio tracks, but also using MIDI Thru to echo the MIDI data to your DAW.
You have to decide for yourself whether you want to go to all this trouble for what you want to achieve.[/quote]
Thanks Peter.
Wasn’t aware of this method, will give it a try when I get some spare time.
I think it will definitely be worth it if it works! What you can do with Octa live is incredible. Being able to record this and edit multitrack = best of both worlds (to me anyways)

1 Like

Hey Reeloy.
This is essentially what I decided on in the end. (if the midi aspect is too involved)
Don’t have to worry about the drums as they are all going out A-F on MD. Just trying to get the best workflow/track separation balance I guess.