The converters are gone!

Discuss the current and future development of Max.
Maurits
Posts: 117
Joined: Sun Jan 29, 2006 1:36 pm
Location: London, Europe

Post by Maurits » Tue Oct 10, 2006 12:27 pm

Screwtape wrote:Just a note - I downloaded the 995 build of Max and used it to rip a few CDs that just arrived from Amazon. It worked pretty well, except that it seems that when I rip a track over 15 mins long and convert to MP3, Max throws up an error dialog when it's finished encoding. The resulting file seems OK, but the error message is jarring (something about trying to put nil into an NSCFDictionary, I think).
Is it the same error as this one?

Screwtape
Posts: 8
Joined: Tue Jan 24, 2006 11:48 am

Post by Screwtape » Tue Oct 10, 2006 1:56 pm

Maurits wrote:
Screwtape wrote:Just a note - I downloaded the 995 build of Max and used it to rip a few CDs that just arrived from Amazon. It worked pretty well, except that it seems that when I rip a track over 15 mins long and convert to MP3, Max throws up an error dialog when it's finished encoding. The resulting file seems OK, but the error message is jarring (something about trying to put nil into an NSCFDictionary, I think).
Is it the same error as this one?
I definitely got an error about NSCFDictionary, although it's quite possible that at some other point I got the NSCFArray error you describe - Max has an annoying habit of popping up its dialogs while I'm in the middle of typing into another window, and I wind up accidentally hitting enter or space and dismissing the dialog before I've read it. :(

shanecavanaugh
Posts: 68
Joined: Sat Jan 14, 2006 12:32 am
Contact:

Post by shanecavanaugh » Sat Oct 14, 2006 5:08 pm

I think the same bug in custom file naming is back. The MP3 encoder isn't encoding for r1024.

User avatar
sbooth
Site Admin
Posts: 2445
Joined: Fri Dec 23, 2005 7:45 am
Location: USA
Contact:

Post by sbooth » Sat Oct 14, 2006 6:23 pm

shanecavanaugh wrote:I think the same bug in custom file naming is back. The MP3 encoder isn't encoding for r1024.
I am encoding to MP3 using custom naming as we speak (type?). I'm not sure why it wouldn't be working for you. Can you post some details?

shanecavanaugh
Posts: 68
Joined: Sat Jan 14, 2006 12:32 am
Contact:

Post by shanecavanaugh » Sat Oct 14, 2006 8:33 pm

Sorry for not testing it further. Max spits this into the console after each track had ripped:

Code: Select all

2006-10-14 16:31:15.246 Max[1462] *** -[NSCFString boolValue]: selector not recognized [self = 0x6657f90]

User avatar
sbooth
Site Admin
Posts: 2445
Joined: Fri Dec 23, 2005 7:45 am
Location: USA
Contact:

Post by sbooth » Sun Oct 15, 2006 4:03 am

Nothing jumps out at me in the source code. Can you post steps I can follow to reproduce the bad behavior?

Edit: The problem is fixed. See http://sbooth.org/forums/viewtopic.php?t=423.

shanecavanaugh
Posts: 68
Joined: Sat Jan 14, 2006 12:32 am
Contact:

Post by shanecavanaugh » Mon Oct 16, 2006 7:08 pm

When ripping to MP3 set to the Transparent setting on r1037, Max's log spits out: "LAME settings: 0 kbps qval=-1".

I believe the quality value for that setting is "2". Is Max still encoding at that value though the log says otherwise?

User avatar
sbooth
Site Admin
Posts: 2445
Joined: Fri Dec 23, 2005 7:45 am
Location: USA
Contact:

Post by sbooth » Tue Oct 17, 2006 4:28 am

shanecavanaugh wrote:When ripping to MP3 set to the Transparent setting on r1037, Max's log spits out: "LAME settings: 0 kbps qval=-1".

I believe the quality value for that setting is "2". Is Max still encoding at that value though the log says otherwise?
Yes, this was because the log message was being generated before the encoder parsed its settings. I've just changed things so the settings get parsed before anything else, so this should be fixed. In any case, the encoder was actually encoding with the correct settings regardless of what the log said.

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest