Hello -
When I double-click on a .pd file in OSX or Linux, it will open a new instance if none is running, and any subsequent files are opened in the same instance. In Windows, every time I open a file from explorer, it launches a new instance.
Is there any way to stop this, and make it behave as it does on other platforms?
thanks!
Paul

@forty-2 I don't have this problem and I have not seen anyone else raise an issue.
I would take a look at the file associations for Windows.
In my associations the .pd extension shows the wish application as the default program.
If it shows Pd.exe that could be the problem?
Otherwise (for other programs) a registry problem or a remote user logon have been mentioned.
David.

@forty-2 I remember this behavior from some previous version of PD on Windows, but I don't remember if it was the same on MacOS. What version are you running now?

@jameslo - I'm on the latest version .50-2. Mac hasn't launched new instances for as long as I can remember. Linux I'm not sure, I feel like I've seen it go either way.

@whale-av - Mine had Pd as the default application. I changed it to Wish, but it behaved the same. Same thing as doing a right-click 'open with': Both Pd & Wish will launch a new instance.

My registry entries all seem pretty straightforward, but I think I'm just going to nuke them all and try a fresh install.

unrelated - any reason to consider 64 Bit over 32 Bit versions or vice versa? I'm on a 64 Bit OS, but can't imagine a scenario where I'd need more than 4GB for PD.

@forty-2 I can confirm the issue with PD 0.50.2 64bit / Windows 10. I think with older PD versions too, but I was not bothering too much.

@jona - interesting, thanks. I was going to try 32 bit just for kicks. In that case, I have to use Deken to re-download any externals that use compiled dlls, right?

I can confirm 32 Bit does not have the same issue. I've moved my old externals into a 64 bit folder, in case I decide to go back.
weird...
thanks!

@forty-2 I also am using PD 0.50.2 64bit / Windows 10 but am not seeing this issue. I thought it was version specific but apparently not.

I'm still hoping someone comments on your 64 vs 32 bit question though. I was hoping that 64 bit meant double-precision floats, but apparently that's not a light undertaking.

Well now I'm having all sorts of trouble getting externals working. Gem is throwing errors, some parts of iemlib are missing, or just not working.
.. I'm re-installing them using deken, so they should be the 32 bit versions. Maybe I'll try deleting all those registry entries again and give the 64 bit another go?

@forty-2 Now it is working correctly for me, it seems it was because an older PD version was not uninstalled correctly... If you install a 32 bit version, i would specify a different externals folder, but I think the only advantage is that you can run it on a 32bit os (and use 32-bit compiled externals).

@jona I did another wipe of the registry and a fresh install of the 64 bit, and I'm no longer having this issue. I wish I knew what actually caused it, because I hate when a re-install magically fixes things, but here we are...

@forty-2 That's good news. All Vanilla versions from 0.48 store their registry settings in the same place. Another place up to 0.47. Extended used a very different location.
Unfortunately when shared the path and lib settings are also shared so Pd can go looking for binaries from other versions that are not 32/64 bit compatible with the version that was just opened.
David.