MacOS 13/14 fix for Bazille, ACE, Uhbik, MFM2, F'Scape
- u-he
- Topic Starter
- 28063 posts since 8 Aug, 2002 from Berlin
Hi all,
As you know, the file sorting issue with APFS in High Sierra (and now Mojave) took us by surprise. While luckily it coincided with the advent of our revised preset browser, we have not yet been able to tag all presets of all products and update the UI of each. So we took a backup of the old code base (rev 3898), made it compile under our current tool chain and added workarounds to save presets. In doing so, we have ACE, Bazille, Uhbik, MFM2 and Filterscape back up and running on those Macs again, with presets sorted.
However, we had to leave VST2 32-bit and AAX support behind in these versions - whatever happened since revision 3898, I couldn't bring those back
We will continue to update our existing plug-ins (including formats omitted now) with the new preset browser, but it takes an amazing amount of time. Therefore, a temporary fix:
ACE 1.4 APFS hotfix revision 7859
Bazille 1.1 APFS hotfix revision 7859
Filterscape 1.4.1 APFS hotfix revision 7859
MFM2 2.2.1 APFS hotfix revision 7859
Uhbik 1.3.1 APFS hotfix revision 7859
Please let us know if you experience any problem.
Thanks,
- Urs
As you know, the file sorting issue with APFS in High Sierra (and now Mojave) took us by surprise. While luckily it coincided with the advent of our revised preset browser, we have not yet been able to tag all presets of all products and update the UI of each. So we took a backup of the old code base (rev 3898), made it compile under our current tool chain and added workarounds to save presets. In doing so, we have ACE, Bazille, Uhbik, MFM2 and Filterscape back up and running on those Macs again, with presets sorted.
However, we had to leave VST2 32-bit and AAX support behind in these versions - whatever happened since revision 3898, I couldn't bring those back
We will continue to update our existing plug-ins (including formats omitted now) with the new preset browser, but it takes an amazing amount of time. Therefore, a temporary fix:
ACE 1.4 APFS hotfix revision 7859
Bazille 1.1 APFS hotfix revision 7859
Filterscape 1.4.1 APFS hotfix revision 7859
MFM2 2.2.1 APFS hotfix revision 7859
Uhbik 1.3.1 APFS hotfix revision 7859
Please let us know if you experience any problem.
Thanks,
- Urs
- KVRist
- 344 posts since 3 Mar, 2015 from Japan
-
- KVRian
- 601 posts since 23 Jun, 2005
Thanks very much for these! Working well so far in 10.13.6
-
- KVRian
- 601 posts since 23 Jun, 2005
One small thing I've noticed - in Bazille, I have a folder of presets I made which are all .fxb files, and this new version of Bazille won't load them - the folder shows up as empty. Any idea what could be going on?
-
tasmaniandevil tasmaniandevil https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=62450
- KVRAF
- 1734 posts since 22 Mar, 2005 from a planet called u-he
Since Bazille (rev 3898) does not let you choose the format you want to save the preset in, you must have saved those presets with your host software, rather than with Bazille.mustgroove wrote: ↑Mon Oct 29, 2018 6:12 pm One small thing I've noticed - in Bazille, I have a folder of presets I made which are all .fxb files, and this new version of Bazille won't load them - the folder shows up as empty.
I have tested it, and .fxp as well as .vstpreset presets will show up in rev. 3898, as well as in rev. 7859.
But not even revision 3898 would show me .fxb files, since those are preset banks, not single presets (those would be saved as .fxp).
Did you maybe usually load those fxb presets through your host software? Could this be?
I tried it in Ableton Live, which lets me save and load .fxb files.
This works, but as said, you'd have to use Ableton Live's (or whatever host you are using) preset management to load those .fxb presets.
Pretty sure that .fxb files were never showing up in our plugin's integrated browsers (I could be wrong here, but I am almost sure).
That QA guy from planet u-he.
-
- KVRian
- 601 posts since 23 Jun, 2005
Thanks for the reply tasmaniandevil - I think I must have saved them with Ableton rather than with Bazille itself because they're FXBs (which Ableton defaults to when you save VST presets), either that or they were saved with a very old Bazille version, possibly the beta.
In any case I saved them as H2Ps using rev 3898 and then updated to 7859, and all is well.
In any case I saved them as H2Ps using rev 3898 and then updated to 7859, and all is well.
-
tasmaniandevil tasmaniandevil https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=62450
- KVRAF
- 1734 posts since 22 Mar, 2005 from a planet called u-he
Yes, I noticed that too, when I checked it with Ableton. I found it a weird decision to offer fxb as the default format, rather than fxp.mustgroove wrote: ↑Mon Oct 29, 2018 8:19 pm I must have saved them with Ableton rather than with Bazille itself because they're FXBs (which Ableton defaults to when you save VST presets)
Phew, good to hear that.mustgroove wrote: ↑Mon Oct 29, 2018 8:19 pm In any case I saved them as H2Ps using rev 3898 and then updated to 7859, and all is well.
That QA guy from planet u-he.
-
- KVRist
- 56 posts since 6 Jul, 2008 from Sherwood Park, AB, Canada
Works great and I can save my favourites!
Rainguitar is a writer and musician living in Sherwood Park, Alberta. He is known by his pseudonym "T.K. Boomer" which he uses to write science fiction. Music production is a hobby.
-
- KVRist
- 393 posts since 12 Sep, 2005 from NYC
I'm using Sierra not High Sierra or Mojave am I correct in assuming these fix's aren't required?
Thanks
Thanks
2012 Mac Pro,3.46 Ghz,12 core 96g ,Mojave,RME, DP11.01, Logic 10.51,RME UCX, Great River ME-1NV, a few microphones,Spectrasonics, U-he Komplete12U & way too many VI's,Synths & FX galore!, UAD,Mimic Pro/SD3,Focal Twin 6 monitors, Shunyata ....
-
- KVRAF
- 2313 posts since 20 Oct, 2014
Yes, then it is not required. It is about APFS. You also can update to High Sierra without a APFS conversion, keeping HFS+ (which runs faster here on non-apple-drives), by starting the updater app from terminal with:
For High Sierra:
For Mojave you will need to make a 1:1 clone to another (external) drive using CarbonCopyCloner, then update (+ automatic conversion) and then 1:1 clone back to your internal, still HFS+ formatted drive. AFAIK. Maybe there already is a way while using the installer, but I don't know about it.
For High Sierra:
Code: Select all
/Applications/"Install macOS High Sierra.app"/Contents/Resources/startosinstall --converttoapfs NO --agreetolicense