Now that JUCE and PACE are married, can we please get a place where verified AAX developers can talk about everything PACE?
Surely there must be a way to offer such a space to paying customers, who pay for both JUCE and PACE. The PACE docs are themselves behind a login, a similar space could be offered either on this forum or on their website, where only users with appropriate access can talk.
I decided to spare everyone the personalized rant, as to why this is a good idea, but I know PACE and the inability to talk about it to other developers has been a sore point for many on here for quite some time. Alone just having the ability to browse other peoples PACE issues to resolve your own, is a crucial part of development that is just non-existing with PACE.
I’m 10h into debugging our PACE setup once again (round 5 yay, every simple change is pure hell), the issue seems exotic and support is useless and I’ve read tutorials and docs up and down many many times. I wish I could openly talk to someone in a designated space, who is NOT their support.
I’ve always been curious to talk or just “listen” to someone actually using PACE. I opened a conversation with PACE about two years ago but the project eventually stalled for reasons unrelated to PACE. Maybe it’s a PACE NDA issue, but why not just start a conversation and see how it goes? If it’s popular, the JUCE team could always add a PACE category.
This is - in fact - a NDA issue. We’re basically not allowed to talk about PACE and their tools. And i get it, since they also offer DRM next to their signing stuff, they have incentive to keep details about their inner workings off the internet.
Hence, why I’m asking to get a secured space for it, where verified AAX developers can talk. It used to be, that there was no online-documentation of the tools for the same secrecy reason, and now there is one where they just require you to login with an account that has access.
The same could be offered for a forum and i don’t see any reason why it couldn’t be done, if the documentation is now securely accessible online as well.
It just sucks, that I get an “Error 38” from PACE’s tools, ask support about it after almost 10h of self-directed debugging and deliver insane detail, and all they do is link me back to a 3rd party tutorial on github (the Koala DSP Azure tutorial), assuming I’m doing something stupid, instead of just telling me what their freaking error code actually means. I have gathered many support tickets with PACE over the years and not a single one helped me find a solution, but it’s always patronizing, canned responses that don’t even address your issue (at least that’s my own experience here through the years). In the end solutions always happen, because I find the right, other NDA’ed person privately after days of searching, who coincidentally has seen my issue before.
