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: New tool: React - [Run EAC Tasks] (Read 288620 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

New tool: React - [Run EAC Tasks]

Reply #425
Also be aware that @track@==@numtracks@ won't work if the last track is one of those "data" tracks, because you can't copy it.

New tool: React - [Run EAC Tasks]

Reply #426
From REACT source code:
Code: [Select]
    If FileExists($g_eacLog) Then
        Local $logTime = fFileGetTime($g_eacLog)
        Local $srcTime = fFileGetTime($g_source_tmp)
        $g_islast = ($logTime >= $srcTime - 1 And $logTime <= $srcTime + 2)
    EndIf

If i understood correctly islast =1 when:
- log exists AND, if we assume log creation time = 0, the timestamp of the extracted file is in the time range [-1, 2].

That said, a failure should only occur when dealing with very fast extraction and short tracks (confirmed mounting a virtual image with daemon tools). Someone experienced other issues ?

edit: codebox with REACT source code added
WavPack 4.3 -mfx5
LAME 3.97 -V5 --vbr-new --athaa-sensitivity 1

New tool: React - [Run EAC Tasks]

Reply #427
There are various reports in this thread AFAIR.

Searching this thread for "islast" I found the following in the top 20 posts:

http://www.hydrogenaudio.org/forums/index....st&p=389778
http://www.hydrogenaudio.org/forums/index....st&p=435672

I remember seeing others when I used to hang around this thread more frequently.

It's a very valid point though: my test is not particularly "real-world".  I guess this will only happen with burst mode and very, very short tracks normally (?).
I'm on a horse.

New tool: React - [Run EAC Tasks]

Reply #428
Ok, I've got it downloading coverart and all automatically and using metaflac at the end to replaygain all the files, but it writes the tags in the wrong order (track first, then album unlike fb2k) and the tag names in uppercase (opposed to fb2k, which does lowercase). I know this is picky but it gets on my nerves, any solutions?
err... i'm not using windows any more ;)

New tool: React - [Run EAC Tasks]

Reply #429
I can't see anything wrong with your setup.

I have created a test config: ...

Please save this as "TEST-tracks.txt" and put it in your "/Config" folder.  Edit: Please ensure destdir1 is a valid path as it is used as the path for the log file. Then, change "react.ini" to use "TEST", set it going on the Sheryl Crow CD, and post the log created in a CODEBOX to this thread.  It may help.

FYI: Here are two example logs.  The first is using freedb info that got picked up for the test CD I created.  The second is using a VA setup with album, track artist and track names entered by me.  All values are as expected.
...
Some more info to help you make sense of the logs (CD meta data refers to Test Album.txt):

Naming scheme: %D - %C - %N - %T
Various artist naming scheme: %D - %C - %N - %T (%A)

CD Title: Test Album
CD Artist: Various

Tracks:
Artist One / Track One
Artist Two / Track Two
Artist One / Track Three
Artist Three / Track Four
Artist Two / Track Five

NB: Config file updated to newer version @ 12:08, so the output of my log may not exactly match yours.

FYI: To those interested.  To test I have created a nero NRG file of an audio CD created from 5 MP3s (the first five tracks of the Arctic Monkeys' album in fact).  I have mounted this NRG file using a virtual CD drive and am testing in burst mode.  This make s ripping extremely fast, and allows you to spend more time testing your scripts and less time watching EAC's progress bars.  You can, of course, just use one or two tracks, but I thought five better suited this issue.


Synthetic soul,
I used your TEST-tracks.txt file on the Sheryl Crow album and everything worked fine. The log file showed everything going to the right directory. Next, I tested this album with FLAC_MP3-tracks.txt. To my surprise, everything works fine with this album today. For the life of me, I can't figure out what changed between yesterday and today. Today, all the tracks end up in the right folders and all the WAV to FLAC and MP3 conversions work successfully.

Anyway, thanks for your help. The TEST-tracks.txt file will definitely come in handy for future troubleshooting.

atulc

New tool: React - [Run EAC Tasks]

Reply #430
How very strange.  At least it's working now.

I hope the TEST config will be of use to you, and perhaps others.  I may create a TEST-image config as well and upload that, as I hope others may find them useful.

Good luck with your ripping.
I'm on a horse.

New tool: React - [Run EAC Tasks]

Reply #431
I have tidied up the TEST-tracks.txt config and created TEST-image.txt.  Both can be found in this file: REACT-TEST-config.7z.

You can also see an example log with output from both the image and tracks config.

Hopefully thes configs will be useful for users finding it difficult to debug an existing config, and also new users wanting to get to grips with the variables that REACT exposes.

NB: To explain the @comment@ output "DISCNO":

@comment@ takes the value stored in the "ID3 Tag comment field" textbox found on the "Offset" tab of "Compression options".

I store all my backups on DVD.  I use @comment@ to pass the disc number that the archive should be stored on.  As I burn a disc I manually update this value in EAC.  At work I just use the value "DISCNO" and manually change the record when I paste it into the real log file at home, where I do actually pass the correct disc number.

Here's my WAVPACK config, for reference.  It creates a WavPack image with embedded cuesheet and EAC log; verifies the image; creates PAR2 data for the image; creates track MP3s using ACDIR; and writes the disc info, including DVD disc number, into a CSV file, creating the CSV with headers if it does not exist all ready:


Code: [Select]
!Description=Wavpack image with embedded cuesheet and EAC log with PAR2 data and CSV log

!ImageExt=wv
!CuesheetExt=wv.cue
!destdir1=@musicdir@\Wv\$cdartist$\$album$
!destdir2=@musicdir@\Log
!destdir3=@mydocumentsdir@\My Music

:CheckForLog
IF NOT EXIST "@eaclog@" GOTO Pause
WAVPACK.EXE -hm -w "CUESHEET=@@cuesheet@" -w "LOGFILE=@@eaclog@" -w "ARTIST=@cdartist@" -w "ALBUM=@album@" -w "YEAR=@year@" -w "GENRE=@genre@" "@source@" "@image@"
WVUNPACK.EXE -vm "@image@"
IF ERRORLEVEL 1 PAUSE
PAR2.EXE c -s204800 -r10 -- "@image@"
SET filename=$n - $~t
IF [$cdartist$] EQU [Various] SET filename=$n - $~t ^($~a^)
ACDIR.EXE --overwrite --output "@destdir3@\$~A\$~T\%filename%.mp3" --pipe "LAME.EXE -V5 --vbr-new --ignore-tag-errors --ta $#a --tl $#T --tt $#t --tn $#n --ty $#r{DATE} --tg $#r{GENRE} - $#o" "@sourcecuesheet@"
DEL "@source@"
MOVE "@eaclog@" "@destdir1@"
MOVE "@sourcedir@\@basename@.*" "@destdir1@"
IF NOT EXIST "@destdir2@\cdbackup.csv" ECHO Disc,Artist,Album,Date,Time> "@destdir2@\cdbackup.csv"
ECHO @comment@,"@cdartist@","@album@",%DATE%,%TIME%>> "@destdir2@\cdbackup.csv"
GOTO :EOF
:Pause
ECHO Waiting for EAC log file...
PING 1.1.1.1 -n 1 -w 2000 >NUL
GOTO CheckForLog

NB: I don't think I'd advise PAR2 for each WV file, it seems that creating data for the whole DVD disc image is better; however I've been doing this since I started and I've yet to have to use it, so I'm sticking with it for now.  I think dvdisaster looks pretty useful, but haven't gotten around to testing it seriously.
I'm on a horse.

New tool: React - [Run EAC Tasks]

Reply #432
Code: [Select]
:Pause
ECHO Waiting for EAC log file...
PING 1.1.1.1 -n 1 -w 2000 >NUL
GOTO CheckForLog

Is there a specific reason to introduce this ?
I'm curious, does this procedure ever been executed when ripping ?
WavPack 4.3 -mfx5
LAME 3.97 -V5 --vbr-new --athaa-sensitivity 1

New tool: React - [Run EAC Tasks]

Reply #433
I introduced this to the script I use at work.

I must admit I cannot say 100% whether it was a requirement or not, but I can only assume, by its presence, that I did see the requirement.  As I say, I do not have that code in the script at home.

I do not really pay any attention to the shell when it is executing, so I  cannot say whether it comes into play often, or ever.

Apologies for the vague answer!  In essence though I would say there must have been a reason why I added it.  I know I have suggested similar code to other users in this thread when it appeared that their log file was taking a fraction of a second too long to be created.

The difference between me running REACT at home and at work may be that at work (occassionally) I am doing other things while EAC runs, while at home I always leave EAC alone while it rips.  This extra load may be the reason for this small delay... perhaps.
I'm on a horse.

New tool: React - [Run EAC Tasks]

Reply #434
Firstly thx to Tycho for this program
I've a parsing issue with various artists string. Sometimes, freedb, returns tracknames with '/' and react, creates directories, so, at the end of the batch, only one file will be encoded (cause wav files are stored in different directories). I solved this by editing by hand the trackname, removing '/' character. (i've the latest v1.0)
If Tycho or someone else know how to fix this or have the same issue, can you please help?

Aside that, if Tycho or someone else is interested, I've added a little gui inside to change encoder and apply the settings without invoking notepad.

Cheers

New tool: React - [Run EAC Tasks]

Reply #435
If the CD is a VA CD track titles in the format "<artist> / <title>" is correct - changing them will cause more problems.  If the VA checkbox is checked, and your various artist naming scheme is correctly set to "%D - %C - %N - %T (%A)" (EAC options > Filename tab) there really should not be an issue.

Edit: I would be interested to see the GUI.  I have no problem editing by hand (although I rarely need to) but I'm always interested in seeing developments.  I think a GUI to set the INI settings and possibly a wizard to create configs (an idea I would like to pursue) could be very useful to some people.
I'm on a horse.

New tool: React - [Run EAC Tasks]

Reply #436
If the CD is a VA CD track titles in the format "<artist> / <title>" is correct - changing them will cause more problems.  If the VA checkbox is checked, and your various artist naming scheme is correctly set to "%D - %C - %N - %T (%A)" (EAC options > Filename tab) there really should not be an issue.


I change nothing. I report what happens to me. I don't exactly know why this happens, I've less and less time to spend to :-\

Also I report that $year$ returns empty value to me (-> a dir with "()" is created) but on the other hand, @year@ variable works ^^;

Quote
Edit: I would be interested to see the GUI.  I have no problem editing by hand (although I rarely need to) but I'm always interested in seeing developments.  I think a GUI to set the INI settings and possibly a wizard to create configs (an idea I would like to pursue) could be very useful to some people.


Nothing of exceptional. Just a tiny guy with 2 buttons (abort and apply) and a combobox with a list of avaible encoders. Once clicked on apply button, it hides the guy and writes the ini file with actual values.

I would like to see more about REACT.
Keep care ;-)

New tool: React - [Run EAC Tasks]

Reply #437
I change nothing. I report what happens to me. I don't exactly know why this happens, I've less and less time to spend to :-\
But you said:
I solved this by editing by hand the trackname, removing '/' character.
If you have no interest in pursuing this as a bug report why post in the first place?

Also I report that $year$ returns empty value to me (-> a dir with "()" is created) but on the other hand, @year@ variable works ^^;
That's easy, $year$ is not a valid token, as a year is always filename-friendly.  Always use @year@.

Nothing of exceptional. Just a tiny guy with 2 buttons (abort and apply) and a combobox with a list of avaible encoders. Once clicked on apply button, it hides the guy and writes the ini file with actual values.
OK, thanks.
I'm on a horse.

 

New tool: React - [Run EAC Tasks]

Reply #438
Moderation: Unneccessary quote removed (keeps things flowing better).

Here is a sample of the log file:

Code: [Select]
----- [MP3-tracks] ----- 2006-10-12 16:59:53
@echo Disc info   : "Queen" - "Greatest Hits II"
@echo Track info  : (2) "Under Pressure (1981)"
@echo Description : "LAME -V2 mp3 track files, RG album gain, APE2 and id3v1 tags"
echo.> "\MP3\Queen\(1996) Greatest Hits II\02 - Under Pressure (1981).mp3.tmp"
C:\PROGRA~1\REACT\Encoders\Tag.exe --nocheck --ape2 -t "ARTIST=Queen" -t "ALBUM=Greatest Hits II" -t "TRACK=2" -t "TITLE=Under Pressure (1981)" -t "YEAR=1996" -t "GENRE=Rock" -t "TOTALTRACKS=17" -t "FREEDB=EC11CD11" -t "CRC=08C8A2A1" "\MP3\Queen\(1996) Greatest Hits II\02 - Under Pressure (1981).mp3.tmp"
move "C:\Documents and Settings\x2f\Documenti\Qtmp1!542.wav" "\MP3\Queen\(1996) Greatest Hits II\02 - Under Pressure (1981).wav"
if True==1 (
  move "C:\Documents and Settings\x2f\Documenti\Greatest Hits II.log" "\MP3\Queen\(1996) Greatest Hits II\eaclog.txt"
  move "C:\Documents and Settings\x2f\Documenti\Greatest Hits II.[*].cue" "\MP3\Queen\(1996) Greatest Hits II"
  cd /d "\MP3\Queen\(1996) Greatest Hits II"
  C:\PROGRA~1\REACT\Encoders\WaveGain.exe -a *.wav --exec C:\PROGRA~1\REACT\Encoders\lame.exe -V2 --vbr-new --scale %%ALBUM_SCALE%% --tc "AG appl:%%ALBUM_GAIN%%,TG:%%TRACK_GAIN%% dB" "%%INPUT_NAME%%.wav" "%%INPUT_NAME%%.mp3"
  for %%i in (*.mp3) do C:\PROGRA~1\REACT\Encoders\Tag.exe --force id3v1 --force ape2 --fromfile "%%i.tmp" "%%i"
  del "*.mp3.tmp" "*.wav"
)
pause


As you can see, now $year$ works, but now, that True==1 appears.

That's wrong @islast@ value passed to batch file. I fixed it right now and everything works smoothly (/me crosses fingers). I just think to add a better gui to config it (with debug checkbox, buttons and such stuff).
Now i've to go, maybe later I add something. BTW I would like to hear from the author himself if I can post stuff (such new code , gui and installer).

Keep care as always

New tool: React - [Run EAC Tasks]

Reply #439
As you can see, now $year$ works
Actually, you're right.  I apologise.  $year$ should work exactly like @year@.  It is not invalid, just unnecessary.  NB: your log does not prove that as I can't tell what token you used! However, I checked the source and noted that both tokens are replaced by the same variable.

but now, that True==1 appears.
That is very strange.  The obvious intention, and what happens on my system, is that @islast@ is output as 0 or 1.  I wonder why yours should be outputing as "True"?  The variable is boolean, but I don't understand why one system would output it as 1 and another as True.

That's wrong @islast@ value passed to batch file. I fixed it right now and everything works smoothly (/me crosses fingers).
...
BTW I would like to hear from the author himself if I can post stuff (such new code , gui and installer).
Did you amend the source and recompile, or change your config?

I get the impression that you are amending the source, which may explain your "issues"...
I'm on a horse.

New tool: React - [Run EAC Tasks]

Reply #440
I get the impression that you are amending the source, which may explain your "issues"...


Believe or not, that issue comes with the original archive (the one published here).
And ok, I admit that I played with source, I'm guilty 

I would like to play with it more but I'm always on the run :-(

Now gotta go, cul8r

New tool: React - [Run EAC Tasks]

Reply #441
OK, when you have more time perhaps you should post your config and ini contents.  I can try them on my system to see what response I get. 

Alternatively, or additionally,  you could try my test config I posted in post #432 above, and post the log contents to this thread.  The config does not currently list $year$, but you could add that as per the others (i.e.: "@year@ ($year$)").
I'm on a horse.

New tool: React - [Run EAC Tasks]

Reply #442
News from me:


New tool: React - [Run EAC Tasks]

Reply #443
Fixed $year$ empty bug
Everything works but needs some testing 
It works for me without any fixing. 

Code: [Select]
==============================================
TEST-tracks config, Thu 12/10/2006 22:59:43.94
==============================================

"reactdir:      C:\Program Files\REACT"
"encdir:        C:\PROGRA~1\REACT\Encoders"
"mydocumentsdir: D:"
"musicdir:      E:\CDBackup"
"sourcedir:      F:"
"eaclog:        F:\The Album Name.log"
"destdir1:      E:\CDBackup\TEST\Various\The Album Name"
"destdir2:      E:\CDBackup\TEST"

----------------------------------------------

"trackscuesheet: F:\The Album Name"
"  single:      F:\The Album Name.[s].cue"
"  with:        F:\The Album Name.[mg].cue"
"  leftout:      F:\The Album Name.[m].cue"
"  corrected:    F:\The Album Name.[mc].cue"

----------------------------------------------

"basename:      Various - The Album Name - 01 - Track 1 (Artist 1)"
"source:        F:\Vtmp56)!5.wav"
"dest1:          E:\CDBackup\TEST\Various\The Album Name\01 - Track 1 (Artist 1)"
"dest2:          E:\CDBackup\TEST\The Album Name - 01 - Track 1 (Artist 1)"

"cdartist:      Various (Various)"
"album:          The Album Name (The Album Name)"
"artist:        Artist 1 (Artist 1)"
"title:          Track 1 (Track 1)"
"track:          1 (01)"

"numtracks:      2 (02)"
"islast:        0"
"genre:          "
"year:          2006 (2006)"
"comment:        41"
"freedbid:      11018102"

"crc:            5297D529"
"bitrate:        128"
"curdate:        2006-10-12"

----------------------------------------------

"basename:      Various - The Album Name - 02 - Track 2 (Artist 2)"
"source:        F:\Vtmp8)58-.wav"
"dest1:          E:\CDBackup\TEST\Various\The Album Name\02 - Track 2 (Artist 2)"
"dest2:          E:\CDBackup\TEST\The Album Name - 02 - Track 2 (Artist 2)"

"cdartist:      Various (Various)"
"album:          The Album Name (The Album Name)"
"artist:        Artist 2 (Artist 2)"
"title:          Track 2 (Track 2)"
"track:          2 (02)"

"numtracks:      2 (02)"
"islast:        1"
"genre:          "
"year:          2006 (2006)"
"comment:        41"
"freedbid:      11018102"

"crc:            62630444"
"bitrate:        128"
"curdate:        2006-10-12"

----------------------------------------------

==============================================
TEST-image config, Thu 12/10/2006 23:00:48.52
==============================================

"reactdir:      C:\Program Files\REACT"
"encdir:        C:\PROGRA~1\REACT\Encoders"
"mydocumentsdir: D:"
"musicdir:      E:\CDBackup"
"sourcedir:      F:"
"eaclog:        F:\The Album Name.log"
"destdir1:      E:\CDBackup\TEST\Various\The Album Name"

----------------------------------------------

"basename:      Various - The Album Name"
"source:        F:\Vtmp!)(0(.wav"
"image:          F:\Various - The Album Name.wav"
"sourcecuesheet: F:\Vtmp!)(0(-react.cue"
"cuesheet:      F:\Various - The Album Name.cue"

"cdartist:      Various (Various)"
"album:          The Album Name (The Album Name)"
"artist:        Artist 2 (Artist 2)"

"genre:          "
"year:          2006 (2006)"
"comment:        41"
"freedbid:      11018102"

"crc:            62630444"
"bitrate:        128"
"curdate:        2006-10-12"

----------------------------------------------

The year in brackets is retrieved using $year$.

Tested using my TEST configs, with $year$ added, using a test NRG image as the source.

The official AutoIt source has the lines:

Code: [Select]
$str = StringReplace($str, "$year$", $g_year)
... and
Code: [Select]
$str = StringReplace($str, "@year@", $g_year)
I don't understand how one can work and not the other.

Also, bear in mind, $year$ is not in the documentation, and @year@ will do exactly the same.  Why the need to use it?!

Edit: I am more and more coming to the conclusion that you are causing all of your problems by using a recompiled version of REACT.  I suspect that the True/1 issue is down to the version of AutoIt used to compile, or maybe your OS.  This is all guess work on my part, but your symptoms are very strange, you appear too quick to hack about with the source, and you don't appear to have any interest in getting help to resolve your issues, preferring to bugger around with the source that works fine for everyone else (AFAIK).  I would like to see the TEST config log file produced by your version of REACT and the official version.  Until then I don't see much point in trying to help further (not that it appears you want me to ).
I'm on a horse.

New tool: React - [Run EAC Tasks]

Reply #444
The fact that is working for you does not means that works for me; pls understand that those problem exists to me even if i recompile the src without modifying it. News: all Fkey are now fully customizable - bye

New tool: React - [Run EAC Tasks]

Reply #445
But why recompile the source?  As I say, I think you may be introducing issues by using a different version of AutoIt.  You're reporting "bugs" on things that don't exist in the official EXE.  If you are introducing them, how is this useful, or relevant, to the rest of us?  It really makes me keen to use your "new and improved" version that you appear to be working on...

Also, you're ignoring points, such as, why the need to use $year$ when @year@ is available and does the same thing?  You appear to be simply looking for problems, which you are actually creating yourself!

You started out talking of a "bug" with VA albums, but refuse to expand on the actual problem or provide any resource or proof to help us diagnose the issue.  You then post "bugs" that no-one else has ever reported - that you appear to have introduced yourself.

What are you trying to achieve?  I'm flumoxed.

Can other users confirm what @islast@ and $year$ returns for them?  I am not discounting the fact that I am totally wrong; it's just that I've never seen it reported before.
I'm on a horse.

New tool: React - [Run EAC Tasks]

Reply #446
I have recompiled REACT from the original source, using the latest AutoIt, version v3.2.0.1.

$year$ works fine for me (as expected), but I can confirm that @islast@ now returns True instead of 1.

To fix I simply changed:

Code: [Select]
$g_islast = ($logTime >= $srcTime - 1 And $logTime <= $srcTime + 2)

to

Code: [Select]
If ($logTime >= $srcTime - 1 And $logTime <= $srcTime + 2) Then $g_islast = 1

Edit: Bear in mind this will only affect users wanting to adapt the source and recompile.  It has no bearing on users using the official REACT 1.0 EXE.
I'm on a horse.

New tool: React - [Run EAC Tasks]

Reply #447
I am attemptingt to create a Wavpack image and yet all I'm getting is a cue sheet after the process completes.    Okay, here are my REACT settings:

Code: [Select]
[Settings]
Config=wv
Version=1.0
EAC=C:\Program Files\Exact Audio Copy\EAC.exe
musicdir=C:\Rips
encdir=C:\Program Files\REACT\Encoders
LogFile=react.txt
CodePage=1252
MinimizeCompressionWindow=1
ProcessPriority=1
TracksHotKey={F4}
TracksHotVal=+{F5}
SaveTracksCuesheets=0
ImageHotKey={F10}
ImageNaming=$artist$ - ($year$) $album$
Sla_Bks_Col_Qst_Bar_Quo_Ast_Lt_Gt=-|-|-||!|'|#|[|]
Debug=0


Here's my WV-image settings:
Code: [Select]
Description=Wavpack image with APEv2 RG album tags and embedded cuesheet and EAC log

ImageExt=wv
CuesheetExt=wv.cue
destdir1=@musicdir@\IMAGES\$cdartist$

start @encdir@\albumart.exe "@artist@" "@album@" "@destdir1@\@basename@.jpg"
@encdir@\WaveGain.exe -a "@source@" --exec @encdir@\wavpack.exe -hmy -w "ARTIST=@artist@" -w "ALBUM=@album@" -w "YEAR=@year@" -w "GENRE=@genre@" -w "REPLAYGAIN_ALBUM_GAIN=%%ALBUM_GAIN%% dB" -w "REPLAYGAIN_ALBUM_PEAK=%%ALBUM_PEAK%%" -w "REPLAYGAIN_TRACK_GAIN=%%TRACK_GAIN%% dB" -w "REPLAYGAIN_TRACK_PEAK=%%TRACK_PEAK%%" -w "CUESHEET=@@cuesheet@" -w "EACLOG=@@eaclog@" "@source@" "@image@"
del "@source@" "@eaclog@"
move "@sourcedir@\@basename@.*" "@destdir1@"


Now, here's the message that comes up when the process begins:



And, at the bottom of this pic, it appears as if the image is being created, but after it finishes, nothing is left but a cue file. 


Please let me know where I went wrong.  Thank you.

New tool: React - [Run EAC Tasks]

Reply #448
Change

Code: [Select]
Description=Wavpack image with APEv2 RG album tags and embedded cuesheet and EAC log

ImageExt=wv
CuesheetExt=wv.cue
destdir1=@musicdir@\IMAGES\$cdartist$

to

Code: [Select]
!Description=Wavpack image with APEv2 RG album tags and embedded cuesheet and EAC log

!ImageExt=wv
!CuesheetExt=wv.cue
!destdir1=@musicdir@\IMAGES\$cdartist$

I'm not sure whether that's all your problems solved, but make that change, try again, and report back if it's still not right.

Edit:  I suspect the WV file is somewhere, just not where it should be.  Because you weren't correctly defining destdir1 the MOVE command will have gone a bit screwy I guess.  I would expect the WV file to be in C:\Rips still but I assume it is not.  It may be in your REACT folder, your REACT\Encoders folder or in your Windows folder.  Maybe you could do a search for *.wv to track it down.  There's no point in leaving a 400MiB file around for no reason...
I'm on a horse.

New tool: React - [Run EAC Tasks]

Reply #449
The following script will encode LAME -V2 MP3 track files with ID3v1 + ID3v2 tags. The MP3s are then Album Gained with mp3gain.exe which also stores the RG info as APEv2.0 tags in the MP3s, so that it is possible to change from Album Gain to Track Gain in fb2k or for undoing the gain process completely. When playing the MP3s in a portable player that dosen't support RG, then the MP3s will be played Album Gained. Also there is added a "TOTALTRACKS" APEv2.0 tag to the MP3s. I would recommend that after the ripping and encoding has finished, then load the MP3s into fb2k and rewrite the tags as ID3v1 + ID3v2, so that the APEv2.0 tags are converted to ID3v2 tags and deleted afterwards, but that's of course up to you...

Code: [Select]
!Description=Album Gained LAME -V2 MP3 track files with ID3v1 + ID3v2 + APEv2.0 tags.

!destdir1=@musicdir@\$cdartist$ - ($year$) $album$
!dest1=@destdir1@\$track$ - $title$
!Various-dest1=@destdir1@\$track$ - $title$ ($artist$)

@encdir@\lame.exe -V2 --vbr-new --noreplaygain --add-id3v2 --pad-id3v2 --ignore-tag-errors --ta "@artist@" --tl "@album@" --tt "@title@" --tn "@track@" --ty "@year@" --tg "@genre@" "@source@" "@dest1@.mp3"
del "@source@"
@encdir@\Tag.exe --ape2 -t "TOTALTRACKS=@numtracks@" "@dest1@.mp3"
if @islast@==1 (
move "@eaclog@" "@destdir1@\eaclog.txt"
cd /d "@destdir1@"
@encdir@\mp3gain.exe -a -k *.mp3
)


Edit: Corrected mistake in command line.

Is there a way to integrate ID3v2.3 tags into the FLAC files ripped by EAC & REACT? The default FLAC_MP3-tracks.txt file uses tag.exe to write ID3v1 tags into the FLAC and MP3 files. The config file quoted above uses LAME's --add-id3v2 --pad-id3v2 flags to write ID3v2.3 tags to MP3 files. I also need to include ID3v2.3 tags on my FLAC files in case I need to use them to recreate my MP3 collection. Does anyone have an EAC/REACT config file for ripping tracks to FLAC and MP3 formats using ID3v2.3 tags for both formats?