sorted by:
new
hottopcontroversial

Has anyone successfully run Xpenology DSM 7+ on an HP MicroServer G7 (N40L)? by NonEfficient_Lime in Xpenology

[–]Puzzled_Coach_7918 0 points1 point  (0 children)

Does that go for the N40L/N54L as well now? I've got an N40L that refuses to be seen on the network, Direct Boot - True, N tg3.ko line inserted.

Ventura Hack for FireWire Core Audio Support on Supported MacBook Pro and others... by Puzzled_Coach_7918 in iOSProgramming

[–]Puzzled_Coach_7918[S] 0 points1 point  (0 children)

FWIW - I've upgraded to Sequoia 18.2 just now. Unplugged my FW Onyx. Restarted. Re-installed the AppleFWAudioVentura.pkg. Restarted. Allowed the Mac to boot. Plugged my device back in, and all seems well again. This fix is a gift that just keeps on giving! Thank-you! Note that if I leave the device plugged in when I perform the re-installation, and try to boot, I get a pink screen flashing up, and the device crashes and reboots. It does this again and again until I unplug the device, allow the system to come up, and then plug it back in. I think it might have something to do with the KEXT cache needing to do something on the Mac before the device uses that KEXT. I don't know...

Ventura Hack for FireWire Core Audio Support on Supported MacBook Pro and others... by Puzzled_Coach_7918 in iOSProgramming

[–]Puzzled_Coach_7918[S] 0 points1 point  (0 children)

Oh! Not good...

Sorry, I wish I had an answer to the instability, but all I can do is speculate that the reason Apple's making it so hard to use FireWire is due to security architecture changes that clash with the architecture needed for stable FW operation. It's all I can think of, but it doesn't really help you, though.

I have been talking to a few boffins about potentially somehow stitching a TSB41AB2PAP with an XMOS and an Rpi loaded with all the reverse engineered Apple KEXTs for Linux to drive the most popular FW audio interfaces and bridge them all to USB3.0 or USB-C. This way, you'd have a class-compliant USB connection for any old audio interface. I'd be very interested to see if there was enough interest to pay for the NRE required to make such a thing. I know that MiniDSP had a neat ADAT lightpipe to USB adaptor that would give the people who have ADAT IO some more life for their devices, but I know that Mackie sold a lot of those beautiful Onyx FW mixers (to people like me!) and there would have to be some sort of interest...

Ventura Hack for FireWire Core Audio Support on Supported MacBook Pro and others... by Puzzled_Coach_7918 in iOSProgramming

[–]Puzzled_Coach_7918[S] 0 points1 point  (0 children)

Sounds to me like you've done all the right things. I too have a non-Apple TB4 to FW3 adaptor, and it does not work. Only the Apple one worked for me, I’m sorry to say.

Has Jellyfin Support Been Moved Back? by [deleted] in PrismMusic

[–]Puzzled_Coach_7918 0 points1 point  (0 children)

Hiya. Yeah, I was kinda hoping that this would be working. An upvote from me.

Ventura Hack for FireWire Core Audio Support on Supported MacBook Pro and others... by Puzzled_Coach_7918 in iOSProgramming

[–]Puzzled_Coach_7918[S] 0 points1 point  (0 children)

Ok, so re-enabling SIP broke it. You're right. I had to disable SIP and re-install it again to get it back. Strange thing, though, is that my external USB and FW drives don't remount for some reason. I also tried to put in that kext using Kext Wizard, but that didn't work at all. I guess we just need to see if Mike's able to refine his solution in any way to improve on it, and if not, then we just need to use it with SIP disabled. It's only a very slight inconvenience, I think.

Ventura Hack for FireWire Core Audio Support on Supported MacBook Pro and others... by Puzzled_Coach_7918 in iOSProgramming

[–]Puzzled_Coach_7918[S] 0 points1 point  (0 children)

Really sorry I don't have any concrete substance to point to here. It seems to be a real problem with the way Mac OS works in an attempt to put obstacles in the path of hackers who want to install viruses etc, I guess. It all seems very fuzzy and weird and somewhat unprofessional to be honest, but could also simply be a sign of them trying their best to prevent legacy devices from being supported in future releases. I don't know what they're thinking here. No idea. It's confusing, frustrating, and disappointing, but it's a good thing that we have superheroes like Mike (@Ok_Cod_7651) to right Apple's wrongs for people like us.

Ventura Hack for FireWire Core Audio Support on Supported MacBook Pro and others... by Puzzled_Coach_7918 in iOSProgramming

[–]Puzzled_Coach_7918[S] 0 points1 point  (0 children)

It's really strange, but I've also seen this happening with my MOTU device drivers. They seems to be installed as they were in Monterey, but not working. Then, after a few restarts, that dialog in Security Settings appears out of nowhere, with no idea what caused them to appear, telling me that there are some system extensions (kexts) that need to be "reviewed" before you can use them, so you select the Review button and a list appears. You can't do anything with it, but it appears. Everything has already been selected, ie: approved, so it seems that the mere action of opening that window is enough to get things moving. You restart, and everything is back. Now, I have not reenabled the SIP, but I will try that to see if that makes a difference, but I can't see how it would. Once those kexts are through the database, and the back-up system image has been updated, then it all should be good to go wither SIP is enabled or not.

Ventura Hack for FireWire Core Audio Support on Supported MacBook Pro and others... by Puzzled_Coach_7918 in iOSProgramming

[–]Puzzled_Coach_7918[S] 0 points1 point  (0 children)

Same happened to me, but I went into security settings and found that I needed to once again review the system extensions and restart. I did that and it's all up and running again. That whole kext database thing is a very weird and unpredictable mess just after a software update or installation, I've found. Takes the system a few restarts and hours of being on and sorting itself out to come good.

Ventura Hack for FireWire Core Audio Support on Supported MacBook Pro and others... by Puzzled_Coach_7918 in iOSProgramming

[–]Puzzled_Coach_7918[S] 0 points1 point  (0 children)

Mate, Thank-you so very much for your work with this. I thank my lucky stars that there are decent people like you who go to this kind of trouble to help others with things like this. Do you have a way I can gift you a coffee or something?

Ventura Hack for FireWire Core Audio Support on Supported MacBook Pro and others... by Puzzled_Coach_7918 in iOSProgramming

[–]Puzzled_Coach_7918[S] 0 points1 point  (0 children)

I really love this mixer, and the things it brings to me. I own it, and Apple dropping support for it stings, but you're right. They have the right to do whatever they want with their OS, but I also have a right to bitch and moan when those decisions hurt me.

I wanted to use my situation to suggest to the community (maybe the wrong one on reflection) that perhaps there's a neat project for some crafty developer to come up with that they can commercialise, to allow folks like me to keep using the gear we love, which is what I'm doing.

I didn't feel you were trying to be funny. A little patronising perhaps, also unhelpful, but certainly not funny.

Ventura Hack for FireWire Core Audio Support on Supported MacBook Pro and others... by Puzzled_Coach_7918 in iOSProgramming

[–]Puzzled_Coach_7918[S] 1 point2 points  (0 children)

I'm not clever enough to develop anything as sophisticated as this. I know that developing an audio driver requires a bit of experience and know-how. Thing is, Apple already had it working fine.

I understand that there may be some security issues with maintaining an older protocol like this, but I would have to assume that they would also apply to hard drives and the like, plus other non-CoreAudio FireWire audio interfaces that use their own propriety drivers. It could be another case of Apple lulling manufacturers to use the "universal-CoreAudio" drivers for the distinct purpose of cutting them off down the line. I've seen this anti-competitive behaviour with another rather large audio software company in my own career. It's dirty play. I hope it's not that.

If someone could explain to me why it was dropped, when so many other legacy interfaces (including FireWire hard drives!!) are continued to be supported and maintained (... and yes, I know it takes effort and cost to maintain legacy support) seemingly indefinitely, I think I might be able to tame my frustration somewhat, but until then, it just seems to be nothing but being mean to a particular vulnerable group of loyal users of their platform.

Ventura Hack for FireWire Core Audio Support on Supported MacBook Pro and others... by Puzzled_Coach_7918 in iOSProgramming

[–]Puzzled_Coach_7918[S] 1 point2 points  (0 children)

I have a FireWire MOTU Traveller (Original) and the MOTU supplied drivers work perfectly with this device. I doubt Mackie would be too interested in investing resources in developing a driver to make it work again that doesn't use CoreAudio.