Don: I lost your original message, so let's take it from the top. You say some MP3 file names are not reading properly with this new beta. How did the files get on the Book Port? Can you tell me anything else about the files, such as whether or not they have tags? I need to find such a file to get this fixed. Rob Meredith >>> Don.Barrett@xxxxxx 01/17/06 07:22PM >>> Rob, I can confirm the problem. I put the flash card in a book port running 2.01.00.00 and all of the file names read perfectly; I then put the card back in mine running 2.01.00.22 and at least 1/5 to 1/4 of the mp3 file names did not read correctly at all. Also, with these files whose names did not read correctly, pressing the five key yielded the message "cannot get play time, 0 minutes 0 seconds) no matter how far I was in the file, implying that they were VBR files I guess??? Anyway, something is definitely different and I grant that perhaps track numbers are in the tags, but as I say, version 2.01.00.00 is not having this issue. Can anyone help me out here in explaining this? Thanks Rob and all, Don -----Original Message----- From: bookport-bounce@xxxxxxxxxxxxx [mailto:bookport-bounce@xxxxxxxxxxxxx] On Behalf Of ROB MEREDITH Sent: Tuesday, January 17, 2006 3:15 PM To: bookport@xxxxxxxxxxxxx Subject: [bookport] Re: Book Port Firmware Beta 2.1.0.22 Don: I think this is really more of a problem what is in the ID3V1 tag and not anything to do with the Book Port. For example, if one copies a MP3 file to the device directly and find it has the name "Track1", the file has the name "Track1" imbedded in its ID3 tag. The Book Port has always done this. If its something else, let me know. Rob Meredith >>> Don.Barrett@xxxxxx 01/17/06 02:43PM >>> Rob, Have you been able to verify problems with file names not being spoken fully? -----Original Message----- From: bookport-bounce@xxxxxxxxxxxxx [mailto:bookport-bounce@xxxxxxxxxxxxx]On Behalf Of ROB MEREDITH Sent: Tuesday, January 17, 2006 2:31 PM To: bookport@xxxxxxxxxxxxx Subject: [bookport] Re: Book Port Firmware Beta 2.1.0.22 Chris and others: I am waiting to find out if 4GB is the top for the card size, or if it is unlimited. We will know soon. You may safely assume that it is at least 4GB at this time, as we have tested with this size. Other than the new file sizes I mentioned in a previous message, 16MB for text and 4GB for audio, and the new level commands, not much has changed. It doesn't seem like much, but the size breakthroughs were major changes which took a lot of time. Rob Meredith >>> chris.BP.FL@xxxxxxxxxxxxxxx 01/17/06 01:11PM >>> hello rob meredith, you seem to know more about the beta firmware 2.1.0.22 than said in beta "what's new". can you tell us about the maximum capacity of CF, is it "no issue anymore" or 4GB or maybe still 2?. and what is your comment on the post "[bookport] Summary of new beta features (January 2006) - emai7s" in this list? Chris Sauer. -----Original Message----- From: bookport-bounce@xxxxxxxxxxxxx [mailto:bookport-bounce@xxxxxxxxxxxxx] On Behalf Of ROB MEREDITH Sent: Tuesday, January 17, 2006 15:21 To: bookport@xxxxxxxxxxxxx Subject: [bookport] Re: Book Port Firmware Beta 2.1.0.22 Brian: 1. The new firmware is compatible with old index files. Resending should not be necessary. 2. The maximum file size for text files is 16MB, and the maximum file size for MP3 files is 4GB. 3. I don't think page navigation speeds have been improved. If this is still a problem, let us know. Rob Meredith >>> buhrow@xxxxxxxxxxxxxxxxxxxxx 01/13/06 06:32PM >>> Helo Robert. Here are a couple of questions which might seem obvious, but I'll put them out there none the less. 1. I'm assuming the new firmware is backward compatible with the old index formats, right? That is, I don't need to resend material to the Bookport which is already there just because I update the firmware, right? 2. What are file size limitations now for text and audio files? Can we assume that the 4GB file size limit which applies to files in the FAT32 filesystem is the limiting factor now? 3. In older versions of the firmware, text files with a lot of pages would cause the Bookport to get slower and slower when querying for the current page number with the 0 key as you read further and further into the file. I always assumed that this was because Bookport was scanning the index file to get the page count each time it was asked. With the 4MB file size limitation now gone in the latest beta firmware, it seems likely that documents with more pages would become more common. Does this new firmware perform page counting faster now, given that the old way is fairly slow, and only likely to get worse as files get bigger? Or, as a corolary question, is there a limit to the total number of pages supported in a given text file? I guess I shouldn't limit this to text files, since audio files have pages to, and since the same bad behavior is displayed. -thanks -Brian -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.375 / Virus Database: 267.14.19/231 - Release Date: 1/16/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.375 / Virus Database: 267.14.19/231 - Release Date: 1/16/2006