Centrafuse 1.5 Bugs

**kbreeden** · 11-02-2005, 10:31 PM

Originally Posted by justintime

OK, now that is a MAJOR bug right there. I will choose not to ahve this installed on my Carputer until fixed. I was OK with the other issues, but this one can't be ignored

I'm trying to figure out if that's a sarcastic response to my post. This is a pretty big issue for me because it messes up my GPS receiver.

**SnyperBob** · 11-02-2005, 10:47 PM

Originally Posted by alti

shutdown and restart dont work either with centrafuse set as shell or with explorer as shell

hibernate and standby do.

Yeah, this is a pain in the ***. Have to exit out of CF, then shutdown thru windows or another frontend. Lol....

I mean, this is major - can you fix this and shoot out another updated version of CF or something?

**justintime** · 11-03-2005, 06:37 AM

Sarcasm? Hell, no. I'm serious... if I cannot get my GPS to work/launch reliably, there no way I am putting this in my car.

Originally Posted by kbreeden

I'm trying to figure out if that's a sarcastic response to my post. This is a pretty big issue for me because it messes up my GPS receiver.

**Motoko** · 11-03-2005, 07:29 AM

When setting CF to 800x480 in the settings, the right hand side of most windows (GPS, Media etc.) are cut or not lined up properly. CF 1.4 worked perfectly in 800x480.

**kbyrd** · 11-03-2005, 07:57 AM

I might have some insight with the corrupted artist names and such. It's not a display problem, I looked in the data file and those strings (artist, album, etc.) aren't right in there, so I think it's in the tag parsing code.

I played around with a tag editor and I think I now have a sample of the same song file with "broken" tags and "working" tags

"broken" = CF parses it wrong
"working" = CF parsed it correctly

My guess is the CF doesn't handle Unicode ID3 tags correctly. It's just a hunch, but I've been bitten by this type of problem before, and when I diffed the broken and working files the tag characters looked like some sort of wide-chararacter strings rather than plain old c strings. Things like strlen, and such just don't work with Unicode strings. But, the tags almost parse correctly so I'm guessing veetid tried to do unicode support but is assuming 1 byte = 1 character in at least one spot still.

I'm using "Tag and Rename" to edit tags. Under "Options->Program Options->Tags", I unchecked "Write Unicode ID3v2 tags". If I then force the program to resave the tag info for a file and force CF to reload it that file, CF parses it correctly.

veetid, I can send you a before and after of the same mp3 so you can compare and debug, or you can decide unicode is such a pain you don't want to fix it.

**veetid** · 11-03-2005, 09:55 AM

Originally Posted by kbyrd

I might have some insight with the corrupted artist names and such. It's not a display problem, I looked in the data file and those strings (artist, album, etc.) aren't right in there, so I think it's in the tag parsing code.

I played around with a tag editor and I think I now have a sample of the same song file with "broken" tags and "working" tags

"broken" = CF parses it wrong
"working" = CF parsed it correctly

My guess is the CF doesn't handle Unicode ID3 tags correctly. It's just a hunch, but I've been bitten by this type of problem before, and when I diffed the broken and working files the tag characters looked like some sort of wide-chararacter strings rather than plain old c strings. Things like strlen, and such just don't work with Unicode strings. But, the tags almost parse correctly so I'm guessing veetid tried to do unicode support but is assuming 1 byte = 1 character in at least one spot still.

I'm using "Tag and Rename" to edit tags. Under "Options->Program Options->Tags", I unchecked "Write Unicode ID3v2 tags". If I then force the program to resave the tag info for a file and force CF to reload it that file, CF parses it correctly.

veetid, I can send you a before and after of the same mp3 so you can compare and debug, or you can decide unicode is such a pain you don't want to fix it.

your exactly right... it's a unicode issue... I did add some unicode support into 1.5, but did not test that much... send the files over... email to support@fluxmedia.net...

david

**kbyrd** · 11-03-2005, 10:26 AM

Originally Posted by veetid

your exactly right... it's a unicode issue... I did add some unicode support into 1.5, but did not test that much... send the files over... email to support@fluxmedia.net...

david

email sent. Glad I could help.

**ret** · 11-03-2005, 03:09 PM

i think there is a mistake in the english lanuage file:

<FORWARDFINETUNE>Tune +</FORWARDFINETUNE>
<FORWARDTUNE>Finetune +</FORWARDTUNE>

should be switched!!???

**replicant** · 11-03-2005, 06:16 PM

Quick bug that I found, however, it may be related to the performance issues that you've already spoken about. When changing tracks, about 1 out of 3 times it will keep the previous song's title up in the title bar instead of the currently playing song's title.

Thanks David.

**justintime** · 11-03-2005, 06:49 PM

I hope Daivd will have the clarity of mind to allow us to remove the title bar from mbedded applications (like you could do in 1.4).

I am not about to lose precious GPS space from my screen. I use that bar for NADA.