I upgraded my Macbook to the new Ventura OS and now when I plug in my USB’s to export my tracks from Engine DJ I get the message USB is incompatible with Engine OS devices even though the format is correct and the mac can see the USB, any ideas?
There’s been an official post and social media posts asking Mac users not to upgrade to Apple/Ace Ventura … yet.
Thanks for the reply Pasha, unfortunately I didn’t see the bulletin before I upgraded my Macbook. Hopefully you guys come up with a solution shortly. Many thanks
I updated to the new version and realized the error happened here. I just ignored the message. Everything worked well even with the message. Add new tracks and so on…
I have the same problem, also with my SSD’s, but I could update my library OK but was unable to transfer to USB / SD using Sync manager. Hope there comes a fix soon.
The ‘fix’ is, dont update your OS when the software that runs on it isnt supported.
Wise words STU
On a more serious note, happy to offer some tips if anyone wants to backwards install their OS, I’ve done it before and also rebuilt my macs about 3/4 times so can help people out with where to look for info and steps to take to protect data etc.
Hi STU, I have looked at a backwards install but looks a bit complicated for me. I’ll wait a little while to see if the Engine DJ tech come up with a software update, hopefully it wont be too long as its going to be a hindrance not being able to play my newest tracks on my controller. I wonder if Rekordbox and Serato have similar problems?
It’s actually not too bad, the main issue is you can’t use the normal Time Machine route to rebuild.
You have to put the old OS on a bootable USB, manually remove all your files (music, photos and documents) to an external drive, then do a clean install from the bootable USB, and finally re-add your files and then wipe your Time Machine and back up from scratch.
It’s daunting but as long as you follow the instructions (I usually have them up on a tablet so I can read them) and double check you have extracted everything you need to keep beforehand you should be fine.
I had to go back to Catalina after my SL3 box stopped working on Big Sur, it took me a night to sort out but it was well worth it.
Like you say though hopefully they can sort it.
Ventura has been available since June to developers and the public (for preview) since July. Apple stated that it would be released in the fall. The real fix is for customer facing software companies (i.e. the team behind engine dj) to ensure they test their software at the earliest opportunity and also don’t use deprecated or unsupported API calls. 99% of software runs on upgraded O/Ss without any intervention (unless the O/S provider wants to break software). Yes the “get out of jail” here is to just not upgrade your OS until it’s supported, but that should not be the fix. The emergency alternative to those who may have upgraded their Mac is to install and run “parallels” and then run engine dj on top of that (if no other machine is available). However, you will be starting with a completely empty database, but if you need new material, then you can write to an USB drive instead of a SD card. I’m not sure about all of the controllers, but my one actually supports a USB hub so I can load off several USB drives. However, even with workarounds such as we’ve all suggested, this shouldn’t be an issue in the first place.
I agree Rich, this shouldn’t be an issue in the first place. Its very frustrating and hopefully fixed before I next have to use my controller.
Never, ever update your OS as soon as a new OS comes out, if you use your laptop professionally. Live by this and you’ll always have a happier, less stressful life. : )
If you’re like me and don’t want to downgrade/change machines and just need to sync from the library to a drive, you can use this tool I’ve built:
I only tested it on arm64 (M1) hardware so far. Please read the README and contained disclaimers carefully before using the software.
Hey @lerk looks as if a few of us independents have started to pick up the slack. I was considering writing one that would sync the dbs via playlists (i.e. open up m.db on the main database, open up m.db on the target drive and do some magic) to get people out of this hole. I’ll take a look at yours and if we can agree on a common language maybe we can colab? Glad to see it’s open source - mine will be when it’s reached a level of maturity.
Hi @RichGreen, I’m using golang (doing the UI using fyne) and I decided to just copy the DB files and then open the copied DB to change the track paths; that way I don’t need to touch anything besides the things I need to update.
thanks for doing this. This bailed me out
I used it and was able to synch. Thanks for creating this as a work-around.