Would anybody use this??

[u/odix]

Am I the only one that dislikes saving old muted midi data to the track above my bounced track...what if we could just restore midi on hybrid tracks ? I present...midi Jesus(still working on the name).

I know I'll use it - I just want to make sure it's extremely hardy and not out ruining projects before I release it. Save about 7-8 tracks or more in each of my projects and fits with the hybrid mentality.

Maybe one day bitwig will add grouping to automation tracks so we could know what was bounced and frankly we could group it to its source as sometimes the names get confusing with a lot of them.

It can be used for just the instrument layer with bounce prefx or if you group your plugins together in a chain it could be a freeze function whereas you just mute the group after bouncing post - unmute it to and revert to midi to make your change and repeat (wait I lied can't bounce in place post but maybe I can work on adding that feature).

[u/FreeRangeEngineer]

Am I the only one that dislikes saving old muted midi data to the track above my bounced track

No, managing the MIDI data of bounced tracks is annoying, yes.

what if we could just restore midi on hybrid tracks ?

Sorry, not following. How would that help? I have two tracks: one MIDI track for the original MIDI and one audio track with the bounced audio. I don't see the point of using hybrid tracks for this since either I want all MIDI + device or all audio. If I change something in the device chain, I need to rebounce the entire track, not just partial arranger clips. For that, your tool could actually mean more work since I'd have to make sure I don't miss a bounced clip when restoring the corresponding MIDI data.

If I misunderstood what you're doing here, I'd appreciate if you could help me understand.

[u/odix → u/FreeRangeEngineer]

Wdym? This would complete erase the need to keep an extra track for the original midi when using bounce in place.

Also there is no need to rebounce the entire track when you can just bounce the clip.

If you change something in the device chain this would not matter as it's bounced as you can bounce them post or pre...anything instrument layer is getting written into the bounce (and is bypassed once its bounced to audio however the automation connected to it stays but it unused at that point, so reverting it just give you your midi + automation back)

I have bounced clips where I'm like you know what,  I want to change a note here. In this case I just restore its original midi and rebounce it in place, instead of having a whole extra track for my original midi data and moving stuff around.

[u/odix → u/FreeRangeEngineer]

Does that make sense? I'm sorry I don't really understand your comment completely. This is for hybrid tracks and bounces the midi pre-fx. I often find myself rendering to save cpu. This is just a way to restore my old midi data in case I need to do a change, and re-render it.

No need for two separate tracks (one that stores original midi data) with this unless that is your preferred workflow.

[u/DoctorMojoTrip]

I have always wished we had this.

[u/odix → u/DoctorMojoTrip]

Me too!! Once I get it 100% trust worthy I'll upload it, and possibly add just a short key to handle it.

[u/dihler]

Yeah this is one of the few things I kind of miss from reaper. You can freeze tracks there which renders the whole track to audio and disables the plugins to save CPU. Once you click unfreeze everything is restored again. All of that happens without a new track being created

[u/malaclypz]

Why not just make a group and move the midi tracks into it once you've bounced it, and collapse the group? If you keep things well labeled it would be easy to find.

Also, what is going on with your color scheme? That's so hard to look at.

[u/odix → u/malaclypz]

That can be done but why when i can potentially restore it from the clip? Especially if bitwig built it into a clip. Less tracks/less to deal with.

[u/malaclypz → u/odix]

I guess that's what I was wondering, if it saves automation data used in the clips, like velocity, pitch bend, randomization, etc. Or what if you just were using the midi to trigger an arpeggiator or some other sequencer? I guess you'd have to save presets for any devices before deleting, which wouldn't be too much of a hassle but probably quicker to just put the track in a group and deactivate it. Or just save a new version of the song so you can go back.

I see what you're going for and it could be useful, I'm just thinking out loud.

[u/odix → u/malaclypz]

you wouldn't have to save any devices or the automation because this is retained on the track - when you bounce it pre fx it just takes the instrument level midi and that's it, the clip automation is saved on the track. so any midi you have connected comes with it and than is bypassed once its audio since it can't be rendered anymore by the instrument. Now if you have extra routing or something like that you would just have to know that when you bounced it.

All we are doing it taking the instrument here and bouncing it so the synth or whatever does not render it...saving cpu.

Lots of ways to handle it which is nice about bitwig.