Thanks, I cleaned up some unused MIDI devices (Mac). But still the same behaviour.
Immedialety after firing a pgm change it sends another to pgm 1 - when using overbridge.
A working work-around is phealams hint with using a midi cable though. I put on from digitakt to my audio interface and set the digitakt to send midi out only. Thank you for this!
Hi!.. I have the update 1.10 on my Digitakt and i’ve install the Overbridge 2.0.11.2, but it says that the ‘‘Firmware’’ of the Digitakt is not compatible… I don’t see another update version… Somebody can help!??.. Thanks!!
Thanks Peter!.. I’m trying but there’s another issue… not able to tranfert the Os update… the ‘‘Elektron Transfer’’ don’t recognise the Digitakt (no divices connected)… it already happened , and just restarting my computer worked… but not this time!
Make sure that you match ob and fl to 48kHz and also match the buffer in ob to fl…mine are 512…if its to short you will gett pops and crackles…i have DT and ARmkii streaming 16 mono channel and 8 stereo no problem. But when set to 44.1 and a shorter buffer i had pops and crakles. Also make sure you are on the most recent version of FL20…
I’m having an issue with Ableton (10.1 beta) + OB + Analog Heat Mk II. The problem is that animations on the AH Drive parameter - critical for a track I’m working on - are only applied & can only be heard when I press ‘play’ in Ableton and listen to the arrangement. Animations are unfortunately missing from the rendered track, and also missing if I create a new audio track and try resampling from all active tracks.
Freezing / flattening does not help: animations are missing from the track when it’s frozen / flattened.
Has anyone encountered this - ie, animations for AH work fine when composing, but are completely absent when rendering the audio for upload or resampling?
Are you rendering in realtime? Heat is an analog device and can only process signals in realtime as you play audio though it, it’s not a vst that can just run code faster, it’s analog circuitry…
That was the problem, thanks. I did understand AH was analog, or partially so but hadn’t realized I’d need to change my workflow for MIDI tracks that use the Heat VST. One solution is to record a new audio track, using the post-FX output of the track I care about - with the animations on the Drive parameter. That works fine, whereas the non-realtime freezing / flattening, or non-realtime audio export, do not - for the reason you point out.
Anyone seeing that there is no signal if the Analog Heat plugin is placed last in chain? But placing it 1st generates the audio signal through Analog Heat?