Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[basabasa]

I have started re-ripping my 500 cds again using MP3 VBR with MC 11... Sometimes when I insert a CD to rip, I get the message that YADB Access Failed! Meaning I have to type in all the track names manually and after doing this onerous task
1. The file directory path and filename does not change.
2. And If I insert another CD and YADB fails again the Unknown Blah Blah goes to replace the previous rip which I thought I had manually typed in the trask names....

Is there a way that I can avoid this YADB Failed Access Business.
What should I do after typing in the track names, artist and album. I update the library from tags? I did it but i don't think it did the job.

Help please.

[John Gateley]

Have you tried getting info a second time? Right click and choose "Downoad from database".

j

[basabasa]

Yes, I tried for a second time. Sometimes it works, most times not. Right click on what? Anywhere on the MC interface? I will try it next time. Thanks a lot.

[John Gateley]

On the CD icon in the tray. Next time it fails, note the time and your IP address (open a dos or command window, type ipconfig) and put a message here (use a private message if you want to hide your IP). I'll check out what's going on...

j

[basabasa]

Alright. Thanks a lot John.

[mander]

I have had similiar issues.  If I release and renew my ip it fixes the problem.  I am using NAT behind a firewall.  I believe it is leaving the session open.  If I rip on my laptop and my desktop at the same time this problem is more prevalent.

You can go to a CMD prompt and type ipconfig /release <ENTER> then ipconfig /renew <ENTER>

This will close any open TCP connections. 

Hope this helps,
Matthew

[John Gateley]

Nice find mander. I'll fix this.

j

[basabasa]

thanks manda.

[John Gateley]

It looks like it's not as simple as I thought. Would y'all turn on debug logging for the reader (MC Help, Configure debug logging), and when it happens next time, post the log here (if it's not too long)?

Thanks,

j

[John Gateley]

I tried reproducing this - 40 lookups in a row with no waiting, and all succeeded. Any further ideas? Could this be a limitation of the NAT implementation?

j