BUG in 3.108- Using ZIP file conversion

[admin]

Originally Posted by thebyrds

What about the Brand window and the discID window? I've got all my mp3+g zip files in folders by first the brand then by discID. Before this error started occuring when I tried to convert zip I clicked on the first song of the cdg and clicked open, it had the Brand window filled and the discID. Now nothing comes up in the Brand window but the discID is there. I type in the brand such as CHARTBUSTER then the right discID is still there. I go and select all then process. A window pops up to tell me that this is a invalid discID. Is there something need to fix on my end or will 3.109 take care of this problem?

We do NOT detect folder names to establish your Brand and DiscID. We only use the Filename "field" contents. It would be a very different algorithm to key off the "path" the filenames are in. It may be possible and I'll add that to our spec for discussion.

The reason SOME files you are importing capture the Brand (which is not embedded as a field in your filenames that we look at), is that our code takes the DiscID, looks for it in the Import Database, then the Songs Database and if we find it, we can add the Brand in its field. Also, if your Title and Artist are not defined in a file, but the DiscID is in our Databases, we will automatically provide the Title and Artist for each track.

If your DiscID is not in our Databases, you must type in the Brand field.

As to the DiscID being reported missing when it is there, that sounds like a bug. If you can give us as much info as you can, so we can duplicate the problem, then we can solve the problem. For example:

1. Post the entire path name to a folder holding files you are having a problem with.

2. Post a typical entire filename so we can see what field-delimiter-field-delimiter-field etc. format you are using. Make sure you post a TYPICAL filename. We found in some cases while we were developing and debugging that if TRACK 1 failed, weird things happened. We thought we solve that, but maybe there is another bug our Beta Testers didn't activate.

It happens. These are new and extremely complex features we have added. I'm sure you folks will discover bugs. I commit that we will work on the bugs you find until they are fixed, or we realize there is no fix and the filenames must be edited. The variable nature of unknown and varying filenames is something that is very hard to work with. Since we KNOW the filename structure and the delimiters that (you define it in the Template dialog, we may be able to add logic to ignore all symbols (, . etc) that appear between the delimiters.

Keep in mind that bug/problem reports can stretch out over several weeks or months with a new release like 3.108. We'll try to get out a new release as soon as we fix currently identified bugs.

It is important to identify work-arounds for each reported problem to keep everyone importing, until we can duplicate the problem and create a permanent solution.