Build 42

alexs1

jeff Reverse is a big one, but it's slightly complicated.

With MIDI, there seems to be a twofold path: 1) Reverse=playing back the sequence of Notes/CCs in reverse order and/or 2) putting the actual audio tail of each note in Reverse. I'm guessing that it's probably much easier to implement the former?

jeff Pitch functions are a whole lot easier with MIDI so I could add those.

That would be solid!

jeff

alexs1 "With MIDI, there seems to be a twofold path: 1) Reverse=playing back the sequence of Notes/CCs in reverse order and/or 2) putting the actual audio tail of each note in Reverse. I'm guessing that it's probably much easier to implement the former?"

Reverse would be playing back the sequences of events in reverse order. The trick is that notes have an On and an Off, so the meaning of those needs to be swapped. It's actually a little more complicated for me because I don't store NoteOff, I store NoteOn and a Duration which makes a number of things easier for layering and editing. But it makes reverse harder.

For the audio tail, AFAIK, there is no way to ask a synth "this is a NoteOn but start your envelope at the end rather than the beginning" so it won't sound like true reverse, notes will attack and decay like they normally would just played in the reverse order.

This was touched on in the Bounce thread, but a hybrid solution is possible, the sequence is MIDI, but at the same time it is capturing the audio produced by the synth so that when you reverse, it is a true waveform reversal. You would lose the MIDI-ness of that though, you could no longer time stretch, transpose, or changes patches once it was captured as audio.

alexs1

jeff I'm seeing MIDI tracks becoming the TSM, and then audio tracks syncing with it, but I recorded them one after the other.
Are you syncing the recording of both a MIDI and audio track at the same time?

Found the problem. The Track Master Sync parameter for my MIDI tracks was set to "Never" by default. Changed it to "Accept" and now they're working as expected.

jeff I am seeing some strange behavior using Focus Lock on two tracks, one audio and one MIDI. The Record starts at the
same time, but the second Record only ends the MIDI track and the audio track keeps going.

I may try something like this in the future. In this case, would setting MIDI Tracks to "Preferred" instead of "Accepted" change the priority for simultaneous recording using FocusLock?

alexs1

jeff Reverse would be playing back the sequences of events in reverse order.

That sounds right.

jeff at the same time it is capturing the audio produced by the synth so that when you reverse, it is a true waveform reversal.

This is the workaround I'm currently using. Not to dig another rabbit hole, but maybe there could be a dedicated function to do this (Audio-bounce reversal on MIDI tracks).

jeff

alexs1 Yeah, it's an interesting concept. You start by recording and playing a MIDI track as usual. Then ask for some kind of Capture Mode where as the MIDI track plays it is also effectively recording what is coming in on one of the ports, then keeping those together. It's either two tracks that know about each other and are synced in some way, or it's a new kind of hybrid track that has both MIDI and audio in it, or once you do this, it ceases to be a MIDI track and becomes an audio track, and you use it normally.

It's very similar to Bounce, where you enter a recording state that can't be interrupted, then when you're done, you have the bounce track going and the source tracks as independent things, but now related in some way such that the bounce track is kept muted until the MIDI track goes into reverse, then the MIDI track is muted and the bound track unmuted in reverse. The problem is that this audio capture isn't going to respond to further change you make to the MIDI track without recapturing it, unless you're in a kind of perpetual recording state for the capture track. It would end up being a lot like using Focus Lock or Track Groups and just having two tracks responding to the same functions with one dealing with MIDI and the other dealing with audio.

alexs1

jeff Ah, the "transfer flags", I had forgotten about those.

Is there a way to set one of these for Mute? If not, would you be able to add a Mute Transfer option in the next build?

edit: nvm, just found the Mute Cancel parameter and set to "Trigger."

jeff

alexs1 Forgot about that one too. "Trigger" is a bad name, goes back to when restarting a loop was called Retrigger. But it conflicts with the use of trigger as the thing that causes a binding action. It should be Switch. But since Mute is also a minor mode it makes more sense for that to be a transfer option.

« Previous Page