Jump to content

889 - 1443 - Format of the Audio Tag "Track"


Uwe
 Share

Recommended Posts

Hello,

 

the format of the Audio Tag "Track" is INTEGER in the database:

 

CREATE TABLE music

(

id_mediaitem bigserial NOT NULL,

musictitle text,

musicalbum text,

musictrack integer,

musicconductor text DEFAULT ''::text,

CONSTRAINT music_pkey PRIMARY KEY (id_mediaitem),

CONSTRAINT fkec5148079151a056 FOREIGN KEY (id_mediaitem)

REFERENCES mediaitems (id) MATCH SIMPLE

ON UPDATE NO ACTION ON DELETE NO ACTION

)

WITH (

OIDS=FALSE

);

ALTER TABLE music

OWNER TO postgres;

 

That leads to the situation that leading "0" are not saved in the database. Also the syntax 1/11 is not possible because of the INTEGER format.

As far as I understand the ID3 spec the tag "Track" is NUMERIC CHAR. From my point of view Daminion should use the NUMERIC CHARACTER format for this field in the database.

 

http://id3lib.sourceforge.net/id3/id3v2-00.txt

 

TRK

The 'Track number/Position in set' frame is a numeric string

containing the order number of the audio-file on its original

recording. This may be extended with a "/" character and a numeric

string containing the total numer of tracks/elements on the original

recording. E.g. "4/9".

 

Regards, Uwe

Link to comment
Share on other sites

  • 6 months later...
  • 1 month later...

Hello,

 

in build 1019 the format of the musictrack is "text" now. That's ok.

 

CREATE TABLE music

(

id_mediaitem bigserial NOT NULL,

musictitle text,

musicalbum text,

musictrack text,

musicconductor text DEFAULT ''::text,

CONSTRAINT music_pkey PRIMARY KEY (id_mediaitem),

CONSTRAINT fkec5148079151a056 FOREIGN KEY (id_mediaitem)

REFERENCES mediaitems (id) MATCH SIMPLE

ON UPDATE NO ACTION ON DELETE NO ACTION

 

But: it's written as an integer value to the database. That means: I enter the value "01" in the Properties Panel but in the database is "1" and when I read tags from file the "01" is overwritten by the "1".

 

Regards, Uwe

Link to comment
Share on other sites

  • 9 months later...

Hello,

 

am I wrong or did you really go back to the INTEGER format of the musictrack? If this is true: why and is it possible to adjust it in the official 3.7 release because there were some adjustments compared to 3.4? Why not in this case to adjust it in the database and the UI?

 

CREATE TABLE music

(

id_mediaitem bigserial NOT NULL,

musictitle text,

musicalbum text,

musicconductor text,

musictrack integer,

CONSTRAINT music_pkey PRIMARY KEY (id_mediaitem)

)

WITH (

OIDS=FALSE

);

ALTER TABLE music

OWNER TO postgres;

 

Regards, Uwe

Link to comment
Share on other sites

  • 1 year later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...