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 54142 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

fooCDtect - temp files and automatic launching

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

fooCDtect - temp files and automatic launching

Reply #26 –
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 or rapidshare
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)

fooCDtect - temp files and automatic launching

Reply #27 –
Thanks baralgin ! 

Now here's my fooCDtect tagging script : 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/
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) :

Code: [Select]
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

fooCDtect - temp files and automatic launching

Reply #28 –
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:



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?

fooCDtect - temp files and automatic launching

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

Quote
in the title bar encoding name is UTF8, although i selected UTF16, but the output is correct of course.

Thanks, I'll fix it.

Quote
are you working on a spectrogram?

yes, I am working on this feature  .

fooCDtect - temp files and automatic launching

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



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?

fooCDtect - temp files and automatic launching

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

fooCDtect - temp files and automatic launching

Reply #32 –
Quote
it stays that way until some kind of refresh is done.

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


Quote
will you be using fftw?

I am going to use source code of audacity project. But I have not decided finally yet.

fooCDtect - temp files and automatic launching

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

fooCDtect - temp files and automatic launching

Reply #34 –
Any news about this project of yours Baralgin?

fooCDtect - temp files and automatic launching

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

fooCDtect - temp files and automatic launching

Reply #36 –
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!

fooCDtect - temp files and automatic launching

Reply #38 –
Hello, may I know which fooCDtect version are you using?


UPDATE: now it all seems to work, thank you anyway!.

fooCDtect - temp files and automatic launching

Reply #39 –
In last version foobar 1.1 beta 1 it doesn't work. Foobar says "Not a valid command line encoder"

fooCDtect - temp files and automatic launching

Reply #40 –
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.
Code: [Select]
  Offset     fooCDtect2.exe.orig   fooCDtect2.exe 
----------- --------------------- ----------------
 0000014Ch           02h                 03h      
1 differences total.

Full-quoting makes you scroll past the same junk over and over.

fooCDtect - temp files and automatic launching

Reply #41 –
thanks for the clarification, but what exactly should i do with my foocdtect2.exe to make it work with foobar 1.1?

fooCDtect - temp files and automatic launching

Reply #42 –
Quote from: Yirkha on
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.
Code: [Select]
  Offset     fooCDtect2.exe.orig   fooCDtect2.exe 
----------- --------------------- ----------------
 0000014Ch           02h                 03h      
1 differences total.


Thanks, that worked.
 

fooCDtect - temp files and automatic launching

Reply #45 –
Could someone re-upload the patched executable, please?

Thanks.

fooCDtect - temp files and automatic launching

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

fooCDtect - temp files and automatic launching

Reply #47 –
Quote from: Yirkha on
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.
Code: [Select]
  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:



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.

fooCDtect - temp files and automatic launching

Reply #48 –
It doesn't make sense to check whether a MP3 file is really lossless, hence it's totally fine that foocdtect refuses it.

fooCDtect - temp files and automatic launching

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