Hello everyone,
I've been using the dBpoweramp cd ripper for about 5 years now and i'm very happy with it.
However, I've just come across what for me was a real mystery. All sorts of problems with MinimServer after ripping a CD with a hard space I didn't know about. I had actually copied it from notepad with Cntrl-C Cntrl-V.
A normal space character hex=20 dec=32 displays the same as a hard space hex=A0 dec=160 but if by bad luck you happen to copy a hard space into the ripper as part of the title or any other field when the disc rips it looks OK but it isn't.
Wherever you have hex=A0 for a space the ripper places both hex=C2 and hex=20 which still show up as just one space but MinimServer picks this up and it makes life interesting to say the least.
Now I know what is happening it isn't a problem but I took me some hours to fathom it out. Why does the ripper replace hex=A0 with hex=C2 hex=20. Could the ripper warn if it spots a hard space, before it rips the disc? Just a suggestion.
Thanks.
Bob.
I've been using the dBpoweramp cd ripper for about 5 years now and i'm very happy with it.
However, I've just come across what for me was a real mystery. All sorts of problems with MinimServer after ripping a CD with a hard space I didn't know about. I had actually copied it from notepad with Cntrl-C Cntrl-V.
A normal space character hex=20 dec=32 displays the same as a hard space hex=A0 dec=160 but if by bad luck you happen to copy a hard space into the ripper as part of the title or any other field when the disc rips it looks OK but it isn't.
Wherever you have hex=A0 for a space the ripper places both hex=C2 and hex=20 which still show up as just one space but MinimServer picks this up and it makes life interesting to say the least.
Now I know what is happening it isn't a problem but I took me some hours to fathom it out. Why does the ripper replace hex=A0 with hex=C2 hex=20. Could the ripper warn if it spots a hard space, before it rips the disc? Just a suggestion.
Thanks.
Bob.
Comment