Is it the same error as this one?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).
The converters are gone!
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. :(Maurits wrote:Is it the same error as this one?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).
-
- Posts: 68
- Joined: Sat Jan 14, 2006 12:32 am
- Contact:
-
- Posts: 68
- Joined: Sat Jan 14, 2006 12:32 am
- Contact:
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]
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.
Edit: The problem is fixed. See http://sbooth.org/forums/viewtopic.php?t=423.
-
- Posts: 68
- Joined: Sat Jan 14, 2006 12:32 am
- Contact:
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.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?