Re: [PD] [hidraw] pre Deken release. was:(Reading/writing a HID device current best practice?)

One option is to directly circumvent the app/binary quarantine process. Essentially, you can remove the quarantine flag manually: sudo xattr -r -d com.apple.quarantine path/to/MyApp.app Print the current flags to check with: xattr path/to/MyApp.app I think this should work with dylibs

Re: [PD] [hidraw] pre Deken release. was:(Reading/writing a HID device current best practice?)

I'm still on old macs and I am not yet sure if my stuff is working or not in new macs. I just updated ELSE btw, I am now wondering if people can use it just fine or if it doesn't work or is a nightmare (like asking every time if on external should be loaded). Em ter., 11 de out. de 2022 às 15:03,

Re: [PD] [hidraw] pre Deken release. was:(Reading/writing a HID device current best practice?)

looks like you can „ask apple“ only if you are "members of the Apple Developer Program or Apple Developer Enterprise Program“ furthermore topics are set to apples latest + shiniest https://developer.apple.com/events/ask-apple/questions-and-answers/

Re: [PD] [hidraw] pre Deken release. was:(Reading/writing a HID device current best practice?)

Looks like we could “Ask Apple”… https://developer.apple.com/events/ask-apple/ I would like to know how an open source project which relies on freely-shared plugins is supposed to exist on a platform that is making it harder on accessibility. I have had a developer account for many years but

Re: [PD] [hidraw] pre Deken release. was:(Reading/writing a HID device current best practice?)

You already have you answer: no code signing or notarization means users get the security popup when the dylibs are loaded but they just have to select open as far as I know. Gatekeeper asks them once, then the system remembers the selection. I believe it may also require changing a privacy

Re: [PD] [hidraw] pre Deken release. was:(Reading/writing a HID device current best practice?)

hi lucas, > if I don't codesign/notarize the builds: is just that users have an "open > anyway" dialog? or is it a total "show stopper" that quits Pd? its a bit more than just that (sigh), but not a complete show stopper. i fully symphatize with your take on that, even if it means i will have

Re: [PD] [hidraw] pre Deken release. was:(Reading/writing a HID device current best practice?)

@ Dan Thanks for sharing this. I'll be digging about  ` you need an Apple Developer account (and Apple ID to sign up for one)`. If there's no workaround about the us$100 i'll be giving up notarizing builds. Do you know of a way to not send money to the thieves (if i'm not mistaken) ? or to

Re: [PD] [hidraw] pre Deken release. was:(Reading/writing a HID device current best practice?)

Am 11. Oktober 2022 16:48:42 MESZ schrieb Lucas Cordiviola : > > >Do I need an `apple developer` account ? Yes. 100.00$ iirc. mfg.sfg.jfd IOhannes ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management ->

Re: [PD] [hidraw] pre Deken release. was:(Reading/writing a HID device current best practice?)

Howdy Lucas, I have the makefiles working but realize now I need to do some refactoring to better handle non-app bundles like dylib libraries. Apparently the notarization process is a little different. In any case, you can check them out for now but I will be working on them further:

Re: [PD] [hidraw] pre Deken release. was:(Reading/writing a HID device current best practice?)

@ Dan I'm back on my "machines home". I did:     xcrun notarytool and I got its help options. Do I need an `apple developer` account ? I don't even have an `apple id`. How should I proceed? do I wait for your script? do i get my `apple id`? I'm sure I'm not the only one willing to provide

Re: [PD] [hidraw] pre Deken release. was:(Reading/writing a HID device current best practice?)

I meant "server room" as "machine room" or more accurate "home". I actually have an Monterey VM via qemu on Debian11 (on some amd-A6 cpu). I tried `xcrun --find altool` and it returned `not found`. I got xcode via `xcode-select --install`. -- Mensaje telepatico asistido por maquinas. On

Re: [PD] [hidraw] pre Deken release. was:(Reading/writing a HID device current best practice?)

I'd suggest the latest versions of Big Sur, so 11.7. My work laptop is on 12 which is also fine. macOS 13 Ventura comes out soon, but it's too soon to set up a build environment for it, at least on a server. > On Oct 8, 2022, at 3:16 PM, Lucas Cordiviola wrote: > >> Actually using altool is

Re: [PD] [hidraw] pre Deken release. was:(Reading/writing a HID device current best practice?)

istido por maquinas. On 10/7/2022 8:17 PM, Dan Wilcox wrote: On Oct 7, 2022, at 12:00 PM, pd-list-requ...@lists.iem.at wrote: Message: 1 Date: Thu, 6 Oct 2022 17:32:50 -0300 From: Lucas Cordiviola To: "hans w. koch" Cc: William Brent , Pd-List Subject: Re: [PD] [hidraw] pre Deken r

Re: [PD] [hidraw] pre Deken release. was:(Reading/writing a HID device current best practice?)

ailto:william.br...@gmail.com>>, > Pd-List > mailto:pd-list@lists.iem.at>> > Subject: Re: [PD] [hidraw] pre Deken release. was:(Reading/writing a > HID device current best practice?) > Message-ID: > > > <mailto:ds7pr10mb484547c68358a0f3802

Re: [PD] [hidraw] pre Deken release. was:(Reading/writing a HID device current best practice?)

Thanks Hans! I thank all the M1 testers. Seems I'll wait for Dan's makefile for the notarizing stuff. Or later try to update if possible my Xcode VM (as in iem-ci.yml) to be able to : "try to switch to the latest and greatest XCode, so we get 'altool'" and stuff. M1 users please note that

Re: [PD] [hidraw] pre Deken release. was:(Reading/writing a HID device current best practice?)

hi lucas, i just tested on mac os monterey / M1 and i still had to allow the same way as william. then it worked fine (only had an external mouse to test - not very thrilling…) thanks for the effort! hans > Am 06.10.2022 um 16:41 schrieb Lucas Cordiviola : > > Hi William, > > Thanks for the

Re: [PD] [hidraw] pre Deken release. was:(Reading/writing a HID device current best practice?)

Hi Sebastian, Thanks for the test. Would hidraw enable to get access multitouch data? Like fingerpincher on Max? I doubt it but not sure. Looking at the sources of fingerincher from https://www.anyma.ch/2009/research/multitouch-external-for-maxmsp/ this looks to me as an apple exclusive

Re: [PD] [hidraw] pre Deken release. was:(Reading/writing a HID device current best practice?)

On 10/6/22 17:14, Lucas Cordiviola wrote: That would be fantastic. Please let me know when its done. and then there is which is what I use on our CI-infrastructure to codesign Pd-externals. it's not a

Re: [PD] [hidraw] pre Deken release. was:(Reading/writing a HID device current best practice?)

That would be fantastic. Please let me know when its done. -- Mensaje telepatico asistido por maquinas. On 06/10/2022 11:50, Dan Wilcox wrote: You also need to notarize binaries, not just codesign. I am actually working on a Makefile which automates mac-specific distribution stuff like this

Re: [PD] [hidraw] pre Deken release. was:(Reading/writing a HID device current best practice?)

t; Date: Thu, 6 Oct 2022 11:41:43 -0300 > From: Lucas Cordiviola mailto:lucard...@hotmail.com>> > To: William Brent mailto:william.br...@gmail.com>> > Cc: Pd-List mailto:pd-list@lists.iem.at>> > Subject: Re: [PD] [hidraw] pre Deken release. was:(Reading/writing

Re: [PD] [hidraw] pre Deken release. was:(Reading/writing a HID device current best practice?)

Hi William, Thanks for the test. I did an ad-hoc codesign but seems it is not enough. Now I signed with a self certificate:     https://nc.nubegris.com.ar/index.php/s/KL3dF777TPwTkM9 I'm not sure if your mac can test this one as you already got the file in your white list. If you know a

Re: [PD] [hidraw] pre Deken release. was:(Reading/writing a HID device current best practice?)

Amazing, I could only test running it on the M1 itself without any additional equipment, but all seems to work as expected. After going through the 'malicious software stuff' I'm getting data results for devices 4-7. Ech of these report xy coordinate changes on the touchpad. Roughly >250 for

Re: [PD] [hidraw] pre Deken release. was:(Reading/writing a HID device current best practice?)

Hi Lucas - thanks for this! I just tested it on an M1 MacBook Pro under macOS Monterey. I got the "malicious software" warning and had to go to system prefs/security & privacy to allow the external to be run anyway, but then it worked just fine to access my Logitech game controller. On Wed, Oct

Re: [PD] [hidraw] pre Deken release. was:(Reading/writing a HID device current best practice?)

Hi Simon, Interesting! I am away from my M1 for quite a while, might be able to do some testing in a few weeks. Thanks, i need this confirmation. Will [hidraw] also support writing to the device? There are some devices that need 2 way communication to enable/disable functions and states.

Re: [PD] [hidraw] pre Deken release. was:(Reading/writing a HID device current best practice?)

Hi Luca, Interesting! I am away from my M1 for quite a while, might be able to do some testing in a few weeks. Will [hidraw] also support writing to the device? There are some devices that need 2 way communication to enable/disable functions and states. On Wed, 5 Oct 2022, 13:00 Lucas

[PD] [hidraw] pre Deken release. was:(Reading/writing a HID device current best practice?)

Hi all, Next week or so i'll hopefully release hidraw. An object that reads raw bytes from HIDs. Can anyone test this builds on a mac M1 with arm64 or a Monterey x64 intel?     https://nc.nubegris.com.ar/index.php/s/Rk7HRq67eCqF7kQ i'm not sure if i did correctly the code sign. (the object