Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

first Pd patch (ai_duet) does not open #8

Open
yannseznec opened this issue Oct 1, 2021 · 11 comments
Open

first Pd patch (ai_duet) does not open #8

yannseznec opened this issue Oct 1, 2021 · 11 comments

Comments

@yannseznec
Copy link

I'm running a new MacBook Pro M1, macOS 11.6, Pd 0.51.4.

I'm almost certain that I've followed all of the setup correctly, resulting in a build of pyext that is installed in my Pd externals directory. When I launch Pd I see the messages in the Pd window indicated that pyext (and zexy) has loaded without errors.

magenta has also been installed and seems to be activating properly.

I have downloaded the pretrained models, but when I launch ai_duet.pd the patch will not open in Pd. It will sometimes crash Pd too, though not consistently. I'm not sure where the problem is coming from.

The only differences I'm seeing between my setup and the information in the docs is that I'm running Pd 0.51.4 (instead of 0.51.3) and I'm using Python 3.7.11 (instead of 3.7.10).

I recognise that this may not be enough info to go on, but...any ideas?

@yannseznec
Copy link
Author

slight update: the issue is not just with the first Pd patch, I've just tried opening some of the other patches and they also won't load - I just tried nsynth.pd and nsynthosc.pd, for example, and they didn't work either.

also, if it's any clue, I'm doing this on a work computer that is managed by a superuser. I have admin privileges but I don't know if there's some chance that some things could be getting blocked...however I feel like I would not have been able to build pyext and install conda if that were the case.

@SopiMlab
Copy link
Owner

SopiMlab commented Oct 4, 2021 via email

@yannseznec
Copy link
Author

Excellent, thanks - yes I'm pretty certain that pyext is all set up correctly, here's a screenshot of the Pd window when I start up.

Screenshot 2021-10-05 at 09 33 32

@ahihi
Copy link
Contributor

ahihi commented Oct 5, 2021

hi,

just wanted to note that we don't currently have access to M1 macs, and so this code has only been tested on Intel. i'm pretty sure the codebase still has some memory related bugs and it's possible those are more fatal on the M1, or that there's some other kind of compatibility issue. if you're comfortable with debugging tools like Valgrind, it would be really interesting to find out where things are going wrong. but other than that i'm afraid i can't be of much help at the moment.

@yannseznec
Copy link
Author

hmmm ok, so currently there are two big unknowns:

  • is this due to the M1 chip?
  • is this due to my computer being managed by my university, despite me having admin privileges. perhaps the communication between Pd and Python is being blocked?

There are certainly a number of other possible issues, but if anyone can shed any light on those two ideas that would be great.

@ahihi
Copy link
Contributor

ahihi commented Oct 6, 2021

the second case seems unlikely to me - i'd imagine any such restriction would break a lot of other things too.

some things you could try to maybe narrow down the issue:

  • see if you can open any of the pyext example patches, e.g. simple-1.pd (you'll probably have to move the python files from scripts into pd where the patches are)
  • if not, what happens if you create a new patch and add a simple py object like pym 2 +? are you able to compute with it? (send a number to inlets 2 and 3, then a bang to inlet 1 and check what comes out of outlet 1)

@yannseznec
Copy link
Author

I hadn't noticed the pyext example patches, thanks for that - I can't seem to get any of them to work - I get an error message in the pd window saying "pyext simple ex1 ....couldn't create"

this is a bit confusing, as the Pd window says it is loading the py/pyext 0.2.2 library on startup! however, it's certainly a good sign in terms of tracking down the issue. perhaps I didn't build the objects correctly after all!

on the other hand, the [pym] object seems to work fine, it loads and I am able to do the simple addition like you described.

@ahihi
Copy link
Contributor

ahihi commented Oct 6, 2021

is there any information before the "couldn't create"? usually you should get a slightly more specific error message.

@yannseznec
Copy link
Author

oh yes you're right:
ModuleNotFoundError: No module named 'simple'
Screenshot 2021-10-06 at 16 00 09

@ahihi
Copy link
Contributor

ahihi commented Oct 6, 2021

this sounds like it can't find the simple.py file, hence:

you'll probably have to move the python files from scripts into pd where the patches are

@yannseznec
Copy link
Author

oh gosh my apologies, I totally overlooked that.

when I move the scripts into the same folder where the patches are, there is some "progress" - the patch does not launch at all. it exhibits the same behaviour as when I try to launch the ai_duet patch as described originally, it just quietly hangs without a spinning wheel or anything, and a patch window never opens up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants