I want to scream and yell and smash things.
I opened a project to write audio tracks for an abandoned plugin that doesn’t work in Mac OS Monterey (Tassman). I did not check that the BFD portions of the song were playing, because it was working FINE for the hours prior on other projects, and this is a very long piece of music with the drums at the end.
I saved my changes, moved the project over to my newer iMac (the reason I have to leave Tassman behind)…
…only to find BFD is silent. The lack of BFD3 being authorized resulted in it saving the project with NOTHING, NADA, ZERO in BFD. I have NO EFFING IDEA what the drums were and I don’t even know where to go look, since I moved everything to BFD3. It kept the name of the settings in the preset name area at the top of the UI, from when I ported the settings from BFD2, but none of the ACTUAL settings. This is an EGREGIOUS BUG caused by EGREGIOUS licensing tech.
Your licensing tech is goddamned GARBAGE and I am so disgusted with the MONTHS of SUFFERING that this GARBAGE product has caused me due to converting my projects from BFD2 to BFD3, the preset loading bugs that made that process take three times longer, and now this APPALLING SCREWUP with the licensing killing the plugin’s settings!!!
I cannot imagine EVER spending money on inMusic or BFD, ever ever again. At some point, I will have to write all my BFD tracks to audio and abandon the product entirely. NO ONE should EVER tolerate this number of problems in a product from ANY company. inMusic’s insistence on using this effing BS licensing scheme is a constant form of abuse on their PAYING customers.
EDIT: If anyone gives a damn, I recovered the preset from an older version of the file I had in my Trash from when I moved the new project file to the newer iMac. There seems to be a bug in Mac OS networking that corrupts packages like Logic project files when replacing an old one with a new one across the network, so I started just having it do “Keep Both”, and then trashing the old copy and renaming the new one from “…2”. This was a lucky coincidence (that I had this old copy - though, yes, I do keep backups, and I didn’t even think about that in the moment, because I was FREAKING OUT), so I am still outraged. I am fairly sure that this didn’t occur to other projects earlier this morning/last night, but this could have been a MASSIVE LOSS for me in terms of ruining a very important song for me.
This is a DATA LOSS BUG.
FIX THIS GODDAMNED PRODUCT.