Open emabrey opened 3 years ago
As I stated privately, I think we should wait until our fork matures a bit further and until we gain a general sense of where all of this is is going to go, before we make this sort of commitment that also happens to be a large expense. This seems like a secondary priority for now.
We also need a Apple account. And apple is properitary. I don't have a Apple device nor a apple account.
To clarify, I have an Apple account for other reasons and have volunteered to give a signing key
I'm a registered Apple dev as well. The GPL licensing will preclude it from the app store under the Apple dev agreement (though many manage to sneak some in). On a Mac you can still install separate from the app store. Every few days I sync my repo to the Tenacity upstream and build an app. Once the branding is switched I'll start distributing it to a few my colleagues to see if it's feasible for us to switch. Prior to the pandemic we had 44 shows worldwide with 8 in Vegas. My testing here is limited to a few large shows in Vegas, strictly internal to see if we can switch. Pro Tools is still our primary tool but Tenacity would be a good replacement for when we use Audacity.
In entertainment pro audio Macs are still more or less the standard. Windows boxes have made great inroads in entertainment though creation, recording, editing and mixing is still primarily Mac. Linux is virtually non existent on the pro audio desktop but widely used in embedded apps within hardware.
We need a temporary
Developer ID Installer
certificate for our CI builds of Tenacity.@ajayyy and @emabrey discussed this on 7/14/21 and came to the conclusion it was blocked by the need to generate a Certificate Signing Request on a Mac computer, so this issue was created to track the progress on this.