Print

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

[kentschu]

So I've seen numerous people posting questions about the error "CDDB: Malformed command sent from server to client", but I haven't found the solution yet.

Switching to YADB doesn't seem to change anything.
And it seems that people are still using CDDB successfully.

Anyone have a real answer?

Kent
:-/

[kentschu]

Wait, let me clarify a few things with this problem:

1) Switching to YADB does help but only when I use "Update from CD database", not when I select "CD Disk Info" (then it still tries to use CDDB regardless of setting).

2) YADB doesn't recognize many CD's that CDDB recognizes in other CD ripping programs.  My CDDB registration works elsewhere...

3) CDDB always gives the "malformed content" error.
Kent

[ChicoSelfs]

what is our version of MJ?

[kentschu]

8.0.375

[KingSparta]

>> My CDDB registration works elsewhere...
Within every program that uses CDDB there is a Product registration.

This way if CDDB feels like it they can turn off what ever program uses the CDDB dll's. or maybe even not allow new users with that product.

Basicly what happens when you do A CDDB lookup the dlls send CDDB's server the product Info, this information is in the registry for J river but it is encoded so it can not be used by someone else. and this info along with other info to include the CD TOS. when a match is found the info is sent back to the CDDB dlls and what ever info message is displayed.

so just because CDDB works for you In Helium does not mean it will work for you in MJ.

I just tried CDDB lookup and it is working for me.

[JimH]

Please use yadb.  cddb is no longer supported.  Users who registered it in older versions should find it working.

[kentschu]

OK.  Understood.  But a better error message would be helpful...

So, now I have to weigh the advantages of switching from my old program (which uses CDDB) to MJ which doesn't.  I don't know much about YADB - anything good you can share to help convince me that I won't need to constantly enter my own information?

Thanks.

Kent

[KingSparta]

>> anything good you can share to help convince me
Picture A Guy With A Stick Beating A Dead Horse.

[kentschu]

Any  ideas when YADB will be fully integrated into MJ?

For example, when in File Properties, the menu only gives an option to use CDDB.  And when you select "Get Disk Info", it also always uses CDDB regardless of the preference settings.  I guess we have to wait until version 9 to get those little annoyances fixed, huh?

Kent

[JimH]

OK.  Understood.  But a better error message would be helpful...

Total agreement, but it is the message that the CDDB control returns to us.  In the next build, we will just say something like "CDDB seems to be unavailable.  Would you like to try YADB" and then just do it (if you approve).

So, now I have to weigh the advantages of switching from my old program (which uses CDDB) to MJ which doesn't.  I don't know much about YADB - anything good you can share to help convince me that I won't need to constantly enter my own information?

Well, Francis isn't a horse, and Donald O'Conner isn't beating him, but at least it's something: