| |
Pa-software community
Help, support and conversation |
|
| |
|
|
|
|
| << prev 1 next >> |
hc
Newbie
Group: Members
Posts: 8
Joined: Feb 15, 2012
|
The original file was produced with
Code: 1
lame --id3v2-only --id3v2-utf16 --tt "Aņil" --tn "05" test.mp3
The file was processed with a batch file that has the following content:
Code: 1
2
chcp 65001
"C:\Program Files\ID3 Editor\id3edcmd.exe" -vn 2.3 -tr "5" -ti "Aņil" test.mp3
I tried with and without the first line. After your post, I have also tweaked the batch file to include correct utf-8 characters:
The after and before:
This is how they look in explorer
These issues do reproduce on both of my Windows 64 machines.
Where can I send you the files?
|
|
|
Posted Feb 18, 2012, 3:25 pm |
|
|
|
hc
Newbie
Group: Members
Posts: 8
Joined: Feb 15, 2012
|
I bought a license of id3 editor yesterday. Unfortunately, today I found another bug(?).
When called from the command line in Windows 7 64 bits,
"C:\Program Files\ID3 Editor\id3edcmd.exe" -vn 2.3 -ti "Aņil" someFile.mp3
id3editor chokes at the non-7-bits characters. That is not a problem in the GUI, only in the command line. I tried several things like:
- setting codepages 437, 1252, 65000, 65001, or 28591
- launching the 64 bit version or cmd.exe and launching the 32 bit version of cmd.exe
- launching from unicode autohotkey.
The help states that -ti can be followed by any utext, where utext is unicode. Am I missing something?
++hc
|
|
|
Posted Feb 17, 2012, 3:07 pm |
|
|
|
hc
Newbie
Group: Members
Posts: 8
Joined: Feb 15, 2012
|
|
I used the tagging switches of lame 3.99.4 (64 bit version). Encode any tag with the latest lame and use the shell extension in Windows 7 64 bits to reproduce the behavior.
|
|
|
Posted Feb 17, 2012, 3:09 pm |
|
|
|
hc
Newbie
Group: Members
Posts: 8
Joined: Feb 15, 2012
|
| jamesrae said: |
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.
|
Yes, the shell extension was used.
As for a picture showing the Windows issue, it will just show a zero for files that were tagged (by another program) with a leading zero in the track-number column. Files tagged by ID3Editor will show just fine.
Except for the Windows issue, none of the other issues are deal breakers. Even the Windows issue is not a big deal for me since I plan to use ID3Editor in a batch file to re-tag all of my library (that is the reason I am testing carefully before I commit).
|
|
|
Posted Feb 16, 2012, 10:30 am |
|
|
|
hc
Newbie
Group: Members
Posts: 8
Joined: Feb 15, 2012
|
If the command line is used to set some tags, then TLEN is erased, COMM assumes English language, and TRCK is stripped from any leading zero.
After installing ID3Editor in Windows x64, if the track number (TRCK) had a leading zero (e.g. 07) then windows explorer displays only zero (instead of "7" as before the installation).
|
|
|
Posted Feb 15, 2012, 7:56 pm |
|
|
|
hc
Newbie
Group: Members
Posts: 8
Joined: Feb 15, 2012
|
|
It would be nice if ID3 Editor would expose other tags to the shell extensions. For example, I cannot find a way to expose the Original Artist tag in Windows 7 64 bits. I know it is in my files but it is not available among the Explorer columns.
|
|
|
Posted Feb 16, 2012, 10:39 am |
|
|
|
hc
Newbie
Group: Members
Posts: 8
Joined: Feb 15, 2012
|
|
Testing before buying ... I do not recall any song that begins with -ti. But in any case, there is an error in the parsing logic. Nevertheless, I will buy it shortly.
|
|
|
Posted Feb 16, 2012, 12:51 am |
|
|
|
hc
Newbie
Group: Members
Posts: 8
Joined: Feb 15, 2012
|
If the command line interface is called with the parameters
"C:\Program Files\ID3 Editor\id3edcmd.exe" -ti "-ti" test.mp3
then the title is not set to -ti as expected.
|
|
|
Posted Feb 15, 2012, 7:55 pm |
|
|
|
| << prev 1 next >> |
v2.0.6 © Pa-software 2005-2015
|
