The fooCDtect plugin (official page : http://pelit.koillismaa.fi/plugins/show.php?id=234 (http://pelit.koillismaa.fi/plugins/show.php?id=234) ) works beautifully. I haven't found any fooCDtect topic, so I guess I'll have to post my questions / suggestions here :
1°) I have noticed that all temporary files (decoded WAVs) are not erased until I quit fooCDtectG.exe. So when testing a large batch of lossless files, e.g. if I decide to test 1000 FLAC files (that's about 30GB), the plugin will generate 1000 temporary WAV files (that's about 45GB) and these files will not be erased until I quit fooCDtectG.exe. Is there some reason for that ? IMHO that's a real waste of space, and if we don't have a lot of free space that could even prevent fooCDtect from achieving its batch work. So would it be possible to automatically erase each temporary WAV file as soon as the plugin moves on to the next file to process ?
2°) fooCDtectG.exe has to be launched BEFORE the batch work begins (otherwise we'll get an error on the first processed track). Would there be a way to launch it automatically ? Any ideas welcome. IMHO there should be a way to do so, since fooCDtectG.exe is launched anyway after the first file has ended up with an error.
Thanks in advance for your help.
i think that i saw thread about fooCDtect, but i can't recall right now
1. that's no happening here. the temp wav file is deleted once it's proceded by fooCDtectP, and the only files that remains are .aucd which are < 1KB but of course they are erased when you close fooCDtectG
2. i was trying with some batch files but the converter obviously don't like them. you can use foo_run but it will be messy for more files: so i put fooCDtectG in foo_run (not to leave f2k every time i want to check some cd) and after that i do the convert
edit: auCDtect thread (http://www.hydrogenaudio.org/forums/index.php?showtopic=27910&st=0&p=553384&#entry553384)
i think that i saw thread about fooCDtect, but i can't recall right now
You mean of course this thread (http://www.hydrogenaudio.org/forums/index.php?showtopic=27910). That's precisely where I posted first, and I was rewarded with a warning for TOS#5 violation so I guess it wasn't a good idea for everybody. The topic was splitted by a mod, hence this new topic.
BTW that's pretty much the only HA thread where fooCDtect is mentioned. See here (http://www.google.com/custom?domains=hydrogenaudio.org&q=foocdtect&sa=Google+Search&sitesearch=hydrogenaudio.org&client=pub-4544327213918729&forid=1&channel=7051718642&ie=ISO-8859-1&oe=ISO-8859-1&flav=0000&sig=6_g3ghDcS6bRpfcd&cof=GALT%3A%23008000%3BGL%3A1%3BDIV%3A%23336699%3BVLC%3A663399%3BAH%3Acenter%3BBGC%3AFFFFFF%3BLBGC%3AFFFFFF%3BALC%3A0000FF%3BLC%3A0000FF%3BT%3A000000%3BGFNT%3A0000FF%3BGIMP%3A0000FF%3BLH%3A50%3BLW%3A262%3BL%3Ahttp%3A%2F%2Fwww.hydrogenaudio.org%2Fforums%2Flogo50.png%3BS%3Ahttp%3A%2F%2Fwww.hydrogenaudio.org%3BFORID%3A1&hl=en). There is no dedicated fooCDtect thred AFAIK (well, there wasn't until this one).
the temp wav file is deleted once it's proceded by fooCDtectP
The temp wav file is not deleted (at least not on my NAS where all my audio files are). It's only trashed, but the trash is not emptied (even after quitting fooCDtectG), so the disk space problem remains the same. I have checked this several times so I can provide screens if necessary : all temp wav files do remain on my HD and I have to delete them manually in the end.
EDIT - here are the screens :
Screen 1 - during the analysis of the first file (see both the aucd and the wav files) :
(http://img166.imageshack.us/img166/4894/foocdtect1jw5.th.jpg) (http://img166.imageshack.us/my.php?image=foocdtect1jw5.jpg)
Screen 2 - after the 4-file analysis. The analysis is over (see fooCDtectG) but all the files are in the trash :
(http://img156.imageshack.us/img156/466/foocdtect2xj7.th.jpg) (http://img156.imageshack.us/my.php?image=foocdtect2xj7.jpg)
Maybe there's a problem for remote files stored in a NAS ?
quote: "Maybe there's a problem for remote files stored in a NAS ?"
probably that is the problem, and not only with this component but also with some others the users are complaining.
btw, i think it's a good thing that you start the fooCDtect topic, and i'm curious about the author also (the file is on rapidshare?)
another thing is that when i mention this component to someone the answer is: accurip, why bother? their db is huge.
well maybe, but:
first of all, although it's no 100% accurate the existence of code which is able to detect MPEG artifact in WAVs isn't for neglecting.
and of course using f2k interface is our priority, not to mention some CDs which arren't on accurip db.
quote: "IMHO there should be a way to do so, since fooCDtectG.exe is launched anyway after the first file has ended up with an error."
i hope there is some coder out there who can make this component more straitforward
fooCDtectG.exe has to be launched BEFORE the batch work begins (otherwise we'll get an error on the first processed track). Would there be a way to launch it automatically ? Any ideas welcome. IMHO there should be a way to do so, since fooCDtectG.exe is launched anyway after the first file has ended up with an error.
I've tried this a few times and the error did not occur all of the time. To me the problem seems to be in how fooCDtectP.exe (the command line encoder adapter) and fooCDtectG.exe (the GUI that presents the results) communicate. By the way, calling fooCDtect a foobar2000 component is misleading.
The temp wav file is not deleted (at least not on my NAS where all my audio files are). It's only trashed, but the trash is not emptied (even after quitting fooCDtectG), so the disk space problem remains the same. I have checked this several times so I can provide screens if necessary : all temp wav files do remain on my HD and I have to delete them manually in the end.
The converter does not delete temporary files when the conversion failed. Unfortunately, while auCDtect has a parameter to read audio data from standard input, this does not work for me (Windows version, haven't tested the others). If it worked, it would be possible to avoid using temporary WAV files.
There is a new version available:
http://cp.people.overclockers.ru/cgi-bin/d...2_26.04.2008.7z (http://cp.people.overclockers.ru/cgi-bin/dl.pl?id=27895&filename=foocdtect2_26.04.2008.7z)
This link isn't direct. I plan to update this program soon.
auCDtect has a parameter to read audio data from standard input, this does not work for me
Yes, it doesn't work at all . Thus I had to use big temporary files.
ps: If you use Media Library you may exclude extension *.aucdtect on the Preferences->Media Library.
ok, thanks for the .ru link
did anyone get this file?
and what is the diff. between version?
did anyone get this file?
[a href="http://images.people.overclockers.ru/163928.png" target="_blank"] :
* one executable file (foocdtect2.exe, it may be renamed);
* gui-process launches anyway;
* program supports multithreading correctly;
* batch saving reports(unicode, I am going to add utf8 and ansi encoding);
* sort checked tracks by directory;
* more process switches(see about window for detail);
* It is possible to stop encoding process(all temporary files will be deleted and all child processes terminated);
* ...
It looks like this:
[a href="http://images.people.overclockers.ru/163929.png" target="_blank"] .
thanks for the reply
i couldn't get the file because of my Opera settings, but i got it with Mozilla
it works like you said, and it looks much better
good luck with updating
It should definately be able to tag the source files with the results imho Is that possible to implement?
odyssey Foobar's converter doesn't transmit input file names to external encoder( for example, it may be cue-sheet or/and wave file, output folder may not match with input files ... ). Therewith foobar2000 doesn't make it possible to edit tags by command line switches. Am I mistaken?
ps: fooaccrip based on foocdtect2 .
odyssey Foobar's converter doesn't transmit input file names to external encoder( for example, it may be cue-sheet or/and wave file, output folder may not match with input files ... ). Therewith foobar2000 doesn't make it possible to edit tags by command line switches. Am I mistaken?
What a shame. Why not make a native foobar component then?
Oh yes, great idea, I second that.
baralgin, why is it that your default auCDtect parameters are :
--output %d --threads 2 --mode 0
... while 'old' fooCDtect paremeters were :
-m0 -v -i %s -o %d
?
I'm not used to such parameters. What would be the 'ideal mix' ?
Why not make a native foobar component then?
I am not still ready to make native components . Perhaps I'll make plugin in the future...
fooriousJust change the old parameters to the new and enjoy.
Parameters
"-m0 -v -i %s -o %d" and
"--output %d --threads 0 --mode 0" are equal.
Switch "--threads" limits converter to decode several tracks at the same time. It is useful when you check files directly from CD/DVD or your hard drive is too slow. By default this parameter is zero(no limits, recomended).
Thanks baralgin.
By the way, is there some auCDtect manual ? I'd like to understand the meaning of all different command-line paramaters and I haven't found anything on True Audio site. Thank you.
As for the tagging part, let's imagine fooCDtect can provide a log that we could save on a separate text file under this form :
Complete file path (e.g. X:\Audio\Lossless\Artist\(Date) Album\Tracknumber - Title.flac) ** fooCDtect result (e.g. CDDA-100%)
Complete file path (e.g. X:\Audio\Lossless\Artist\(Date) Album\Tracknumber - Title.flac) ** fooCDtect result (e.g. CDDA-100%)
Complete file path (e.g. X:\Audio\Lossless\Artist\(Date) Album\Tracknumber - Title.flac) ** fooCDtect result (e.g. CDDA-100%)
...
Then it would be possible to make a small windows script that would read all the lines one by one, look for the relevant audio files and tag them with a "fooCDtect" tag. What do you think ?
(' ** ' is just an example of a separator that could be easily found by a script, but any other usual group of characters would be good)
By the way, is there some auCDtect manual ? I'd like to understand the meaning of all different command-line paramaters
It's very simple:
------------------------------------------------------------
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
------------------------------------------------------------
X:\Audio\Lossless\Artist\(Date) Album\Tracknumber - Title.flac
I have already touched on these questions. foocdtect doesn't receive input file names.
Thanks. However, this short manual doesn't seem to give all the information. Let's take for example previously quoted parameters "-m0 -v -i %s -o %d" and "--output %d --threads 0 --mode 0". We're missing information for the following :
1/ -i
2/ %s
3/ -o
4/ Why %d and not -d like in the manual ?
5/ --threads 0
So I guess there are some undocumented parameters, and a more complete manual would be helpful.
As for the log part, I understand that fooCDtect doesn't receive input file names. What I don't understand is how the file paths end up showing in fooCDtect's window anyway :
Since the information is there, wouldn't there be a way to use it ? I'm sorry, I don't understand. Can somebody please explain ?
the "manual" is auCDtect command line usage
if it isn't obvious:
1/ -i = input
2/ %s = temp input file (f2k converter)
3/ -o = output
4/ %d = output file (f2k converter); -d = auCDtect command line option
5/ --threads 0 = num of active threads (0 is unlimited)
-m0 = --mode 0
-v = verbose
doubleclick fooCDtect2.exe for command line options
save the results and use tagging script to tag the files
and put a thumbnail instead original picture
i just converted some mp3's and aac's to wav, so see the results for yourself:
(http://img237.imageshack.us/img237/1162/clipboard01vy9.th.jpg) (http://img237.imageshack.us/my.php?image=clipboard01vy9.jpg)
what's wrong?
What I don't understand is how the file paths end up showing in fooCDtect's window anyway
This is the output path. In the general case input and output folders/filenames may be mismatch:
input file: <artist> <track> <title>.<music-type extension>
output file: <track> - <title>.aucdtect
or
input file: image + cue-sheet(or embeded cue-sheet)
output file: <track> - <title>.aucdtect
I can continue
i just converted some mp3's and aac's to wav, so see the results for yourself... what's wrong?
aucdtect doesn't detect aac with high bitrate. But as a rule it detects mp3 files very well. In the converter settings you must disable dither:
[a href="http://images.people.overclockers.ru/164246.png" target="_blank"] .
baralgin, forgive for insisting. I'm really sorry, because maybe I'm not understanding this well, but :
1. If we choose foobar's "convert to same folder" option (that's what I choose 100% of the time), then the output directory path will be the same as the input directory path. Do you agree ?
2. If you can write a temp file called
<output directory>\<track> - <title>.aucdtect ,
then I assume you can write the following info in a log :
<output directory>\<track> - <title>.<extension> ** <test result>
Or even only this :
<output directory>\<track> - <title> ** <test result>
Do you agree ?
3. And if you can write that, then anybody can make a separate script to do some mass-tagging (including finding the right extension if needed).
Do you agree with all this, or am I becoming crazy ?
In the converter settings you must disable dither
that solve the problem (can you elaborate?), and what if i put those dithered wavs on CD - auCDtect won't recognise the MPEG source within?
if that is the case than i'll must use something like fooaccrip - is it finished, i haven't tried it yet?
ps: you may check lossy-music directly - you don't need to decode its to wav before
well, out of curiosity i first do that - i convert one mp3 file with fooCDtect and the output was: CDDA-100%
so i converted some files to wav to see the results and that was it
foorious I can do like this:
<output directory>\[%track% ] - %title% ** <test result>
(
"[%track% ] - %title%" is the default output file name in converter's settings )
I think there will not be easily to make like script .
if i put those dithered wavs on CD - auCDtect won't recognise the MPEG source within?
Yes, it won't. I can illustrate by an example. There are three files: lossless-wav, lame3.98_V0 and dithered lame3.98_V0:
[a href="http://images.people.overclockers.ru/164368.png" target="_blank"] .
ps: fooaccrip is not still ready.
thanks for the lesson.
if it is so visually obvious how come auCDtect fails?
according to TA results for dithered mp3's:
[a href="http://img186.imageshack.us/my.php?image=testditheredvv4.png" target="_blank"] .
ps: fooaccrip is not still ready.[/quote]
f2k has simple spectrogram visualization, but you probably think about something different.
looking forward for any update and fooaccrip
foorious
I can do like this:
<output directory>\[%track% ] - %title% ** <test result>
( "[%track% ] - %title%" is the default output file name in converter's settings )
I think there will not be easily to make like script
baralgin, if you can implement this log-writing feature on the next version, I'll do my best to come up with a usable script. Thanks in advance !
EDIT : the Windows script is ready, and it works !
Now all we need is a new version of fooCDtect for the final testing / tuning of the script. Then I'll publish the script so everybody can be happy.
We will make this work.
Hi baralgin,
We haven't had news from you since Sep. 6, and I just can't wait to try out the new fooCDtect version. Like I said, the Windows script is working like a charm. So could you please update fooCDtect with the text-log creation possibilities we have been discussing in this topic, and quickly post a link to the latest version ?
Thank you.
2E7AH
I checked a few hundred mp3-tracks(v2, v0, 320k) with dither. And aucdtect found only 6% of the total tracks .
fooCDtect 2.1: link (http://cp.people.overclockers.ru/cgi-bin/dl.pl?id=29351&filename=fooCDtect2_25.09.2008.7z) or rapidshare (http://rapidshare.de/files/40550408/fooCDtect2_25.09.2008.7z.html)
changes:
- foocdtect window is created as a child of foobar2000.
- switches "--topmost" and "--verlog" were removed.
- Verbose log doesn't contain temporary file names.
added:
- ability to change checking priority and number of maximum threads
(right click in the left part of the status bar).
- three types of log format: simple, normal and verbose.
- ability to choose ANSI, UTF16 or UTF8 encoding for log(UTF16 and UTF8 with BOM).
- path to temporary folder for big wav-files(switch: --tpath).
- simple statistic window(menu File->Stats).
PS: I've fixed a bug (full paths in normal and verbose logs ). Please download file again.
PS2: and another fix...(automatic save didn't work)
Thanks baralgin !
Now here's my fooCDtect tagging script : http://rapidshare.com/files/148381228/fooCDtag.vbs.html (http://rapidshare.com/files/148381228/fooCDtag.vbs.html)
(with credits to my talented friend Gemini)
Here's how it works :
1. Get
Tag.exe : Tag.exe is a tagging utility bundled with FLAC, so it should be in your FLAC folder, typically C:\Program Files\FLAC\ . Otherwise you can look for it here : http://www.synthetic-soul.co.uk/tag/ (http://www.synthetic-soul.co.uk/tag/)
2. Put the
fooCDtag.vbs file inside the same folder as Tag.exe (the folder itself doesn't matter as long as the two files are together)
3. Use fooCDtect to test a bunch of FLAC files
4. Before closing fooCDtect, choose the "Simple" log option <-- **mandatory**
5. Choose also the "ANSI" encoding option <-- **mandatory**
6. Choose "Save all" to generate a log (
fooCDtect.log.txt)
7. Save the log inside the same folder as fooCDtag.vbs and Tag.exe
So now we have Tag.exe, fooCDtag.vbs and fooCDtect.log.txt in the same folder, right ?
Now with a trembling hand, double-click on fooCDtag.vbs... voilà ! That's all !
You'll see a bunch of command-line windows open and close. Wait until everything is finished. All your lossless files tested with fooCDtect will be tagged as follows :
- Tag name : %aucdtect%
- Tag value : fooCDtect result (e.g. "CDDA 100%", "MPEG 95%", etc.)
It's a very simple script, but it works. Hey baralgin, who knows, maybe you can integrate it in a future version of fooCDtect, so that we have an "all-in-one" tool ?
This script has been tested only on FLAC files. I don't know if it will work on other lossless files. I guess it should since Tag.exe is a multi-purpose tagging utility. But it will be up to you to find out (I only have FLAC files so I haven't been able to test). If you want to try the script on non-FLAC files, you just need to manually edit the script and replace the ".flac" part with the right lossless extension.
fooCDtag.vbs is provided "as is". It shouldn't do any harm to your files or blow away your computer. But in the very unlikely event that it should happen, I couldn't be held responsible for that.
Now enjoy !
foorious
PS : before somebody asks (and in case the rapidshare link becomes obsolete), here are the contents of the script (just put them inside a text file, name it fooCDtag.vbs and you're ready to go) :
dim filesys, filetxt
Const ForReading = 1, ForWriting = 2, ForAppending = 8
Set filesys = CreateObject("Scripting.FileSystemObject")
Set filetxt = filesys.OpenTextFile("fooCDtect.log.txt", ForReading, True)
Set shell = CreateObject("WScript.Shell")
Do While Not filetxt.AtEndOfStream
line = filetxt.ReadLine
pos = InStr(line, " ** ")
file = Mid(line, 1, pos - 1)
tag = Mid(line, pos + 4)
cmd = "Tag.exe -t aucdtect=" & chr(34) & tag & chr(34) & " " & chr(34) & file & ".flac" & chr(34)
shell.Run cmd, 1, false
Loop
another thanks
especially for encoding output log formats, and simple output log which makes even easier to use tagging scripts.
but i have a problem with some unicode file names:
(http://img262.imageshack.us/img262/1983/clipboard01wx5.th.png) (http://img262.imageshack.us/my.php?image=clipboard01wx5.png)(http://img262.imageshack.us/images/thpix.gif) (http://g.imageshack.us/thpix.php)
the name of the first file is:
Draußen Ist Feindlich
and the last:
12 Städte (Twelve Cities)
but how did the second one pass (Grundstück - u with diaeresis)?
the output *.aucdtect filenames are correct.
also minor notice: in the title bar encoding name is UTF8, although i selected UTF16, but the output is correct of course.
are you working on a spectrogram?
but i have a problem with some unicode file names:
Strangely, is it repeating? I didn't have any problems with unicode tags/filenames. If I could reproduce this situation, I would correct a problem.
Show me the full path to the problem files and foocdtect parameters.
in the title bar encoding name is UTF8, although i selected UTF16, but the output is correct of course.
Thanks, I'll fix it.
are you working on a spectrogram?
yes, I am working on this feature .
ok, fast reply... nice
the setting were like suggested. all my dirs and files are in ascii (compatibility reasons), but the tags are in unicode. so when i use fooCDtect and the tags have some nonascii chars the file that is checked has the name: temp-(32hex) and it stays that way until some kind of refresh is done.
(http://img210.imageshack.us/img210/3601/clipboard02sp6.th.png) (http://img210.imageshack.us/my.php?image=clipboard02sp6.png)(http://img210.imageshack.us/images/thpix.gif) (http://g.imageshack.us/thpix.php)
i try with the same files, but now everything works fine? the temp-... names stays for some time until couple of tracks are processed and then the names turns like they suppose to do. i can't reproduce the same situation?
great to hear about spectrogram, and if i may ask will you be using fftw?
For the record, I have noticed the same behaviour as 2E7AH (temp file names staying for some time, but then the names turn like they are supposed to). baralgin, this happened with the sep. 25 version, but it didn't happen with the previous version you sent me (sep. 23 I guess).
it stays that way until some kind of refresh is done.
temp file names staying for some time, but then the names turn like they are supposed to
If I understand correctly, it is normal. Look at the normal process of checking:
(http://images.people.overclockers.ru/preview/165940.jpg) (http://images.people.overclockers.ru/165940.png)
will you be using fftw?
I am going to use source code of audacity project. But I have not decided finally yet.
Hello Baralgin,
Any news on this project ?
And what do you think about implementing the suggestions I made on September 25 ? ("It's a very simple script, but it works. Hey baralgin, who knows, maybe you can integrate it in a future version of fooCDtect, so that we have an "all-in-one" tool ?')
Thank you.
Any news about this project of yours Baralgin?
Thanks to everybody for their efforts! Unfortunately, tagging fails when a single flac with embedded cue sheet is used.
In that case, foocdtect treats the tracks as if they were separate, and the tagging script then tries to tag non-existant files. Maybe there's a solution for this?
Using foobar2000 v1.0.2, this component doesn't work.
Indeed, when I want to check a file, it produces a 4 KB .aucdtect file that fooCDtect obviously can't recognize.
I think that would happens by using any 1.x version of foobar2000, too.
Would it be possible to update it, to make it works again?
Thank you!
working fine here Pidgeon on foobar 1.0.2 with same settings used from previous versions
Hello, may I know which fooCDtect version are you using?
UPDATE: now it all seems to work, thank you anyway!.
In last version foobar 1.1 beta 1 it doesn't work. Foobar says "Not a valid command line encoder"
fb2k now checks that the encoders are really command-line/console executables to avoid the problems when people are using installer .exes instead of the real encoder etc.
Patching the subsystem field in fooCDtect2.exe from GUI to Console should help.
Offset fooCDtect2.exe.orig fooCDtect2.exe
----------- --------------------- ----------------
0000014Ch 02h 03h
1 differences total.
thanks for the clarification, but what exactly should i do with my foocdtect2.exe to make it work with foobar 1.1?
fb2k now checks that the encoders are really command-line/console executables to avoid the problems when people are using installer .exes instead of the real encoder etc.
Patching the subsystem field in fooCDtect2.exe from GUI to Console should help. Offset fooCDtect2.exe.orig fooCDtect2.exe
----------- --------------------- ----------------
0000014Ch 02h 03h
1 differences total.
Thanks, that worked.
Here is a prepatched executable.
http://www.nippyzip.com/uploads/100824045807-06222.zip (http://www.nippyzip.com/uploads/100824045807-06222.zip)
The link is only good for 3 days.
Here is a prepatched executable.
http://www.nippyzip.com/uploads/100824045807-06222.zip (http://www.nippyzip.com/uploads/100824045807-06222.zip)
The link is only good for 3 days.
Thank you very much
It works fine with v1.1
(http://img278.imagevenue.com/loc575/th_01495_55_122_575lo.JPG) (http://img278.imagevenue.com/img.php?image=01495_55_122_575lo.JPG)
20x20 22x22 png.set
ttp://www.megaupload.com/?d=GH4T7DQF
Could someone re-upload the patched executable, please?
Thanks.
fooCDtect always gives me an error, UNLESS I run foobar2000 with elevated privileges (that happened before the new convert dialogue already). I've already moved the fooCDtect executable from the program folder to the user folder, but that didn't seem to help. Does anybody know a way around this?
fb2k now checks that the encoders are really command-line/console executables to avoid the problems when people are using installer .exes instead of the real encoder etc.
Patching the subsystem field in fooCDtect2.exe from GUI to Console should help. Offset fooCDtect2.exe.orig fooCDtect2.exe
----------- --------------------- ----------------
0000014Ch 02h 03h
1 differences total.
After having patched the file and having updated foobar from 1.0.1 to 1.1.1, when I try to check some audio files, the program returns an error:
(http://img339.imageshack.us/img339/6835/sshot1vx.png)
Track 3 is flac, the rest are mp3.
I don't think it happened with the previous foobar version.
What should I do to correct that?
I'm using Windows XP 32bit SP3.
It doesn't make sense to check whether a MP3 file is really lossless, hence it's totally fine that foocdtect refuses it.
It doesn't make sense to check whether a MP3 file is really lossless, hence it's totally fine that foocdtect refuses it.
This is very strange, because when I tested some mp3 files with the previous foobar version I mentioned above, aucdtect worked correctly reporting those files as 95% MPEG.
If so, why the flac file (track 3) is reported as error, too?
I know that mp3 are lossy, I only used that files for testing purposes.
Indeed, when I want to check a file, it produces a 4 KB .aucdtect file that fooCDtect obviously can't recognize.
I have the same problem. Foobar 1.1.1, Win 7. Is the solution was found?
Have you tried with the latest fooCDtect version?
http://cp.people.overclockers.ru/cgi-bin/d..._12.09.2010.zip (http://cp.people.overclockers.ru/cgi-bin/dl.pl?id=33954&filename=fooCDtect2_12.09.2010.zip)
Thanks but it did not help.
Thanks but it did not help.
You should post a screenshot of the "Commandline Encoder Settings" foobar2000 window.
Have you placed the folder "fooCDtect" inside your "Components" folder?
I am sorry, problem solved
it was just a Win 7
"run as administrator" )))))
Thanks )
Could someone make an useful post here on how to make this work in foobar? What to do in the menus in foobar to get this to work it would be very helpful, thanks in advance.
Could someone make an useful post here on how to make this work in foobar? What to do in the menus in foobar to get this to work it would be very helpful, thanks in advance.
I got same error but troubleshoot it right now.
It is easy. Just check settings as they are described in docs.
My short instruction.
Converter => ... Saved Presets =>
foocdtect converter settings (select it by double click) => Current Settings and select "Output Format" and Enter Converter setup window.
Select
"foocdtect" => Edit =>
Bit Depth change to
"lossless or hybrid" and choose
Ok.Then at
"foocdtect" should be available:
dither and
bit depth. Set
dither to
"Never" and
bit depth to
"auto".
It's all.
Good Luck.
KyuGoogle.
I have preset cuealac0N4ik.HiQ for converting lossless to m4a
qaac.exe -s -V 127 -q 2 --ignorelength - -o %d
Convertion result:
Tool: qaac 0.47, QuickTime 7.6.9, TVBR Quality 127
BitRate: 274 kbps
Codec: AAC
Codec Profile: AAC LC
Track: Aquarium - Day of Joy.m4a from album Pushkinskaya 10, project KyuAerostat
* * *
Then,
fooCDtect2.exe --autodel --lenc 3 --priority 0 --threads 0 --output %d
Test it in last version of fooCDtect return
CDDA 100% results.
What does it mean?
Maybe, apply lossy is magic?!
I am sorry, problem solved
it was just a Win 7
"run as administrator" )))))
Thanks )
That's no solution but an ugly workaround. I'd never ever run foobar in admin mode just to get fooCDtect running. Any idea how to solve the problem without having to run foobar in admin mode?
I have preset cuealac0N4ik.HiQ for converting lossless to m4a
qaac.exe -s -V 127 -q 2 --ignorelength - -o %d
Convertion result:
Tool: qaac 0.47, QuickTime 7.6.9, TVBR Quality 127
BitRate: 274 kbps
Codec: AAC
Codec Profile: AAC LC
Track: Aquarium - Day of Joy.m4a from album Pushkinskaya 10, project KyuAerostat
* * *
Then,
fooCDtect2.exe --autodel --lenc 3 --priority 0 --threads 0 --output %d
Test it in last version of fooCDtect return CDDA 100% results.
What does it mean?
Maybe, apply lossy is magic?!
As mentioned above, auCDtect cannot reliably detect high-bitrate AAC rips.
I am sorry, problem solved
it was just a Win 7
"run as administrator" )))))
Thanks )
That's no solution but an ugly workaround. I'd never ever run foobar in admin mode just to get fooCDtect running. Any idea how to solve the problem without having to run foobar in admin mode?
give the temp folder full access rights for "user" and "authenticated user" then it works as expected