Software Support > DOS/WinCab

Timer Question - DB Problem - Feature Question

<< < (2/3) > >>

Chris:

--- Quote from: froggerman on April 12, 2007, 05:55:26 pm ---Hi Chris,

I tired your suggestion to turn of the ID3 support and I was able to scan the entire mp3 collection with no problem. This does not produce the same results as the ID3 tags but it should help to localize the problem.

--- End quote ---
Could be a bad tag, but WinCab actually copes with bad tags pretty well.  Now that the collection scanned, can you actually play the songs that bombed out on the scan before or do they die when they play?


--- Quote ---I tried taking out the ampersand for Frankie Valli & The Four Seasons, but that did not change the problem.

--- End quote ---
Odd.  Might be because the ampersand is already in the database.  See if you can manually hack those songs out of the database file (it'll load in a text editor) and see if you can scan it again...


--- Quote ---I have the a small file with the last group of messages from the WinCab log file (Debug leve 5) if you would like to have a look.

--- End quote ---

Logs are always handy!

--Chris

welshmark:
I've had a few strange MP3 files that caused Wincab to exit to Windows.  I took the files, burnt them to cd-rw as a music cd, then ripped them back as MP3 files and manually retagged them.  Cured the problem in every instance.  Never figured out a common denominator though.

froggerman:
Hi Chris,

Sorry to take so long to get back to you but I have had company here and I have not been able to look at this. The problem is being cause by the handling of log ID3 tags. I have examples of the Album tag, the Artist tag and of course the Title tag all causing the problem.

If the tag is 63 characters or longer, WinCab just dies when it processes the tag. If I shorten the tag to 62 characters there is no problem. I have tried it with all 3 tag types and this is the problem each time.

There is no problem with this being from a corrupt database, as this was a new install and when this error occurs, no database is created.

Here are a couple of examples from the WinCab Debug Log:

0:00:07.13-LVL3-INDEXER-LOOP: Working on 02 - I'm Just An Old Chunk Of Coal (But I'm Gonna Be A Diamond Someday).mp3 (5376600 bytes)...
0:00:07.13-LVL4-INDEXER-LOOP: No match (no pointer). File ID=37660002-I
0:00:07.13-LVL4-INDEXER-LOOP: ** ID3 tag found.
0:00:07.17-LVL5-GETID3FIELD: String is Unicode, Raw data: 0 49 0 27 0 6d 0 20
0:00:07.17-LVL5-GETID3FIELD: Converted data: ''

0:00:07.45-LVL3-INDEXER-LOOP: Working on 11 - Are The Good Times Really Over (I Wish A Buck Was Still Silver).mp3 (5088707 bytes)...
0:00:07.45-LVL4-INDEXER-LOOP: No match (no pointer). File ID=08870711-A
0:00:07.45-LVL4-INDEXER-LOOP: ** ID3 tag found.
0:00:07.50-LVL5-GETID3FIELD: String is Unicode, Raw data: 0 41 0 72 0 65 0 20
0:00:07.50-LVL5-GETID3FIELD: Converted data: 'Are The Good Times Really Over (I Wish A Buck Was Still Silver)'

I hope this helps you find the problem, Bryce.

P.S. I did try these same files with other programs and they processed the files without error.

Chris:
WinCab's internal string limit is set at 64 characters.  According to the log these are Unicode strings, so I'm probably not leaving enough buffer space somewhere for the Unicode end-of-string marker.

froggerman:
Hi Chris,

I changed the tags from Unicode to ISO-8859-1. There are no problems processing the ISO-8859-1 tags.

Cheers, Bryce.

Navigation

[0] Message Index

[#] Next page

[*] Previous page