Hi all,

I'm new to this forum, and pretty new to PD, and was just wondering if anybody might be able to give me some help (possibly in the form of examples) with qlist or textfile sequencing. I have found the help documentation on these objects to be sort of cryptic. This is compounded by the fact that my qlist doc is somehow empty, so I don't know how one should look in order to function properly, or how to send information to "recieve" objects in the patch. Any Feedback or examples of how other people implement these objects into their patches would really be helpful.

Thanks,
jack

Welcome Jack,

Sorry I don't have a good, simple example of [qlist] sequencing to hand. The documentation is terse and to be fair to you [qlist] is not the easiest object to
understand. You have to do a lot of work to "pack" your lists correctly to make
a proper sequencer. Maybe someone else can point you at a good example.

Andy

thanks for the reply, andy.

jack

Hi,

I tried use Qlist long time ago.
NOw I update the patch for you. The purpose is to record 6 data flow incoming and read them after.
http://impala.utopia.free.fr/pd/patchs/QLIST_TEST.zip

I don't know how to use it very well ...

For sequencing the best way seems to be array graphic. A beautiful and simple exemple here :
Null pointer Drum Machine
http://www.nullpointer.co.uk/-/pd.htm

jerome

[qlist] is bad for a number of reasons, the main one is that it doesn't work with local names (starting with $0) because when you save the recorded sequence, there is no guarantee that when you reload the patch it will have the same $0 - and using global names means you can't use it in abstractions.

What I did is make something equivalent using [textfile] when I wanted a "guitar looper pedal" thing for messages - the logic is quite hairy, but it worked when I made it.... You can find it as part of my (ancient) Gravity patch, look for 'eveloop':

http://puredata.info/Members/claudiusmaximus/copyme/gravity/source/

It could easily be stripped down to something much simpler, if you don't need the variable-speed looping functionality.

Another simple way to schedule events to occur in the future (the fundamental basis for a sequencer) is using [pipe] - the original version only allowed single floats to be delayed, but it has since been enhanced to work like [pack] with an extra inlet being the delay time.

Thanks everybody for your help. These examples are going to serve me well (just as soon as I get a chance to study them thoroughly, perhaps over the weekend). Any more examples are most certainly welcome.

thanks,
jack