toast 10 titanium compatibility with el capitan

#Toast 10 titanium compatibility with el capitan mac os x#
#Toast 10 titanium compatibility with el capitan install#
#Toast 10 titanium compatibility with el capitan upgrade#
#Toast 10 titanium compatibility with el capitan software#
#Toast 10 titanium compatibility with el capitan code#

However, I have asked the question on their Official Statement about compatibility with El Capitan? thread, so we shall see what they come back with. No official word from RME regarding their Firewire audio, though ones like the FF800 and FF400 were officially discontinued anyway. … ending official support of these products on OS X El Capitan and beyond, …

#Toast 10 titanium compatibility with el capitan mac os x#

Note that, as reported on their Mac OS X El Capitan Compatibility Info page, for their Firewire audio interfaces, Duet and Ensemble, Apogee is: So in a nutshell, you can still work at 44.1 or 48 on the Duet until Steinberg sorts this out. However, if I try to launch C8 into a 44.1 or 48k project verify that the audio is working, then try to flip that project to anything above 48 or open another project above that rate and adjust the rates in my Duet 2 and C8 accordingly, I lose audio again. I have been able to confirm that the Duet 2 will work with C8 on El Capitan at 44.1k and 48k. The wording on their site seems to imply that once launched, you can then flip to 88.2 or 96 if you have a project running at that rate, but I can’t confirm that. Many of the Focusrite products will_work with C8 if you set both C8 and the Focusrite device affected by the no audio problem (the Scarlett series and one or two others) to 44.1k or 48k prior to launching it. I tried the same things they are reporting with my Duet 2.

Focusrite reports that a number of their products will work if both the interface and C8 are set to 44.1 or 48k at launch time:.That little bit of effort would have better informed my decision making, and kept me working.Ĭouple of hardware updates that I discovered: It doesn’t take a big Dev team to do that much, and they could have put the message out sooner based on findings at the minimum.

#Toast 10 titanium compatibility with el capitan upgrade#

Not good business.Īs for resources, it takes a Dev or QA person half a day to spin up a beta build, load an Application in development onto it with some array of known common setups, and start reporting the things that are going to be problematic, and another hour or two after that to upgrade and perform some cursory checks again. I feel like the messaging from Steinberg was clear enough, pervasive enough and early enough to stop me. The Apple media outlets had already put out the message that this was a fairly innocuous maintenance release, which is what prompted me to upgrade, at a time I usually don’t. If what you are saying is true, the iOS app store should be brought to its knees with broken apps every time they rolled out a new release.

Not doing so leaves you with a pile of very upset long-standing, dedicated customers.

#Toast 10 titanium compatibility with el capitan software#

I would argue that It is healthy software development - when you are building against a platform that you_know is going to change significantly once a year - to proactively develop against the next release of the platform you are developing for.

#Toast 10 titanium compatibility with el capitan code#

I have had to wait for them to fix issues that affect my code, but if there is change in the API, there are typically options that allow me to stick with the code I have to some degree. I can’t think of a time I had to make any significant code changes to accommodate a GM build at the last minute, after having done dev against a beta, put it that way. I have found that the iOS/OSX beta builds_are good indicators of what final builds will look like. It’s usually fielding and addressing radars around issues with the APIs as they are within that beta. By the time they drop a beta release, they don’t change a whole lot. Yes, there are issues, as there are with anything beta. I’ve had to do iOS dev against beta iOS and Xcode releases.

#Toast 10 titanium compatibility with el capitan install#

company they work for mandates latest versions for security reasons, they develop for iOS/Mac, they need some fix for hw problems, etc) let them wait…Īnd of course anybody buying a new Mac between now and December or whenever the fix is released will have to jump through hoops, un-install the OS, install Yosemite, etc to be able to work with Cubase…ĭon’t know who you are talking to but I disagree. Nothing like a month+ head start of an El Capitan-compatible 8.5 to force users to the paid upgrade if they want to use Cubase on their El Capitan Macs…Īs for the Cubase users who need to be on El Capitan because they use their laptops for other things too (e.g. So learning by history, we’ll probably see the following timetable:Ĭubase 8.5 will be released, early or middle, December and an El Capitan compatible version of Cubase 8 will appear late January, next year. Cubase 7.5 was released in December and Yosemite compatible version of Cubase 7 was released at the end of January 2015. When OS X 10.10 (Yosemite) was released in October 2014, it “broke” Cubase 7.

Learning from history is usually a good idea.