INTERACT FORUM
More => Old Versions => Media Center 11 (Development Ended) => Topic started by: liam on February 06, 2004, 09:59:40 am
-
ive been using mc9 for a few months now on my laptop and have been happy with it til now :P
everytime i try to rip a cd mc9 comes up with an error msg - failed to load plug in ". - then xp error msg comes up and mc shuts down :o
sometimes it happens before the cd is ripped, sometimes after ive ripped the cd. sometimes when i eject the cd after ripping it. weird.
any ideas?
Media Center Registered 9.1.316 -- C:\Program Files\J River\Media Center\
Microsoft Windows XP Workstation 5.1 Service Pack 1 (Build 2600)
Intel Unknown 253 MHz MMX / Memory: Total - 260 MB, Free - 86 MB
Internet Explorer: 6.0.2800.1106 / ComCtl32.dll: 5.82 (xpsp1.020828-1920) / Shlwapi.dll: 6.00.2800.1400 / Shell32.dll: 6.00.2800.1233 (xpsp2.030604-1804) / wnaspi32.dll: N/A
Ripping / Drive D: Copy mode:ModeSecure CD Type:Auto Read speed:Max
Digital playback: Yes / Use YADB: Yes / Get cover art: Yes / Calc replay gain: Yes / Copy volume: 32767
Eject after ripping: Yes / Play sound after ripping: Yes Soundfile: chord.wav
Burning / Drive D: TOSHIBA DVD-ROM SD-R6012 Addr: 1:0:0 Speed:16 MaxSpeed:16 BurnProof:Yes
Test mode: No / Eject after writing: Yes / Direct decoding: Yes / Write CD-Text: No
Use playback settings: No / Normalization: None
-
Try installing the encoder plug-in you need. MP3, for example.
-
again.. huh? why would i need an encoder? isnt it built in to mc9? ive ripped cd's on this laptop before with mc9?
sincerely,
confused :-\
-
it actually says - cannot create plug in ". if that makes any diff :)
it just did it again, i ripped a cd, mc9 acquired info from yadb then bamn error message
mc9 closed then i reopened it
the cd was still in the drive and showed up in mc9 so i ripped it. cd ejected and bamn error message and mc9 shuts down
hmmm....
-
There was an issue with certain systems and handhelds.
I know it has been addressed in MC 10. I'm not sure if there's a workaround for MC 9.1 or not.
-
hi matt
i have an ipod that has always worked fine with mc9 ( actually the reason i got mc9 )
but im not sure what that has to do with my cd ripping problem?
-
Did you re-install the plug-in?
Try other formats. WMA, for example.
-
sorry guys but you need to break it down. i dont know what plug in you are talking about. i havent installed any plug ins. hell i dont even know what a plug in is. ive used this program to rip and encode nearly 200 cd's so far but as of today this error message is coming up.
i updated mc9 by using the help link but i dont if thats related :(
-
Choose another format when you encode. Instructions are in the Help section of MC.
-
ok i tried that no luck, other formats cause the same error message then crash mc9
ive got screen shots if it helps, just cant figure out how to upload em here..
-
It may be a handheld plugin error.
Media Center 10 (available at the top of this forum) will fix it. There may be another solution, but I'm not sure.
-
ok i dont understand how its a handheld issue as i havent changed my ipod but i have absolute faith in you guys ehehehe
before i download version ten, ive got three questions...
1) is it a free upgrade to version 10 to fix the problem?
2) do i have to uninstall version 9 first?
3) will i lose my database of music?
thanks a lot for the support ;D
-
So the solution is to go beta? I thought serious problems that were found in MC 9.1.316 would be fixed. They paid their money for the current released version and it doesn't work.
I've heard of insisting that users with problems install the latest available release before asking for support but asking them to install a beta that will expire unless they pay more $ is a bit much surely.
-
We have said we will fix only major problems in MC 9.1. In my opinion, the problem found here is neither conclusively MC nor wide spread.
-
ok i dont understand how its a handheld issue as i havent changed my ipod but i have absolute faith in you guys
1) is it a free upgrade to version 10 to fix the problem?
No. It's $19.98. Please see this page: www.mediajukebox.com/license .
2) do i have to uninstall version 9 first?
No.
3) will i lose my database of music?
No.
-
k thanks jim
im a bit dissapointed ive got to pay for a new/beta version to fix a problem within mc9 ( thats come outa nowhere )
but if thats the way the ball bounces then so be it. for $20 it worth trying to figure out lol!
cheers
liam
-
I've heard of insisting that users with problems install the latest available release before asking for support but asking them to install a beta that will expire unless they pay more $ is a bit much surely.
I don't believe that anyone is insisting that he do anything. Matt said:
"Media Center 10 (available at the top of this forum) will fix it. There may be another solution, but I'm not sure. "
Like the U.S. Intelligence, we are rarely completely right or completely wrong. We just do our best every day.
-
If it's a handheld problem, Try turning the Sync off..
That may help..
http://yabb.jriver.com/interact/index.php?board=3;action=display;threadid=18230
-
I never said you insisted anything. If you read my post carefully I said 'I've heard of insisting that users install the latest available release' [in this case 9.1.316] ... 'before asking for support but ASKING to install a beta....]
So I was suggesting that you JRiver were ASKING them to install a beta to fix a fault not INSISTING they install a beta.
As you know this problem has been discussed before by other users and you claimed at that time to have fixed it in v10, and since no users complained again it would seem fair to presume you had.
This is the thread. (http://yabb.jriver.com/interact/index.php?board=3;action=display;threadid=18230)
However you now say it's not conclusively MC. So you fixed it in v10 but it's not conclusively MC? And now you suggest someone might want to fork out $20 to see if it's fixed. That does not seem right or proper to me.
When I buy something I expect it to do what it says on the tin and if it doesn't I expect it to be fixed without having to pay extra for the priviledge.
-
What reason could you possibly have for not applying the fix to 9.1.316 to benefit existing v9 users. If the fix goes belly up and all hell breaks loose in the worst case they just revert to 9.1.316.
Maybe there's another reason you don't want to fix 9.1.316?
-
What reason could you possibly have for not applying the fix to 9.1.316 to benefit existing v9 users. If the fix goes belly up and all hell breaks loose in the worst case they just revert to 9.1.316.
Maybe there's another reason you don't want to fix 9.1.316?
Yes. It could break something. 316 if incredibly stable for most folks. Take a look at the bug thread here. Almost all problems posted now are questions and comments about operation. Very few problems and all are unusual, unexplained, or minor.
-
From liam by PM:
"i fixed the error without having to "upgrade" to version 10
i had to untick the auto sync handheld option in device settings."