TX16WX Bugged Out and I Have No Idea How to Fix It

[joeschmoe99]

I have no clue what happened, but TX16WX (Professional version if it helps) randomly bugged out and crashed Garageband on my new Macbook Air. Now every time I try to load it, it looks like this and doesn't function properly. I've tried re-installing the newest version of TX, but it didn't fix anything. Help!!

[elcallio]

Is this a M1 mac? TX does not have native support for this yet, so maybe this is what you hit? Also, what version of OSX is this?

It looks like somehow yo managed to break both the installed bundle and on-disk skin files. I would suggest manually deleting (oh, if OSX could have uninstallers proper) /Library/Audio/Plug-Ins/Components/TX16Wx.component (and all VST, AAX, VST3 variants as well), then /Library/Application Support/TX16Wx as well as any ~/Library/Application Support/TX16Wx files.
Then try re-installing.
Native apple silicon support is coming at the end of the month.

[joeschmoe99]

It looks like somehow yo managed to break both the installed bundle and on-disk skin files. I would suggest manually deleting (oh, if OSX could have uninstallers proper) /Library/Audio/Plug-Ins/Components/TX16Wx.component (and all VST, AAX, VST3 variants as well), then /Library/Application Support/TX16Wx as well as any ~/Library/Application Support/TX16Wx files.
Then try re-installing.
 

I tried to do this, and it seemed to work for a few minutes then just started getting messed up again. It's not screwing up the skins anymore as far as I can tell, but now it won't even open at all and keeps telling me "An Audio Unit plug-in reported a problem which might cause the system to become unstable. Please quit and restart GarageBand." and gives me the option to either "recover" or "quit". I tried clicking recover and it loads something, but nothing changes and it still gives me the same error message. Quitting the application just puts me in a loop of trying to recover the plug-in and it still refusing to work. It's probably worth noting that this only started happening since I got the TX16WX Pro License.

Also to answer your question, it's an M2 and is on the most up-to-date version of OSX, whatever that may be.

[elcallio]

Yeah, M2 + Ventura is wholly untested, so it is very likely the rosetta translation failing here. Give me a few days (hoping to get my M2 tomorrow) and I'll have a native version up.

[elcallio]

If you try the latest drop of 3.6.0 beta, it now has native ARM support on MacOS, and should work proper on ventura (in my limited testing).

[joeschmoe99]

Thank you so much! I will try it out as soon as I get home.

[joeschmoe99]

So, I tried it and it seemed to work great...for a bit. I'm beginning to think it may be an issue with Garageband itself. The skins bugged out on me again, so I quit and restarted Garageband and now it's back to straight up not loading. It's doing the same thing with all of my other software. This is why Apple users can't have nice things. :/

[elcallio]

Well, then I am sort of running out of ideas. Note that I put up two different installers for 3.6 now, one for older OSX and one universal for 10.13 and above. I would suggest you try the latter if you have not already. But also check the TX log for what it is saying. If skins fail to load it still sounds like the bundle is broken. Did you ensure manually deleting all TX files from disk before reinstalling?

[elcallio]

Note: I verified this on Garageband on brand new M2 macmini running Ventura: no issues observed. If there is an issue you should really try to generate a core file or something...

[elcallio]

Also, just for kicks, if you check the skin chooser in settings, what is it set to? If you change skin, what happens?

[joeschmoe99]

I've installed the 10.13 version, and it is still not working. I'm not sure what you mean by "generate a core file", and I can't even look at the skin chooser in settings because the software won't load period. Last time I looked though, it was set to "default.skin" and changing it did nothing. Might be worth noting there were two "default.skin" options which I thought was kind of weird. I can't even begin to understand why my stuff isn't working. It's genuinely baffling to me. Lol.

[joeschmoe99]

Hi, Just an update as to what's going on with TX on my Macbook Air M2. I scrubbed all the TX16WX files and downloaded the latest Mac build for 10.13+. Now, whenever I start up a new project file, it works as intended until I close the project. When I open the project file back up and try to access TX, it just gets stuck on the loading screen. I've provided a screenshot of what that looks like below. Is this fixable?

Screenshot 2023-03-17 at 8.17.05 PM.png

EDIT:
I tried to close and reopen the project again to see if it fixed anything, and now some of the tracks aren't playing any sound even though they were just working not that long ago. No clue what caused this but I thought it worth mentioning.

[elcallio]

I would suggest using activity monitor and do a thread dump of the process. Then send it to me.

[joeschmoe99]

I wasn't sure what you meant by "thread dump" but I did see something called "sample process" so I did that for both the AU Hosting Service and Logic itself. It's really long so I'm not sure I did the right thing, but here you go.

Sample of AUHostingService (Logic Pro).zip

Sample of Logic Pro.zip

EDIT: Just for kicks, here's Garageband equivalents.

Sample of GarageBand.zip

Sample of AUHostingService (GarageBand).zip

[elcallio]

Not 100% clear due to no symbols etc, but in both cases, it sure looks like the plug-in that is stuck is actually Zebra2... Maybe you could try eliminating that from the equation and test again, just to see if the problem still appears, and if it maybe gives more info...