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

REACT 2 Released

Reply #1425 –
Quote from: Akkurat on
Quote from: Endox on
So your guess about the AutoIt version would seem correct, but I've got no idea how to get around it, do you think it's incompatible with my OS version or something?

I don't know exactly what's going on, just a hunch.. but, there are other Vista users and you're the first one to report something like this.

I could build you a debug version to try to confirm the culprit. Also we could test older and newer AutoIt versions if that would help. Also I could try to change the way the info is read from the EAC window (if this truly is the problem here). I've just noticed in other case (other EAC save dialog problem.. again) a very strange behaviour of a ControlSetText-function in WinXP too which could finally explain the seemingly endless "image filename wrong" bughunting/fixing I've done with previous versions.. and with your case I'm guessing that the ControlGetText fails for some reason.. I haven't yet ended my tests with the previous problem but it seems to be a pretty clear case.. maybe there's a really strange, rarely occurring bug with these AutoIt functions (in newer AutoIt versions).

How does this sound? PM me your email and I'll get back to you, perhaps already tomorrow (it's 3am here in Finland and I'm going to bed.. to read a couple of short stories by Ray Bradbury ).

Sweet. Don't feel obliged at all, it sounds like a lot of work, but if you're happy to then I would certainly appreciate it. I'll PM you email add now.

REACT 2 Released

Reply #1426 –
Have just noticed something strange with Reacts replaygain of mp3's. I am ripping to flac image, flac tracks and then mp3 tracks.

Using mp3tag I wanted to check that the replaygain tags were getting populated. All flac tracks are OK. However a number (about 25 out of 8,000) mp3 tracks are missing replaygain tags (all 4 of them). In the main all these tracks end with a fullstop - a few don't but they all seem to be particularly long track titles. Some examples:

N.I.B.
L.A.
Momma...
Introduction-Workin' For MCA (Alternate Take, Previously Unreleased) (Live) (Bonus)

I wonder if this is a bug in React2

REACT 2 Released

Reply #1427 –
I wonder if someone could advise whether it is possible to pass thru to REACT, the filename as generated by EAC. I want to be able to do this in order to expand the options I have available with CDs containing indexed tracks (I have quite a number of these in my collection).
.
EAC handles indexes fine – each index is ripped as a separate track with the same track name but with the track number modified to incorporate the index number. So, for example,  track 4 , index 1 is numbered  04.01. When using FLAC as the compressor, that indexed filename is passed thru and all works OK.

When used with REACT, EAC still formulates the filename in that manner. However,  the filenaming processes in REACT are such that the same track number/track name is used for each index. Consequently, the same file name is applied to each index. So each index file simply overwrites the previous one and all I end up with is the last written.

There are alternatives of course. I can rip the index tracks using FLAC as the encoder and then rename the tracks and calculate replay gain with FooBar. I can also simply rip the track in REACT non-indexed and use my editor to extract the index segments from the combined wav file. Depending on the number of indexed tracks on the CD, any of those (and other) options might be OK. But I’d like to have the additional option of having REACT recognize the indexed track number.

Any help would be appreciated.

REACT 2 Released

Reply #1428 –
Quote from: gsa999 on
However a number (about 25 out of 8,000) mp3 tracks are missing replaygain tags (all 4 of them). In the main all these tracks end with a fullstop - a few don't but they all seem to be particularly long track titles.


So, do I understand correctly; you have some separate mp3 tracks without RG tags from different albums where other (or some) album tracks have the RG tags? Can you reproduce the problem when re-ripping the albums which have the affected tracks? Were you using amended .cfg files? If yes, can you test with the stock .cfg files? Also try to spot a pattern. You say that the tracks have long titles, have you counted the lengths and checked other long track titles from your collection? Can you test out metamp3.exe manually? Just run: "C:\Program Files\REACT\tools\metamp3.exe"  --replay-gain *.mp3 for the mp3 files which don't have RG tags.. does it work?   

REACT 2 Released

Reply #1429 –
Quote from: Mike-C on
I wonder if someone could advise whether it is possible to pass thru to REACT, the filename as generated by EAC. I want to be able to do this in order to expand the options I have available with CDs containing indexed tracks (I have quite a number of these in my collection).
.
EAC handles indexes fine – each index is ripped as a separate track with the same track name but with the track number modified to incorporate the index number. So, for example,  track 4 , index 1 is numbered  04.01. When using FLAC as the compressor, that indexed filename is passed thru and all works OK.

When used with REACT, EAC still formulates the filename in that manner. However,  the filenaming processes in REACT are such that the same track number/track name is used for each index. Consequently, the same file name is applied to each index. So each index file simply overwrites the previous one and all I end up with is the last written.

I'm a bit lost here, what are you trying to do?

Are you aware that REACT has 2 ripping methods?
1) F4 key = activates either Action -> Copy Selected Tracks -> Compressed... or Action -> Test & Copy Selected Tracks -> Compressed...
2) F10 key = activates either Action -> Copy Image & Create CUE Sheet -> Compressed... or Action -> Test & Copy Image & Create CUE Sheet -> Compressed...

REACT 2 Released

Reply #1430 –
Quote from: Akkurat on
I'm a bit lost here, what are you trying to do?

Are you aware that REACT has 2 ripping methods?
1) F4 key = activates either Action -> Copy Selected Tracks -> Compressed... or Action -> Test & Copy Selected Tracks -> Compressed...
2) F10 key = activates either Action -> Copy Image & Create CUE Sheet -> Compressed... or Action -> Test & Copy Image & Create CUE Sheet -> Compressed...


Hi Akkurat
Thanks very much for your prompt response and for the excellent work that you (and others) have done in developing this great set of integrated tools.
Based on your response, it seems my post wasn’t easily understood and I apologise for that. I realise the risk that adding more information to an unclear situation  will simply complicated matters even more.  However I’ve provide a bit of background and info about how I use REACT which may help. I am new to REACT  and this post probably reflects my limited experience and limited understanding of how REACT works. I’m not sure if this post infringes any post length rules or protocols but I couldn’t find any in the Help pages.
Using REACT
Usually, when using REACT, I rip the whole CD to FLAC in track mode. Occasionally I only rip selected tracks (but always the last track – so that RG can be applied) and I also sometimes rip to MP3 as well as FLAC. I note the advice about REACT being designed to work with whole albums but I haven’t had any problems ripping selectively. I don’t use image mode.
REACT Methods
I didn’t really understand your comments about REACT methods. It seems to infer that REACT only works via Hotkeys. I do realize that REACT can be invoked using a Hotkey but I find it works fine when invoked via the Action menu or associated shortcut keys. In my case I do mostly use F4 but not always because I find that method is sometimes more problematic. For example
  • Gap detection problems seem to arise much more frequently
  • Can’t find/move the cuesheet” situations sometimes occur – I’m guessing this is CoverDownloader related.
  • I find using the MetaData popup with sets is inefficient because the data is reset for each CD meaning that the common info has to be re-entered each time. I have a number of additional fields of MetaData and find this a nuisance. So I prefer to use Action -> Copy Selected Tracks -> Compressed from the EAC menu and edit the MetaIni file  manually with Notepad
  • Doesn’t provide access to index based ripping
So I do use the action menu quite often and successfully. Across the board I find action menu based extractions more reliable than the F4 method. I’ve compared files produced via F4 with those generated via the action menu and the normal shortcut keys and find they are all identical based on binary, MD5 and SHA-1 comparisons.
Indexing issues
I’m assuming that you understood that I’m using REACT to rip CDs some of which contain indexed tracks. EAC provides at least 2 methods of handling indexed tracks
Method 1 -  Indexed based.
This is done via Action -> Copy Selected Tracks Index Based ->  Un Compressed... (AltX) OR -> Compressed...(AltShiftX)
As I mentioned, each index is ripped as a separate track with the same track name but with the track number modified to incorporate the index.
Method 2 – Normal (ie non indexed)
As far as I’m aware, using any other extraction option, including the REACT F4 method, results in the indexed track being extracted as one consolidated wav file. This means the ability to directly access the indexed segments is lost (which defeats the purpose of indexing). So given that the F4 method doesn’t recognise indexes (at least for track extraction purposes) I’d need to use the action menu option.

Objective
The short answer to your “what do you want to do?” question is -  I’d like to be able to generate FLAC files with file names exactly the same as EAC uses to name the original ripped wav file.
When I rip to FLAC files using FLAC as the compressor, indexes work perfectly. EAC first generates wav files with the track number segment of the file name incorporating the index number. I end up with FLAC files named exactly like the extracted wav file.
Here is an actual example
H:\Flac Test\Doc Severinsen\ Trumpet Spectacular\ 07.01 Medley of Famous Tenor Arias.wav
H:\Flac Test\Doc Severinsen\ Trumpet Spectacular\ 07.02 Medley of Famous Tenor Arias.wav
H:\Flac Test\Doc Severinsen\ Trumpet Spectacular\ 07.03 Medley of Famous Tenor Arias.wav

H:\Flac Test\Doc Severinsen\ Trumpet Spectacular\ 07.01 Medley of Famous Tenor Arias.flac
H:\Flac Test\Doc Severinsen\ Trumpet Spectacular\ 07.02 Medley of Famous Tenor Arias.flac
H:\Flac Test\Doc Severinsen\ Trumpet Spectacular\ 07.03 Medley of Famous Tenor Arias.flac

When using REACT (via action menu) however, I initially get a wave file named exactly as described above. But this is immediately renamed to a Tmp name. In the case of this example, the compressor window would then be  opened three times to generate a FLAC for each index segment. But each time it does that it uses  “07 Medley of Famous Tenor Arias” as the file name – ie no index. So each file overwrites the previous one and all I end up with is the last written. I’m guessing that REACT uses the track number  and track name as passed via the “%t” and “%n” parameters from the EAC command line options. I’ve tried experimenting with the command line options  but without success.

A simple (in theory?) solution would be to write the FLAC file in REACT using  the same file name  that EAC uses when writing the original wav file - exactly as I assume FLAC does when interfacing directly with EAC. Alternatively, using the same track number as EAC uses would produce the same result. I presume (perhaps wrongly) that REACT overwrites the original wav filename with the temp file name so it presumably “knows” what file name to overwrite. I naively assume that because the EAC/FLAC process is capable of generating wav and FLAC files with identical names, that the functionally similar EAC/REACT process can do the same. I’m not sure whether that’s actually possible. Is there, for example a variable or EAC generated parameter available to REACT which has the original filename? If so, then I presumably could use that in the config file to generate the FLAC filename.

I hope this is a bit clearer. But like I said initially, I do have other options so its not a big deal if it can’t be done in the way I’d like. I’m always keen to add to my knowledge of this stuff so worst case is I may just learn something new and that can't be bad.

Thanks again for your help.

REACT 2 Released

Reply #1431 –
Quote from: Mike-C on
Usually, when using REACT, I rip the whole CD to FLAC in track mode. Occasionally I only rip selected tracks
...
It seems to infer that REACT only works via Hotkeys

You're on your own if you don't use REACT like it's meant to be used. The F4 or F10 ripping keys doesn't just activate certain ripping methods from EAC menu, pressing these keys do lot more. The source code is public, so you can check what REACT does (or modify it to your needs) if you're familiar with programming languages.

Quote from: Mike-C on
I do mostly use F4 but not always because I find that method is sometimes more problematic. For example
  • Gap detection problems seem to arise much more frequently
  • Can’t find/move the cuesheet” situations sometimes occur – I’m guessing this is CoverDownloader related.
  • I find using the MetaData popup with sets is inefficient because the data is reset for each CD meaning that the common info has to be re-entered each time. I have a number of additional fields of MetaData and find this a nuisance. So I prefer to use Action -> Copy Selected Tracks -> Compressed from the EAC menu and edit the MetaIni file manually with Notepad
  • Doesn’t provide access to index based ripping

  • Not REACT's fault, select different settings for EAC gap detection (Drive Options -> Gap Detection). Remember that some CD's could work with another setting and others not. I've 1 of this kind of CD out of about 450 CD's. Selecting another method makes the gap detection work with this CD.
  • It's most probably because of the gap detection errors. Although I've a high priority fix to be made to the cuesheet generation in my ToDo list.. if your CD's have lots of "track indices", which you seem to have, there is a problem in the code which could yield error messages you're seeing. I feel really stressed because I've so little time to put to REACT development (I've many ideas/enhancements and a loooong ToDo list).. also the support I try to give here in HA takes time.. and currently I'm debugging 2 different problems with 2 users.. it's hard to take time to further develop REACT. I've got to find a solution to this situation somehow.
  • I'm curious as to what such information do you have. If you have information that doesn't change ever, simply edit the track.cfg file add the needed tags this way. That said, I'll add this to my ToDo list.. a "keep data" checkbox for that add. metadata dialog.
  • Index Based ripping support for REACT, not happening, at least not in the near future. Sorry. It's not so simple to do.. I won't go into details. I'll add it to my ToDo list but with low priority.

Quote from: Mike-C on
I do have other options so its not a big deal if it can’t be done in the way I’d like.

You could use the profiles in EAC. E.g. save a full profile with different compression options (+other options if needed) when you need index based ripping. And save a profile for using REACT.

Thanks for writing and sorry that I couldn't help you out more.

REACT 2 Released

Reply #1432 –
Quote from: Akkurat on
So, do I understand correctly; you have some separate mp3 tracks without RG tags from different albums where other (or some) album tracks have the RG tags?
Yes that is correct
Quote from: Akkurat on
Can you reproduce the problem when re-ripping the albums which have the affected tracks? Were you using amended .cfg files? If yes, can you test with the stock .cfg files? Also try to spot a pattern. You say that the tracks have long titles, have you counted the lengths and checked other long track titles from your collection?
I have already re-ripped the CDs and got the same results. The main problem is track names with a fullstop at the end (there were only 2 with long file names). I am using slightly amended cfg files
Quote from: Akkurat on
Can you test out metamp3.exe manually?
Have done this and it works fine in terms of creating the 2 track RG values, so I have just updated the offending tracks like this - took about 1 hour so not too bad. I then went into each track using mp3tag and copied the 2 album RG values into the tag field (using the same value as all the other tracks on the album)


REACT 2 Released

Reply #1433 –
Quote from: gsa999 on

Found a bug in metamp3 (bug post here) which explains your problem.

Here's the fix to both .cfg files:

REACT-track.cfg:
Code: [Select]
IF %add_rg%==1 @tools@\metamp3.exe %RG_MetaMP3% *.mp3

change that line to:
Code: [Select]
IF %add_rg%==1 @tools@\Glob.exe -v -c @tools@\metamp3.exe %RG_MetaMP3% *.mp3


REACT-image.cfg:
Code: [Select]
IF %add_rg%==1 @tools@\metamp3.exe %RG_MetaMP3% *.mp3
IF @ApplyAlbumGain@==1 @tools@\metamp3.exe %ApplyAG_MetaMP3% *.mp3

change these lines to:
Code: [Select]
IF %add_rg%==1 @tools@\Glob.exe -v -c @tools@\metamp3.exe %RG_MetaMP3% *.mp3
IF @ApplyAlbumGain@==1 @tools@\Glob.exe -v -c @tools@\metamp3.exe %ApplyAG_MetaMP3% *.mp3


NOTE!
There's also a limitation in EAC (post #225) which crops long titles in cue files to 80 chars (first 77 chars of the title + 3 period chars). What this means in REACT is that when ripping tracks in image mode (F10), the track filenames are taken from TITLE fields by ACDIR and if the TITLE is cropped in the cuesheet, then you get cropped filenames PLUS cropped track title TAGS!! This affects ALL encoded tracks in image mode. In track mode ripping there's no problems.


gsa999, remember that if you copy RG values to files which haven't been in the calculation process with the other files, RG values are not correct for that whole album.

REACT 2 Released

Reply #1434 –
Hello,

I'm looking to set ARTISTSORT and ALBUMSORT tags in my FLAC images.  Ideally I want to trim the leading "The " for sorting purposes as documented in SlimServerSupportedTags.  I thought I had this figured out with the following code in my REACT-image.cfg however it fails if there are special characters my variables get truncated, if I nest them in quotes it doesn't work quite right either.  Any ideas?

Code: [Select]
SET strArtist=@cdartist@
SET strArtistParse=%strArtist:~0,4%
IF /I %strArtistParse%==the % %(SET strArtistSort=%strArtist:~4,99%) ELSE SET strArtistSort=%strArtist%
@echo %strArtist%
@echo %strArtistSort%


Code: [Select]
@echo off
SET strAlbum=@album@
SET strAlbumParse=%strAlbum:~0,4%
IF /I %strAlbumParse%==the % %(SET strAlbumSort=%strAlbum:~4,99%) ELSE SET strAlbumSort=%strAlbum%
@echo %strAlbum%
@echo %strAlbumSort%

REACT 2 Released

Reply #1435 –
Quote from: Endox on
I've been getting a problem with image names when using the Akkurat mod and hitting F10 - both the wav files and final image (FLAC or otherwise) are being named simply " - [].wav" or " - [].flac" etc.


I had this on one XP machine but not on another.  Turned out to be caused by having the Sony Ericsson PC Suite running.  I closed the PC Suite systray icon and the image name dialog box was populated correctly.

REACT 2 Released

Reply #1436 –
I'm a bit of a newbie and am confused about using REACT image mode.  I'm using REACT v2.0.akku.b03.  It's working correctly in that the disc is copied to an image which is named correctly.

However, when processing the image into tracks the track names are coming out as, for example, 01 - .flac and the tags aren't being populated with the artist name, album name or track name.  If I process the CD using track mode this all works fine, but I would like to keep an image and also have the MP3 and FLAC tracks created.  Looking at the CFG file for image mode I can see that these tags are supposed to be passed to acdir.exe and the encoder, but for the life of me I can't get it to work.

Am I missing sometihng obvious here (such as, it can't be done in image mode)?  I've spent ages trying to get it to work, and started from scratch several times but to no avail.

REACT 2 Released

Reply #1437 –
ACDIR extract the information from the cue sheet.

Go into EAC options (EAC > EAC Options...), switch to the Tools tab, and ensure "Use CD-Text information in CUE sheet generation" is checked.
I'm on a horse.

REACT 2 Released

Reply #1438 –
Quote from: Synthetic Soul on
Go into EAC options (EAC > EAC Options...), switch to the Tools tab, and ensure "Use CD-Text information in CUE sheet generation" is checked.


A big thank you for that - I would never have worked it out.  I had wrongly assumed that option related to reading CD-Text information from a disc, and as I had freedb disc information I would never need to read CD-Text.

REACT 2 Released

Reply #1439 –
Thanks Akkurat, will amend my config files
Quote from: Akkurat on
gsa999, remember that if you copy RG values to files which haven't been in the calculation process with the other files, RG values are not correct for that whole album.
Do you just mean the albumgain tags will be incorrect, or will the trackgain tags be incorrect as well - I recalculated the trackgains again manually using metamp3 and then just filled in the missing albumgain using the same value as the other tracks. I only really use trackgain so I'm not that bothered about albumgain being slightly out.




REACT 2 Released

Reply #1440 –
Quote from: BM29759 on
Ideally I want to trim the leading "The " for sorting purposes

Jeez, this topic has turned into a DOS command support topic.

Here's my jab at the problem (for your first code listing):
Code: [Select]
REM ** The % % at the end just illustrates that the string stored in var ends in space char.
SET strDefiniteArticle=the % %

SET strArtist="@cdartist@"

SETLOCAL EnableDelayedExpansion

REM ** Remove unnecessary quote chars.
SET strArtist=!strArtist:"=!

SET strArtistParse=!strArtist:~0,4!

IF /I !strArtistParse! EQU !strDefiniteArticle! (
    SET strArtistSort=!strArtist:~4!
) ELSE (
    SET strArtistSort=!strArtist!
)

SETLOCAL DisableDelayedExpansion

@echo "%strArtist%"
@echo "%strArtistSort%"

Note that the last ECHO vars are wrapped in quotes. I removed the "get 99 chars after char position 4" (~4,99), why limit the parse?

REACT 2 Released

Reply #1441 –
Quote from: hartpark on
Quote from: Endox on
I've been getting a problem with image names when using the Akkurat mod and hitting F10 - both the wav files and final image (FLAC or otherwise) are being named simply " - [].wav" or " - [].flac" etc.

I had this on one XP machine but not on another.  Turned out to be caused by having the Sony Ericsson PC Suite running.  I closed the PC Suite systray icon and the image name dialog box was populated correctly.

WOW! That's strange! Can you tell me what was the version of that Sony Ericsson PC Suite? Also tell me which phone (model) did you use? (the download page insist me to first choose a model.. maybe there are different versions for different phones?)

It's funny to hear this because I have just realized that the Endox problem is most probably caused by a newer version of AutoIt which has gone from ANSI to Unicode. I compiled my mod with later AutoIt version (with version that Synthetic Soul's mod uses) and it worked fine (the next AutoIt version causes the problem for Endox). This I believe is also linked to the problem with "wrong filename in save dialog" that gsa999 is having.

It's a tough situation; should I downgrade my AutoIt for REACT? Or, do I code around the problem with maybe not so nice solution? And, what about the next EAC version (current beta) with some Unicode changes (don't know exact changes due to lack of verbose changelogs)? And I can't properly test the problem because I can't reproduce it in my system. Is the problem in "ANSI" EAC, "ANSI" EAC & Unicode AutoIt or Unicode AutoIt? Hard decisions ahead.

Quote from: hartpark on
Quote from: Synthetic Soul on
Go into EAC options (EAC > EAC Options...), switch to the Tools tab, and ensure "Use CD-Text information in CUE sheet generation" is checked.

A big thank you for that - I would never have worked it out.  I had wrongly assumed that option related to reading CD-Text information from a disc, and as I had freedb disc information I would never need to read CD-Text.

Yes thank you Synthetic Soul, I didn't know that. The setting name is a bit misleading, the popup description though explains it better. I'm going to put this setting to the "config REACT" function. Synthetic Soul, do you know why this wasn't there in the first place? Is it safe to put it on for all users?

REACT 2 Released

Reply #1442 –
Quote from: gsa999 on
Do you just mean the albumgain tags will be incorrect, or will the trackgain tags be incorrect as well - I recalculated the trackgains again manually using metamp3 and then just filled in the missing albumgain using the same value as the other tracks. I only really use trackgain so I'm not that bothered about albumgain being slightly out.

Album Gain and Peak at least will be wrong, can't remember exactly but weren't there other tags as well, not the track gain&peak but others (some "undo" tags or something like that)? Also if you apply the album gain to mp3's, then it matters.

REACT 2 Released

Reply #1443 –
Quote from: Akkurat on
Synthetic Soul, do you know why this wasn't there in the first place? Is it safe to put it on for all users?
No, I don't.  I don't think Tycho paid too much attention to setting any EAC setting that may be required, only those that were absolutely required for basic operation.  I see no problem in ensuring that it is checked.

Keep up the good work.
I'm on a horse.

REACT 2 Released

Reply #1444 –
Quote from: Akkurat on
Quote from: BM29759 on
Ideally I want to trim the leading "The " for sorting purposes

Jeez, this topic has turned into a DOS command support topic.

Here's my jab at the problem (for your first code listing):
Code: [Select]
REM ** The % % at the end just illustrates that the string stored in var ends in space char.
SET strDefiniteArticle=the % %

SET strArtist="@cdartist@"

SETLOCAL EnableDelayedExpansion

REM ** Remove unnecessary quote chars.
SET strArtist=!strArtist:"=!

SET strArtistParse=!strArtist:~0,4!

IF /I !strArtistParse! EQU !strDefiniteArticle! (
    SET strArtistSort=!strArtist:~4!
) ELSE (
    SET strArtistSort=!strArtist!
)

SETLOCAL DisableDelayedExpansion

@echo "%strArtist%"
@echo "%strArtistSort%"

Note that the last ECHO vars are wrapped in quotes. I removed the "get 99 chars after char position 4" (~4,99), why limit the parse?


Thank you very much!  This is exactly what I was looking for...  I've added the year before the album in the album sort so my albums sort chronologically...  I've found an updated version of Atomic Parsley too so now they sort correctly on my iPod too...  This made my day!  Thanks again!

REACT 2 Released

Reply #1445 –
Quote from: hartpark on
I had this on one XP machine but not on another.  Turned out to be caused by having the Sony Ericsson PC Suite running.  I closed the PC Suite systray icon and the image name dialog box was populated correctly.

Thanks again for reporting this! Saved a lot of my time, Endox had the same software and it was causing the problem with REACT compiled with newer than 3.2.4.0 version of AutoIt.

@Synthetic Soul: Thanks, I'll add that setting to REACT.

REACT 2 Released

Reply #1446 –
Quote from: BM29759 on
I've added the year before the album in the album sort so my albums sort chronologically...  I've found an updated version of Atomic Parsley too so now they sort correctly on my iPod too...  This made my day!  Thanks again!

You're welcome. Is there a problem with the Atomic Parsley which comes with REACT?

REACT 2 Released

Reply #1447 –
Quote from: Akkurat on
You're welcome. Is there a problem with the Atomic Parsley which comes with REACT?


Nothing wrong with it...  I've been using it for some time now...  It just doesn't have the ability to add sorting tags...  from the Atomic Parsley Sourceforge.net forum I tracked down Elementary Productions and ultimately Tagger 3.2

The updated Atomic Parsley includes the following additional sortOrder tags.

  --sortOrder    (type)      (str)    Sets the sort order string for that type of tag.
                                      (available types are: "name", "artist", "albumartist",
                                        "album", "composer", "show")

REACT 2 Released

Reply #1448 –
I haven't been keeping up on the latest mods/fixes to REACT2 (ssb). I decided to try to install a fresh copy on a new computer by following these steps:

1) Installed EAC-0.99pb4.exe, then used the wizard to check for my CD drive's capabilities, etc.
2) Installed react20.exe.
3) Copied the updated files from REACT_2.0.ssb16p.zip into C:\Program Files\REACT2.
4) Started REACT2 and used F2 to set up the necessary settings.
5) Performed my first test rip (The Beatles White Album).

I noticed that many of the tools in the tools directory are slightly out of date. Notably (to me) WavPack (4.40.0 versus 4.50.0) and LAME (3.97 versus 3.98.x (which is currently the HA endorsed version? 3.98.2?)). Also the XUI version of the album art downloader doesn't seem to be there.

1) Is there a list of which software can be safely updated without blowing up REACT2's capabilities? Or an updated tools download?
2) Is there an install document which covers XUI or ... do I really need to go through this 58 page forum topic <eeek!> to remind myself how to get XUI running?

Thanks,
Bill
 

REACT 2 Released

Reply #1449 –
Quote from: Bill02888 on
1) Is there a list of which software can be safely updated without blowing up REACT2's capabilities? Or an updated tools download?
2) Is there an install document which covers XUI or ... do I really need to go through this 58 page forum topic <eeek!> to remind myself how to get XUI running?

1) Lame (edit: and flac & metaflac) can be updated safely AFAIK. Metamp3 is a different thing, updating that to a newer version (.92b5) breaks .cfg-files. Dunno about the rest. What tools would you like to update?
2) Just download the zip and extract that to the coverdownloader folder.. or install XUI and set the INI CoverDownloader setting to point to the installed directory. Also put the INI CoverDownloaderXUI setting to 1. That's all.

P.S. check out the mods Wiki page for an updated situation.