• jfernandezriverola

    If someone is interested, I ended up with this in order to change patches.
    I'm forcing the quantity of patches to 8, but in the future I'll try to force the length to the number of patches in the folder ( with the [folder_list] object ).

    It's a very simplistic approach, but it's working fine!

    Captura de pantalla 2016-08-07 a las 12.45.42.png

    posted in technical issues read more
  • jfernandezriverola

    @jancsika said:

    @whale-av

    @whale-av and @jancsika thank you very much.

    The problem I was having with pd open is that I was trying to make it work with the relative path.
    I see in the docs you show that "usually you don't get it to work with relative paths".. and that's right, once you try it with ABSOLUTE path it's working nicely.

    THANK YOU BOTH for the quick answers, what an awesome forum and community.

    posted in technical issues read more
  • jfernandezriverola

    I'm experimenting right now with: [openpatch] / [opa] but failing anyway...
    It sounds like exactly the thing I need but I can't make it work.

    My folder structure:
    Captura de pantalla 2016-08-05 a las 21.09.06.png

    My pure data code:
    Captura de pantalla 2016-08-05 a las 21.08.35.png

    And still does not open..

    posted in technical issues read more
  • jfernandezriverola

    @jancsika thanks for the quick answer!

    Several reasons:

    • Using [switch~] implies to slightly modify every (third party) patch that I want to use. I'd prefer to use them as is, and simply put them on a folder.
    • As i understood, if load let's say 20 patches with switch to off, it'll consume less cpu but will still be consuming some anyway. Is that right?
    • I don't mind to interrupt the audio engine every time I want to open / close patch . The open and patch close is an analogy for changing a "Preset" on a synthesizer, so it's ok I won't be emitting audio in between preset changes.
    • Keep in mind that the mother patch will alway be loaded, i want to open close only the "child pure data patches" ( ore 'presets' ).

    What do you think?

    THANKS!

    posted in technical issues read more
  • jfernandezriverola

    HI!

    Quick version:

    My folder structure:
    /mother-patch.pd ( main pure data patch first loaded and running... )
    /patches/1/main.pd
    /patches/2/main.pd
    /patches/3/main.pd
    ...

    How i could open /patches/1/main.pd triggered by some action in the mother-patch.pd?
    How i could close /patches/1/main.pd triggered by some action in the mother-patch.pd?

    Long read

    I'm attempting to clone the Critter and Guitari organelle ( link ).
    This instrument is basically a computer running libpd and running very cool pure data patches
    You can read more about my project here ( link )

    I have a mother pure data patch that it's first loaded when the device is on, this patch is doing some [send] and [receive] operations related to the knobs/keyboard/volume/led and it should be also managing the loading ( opening and closing ) of the child pure data patches ( mentioned above ). This child patches are receiving the actions from the mother patch.

    If I open the mother patch and the child patches manually, everything works fine. But now I need to OPEN this CHILD PURE DATA patches with a object within the mother patch.

    I've been testing [open] , for opening the main.pd of the child patches but it does not work.
    I've been testing [pd] , for opening the main.pd of the child patches but it does not work.
    I wouldn't like to modify the original organelle patches.
    I wouldn't like to end up loading all the patches using [pd ...] and inserting a [switch] object inside every main.pd file in the patches in order to enable only the dsp of the desired patch.

    It would be perfect If i could have a folder with all the patches and load them within the mother patch with some kind of object. And I would also want to be able to CLOSE the pure data patch and open another ( changing patches... )

    Every little and big help woul be MUCH APRECIATED!

    THANKS!!!!!!!

    posted in technical issues read more

Internal error.

Oops! Looks like something went wrong!