Thanks Quinn, for your reply! Subpackages are only notarized within our overall product. They are not notarized independently. Because reading your text I get the impression that it’s the latter, but the notary log snippet you posted doesn’t show any nesting. isn't this the indication: "message": "b\"Invalid component package: mypackage_vstpreset Distribution file's value: #com.mycompany.mypackage.vstpreset.pkg\\n\"", its the com.mycompany.mypackage.vstpreset.pkg that contains the non-binary preset files. Thanks

Thank you very much, Quinn, We need to set the thread priority for our streaming engine. Our unit tests are testing its modules - beneath other things - with all kinds of (unrealistic) sample rates. And it tries to set thread priorities for standard sample rates like 44.1kHz, 48kHz, ..., 192kHz, etc. while setting up the streaming engine to run on block sizes from 1 sample to something like 16384, which means the thread needs to be set up for computation down to every 1/44100, 1/192000 sec, etc. IIRC setting the thread_policy below 4/44100 fails. Although this is (for our current tasks) not a very realistic scenario, I think it should work, at least I would like to know how low the unit tests can go, or even better be able to ask the specific machine about its valid thread_policy range.

Enlightening! So, where is the documentation?

Thanks @endecotp! But isn't syncstream not part of the standard, and therefor shouldn't it be available to Xcode?

Thanks for giving the space to get lost in soliloquies! After this breathing practice, I would now like to get back to work and finish the exercise, for example with the help of an appropriate documentation or a hint from the people behind the API/technology. Or you could also just tell me that your operating system does not need my support, then I could go straight to the beach and wouldn't need to wait for the bus here.

Thanks, Quinn! For debugging purpose and exchanging of logs/dumps its sometimes easier to directly write to log files. Which are suitable locations to write from CoreAudio and CoreMIDI? (We see that permissions do change between the MacOS versions.) Thanks, hagen.

Thanks, for giving me the chance to soliloquy. The issue persists in Bug Sur, we have worked around this by requesting a USBDeviceReEnumerate(); This continues to work on M1 for some USB devices, while for others the interface iterator is still empty and is not getting filled by any magic we tried. In this case the USB device is pretty simple it has a single configuration with 2 interfaces. What is the cause for this and can this be fixed/worked around?

--timestamp=none is generally not a good ID as your signature gets invalid when its signing certificate validity expires! You will not recognize any issue with the signed binary until the end of the validity of the certificate.

Any news on that issue?

Thanks again,yep you were right. I don't know why I didn't see them.Unfortunately restarting either/both of the demons does not reset the logging system in a way so it cures the garbled output...BTW. Its not only garbled, it seems also that the logging system accesses the log string at the wrong memory position. Here it seems that it reads the format string at a position skipping the string start which contained %s (to display the denoted string parameter)...<decode: mismatch for [%x] got [STRING sz:59]>] {I am bit clueless right now, since logging is a very valueable and neccesary way of developing/debuggin kernel code. Often its not even possible/manageable to connect a debugger...What can I do to progress here?Thanks & cheers,Hagen

@mhorgan, did you find a way yet to get precedence over AppleMIDIUSBDriver.plugin and possibly com.apple.driver.AppleUSBAudio?@Apple: wouldn't that be easy to answer: just a yes or a no. And if you don't care, just a "we don't care" so we know at least what to expect!Thanks,Hagen.

Thanks Quinn,that seems to be true for Catalina (even for the man page - great, I am impressed...!!!), and there its named properly,but not for Mojave (and unfortunately I am still bound to Mojave for some reasons like svn support, I still need Xcode 9 - while running current Xcode in parallel).What would be the name of the unified logging process in Mojave?Thanks & cheers,Hagen.

Since there is no progress here, is it possible to restart the logging process? Whats the name of the process?

Hi Quinn,I probably don't get you quite right here.Amongst the audio plugin development community there are ongoing discussionsi.e.https://forum.juce.com/t/macos-plugins-in-sandboxed-daw/36999https://forum.juce.com/t/garageband-x-sandboxing/11739and others, which indicate that the entitlements can be successfully set for individual bundles (wether .vst/ .vst3/ .component/ or .aax); this also is in accordance to our own findings - except for IOHIDDevice access, which can't be accessed; even when the sandbox is excepted by setting the plugins com.apple.security.device.usb entitlement.Now, my question is: should this work (i.e. is there something wrong on our side or is there a bug in Apples sandbox)? or is this not suppose to work and how can we achieve in this case IOHiddevice communication from within a sandboxed plugin? So far to me Apples sandboxing does not look being entirely thought thru (what is with other hardware/kext/IOKit access?) but I strongly hope I am wrong here.Having said that, an entire product line is depending on being able to communicate from our audio plugins with our controlling hardware.Or, maybe we are not using the correct (sandbox except-able) API? I see there are more HID related frameworks (i.e. HIDDriverKit.framework vs. IOKit.framework), where we are currently using the later...?!On the other hand, according to the sandbox profiles located at/System/Library/Sandbox/Profiles/application.sbthere seem to be a separate (but nowhere mentioned) "com.apple.security.device.hid" entitlement. Is this the one to use? Can these profiles be "trusted" in any way? Where is the actual documentation?I am blindly tumbling around, waisting my time with simple question... Just because Apples seems to be too ignorrant to provide adequate documentation. Those "maybe this or that" are so tiring and far away from being professional and in the end the cause of bad or wrong development decisions.Thanks & cheers,Hagen.

Thanks Quinn, but I think you are wrong here:https://developer.apple.com/library/archive/technotes/tn2247is indicating the possibilty to control sandbox exceptions.Thanks & cheers,Hagen.