[PD-dev] Looks like there's a song position pointer bug

Chris McCormick chris at mccormick.cx
Mon Sep 22 12:58:21 CEST 2003


On Sat, Sep 20, 2003 at 01:05:29PM -0700, Miller Puckette wrote:
> Yep, this is apparently a Bug, which has been present in every version of Pd 
> and probably some versions of Max too.
> 
> Pd's MIDI parser just ignores everything starting with F0 or higher.  (I
> thought I was dealing with sysex but, having just looked at the code,
> it looks like I forgot to put that in.)
> 
> I'm willing to try to fix this... but I can't really test it since I
> don't have any gear that spits out messages like that.

How about using the v_midi kernel module? You could pipe the output into
another program which can print midi messages.

Chris.

> On Sat, Sep 20, 2003 at 11:14:01AM -0400, Larry Troxler wrote:
> > (Sorry if this has been sent more then once)
> > 
> > Well, I haven't heard from anyone, and I don't see anything later than what I
> > have that's relevant in CVS, so, I assume that no news is bad news, and that
> > the PD MIDI parser vomits green blood when you send it Song Position Pointer
> > messages.
> > 
> > ... so I guess if you want something done, you gotta do it yourself.
> > 
> > So:
> > 
> > How are bug fixes submitted? (since the midi parser trips and falls when
> > getting an $F2, screwing up for example, the notein object, this isn't just a
> > missing feature, it's a bug)
> > 
> > I suppose I'll also have to make a MIDI object that sends a float when it
> > receives a song position pointer (this I need). And also one that can send
> > song position pointer messages (this I don't need, but I guess I gotta submit
> > anyway for the sake of completeness - grumble grumble).
> > 
> > So, can someone suggest that best procedure  who to send it to, in what
> > format, should I put it in the CVS directly, post patch files, send to
> > Miller, etc...?
> > 
> > But honestly, it would motivate me greatly to do a complete and thorough job,
> > if someone would send me some pointers or URLs on how to deal with this
> > hard-tab issue. It seems that the source I got from CVS has actual hard tabs
> > in it, and so far I don't see anything in the CVS docs on how to bypass that
> > so I get a clean copy, nor any mention anywhere in the source files of what
> > the spacing that these hard tabs represent.  I truly wish people would stop
> > using these retarded things, but since they still insist, I need advice on
> > how to deal with these "legacy" files.
> > 
> > Larry
> > 
> > 
> > _______________________________________________
> > PD-dev mailing list
> > PD-dev at iem.at
> > http://iem.at/cgi-bin/mailman/listinfo/pd-dev
> 
> _______________________________________________
> PD-dev mailing list
> PD-dev at iem.at
> http://iem.at/cgi-bin/mailman/listinfo/pd-dev

-- 
_________________________________
chris at mccormick.cx
http://www.mccormick.cx
http://www.hypercube.com.au
http://www.sciencegirlrecords.com




More information about the Pd-dev mailing list