I could really use some help regarding OB and Syntakt.
I submitted a ticket but y’all, I just spent a year in medical bullshit world, finally in a place of making music and this thing that has worked for almost 2 years, is shitting out on me.
I updated OB… Syntakt… updatedy Digitakt 1 even though it’s not going into OB…
I uninstalled OB… reinstalled… tried different USB ports… I deleted things in the registry as suggested by knowledge base.
so - the problem:
SYNTAKT is sending data out via the channels, but nothing is coming through the regular channels. before, I was playing just find. it happened mid session - suddenly, nothing was coming through. I gave up for the evening, tried again next day
it was working! then about 20 mins later, only the Midi channels were sending data
but this whole time, until suddenly, SYNTAKT was going through OB and showing in OB.
now, it will not show in OB… unless I turn off OB mode inside SYNTAKT. then it says “uh oh look, a Syntakt and it isn’t in OB mode! better put it on OB mode!”
so I humor it, turn OB mode back on, and it vanishes from OB Engine again. this whole time, on or off, it will not show up in the OB VST ( that is standalone, or in Live)
please, help
edit: oh, and OB immediately recognizes and accepts the Digitakt I no problem. I believe I either have a) some sort of midi hell issue or b) something is actually messed up on my Syntakt
Hi, welcome to the forum, sounds like a real bad time! Must be frustrating for you. I really have no idea what’s going on with your device, there doesn’t sound like there’s anything that should be wrong from your account of it but it’s hard to tell which details are missing, however I’m certainly getting the impression that there is a device detection issue when in OB mode which was unresolved by firmware updates or software reinstall.
That’s great, this is exactly what you should do in this event. Make sure you mention to them the model of computer and the operating system or you’ll waste an email back and forth waiting to mutually confirm this information.
I would have no idea where to begin troubleshooting your PC or Mac or OB if I didn’t have some idea of what kind of system you’re trying to get it working with.
The first thing I would do is the simple stuff like turn off your device and turn it back on again.
Turn off your computer and turn it back on again.
Unplug the USB from the computer, switch out of overbridge mode and then back into overbridge mode and reconnect it to the computer and check for results.
Try a different USB cable.
Turn off overbridge mode so it’s instead set to usb midi / audio and then try and set your device as an audio interface in live and see if that works.
See if it’s detected by the transfer software when in overbridge mode or only when in usb midi / audio mode.
Maybe even try and sysex the firmware update to the syntakt instead of updating via USB.
But since all of that is unlikely to help, I’d probably recommend patience and wait for that support ticket to go through and hopefully the people getting paid to resolve your issue will be able to resolve it.
Maybe someone else has something to add to this but if it happens to be a Mac computer, I would advise some extra additional patience and clear communication with support about your OB issues otherwise you might be working on this for a while.
They always usually most of the time as far as I’m aware get the problems resolved though, mostly, almost without fail 60% of the time every time.
Hope it works out for you though so you can get back to working on music on your device which can make music without a computer if you are really hard up to work on some. I don’t use a computer hardly at all and definitely still enjoying my elektron devices so there’s hope for us yet!
At any rate, I’m positive they’ll get you sorted and in the meantime if you want to complain about other non-synth related things or get gassed up on new overpriced products from a variety of bloodthirsty manufacturers check out the rest of the elektronauts forum as it has just reached a proper vintage and we’re about to uncork the sucker and see how it turned out!
Cheers
Also, it’s clear that your Digitakt 1 is working properly, and doesn’t have any conflicts in situ, however I would say first off that your syntakt is unlikely to have an internal issue and you can confirm that by going into test mode (device powered off, hold down func and then turn it on, when the menu comes up run the error test and see if it detects any errors) but I think that the conflict in either software or firmware or configuration can exist entirely separate of whether or not the digitakt works in this same configuration, so it’s a positive thing that those are connecting but I don’t think it’s going to be reflective of the issue with syntakt specifically.
Does show that some software and hardware work in the present configuration though, so we know something at least.
Thanks for your reply!! I’m on Windows, in Ableton Live but the issue is also in OB Standalone.
So, as part of my troubleshooting, I already did everything leading up to this coming quoted question prior to posting. I did try your “unplug>switch OB setting off> switch back on> plug back in” and unfortunately no dice.
It is detected by Transfer… but not in OB Control Panel or Engine.
This was the detail I’d included in my OP, this is the part that confuses me the most - Why it see’s the device in USB MIDI mode, and recognizes it isn’t in OB mode any longer, but when I turn OB mode back on, it can’t see it… !!
I suppose I just have to wait to hear from Elektron Thanks again!
Well I do see the situation frequently where there’s a problem with overbridge connectivity and still not impacted for use with the basic configuration as an audio device and I assume this has something to do with plug and play drivers vs device and software specific drivers. That makes me think they’re separate types of issue.
Elektron devices which can use overbridge and also act as a standalone interface are class compliant so they can talk to the computer in a more general mode which doesn’t require specific drivers and overbridge definitely requires specific compatibility so I can only guess that’s part of the reason that I say specifically that there’s a device detection issue when in OB mode because that’s likely going to be key in that it’s only in OB mode.
At this point if none of the basic stuff helped and you already went so far as to clean the registries, then I’m suspicious that you’ll need one of their tech support to guide you through some question and answer which might yield some positive results. It’s probably a matter of familiarity with specific symptoms or the way it’s behaving.
For my knowledge, you’ve done everything correctly so far and I honestly don’t see what you did to cause this so it may have nothing to do with you at all, however if anything else changed, or you did any of the updates prior to the problem popping up, I would say look at whatever that was as a specific potential cause of the conflict and work backwards from there.
Anyways from my experience what you’re seeing is normal in the regard of detected in normal midi mode but not in OB mode when people are having this sort of issue and would probably be a much bigger problem if it’s not detected at all so I think that’s a positive at least!
Oh, and also make sure to let them know which specific version of the Windows operating system that you’re running as that will also be relevant!
Thanks again!