@ben.wes Does OSX have /proc/ or something like it where devices can be written too? Would mean you can just use [command] to write to the appropriate file. Or perhaps OSX has a command for this which you can run from [command]? Have not used OSX to any real extent since 10.2 so no idea how far it has strayed from its BSD roots.

@cfry The simple hack to make this work on both in linux and OSX.
logger4.pd
Not completely sure the output of uname on OSX will be Darwin, if it does not work open up a terminal and run uname, what ever the output is is what you want to be the symbol in the [route]. And make sure to fix that path. You can also shorten that [del 1000], should be able to be dropped to at least 100.

The one fault with this is that killall tee is not great, it is possible there could be some other instance of tee running somewhere else and killall does kill all within the users permissions. OSX's paranoia might save you here, pd may not be able to kill apps which it did not start, depends on how they set things up. It is fairly safe as long as you do run pd as root and do not start any scripts running before sending that bang. Personally I would not worry about it until it bit me, I abuse killall to save having to get pids and it has only bitten me a few times in 20 years and never on something as innocuous as tee. If you are feeling paranoid or curious you can run tee in a terminal and then bang that right inlet to see if it kills the instance running in the terminal. We can make this safe with a few more [command]s if you want, need to rework a command like ps -f | grep "tee -a <log file name>" into playing well with [command], grab the pid and then run kill on that pid,

@oid said:

Did you ever try using the full path to pdreceive as mentioned above,

Sweet, It works with the full path! I thought I tried it several times, hmm. And no error code. The right "error" outlet does send out listening on 3000 but it works anyhow.

I changed permissions: chmod a+rwx pdreceive but still didn't work without full path.

then I did this and noticed the com.apple.quarantine flag:

jnl@nmbp bin % ls -@l pdreceive
-rwxrwxrwx@ 1 jnl  admin  174048  3 Jul 18:11 pdreceive
    com.apple.lastuseddate#PS       16 
    com.apple.quarantine        57 
jnl@nmbp bin % xattr -d com.apple.quarantine pdreceive 
jnl@nmbp bin % ls -@l pdreceive                       
-rwxrwxrwx@ 1 jnl  admin  174048  3 Jul 18:11 pdreceive
    com.apple.lastuseddate#PS       16 
jnl@nmbp bin % 

The com.apple.quarantine flag is added on downloaded apps by osx, preventing them to run without confirmation.

Removed the flag but it still does not work. I have to read up a bit on osx security. Its close though.

@oid said:

But there could be an Applications directory in root for apps available to all users these days, once again my lack of knowledge regarding modern OSX.

that's how it is structured nowadays yes.

@cfry said:

what does the "2" exit code indicate?

Assuming OSX sticks to standard error codes it means that [command] is not finding pdreceive. Did you ever try using the full path to pdreceive as mentioned above, [exec /Applications/Pd-0.53-2.app/Contents/Resources/bin/pdreceive 3000(? My guess is that OSX does not allow programs to execute user path as a security measure so even full path may not work. There is some sort of permissions thing you likely need to do but I have not used OSX since long before their modern permissions setup. If full path does not solve the issue then we need one of the more OSX experienced users to chime in.

Edit: If using the full path throws an exit code of 1 we can be fairly confident of it being a permissions thing, 1 is operation not permitted. If it works it is just a path thing. Either should make it simple enough to find the solution.

Another edit: make sure /Applications/Pd-0.53-2.app/Contents/Resources/bin/pdreceive is actually the full path, back when I last used OSX the Applications directory was always in the user home directory so the full path would be /home/user name/Applications/... But there could be an Applications directory in root for apps available to all users these days, once again my lack of knowledge regarding modern OSX.

@Riccardo-V Yes.... your patch is not causing the problem.
There are issues with coreaudio in Ventura 13.0....... https://community.roonlabs.com/t/strange-audio-issues-w-ventura-roon-investigating-known-apple-issues-w-ventura-system-audio/222113/24 .... see posts from Dec 1 onwards.
Try the latest Ventura 13.1 update.
Then reset coreaudio if necessary (probably not).
Or downgrade OSX.... I think you need all data backed up to do that successfully.

Ignore the following if the OSX upgrade/downgrade solves the problem.
I suggest building the Pd app for your OS and system from the source code.... here...... https://puredata.info/downloads/pure-data/releases/0.53-0
I don't use OSX much (still Snow Leopard when needed) but I believe it is a simple procedure.
As far as I know.... unzip the tar.gz file.
Navigate to the folder in a terminal window.
Type "make" and press enter,
It only builds a Pd app tailored to your system..... it doesn't change any other files.
If it doesn't work then at least you will get messages to the terminal telling you why...... something missing or incompatible.
David.

You can find all my pd externals here: https://github.com/myQwil/pdxtra

I wasn't able to build for OSX, but only because the environment I use for OSX builds is really old and out-dated, and I was not able to do a brew install of ffmpeg. For anyone with a more up-to-date version of OSX, they should be able to build it by installing ffmpeg and running make

As for Windows, I did a 64-bit build (m_amd64), but not 32-bit. I came across an issue when attempting to build for 32-bit, though I can't recall at the moment what the exact issue was.

@JMC64 On linux and OSX you can use [ggee/shell] to handle the clipboard, here is a quick abstraction, will combine with most of the text box solutions mentioned and simple to assign it a key combination if you want that. Just bang it's input to get the clipboard. On linux xsel or xclip may need to be installed, not all flavors of linux come with one of them. Neither the xclip method or the OSX pbpaste method have been tested by me but should work, I have not used OSX in a good while and my xclip seems to have an issues with erratic output which I don't care enough to sort out at this time. There is probably a way to extend this to windows as well, but no clue.

cbget.pd

Edit, got rid of the rather pointless [metro].

I compiled TheTechnobear's mutable instruments externals and made some slightly better helpfiles from the info in orac plugin descriptions and source.
so far only compiled for osx:
Mi4Pd-OSX-x86_64.zip

@60hz I replied in the bug report, but basically the event loop handling is supposed to be much more stable and improved on modern macos with 8.6.11 from my understanding. For instance, 8.6.10 required patching to get the scrollbars to show up on newer osx (also this is why there are 2 different releases for osx on miller's site I think). The patch was kind of hacked out of 8.6.11 which changed the architecture of its event handling since 8.6.10.

I noticed the bug you mentioned in an earlier release with tk 8.6.10, and the fix was actually merged into main pd vanilla. I cannot reproduce on osx 10.14.6 so unfortunately I'm not sure how to go about fixing it..

as for the ceammc bug, it is an issue with tk 8.6.11 with the ttk "alt" theme and has to be fixed in either ceammc or tk.
However you can still package w/8.6.10, I suppose I can upload a version using it instead if it makes that big of a difference..

@Butahuruf There is a plugin....... put it in a pd search path...... https://puredata.info/downloads/fullscreen-plugin/releases/0.1.20101207
You lose the menu though so it depends on what you want it for.
Press F11 to toggle full screen.
If you need the menu it will have to be modified but most menu items have shortcuts.
It is probably possible to modify it so that it starts a patch in fullscreen.
Remove it from the search path to go back to normal.

You have to open the patch from Pd first....... if you open Pd by double-clicking a patch then it doesn't work.
David.