Re: [PD] midifile object
Alex wrote: I made my own little help file which pulls the messages apart a little bit more.. I've attached it. Thanks, Alex, I just merged that into the midifile-help patch in svn. I just added a subtract 8192 from the pitch bend value to get the right value. Martin ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] midifile object
danomatika wrote: I made some objects to mimic notein, ctlin, pgmin using a stream from midiin/midifile, mabey someone finds them useful? Looks interesting, but it's missing [rc-filename]... Martin ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] midifile object
Hallo, Martin Peach hat gesagt: // Martin Peach wrote: > Frank Barknecht wrote: >> Hallo, >> Frank Barknecht hat gesagt: // Frank Barknecht wrote: >> >>> Here's what c_seqplay deals with: >>> >>> 144 + channel = note on; >>> 128 + channel = note off; >> >> Whoops: I just spotted a documentation bug here! It's reverse of course: >> >> 128 + channel = note on; >> 144 + channel = note off; > > No, you had it right the first time...128 is off. Ah, damn. :) Well, then it's worse: The patch is wrong, not the doc. Will fix ASAP. Ciao -- Frank ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] midifile object
I made my own little help file which pulls the messages apart a little bit more.. I've attached it. -Alex On Wed, Jul 8, 2009 at 1:04 PM, Martin Peach wrote: > Frank Barknecht wrote: >> >> Hallo, >> Frank Barknecht hat gesagt: // Frank Barknecht wrote: >> >>> Here's what c_seqplay deals with: >>> >>> 144 + channel = note on; >>> 128 + channel = note off; >> >> Whoops: I just spotted a documentation bug here! It's reverse of course: >> >> 128 + channel = note on; >> 144 + channel = note off; >> > > No, you had it right the first time...128 is off. > > Martin > > ___ > Pd-list@iem.at mailing list > UNSUBSCRIBE and account-management -> > http://lists.puredata.info/listinfo/pd-list > midifile-help-x37v.pd Description: application/puredata ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] midifile object
Frank Barknecht wrote: Hallo, Frank Barknecht hat gesagt: // Frank Barknecht wrote: Here's what c_seqplay deals with: 144 + channel = note on; 128 + channel = note off; Whoops: I just spotted a documentation bug here! It's reverse of course: 128 + channel = note on; 144 + channel = note off; No, you had it right the first time...128 is off. Martin ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] midifile object
Andres Ferrari wrote: hello, the martin peach's object midifile has 3 outlets, the first outlet output a list with 3 numbers: xxx,note,velocity what is xxx ??? It's the MIDI status byte. For example the "note on" status on channel 1 is 144 (hex 90). Channel 2 would be 145, etc. See for example: http://www.ibiblio.org/emusic-l/info-docs-FAQs/MIDI-doc/MIDI-Statusbytes.txt Martin ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] midifile object
Hallo, Frank Barknecht hat gesagt: // Frank Barknecht wrote: > Here's what c_seqplay deals with: > > 144 + channel = note on; > 128 + channel = note off; Whoops: I just spotted a documentation bug here! It's reverse of course: 128 + channel = note on; 144 + channel = note off; Ciao -- Frank ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] midifile object
Hallo, Andres Ferrari hat gesagt: // Andres Ferrari wrote: > the martin peach's object midifile has 3 outlets, > > the first outlet output a list with 3 numbers: > > xxx,note,velocity > > what is xxx ??? [midifile] is pretty funky as is the [seq] object in Cyclone/Max: "xxx" is the midi command byte that specifies how to interpret the rest of the list and the channel. So your "note" and "velocity" need not be note and velocity, they could also be cc-messages or pitchwheel data or whatever. You can read up the midi spec somewhere on the web, but here's a quick rundown: If "xxx" is between 128 and 143, the message is a noteon message. Substract 128 from "xxx" and you get the channel. Example: "140 80 100" would be a noteon message on channel 140-128=12 with pitch 80 and velocity 100. noteoff messages start at 144, CC messages use a midi command byte between 176 and 191, so a message "177 ..." would be a CC message on channel 1 (= 177-176) This format is used both in [midifile] and in [seq], but seq gives the list as a number sequence which is tricky to parse (except with [midiparse]) The rj library for the Pd vanilla as used in RjDj includes a [c_seqplay] object that converts the textfiles which [seq] writes when opening a midi file and saving it with a *.txt suffix to a [qlist] capable format and plays back these files while tagging them according to the midi commands. So e.g. the message "140 80 100" from above would be converted to "12 noteon 80 100" and send to the outlet of c_seqplay. Here's what c_seqplay deals with: 144 + channel = note on; 128 + channel = note off; 176 + channel = cc; 192 + channel = pgm change; 224 + channel = pitch wheel; 160 + channel = polypressure; All in all [c_seqplay] is a nice vanilla way to play back midi sequences, provided you have access to a Pd with [seq] to convert the files to textfile in advance. If you want, you can grab the respective code from here: http://trac.rjdj.me/browser/trunk/rjlib/rj Ciao -- Frank ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] midifile object
I think you're thinking about a different thread, here he is talking about the midifile object where he specifically mentions notes. I haven't used the midifile object though so i'm simply guessing based on the message: xxx, note value, velocity which he mentioned -Alex On Wed, Jul 8, 2009 at 11:34 AM, Lao Yu wrote: > sysex has no channel being a system and not a channel message, as far as I > know. The first value should by in hex 'f0' meaning start of sysex. the 2nd > byte which in some software appears at the channel# is the manufacturer id > ($01 for sequential circuits, $04 for Moog, $11 for Apple, for example). > but it is all on the MIDI site, no? > > Best > Jurgen > > On Jul 9, 2009, at 2:06 AM, Alex wrote: > >> I'm not 100% but if I were to guess I'd say xxx would be midi channel. >> >> -Alex >> >> On Wed, Jul 8, 2009 at 10:54 AM, Andres Ferrari wrote: >>> >>> hello, >>> the martin peach's object midifile has 3 outlets, >>> >>> the first outlet output a list with 3 numbers: >>> >>> xxx,note,velocity >>> >>> what is xxx ??? >>> >>> thanks!! >>> >>> Andrés Ferrari G. >>> >>> http://www.myspace.com/anfex >>> >>> >>> >>> >>> >>> >>> >>> ¡Obtén la mejor experiencia en la web! >>> Descarga gratis el nuevo Internet Explorer 8. >>> http://downloads.yahoo.com/ieak8/?l=e1 >>> >>> >>> ___ >>> Pd-list@iem.at mailing list >>> UNSUBSCRIBE and account-management -> >>> http://lists.puredata.info/listinfo/pd-list >>> >> >> ___ >> Pd-list@iem.at mailing list >> UNSUBSCRIBE and account-management -> >> http://lists.puredata.info/listinfo/pd-list > > ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] midifile object
sysex has no channel being a system and not a channel message, as far as I know. The first value should by in hex 'f0' meaning start of sysex. the 2nd byte which in some software appears at the channel# is the manufacturer id ($01 for sequential circuits, $04 for Moog, $11 for Apple, for example). but it is all on the MIDI site, no? Best Jurgen On Jul 9, 2009, at 2:06 AM, Alex wrote: I'm not 100% but if I were to guess I'd say xxx would be midi channel. -Alex On Wed, Jul 8, 2009 at 10:54 AM, Andres Ferrari wrote: hello, the martin peach's object midifile has 3 outlets, the first outlet output a list with 3 numbers: xxx,note,velocity what is xxx ??? thanks!! Andrés Ferrari G. http://www.myspace.com/anfex _ ___ ¡Obtén la mejor experiencia en la web! Descarga gratis el nuevo Internet Explorer 8. http://downloads.yahoo.com/ieak8/?l=e1 ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] midifile object
I'm not 100% but if I were to guess I'd say xxx would be midi channel. -Alex On Wed, Jul 8, 2009 at 10:54 AM, Andres Ferrari wrote: > > hello, > the martin peach's object midifile has 3 outlets, > > the first outlet output a list with 3 numbers: > > xxx,note,velocity > > what is xxx ??? > > thanks!! > > Andrés Ferrari G. > > http://www.myspace.com/anfex > > > > > > > > ¡Obtén la mejor experiencia en la web! > Descarga gratis el nuevo Internet Explorer 8. > http://downloads.yahoo.com/ieak8/?l=e1 > > > ___ > Pd-list@iem.at mailing list > UNSUBSCRIBE and account-management -> > http://lists.puredata.info/listinfo/pd-list > ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
[PD] midifile object
hello, the martin peach's object midifile has 3 outlets, the first outlet output a list with 3 numbers: xxx,note,velocity what is xxx ??? thanks!! Andrés Ferrari G. http://www.myspace.com/anfex ¡Obtén la mejor experiencia en la web! Descarga gratis el nuevo Internet Explorer 8. http://downloads.yahoo.com/ieak8/?l=e1 ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] Midifile Object
patrick wrote: > if you can clean up midifile a bit (no offense martin!) so that we can load > a midi and play the song with some simple sound (can be osc~ for piano, > phasor~ for bass, noise~ for snare etc...). that would be neat. actually, i I just checked in a new help file that uses some [osc~]s for the first few channels. > was working with midifile for loading channel 10 (drums) but i am having > some problem with note-on / note-off (properly play the kick, snare). also Some files use the MIDI noteoff message for note offs and others use noteon with velocity zero. Possibly drum tracks use only note ons and never send any note offs. > when i load a midifile, there's like 5 sec. with no sound when pressing > play. bref, i will investigate more but if we can come up with a good > demo... I've noticed a lot of midi files have a few seconds of nothing at the beginning as though they were made by recording a keyboard live (or they set up a bunch of controls before starting). If you note the tick at which the sound starts you can just specify that offset to [midifile] and start there. Martin ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] Midifile Object
ah cheers thanks a million martin, you're a lifesaver! am looking forward to getting stuck into your external properly now! thanks, john. - Original Message > From: Martin Peach <[EMAIL PROTECTED]> > To: saint <[EMAIL PROTECTED]> > Cc: pd-list@iem.at > Sent: Tuesday, 19 February, 2008 2:09:05 PM > Subject: Re: [PD] Midifile Object > > It's fixed now in svn and works as advertised (opens files in patcher > directory unless absolute path given). > You can get source code and a compiled dll from > http://puredata.info/Members/martinrp/ > > Martin > > saint wrote: > > hi martin/all, > > > > sorry for buggin you about this again, but unfortunately i can't use your > > (or > any) midi external > > for my purpose if i can't get this to work. > > > > the problem i'm having with midifile is this: i can't get midifile to read > > a > .mid file that's in the > > same folder as the pd patch by referring to it by it's short name only > > i.e. without the full path c:/progra~1/etc/etc (which does work btw, thanks) > > > > is there anyway to get this... > > > > [read test.mid( > > | > > [midifile] > > > > ...to work?! > > > > (where the midi file and pd patch are in the same folder of course) > > > > basically i need to copy multiple instances of the patch and run it from > > lots > of different folders > > each referring to different midi files > > > > again thanks a million in advance you've been more than helpful so far! > > > > - Original Message > > From: Martin Peach > > To: [EMAIL PROTECTED]; pd-list@iem.at > > Sent: Tuesday, 12 February, 2008 8:53:59 PM > > Subject: Re: [PD] Phasor Driven Midi File Playback? > > > > The latest versions are part of pd-extended in > > http://autobuild.puredata.info/auto-build/ but the last functional WinXp > > version is in late 2007. The spaces in path names cause trouble throughout > > pd and other "cross-platform" programs, the only workaround I know of is to > > rename your directories without spaces. I usually use underscores instead. > > "Program Files" always causes trouble. Sometimes you can access it using > > something like C:\PROGRA~1 (the short DOS name) > > This works on my system: > > > > [read C:/PROGRA~1/pd/doc/5.reference/textfile.txt( > > > > but > > > > [C:/PROGRA~1/pd/doc/5.reference/textfile.txt( > > | > > [read $1( > > > > does not work. > > > > Martin > > > > > >> From: saint > >> To: pd-list@iem.at > >> Subject: Re: [PD] Phasor Driven Midi File Playback? > >> Date: Tue, 12 Feb 2008 11:39:53 -0800 (PST) > >> > >> hmmm. i did try that but it seems to stumble at the first space in the > >> full > >> path (as pure data does) > >> > >> unfortunately the patch will need to be ported around when it's done so > >> specifying a full path won't fulfill my needs. > >> > >> is there a .dll of the midifile external for w32 knocking around for which > >> this read message works for shortened paths? > >> > >> > >> > >> again, thanks all of you for your time! > >> > >> > >> - Original Message > >> From: Mike McGonagle > >> To: saint > >> Cc: pd-list@iem.at > >> Sent: Tuesday, 12 February, 2008 7:22:29 PM > >> Subject: Re: [PD] Phasor Driven Midi File Playback? > >> > >> I think what is happening is that [midifile] is expecting a full path for > >> the file name when using read. This is why it works for the [openpanel] > >> because it returns a complete path. Did you try using the full path with > >> [read $1(? > >> > >> > >> Mike > >> > >> > >> On Feb 12, 2008 12:33 PM, saint wrote: > >> > >> thanks for the quick reply again martin, > >> > >> it's a strange problem that i seem to be having. > >> > >> because i definitely have all the midifiles in the same folder as the > >> patch > >> but > >> > >> [midifile test.mid] > >> ...or... > >> [read test.mid(---[midifile] > >> gives... 'error: midifile: unable to open test.mid' > >> > >> > >> but when i do > >> [bang]---[openpanel]---[read $1(---[midifile] > >> and point it to 'test.mid' it seems to work? > >> > >> h... > >> unfortunately for what i want to do i need to be able to automate opening > >> different midifiles. > >> > >> i'm using your zip from > >> http://puredata.info/Members/martinrp/midifile/midifile.zip/view > >> > >> > > > > > > > > > > > > > > > > ___ > > Support the World Aids Awareness campaign this month with Yahoo! For Good > http://uk.promotions.yahoo.com/forgood/ > > > __ Sent from Yahoo! Mail. A Smarter Inbox. http://uk.docs.yahoo.com/nowyoucan.html ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] Midifile Object
It's fixed now in svn and works as advertised (opens files in patcher directory unless absolute path given). You can get source code and a compiled dll from http://puredata.info/Members/martinrp/ Martin saint wrote: > hi martin/all, > > sorry for buggin you about this again, but unfortunately i can't use your (or > any) midi external > for my purpose if i can't get this to work. > > the problem i'm having with midifile is this: i can't get midifile to read a > .mid file that's in the > same folder as the pd patch by referring to it by it's short name only > i.e. without the full path c:/progra~1/etc/etc (which does work btw, thanks) > > is there anyway to get this... > > [read test.mid( > | > [midifile] > > ...to work?! > > (where the midi file and pd patch are in the same folder of course) > > basically i need to copy multiple instances of the patch and run it from lots > of different folders > each referring to different midi files > > again thanks a million in advance you've been more than helpful so far! > > - Original Message > From: Martin Peach <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED]; pd-list@iem.at > Sent: Tuesday, 12 February, 2008 8:53:59 PM > Subject: Re: [PD] Phasor Driven Midi File Playback? > > The latest versions are part of pd-extended in > http://autobuild.puredata.info/auto-build/ but the last functional WinXp > version is in late 2007. The spaces in path names cause trouble throughout > pd and other "cross-platform" programs, the only workaround I know of is to > rename your directories without spaces. I usually use underscores instead. > "Program Files" always causes trouble. Sometimes you can access it using > something like C:\PROGRA~1 (the short DOS name) > This works on my system: > > [read C:/PROGRA~1/pd/doc/5.reference/textfile.txt( > > but > > [C:/PROGRA~1/pd/doc/5.reference/textfile.txt( > | > [read $1( > > does not work. > > Martin > > >> From: saint <[EMAIL PROTECTED]> >> To: pd-list@iem.at >> Subject: Re: [PD] Phasor Driven Midi File Playback? >> Date: Tue, 12 Feb 2008 11:39:53 -0800 (PST) >> >> hmmm. i did try that but it seems to stumble at the first space in the full >> path (as pure data does) >> >> unfortunately the patch will need to be ported around when it's done so >> specifying a full path won't fulfill my needs. >> >> is there a .dll of the midifile external for w32 knocking around for which >> this read message works for shortened paths? >> >> >> >> again, thanks all of you for your time! >> >> >> - Original Message >> From: Mike McGonagle <[EMAIL PROTECTED]> >> To: saint <[EMAIL PROTECTED]> >> Cc: pd-list@iem.at >> Sent: Tuesday, 12 February, 2008 7:22:29 PM >> Subject: Re: [PD] Phasor Driven Midi File Playback? >> >> I think what is happening is that [midifile] is expecting a full path for >> the file name when using read. This is why it works for the [openpanel] >> because it returns a complete path. Did you try using the full path with >> [read $1(? >> >> >> Mike >> >> >> On Feb 12, 2008 12:33 PM, saint <[EMAIL PROTECTED]> wrote: >> >> thanks for the quick reply again martin, >> >> it's a strange problem that i seem to be having. >> >> because i definitely have all the midifiles in the same folder as the patch >> but >> >> [midifile test.mid] >> ...or... >> [read test.mid(---[midifile] >> gives... 'error: midifile: unable to open test.mid' >> >> >> but when i do >> [bang]---[openpanel]---[read $1(---[midifile] >> and point it to 'test.mid' it seems to work? >> >> h... >> unfortunately for what i want to do i need to be able to automate opening >> different midifiles. >> >> i'm using your zip from >> http://puredata.info/Members/martinrp/midifile/midifile.zip/view >> >> > > > > > > > > ___ > Support the World Aids Awareness campaign this month with Yahoo! For Good > http://uk.promotions.yahoo.com/forgood/ > ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] Midifile Object
# Hi, # I'll be very happy too if this feature can be done. Once I made a demonstration about tuning systems, where I used a midi file as the input. I packed the midi file with the patch but it did not work on any computer other than mine because [midifile] could not find the file. # Thanks in advance! -uğur- On Thu, Feb 14, 2008 at 8:26 PM, saint <[EMAIL PROTECTED]> wrote: > hi martin/all, > > sorry for buggin you about this again, but unfortunately i can't use your > (or any) midi external > for my purpose if i can't get this to work. > > the problem i'm having with midifile is this: i can't get midifile to read a > .mid file that's in the > same folder as the pd patch by referring to it by it's short name only > i.e. without the full path c:/progra~1/etc/etc (which does work btw, thanks) > > is there anyway to get this... > > [read test.mid( > | > [midifile] > > ...to work?! > > (where the midi file and pd patch are in the same folder of course) ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] Midifile Object
The way it works now [midifile] reads from the same directory that pd is in unless you specify the full path. It should be possible to get it to search in the patch directory, probably by calling canvas_open in pd. I'll look into it this weekend. Martin >From: saint <[EMAIL PROTECTED]> >To: pd-list@iem.at >Subject: [PD] Midifile Object >Date: Thu, 14 Feb 2008 10:26:07 -0800 (PST) > >hi martin/all, > >sorry for buggin you about this again, but unfortunately i can't use your >(or any) midi external >for my purpose if i can't get this to work. > >the problem i'm having with midifile is this: i can't get midifile to read >a .mid file that's in the >same folder as the pd patch by referring to it by it's short name only >i.e. without the full path c:/progra~1/etc/etc (which does work btw, >thanks) > >is there anyway to get this... > >[read test.mid( >| >[midifile] > >...to work?! > >(where the midi file and pd patch are in the same folder of course) > >basically i need to copy multiple instances of the patch and run it from >lots of different folders >each referring to different midi files > >again thanks a million in advance you've been more than helpful so far! > ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
[PD] Midifile Object
hi martin/all, sorry for buggin you about this again, but unfortunately i can't use your (or any) midi external for my purpose if i can't get this to work. the problem i'm having with midifile is this: i can't get midifile to read a .mid file that's in the same folder as the pd patch by referring to it by it's short name only i.e. without the full path c:/progra~1/etc/etc (which does work btw, thanks) is there anyway to get this... [read test.mid( | [midifile] ...to work?! (where the midi file and pd patch are in the same folder of course) basically i need to copy multiple instances of the patch and run it from lots of different folders each referring to different midi files again thanks a million in advance you've been more than helpful so far! - Original Message From: Martin Peach <[EMAIL PROTECTED]> To: [EMAIL PROTECTED]; pd-list@iem.at Sent: Tuesday, 12 February, 2008 8:53:59 PM Subject: Re: [PD] Phasor Driven Midi File Playback? The latest versions are part of pd-extended in http://autobuild.puredata.info/auto-build/ but the last functional WinXp version is in late 2007. The spaces in path names cause trouble throughout pd and other "cross-platform" programs, the only workaround I know of is to rename your directories without spaces. I usually use underscores instead. "Program Files" always causes trouble. Sometimes you can access it using something like C:\PROGRA~1 (the short DOS name) This works on my system: [read C:/PROGRA~1/pd/doc/5.reference/textfile.txt( but [C:/PROGRA~1/pd/doc/5.reference/textfile.txt( | [read $1( does not work. Martin >From: saint <[EMAIL PROTECTED]> >To: pd-list@iem.at >Subject: Re: [PD] Phasor Driven Midi File Playback? >Date: Tue, 12 Feb 2008 11:39:53 -0800 (PST) > >hmmm. i did try that but it seems to stumble at the first space in the full >path (as pure data does) > >unfortunately the patch will need to be ported around when it's done so >specifying a full path won't fulfill my needs. > >is there a .dll of the midifile external for w32 knocking around for which >this read message works for shortened paths? > > > >again, thanks all of you for your time! > > >- Original Message >From: Mike McGonagle <[EMAIL PROTECTED]> >To: saint <[EMAIL PROTECTED]> >Cc: pd-list@iem.at >Sent: Tuesday, 12 February, 2008 7:22:29 PM >Subject: Re: [PD] Phasor Driven Midi File Playback? > >I think what is happening is that [midifile] is expecting a full path for >the file name when using read. This is why it works for the [openpanel] >because it returns a complete path. Did you try using the full path with >[read $1(? > > >Mike > > >On Feb 12, 2008 12:33 PM, saint <[EMAIL PROTECTED]> wrote: > >thanks for the quick reply again martin, > >it's a strange problem that i seem to be having. > >because i definitely have all the midifiles in the same folder as the patch >but > >[midifile test.mid] >...or... >[read test.mid(---[midifile] >gives... 'error: midifile: unable to open test.mid' > > >but when i do >[bang]---[openpanel]---[read $1(---[midifile] >and point it to 'test.mid' it seems to work? > >h... >unfortunately for what i want to do i need to be able to automate opening >different midifiles. > >i'm using your zip from >http://puredata.info/Members/martinrp/midifile/midifile.zip/view > > ___ Support the World Aids Awareness campaign this month with Yahoo! For Good http://uk.promotions.yahoo.com/forgood/ ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
