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: REACT 2 Released (Read 1280303 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

REACT 2 Released

Reply #1000 –
Quote from: feelgood on
Just found that the latest Avast! Home scanner reports a trojan/virus in SS-modified react.exe file: Win32:Trojan-gen {UPX}. (http://www.synthetic-soul.co.uk/temp/REACT_2.0.ssb16n.zip)
A false positive? Avast! doesn't report anything malicious in the original react.exe file.

False positive. Here's the scan result by virusscan.jotti.org:

File:    REACT.exe
Status:    POSSIBLY INFECTED/MALWARE (Note: this file was only classified as malware by scanners known to generate more false positives than the average scanner. Do not consider these results definately accurate. Also, because of this, results of this scan will not be recorded in the database.)
MD5:    4db906bddccb0cd925306e252f746864
Packers detected:    PE_PATCH.UPX, UPX
Bit9 reports:    File not found

Scanner results
Scan taken on 14 Jan 2008 23:37:27 (GMT)
A-Squared    Found nothing
AntiVir    Found nothing
ArcaVir    Found nothing
Avast    Found Win32:Trojan-gen {UPX}
AVG Antivirus    Found nothing
BitDefender    Found nothing
ClamAV    Found nothing
CPsecure    Found nothing
Dr.Web    Found nothing
F-Prot Antivirus    Found nothing
F-Secure Anti-Virus    Found nothing
Fortinet    Found nothing
Ikarus    Found nothing
Kaspersky Anti-Virus    Found nothing
NOD32    Found nothing
Norman Virus Control    Found nothing
Panda Antivirus    Found nothing
Rising Antivirus    Found nothing
Sophos Antivirus    Found nothing
VirusBuster    Found nothing
VBA32    Found nothing

Quote from: feelgood on
First I rip the CD with EAC to a wav-image and then re-rip the wav file with React/Daemon-Tools to get a FLAC image-file and AAC track-files in two consecutive sessions (F4 and F10). This procedure is the fastest and most convinient to my knowledge. I tried to modify the ini and cfg-files to leave the temporary wav file, the cue file and the log file from a CD->FLAC-image conversion session intact, but it went too complicated. If somebody knows how to do that, I would be very happy to get the information.

You want only FLAC image & AAC tracks? You only need to edit the INI file:

1. Change "ImageExt=wav" to "ImageExt=flac" (without quotes)
2. Set "NeroAac=0" OR "iTunesAac=0" (I don't know which one you would like) setting to =1 (others to 0 of course)
3. Rip with F10

All this information is available in the original REACT Wiki page.

REACT 2 Released

Reply #1001 –
Is there anyway to embed artwork to .ogg files in REACT? I can do it manually with AudioShell. I have searched, but cannot find a way to do it with REACT.

REACT 2 Released

Reply #1002 –
I don't know of any command line tools to add album art to APE tags (TAK and WV) or to add to vorbis comments (OGG)... I'd love to know myself.


As for the virus report, if you got the .exe straight from Neil's website, I'm sure it's a false positive. If you are worried you can even compile the .exe yourself if you'd like
 

REACT 2 Released

Reply #1003 –
Quote from: feelgood on
First I rip the CD with EAC to a wav-image and then re-rip the wav file with React/Daemon-Tools to get a FLAC image-file and AAC track-files in two consecutive sessions (F4 and F10). This procedure is the fastest and most convinient to my knowledge. I tried to modify the ini and cfg-files to leave the temporary wav file, the cue file and the log file from a CD->FLAC-image conversion session intact, but it went too complicated. If somebody knows how to do that, I would be very happy to get the information.
You could quite easily do this in one stage with REACT.

Keeping the WAV image is easy. The only slightly complicated bit is ensuring that you have an accurate cuesheet for the WAVE file.  I would use SED for this: to amend the FLAC cuesheet, and save it in your WAV folder.  Here's how:

Assuming that you are using the amended CFGs, replace the section (at the beginning of the image processing code):

Code: [Select]
REM Ensure that the EAC log is available
:CheckForLog
IF NOT EXIST "@eaclog@" GOTO Pause

.. with this:

Code: [Select]
REM Ensure that the EAC log is available
:CheckForLog
IF NOT EXIST "@eaclog@" GOTO Pause


REM Store WAVE image
SET dest="@ImageDir_WAV@%imageDir%"
IF NOT EXIST %dest% MKDIR %dest%
PUSHD %dest%
    FOR %%G IN ("@image@") DO SET imageName=%%~nG
    COPY /Y "@source@" "%imageName%.wav"
    COPY /Y "@eaclog@" "%imageName%.log"
    @tools@\SED.EXE s/\.@imageext@/\.wav/ <"@cuesheet@" >"%imageName%.cue"
POPD

Then simply add a line in REACT.ini, under the [UserOutputNames] section, to set the value of ImageDir_WAV.

This additional code will create the folder that you specify with ImageDir_WAV.  It will then copy the source WAVE image to this folder, using the same naming scheme as your FLAC image ("<imageName>"). It will copy the EAC log to the folder naming it as "<imageName>.log".  Finally it will use SED to replace ".flac" with ".wav" in the cuesheet text, and save it as "<imageName>.cue".

Check this wiki article to find out where to get SED and what to do with it.
I'm on a horse.

REACT 2 Released

Reply #1004 –
I like your SED methodology on the wiki page, but I think I had ran into a problem with a similar methodology when trying to accomplish the same effect myself...

If there is an Ampersand in the resultant %TrackName%, doesn't sed replace it with the matched string? Or does your method somehow avoid that pitfall? I wasn't able to find a method to escape the ampersand within SED, as it didn't except \Q...\E regex within the RHS.

REACT 2 Released

Reply #1005 –
No, my method does not escape potentially problematic characters; so, you're right: it's possible that some filenames may cause a problem.

I guess with some effort we could escape characters before adding them to the SED command.  I hate doing this sort of thing in batch files though: the commands aren't really up to it.

Edit: @feelgood, BTW: the potential issue discussed does not affect the code above - only the code in the wiki article.  Fear not!
I'm on a horse.

REACT 2 Released

Reply #1006 –
Quote from: Synthetic Soul on
I hate doing this sort of thing in batch files though: the commands aren't really up to it.


I've certainly noticed this.

I was pondering at one point if I shouldn't just replace the whole DOS backend with a BASH one instead...

Maybe for this summer's "I'm Bored" project?

I don't think there are any other problematic characters, though. I believe the RHS only interprits Ampersands (Matched strings), backslashes and forward slashes. The latter two which should not be in %TrackName% anyway.

Edit: Whoops! Didn't mean to start a fear campaign. Fear not indeed!

REACT 2 Released

Reply #1007 –
Quote
Quote from: feelgood on

First I rip the CD with EAC to a wav-image and then re-rip the wav file with React/Daemon-Tools to get a FLAC image-file and AAC track-files in two consecutive sessions (F4 and F10). This procedure is the fastest and most convinient to my knowledge. I tried to modify the ini and cfg-files to leave the temporary wav file, the cue file and the log file from a CD->FLAC-image conversion session intact, but it went too complicated. If somebody knows how to do that, I would be very happy to get the information.

REACT is just EAC, only with things applied over it. Why not just set your INI:
Code: [Select]
ImageExt=flac
...
NeroAac=1

And do it in one pass instead of three? It should leave the EAC LOG alone, and it wouldn't make sense to keep the WAV-image when you have the FLAC image.

Thought it took me to the last page just now... sorry for the late reply.
OP can't edit initial post when a solution is determined  :'-(

REACT 2 Released

Reply #1008 –
FEAR NOT! I'm working on the SED problem right now.. actually have been couple of days already.. it's not easy but I think I got it figured out. There's more problematic chars besides the ampersand. I've gathered all the information and now I'm testing and creating escape code. I'll get back in 1-2 days (I can't use all my time to do these things u know).

The SED tool is a bad choice (in case there's more options to choose from) for "REACT:Amending Cuesheet File References" because there's no need to use regex in the substitution. If anyone knows a good DOS command line utility to just change strings in text files, let me know. It would be much easier to use without these regex special char escapes. It's impossible to write a "definitive" escape guide (or code) to SED since there's a few "what if user decides to do.." options.

And for the cherry on the top: SED converts all modified/created files into unix-type newline files (CR/LF -> LF). Files work ok in windows but... devil in the details kind of thing. I had to get a new tool (todos.exe) to change SED modified files back to CR/LF.

REACT 2 Released

Reply #1009 –
GSAR:  http://gnuwin32.sourceforge.net/packages/gsar.htm

Code: [Select]
gsar, ver 1.20 -- Copyright (C) 1992-2007 Tormod Tjaberg & Hans Peter Verne

Usage: gsar [options] [infile(s)] [outfile]
Options are:
-s<string> Search string
-r[string] Replace string. Use '-r' to delete the search string from the file
-i         Ignore case difference when comparing strings
-B         just display search & replace Buffers
-f         Force overwrite of an existing output file
-o         Overwrite the existing input file
-c[n]      show textual Context of match, 'n' is number of bytes in context
-x[n]      show context as a heX dump, 'n' is number of bytes in context
-b         display Byte offsets of matches in file
-l         only List filespec and number of matches (default)
-h         suppress display of filespec when displaying context or offsets
-du        convert a DOS ASCII file to UNIX (strips carriage return)
-ud        convert a UNIX ASCII file to DOS (adds carriage return)
-F         'Filter' mode, input from stdin and eventual output to stdout
-G         display the GNU General Public Licence

Ctrl characters may be entered by using a ':' in the string followed by the
ASCII value of the character. The value is entered using ':' followed by three
decimal digits or ':x' followed by two hex numbers. To enter ':' use '::'

Neither solution discussed today require regular expressions.  GSAR would require some extra coding to create the list of commands to execute, as it can't appear to run a list of actions from a text file as per SED; however I would assume that you could simply write GSAR commands to a batch file instead, and just execute it (rather than write SED actions to a text file and pass it to SED).


As an example, the SED line above:

Code: [Select]
@tools@\SED.EXE s/\.@imageext@/\.wav/ <"@cuesheet@" >"%imageName%.cue"

.. could be amended to:

Code: [Select]
@tools@\GSAR.EXE -s.@imageext@ -r.wav "@cuesheet@" "%imageName%.cue"
I'm on a horse.

REACT 2 Released

Reply #1010 –
This would be my suggestion for the cuesheet amend code:

Use the following in the track processing section:

Code: [Select]
SET trackCueFile="$cdartist$ - $album$.cue"
IF NOT EXIST %trackCueFile% COPY "@albumfile@.[mg].cue" %trackCueFile%
ECHO @tools@\GSAR.EXE "-sFILE """@basename@.wav"""" "-rFILE """%TrackName%.wv"""" -o %trackCueFile%>>update-cuesheet.bat

E.g.:

Code: [Select]
IF NOT @Wavpack@==1 GOTO end_wavpack_tracks
    IF NOT EXIST %TrackDir_Wavpack% MKDIR %TrackDir_Wavpack%
    PUSHD %TrackDir_Wavpack%
        IF @various@==1 SET VA_tag=-w "album artist=@VA@"
        ECHO ON
        @tools@\wavpack.exe @Opt_Wavpack@ %VA_tag% -w artist="@artist@" -w album="@album@" -w track="@track@/@numtracks@" -w title="@title@" -w year="@year@" -w genre="@genre@" -w comment="@comment@" -w encodedby="%USERNAME%" -w encodersettings="Wavpack @Ver_Wavpack@ @Opt_Wavpack@" "@source@" "%TrackName%.wv"
        @ECHO OFF
        SET trackCueFile="$cdartist$ - $album$.cue"
        IF NOT EXIST %trackCueFile% COPY "@albumfile@.[mg].cue" %trackCueFile%
        ECHO @tools@\GSAR.EXE "-sFILE """@basename@.wav"""" "-rFILE """%TrackName%.wv"""" -o %trackCueFile%>>update-cuesheet.bat
        IF %have_cover%==1 IF NOT EXIST folder.jpg COPY "@cover@" folder.jpg
        TITLE @track@/@numtracks@ - "@album@"
    POPD
:end_wavpack_tracks


Use the following in the final track section:

Code: [Select]
CALL update-cuesheet.bat
DEL update-cuesheet.bat

E.g.:
Code: [Select]
IF @Wavpack@==1 (
    PUSHD %TrackDir_Wavpack%
        IF %add_rg%==1 @tools@\wvgain.exe -a *.wv
        REM COPY /Y "@eaclog@" "EAClog.txt"
        CALL update-cuesheet.bat
        DEL update-cuesheet.bat
    POPD
)


If anyone wants to test and confirm we could add it to the wiki article.
I'm on a horse.

REACT 2 Released

Reply #1011 –
I can do it. I have already done some test code but just need to finish it later (I'm watching a hockey game currently).

I don't think you can escape quotes with "".

Here's my test (for general use):
Code: [Select]
REM ** test.txt contains one or more following line(s): this is a "piece" of: text to: test with :: this "" test text

REM ** VARS
SET text=this is a "piece" of: text to: test with :: this "" test text
SET outputText=TESTING DONE:all done "great" work :: "" thank you"

REM ** ESCAPE
SET text=%text::=::%
SET text=%text:"=:x22%

SET outputText=%outputText::=::%
SET outputText=%outputText:"=:x22%

gsar.exe "-s%text%" "-r%outputText%" "test.txt" "output.txt"

In general we need to escape two chars: the quote (") and the colon (:). The quote is escaped with hex (" -> :x22). I know that we don't need these escapes with "Amending Cuesheet File References", but I think that it would be better to include these (+text to explain them) because somebody could use GSAR to other needs.

Also I found this in the manual:
Code: [Select]
The precompiled MSDOS executable in the archive supports response files. Just put you gsar commands into a file and put a ‘@’ in front of the filename on the gsar command line. 

Example: file foobar.txt contains -ssupercalifragilisticexpialidocus: 
gsar @foobar.txt poppins.txt

So if you let me, I can change the wiki page later today. ok?

REACT 2 Released

Reply #1012 –
Quote from: Akkurat on
I don't think you can escape quotes with "".
The code I posted has been tested, and works.

Quote from: Akkurat on
I know that we don't need these escapes with "Amending Cuesheet File References", but I think that it would be better to include these (+text to explain them) because somebody could use GSAR to other needs.
I'm not sure that it should be included in that wiki article, but some tips for using GSAR elsewhere would always be useful.
I'm on a horse.

REACT 2 Released

Reply #1013 –
Quote from: Synthetic Soul on
You could quite easily do this in one stage with REACT.
Keeping the WAV image is easy. The only slightly complicated bit is ensuring that you have an accurate cuesheet for the WAVE file.  I would use SED for this: to amend the FLAC cuesheet, and save it in your WAV folder.  Here's how:
*
*
*
Then simply add a line in REACT.ini, under the [UserOutputNames] section, to set the value of ImageDir_WAV.

This additional code will create the folder that you specify with ImageDir_WAV.  It will then copy the source WAVE image to this folder, using the same naming scheme as your FLAC image ("<imageName>"). It will copy the EAC log to the folder naming it as "<imageName>.log".  Finally it will use SED to replace ".flac" with ".wav" in the cuesheet text, and save it as "<imageName>.cue".

Check this wiki article to find out where to get SED and what to do with it.

Synthetic Soul, you're the man! This worked perfectly!

Now, after ripping the CD (F10) and virtual-ripping the wav image-file (F4) I have:
1. FLAC-image and
2. iTunes AAC-tracks with all the appropriate cue and log files. I even get
3. the original WAV image-file and cuesheet to burn a backup copy of a badly scratched disc, if needed.

Thousand thanks!

SamHain86 and Akkurat:
React/iTunesEncode don't support one-pass conversion of FLAC-image and iTunes AAC-tracks. That should be added to the Wiki.

- feelgood

REACT 2 Released

Reply #1014 –
Quote from: Synthetic Soul on
Quote from: Akkurat on
I don't think you can escape quotes with "".
The code I posted has been tested, and works.

We were both right (if we count out my bad expression I made in a hurry): one can't _replace_ (this is what I meant) the quote with two quotes but three quotes.. quite confusing since the colon is escaped with replacing it with two colons. I would use the hex or decimal escape solution. But in fact we don't need that in "Amending Cuesheet..." because we can shorten the substitution to:

Code: [Select]
GSAR.EXE "-s@basename@.wav" "-r%TrackName%.wv"


Quote from: Synthetic Soul on
Quote from: Akkurat on
I know that we don't need these escapes with "Amending Cuesheet File References", but I think that it would be better to include these (+text to explain them) because somebody could use GSAR to other needs.
I'm not sure that it should be included in that wiki article, but some tips for using GSAR elsewhere would always be useful.

Any suggestions where? I think I'd put that in the "Amending Cuesheet..." wiki article since this is the only place where it's going to be used... BUT in the bottom part of the page with big header separating it from the main article. No?

REACT 2 Released

Reply #1015 –
Quote from: Akkurat on
But in fact we don't need that in "Amending Cuesheet..." because we can shorten the substitution to:

Code: [Select]
GSAR.EXE "-s@basename@.wav" "-r%TrackName%.wv"
I believe that I had the additional text to ensure that the right part was being acted upon; however, it should be reasonably safe to cut the text down to the above.

Quote from: Akkurat on
I think I'd put that in the "Amending Cuesheet..." wiki article since this is the only place where it's going to be used... BUT in the bottom part of the page with big header separating it from the main article. No?
I totally agree.  In retrospect the article is an acceptable place, if the additional code is added as an extra section at the bottom, as supplimentary information to the actual article text.

Thanks.
I'm on a horse.

REACT 2 Released

Reply #1016 –
So is
Code: [Select]
GSAR.EXE "-s@basename@.wav" "-r%TrackName%.wv"

The final verdict?

If Akkurat thinks it works then I guess I'm inclined to believe, since he tests everything so meticulously

REACT 2 Released

Reply #1017 –
Quote from: nago on
So is
Code: [Select]
GSAR.EXE "-s@basename@.wav" "-r%TrackName%.wv"

The final verdict?

If Akkurat thinks it works then I guess I'm inclined to believe, since he tests everything so meticulously

That's my trademark. Pain in the ass.  I vote yes.. would you believe?!  But seriously, is there a possibility to find more than one identical "$cdartist$ - $album$ - $track$ - $title$" text strings in cue file? No. At least the $track$ is always different. The "FILE "" string at the front makes no difference whatsoever.

The work is a little bit stopped because, can you already guess, I think I've found a bug/problem in GSAR (I emailed authors). Whatever I do, I find problems... I don't know if I should laugh or cry.  Get this; I still don't have my custom working REACT configured.. all I seem to do is bug hunt... I implemented tag.exe to my conf and found a bug/problem, fixed it, next SED amend cuesheets, major problems.. maybe I have my REACT working in the next century.

Anyone care to try following instructions with GSAR?
Code: [Select]
The precompiled MSDOS executable in the archive supports response files. Just put you gsar commands into a file and put a ‘@’ in front of the filename on the gsar command line. 

Example: file foobar.txt contains -ssupercalifragilisticexpialidocus: 
gsar @foobar.txt poppins.txt

This always gives me the following error message: "gsar: command error, no search string specified".

REACT 2 Released

Reply #1018 –
Quote from: feelgood on
SamHain86 and Akkurat:
React/iTunesEncode don't support one-pass conversion of FLAC-image and iTunes AAC-tracks.
Um... I am not quite sure what you mean... Is that because iTunesEncode does not support piping?

I use my REACT2 to rip a CD to a FLAC-image [with embedded CUE-sheet] AND create MP3 and OGG Tracks in one pass. Image mode can process the WAV and CUE to create the tracks using ACDir.
OP can't edit initial post when a solution is determined  :'-(

REACT 2 Released

Reply #1019 –
Quote from: nago on
So is
Code: [Select]
GSAR.EXE "-s@basename@.wav" "-r%TrackName%.wv"

The final verdict?
My string will work absolutely fine (whatever Akkurat's concerns) but the above should be perfectly adequate, and I would second it for the sake of clarity.

BTW: It took me five minutes of Googling to settle on GSAR.

Quote from: Akkurat on
The work  is a little bit stopped because, can you already guess, I think I've  found a bug/problem in GSAR (I emailed authors). Whatever I do, I find  problems...
Can you share what the problem is?
I'm on a horse.

REACT 2 Released

Reply #1021 –
Quote from: nago on
Quote from: Synthetic Soul on

Can you share what the problem is?
I think his issue is that he cannot get it to execute a script from file.

Correct. I'm sorry, I'm sometimes completely fu#%ing useless at communicating. It was clear to me that everybody would understand that the last request to test GSAR instructions I posted is the bug/problem I encountered. Sorry. *crawling back under my rock*

Quote from: Synthetic Soul on
My string will work absolutely fine (whatever Akkurat's concerns) but the above should be perfectly adequate, and I would second it for the sake of clarity.

Yes it works, I just offered a replacement so that we could get away from the confusing char escape.. as you say, for the sake of clarity.

REACT 2 Released

Reply #1022 –
Quote from: SamHain86 on
Quote from: feelgood on
SamHain86 and Akkurat:
React/iTunesEncode don't support one-pass conversion of FLAC-image and iTunes AAC-tracks.
Is that because iTunesEncode does not support piping?

I don't know for sure, but there is some discussion in this thread beginning from post #167.

- feelgood

(and I sure feel good now, thanks to this magnificent forum!)

REACT 2 Released

Reply #1023 –
Quote from: Akkurat on
Correct. I'm sorry, I'm sometimes completely fu#%ing useless at communicating. It was clear to me that everybody would understand that the last request to test GSAR instructions I posted is the bug/problem I encountered. Sorry. *crawling back under my rock*
No, that's fine, no doubt me being dumb.

I think I was probably confused as I didn't see it as being a very useful feature, and therefore not a showstopper for GSAR.  I'm glad to hear that it's not to do with the core functionality anyway.  I think GSAR could be useful for some other actions in REACT configs.
I'm on a horse.

REACT 2 Released

Reply #1024 –
Quote from: feelgood on
Quote from: SamHain86 on
Is that because iTunesEncode does not support piping?
I don't know for sure, but there is some discussion in this thread beginning from post #167.
Looking at the original REACT-image.cfg, there is no itune track setup. However:
  • there is the Nero AAC encoder; is there is big difference? They both use M4A
  • Would you be against using MP3?
Another idea for you is to use FB2K to transcode your FLAC-image configured with the iTunes AAC encoder, saving the time to mount a WAV image. Also, provided iTunes M4A allows it, it will keep all your tags, image art, and put the embedded EAC log into the M4A files you make.
OP can't edit initial post when a solution is determined  :'-(