Uwe Posted October 8, 2013 Report Share Posted October 8, 2013 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 Quote Link to comment Share on other sites More sharing options...
Murat Posted October 9, 2013 Report Share Posted October 9, 2013 Yep. It seems that this is the textual field. Added to the issue queue. Thank you! Quote Link to comment Share on other sites More sharing options...
Uwe Posted April 10, 2014 Author Report Share Posted April 10, 2014 Hello Murat, do you have any news regarding the issue? When (release/build) do you adjust the database format of this field? Regards, Uwe Quote Link to comment Share on other sites More sharing options...
Uwe Posted May 31, 2014 Author Report Share Posted May 31, 2014 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 Quote Link to comment Share on other sites More sharing options...
Uwe Posted March 14, 2015 Author Report Share Posted March 14, 2015 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 Quote Link to comment Share on other sites More sharing options...
Uwe Posted April 27, 2016 Author Report Share Posted April 27, 2016 Hello, is it possible to fix this issue in the next release 5.x? Regards, Uwe Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.