emplode & empeg-car database field sizes

Posted by: Derek

emplode & empeg-car database field sizes - 20/09/2000 08:18

It would be nice if the field lengths in emplode reflected the field sizes in the empeg-car database. Currently I can type much more into the song and playlist property fields than the empeg-car database will accept, and if I do this in a playlist it trashes the whole playlist and sticks its contents in to the Unattached items folder.

If the Title and Source entries combined are too long, the Year entry is shortened, so I get 20 or 200 instead of 2000 after syncronising (or even nothing!)

Anyone else experienced anything like this? Is it is a problem with the the field lengths in the empeg database and emplode is trying to fit in more than will go?

(cc: [email protected])

(list 6284, Mk1 S/N 00299 4GB blue [for sale]. Mk2 S/N 080000094 6GB blue)
Posted by: peter

Re: emplode & empeg-car database field sizes - 20/09/2000 08:28

It's a bug in the player software, and is fixed in the next release.

Peter


Posted by: bootsy

Re: emplode & empeg-car database field sizes - 20/09/2000 13:24

"If the Title and Source entries combined are too long, the Year entry is shortened, so I get 20 or 200 instead of 2000 after syncronising (or even nothing!)"

I just ran into this problem last night. I tried re-ripping some Negativland albums. Some of the titles were huge... for example, "Negativland - Over The Edge Vol. 7 Part One:Time Zones Exchange Project 07. The Piddle Diddle Report: A Future Confronting the Past which is Our Future, Last Call from Howland Island, Eaten by a Black Hole, Returned to you Rightful Channel"

Ugh... I was experimenting with VBR and thought that was the problem. Then I was worried that the files themselves were too big. Some of these tracks were between 11 and 18 minutes. I greatly reduced the size of the track names and they finally appeared on the empeg, but with the odd truncated dates as you found. Good to hear it's not an isolated case and will be fixed.





Brian H. Johnson
MK2 36GB Blue
"Born to Lose..."
Posted by: empegLover

Re: emplode & empeg-car database field sizes - 21/09/2000 20:58

I seemed to get the same problem with truncated years if the comment field length was too long. I would like to have some indication as to what field lengths will be acceptable before I begin modifying all my v2 ID3 tags. Could we get any indication before release as to what field lengths (if there are limits) would be usable in the empeg database structure of bug fixed version 1.01.

Tom Hitchcock
Posted by: Roger

Re: emplode & empeg-car database field sizes - 22/09/2000 02:21

v1.01 imposes a maximum field length of 255 characters. I don't remember whether that includes the terminator, so stick with 254 characters, and you should be fine.

The problem with v1.0 was that a buffer wasn't large enough, so the total length of all fields was restricted to something like 260 characters. That's been fixed.


Roger - not necessarily speaking for empeg
Posted by: empegLover

Re: emplode & empeg-car database field sizes - 23/09/2000 08:40

Just want to be sure I understand your answer. Will v1.01 allow a maximum 254 characters on each field of a V2 tag? Will the scrolling info line scroll a title that long?

Tom Hitchcock
Posted by: Roger

Re: emplode & empeg-car database field sizes - 25/09/2000 03:21

To clarify: 254 (or 255) characters per field.

Don't know about the scrolling, though.

Roger - not necessarily speaking for empeg