ProSoundWeb Community
Sound Reinforcement - Forums for Live Sound Professionals - Your Displayed Name Must Be Your Real Full Name To Post In The Live Sound Forums => LAB: The Classic Live Audio Board => Topic started by: Mark Norgren on December 10, 2019, 08:43:43 AM
-
Can anyone give a definitive answer on whether or not the new 4.1 app will run on Catalina? The FB page is all over the board. I can't get it load? Thanks in advance!
-
Given Catalina's current track record with various programs' reliability, the crapshoot of success/failure that you're seeing is pretty spot on. There's a whole other thread on here of people trying (and often failing) to get things running like they should.
-
Can anyone give a definitive answer on whether or not the new 4.1 app will run on Catalina? The FB page is all over the board. I can't get it load? Thanks in advance!
Get a cheap Windows machine. Don't wait for Apple or the software authors to figure it out. SERIOUSLY..
-
I'm disappointed that Midas has not worked this out yet? I've seen where some people can seem to get to load, while others are stuck. I'm not in the position to buy a PC just for this one app. Mixing station is working well and I'll go with that for the time being.
-
I'm disappointed that Midas has not worked this out yet? I've seen where some people can seem to get to load, while others are stuck. I'm not in the position to buy a PC just for this one app. Mixing station is working well and I'll go with that for the time being.
The hit-or-miss operation is likely due to some users having a program or driver package installed that has a dependency/driver/library that is 64-bit compatible, and therefore allows M32 Edit to run.
I think a lot of people don't quite grasp just how big of a wrench in the works Catalina is for developers. With Catalina, support for ANY 32-bit processes is removed. That includes core programs, plug-ins, license/activation services, audio/video/device drivers, etc etc. The issues are also not limited to 'smaller' dev outfits like MG, either. Adobe is having a ridiculously hard time navigating this change as various 32-bit components are in every single product and utility they offer. Microsoft is in a similar boat with its Office suite. So if a user 'upgrades' to Catalina, they not only can't use these apps, they can't even uninstall them since the uninstaller is, you guessed it, a 32-bit application. Catalina also removes itunes, so any program that relied on it for library management or audio services is bricked as well, which covers a hefty portion of DJ tools and production software like Apple's own Protools.
This isn't the first time that a new version of MacOS has screwed things up, by this point I figured Apple users would be used to waiting 3-6 months after a release to let everything settle, especially those users who depend on their devices in a professional capacity. It's an easy enough process to downgrade back to Mojave or Sierra, so people may as well do that until all this gets sorted out.
-
I'm sure as hell not switching to a Windows machine for my daily driver. I've just learned to put off major OS updates as long as possible. There's nothing wrong with the older system I'm running so why upgrade before the dust settles? Not helpful for OP, but if you need the apps more than the new OS "improvements" why be so quick to update?
[posted from 2018 MBP running Mojave 10.14.6]
-
Unfortunately, my Mac was having some issues and the only way Apple suggesting fixing was to update. It did fix the issues of freezing and not loading properly, unfortunately the one app that did not take was the Midas. I had a few others that I use that went well, not so much with the Midas app.
-
If having the Behringer editor run correctly on your computer is mission critical to your computer use it sounds like its time to back up your machine to an external drive, wipe the internal drive and reinstall a version of the OS that supports that app ( Mojave would be the last version before Catalina ) and then reinstall all your other apps and docs. If you Mac won't work correctly with the OS that shipped with it that sounds like you have a hardware problem or a faulty install of the OS.
Unfortunately, my Mac was having some issues and the only way Apple suggesting fixing was to update. ...
-
For the time being, I'm staying on Catalina. Although it would be nice to use the software, Mixing Station has filled in most of the holes. I can do most of the setup from the board and then take it to FOH with my iPad. My guess is that Midas is working on it and it will just be a matter of time before all is well? Fingers crossed!
-
So can confirm that the latest one will not open on Catalina but the previous version I was using(Nov 2017?) runs although not sure if it will work if the console is on the latest firmware version.
This puts the fault firmly on MG. If the old version is running they added something without confirming it, Catalina dropping 32bit support has been announced for years already, this is not a shock for software developers.
-
I know people like to crap on the Vendors for not updating software to work with Mac's newer OS's, but I think Apple is to blame. For years Apple has been releasing OS's that are not compatible with recently updated software. At what point does it become Apples problem to be sure users can rely on software that they paid good money for ( or not ) to just fricken work? I have a Mac that is locked into what is an ancient OS because the software WILL NOT work with anything newer and the Vendor has since stopped supporting the devise and software ( for obvious reasons ). Mac needs to realize that they are charging a lot of money for a machine that for many people, is a work-related unit, and it HAS TO WORK for them. I am so angry with Apple these days. Between making phones that will surely be electronic waste within 2-3 years they also can't make a backward compatible OS.
-
So can confirm that the latest one will not open on Catalina but the previous version I was using(Nov 2017?) runs although not sure if it will work if the console is on the latest firmware version.
This puts the fault firmly on MG. If the old version is running they added something without confirming it, Catalina dropping 32bit support has been announced for years already, this is not a shock for software developers.
While the announcement of their dropping 32-bit support was telegraphed early on in Apple's development process of Catalina, the developer's beta hasn't even been in the wild for 6 months and has seen numerous revisions that made any third-party dev road map a moving target. Now that Catalina itself is fully released, we can see third-party devs finally sink their teeth into rewriting their apps to work in a totally new environment.
Expecting a sub-6 month turn time on developing an app from scratch is already crazy, then add that this is not a company whose expertise is in software development and you can hardly place all the blame at the feet of the devs. Even software giants like Adobe haven't resolved their issues yet, and will likely not until well into next year.
-
While the announcement of their dropping 32-bit support was telegraphed early on in Apple's development process of Catalina, the developer's beta hasn't even been in the wild for 6 months and has seen numerous revisions that made any third-party dev road map a moving target. Now that Catalina itself is fully released, we can see third-party devs finally sink their teeth into rewriting their apps to work in a totally new environment.
Expecting a sub-6 month turn time on developing an app from scratch is already crazy, then add that this is not a company whose expertise is in software development and you can hardly place all the blame at the feet of the devs. Even software giants like Adobe haven't resolved their issues yet, and will likely not until well into next year.
Built from scratch?
All you have to do in most cases is recompile as a 64-bit app instead of 32 for it to work. (I'm a programmer). Now, if the manufacturer relied on 32-bit 3rd party plugins or other things that they can't recompile, and the 3rd party no longer makes those plugins, then that's on them, not Apple. This was a mistake the programmers should have dealt with years ago.
-
While the announcement of their dropping 32-bit support was telegraphed early on in Apple's development process of Catalina, the developer's beta hasn't even been in the wild for 6 months and has seen numerous revisions that made any third-party dev road map a moving target. Now that Catalina itself is fully released, we can see third-party devs finally sink their teeth into rewriting their apps to work in a totally new environment.
Expecting a sub-6 month turn time on developing an app from scratch is already crazy, then add that this is not a company whose expertise is in software development and you can hardly place all the blame at the feet of the devs. Even software giants like Adobe haven't resolved their issues yet, and will likely not until well into next year.
The older version of the app works on Catalina, only the new 4.1 version does not? This is a MG problem, 4.1 released after Catalina release AFAIK.
-
I just found a link to a 3.2 version of the app. It loads fine on Catalina? That is CRAZY! What is the hold up on the newer version. I am now more confused than ever? Here is a link to all of their stuff for the boards. For now, I will try and use the older version of the app on my Catalina laptop!
https://www.midasconsoles.com/c/Midas/Downloads?text=m32+4.1#googtrans(en|en) (https://www.midasconsoles.com/c/Midas/Downloads?text=m32+4.1#googtrans(en|en))