INTERACT FORUM

More => Old Versions => Media Jukebox => Topic started by: Alan on August 13, 2002, 05:01:38 am

Title: Version 8.0.346 First VBR Rip on XP fails
Post by: Alan on August 13, 2002, 05:01:38 am
Virgin Windows XP Pro machine & virgin 8.0.346 install.
Tried to RIP first CD, selected MP3 VBR.
Encoder correctly downloaded & installed (or so I thought).
Combo box underneath MP3 VBR was not enabled (and looked wrong).
I went ahead and did the RIP anyway (my mistake).
RIPped 2 CD's both were mostly regular interval skips (every 1-2 seconds) with a little music interspersed.
Exitted MJ and restarted it.
Did the RIP again just fine.
NOTE that the combo box under MP3 VBR was now correct for the quality setting (I seelcted Normal/high). RIP was fine.
This would *not* be a pleasant experience for a novice.
(for those of us around since 6.xxx or earlier, it's no big deal...)
Title: RE:Version 8.0.346 First VBR Rip on XP fails
Post by: Charlemagne 8 on August 13, 2002, 02:58:01 pm
Mine also was fine after a restart. Maybe that should be suggested as SOP.
Title: RE:Version 8.0.346 First VBR Rip on XP fails
Post by: sekim on August 13, 2002, 03:33:25 pm
If you are using the internal ASPI for XP it does mention this in the options.(Re-Start Required) Should also re-start if switching to Adaptecs ASPI layer just for good measure. I think it updates configuration then.

I did notice many times when using 98SE that a re-start would often times do wonders. Using XP now and things are much smoother than 98SE.
Title: RE:Version 8.0.346 First VBR Rip on XP fails
Post by: Alan on August 14, 2002, 09:00:23 am
As a followup, I'm not sure if my ripping problem was caused by an audio CD in my DVD drive as it now appears that the DVD has problems at times on *some* audio CD's?!?!  The strange thing is I have it set for Digital Playback, so I wouldn't have guessed any problem should exist.

However, my primary mention was for the seamless ripping that an XP newbie would expect. I think it would be lousy if they deleted MJ from their hard drive because their first RIP failed miserably. (i.e. this is a marketing bug, not a bug I think is technically important.)