known bugs

Jul 8, 2013 at 10:33am

known bugs

Is there a current list of known bugs?

#255265
Jul 9, 2013 at 6:57pm

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:

http://cycling74.com/forums/topic/can-you-create-a-wav-file-with-more-than-two-channels/

http://cycling74.com/forums/topic/sfrecordsfinfo-problem-wmultichannel-wav-files/

#255486
Jul 10, 2013 at 1:19am

there is such a list, in the wiki :

http://cycling74.com/wiki/index.php?title=known_bugs

…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…

#255502
Jul 10, 2013 at 1:22am

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).

#255503
Jul 10, 2013 at 1:55am

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 :

RIFF@Ú+

#255507
Jul 10, 2013 at 1:57am

THE IRONY
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.

<code>

– Pasted Max Patch, click to expand. –

</code>

Attachments:
  1. Capture-d’écran-2013-07-10-à-10.58.31
#255508
Jul 10, 2013 at 2:04am

Second try : with this patcher
<code>

– Pasted Max Patch, click to expand. –

</code>

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.

Attachments:
  1. Capture-d’écran-2013-07-10-à-10.58.55
#255510

You must be logged in to reply to this topic.