Forums > MaxMSP

known bugs

Jul 08 2013 | 10:33 am

Is there a current list of known bugs?

Jul 09 2013 | 6:57 pm

I’m guessing that’s a "no"?

It seems like this would be a useful thing to have so that when you’re thinking about filing a bug report you would know whether the problem has already been reported.

You can look at the forums and get a sense of whether others have had the same or similar problems, and people often talk about filing a bug report but there is no way to know whether it has happened.

I’m curious about this because I filed a bug report at some point in the past year – received a very nice reply saying that the problem had been confirmed by duplication – but haven’t seen any action on solving the problem. As I research this further it seems that this problem has existed since at least 2006.

The problem, if anyone is curious:

Jul 10 2013 | 1:19 am

there is such a list, in the wiki :

…but, as you can see, it’s not really used. Feel free to use it anyway, though, since it’s wiki (as long as you follow the indications on the page).`

edit : regarding your problems… i will take a look, but been working with aiff more than wave, so…

Jul 10 2013 | 1:22 am

I agree. Would be nice to publish a list of reported issues and the status of it (reported, confirmed, under treatment, fixed in release x.x). Though I don’t know if any commercial software company publishes this sort of thing (look at all those bugs! what a piece of cr*p!). Openness about it would surely grace software companies (and save users a load of frustrations).

Jul 10 2013 | 1:55 am

Back on topic : indeed, the 6 channels wave file i created could only be read back by Max, not Audacity, Soundhack can’t read more than 6 channels apparently, etc…

I could totally reproduce.
By sending a (open wave) message to Max then manually entering the name : file records fine, playback / sfinfo~ are fine, and file header begins with :


Jul 10 2013 | 1:57 am

i wrote a long post, but it didn’t survive the strange symbols of the first header i’m mentioning. I try again

well i’ll do screenshots………..

First file header : file recorded with that patcher – works fine in Max, nowhere else – sends [sfrecord~] this message : (open wave) ; then i manually entered filename.

-- Pasted Max Patch, click to expand. --


  1. Capture-d’écran-2013-07-10-à-10.58.31


Jul 10 2013 | 2:04 am

Second try : with this patcher

-- Pasted Max Patch, click to expand. --


which should send a (open [filename] WAVE) message to sfrecord~ ; works fine anywhere else than Max. Header beginning in included image. Seems to be an aiff file in disguise.

edit : at that point, using the bug reporting form is the right way.

  1. Capture-d’écran-2013-07-10-à-10.58.55


Viewing 7 posts - 1 through 7 (of 7 total)

Forums > MaxMSP