3/24/2023 0 Comments Uviworkstation updateI ran into the same problem after getting my new M1. I'm planning on keeping this Mac Pro around for a while, and if it dies replacing it with a Windows box to serve as a VEP slave for software like this, because this is how it's worked forever on the Mac side, OS 9 to X, PPC to Intel, and now Intel to M1 always ends up with some software being ends of line. Not my favorite MOTU trait, M53 is not currently listed as deprecated on their site, but it is. So the libraries attached to M53 will not work on an M1 Mac. The M53 iLok license is what authorizes the 9+ libraries that come with M53, and M53 hasn't been touched software wise in years, so the license is not current enough for M1 software changes, MOTU would probably have to pay to update it and even update the M53 application to allow for the changes on the iLok side. Got ahold of MOTU about this, because basically this is an iLok issue. UVI aren't able to help, it's not really an UVI issue. UVI aren't responding to my support request. Maybe I'll try installing Falcon on my Mojave intel machine and see if it opens the. ufs volumes from the original M5 library somehow need iLok authorization to open in Falcon. Some of these are duplicated in the MOTU Instruments download from MOTU I think? I have to check. ufs file so that it appears as a volume in the MachFive browser, yes? So once an instrument is saved onto a drive and not into the virtual UFS volume, it should be able to be used without the iLok from then on. All the iLok is necessary for is opening and mounting the large. You'd think that there's likely a way to open instruments individually in Falcon and then save as Instrument + Samples in Falcon which might then decouple the instrument from the need for iLok. Worth contacting MOTU about, I kinda doubt UVI are going to offer a solution there. They still work of course with the iLok plugged into a Intel Mac, but I'm willing to bet it's a matter of some iLok update that either PACE has to do, or unfortunately MOTU has to pay to update for. Most of the libraries that come with M53 are not showing as authorized on Apple Silicon M1 etc. The burning question really is what is going to happen to the M53 libraries that are attached to it's iLok? Opening AudioFinder in Rosetta mode you can play them, but the code OS level I suppose is not there to translate them to AIFF or WAVE. Reason Studios have the new SDK out, but as of now if you drag a REX file into DP it crashes, and they don't load in Falcon or UVI workstation. It's one of many reasons I'm keeping Mojave on a Mac Pro in the studio.Īnother thing, Monterey and M1 Macs as of this writing do not support REX files. exs translation even though they supposedly still offer it. Yeah that's the major negative difference between M53 and Falcon, UVI are no longer licensing the Chicken Systems translations that MOTU did with M53, and like I mentioned, UVI are ambivalent about. Just trying to phase out MachFive3 as a plug in in my projects. So it looks like I'm going to have to one by one load the EXS instruments with MachFive3, locate the samples, then save from MachFive3 and convert all the Logic EX instruments that way and they should then all be useable in Falcon.īottom line is it's good to keep MachFive3, especially the Standalone app, on your drive and working in case you'd ever have a need to translate an EXS format. uvip extension, but it seems unnecessary. You CAN do a Save As and Falcon will save in Falcon's format which has a. You cannot direct import in Falcon!! Once you've loaded the MachFive 3 instrument into Falcon, saving it retains the MachFive3 format. MachFive3 does not save as EXS) and THEN I can open it in Falcon and it will sound as it should. So apparently what I have to do is import each EXS instrument using MachFive3 and then save it as a. I sent an archive with the necessary files for one instrument as an example to UVI to see if they can reproduce. The bigger issue is that EXS instruments imported with Falcon JUST SOUND WRONG! After moving the appropriate directors to my Sample Libraries drive, that issue was solved. I'm in contact with UVI tech support over my original issue which was not being able to find the samples when prompted to locate them in Falcon. What I've found is Falcon is utterly unreliable at correctly importing EXS instruments.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |