09-25-2023, 03:00 PM
(09-24-2023, 10:59 AM)a740g Wrote:(09-22-2023, 08:31 PM)NakedApe Wrote: I've been having QB64 sound issues - thankfully I'm back up and running now - but in trying to resolve the issue I loaded v3.8.0 on my M2 Mac Mini. It set up fine, but when I went to run my current project the program crashed repeatedly and almost instantly. When I reverted back to v3.6.0 everything ran as expected with no crashes. Would the forum's Mac specialist like to see the "Unexpected Termination Report" that the OS spits out? Or is there somewhere else I should post this? Thnx.
Would you be able to share the code that is crashing for you in v3.8.0?
Also, I do not have any Apple Silicon based Macs so I am not really sure if QB64 works correctly on those.
@grymmjack do you run any Apple Silicon based Macs?
@a740g I don't personally have a M1/M2 mac, but work laptop is a M2 mac. That said, I can't put anything on it not work specific. I am aware of the pain and incompatibilities that exist however.
I know that isn't helpful, but it's the truth. I'd kick in $50 and if we could find another 9 folks to do the same, we could buy one for QB64pe development and compatibility testing. Mac Mini https://www.apple.com/shop/buy-mac/mac-m...-gpu-256gb
It looks like you can use platform emulation on the M2 to do the other way around using Rosetta. e.g. M1/M2 can emulate amd64, but not vice versa. In my short stint doing a bit of research the closest I found was qemu which had mentioned stuff.
GitHub runners don't support Apple Silicon either: https://docs.github.com/en/actions/using...-resources
qemu does not seem to have the ability to guest virtualization of arm apple silicon either.
via the process of elimination you could try the other way around, have the user having an issue try it on emulation of amd64 and if it works, then you know something is up with the native arm m1/m2 stuff?
Hope this part helps..