Damn I thought I was a blackbelt user.
Perhaps Iāve missed something in your lengthy and detailed post⦠but could plays free tracks not be exploited here? Iām using them quite a bit to trigger recordings with trigs 1-8 before playing back with trigs 9-15 (16 for master in my case)
Thanks for your reply, Tomes.
If I am understanding correctly, youāre recommending getting ādirect-touch recordā functionality on some track X by panel-UI and/or by Remote MIDI (on one channel) by using the that Tracks RECorder Trigs, dedicating Track N to trigger recording into Track N machine.
Iāve done this before (years ago), and it was a step in the work-flow Iāve been pursuing.
If I remember this setup correctly:
- set Track X to āPlays freeā so it is (re)started) by the Track Trigger (buttons 1-8).
- set a REC trig on (first step) of Track X
- if you want momentary/gated recording, set Track X SequencePlay to āholdā AND set Track X RecordMode to Hold
- if you want to catch specific lengths, set Track N Sequence Play to Once, and set Track Xās RecordLength to desired LENGTHin steps.
Yes, this works, for N multiple tracks even, butā¦
- you waste that Trackās Xās sequencer on firing the RECorder Trig,
- you cannot replay that RAM slotās sound with Track X sequencer to afford rhythmic Trigs, Locks, unqiue TrackLength, conditionality, etc.
- youād have to use a different Track Y pointed to Track Xās RAM buffer, ā¦where youāre kinda stuck with
ā¦so this work-around rapidly takes the āTracksā out of OctaTrack,, and unless you want to only play the OT by hand, and sets your sequencing back to the workflow/limits of the MachineDrum using RAM machines, where youād have to pairs of REC and PLAY tracks for the few (four) RAM machines.
My work-around gets OctaTrack to have ALL EIGHT tracks haveā¦
- direct-remote control of (re)RECording audio into each Trackās RAM
- direct-remote control of live PLAY of each RAM sound
- sequencing each RAM sound
ā¦all in itās own track, with 1-to-1 logic navigating/muting/etc of tracks, with the Trigs/Locks/ClockDivision of the OTās design intact.
This my current application setup makes the OT something really special (to me) where I can fully decouple the (pre)programmed rhythms/melodies from the āsoundsā, which can be performative (re)sampled live.
If people need to see/hear it to understand it beyond this, I can try to make a video-demo if it would help muster understanding and interest.
Unfortunately, since the MIDI Message for AutoRec is a MIDI Track-Channels message (like the other Note messages for PickUp-s and all the CCs for Volume/Pan/Pitch/etc), and not allocated for all 8 tracks on the AutoChannel (which contains 8 Mutes and SeqPlays), my current approach has to eat up one MIDI channel for each ādirect-recā track I want on the OT.
Eating up 7 or 8 MIDI channels just for OT-input control really crowds the MIDI Standard of 16, when it comes to wanting the OT to play well with (or even sequence output to) other (multi-timbral, mutli-channel) MIDI gear.
It would be for a next/future OT FirmWare to simple-trivial fix to add 8 Notes of AutoRec messages on the Auto channel, and it would really sharpen the OT to do everytong on the one Auto MIDI channel.
This is doable with a midi processor, while waiting an hypothetical update.
Or a Launchpad Pro ?
Hey Sezare,
I have set up and used my above LaunchPad control map show in my above post on all 3 types of Mk3 LaunchPads (the Pro, the X, and the Mini)⦠they all the the same basic MIDI vocabulary: Notes, ControlChanges, and ProgramChanges.
At present, all my MIDI gear is networked through an iConnectivity MioXL (8 ins, 12 outs), where each the ports patch to/from each OTHER port, so all I can just keep things simple with assigning MIDI channels, and limit myself to ONE clock Master (the OT).
This works well with a modest half-dozen bits of kit (Elektron Rytm, korg Radias, some MIDI vocal effects, and a Circuit), that might use up one or more MIDI channels each.
Hence, my ache of having the OT eat up more than one Auto Channel just to combine āRAMplingā with Sequencing.
Setting up the iConnectivity to do Channel ReMapping specifically on the DIN port to the OT would not solve this problem, just move it to other ChannelS.
I have thought (many times) about buying/building some prosthetic MIDI processor to stick in between the DIN Out to the OT and the DIN Input to to the OT that could listen for specific Notes on the OTās Auto channel and remap them to the MIDI channel of the N OT-Tracks I want to use.
Iāve done it in software (purrData if I recall), but have yet to find or buy a hardware/DAWless solution.
Feels like Iād be giving my OT a CPAP.
Thatās what I did for recordings from a midi foot controller.
This way I can use RECORDERS/FLEX recording with undefined quantized length (QREC=16) and direct playback when I stop.
I used EVENT PROCESSOR PLUS.
The Midihub could do this, I believe.
Which Make/Model are you talking of specificaly,
the Bomeās āBomeBoxā ?
The Blokas Midihub, highly recommended.
Ooohh.
I was not aware MidiSolutions had made such a programmabel box.
ā¦and powered by in-line phantom MIDI.
This might just be the next good-enough thing to get me closer to using the OT the way Iāve been seeking.
Since Iām only looking to reMap 8 or so Notes, I could get away with the cheaper Non-PLUS version
Cheers Sezare56 !
Iād still recommend the Blokas Midihub instead, many more features than the Event Processor and still cheaper.
Thanks to all who have given a refreshed suggestion on a prosthetic MIDI Event Processorā¦
I realized some Event Processing / Re Mapping was available in my CME H4MIDI ( USB hub w pain DIN In/Out), and was able to set up a work-around for for track REC and MUTE buttons (usually requiring their own MIDI Channel) to all cram onto one MIDI Channel. So far it worksā¦
Iāll try to follow-up with finer reflection on the gains of opening up more MIDI Channels of MIDI Traffic for the OT to send and/or ignore, and discrete audio for the OTās effects/sampling/looping/etcā¦
Thanks AGAIN !
MultiMap please.
And Step Record mode.