greentrumpet

Thanks, I'll probably download the latest version but might wait until after I upgrade from monterey on my 2017 MBP.

I've kept lots of earlier versions of A+ to go back to but since Studio came out I've found that if I resurrect an earlier version it gets updated. I've been very happy with Studio but would like to know if there is any way to keep and use earlier versions in case I don't like the new iteration.

Thanks Dandou.

I absolutely agree. Is there a discount for those who have been customers of 1 series, 2 series and 3 series, let alone Studio? I have bought in several times, baulked a bit at the subscription model but pleased at it's performance.

Not convinced you can fix this, I bought one to use solely as a USB converter, it failed immediately, straight from the box. I know many rate them but I fear they are unreliable. Thankfully the supplier refunded me.

The installation went fine for me and I'm pleased with the sound. Internet radio is a bonus as well.

Thanks for clearing that up for me.

Audirvana with mojave question. My 2017 MBP is running Sierra, I've avoided High Sierra having seen bad reports and have been satisfied with the performance of Audirvana 3.5 with Sierra. Now there is another OSX update coming is it a good idea to move to Mojave for now or is that a mistake and would I be better staying with Sierra. I'd be grateful for the benefit of your experience.

I'm glad too! Both Apple and the shop that I bought the new MBP from said I could not use El Capitan with my MBP. The Apple store won't provide it saying my MBP is incompatible. I had to completely wipe the drive to re-intall Sierra which is as far back as I can go. But it's good to be able to access all my music again!

Please re-read My old Mac failed. The new one won't accept El Capitan therefore I tried the fix. You kindly entered into a fairly long exchange to help me with the patch but it was still a disaster for me, fortunately I was able to completely wipe my MBP and re-install Sierra ( good job I tried the kext with High Sierra as I was able to go back the the OS my MBP was shipped with) then use a backup to retrieve my data. As you may recall you acknowledged part of your patch assumed the existence of a file that I didn't have.

I tried the patch, wasn't confident as I'm not confident playing with Macs, it was an utter disaster and took days to undo. Wouldn't have been necessary but my old Mac failed and new ones won't accept El Capitan or earlier ( I tried). I e-mailed Apple as suggested, didn't even get the courtesy of a reply.

Well I had to open a new folder as you put yours in a bin folder you already had but other than that yes. I have given up on this but thank you for your help. I will use a backup but don't know if I need to re-enable SIP after, must check. Sadly this was beyond me but I thank you for your patience and other forum members for their helpful suggestions too. Thanks again and best wishes Steve

No, I copied and pasted them from the .txt. The spelling error was just on here! The extensions. chmod and chown commands in step 4 had to be pasted separately as my Mac wanted to highlight the whole line. The Mac didn't ask for my password and I then restarted the Mac. I then did step 5 and pasted 'sudo RepairPermissions /' after I put in my password it said 'sudo: RepairPermissions: command not found' So I don't think I need to put the three commands for step 4 in again, even if i try to copy from here my Mac wants to highlight whole lines. Thanks for your patience Steve

Thanks for your ongoing consultancy! When I copy the commands my Mac highlights in blue to the end of the line wherever I try to start so I pasted the three commands separately. But, when i restarted and pasted the 'sudo RepaitPermissions /' it says command not found. ? Sorry I'm being a pain.

Hello, it's only me! I turned off SIP as described no problem. I replaced the kext in /System/Library/extension no problem. Next I pasted the commands in step 4 in the Terminal app window Ugh message chmod: sudo: No such file or directory chmod: chown: No such file or directory chmod: -R: No such file or directory chmod: root: No such file or directory What could iI have done wrong? If I want to give up on the workaround and restore from my backup will it undo the SIP disabling or do I have to do that first? Thanks Steve