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

REACT 2 Released

Reply #725 –
Martin H
Many thanks for the response. Can you confirm whether mp3gain is actually changing the content of my mp3's and what the difference is between this and replaygain. I am a little confused between what these two technologies
Rgds
Gordon

Hi Synthetic Soul
I have now successfully setup a @_ukdate@ token which is now appearing in the correct format in my comment field and I even managed to exclude it from the cuesheet by using the underscore. Thanks for this mod.

I had already implemented your suggestion from a couple of months ago about using my local albumart and that works fine as well.

Finally thanks to Martin H I have got metamp3 working and leading zeros on my mp3's.

Next task - this goes back to my earlier post about trying to automate REACT with existing WAVS and cuesheets. I have to admit I completely missed your change to run REACT from the command line; I will test this out tonight. However one thing I liked from doing it all manually - ie load the wav in daemon tools, load EAC, F10 was that I got a nice new cuesheet with all the correct info on - eg if genre was missing on the initial cue sheet it created a new cuesheet with genre included (becuase I put it in the EAC genre box). Another example would be the creation of a missing disk id. I am guessing this won't work with the command line option, so the cue sheet will not have any data that is not on the original one. Is this correct?

Gordon

REACT 2 Released

Reply #726 –
Re: the error I was getting:

Code: [Select]
Unhandled exception

at Gaps.2150 -> INDEX-RANGE


Quote from: Synthetic Soul on
Quote from: hobbsy on
Have you seen this before?
No!

I can't guess what application is raising that error.  Any more info?

Does this happen with only one disc, or with a few?


It's happened on about 3 out of the last 4 discs I tried.
Haven't had much time recently to test this out any more I'm afraid.
I might just try reverting back to the original REACT.ini / REACT-image.cfg / REACT-track.cfg files
I was probably getting too fussy - a set of FLAC and v0 mp3s are all I really need

REACT 2 Released

Reply #727 –
Quote from: gsa999 on
I have now successfully setup a @_ukdate@ token which is now appearing in the correct format in my comment field and I even managed to exclude it from the cuesheet by using the underscore. Thanks for this mod.
Ah, good thinking.  You're welcome.

Quote from: gsa999 on
... so the cue sheet will not have any data that is not on the original one. Is this correct?
Yes.
I'm on a horse.

REACT 2 Released

Reply #728 –
Quote from: gsa999 on
Many thanks for the response.

You're very welcome, mate
Quote
Can you confirm whether mp3gain is actually changing the content of my mp3's and what the difference is between this and replaygain.

Yes, your MP3's are getting the gain applied directly and i know that since you have previously said that you are getting a 'mp3gain_undo' tag field besides the other standard RG fields. Normally, then RG is just added as tags, which then RG aware players can parse and then scale the decoded output accordingly, but this then also means that non-RG aware players, like e.g. portables and such, will not be able to use the RG tags to adjust the loudness of the files. Therefore, some people preffer to apply the gain directly to the files, so that all players used will be able to playback the content with the wanted loudness even though they don't support parsing the RG tags and scalling the content accordingly. Also, when you apply the gain to your MP3s, then you can always undo the gain later on if needed, because you have those 'mp3gain_undo' tags in the files. So you have the option of either getting your MP3s to get the gain applied directly, or to just add RG tags to them instead. Btw, when you apply the gain directly, then those files will still have the RG tags in them, since this gives you the possibility of changing from e.g. album gain and to track gain and also because the applied gain is only applied in steps of 1.5dB and so the tags will make RG aware players scale the decoded output to reach a 0.01 dB precision by parsing those tags and scaling the decoded output during playback. Don't worry about the 1.5dB steps of precision when using non-RG aware players, since that is a neglible difference only. So, if you want the RG aplied directly, then in your REACT.ini you should set 'ApplyAlbumGain=1' and set 'AdjustAlbumGain_dB=+3.0' to whatever you like(the number is added to the 89dB standard reference, so if you e.g. just wants to follow the reference, then just set it to '0'). If you only want RG tags and not getting the gain applied directly, then set 'ApplyAlbumGain=0' and set 'ReplayGain=1'. Also, if you want to have RG tags on the lossless images/track files then you should set 'ReplayGain=1'. Btw, the option 'ApplyAlbumGain=1' only applies to lossy files and not lossless ones.

REACT 2 Released

Reply #729 –
Thanks Martin
Which one should I use on mp3 files for playing on (a) iPod and (b) Squeezebox

G

REACT 2 Released

Reply #730 –
I don't know about the Squeezebox, but i believe that ipods dosen't support RG(however they support a similar implementation called Soundcheck), so in that case, i guess that it would propperly be best to apply the gain directly. Personally, then i would recommend applying the RG through an alternative method which REACT also supports and which will cut about 10% off from the filesize for newer releases, but however, you cannot undo the gain applied with this method, though(but you can always transcode new MP3s from your lossless files anyway if needed). This method is about running WaveGain.exe on the WAV image to calculate the recommended album gain and scale value and then afterwards use that scale value together with lame.exe's '--scale' switch during encoding to MP3s. This will give smaller size and give you RG'ed playback on all equipment, but as i said, cannot be reversed, though. If you want to do this, then you should do the following to your REACT.ini : 'ApplyAlbumGain=1' & 'UseWaveGainAG=1' + also add 'REM' infront of this line under the mp3 tracks section in REACT-image.cfg :

IF @ApplyAlbumGain@==1 @tools@\metamp3.exe %ApplyAG_MetaMP3% *.mp3

When you do that, then the files will be scalled to have an average album gain value of 89dB and it dosen't matter what you have the following option set to as it isn't used in that case : 'AdjustAlbumGain_dB=+3.0'. If you don't add the 'REM' infront of the line, then metamp3.exe is runned on the MP3s additionally to alter them according to the 'AdjustAlbumGain_dB' option. If you want another value than 89dB, then i would advice you to forget this method and don't do any of the instructions i have given you in this post and instead just look at my last post for the right instructions.

REACT 2 Released

Reply #731 –
Thanks again for the explanation. I seem to have both RG tags and the mp3gain in my mp3's. I'll leave as is for the time being. I am pretty sure squeezebox can read RG tags, which is my main priority.

Another question though. As well as creating mp3 tracks I am creating a flac image which has cusheet, coverart and eac log embedded in it. What is the best way of viewing all this information in the flac afterwards. Also if I have embedded the cuesheet and the eac log do I need to keep them as seperate files.

REACT 2 Released

Reply #732 –
When you say 'view', then if you just mean to check that it's there, then i would recommend Mp3tag for that. About the issue of if you should save the cuesheets and logs externally, then it's up to yourself really. I personally do not keep them around as external files, as to me, then the biggest selling point of images with embedded cuesheets and eaclogs, is actually the fact that you just have one single file to represent each single album, and not three of them, but hey - that's just me. Some people keep the cuesheets externally for writing purposses, but still, there are several ways to extract the cuesheets quickly from the images whenever you need them, like e.g. Synthetic Soul's great ammended version of Tag.exe and foobar2000. Additionally, then Burrrn is a great little tool which even supports writing those images without you needing to extract the cuesheet from them first. At the end of the day, then it's really just a personal preference and nothing else...

REACT 2 Released

Reply #733 –
Quote from: Synthetic Soul on
FYI there is another way I found to get the freedb id, which is to export the disc data to a DB text file, ensuring that the settings (freedb / Database options > Export) are such that the freedb id is included.  However, this process is no less simple than creating a cuesheet, and requires that the user's EAC settings are tampered with (and maintained), so I still favour the cuesheet approach.


Does the option to export the 'whole' EAC database to db text ACTUALLY WORK for you.  When I do it, all I get is a string of zeros "00000000" in place of the disc id. 

e.g. 00000000;Sinatra Reprise;Frank Sinatra;The Last Dance;0:02:47.73;Frank Sinatra

However, if I stick a CD in the drive and choose the export to db text for the current CD, the discid is output correctly.

e.g. 230FCE14;Sinatra Reprise;Frank Sinatra;The Last Dance;0:02:47.73;Frank Sinatra

I'm using the latest version of EAC on WinXP sp2

Thanks.

REACT 2 Released

Reply #734 –
I get similar results to you when exporting the whole database.  Presumably EAC does not record the ID, so cannot provide it as part of the database, only when exporting the current disc info.

FYI the process I discussed was using the "Export CD Information To" option, exporting only the current disc info as an alternative to a cuesheet.
I'm on a horse.

REACT 2 Released

Reply #735 –
Quote from: Synthetic Soul on
I get similar results to you when exporting the whole database.  Presumably EAC does not record the ID, so cannot provide it as part of the database, only when exporting the current disc info.

FYI the process I discussed was using the "Export CD Information To" option, exporting only the current disc info as an alternative to a cuesheet.


I just wanted to confirm that I was not the only one experiencing this anomally with the discid when exporting the  'whole' database.  I used a text editor to open the EAC database file 'cddb.dat', and the discid does appear to be saved in the file.

Thanks.

REACT 2 Released

Reply #736 –
Hi
Would it be possible to add to the tracks section of image.cfg for mp3 files (and others) the ability to auto convert RG tags to iPod soundcheck tags and then add them to the ITUNESNORM tag. For iPod owners I think this would be a better solution to applying mp3gain.


I have just read a post about how it can be done in MP3Tag but it would be nice to be able to do it as part of the initial rip/transcode process.


G

REACT 2 Released

Reply #737 –
I remember Tycho being in a conversation about this - perhaps it was the metamp3 thread (I'll have to have a look).

Anyway, while searching for that I found this thread, which talks about a command line app, IPODRG.EXE, that will convert RG tags to SoundCheck tags.

It should be trivial to get metamp3 to write RG tags (as it should already) and then run this app to convert them to SoundCheck tags.

Edit:  Hmm... it seems the app needs a SoundCheck value to begin with (  ).  There is an explanation here regarding how to achieve this (a dummy value) with MP3Tag.  This should eb achievable with metamp3 also.  It may be worth checking first to see if it really does still need a value there to begin.

Edit: Would I be right in saying that you would set the dummy SoundCheck value with metamp3 using:

Code: [Select]
--frame "COMM[ITUNNORM]: 00000F0A 000003E2 000054FF 00003C89 00008AFA 00006158 0000842C 000084CF 0002FF0A 0001DDC1"
I'm on a horse.

REACT 2 Released

Reply #738 –
OK thanks SS. I don't know whether this command is right or not - its a bit too technical for me, hopefully someone else may know

In the meantime I have another problem. I would like to add the year of the album plus  hyphen in front of the album title so they sort in release order on the iPod.

I tried amending this line:

Code: [Select]
@tools@\acdir.exe --overwrite --output "%TrackName%.mp3" --extra-opt "APIC{3}:%cover%" --pipe "TITLE $n/$N mp3 $#T & @tools@\lame.exe @Opt_LameMP3@ %ApplyAG_Lame% - $#o & @tools@\metamp3.exe %Cover_tag% %VA_tag% %Disc_MP3_acdir% --artist $#a --album $#T --title $#t --track $n/$N --year $q@year@$q --genre $q@genre@$q --comment $q@comment@$q --frame TENC:$q%USERNAME%$q --frame TSSE:$qLAME @Ver_LameMP3@ @Opt_LameMP3@$q $#o" "@sourcecuesheet@"


to this

Code: [Select]
@tools@\acdir.exe --overwrite --output "%TrackName%.mp3" --extra-opt "APIC{3}:%cover%" --pipe "TITLE $n/$N mp3 $#T & @tools@\lame.exe @Opt_LameMP3@ %ApplyAG_Lame% - $#o & @tools@\metamp3.exe %Cover_tag% %VA_tag% %Disc_MP3_acdir% --artist $#a --album $#T --title $q@year@$q - $#t --track $n/$N --year $q@year@$q --genre $q@genre@$q --comment $q@comment@$q --frame TENC:$q%USERNAME%$q --frame TSSE:$qLAME @Ver_LameMP3@ @Opt_LameMP3@$q $#o" "@sourcecuesheet@"


I get an ACDIR crash with this though. Any ideas what I have done wrong 
 

REACT 2 Released

Reply #739 –
Use:

Code: [Select]
--title $q@year@ - $t$q

... or

Code: [Select]
--title $q$R{DATE} - $t$q

The "#"in "$#t" will surround the value in quotes, so yours would have ended up as

"2007" - "Title"
... not
"2007 - Title"

I don't really like the idea of poluting your tags in this way - but if it's the only way then who am I to argue.
I'm on a horse.

REACT 2 Released

Reply #740 –
Quote from: Synthetic Soul on
I don't really like the idea of poluting your tags in this way - but if it's the only way then who am I to argue.

Thanks
I agree totally, its horrible but its the only way I can get the year to appear on the iPod and also to get the albums sorted in release order rather than alphabetically!

I am also going to create an mp3tag action to do this on my existing mp3 collection and a second one to remove the year info. See my posts under the mp3tag thread yesterday and today mp3tag link

So should the firmware ever change on the iPod I can easily go through and get rid of the year from the title.

Rgds

REACT 2 Released

Reply #741 –
Just been tested ripping flac and mp3 tracks at the same time as a flac image. All works great. However looking into the RG tags in the flac and mp3 files I notice they are not the same.

The album gain and track gain figures are very close between the flac and mp3 version of same track. Maybe this is just a rounding in the calculations.

But album peak and track peak are considerably different between the flac and mp3 version of the same track. One says 1.30556 (flac) and the MP3 says 0.98751831

Is this what you would expect or is something not right here?

On another point. I mentioned in an earlier post that I had got SS's mod working with a ukdate token. I thought I would try to take this one step further and put this into the DefaultMetaData on react.ini

Instead of
_ukdate=
I then change the comment under UserSettings to
Comment=Created on @_ukdate@ 

This works when I manually type in a date in the metadate window. But I wanted to avoid having to type the date in manually each time so I tried:

_ukdate=%date%

%date% is the DOS command that pulls back the system date from the machine in UK format since that it how the PC is setup. I tried this in a test batch file ie

@echo off
set _ukdate=%date%
echo %_ukdate%
pause

The batch file works fine as a standalone test

But %date% does not work with REACT. My comment just appears as Created on %date%. Any ideas how I could get this to work.


Thx

REACT 2 Released

Reply #742 –
Quote from: gsa999 on
But %date% does not work with REACT. My comment just appears as Created on %date%. Any ideas how I could get this to work.
I think I'd have to see the code in question to attempt a response,  Looking at REACT-image.cfg I see the calls to ACDIR currently use some DOS variables, so I don't see why yours won't.

The only shot in the dark I can try would be to use something like:

Code: [Select]
SET Comment_tag=--comment $qCreated on %DATE%$q
...
@tools@\acdir.exe --overwrite --output "%TrackName%.mp3" --extra-opt "{3}@cover@" --pipe "TITLE $n/$N mp3 $#T & @tools@\lame.exe @Opt_LameMP3@ %ApplyAG_Lame% - $#o & @tools@\metamp3.exe --fit %Cover_tag% %VA_tag% %Disc_MP3_acdir% --artist $#a --album $#T --title $#t --track $n/$N --year $q@year@$q --genre $q@genre@$q %Comment_tag% $#o" "@sourcecuesheet@"
I'm on a horse.

REACT 2 Released

Reply #743 –
Quote from: gsa999 on
But album peak and track peak are considerably different between the flac and mp3 version of the same track. One says 1.30556 (flac) and the MP3 says 0.98751831

Getting different peak values between lossless and lossy formats is perfectly normal, since lossy encoders introduce quantization to the sample values. Btw, then the file with the peak of 1.30556 must be a MP3 file, since 16bit lossless files cannot have peaks over 32768 which then is normalized to 1.00 i.e. 32768 / 32768 = 1.00.

REACT 2 Released

Reply #744 –
Quote from: Synthetic Soul on
The only shot in the dark I can try would be to use something like:

Code: [Select]
SET Comment_tag=--comment $qCreated on %DATE%$q
...
@tools@\acdir.exe --overwrite --output "%TrackName%.mp3" --extra-opt "{3}@cover@" --pipe "TITLE $n/$N mp3 $#T & @tools@\lame.exe @Opt_LameMP3@ %ApplyAG_Lame% - $#o & @tools@\metamp3.exe --fit %Cover_tag% %VA_tag% %Disc_MP3_acdir% --artist $#a --album $#T --title $#t --track $n/$N --year $q@year@$q --genre $q@genre@$q %Comment_tag% $#o" "@sourcecuesheet@"

Hi SS
This works great. Many many thanks.
Interestigly I first tried putting the SET command in react.ini and it did not work, but when I put it in REACT-image.cfg it worked fine. Why would that be?

REACT 2 Released

Reply #745 –
Variables set in the INI are just REACT tokens, not DOS variables.

If you set it in the INI you would need to refer to it as @Comment_tag@, not %Comment_tag%.

Use the INI and @token@ tokens for static values, but use the CFG and DOS %var% variables for dynamic values.

Have you tried the SoundTouch stuff yet?
I'm on a horse.

REACT 2 Released

Reply #746 –
Quote from: Synthetic Soul on
Have you tried the SoundTouch stuff yet?

No not yet. I am testing a solution for populating the SoundCheck tag in mp3tag first this weekend. If that works I will then move onto trying to get it to work with REACT.

REACT 2 Released

Reply #747 –
Another REACT question
How do I stop it writing MP3 files with the ID3v1 tag - I only want ID3v2.3

Thx

REACT 2 Released

Reply #748 –
Quote from: gsa999 on
How do I stop it writing MP3 files with the ID3v1 tag - I only want ID3v2.3

In REACT-image.cfg change :

@tools@\acdir.exe --overwrite --output "%TrackName%.mp3" --extra-opt "APIC{3}:%cover%" --pipe "TITLE $n/$N mp3 $#T & @tools@\lame.exe @Opt_LameMP3@ %ApplyAG_Lame% - $#o & @tools@\metamp3.exe %Cover_tag% [...]

Into :

@tools@\acdir.exe --overwrite --output "%TrackName%.mp3" --extra-opt "APIC{3}:%cover%" --pipe "TITLE $n/$N mp3 $#T & @tools@\lame.exe @Opt_LameMP3@ %ApplyAG_Lame% - $#o & @tools@\metamp3.exe --2 %Cover_tag% [...]

Edit: Only the red part needs to be added i.e. '--2'.

REACT 2 Released

Reply #749 –
Quote from: Martin H on
Edit: Only the red part needs to be added i.e. '--2'.

Hi - this does not seem to have worked. When I look at the contents of the MP3 aqfterwards with the dbPowerAMP Explorer properties it still says it contains an ID3v1.1 tag as well as ID3v2.3. Should I be setting -- id3v2-only in LAME as well.

Also I notice that the ID3v2.3 says ANSI in brackets. Using MP3tag on another mp3 file (not created with REACT) it says UTF16 in brackets for v2.3. Which one should I be using and how do you change them in REACT2? Is there somewhere that explains what all these different tags mean?

Rgds