• smccusker

    hey, ive been writing a patch that will allow me to create and instansiate any number of abstractions, each with unique varibles so as each instance of the abstraction will run independantly, but ive hit a problem. I'm using message objects filled with the code from the original abstraction to instansiate it (much like an example in the extended documentation dealing with messages to pd).
    its working fine, except that it creates the abstraction in a temporary space.
    i want to add a line or two of code to the original message that will direct the newly created abstraction to a fixed location, with a unique name, and then call pd to then place an instance of that abstraction into the existing patch. does this make sense?
    if anyone has a detailed knowlege of the pd commandlines and so forth i would really appreciate some help.
    thanks, sam

    posted in technical issues read more
  • smccusker

    [inlet]
    |
    [ f ]X[+ 2]
    |
    [outlet]

    posted in technical issues read more
  • smccusker

    thanks for the reply
    how would i go about directing pd to create the new object in a subpatch?
    something like this? (appologies for the crude diagram)

    [message which creates object( [pd subpatch]
    |
    |


    is this what you meant?

    posted in technical issues read more
  • smccusker

    thanks for the reply,
    by my understanding of your post, i think our ideas are quite similar. My patch has a global counter which assigns a number for the creation argument of the abstraction, so that when created, the array and any related objects will all be given a name/assignment of sample1 or sample2 etc. when the next abstraction is created, the global counter will then send the next sequential number, sample2, sample3 etc.

    that part is working fine, the problem lies in that every instance of the abstraction that i create has been created in a cache somewhere, which i can only assume isn't on the scratch disc (since a search for the file yeilded no results), what i want to do is add a few lines to the creation code that will tell pd (much in the same way that it tells it to create a new abstraction, fill it, and open it) to save the file to a set location, with a unique name, and then create an instance of it on the original canvas, so that it can be used.
    i have also written a simple delay loop object, and another patch based on a vst plugin that i use with audiomulch that overides the buffersize and samplesize of the soundcard which i would like to be able to create any number of.
    Essentially my goal is to create a patch which, when opened, is blank save for a few message boxes, which when clicked will create my abstractions so that any number of instances can be linked together in any combination.
    anyway, i hope that my reply was clear enough, and that you might be able to help me.
    thanks
    -sam

    posted in technical issues read more
  • smccusker

    sorry, i should add that this is to be used with a loop playing abstraction that i have written, and my aim is to be able to click and instantly create a new instance of the loop abstraction, with a unique table name and object calls so that more than one loop player will play different samples simaltaneously.

    i could always manually change the name of each table and so forth, but thats boring.

    cheers

    posted in technical issues read more

Internal error.

Oops! Looks like something went wrong!