Pa-software community
Help, support and conversation
Welcome! ( login | register )
 
  Forum » Search » Search Results
 

<< prev ... 2, 3, 4, 5, 6 ... next >>
Topic Forum Starter Posts Matches
TLEN erased and other changes MP3 file problems hc 6 2
jamesrae
Member


Member Level

Group: Moderators
Posts: 63
Joined: Dec 13, 2008

The leading zero is not an issue we have had reported before so we will need to investigate why the extension is showing a zero. Would it be possible to send a copy of the track so that we can be sure it is not an issue in the tag.

Posted Feb 16, 2012, 1:11 pm
jamesrae
Member


Member Level

Group: Moderators
Posts: 63
Joined: Dec 13, 2008

The TLEN field was considered depreciated and thus we do not support it. If you would like it to be supported, please contact support and it could be added to the next update or release.

As only one COMM is currently supported the language is of little use, but we are intending to offer multi-comment support which will then require the need to specify the language.

ID3 Editor uses a number for the track and thus no leading zero. This is certainly an option we could add though.

With regards to the Windows issue, could you contact support with an image of this so that we can investigate. Could you also state if the shell extension is used.

Posted Feb 16, 2012, 9:58 am
Expose more columns to Windows Explorer ID3 Editor hc 2 1
jamesrae
Member


Member Level

Group: Moderators
Posts: 63
Joined: Dec 13, 2008

The original artist field is not a column that was part of the predefined OS columns and was not requested in pre-release trials so we did not add it as a custom column. This can of course be added as offering support such as this was the reason for creating the shell extension.

Posted Feb 16, 2012, 11:35 am
Command line parsing bug MP3 file problems hc 4 2
jamesrae
Member


Member Level

Group: Moderators
Posts: 63
Joined: Dec 13, 2008

It is the intention of the parsing to check if the next argument was a command and thus assume the previous argument was missing the data and thus ignore it.
I will recommend this is changed as it is not obvious and not needed for most users.

Posted Feb 16, 2012, 9:33 am
jamesrae
Member


Member Level

Group: Moderators
Posts: 63
Joined: Dec 13, 2008

This does appear to cause the title to be ignored in the CLI and I have requested an investigation so that it can be fixed.

Was this just testing or did you require the line to start with -ti?

Posted Feb 15, 2012, 10:28 pm
Release Date MP3 file problems AllynD 5 1
jamesrae
Member


Member Level

Group: Moderators
Posts: 63
Joined: Dec 13, 2008

Did you change the version to 2.4/auto in the preferences/options of ID3 Editor? As, if the version option is set to 2.3 the assumption is that you want 2.3 compatibility and thus all 2.4 fields will be disabled and removed when the track is updated.

Posted Nov 7, 2011, 9:23 am
Copyright ID3 tag for MP3s not recognised in itunes ID3 Editor rbiz 4 2
jamesrae
Member


Member Level

Group: Moderators
Posts: 63
Joined: Dec 13, 2008

I am afraid that is best put to Apple. I have always thought it was odd but I guess Apple have their reasons.

Posted Nov 2, 2011, 9:57 pm
jamesrae
Member


Member Level

Group: Moderators
Posts: 63
Joined: Dec 13, 2008

ID3 tags do support the copyright field (as per the ISO), but iTunes only shows a copyright field for m4a and m4p files.

Posted Nov 2, 2011, 1:05 pm
id3edcmd.exe usage format in Windows MP3 file problems Troy Mitchell 2 1
jamesrae
Member


Member Level

Group: Moderators
Posts: 63
Joined: Dec 13, 2008

I am afraid the problem is because wildcards are not allowed in the command line editor file names. You need to use a batch script to get the files and then pass them to the editor e.g.:

@echo off
for /r "drive:\path\dir" %%g in (*.mp3) do (
rem echo %%~nxg
"C:\Program Files\Pa-software\Windows ID3 Editor\id3edcmd.exe" -ir "%%~nxg" Folder.jpg
)
pause

Where 'drive:\path\dir' is where the MP3 files reside.

Posted Jun 20, 2011, 12:19 pm
ISRC codes MP3 file problems mcnichols 2 1
jamesrae
Member


Member Level

Group: Moderators
Posts: 63
Joined: Dec 13, 2008

We have adhered to the ID3 ISO standard which states that the 'ISRC' frame should contain the International Standard Recording Code as 12 characters. This means no dashes can be used and although longer codes can be read only 12 will be written.

As far as we could infer from the ISRC handbook, the dashes are for ease of reading only.

The ISRC handbook is available at:
http://www.ifpi.org/content/section_resources/isrc.html

Posted May 30, 2011, 12:27 pm
<< prev ... 2, 3, 4, 5, 6 ... next >>