Mac Os Ventura Supported Devices

0 views
Skip to first unread message

Telly Piatt

unread,
Aug 5, 2024, 9:40:38 AM8/5/24
to meibaroomsra
Appledropping on-going development for FireWire devices that were supported with the Core Audio driver standard is a catastrophe for a lot of struggling musicians who need to both keep up to date on security updates that come with new OS releases, and continue to utilise their hard earned investments in very expensive and still pristine audio devices that have been reduced to e-waste by Apple's seemingly tone-deaf ignorance in the cries for on-going support.

Probably not the first time you gurus have had someone make the logical leap leading to a request for something like this, but I was wondering if it might be somehow possible of shoe-horning the code used in previous versions of Mac OS that allowed the Mac to speak with the audio features of such devices to run inside the Ventura version of the OS.


AppleFWAudio.kext was removed from Ventura. I took a Mac that still has Monterey, took AppleFWAudio.kext, and modified it slightly so it would install on Ventura. The installation process is the same as installing any third party kernel extension, so you'll have to grant permission in System Settings once prompted.


The google drive link below is a download of the installer package I made. I suggest using the free Suspicious Package application developed by Mothers Ruin Software to inspect this installer package, so you know that it does what I'm telling you it does.


Regarding matt9's hack, well, we all really appreciate it man. Does it work for everybody that tried it? I'm thinking about upgrading to Ventura to try this also, I have a perfectly working RME Fireface 400 interface. But not sure how an eventual downgrade would work or if I would need to actually reinstall everything from scratch..


If you have any familiarity with the 'underground collective who builds Mac clones using regular PC parts' - you may have heard of an app called Kext Wizard. It's used to do just exactly this sort of thing (properly install kexts & then rebuilds permissions).


I am in the same boat...Maybe Apple is more sensitive for security risks. And this decision does introduce a risk caused by an Apple decision.Very often a seemingly more secure, but in reality more complicated technology completely removes security in the real world. People need to get work done, if security measures are in the way, they bypass them.This is a perfect example, it should be reported as a security flaw! Maybe they are willing to listen to that aspect...


Hoping Apple will reply, or even notice, a few requests among the millions received daily, may be a tad optimistic.However, how would we go about creating petition, or some kind of group poll, that they might react too?What would be the best format to accomplish this in?


Unfortunately doesn't work with my Motu Traveler v1 on M2 pro Mac mini. I tried installing with Kext Wizard and pacifist after disabling SIP and it never shows up after multiple restarts and accepting extensions in system settings.


Have been playing around with getting this to work this afternoon. I'm on a Mac Mini M2 PRO + Ventura 13.2. I wasn't able to make the installer work, unfortunately. So I used 'Suspicious Package' to extract the AppleFWAudio.kext file from the installer. I've dabbled for years in the Tonymacx86.com world, so I am somewhat used to doing this sort of thing.


...but nothing shows up in the Sound System Settings option. I have another audio interface now that is my primary interface, but I could sure use the extra input channels with doing a bigger session & need more than 8 channels of input (other interface has 8 mic pre's).


I have managed to get this working on an M2 2023 MacBookPro. I'm using an Apogee Ensemble Firewire and it is now detected and works, mostly. I had to use kmutil myself to get the kernel extension to load. The script in the package didn't work so I just grabbed the files from it using Suspicious Package, disabled SIP, modified my Startup Security Utility settings and then ran kmutil in the terminal.


However, I have been having problems with my system crashing at random intervals when using the ensemble. I'm going to keep tinkering and see if I can figure out a work around. Any assistance folks can provide would be greatly appreciated. I noticed a similar situation for folks here: eyetvforum.com/index.php?/topic/305278-incompatibility-with-macos-13-ventura-beta/My console reports: Library not loaded: /System/Library/Frameworks/FWAUserLib.framework/Versions/A/FWAUserLib


Thanks Apple ??? You now disabled this ability in Ventura 13.4 ??? I have no words.... Now I'm getting error message that this Kext cannot be loaded. Once I'm clicking on "Allow" button, I'm getting to the loop where I need restart computer.


Hey! Need help from you guys. Im got a Mac Mini M2 Pro, with ventura installed, i have a Mackie Onyx 1640i, Firewire audio interface. With the help of this post, i was able to make Ventura recognise the audio interface in the System Report, on the firewire devices, but it doesnt appear on Audio Midi Setup, System Sound or in Ableton Live. I followed all steps from this post, minus the "kmutil" command, it always give me an error. Anyone can help me please? I need this audio interface to work...thanks in advance


I very sad and very worried because im update my MacBook Pro to Mac OS to ventura and my very expensive firewire audio stuff stop working, It worked in Monterey with the "dongle-chain" Thunderbolt 3 adapter -> Thunderbolt 2 Adapter -> Firewire Adapter-> Firewire 800 to 400 adapter


Thank you for your assistance!!! I currently own a Mackie D4 Firewire mixer and I'm looking to upgrade it to be compatible with the latest Logic update. I'm wondering if the AppleFWAudioVentura.pkg package will work with Sonoma. It's quite frustrating that Apple promotes sustainability goals while seemingly neglecting the issue of making Firewire hardware compatible with a straightforward software fix.


I been the same, I had several Echo AudioFire audio interfaces, and suddlenly all gone because Ventura does not include the AppleFWAudio.kext what allow Core Audio FW devices to be recognized as Audio available interface for the OS.


I go Back to Monterey and use it that way until a few weeks back (what is really a pain, but Timemachine allow at least to recover my data). So I decide to check if there is a solution and if recent Ventura version works, just find out it is the same. Before I go back to Monterey investigate further and get a very good solution.


I have a near 20 year old LaCie 160GB HD used with my old Cube and it mounts under the latest Ventura. Not the same as the item under question, but uses the adapter with my MacStudio in a daisy chain with another HD between.


Hey be careful with them words there. I wrote exact thing a week ago, 2 times and both times a moderator removed it for some reason. The fact yours is even still there and mine was removed *twice now* makes me wonder.


However our customers tell us this version will install and work for them in most cases on 10.11-10.15. So you can think of it as "compatible" on those versions because it seems to work (it uses an Apple Firewire driver), but not "supported" because we do not test or guarantee it will work flawlessly.


Starting with macOS 13 Ventura, Apple has removed the Firewire CoreAudio driver upon which the Duet & Ensemble Firewire depend. The result is these devices will not work at all with Ventura or newer OS's. For continued use of these devices, please remain on macOS 12 Monterey or earlier.


Even without Maestro software, the Duet Firewire it is still recognized by Apple's Firewire Audio driver and works on a basic level in Mac Sound Preferences. You will only be able to control or adjust settings using Apple's Audio MIDI Setup utility, or the physical controls on the interface. You will not be able to access or change other features or settings that require Maestro.


(I'm on macbook pro m1 ventura with onyx 1620i). Was not working for me continuously until I went to the startup security in recovery mode and enabled kernal extensions. I disabled SIP: csrutil disable , in terminal, then entered: kmutil trigger-panic-medic--volume-root/Volumes/Macintosh_HD Then I went to rerun this program from Matt and then went back to terminal to enter: csrutil enable --without kext .Finally it is working on restarting the machine several times.


Hey can you help me out i tried installing the package from matt it worked but the mac kept restarting and for the fear of it being damaged i reenabled sip and it returned to normal but the firewire device is not visible ss before what is my next step like you did


Apple representatives are not here. We're all end users like yourself. Tell Apple what missing features you'd like restored or new features added to the system via Feedback - macOS - Apple.


Students and exam-takers downloading the test-taking software, Examplify, should review these Minimum System Requirements (MSRs) to ensure their devices are supported. Examplify works with most modern computers, both Mac and Windows operating systems. To keep Examplify current in the rapidly evolving market, when new technology is introduced, Examplify works hard to timely implement updates that accommodate changes in technologies. It is not always possible, however, to support all hardware or software, unless and until we test and certify updated technologies, including chipsets and operating systems.


While unsupported versions may still function, ExamSoft may not troubleshoot issues arising on unsupported versions. Users encountering technical issues on an unsupported version may be instructed to update to a supported version in order to resolve their issue.

3a8082e126
Reply all
Reply to author
Forward
0 new messages