Copied hjh-abs/ into a student's Documents/pd/Externals folder.

Added Documents/pd/Externals/hjh-abs to the paths.

None of the abstractions in that folder are available ("couldn't create").

cyclone is also installed and in the path -- and there's no problem.

So how should we fix this? I never had this problem with my abstraction folder before.

hjh

@ddw_music A lot of complaints of the same with externals lately.... always on a recent Mac.
What is this students machine /OS?
You could try putting one of the abstractions in the Pd/bin folder. If it is then not found it must be an os security problem?
David.

@whale-av said:

@ddw_music A lot of complaints of the same with externals lately.... always on a recent Mac.
What is this students machine /OS?

It is mac, not sure the version.

You could try putting one of the abstractions in the Pd/bin folder. If it is then not found it must be an os security problem?

I guess I'd have assumed that macOS would treat a text file (.pd) as "just data" and not as an executable that could be quarantined. Also, I tested with a cyclone binary external (play~) and no problem, but the pure-vanilla abstraction failed.

Are there any additional log messages about objects that couldn't be created? "... couldn't create" isn't enough information to troubleshoot this problem. Is it because the file wasn't found? Or was there something wrong in the file? Or permissions...? I can only guess.

hjh

@ddw_music If they were externals I would guess that they installed an old 32-bit (<Pd 048) but as they are abstractions they are simply not being found..... so the path...
I have a vague recollection that you declared the path in patches a few years ago. I wonder whether recent mac's baulk at the hyphen in the path name.
There are quite a few google results for problems with hyphens in filenames from Catalina onwards.... so maybe?... try an underscore instead...?
David.

@ddw_music I'm pretty sure there's an option to display all of the searched paths that get failed trying to load a certain class, if you run pd at higher verbosity. It will be like "tried xxx and failed" or something.
Anyways you could use that to see which paths are being tried

@seb-harmonik.ar said:

@ddw_music I'm pretty sure there's an option to display all of the searched paths that get failed trying to load a certain class, if you run pd at higher verbosity. It will be like "tried xxx and failed" or something.

I tried log level 4 (maximum) and I don't see any such messages.

hjh

@ddw_music He was referring to the startup flags, start it from the terminal with -verbose and see what prints in the terminal. You could also try specifying the library on the command line, might get some extra print out that way if you are lucky. I seem to recall once upon a time getting a vital clue that way.