hi ,
i was just curious if there was an object available that is capable of reading in midi files on the windows platform ..
joge .
hi joge,
try xeq. If in trouble, send me a note off the list (with a hint how could I reach you -- it seems like my server is blacklisted at your site?)
Krzysztof
joge . wrote: ...
i was just curious if there was an object available that is capable of reading in midi files on the windows platform ..
hi Krzysztof ,
thank you much for this object !! its exactly what i am looking for .. however i am bit confused as to how to use it . i have been reading the online documentation you have for each object and i've looked at the examples posted online also . however i am still not quite getting how to use the objects , are there any help patches available ?
i am basically looking for a way to record and play back midi files . i would be recording from a midi keyboard into a file [would this file be able to be opened in nuendo or some similar sequencing file ] ... then i would be playing back the midi file for use with the vst~ object running pro-52 , all the while dynamically influencing the values that are coming from the midi file . its my initial experiment into algorithmic composition of sorts .
thanks !
joge . ----- Original Message ----- From: "Krzysztof Czaja" czaja@chopin.edu.pl To: pd-list@iem.kug.ac.at Sent: Wednesday, March 27, 2002 3:50 AM Subject: Re: [PD] object to read in midi files .
hi joge,
try xeq. If in trouble, send me a note off the list (with a hint how could I reach you -- it seems like my server is blacklisted at your site?)
Krzysztof
joge . wrote: ...
i was just curious if there was an object available that is capable of reading in midi files on the windows platform ..
hi joge,
indeed, I am so lazy... Have you tried using mfread', and
mfwrite'
messages? They may be applied to any host, also to [xeq_record].
What is puzzling? Maybe the host and friends' thing? The idea is to be possible to load (record, construct) a sequence once, and then to trigger multiple players for that sequence, each with a separate set of playback parameters (tempo, transposition, looping, etc). It is like using a single [delwrite~] (a delay line
host'), and
multiple [delread~]s or [vd~]s (`players').
Otherwise, I think, all the main object classes are documented, their inputs, and outputs alike. Playback is as easy, as connecting a proper [xeq_parse]'s outlet to a [noteout] (and/or [ctlout], etc). Or connecting middle outlet of [xeq] (also of [xeq_record]) to a [midiout]. Recording may be trickier, because it is meant to be more general, than just midi recording. Have a look at the help patch for [xeq_record].
Krzysztof
p.s. I am sending this through the list, not being able to reach joge directly, sorry! And I am going to go off-line until around tuesday, sorry again...
joge . wrote: ...
however i am bit confused as to how to use it . i have been reading the online documentation you have for each object and i've looked at the examples posted online also . however i am still not quite getting how to use the objects , are there any help patches available ?
#N canvas 358 224 506 282 12; #X obj 92 45 notein; #X obj 92 194 xeq_record x; #X obj 92 91 pack 0 0 0; #X msg 275 133 record; #X msg 362 45 bang; #X msg 225 45 rewind , flush; #X msg 33 194 edit; #X obj 362 133 noteout; #X msg 277 173 restop; #X obj 362 91 xeq_parse x; #X msg 92 133 readd 144 $1 $2 $3; #X connect 0 0 2 0; #X connect 0 0 7 0; #X connect 0 1 2 1; #X connect 0 1 7 1; #X connect 0 2 2 2; #X connect 2 0 10 0; #X connect 3 0 1 0; #X connect 4 0 9 0; #X connect 5 0 9 0; #X connect 6 0 1 0; #X connect 8 0 1 0; #X connect 8 0 5 0; #X connect 9 0 7 0; #X connect 10 0 1 0;