Audio Identifier is an audio inspector. You can browse through your
audio collection with it and it will show you useful information,
like average bitrate, used encoder and settings, guessed quality etc.
It has Unicode support, the capability of exporting data as HTML and much,
much more.
It supports many audio formats: MPEG Audio (mp3), MPEGplus (mpc),
WAV (wav), TwinVQ (vqf), Ogg Vorbis (ogg), Windows Media Audio (wma),
AAC (aac), Speex (spx), Monkey's Audio (ape), WavPack (wv), FLAC (flac),
TrueAudio (tta), OptimFROG (ofr), AC3 (ac3) and DTS (dts).
Download it here: (Umm, no.)
Audio Identifier is a fork from: Mr QuestionMan
© 2004-2005 by Gambit
http://www.burrrn.net/mrq
(How nice of you to acknowledge that. Now if only you would do the same on your home page, and in the installer, and the documentation...)
In addition to MrQuestionMan, it has the following:
+ a la Encspot file coloring!!! The red level/green level limits can be set
in Settings for each supported extension separately!
+ Ability to scan recursively (with customizable level of recursivity)
+ Ability to export the list (all or only selection) as HTML!
(with or without coloring)
+ Favorites!
+ Unicode support! (on Windows 2000/XP/2003 or newer)
+ Display LAME Tag!!! (right-click on a LAME MP3 file->View LAME Tag)
(thanks phwip for the original code)
+ Drag & drop support (e.g. Drag a folder from Explorer into Mr QM ME)
* Now, selecting a folder does not start scanning by default. Instead, I
introduced a new button "Scan!". Also, there is now an option - "Autoscan"
whose job is to work exactly as previous, e.g. selecting a folder => start
scanning
* New statusbar behaviour: if no files or all filess are selected from the list,
the statusbar will display average bitrate & info for all files (like before).
When selecting several files, the statusbar will display average bitrate &
info only for the selected files
Edit: minor things.
Full Version: Audio Identifier
Yes, it's the ex Mr QuestionMan ME (Miriam Edition).
From now the program is called Audio Identifier.
Hope you like it.
Regards.
From now the program is called Audio Identifier.
Hope you like it.
Regards.
found a bug.
the only difference in AI 0.7alpha1 is that you cannot close the app, only via taskmanager.
the only difference in AI 0.7alpha1 is that you cannot close the app, only via taskmanager.
Cannot reproduce it, think I need some more [advanced] testing.
On my sistem at least -- even if the CD-ROM drive has no CD inserted, no abort/retry/ignore message is displayed.
Actually, that drive acts like an empty folder, so no problem occurs.
PS: Weird bug, anyway.
On my sistem at least -- even if the CD-ROM drive has no CD inserted, no abort/retry/ignore message is displayed.
Actually, that drive acts like an empty folder, so no problem occurs.
PS: Weird bug, anyway.
QUOTE (Miriam @ Mar 28 2005, 04:27 PM)
Cannot reproduce it, think I need some more [advanced] testing.
On my sistem at least -- even if the CD-ROM drive has no CD inserted, no abort/retry/ignore message is displayed.
Actually, that drive acts like an empty folder, so no problem occurs.
do you need any more more info from my side?On my sistem at least -- even if the CD-ROM drive has no CD inserted, no abort/retry/ignore message is displayed.
Actually, that drive acts like an empty folder, so no problem occurs.
QUOTE
PS: Weird bug, anyway.
well, yes. but nevertheless it's there (at least here).
QUOTE (Digga @ Mar 28 2005, 05:30 PM)
do you need any more more info from my side?
If you can you provide even more (more procedural: 1. I open the program ; 2 ... ) info, yes.
Audio Identifier 0.7 alpha 2 released.
Download it here: (Link eaten by the Truncat.)
Changes:
* LAME Tag window now bigger
* Fix the bug when a file without a LAME tag would also be "read". Now, the message "LAME tag not found" is displayed.
Download it here: (Link eaten by the Truncat.)
Changes:
* LAME Tag window now bigger
* Fix the bug when a file without a LAME tag would also be "read". Now, the message "LAME tag not found" is displayed.
I would find it useful to know what tags have been used in my audio files, I suggest a check contained tags feature, a field/column for each tag type with a yes/no displayed for each file/row would would be an easy way of displaying this information.
Some of the tag formats that should be scanned for:
Some of the tag formats that should be scanned for:
- ID3v1/v2
- APEv1/v2
- Lyrics3v1/v2
- Ogg Vorbis comments
When the "Scanning... " screen is displayed should it always be on top? i.e. if I scan a large dir and then switch over to my browser (same for other apps I've tried), the "Scanning... " screen will then appear, after a few seconds delay, on top of my browser. If I click the "Scanning... " screen it takes me to Audio Identifier - that's expected. It's not a biggy but I'd rather leave the "Scanning... " screen in the Audio Identifier program and not have it disturb me when I'm doing other things on my PC (which is XP sp2).
Good job on AI btw
Good job on AI btw
QUOTE (westgroveg @ Mar 28 2005, 06:39 PM)
I would find it useful to know what tags have been used in my audio files, I suggest a check contained tags feature, a field/column for each tag type with a yes/no displayed for each file/row would would be an easy way of displaying this information.
Some of the tag formats that should be scanned for:
Some of the tag formats that should be scanned for:
- ID3v1/v2
- APEv1/v2
- Lyrics3v1/v2
- Ogg Vorbis comments
I've put it on my TO-DO list.
QUOTE (jaybeee @ Mar 28 2005, 06:47 PM)
When the "Scanning... " screen is displayed should it always be on top? i.e. if I scan a large dir and then switch over to my browser (same for other apps I've tried), the "Scanning... " screen will then appear, after a few seconds delay, on top of my browser. If I click the "Scanning... " screen it takes me to Audio Identifier - that's expected. It's not a biggy but I'd rather leave the "Scanning... " screen in the Audio Identifier program and not have it disturb me when I'm doing other things on my PC (which is XP sp2).
Good job on AI btw
Good job on AI btw
Done. It'll come fixed with the next alpha (3).
Conversation continued from the MrQ ME thread...
In the case of Gogo this is not an issue for LameTag as the FTag.Encoder value is the encoder string from the lame tag, and Gogo writes LAME in there. This was discussed here: http://www.hydrogenaudio.org/forums/index....ndpost&p=213969
As for the tool that writes LAME Tags to FhG encoded files, if somebody could give me a link to where I can find this I check what value it writes to the encoder field.
LameTag needs to find some predefined value otherwise there is no way I know of determining whether there actually is a lame tag or not.
QUOTE (westgroveg @ Mar 28 2005, 04:07 PM)
Also note that any mp3 file can have a LAME Tag. A tool was recently written that would write LAME Tags to FhG encoded mp3 files.
QUOTE (rjamorim @ Mar 28 2005, 04:10 PM)
Gogo 3.x also writes LAME tags.
QUOTE (Miriam @ Mar 28 2005, 04:23 PM)
Oh shit.. Updated, please redownload: (On second thought, please don't.)
Now, the "Display LAME tag" option is displayed whenever clicking on a mp3 file regardless of the encoder used - LAME, FHG, Xing etc.
So - it's also a problem for LameTag as can be seen:
( if FTag.Encoder <> 'LAME' then
raise ELameTagReaderExpected.Create('LAME tag not found.');
)
phwip?
Guys, from now on, please use the new Audio Identifier thread
Now, the "Display LAME tag" option is displayed whenever clicking on a mp3 file regardless of the encoder used - LAME, FHG, Xing etc.
So - it's also a problem for LameTag as can be seen:
( if FTag.Encoder <> 'LAME' then
raise ELameTagReaderExpected.Create('LAME tag not found.');
)
phwip?
Guys, from now on, please use the new Audio Identifier thread
In the case of Gogo this is not an issue for LameTag as the FTag.Encoder value is the encoder string from the lame tag, and Gogo writes LAME in there. This was discussed here: http://www.hydrogenaudio.org/forums/index....ndpost&p=213969
As for the tool that writes LAME Tags to FhG encoded files, if somebody could give me a link to where I can find this I check what value it writes to the encoder field.
LameTag needs to find some predefined value otherwise there is no way I know of determining whether there actually is a lame tag or not.
QUOTE (westgroveg @ Mar 28 2005, 08:39 AM)
Some of the tag formats that should be scanned for:
- ID3v1/v2
- APEv1/v2
- Lyrics3v1/v2
- Ogg Vorbis comments
This would be nice... in addition to this, it would also be really great to be able to view the contents of such tags. Perhaps there could be a "viewer window" at the top, or on the side, or something to see all the details of the one particular file, because not very many people would be able to fit it all on one line on their screen.
In addition, being able to customize the fields being viewed would be a nice touch too (possibly being able to move the order of them?). One might implement this (being that there are not more than about 15 fields) by right clicking on the labels and seeing a context menu with a checklist for the available Tech Data or Tag fields.
I'm thinking that adding this to AI would be a lot of work for Miriam, but it would make the program a lot more useful for a lot of people. Perhaps if Miriam feels real ambitious, he can ad some tag editing capabilities as well.
This is a very good program, nice work.
No one really cares much about iTunes encoded mp3, but they do exist and are posted to usenet often. I've probably said this like three times so this will be the last.
I could upload some songs encoded by itunes if you need to see some samples.
I could upload some songs encoded by itunes if you need to see some samples.
QUOTE (Miriam @ Mar 28 2005, 05:03 PM)
QUOTE (Digga @ Mar 28 2005, 05:30 PM)
do you need any more more info from my side?
If you can you provide even more (more procedural: 1. I open the program ; 2 ... ) info, yes.
I've got a file encoded with LAME 3.95, however AI is not able to make a guess what setting has been used. From the LAME-Tag:
everything looks like --preset fast medium...the average bitrate is in the -V4 range too. That's something that could be worked on. I mean, it already says "V4 and q2" in the Quality tag...
Edit: if there's no LAME-Tag why even bother to put a link in the file's context menu?
CODE
Quality: 58 (V4 and q2)
Encoding method: vbr new / vbr mtrh
Lowpass: 18.000Hz
nspsytune: yes
nssafejoint: yes
ATH type: 4
Noise shaping: 1
Stereo mode: joint
Source sample freq: 44.1kHz
Preset: <not stored> - unable to guess
Encoding method: vbr new / vbr mtrh
Lowpass: 18.000Hz
nspsytune: yes
nssafejoint: yes
ATH type: 4
Noise shaping: 1
Stereo mode: joint
Source sample freq: 44.1kHz
Preset: <not stored> - unable to guess
everything looks like --preset fast medium...the average bitrate is in the -V4 range too. That's something that could be worked on. I mean, it already says "V4 and q2" in the Quality tag...
Edit: if there's no LAME-Tag why even bother to put a link in the file's context menu?
I think LAME Tag reading could be left for phwip to work on
Perhaps phwip could work on that?
Perhaps phwip could work on that?
phwip, here is the location for ACMENC. It should work with any ACM encoders from reading the post.
QUOTE (schonenberg)
No one really cares much about iTunes encoded mp3, but they do exist and are posted to usenet often. I've probably said this like three times so this will be the last.
I could upload some songs encoded by itunes if you need to see some samples.
I could upload some songs encoded by itunes if you need to see some samples.
Modifying encoder detection algorithm will take a fair amount of research & time, I think it is best to first focus more easily achievable goals for AI.
QUOTE (schonenberg @ Mar 28 2005, 09:14 PM)
No one really cares much about iTunes encoded mp3, but they do exist and are posted to usenet often. I've probably said this like three times so this will be the last.
I could upload some songs encoded by itunes if you need to see some samples.
I could upload some songs encoded by itunes if you need to see some samples.
You may upload one, but I don't promise anything (see below). Please, if you have the possibility, encode a .wav file twice, one time with iTunes, one time with FHG (Nero). Use please the same encoding parameteres - CBR and, let's say 128 kbits.
Please upload both files.
QUOTE (westgroveg @ Mar 29 2005, 02:47 AM)
I think LAME Tag reading could be left for phwip to work on
Perhaps phwip could work on that?
Perhaps phwip could work on that?
That would be best, IMO.
QUOTE (westgroveg @ Mar 29 2005, 08:22 AM)
Modifying encoder detection algorithm will take a fair amount of research & time, I think it is best to first focus more easily achievable goals for AI.
Agree.
QUOTE (Jojo @ Mar 29 2005, 02:45 AM)
I've got a file encoded with LAME 3.95, however AI is not able to make a guess what setting has been used. From the LAME-Tag:
everything looks like --preset fast medium...the average bitrate is in the -V4 range too. That's something that could be worked on. I mean, it already says "V4 and q2" in the Quality tag...
CODE
Quality: 58 (V4 and q2)
Encoding method: vbr new / vbr mtrh
Lowpass: 18.000Hz
nspsytune: yes
nssafejoint: yes
ATH type: 4
Noise shaping: 1
Stereo mode: joint
Source sample freq: 44.1kHz
Preset: <not stored> - unable to guess
Encoding method: vbr new / vbr mtrh
Lowpass: 18.000Hz
nspsytune: yes
nssafejoint: yes
ATH type: 4
Noise shaping: 1
Stereo mode: joint
Source sample freq: 44.1kHz
Preset: <not stored> - unable to guess
everything looks like --preset fast medium...the average bitrate is in the -V4 range too. That's something that could be worked on. I mean, it already says "V4 and q2" in the Quality tag...
I'll investigate more on this.
QUOTE (Jojo @ Mar 29 2005, 02:45 AM)
Edit: if there's no LAME-Tag why even bother to put a link in the file's context menu?
Good point, actually I've done a trick (implemented in alpha 3), when you right-click, if am mp3 file, the file is scanned for the existance of a LAME tag. If not found, the conext menu item is not shown, otherwise yes.
Regards.
QUOTE (Jojo @ Mar 29 2005, 12:45 AM)
I've got a file encoded with LAME 3.95, however AI is not able to make a guess what setting has been used. From the LAME-Tag:
everything looks like --preset fast medium...the average bitrate is in the -V4 range too. That's something that could be worked on. I mean, it already says "V4 and q2" in the Quality tag...
CODE
Quality: 58 (V4 and q2)
Encoding method: vbr new / vbr mtrh
Lowpass: 18.000Hz
nspsytune: yes
nssafejoint: yes
ATH type: 4
Noise shaping: 1
Stereo mode: joint
Source sample freq: 44.1kHz
Preset: <not stored> - unable to guess
Encoding method: vbr new / vbr mtrh
Lowpass: 18.000Hz
nspsytune: yes
nssafejoint: yes
ATH type: 4
Noise shaping: 1
Stereo mode: joint
Source sample freq: 44.1kHz
Preset: <not stored> - unable to guess
everything looks like --preset fast medium...the average bitrate is in the -V4 range too. That's something that could be worked on. I mean, it already says "V4 and q2" in the Quality tag...
--preset fast medium with 3.95 is Quality 57 (V4 and q3) so it wouldn't match. Besides, there is no preset guessing for preset medium for lame versions 3.93 and higher because if preset medium is used then this is written by lame into the Preset field of the lame tag so there is no need to guess.
phwip,
How about including "Test Music CRC" & "Test Info tag CRC" fields in LAME Tag that could be used to identify if the audio data & LAME Tag are corrupt?
How about including "Test Music CRC" & "Test Info tag CRC" fields in LAME Tag that could be used to identify if the audio data & LAME Tag are corrupt?
Under supported formats, on the homepage, you'd wanna change MPEGplus to Musepack. Very nice app by the way!
QUOTE (westgroveg @ Mar 29 2005, 01:30 PM)
phwip,
How about including "Test Music CRC" & "Test Info tag CRC" fields in LAME Tag that could be used to identify if the audio data & LAME Tag are corrupt?
How about including "Test Music CRC" & "Test Info tag CRC" fields in LAME Tag that could be used to identify if the audio data & LAME Tag are corrupt?
Hi!
I am to implement a such feature in AI, but I have a big problem in identifing things like: where in the file (position) music data starts and where music data ends (making abstraction of header, ID3V1, ID3V2 etc.). PLEASE HELP!!!
Here is the code I wrote so far (hope this helps a bit phwip):
Unit uLameMusic.pas
CODE
unit uLameMusicCRC;
interface
function CRC_update_lookup(value: integer; crc: integer): integer;
implementation
//crc lookup table
const
crc16tab: array[0..255] of integer =
(
$0000, $C0C1, $C181, $0140, $C301, $03C0, $0280, $C241,
$C601, $06C0, $0780, $C741, $0500, $C5C1, $C481, $0440,
$CC01, $0CC0, $0D80, $CD41, $0F00, $CFC1, $CE81, $0E40,
$0A00, $CAC1, $CB81, $0B40, $C901, $09C0, $0880, $C841,
$D801, $18C0, $1980, $D941, $1B00, $DBC1, $DA81, $1A40,
$1E00, $DEC1, $DF81, $1F40, $DD01, $1DC0, $1C80, $DC41,
$1400, $D4C1, $D581, $1540, $D701, $17C0, $1680, $D641,
$D201, $12C0, $1380, $D341, $1100, $D1C1, $D081, $1040,
$F001, $30C0, $3180, $F141, $3300, $F3C1, $F281, $3240,
$3600, $F6C1, $F781, $3740, $F501, $35C0, $3480, $F441,
$3C00, $FCC1, $FD81, $3D40, $FF01, $3FC0, $3E80, $FE41,
$FA01, $3AC0, $3B80, $FB41, $3900, $F9C1, $F881, $3840,
$2800, $E8C1, $E981, $2940, $EB01, $2BC0, $2A80, $EA41,
$EE01, $2EC0, $2F80, $EF41, $2D00, $EDC1, $EC81, $2C40,
$E401, $24C0, $2580, $E541, $2700, $E7C1, $E681, $2640,
$2200, $E2C1, $E381, $2340, $E101, $21C0, $2080, $E041,
$A001, $60C0, $6180, $A141, $6300, $A3C1, $A281, $6240,
$6600, $A6C1, $A781, $6740, $A501, $65C0, $6480, $A441,
$6C00, $ACC1, $AD81, $6D40, $AF01, $6FC0, $6E80, $AE41,
$AA01, $6AC0, $6B80, $AB41, $6900, $A9C1, $A881, $6840,
$7800, $B8C1, $B981, $7940, $BB01, $7BC0, $7A80, $BA41,
$BE01, $7EC0, $7F80, $BF41, $7D00, $BDC1, $BC81, $7C40,
$B401, $74C0, $7580, $B541, $7700, $B7C1, $B681, $7640,
$7200, $B2C1, $B381, $7340, $B101, $71C0, $7080, $B041,
$5000, $90C1, $9181, $5140, $9301, $53C0, $5280, $9241,
$9601, $56C0, $5780, $9741, $5500, $95C1, $9481, $5440,
$9C01, $5CC0, $5D80, $9D41, $5F00, $9FC1, $9E81, $5E40,
$5A00, $9AC1, $9B81, $5B40, $9901, $59C0, $5880, $9841,
$8801, $48C0, $4980, $8941, $4B00, $8BC1, $8A81, $4A40,
$4E00, $8EC1, $8F81, $4F40, $8D01, $4DC0, $4C80, $8C41,
$4400, $84C1, $8581, $4540, $8701, $47C0, $4680, $8641,
$8201, $42C0, $4380, $8341, $4100, $81C1, $8081, $4040
);
function CRC_update_lookup(value: integer; crc: integer): integer;
var
tmp: integer;
begin
tmp := crc or value;
crc := (crc shr 8) or crc16tab[tmp and $ff];
result := crc;
end;
end.
interface
function CRC_update_lookup(value: integer; crc: integer): integer;
implementation
//crc lookup table
const
crc16tab: array[0..255] of integer =
(
$0000, $C0C1, $C181, $0140, $C301, $03C0, $0280, $C241,
$C601, $06C0, $0780, $C741, $0500, $C5C1, $C481, $0440,
$CC01, $0CC0, $0D80, $CD41, $0F00, $CFC1, $CE81, $0E40,
$0A00, $CAC1, $CB81, $0B40, $C901, $09C0, $0880, $C841,
$D801, $18C0, $1980, $D941, $1B00, $DBC1, $DA81, $1A40,
$1E00, $DEC1, $DF81, $1F40, $DD01, $1DC0, $1C80, $DC41,
$1400, $D4C1, $D581, $1540, $D701, $17C0, $1680, $D641,
$D201, $12C0, $1380, $D341, $1100, $D1C1, $D081, $1040,
$F001, $30C0, $3180, $F141, $3300, $F3C1, $F281, $3240,
$3600, $F6C1, $F781, $3740, $F501, $35C0, $3480, $F441,
$3C00, $FCC1, $FD81, $3D40, $FF01, $3FC0, $3E80, $FE41,
$FA01, $3AC0, $3B80, $FB41, $3900, $F9C1, $F881, $3840,
$2800, $E8C1, $E981, $2940, $EB01, $2BC0, $2A80, $EA41,
$EE01, $2EC0, $2F80, $EF41, $2D00, $EDC1, $EC81, $2C40,
$E401, $24C0, $2580, $E541, $2700, $E7C1, $E681, $2640,
$2200, $E2C1, $E381, $2340, $E101, $21C0, $2080, $E041,
$A001, $60C0, $6180, $A141, $6300, $A3C1, $A281, $6240,
$6600, $A6C1, $A781, $6740, $A501, $65C0, $6480, $A441,
$6C00, $ACC1, $AD81, $6D40, $AF01, $6FC0, $6E80, $AE41,
$AA01, $6AC0, $6B80, $AB41, $6900, $A9C1, $A881, $6840,
$7800, $B8C1, $B981, $7940, $BB01, $7BC0, $7A80, $BA41,
$BE01, $7EC0, $7F80, $BF41, $7D00, $BDC1, $BC81, $7C40,
$B401, $74C0, $7580, $B541, $7700, $B7C1, $B681, $7640,
$7200, $B2C1, $B381, $7340, $B101, $71C0, $7080, $B041,
$5000, $90C1, $9181, $5140, $9301, $53C0, $5280, $9241,
$9601, $56C0, $5780, $9741, $5500, $95C1, $9481, $5440,
$9C01, $5CC0, $5D80, $9D41, $5F00, $9FC1, $9E81, $5E40,
$5A00, $9AC1, $9B81, $5B40, $9901, $59C0, $5880, $9841,
$8801, $48C0, $4980, $8941, $4B00, $8BC1, $8A81, $4A40,
$4E00, $8EC1, $8F81, $4F40, $8D01, $4DC0, $4C80, $8C41,
$4400, $84C1, $8581, $4540, $8701, $47C0, $4680, $8641,
$8201, $42C0, $4380, $8341, $4100, $81C1, $8081, $4040
);
function CRC_update_lookup(value: integer; crc: integer): integer;
var
tmp: integer;
begin
tmp := crc or value;
crc := (crc shr 8) or crc16tab[tmp and $ff];
result := crc;
end;
end.
The CRC analysis procedure:
CODE
var
obj: PListItemData;
Reader: TDescriptiveLameTagReader;
ActualCRC, TagCRC: string;
Stream: TTntFileStream;
i, n, music_data_start, music_data_end: integer;
music_data_crc: Word;
buffer: array[0..1000000] of Byte;
begin
if ListView.Selected <> nil then
begin
obj := ListView.Selected.Data;
Reader := TDescriptiveLameTagReader.Create(obj.FileName);
TagCRC := Reader.MusicCRC;
music_data_crc := 0;
if (MPEGAudioFile.ReadFromFile(obj.FileName)) and (MPEGaudioFile.Valid) then
begin
music_data_start := MPEGaudioFile.MPEGStart;
music_data_end := MPEGAudioFile.MPEGEnd;
//!!!!!!!!!!! correct here !!!!!!!!!!!!
if ID3v1Tag.Exists then
music_data_start := music_data_end - ID3v1Tag.TagSize;
if ID3v2Tag.Exists then
music_data_start := music_data_start + ID3v2Tag.Size;
if APETag.Exists then
music_data_end := music_data_end - APETag.Size;
//!!!!!!!!!!! correct here !!!!!!!!!!!!
Stream := TTntFileStream.Create(obj.FileName, fmOpenRead or fmShareDenyNone);
try
Stream.Seek(music_data_start, soFromBeginning);
repeat
n := Stream.Read(buffer, SizeOf(buffer));
if Stream.Position > music_data_end then
n := n - (Stream.Position - music_data_end);
for i := 0 to n - 1 do
music_data_crc := CRC_update_lookup(buffer[i], music_data_crc);
until Stream.Position >= music_data_end;
finally
Stream.Free;
end;
end;
ActualCRC := IntToHex(music_data_crc, 4);
if ActualCRC = TagCRC then
MessageInfo('File CRC ok.') else
MessageWarning(WideFormat('File is corrupted (Actual CRC: %s, CRC from Tag: %s)', [ActualCRC, TagCRC]));
Reader.Free;
end;
obj: PListItemData;
Reader: TDescriptiveLameTagReader;
ActualCRC, TagCRC: string;
Stream: TTntFileStream;
i, n, music_data_start, music_data_end: integer;
music_data_crc: Word;
buffer: array[0..1000000] of Byte;
begin
if ListView.Selected <> nil then
begin
obj := ListView.Selected.Data;
Reader := TDescriptiveLameTagReader.Create(obj.FileName);
TagCRC := Reader.MusicCRC;
music_data_crc := 0;
if (MPEGAudioFile.ReadFromFile(obj.FileName)) and (MPEGaudioFile.Valid) then
begin
music_data_start := MPEGaudioFile.MPEGStart;
music_data_end := MPEGAudioFile.MPEGEnd;
//!!!!!!!!!!! correct here !!!!!!!!!!!!
if ID3v1Tag.Exists then
music_data_start := music_data_end - ID3v1Tag.TagSize;
if ID3v2Tag.Exists then
music_data_start := music_data_start + ID3v2Tag.Size;
if APETag.Exists then
music_data_end := music_data_end - APETag.Size;
//!!!!!!!!!!! correct here !!!!!!!!!!!!
Stream := TTntFileStream.Create(obj.FileName, fmOpenRead or fmShareDenyNone);
try
Stream.Seek(music_data_start, soFromBeginning);
repeat
n := Stream.Read(buffer, SizeOf(buffer));
if Stream.Position > music_data_end then
n := n - (Stream.Position - music_data_end);
for i := 0 to n - 1 do
music_data_crc := CRC_update_lookup(buffer[i], music_data_crc);
until Stream.Position >= music_data_end;
finally
Stream.Free;
end;
end;
ActualCRC := IntToHex(music_data_crc, 4);
if ActualCRC = TagCRC then
MessageInfo('File CRC ok.') else
MessageWarning(WideFormat('File is corrupted (Actual CRC: %s, CRC from Tag: %s)', [ActualCRC, TagCRC]));
Reader.Free;
end;
Hope this helps!
Now, you Help me!
Vlad.
I think your software is very good, but it is not so much different from MrQuestionman. If you really want to improve it you should consider reviewing the whole detection engine: EncSpot is still A LOT better in guessing the codec: ie your software doesn't detect Plugger or Qdesign encoders, which imo are the two worst encoders ever made...
Bye!
Bye!
QUOTE (giopiar @ Mar 29 2005, 12:37 PM)
Plugger or Qdesign encoders, which imo are the two worst encoders ever made...
Plugger is just a dist10 compile, and in that aspect, is no different than SoloH, Cannamp3, etc.
For a high quality detection engine, look for Feltzkrone, wherever he might be :B
When I select some files and choose to play them, only one file is added to the playlist (foobar2000 0.8.3). Is it a bug or feature?
If feature, is it possible to add "play all" option"?
Thanks!
If feature, is it possible to add "play all" option"?
Thanks!
One of my problems:
It's still not reading the encoder info/tags to display the proper quality. And yes, that last song is encoded correctly.
It's still not reading the encoder info/tags to display the proper quality. And yes, that last song is encoded correctly.
Yes, MPC quality should be rated by profile not bit-rate.
Miriam maybe phwip can help you with that code.
Miriam maybe phwip can help you with that code.
I tried to get AI to analyze a wav file using auCDtect but a window flashes up for a second and disapears again...I'm on Win2000
QUOTE (Jojo @ Mar 30 2005, 10:40 AM)
I tried to get AI to analyze a wav file using auCDtect but a window flashes up for a second and disapears again...I'm on Win2000
I can confirm this. Is auCDtect functional yet?
QUOTE (westgroveg @ Mar 29 2005, 02:44 PM)
QUOTE (Jojo @ Mar 30 2005, 10:40 AM)
I tried to get AI to analyze a wav file using auCDtect but a window flashes up for a second and disapears again...I'm on Win2000
I can confirm this. Is auCDtect functional yet?
yep, it should work...I just used it...
it would be nice if deleting (DEL-Key) and renaming files would work...
Hello Guys!
Thank you for feature/bug reporting.
I've just released version 0.7 alpha 3. that should thank you. (ChangFest & Jojo).
(Link removed.)
Changes:
ADD New very nice menu/toolbars skinning system. You can change the default skin (Dream) from View->Skins
ADD Some work on the quality estimation engine for MPC & Vorbis files. All MPC quality profiles (standard, extreme, insane, braindead) are automatically marked as "Good".
FIX "Scan with auCDtect" righ-click option was broken since 0.7 alpha 1 (.bat files seems to not support Unicode!)
CH Again, LAME Tag window now bigger
FIX "Display LAME tag" (right-click) is now shown only if the mp3 file really has a LAME tag
Enjoy.
Thank you for feature/bug reporting.
I've just released version 0.7 alpha 3. that should thank you. (ChangFest & Jojo).
(Link removed.)
Changes:
ADD New very nice menu/toolbars skinning system. You can change the default skin (Dream) from View->Skins
ADD Some work on the quality estimation engine for MPC & Vorbis files. All MPC quality profiles (standard, extreme, insane, braindead) are automatically marked as "Good".
FIX "Scan with auCDtect" righ-click option was broken since 0.7 alpha 1 (.bat files seems to not support Unicode!)
CH Again, LAME Tag window now bigger
FIX "Display LAME tag" (right-click) is now shown only if the mp3 file really has a LAME tag
Enjoy.
Some nice improvements here... the skinning engine is pretty, and helps to give AI its own look and feel, to distinguish it from MQM. (That leads me to conclude that Miriam has big plans for this program... )
I was wondering though...
Is that one of Gambit's jokes? That's the first time I've looked at a WMA file in this program. There really is no useful encoder info to pull out of it, and display version number or something instead?
I was wondering though...
Is that one of Gambit's jokes? That's the first time I've looked at a WMA file in this program. There really is no useful encoder info to pull out of it, and display version number or something instead?
QUOTE (Supacon @ Mar 29 2005, 10:07 PM)
Is that one of Gambit's jokes?
Right. Same happens if you use it on a VQF.
QUOTE (Supacon @ Mar 30 2005, 01:07 PM)
Is that one of Gambit's jokes? That's the first time I've looked at a WMA file in this program. There really is no useful encoder info to pull out of it, and display version number or something instead?
yeah, I think it's best to remove this kind of garbage, display "Windows Media Audio" & if possible the version string & type (pro/standard).
QUOTE (Miriam @ Mar 29 2005, 03:30 PM)
I've just released version 0.7 alpha 3. that should thank you. (ChangFest & Jojo).
Yep. I appreciate the timely correction! The skins are a nice feature as well.
QUOTE (westgroveg)
yeah, I think it's best to remove this kind of garbage, display "Windows Media Audio" & if possible the version string & type (pro/standard).
I still like Gambit's "garbage" aka humor. Although it leads to less professional programs.
QUOTE (westgroveg @ Mar 29 2005, 11:22 PM)
QUOTE (Supacon @ Mar 30 2005, 01:07 PM)
Is that one of Gambit's jokes? That's the first time I've looked at a WMA file in this program. There really is no useful encoder info to pull out of it, and display version number or something instead?
yeah, I think it's best to remove this kind of garbage, display "Windows Media Audio" & if possible the version string & type (pro/standard).
i thought it was kinda funny, and a good idea, i mean, all of us that are educated about quality in audio formats know that wma is not a perfered codec by any means... maybe a pro/std denotation would be nice, but its true, i am ashamed of the wma's i have. all of them were made before my discovery of ha.org...
I have always been suspcious of WMAs, even when most uneducated about digital audio many years ago. But I still always end up with a few, whether it's from trading with friends, or peer to peer, or just because they are offered for download.
Because they do have some (unfortunate) established user basis, they should be supported just like any other codec in this program.
It might also be nice for AI to display if they are DRM as well... No need to keep around stuff that you can't use (that is, if you don't have the corresponding license).
Because they do have some (unfortunate) established user basis, they should be supported just like any other codec in this program.
It might also be nice for AI to display if they are DRM as well... No need to keep around stuff that you can't use (that is, if you don't have the corresponding license).
QUOTE (Digga @ Mar 28 2005, 03:54 PM)
found a bug.
the only difference in AI 0.7alpha1 is that you cannot close the app, only via taskmanager.
strangly, this issue is no more present with alpha3.
the only difference in AI 0.7alpha1 is that you cannot close the app, only via taskmanager.
westgroveg asked me if i could help with this cause he knows i've been working on some stuff that sounds like that...
@Miriam: i can provide you library which returns hashes you need, i have only to change its format, now it uses MD5.
[EDIT]
but...that crc is about what ? what has been hashed ? tags. which tags. before, after audio ? all tags ? only ID3, only APE ?
@Miriam: i can provide you library which returns hashes you need, i have only to change its format, now it uses MD5.
[EDIT]
but...that crc is about what ? what has been hashed ? tags. which tags. before, after audio ? all tags ? only ID3, only APE ?
thanks sn0w 
The "Music CRC" is a hash of the audio data the "Info tag CRC" is a hash of the Lame Tag.
The "Music CRC" is a hash of the audio data the "Info tag CRC" is a hash of the Lame Tag.
No, it's not a joke, Audio Identifier 0.7 alpha 4 released.
(This program is illegal. No joke.)
LOT of changes.
ADD Lots of GUI improvements, more consistent design across all windows. The file list looks now much better
CH Separated columns for Encoder and Encoding Options. Encoder column is now bold
ADD Audio Identifier now sorts automatically the window after scanning. The default sort column is "File Name"
ADD Drop-down folder-list above the folder tree list (some people access folders more quickly this way)
CH Encoder column shortened for MP3 (whitout MPEG 1 Layer III)
ADD Right->clic Play now plays all the selected files in list. :-)
ADD New fields in Lame Tag window (right-click->Display Lame Tag): Actual Tag Info CRC, Actual Music CRC (thanks phwip for the code). The new code is based on a modified version of 0.4 rc1 - unreleased at this moment :-)
Enjoy!
(This program is illegal. No joke.)
LOT of changes.
ADD Lots of GUI improvements, more consistent design across all windows. The file list looks now much better
CH Separated columns for Encoder and Encoding Options. Encoder column is now bold
ADD Audio Identifier now sorts automatically the window after scanning. The default sort column is "File Name"
ADD Drop-down folder-list above the folder tree list (some people access folders more quickly this way)
CH Encoder column shortened for MP3 (whitout MPEG 1 Layer III)
ADD Right->clic Play now plays all the selected files in list. :-)
ADD New fields in Lame Tag window (right-click->Display Lame Tag): Actual Tag Info CRC, Actual Music CRC (thanks phwip for the code). The new code is based on a modified version of 0.4 rc1 - unreleased at this moment :-)
Enjoy!
QUOTE (Miriam @ Mar 31 2005, 03:51 PM)
ADD Right->clic Play now plays all the selected files in list. :-)
Thank you for it
some bugs:
- highlight the scan-level and overwrite it, then press scan...the new value won't be used
- I had a CD in my CD drive and removed it, all of a sudden AI started to scan my entire computer for music files (scan level was set to 0)...but even when it was set to 1 AI refreshes that list every time I reject/insert a CD...
I just noticed that there's a even bigger issue. It seems like everytime something changes, the list is refreshed. For instance if you export the file list and save it on your desktop...or if the scan level is set to 0 it automatically scans your entire hard drive even though I was in a sepcific folder...
otherwise good job!
p.s.: your computer time seems to be one day ahead
- highlight the scan-level and overwrite it, then press scan...the new value won't be used
- I had a CD in my CD drive and removed it, all of a sudden AI started to scan my entire computer for music files (scan level was set to 0)...but even when it was set to 1 AI refreshes that list every time I reject/insert a CD...
I just noticed that there's a even bigger issue. It seems like everytime something changes, the list is refreshed. For instance if you export the file list and save it on your desktop...or if the scan level is set to 0 it automatically scans your entire hard drive even though I was in a sepcific folder...
otherwise good job!
p.s.: your computer time seems to be one day ahead
Alright Miriam! Thanks for the little directory input field. I'm lovin' it already. The program looks better every day.
I was wondering what happened with the ability to drag folders in from explorer, et al. It seems that is gone completely now... A work in progress, I suppose?
Now here comes the scary part... MORE FEATURE REQUESTS!
I'll let others "vote" on which they think are the most useful, or important.
-Ability to drag & drop files from AI into a playlist (i.e. Winamp/Foobar), or explorer folder
-Display tag type: First, display the tag types present, APEv1, APEv2, ID3v1/v2.3, Lyrics3, Vorbis, Flac, et al.
-Add a toggleable side/top/bottom panel that actually shows the contents of the tag, in a human readable format.
-Add a context menu option that allows a human to view the raw tag (If this is useful, which I think it could be, for troubleshooting, etc.)
jtclipper also had some suggestions - I'm not sure if he intended them to be specifically for AI, but they can certainly apply:
Maybe if we're really nice to him, he'll help out the AI project
He certainly has the relevant abilities.
I was wondering what happened with the ability to drag folders in from explorer, et al. It seems that is gone completely now... A work in progress, I suppose?
Now here comes the scary part... MORE FEATURE REQUESTS!
I'll let others "vote" on which they think are the most useful, or important.
-Ability to drag & drop files from AI into a playlist (i.e. Winamp/Foobar), or explorer folder
-Display tag type: First, display the tag types present, APEv1, APEv2, ID3v1/v2.3, Lyrics3, Vorbis, Flac, et al.
-Add a toggleable side/top/bottom panel that actually shows the contents of the tag, in a human readable format.
-Add a context menu option that allows a human to view the raw tag (If this is useful, which I think it could be, for troubleshooting, etc.)
jtclipper also had some suggestions - I'm not sure if he intended them to be specifically for AI, but they can certainly apply:
QUOTE (jtclipper @ Mar 30 2005, 03:45 AM)
an explorer tree on the left, a grid on the right with a few columns, support for all formats + mp4 support , export to xml,html,xls,txt,m3u,pls, parametric color coding based on bitrate and tag usage, a bottom level panel displaying the contents and version of the tags used + album art if it exists in the tag , if not read a .jpg/.png/.bmp/.gif from the same folder..
Maybe if we're really nice to him, he'll help out the AI project
He certainly has the relevant abilities.
QUOTE (Supacon @ Mar 31 2005, 04:53 PM)
Maybe if we're really nice to him, he'll help out the AI project
He certainly has the abilities, but I would not count on that....
see here:
http://www.hydrogenaudio.org/forums/index....topic=32794&hl=
edit: added link
The feature I'd most like to see implemented is a corruption scanner (think sync error detection in encspot) for the various file types. That's by far the most important piece of information to me regarding compressed files.
ok, some more stuff
- when highlighting files the quality column should keep it's color
- when sorting the column 'encoder options', -V2: preset standard and [alt-]preset standard should be treated equally since it's the same setting. But then, I wouldn't mix them all together, therefore I suggest to list them in groups: -V2... first and directly followed by [alt-]p...this also applies for -V0 + --preset standard and so on...
- when selecting several files and displaying the lame tag it should be displayed for every file and not just the first file (or at least the file that I right clicked on)
- mp3 files that have a LAME-Tag but no preset stored show up as "<not stored>", however files that don't have a LAME Tag display nothing at all. Therefore, I'd remove the "<not stored>" string at all. Maybe you could underline the name of the encoder to indicate whether the file contains a LAME-Tag.
- when selecting several files by holding down the shift key and using the page-up/down key, the file info in the infobar is not updated
- Gogo files are recognized as FhG
In addition: I've found a file that is recognized as LAME but by looking at the EncSpot graphs it's definitely not LAME. EncSpot reports it as FhG (fastenc, low quality mode)
Also, once people can decide what columns they'd like to have, it would be nice to offer many options...such as "Stereo Type", "Bad Last Frame", "Frequency", "Number of Frames", "Sync Errors", "ID3 Tag Information", "LAME Tag Info's"...etc. etc. you can take EncSpot as inspiration since it offers at least 35 different columns...
- when highlighting files the quality column should keep it's color
- when sorting the column 'encoder options', -V2: preset standard and [alt-]preset standard should be treated equally since it's the same setting. But then, I wouldn't mix them all together, therefore I suggest to list them in groups: -V2... first and directly followed by [alt-]p...this also applies for -V0 + --preset standard and so on...
- when selecting several files and displaying the lame tag it should be displayed for every file and not just the first file (or at least the file that I right clicked on)
- mp3 files that have a LAME-Tag but no preset stored show up as "<not stored>", however files that don't have a LAME Tag display nothing at all. Therefore, I'd remove the "<not stored>" string at all. Maybe you could underline the name of the encoder to indicate whether the file contains a LAME-Tag.
- when selecting several files by holding down the shift key and using the page-up/down key, the file info in the infobar is not updated
- Gogo files are recognized as FhG
In addition: I've found a file that is recognized as LAME but by looking at the EncSpot graphs it's definitely not LAME. EncSpot reports it as FhG (fastenc, low quality mode)
Also, once people can decide what columns they'd like to have, it would be nice to offer many options...such as "Stereo Type", "Bad Last Frame", "Frequency", "Number of Frames", "Sync Errors", "ID3 Tag Information", "LAME Tag Info's"...etc. etc. you can take EncSpot as inspiration since it offers at least 35 different columns...
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.