retrospective MIDI recording

[Sevantos]

My apology -... Also Ableton manual says nothing else about capture than just recording (same like in bitwish link)..


I ve uninstalled Ableton 4 y. ago ....



Happy new y.

[backtomusic]

Saw that midi cap has come out as beta, havent tried myself though.

https://www.birdsthings.com/midi-cap

[pdxindy]

Saw that midi cap has come out as beta, havent tried myself though.

https://www.birdsthings.com/midi-cap

I haven't tried it yet... anyone?

[pizzatime]

Works great for what I need. Really simple and small interface that is nice to look at - would happily pay for it when it comes out of beta.

[carlca]

Saw that midi cap has come out as beta, havent tried myself though.

https://www.birdsthings.com/midi-cap

I haven't tried it yet... anyone?

There’s also Rewind 2.0
https://www.monkeyc.audio/

[pdxindy]

Saw that midi cap has come out as beta, havent tried myself though.

https://www.birdsthings.com/midi-cap

I haven't tried it yet... anyone?

There’s also Rewind 2.0
https://www.monkeyc.audio/

Do you use it? If so, does it work well?

[carlca]

There’s also Rewind 2.0
https://www.monkeyc.audio/

Do you use it? If so, does it work well?

Like so many of my gizmos, I haven’t really used it in anger yet, but I remember trying it out and saying “This is really cool!” to myself, before being distracted by some other shiny bauble

[takecha]

Rewind (https://monkeyc.audio/) and MIDI Cap (https://www.birdsthings.com) always preserve MIDI logs and can import it into DAW on both Windows and macOS. Even capable of audio as well. I really love these two tools. It's working fine on Bitwig as well.

However, I feel that a feature like Ableton Live's Capture MIDI that automatically detects the BPM accurately and loops instantly is the overwhelming winner when creating dance music.

[krankyone]

What I miss, and what's missing in Ableton also, is a capture that grabs host automation also. I remote control map most plugins and wish that host automation was captured. CC is nice, but not enough.

[steff2000]

I absolutly agree about what you're saying!
The problem is that there isn't a common understanding between daw and plugin manufacturer how to deal with this issue. I'm preferably using fl-studio which in contrary to bitwig is able to send the midi data (e.g. CC) directly to to the plugin and if you're using the internal midi mapping of the plugin (e.g. u-he Repro-1, arturia Modular V3) you can manipulate the parameters with incremental CCs which give you a much higher resolution and additionally you do not have issues with jumping values which is most often the case with absolute CCs.
BUT! Not all plugins do signal their parameter values to the host if they are manipulated by CCs (e.g. u-he does not, arturia does). On the other hand most daws (e.g. Bitwig, Ableton) do not have the ability to send the CCs directly to the plugin or they always record the midi CCs in context with midi notes which results in big mess if they are recording the automation data at the same time (e.g. Reaper).
My hope is that the support of midi 2.0 and the introduction of the new plugin standard CLAP will lead to better solutions concerning the recording of plugin automation data versus midi automation via CC. How ever the exact solution looks like as a user you need to have the possibility the choose which data is recorded as midi data and which data is recorded as plugin automation data. In case you you want to record plugin automation data you need to be able to record only musicaly relevant midi data as notes, pitchbend and aftertouch without any any CCs.
Also we have to be aware about the fact that the recording of plugin automation data and midi notes at the same time adds a certain complexity when it comes to editing of the recorded tracks - but fl-studio has proven that it is possible to solve this in a very usable way.

[lunardigs]

I want retrospective recording too, for audio and midi.

[sQeetz]

Saw that midi cap has come out as beta, havent tried myself though.

https://www.birdsthings.com/midi-cap

I haven't tried it yet... anyone?

Works great... Loaded into an Instrument Channel, set Monitoring to ON and let it do its thing until needed.
Saved it as my default template

Of course it would be a lot nicer if it was integrated into Bitwig itself and mappable to a shortcut, but it works... for now

[JamminFool]

fyi: Waveform has Retrospective Record for both audio and MIDI.

You can set the buffer size from 30 seconds to 10 minutes.

[pikey]

Saw that midi cap has come out as beta, havent tried myself though.

https://www.birdsthings.com/midi-cap

I haven't tried it yet... anyone?

Works great... Loaded into an Instrument Channel, set Monitoring to ON and let it do its thing until needed.
Saved it as my default template

Of course it would be a lot nicer if it was integrated into Bitwig itself and mappable to a shortcut, but it works... for now

Keyboard mappings in the mappings panel are saved with the default template, so it's quite easy to have custom shortcuts for opening the window of plugins that live in your default template like midi cap.

[sQeetz]

Keyboard mappings in the mappings panel are saved with the default template, so it's quite easy to have custom shortcuts for opening the window of plugins that live in your default template like midi cap.

Nice one!

edit: instead of using an instrument channel wasting space, I now put it in the Master track. The master can also monitor incoming MIDI and since the CLAP version passes audio through it's like it's meant to be put there