Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: fooCDtect - temp files and automatic launching (Read 54485 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

fooCDtect - temp files and automatic launching

The fooCDtect plugin (official page : 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.

fooCDtect - temp files and automatic launching

Reply #1 –
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

fooCDtect - temp files and automatic launching

Reply #2 –
Quote from: 2E7AH on
i think that i saw thread about fooCDtect, but i can't recall right now

You mean of course this thread. 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. There is no dedicated fooCDtect thred AFAIK (well, there wasn't until this one).

Quote from: 2E7AH on
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) :


Screen 2 - after the 4-file analysis. The analysis is over (see fooCDtectG) but all the files are in the trash :


Maybe there's a problem for remote files stored in a NAS ?

fooCDtect - temp files and automatic launching

Reply #3 –
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

fooCDtect - temp files and automatic launching

Reply #4 –
Quote from: foorious on
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.

Quote from: foorious on
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.

fooCDtect - temp files and automatic launching

Reply #5 –
There is a new version available:
http://cp.people.overclockers.ru/cgi-bin/d...2_26.04.2008.7z
This link isn't direct. I plan to update this program soon.
Quote
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.

fooCDtect - temp files and automatic launching

Reply #6 –
ok, thanks for the .ru link

did anyone get this file?

and what is the diff. between version?

fooCDtect - temp files and automatic launching

Reply #7 –
Quote
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"] .

fooCDtect - temp files and automatic launching

Reply #8 –
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

fooCDtect - temp files and automatic launching

Reply #9 –
It should definately be able to tag the source files with the results imho  Is that possible to implement?
Can't wait for a HD-AAC encoder :P

fooCDtect - temp files and automatic launching

Reply #10 –
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  .

fooCDtect - temp files and automatic launching

Reply #11 –
Quote from: baralgin on
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?
Can't wait for a HD-AAC encoder :P

fooCDtect - temp files and automatic launching

Reply #12 –
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' ?

fooCDtect - temp files and automatic launching

Reply #13 –
Quote
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...

foorious
Just 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).

fooCDtect - temp files and automatic launching

Reply #14 –
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)

fooCDtect - temp files and automatic launching

Reply #15 –
Quote
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:
Code: [Select]
------------------------------------------------------------
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
------------------------------------------------------------


Quote
X:\Audio\Lossless\Artist\(Date) Album\Tracknumber - Title.flac

I have already touched on these questions. foocdtect doesn't receive input file names.

fooCDtect - temp files and automatic launching

Reply #16 –
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 ?

fooCDtect - temp files and automatic launching

Reply #17 –
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

fooCDtect - temp files and automatic launching

Reply #18 –
i just converted some mp3's and aac's to wav, so see the results for yourself:



what's wrong?

fooCDtect - temp files and automatic launching

Reply #19 –
Quote
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 

Quote
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"] .

fooCDtect - temp files and automatic launching

Reply #20 –
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 ?

fooCDtect - temp files and automatic launching

Reply #21 –
Quote from: baralgin on
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?

Quote from: baralgin on
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

fooCDtect - temp files and automatic launching

Reply #22 –
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  .

Quote
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.

fooCDtect - temp files and automatic launching

Reply #23 –
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

fooCDtect - temp files and automatic launching

Reply #24 –
Quote from: baralgin on
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.