• plusch

    @timothyschoen Thanks for the great work! I tried it with Bitwig 3.2.8 on Windows 10, opened a patch and heard sound.

    Some observations:

    Selecting help from the right-click menu worked on some objects, but not others. For example, list and netreceive showed the help file, but metro and phasor~ gave message "Couldn't find help file."

    Arrays were retained in my opened patch, but editing the values with the mouse was inconsistent, sometimes values would move to the cursor position and then jump back to their previous position. One array showed the dots for values and the other showed nothing but seemed to have correct values being played. Names of the arrays weren't shown, and I couldn't find a way to edit the array properties.

    I probably shouldn't expect to receive OSC data from my Android phone, but I tried sending a "listen 8000" message to netreceive and got the error "netreceive: listen failed: The operation completed successfully."

    I find this an exciting project and hope it continues to develop.

    posted in news read more
  • plusch

    @whale-av Thanks for the detailed write-up. I will refer to it as I try to think of a coherent process for managing and using externals so that the help files will open without "couldn't create" errors.

    posted in technical issues read more
  • plusch

    @alexandros: Ah, I misunderstood you. When you originally referred to Pd/externals, I thought "Pd" meant the folder where the Pd program was installed.

    My OS is Windows 10.

    The defaults in File > Preferences > Path are
    Pd Documents Directory: C:/Users/paul/Documents/Pd
    Externals Install Directory: C:/Users/paul/Documents/Pd/externals

    But because I was running low on space on my C drive, I had changed mine to
    Pd Documents Directory: F:/Pd_patches
    Externals Install Directory: F:/Program Files/Pd_externals

    So I think you're saying that those directories on my F drive should be acceptable. Is that correct?

    posted in technical issues read more
  • plusch

    Thanks, Alexandros, your recommendation worked. I removed cyclone from the Pd search path and moved the cyclone folder into the Pd/extra folder. (There is no externals folder in my Pd installation, but there is an extra folder containing things like bob~ and bonk~.) Now I can create [cyclone/avg~] (and even simply [avg~]), and its help file looks as it should, without errors.

    I had previously saved externals to a separate folder outside of the Pd installation, but I'm inferring that's not a good thing to do. So I'm in the process of moving them all into Pd/extra and removing them from the Pd search path.

    As noted elsewhere on this forum, a confusing thing is that different externals seem to have different ways to gain access to their objects. It's not clear when a declare object is needed or which flag should be used on it.

    Now I'm testing the chaos external. I can create {chaos/base3], for example, but when I open its help file, I get "couldn't create" errors. Different variations of the declare object didn't seem to help.

    posted in technical issues read more
  • plusch

    Forgot to mention that this is on Windows 10.

    posted in technical issues read more
  • plusch

    I installed Cyclone with Deken, added it to the path, and set it as a startup library. In a new patch, I can create Cyclone objects successfully. But when I right-click on an object and choose Help, I get "couldn't create" errors in the console.

    As an example, I successfully created an avg~ object. When I open its Help, I see "couldn't create" errors for cyclone/avg~, cyclone/train~ 200, four cyclone/comments, cyclone/scope~, and cyclone/setdsp~.

    Any idea why this happens?

    posted in technical issues read more
  • plusch

    Hi, all

    I'd like to share this piece. Its source audio was made with a generative Pd patch that I constructed.


    posted in output~ read more

Internal error.

Oops! Looks like something went wrong!