Tau Analyzer version 1.2 (Freeware) has been released.
Known bugs fixed.
Tau Analyzer - the program for determining the authenticity of musical CD, and predicting is it an original studio records or a reconstruction from a lossy encoded data (for example MP3 files). Tau Analyzer works directly with CD and has a some additional functions such as a Spectrum and Frequency analyzers, ATIP and ISRC data readers, etc.
Download Tau Analyzer version 1.2 (Windows Installer, Freeware) (http://www.true-audio.com/ftp/TauAnalyzer-setup.exe)
References
Tau Analyzer version 1.1 discussion:
http://www.hydrogenaudio.org/forums/index....showtopic=31394 (http://www.hydrogenaudio.org/forums/index.php?showtopic=31394)
Best wishes!
-- Alexander Djourik
http://www.true-audio.com (http://www.true-audio.com)
Nice! No crashing no more...
Tau Analyzer version 1.2 (Freeware) has been released.
Known bugs fixed.
http://www.true-audio.com (http://www.true-audio.com)
[a href="index.php?act=findpost&pid=274053"][{POST_SNAPBACK}][/a]
still doesn't work under Windows 2000...
all issues I experienced before are now fixed, ty
still doesn't work under Windows 2000...
[a href="index.php?act=findpost&pid=274125"][{POST_SNAPBACK}][/a]
Please describe your system.. maybe I can help?
or better send to me the drwtsn32.log after crash.
(Usually C:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\drwtsn32.log)
all issues I experienced before are now fixed, ty
[a href="index.php?act=findpost&pid=274126"][{POST_SNAPBACK}][/a]
No critical errors were found in the program, just some of optimizations (like SSE2) are disabled now. We has fixed some of potential bugs only.. And, as I wrote above, some of interface modifications has been made also.
2 ALL: I can't fix the List Control blinking.. Somebody know a solution?
still doesn't work under Windows 2000...
[a href="index.php?act=findpost&pid=274125"][{POST_SNAPBACK}][/a]
Please describe your system.. maybe I can help?
or better send to me the drwtsn32.log after crash.
(Usually C:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\drwtsn32.log)
[a href="index.php?act=findpost&pid=274157"][{POST_SNAPBACK}][/a]
I already described the problem when 1.0 was released...when I start the program it says that same dll couldn't be found...
Now works for me, thanks a lot ald!
I am using auCDtect version 0.8 (Linux) and it seems to be doing it's job quite nicely, but after each file it spits out an error:
[eric@travsys tmp]$ auCDtect 04.la_grange.wav
auCDtect: CD records authenticity detector, version 0.8.2
Copyright (c) 2004 Oleg Berngardt. All rights reserved.
Copyright (c) 2004 Alexander Djourik. All rights reserved.
------------------------------------------------------------
Processing file: [04.la_grange.wav]
Data analysis: [100%]
------------------------------------------------------------
This track looks like CDDA with probability 100%
*** glibc detected *** double free or corruption (!prev): 0x080a4008 ***
Aborted
Like I said, it appears to be working. I just wanted to let you know (if you don't already).
--
Fedora Core 3
still doesn't work under Windows 2000...
[a href="index.php?act=findpost&pid=274125"][{POST_SNAPBACK}][/a]
Please describe your system.. maybe I can help?
or better send to me the drwtsn32.log after crash.
(Usually C:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\drwtsn32.log)
[a href="index.php?act=findpost&pid=274157"][{POST_SNAPBACK}][/a]
I already described the problem when 1.0 was released...when I start the program it says that same dll couldn't be found...
[a href="index.php?act=findpost&pid=274227"][{POST_SNAPBACK}][/a]
I had the same problem with Windows 2000. The missing dll for me was gdiplus.dll. I did a search on my machine, found the file in the foobar directory, copied it to the Tau Analyser directory, and the program now runs without a hitch. I suggest you give this a try.
I already described the problem when 1.0 was released...when I start the program it says that same dll couldn't be found...
[{POST_SNAPBACK}][/a] (http://index.php?act=findpost&pid=274227")
About gdiplus.dll. Its not a error. If I understood of the GDI+ license correctly - I can't to include gdiplus.dll in my distribution package, but you can download it by yourself. As I have wrote at our site:
Windows NT/2000 usage requires installation of the GDI+ package from MicrosoftThus, you can try to get gdiplus.dll from Microsoft directly:
[a href="http://msdn.microsoft.com/library/en-us/gdicpp/gdiplus/gdiplus.asp]http://msdn.microsoft.com/library/en-us/gd...lus/gdiplus.asp[/url]
http://msdn.microsoft.com/isapi/gomscom.as...&DisplayLang=en (http://msdn.microsoft.com/isapi/gomscom.asp?target=/downloads/results.aspx?productID=&freetext=gdi%2B&DisplayLang=en)
Or you can get it from www.dll-files.com:
http://www.dll-files.com/dllindex/dll-files.shtml?gdiplus (http://www.dll-files.com/dllindex/dll-files.shtml?gdiplus)
Best wishes!
I am using auCDtect version 0.8 (Linux) and it seems to be doing it's job quite nicely, but after each file it spits out an error...
[a href="index.php?act=findpost&pid=274288"][{POST_SNAPBACK}][/a]
I have no such errors.. and have no same bug reports yet, but I will check it at soon.
I already described the problem when 1.0 was released...when I start the program it says that same dll couldn't be found...
[{POST_SNAPBACK}][/a] (http://index.php?act=findpost&pid=274227")
About gdiplus.dll. Its not a error. If I understood of the GDI+ license correctly - I can't to include gdiplus.dll in my distribution package, but you can download it by yourself. As I have wrote at our site:
Windows NT/2000 usage requires installation of the GDI+ package from Microsoft
Thus, you can try to get gdiplus.dll from Microsoft directly:
[a href="http://msdn.microsoft.com/library/en-us/gdicpp/gdiplus/gdiplus.asp]http://msdn.microsoft.com/library/en-us/gd...lus/gdiplus.asp[/url]
http://msdn.microsoft.com/isapi/gomscom.as...&DisplayLang=en (http://msdn.microsoft.com/isapi/gomscom.asp?target=/downloads/results.aspx?productID=&freetext=gdi%2B&DisplayLang=en)
Or you can get it from www.dll-files.com:
http://www.dll-files.com/dllindex/dll-files.shtml?gdiplus (http://www.dll-files.com/dllindex/dll-files.shtml?gdiplus)
Best wishes!
[a href="index.php?act=findpost&pid=274386"][{POST_SNAPBACK}][/a]
ok, I got it wo work. However, I inserted a CD and the program froze...I tried to close through the task-manager...but that didn't work either...my entire system locked up and I couldn't even restart it (I had to turn the PC off)...that's the first time that a program causes such a crash...my system never froze...
Windows 2000, SP3, working.
Windows 2000, SP3, working.
[a href="index.php?act=findpost&pid=274616"][{POST_SNAPBACK}][/a]
Windows 2000 SP4 + all other patches, not working
Windows 2000 SP4 + all other patches, not working
[a href="index.php?act=findpost&pid=274667"][{POST_SNAPBACK}][/a]
Windows 2000 SP4 + all other patches, working.
in other words jojo you need to provide more infomation....
So, about assurance. Maybe it isnt correct word. Yes, I've read Testing Results, they looks perfect. But I'm not about my assurance, but about Analyser assurance, someting like this:
This track looks like CDDA with probability 100%
Am I clear?
(Oh, my English!)
So, about assurance. Maybe it isnt correct word. Yes, I've read Testing Results, they looks perfect. But I'm not about my assurance, but about Analyser assurance, someting like this:This track looks like CDDA with probability 100%
Am I clear?
(Oh, my English!)
[a href="index.php?act=findpost&pid=274699"][{POST_SNAPBACK}][/a]
Yes, I see. It looks strange: "looks like" and "probability 100%" :-)
"Looks like" - its more correctly.
"Probability 100%" means: All of our test tracks with such characteristics were original CDDA records.
For some reason this causes a hard reboot on my machine when I have a cd in the drive.
Windows XP SP2
Asus K8V SE Deluxe - AMD Athlon 64 2800+
LITE-ON DVDRW LDW-411S, LITE-ON LTR-16102B
For some reason this causes a hard reboot on my machine when I have a cd in the drive.
Windows XP SP2
Asus K8V SE Deluxe - AMD Athlon 64 2800+
LITE-ON DVDRW LDW-411S, LITE-ON LTR-16102B
[a href="index.php?act=findpost&pid=275479"][{POST_SNAPBACK}][/a]
I think I had a CD in my CD drive as well when it crashed Win2000...
For some reason this causes a hard reboot on my machine when I have a cd in the drive.
Windows XP SP2
Asus K8V SE Deluxe - AMD Athlon 64 2800+
LITE-ON DVDRW LDW-411S, LITE-ON LTR-16102B
[a href="index.php?act=findpost&pid=275479"][{POST_SNAPBACK}][/a]
I think I had a CD in my CD drive as well when it crashed Win2000...
[a href="index.php?act=findpost&pid=275665"][{POST_SNAPBACK}][/a]
I have no such problems, but I will try to find the reason.
For some reason this causes a hard reboot on my machine when I have a cd in the drive.
Windows XP SP2
Asus K8V SE Deluxe - AMD Athlon 64 2800+
LITE-ON DVDRW LDW-411S, LITE-ON LTR-16102B
[a href="index.php?act=findpost&pid=275479"][{POST_SNAPBACK}][/a]
I think I had a CD in my CD drive as well when it crashed Win2000...
[a href="index.php?act=findpost&pid=275665"][{POST_SNAPBACK}][/a]
I have no such problems, but I will try to find the reason.
[a href="index.php?act=findpost&pid=275865"][{POST_SNAPBACK}][/a]
in my case it wasn't an Audio CD but rather a Data Disc with multiple sessions on it. The CD wasn't finalized yet...so there was still space for more sessions...I have a CD burner and a DVD drive...the program started and I could see the GUI, but that was about it. I couldn't navigate through the menus or anything...all I did could do was selecting the drop down menu that showed all CD/DVD drives...after that it froze and it was imposible to close the program or end the task through the task manager in Win2000...the entire system was locked up and as I said before, that's the first time I had to turn my PC off in order to do a restart...
Does the Tau-Analyzer also recognize mp3s (burned as a CD-Audio) which are encoded in a very high bitrate (maybe preset extreme) correctly? Or is the quality-loss of mp3s with very high quality too small to recognize them as compressed?
Does the Tau-Analyzer also recognize mp3s (burned as a CD-Audio) which are encoded in a very high bitrate (maybe preset extreme) correctly? Or is the quality-loss of mp3s with very high quality too small to recognize them as compressed?
[a href="index.php?act=findpost&pid=276559"][{POST_SNAPBACK}][/a]
I would be quite surprised if it didn't detect them. Especially MP3 has some characteristics in the upper frequency range that don't disappear at any bitrate. In fact, it's very easy to visually identify a lossy source in the spectral display of an audio editor just by looking at the frequency range from 16...18 KHz upwards. But make no mistake about it, that visual inspection is no indicator of quality by itself, as the hearing for those frequencies isn't very sensitive. MPC once preserved the full frequency range when you used the --braindead switch, making the visual method more or less impracticable. But since it was only introduced by popular demand and didn't factually improve quality, it was later disabled again. Now all popular lossy codecs will get rid of certain upper frequency content, no matter the bitrate, in theory making automated detection quite easy. Of course you can't only rely on that (think of older records that don't have much content there in the original, to begin with).
Thank you for the great reply! Now i understand more about the technique of unmasking a mp3 -> CDA. It's good to know that on this board are people who really care about audio and audio-quality and have lots of knowledge.
MPC once preserved the full frequency range when you used the --braindead switch, making the visual method more or less impracticable. [{POST_SNAPBACK}][/a] (http://index.php?act=findpost&pid=276584")
It was the --insane preset.
Then Frank Klemm created a new preset (with 0.90s encoder, something like that), which offered the same average bitrate than --insane, but with "higher quality" (e.g. without full frequency encoding -> more bits for important frequency bands).
Now, --insane and --braindead are remaped into a large scale, and none of them encode all frequencies.
EDIT: [a href="http://www.hydrogenaudio.org/forums/index.php?showtopic=1112&view=findpost&p=10409]link[/url]
It was the --insane preset.
Then Frank Klemm created a new preset (with 0.90s encoder, something like that), which offered the same average bitrate than --insane, but with "higher quality" (e.g. without full frequency encoding -> more bits for important frequency bands).
Now, --insane and --braindead are remaped into a large scale, and none of them encode all frequencies.
EDIT: link (http://www.hydrogenaudio.org/forums/index.php?showtopic=1112&view=findpost&p=10409)
[a href="index.php?act=findpost&pid=276607"][{POST_SNAPBACK}][/a]
You're right, now i remember. And before --braindead, people even tweaked --insane cause they were still not satisfied those were the days...
I've just encountered something pretty strange. I used the command line tool and the result using -m0 was 90% probability that it's source was lossless. Anyway, I encoded that file using LAME 3.96.1 -V2 and decoded it back to wav. Now, all of a sudden that file got a probability of 95%!
there seem to be even bigger issues: check out that thread: http://www.hydrogenaudio.org/forums/index....ndpost&p=286836 (http://www.hydrogenaudio.org/forums/index.php?showtopic=32828&view=findpost&p=286836) the provided sample is obviously lossy...looks like a typical mp3 (maybe FhG), nevertheless it's reported as 100% lossless...
I've seen a few recent posts around HA in which some people seem to be surprized that the program makes errors. Well, it's true, the analyzer algorithm doesn't always work perfectly.
Even in their own testing of 5683 samples, the devs found that 2.6% of the results were inaccurate... and they make no secret of it.
Please note: Tau Analyzer does not provide an absolutely warranty in results of detection. Sometimes the program can show a wrong result for the track (please see Testing Results (http://www.true-audio.com/analyzer.tests)). Thus, to make sure you should check all of the CD contents. In this case, the program can produce more trustable CD conclusion, except some special cases.
The point that Tau Analyzer's results can't always be trusted (particularly concerning an individual track) is a good one, but it should not come as a shock to anyone. Though I suppose it's no surprize that not everyone takes the time to read the available info and become aware.
I'm not on my home computer so I don't know if I have the latest version of this, but it crashes (on XP) when I try and use one of the CD drives - it's fine with the other one. I can post more information when I get home.
Probably not really relevant but it doesn't seem to be all that good at vinyl rips. It did get the right conclusion for the whole CD (i.e. no lossy digitial encoding), but on individual tracks on the 1 setting it thought roughly a third were MPEG sourced, and on the 8 setting about a half. I suppose that's inevitable though since any analogue to digital conversion is lossy in its own way.
Hope someone can shed some light on a little problem. Am using XP service pack 2 and can't seem to get accurate results from the Tau 1.2 ISRC function. Each track on an audio CD (legit) is supposed to have a unique ISRC number. On the Tau query, I keep getting the same ISRC for all tracks on the CD.
Any ideas? Hope someone can help me out here....
Thanks
Can someone tell me what do I do with with AuCDtect version 0.8? After unzipping the file I only see a Readme file and auCDtect. When I double click on auCDtect nothing shows up. What do I do with it?
I also downloaded Tau Analyzer version 1.2, do I have to integrate auCDtect into Tau Analyzer version 1.2?
How do I use auCDtect by itself?
auCDtect is a command line app
C:\......>aucdtect -h
auCDtect: CD records authenticity detector, version 0.8.2
Copyright © 2004 Oleg Berngardt. All rights reserved.
Copyright © 2004 Alexander Djourik. All rights reserved.
------------------------------------------------------------
Usage: auCDtect [commands/options] (track.wav|*.wav)
------------------------------------------------------------
commands:
------------------------------------------------------------
-- read data from stdin
-d summary conclusion for set of tracks
-v verbose mode
-h this help
------------------------------------------------------------
options:
------------------------------------------------------------
-mS detect mode S=[0..40], default 8
0 - slow and most accurate
40 - fast, but less accurate
------------------------------------------------------------
For more information please visit: [url=http://www.true-audio.com]http://www.true-audio.com[/url]
Example
C:\....>aucdtect "Girls Of Summer.wav"
auCDtect: CD records authenticity detector, version 0.8.2
Copyright (c) 2004 Oleg Berngardt. All rights reserved.
Copyright (c) 2004 Alexander Djourik. All rights reserved.
------------------------------------------------------------
Processing file: [Girls Of Summer.wav]
Data analysis: [100%]
------------------------------------------------------------
This track looks like MPEG with probability 95%
I see, and Tau Analyzer is the GUI version of auCDtect I suppose?
I see, and Tau Analyzer is the GUI version of auCDtect I suppose?
No. Tau analyser is for a physical cd you have in your cd drive. aucdtect is for wav files.
I've been looking in the wrong place the whole time. I'm searching for a program that allows you to tell if the source file was transcoded. Alot of sites I visit now have idiots who transcode 192kbps to 320kbps and think that transcoding from a lower bitrate to a higher bitrate will yield them higher quality.
I need a program that can distinguish the original source from a transcoded one.
I've been looking in the wrong place the whole time. I'm searching for a program that allows you to tell if the source file was transcoded. Alot of sites I visit now have idiots who transcode 192kbps to 320kbps and think that transcoding from a lower bitrate to a higher bitrate will yield them higher quality.
I need a program that can distinguish the original source from a transcoded one.
I am in the exact situation. Tried aucdtect and now Tau. Tau won't find transcodes.
Not having much luck with aucdtect. This is the result for a LAME -V 0 --vbr-new --add-id3v2 --ignore-tag-errors --ta "%a" --tt "%t" --tg "%m" --tl "%g" --ty "%y" --tn "%n" %s %d rip straight from CD.
auCDtect: CD records authenticity detector, version 0.8.2
Copyright (c) 2004 Oleg Berngardt. All rights reserved.
Copyright (c) 2004 Alexander Djourik. All rights reserved.
------------------------------------------------------------
Processing file: [01 Strutter.wav]
Detected average hi-boundary frequency: 1.975749e+004 Hz
Detected average lo-boundary frequency: 1.919396e+004 Hz
Detected average hi-cut frequency: 2.001185e+004 Hz
Detected average lo-cut frequency: 1.953274e+004 Hz
Maximum probablis boundary frequency: 1.971600e+004 Hz
Coefficient of nonlinearity of a phase: 2.259359e-002
First order smothness: 9.295154e-001
Second order smothness: 7.224670e-001
------------------------------------------------------------
This track looks like MPEG with probability 95%
------------------------------------------------------------
Processing file: [02 Deuce.wav]
Detected average hi-boundary frequency: 1.959083e+004 Hz
Detected average lo-boundary frequency: 1.883666e+004 Hz
Detected average hi-cut frequency: 1.961834e+004 Hz
Detected average lo-cut frequency: 1.902640e+004 Hz
Maximum probablis boundary frequency: 1.967900e+004 Hz
Coefficient of nonlinearity of a phase: 1.962964e-002
First order smothness: 8.863636e-001
Second order smothness: 7.000000e-001
------------------------------------------------------------
This track looks like MPEG with probability 95%
And this is the result from a Audio CD to WMA to MP3 transcode.
auCDtect: CD records authenticity detector, version 0.8.2
Copyright (c) 2004 Oleg Berngardt. All rights reserved.
Copyright (c) 2004 Alexander Djourik. All rights reserved.
------------------------------------------------------------
Processing file: [01 Incoming.wav]
Detected average hi-boundary frequency: 1.912544e+004 Hz
Detected average lo-boundary frequency: 1.747644e+004 Hz
Detected average hi-cut frequency: 1.944789e+004 Hz
Detected average lo-cut frequency: 1.802900e+004 Hz
Maximum probablis boundary frequency: 1.845100e+004 Hz
Coefficient of nonlinearity of a phase: 4.640403e-002
First order smothness: 8.888889e-001
Second order smothness: 6.111111e-001
------------------------------------------------------------
This track looks like MPEG with probability 95%
------------------------------------------------------------
Processing file: [02 Testimonial Year.wav]
Detected average hi-boundary frequency: 1.896774e+004 Hz
Detected average lo-boundary frequency: 1.777095e+004 Hz
Detected average hi-cut frequency: 1.927379e+004 Hz
Detected average lo-cut frequency: 1.788837e+004 Hz
Maximum probablis boundary frequency: 1.830600e+004 Hz
Coefficient of nonlinearity of a phase: 1.354178e-002
First order smothness: 8.961538e-001
Second order smothness: 6.269231e-001
------------------------------------------------------------
This track looks like MPEG with probability 95%
Not having much luck with aucdtect
How that? In both your cases aucdtect showed clearly (95%) that the file didn't originate from CD but from lossy (MPEG) material...
Not having much luck with aucdtect
How that? In both your cases aucdtect showed clearly (95%) that the file didn't originate from CD but from lossy (MPEG) material...
The point is not to find out if the file is lossy (we already know it is). The point is to find out if it's a lossy encode from a lossy source (from MP3 to WMA, for example, or from 192kbps MP3 to 320kbps MP3).
I don't think the program was designed to work out whether an mp3 was ripped from an audio cd.
It's "advertised" function is to detect audio cd's that were made from mp3 files.
I don't think the program was designed to work out whether an mp3 was ripped from an audio cd.
It's "advertised" function is to detect audio cd's that were made from mp3 files.
Agree. However the original program aucdtect supported WAV files. So if a MP3 was converted to WAV and checked with aucdtect then aucdtect will tell if the WAV file is an MPEG source or not.
if it is a lame encoded file with proper lame headers, you can always do the mod588 check.