VST works but standalone doesn't about plugdata HOT 16 CLOSED

Thanks for testing and reporting! I will investigate this soon, I'm on Monterey on M1 myself so I'm surprised it doesn't work. Possibly it can't initialise because it's not allowed to access the filesystem? If you could build and debug in Xcode and tell me where it hangs, that would help a lot!

from plugdata.

I'm happy to try the Xcode thing. What project do I load into Xcode?

from plugdata.

I'm able to reproduce the hanging standalone issue by running it on another MacBook, so I think I'll be able to figure it out! I'll also try running the VST in Bitwig, I've currently tested it mostly in Reaper and Logic.

If you want to investigate it in Xcode, I'd recommend running

cmake -DCMAKE_BUILD_TYPE=Debug -G Xcode ..

Then open the generated project and run the Standalone.

from plugdata.

I'm running cmake -DCMAKE_BUILD_TYPE=Debug -G Xcode .. from the Build folder, and getting this message...

CMake Error: Error: generator : Xcode
Does not match the generator used previously: Unix Makefiles
Either remove the CMakeCache.txt file and CMakeFiles directory or choose a different binary directory.

Any ideas?

from plugdata.

Oh sorry, forgot to mention, you need to empty out the build folder first.

from plugdata.

All I'm getting when I try to debug PlugData is this small message...

from plugdata.

I'm a little out of my depth here. Perhaps I'll let you carry on with this, as you seem to know what you are doing 😉

from plugdata.

Thanks for the information, I think I can figure it out from here! I'll let you know when it's fixed

from plugdata.

Cool! Thanks for your help, and thanks for the app itself.

You know I mentioned the VST crashing. It's done it again. I got these two Bitwig messages. It seems to happen after a period of zero activity after about 15 minutes or so.

from plugdata.

That's useful, I'll try to replicate this. Looks like a deadlock...

The other bug is also caused by some sort of deadlock immediately after starting up, which is strange. It doesn't happen in an older version so it should be fixable.

from plugdata.

I think I solved the standalone issue! It was caused by the audio settings dialog trying to load before the audio was ready. Could you pull the changed and see if it works now?

from plugdata.

I've also found the reason for the crashes in Bitwig, the same thing happened in some other DAWs. It should be fixed now, if you can confirm it I'll close the issue.

from plugdata.

Sorry for the delay. I've rebuilt everything and the Standalone and the VST all seem to work.
However, one slight change has occurred which may be my mistake, but I don't know. I tried to recreate the second of the example screenshots. When I did this last night, the app worked and appeared to respond to Mouse Move events. Now, when I do this it is responding to Mouse Down and Mouse Up click events. here is the pd,,,

#N canvas 827 239 527 327 12;
#X obj 93 41 mouse;
#X obj 58 114 changed;
#X obj 80 176 print Hello World;
#X connect 0 0 1 0;
#X connect 1 0 2 0;

As far as I can tell, this is exactly the same test script that I created last night.
Your thoughts?

from plugdata.

Aha! It was my mistake. Last night I had the cable connected to the middle port of the mouse object, whereas just now I used the left hand port. Time for me to RTFM, I think 😉

from plugdata.

Thanks for reporting these bugs, it would've taken me a while to find them myself!

from plugdata.

Thanks for putting the package together! It adds yet another string to my bow 😉

from plugdata.