Sharedmemory In/Out CHOP - Not working in Local mode - MAC Sequoia - 2023.12120

Sharedmemory CHOP in local mode doesnt seem to work in local mode. When switched to global it works.

I use this in my system in multi process context on a single computer sending audio ch and also control value ch from one TD process to an other, in some cases used also within the same process during dev / or to make system components read the same memory instead of direct wireing to get closer timing.

Best,
Pete

Hi Pete - I can’t immediately recreate this issue here.

Can you let us know the exact macOS version and Mac model?
Do you see a warning on the Shared Memory In CHOP saying the segment can’t be found, or some other problem?
Could you share a simple project which reproduces the issue for you?

Thanks

@bangnoise
Hey Tom,

When starting from blank and also with fresh mind just now, SM in/out worked also in local.
Loading the big system still didnt, only in global mode. No errors showns, just blank black node on the In side.

I went ahead and removed the nodes and re inserted them as new, this way worked. Appologies i should have done this, somehow lacked the freshness to think all possible steps through.

Process leading to the problem was: Moving entire project from PC to MAC, also upgrading from 2023.12000 → 2023.12120 ( both machines ). Win machine logic and network remained working, on mac this issue came up and at that state and hour i somehow missed the full recreation of these nodes…

Question: how is the state of operator nodes saved in the .toe or .tox files? Could the OS migration play a role? Could any other nodes be affected ? ( a good portion of my custom comps I create dynamically via scripting, but based on templates existing in the network or externalised out as .tox) does anything relate to OS? ( i suspect maybe yes )

Other aspect i can think of is the version change up. And its combination to the above question :slight_smile:

Mac Os: 15.1 (24B2083), Machine: Apple M4 Max, macbook pro, 64 GB, 2TB
Win 11 Home, Lenovo Legion i7, rtx4090, 64Gb

So to sum up, when starting from fresh it works. When starting from the migrated .toe it doesn’t, recreating from fresh makes it work, saving and reloading the project keeps working.

At this point im curious what other parts / nodes I should investigate closely in the system. ( its a larger shared system, and the multi ch audio playback of the system is planned to run on mac, while the rest across PC servers.

Thanks a lot,
Pete

Thanks for the details and further info.

Neither the TouchDesigner version change (especially such a small one) nor the move from Windows to Mac should have made a difference. The only case where moving OS would make a difference would be for a few nodes which don’t work on Mac (eg Nvidia-specific ones) - and those would result in warnings.

Could you send the non-working .toe to support@derivative.ca and reference this forum thread? Hopefully we can identify the issue.

Hey Tom,

Sure absolutely. I will attempt to walk through the process with a minimesed isolated .toe first to see if I can reproduce with only the relevant nodes and sample folder assets used… will report here back too so everyone can see.

1 Like