But managed (while trying to make it crash with multiple scenarios) to get it to crash with just the DN on plugin open in the session but all 4 units powered on and active in the OB engine panel…
the first thing the support adviced me to do is to check the midi settings. so - yes - they are aware about the midi feedback loop. but in my case changing the midi settings didnt stop the crashes.
Yeh all MIDI settings are the same across all my devices. It’s just the DN with the problem. Sometimes FL looses the ability to send MIDI data to the DN and the only thing that will get it back is a restart…the midi settings might LOOK correct but if the dev team have the code a little out, the settings won’t matter…
The reason I suspect MIDI loop is I had a uc33 MIDI controller that had a MIDI loop and FL behaved exactly the same way…crashing at start up and exit, dropping recognition of the device, pops and clicks when it was functioning…
same here finally updated the DN just to find out about this bug.
Not having more than two devices on seem to do the trick when opening Ableton … or a project for that matter.
pretty much i am in since the Beta and always worked flwalessly, it goes official release and break everything
I ll kick a ticket for sure
BTW saving all projects on the DN and recreating the links in overbridge worked quiet nicely
this issue is not DAW-related. I am using Ableton 10 + Logic Pro X, and in Logic the same freezing happens frequently. Its even worse. In logic pro x the elektron device running as OB-instance freezes completly and has to be restarted manually, whereas in Ableton “just” the audio-stream freezes/drops out.
I have a Digitakt and Overbridge kept crashing Ableton 10 & Bitwig 3.3
I tested with an empty project, no samples loaded, made 2-3 patterns, no problems so far.
Then I loaded up a saved project and the plugin crashed.
The thing is, it crashed only on certain patterns.
I figured it was ONE Sound (hand made, not a factory sound) used in that particular pattern that caused the issue.
With the AU, when switching from a “clean” pattern to a “wrong” pattern, there was blank in the audio during the transition. No crash of the AU.
Removing the bad Sound from the “wrong” pattern solved the problem too.
i get crushes with newest 2.0.44 version vst
running windows laptop with ableton , bitwig , and reaper ,
all crushing after few seconds to minutes…
and i cant find the previews version install file!!
anyone got a link? the prev was working flawless…
For me it was a “Sound” I created on the Digitakt, based on a stock sample (“BD Pearl”), with a modulation on the filter frequency, and some tweaking with the sample start / length, tune, etc …
so it seems to be related to specific object in the digitakt
sample , instrument or project … for me i try loading the same sounds into a new project and its fine no crash. so its probably some kinda bug error in the process. when it does happens i see the overbridge vst screen empty cant show the sample waveform… right before it crashes… maybe related. any way it does not happens any more and when it will happen sadly i will send the log files to the support guys.
but now im getting lots of OH losing sync! cant send out midi and OH vst at same time for more then a few minutes… well.