Quote
Chai sir what mike means is as users we would love to help but if you do not give a detailed report on the forum no one can help you.

Exactly.

You must walk us through your problem step-by-step. Either we can duplicate it on our systems or we can't. Either result is valuable. Oftentimes, we can see the user error and post how to avoid it or suggest a workaround. Sometimes we can verify an actual bug and submit it ourselves.

A bug is a result of a documented action that gives contrary results. If the documentation states that, to accomplish x, you follow steps a, b, c etc. and that doesn't work, then it's either a bug or the documentation is incorrect.

What is not a bug: I want the app to do x but it won't — that's a feature request and you've made many. There's nothing wrong with that but you might not get it in the current version or ever. Apple will drop Rosetta 2 with macOS 28 which means that BIAB 2027 for the Mac will need to be Native but it will not happen before.

Yes, I am experienced in reading bug reports but I am just another user and do not work for PG Music so I do not want to read yours—I don't care about them. If, however, I am attempting to verify what you are doing and that generates a crash log on my system, I will read that and see what it tells me.

BIAB 2025 Audiophile Mac
24Core/60CoreGPU M2 MacStudioUltra/8TB/192GB Sequoia, M1 MBAir, 2012 MBP
Digital Performer11, LogicPro, Finale27/Dorico/Encore/SmartScorePro64/Notion6 /Overture5