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 1280128 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

REACT 2 Released

Reply #476
A problem arose - now it's the tracks
while most of the files LAME fine
Code: [Select]
TITLE 07/13 mp3 "Serenade; 5 Pieces for Orchestra; Ode to Napoleon Buonaparte -
Boulez/BBC Sym..." & C:\PROGRA~1\REACT2\tools\lame.exe -V3 --vbr-new --noreplayg
ain --nohist  - "07 - VII. Finale.mp3" & C:\PROGRA~1\REACT2\tools\metamp3.exe --
pict "{3}C:\Documents and Settings\ibm\Moje dokumenty\Serenade; 5 Pieces for Orc
hestra; Ode to Napoleon Buonaparte - Boulez BBC Symphony Ensemble InterContempor
ain Shirley-Quirk W.jpg"  --artist "Arnold Schoenberg" --album "Serenade; 5 Piec
es for Orchestra; Ode to Napoleon Buonaparte - Boulez/BBC Sym..." --title "VII.
Finale" --track 07/13 --year "" --genre "Classical" --comment "Created with EAC/
REACT2, 2007-07-19" --frame TENC:"ibm" --frame TSSE:"LAME 3.97 -V3 --vbr-new --n
oreplaygain --nohist" "07 - VII. Finale.mp3"
LAME 3.97 32bits (http://www.mp3dev.org/)
CPU features: MMX (ASM used), SSE (ASM used), SSE2
Using polyphase lowpass filter, transition band: 17960 Hz - 18494 Hz
Encoding <stdin> to 07 - VII. Finale.mp3
Encoding as 44.1 kHz VBR(q=3) j-stereo MPEG-1 Layer III (ca. 8.2x) qval=3
metamp3 v0.91 - Copyright © 2006 by Tycho
Updating: 07 - VII. Finale.mp3
some do not
Code: [Select]

TITLE 08/13 mp3 "Serenade; 5 Pieces for Orchestra; Ode to Napoleon Buonaparte -
Boulez/BBC Sym..." & C:\PROGRA~1\REACT2\tools\lame.exe -V3 --vbr-new --noreplayg
ain --nohist  - "08 - 5 Pieces for Orchestra, Op. 16 -- I. Vorgefuhle.mp3" & C:\
PROGRA~1\REACT2\tools\metamp3.exe --pict "{3}C:\Documents and Settings\ibm\Moje
dokumenty\Serenade; 5 Pieces for Orchestra; Ode to Napoleon Buonaparte - Boulez
BBC Symphony Ensemble InterContemporain Shirley-Quirk W.jpg"  --artist "Arnold S
choenberg" --album "Serenade; 5 Pieces for Orchestra; Ode to Napoleon Buonaparte
 - Boulez/BBC Sym..." --title "5 Pieces for Orchestra, Op. 16 -- I. Vorgefuhle"
--track 08/13 --year "" --genre "Classical" --comment "Created with EAC/REACT2,
2007-07-19" --frame TENC:"ibm" --frame TSSE:"LAME 3.97 -V3 --vbr-new --noreplayg
ain --nohist" "08 - 5 Pieces for Orchestra, Op. 16 -- I. Vorgefuhle.mp3"
Can't init outfile '08 - 5 Pieces for Orchestra, Op. 16 -- I. Vorgefuhle.mp3'
metamp3 v0.91 - Copyright © 2006 by Tycho

Usage: C:\PROGRA~1\REACT2\tools\metamp3.exe [options] [mp3files]
options:
  --artist <artist>   audio/song artist
  --album <album> audio/song album
  --track <track>[/total] audio/song track number
  --title <title> audio/song title
  --year <year>   audio/song year of issue (1 to 9999)
  --genre <genre> audio/song genre name
  --comment [[desc]][{lng}]<text> add user-defined text
  --user-text [[desc]]<text>   add user text frame (TXXX)
  --user-url [[desc]]<URL> add user URL frame (WXXX)
  --frame <frame:text> set any T* or W* type frame
  --pict [[desc]][{type}]<file>  add picture artwork
  --save-pict <pict>   pict=[[desc]][{type}]<file>
  --list-pict-types   list possible picture type numbers
  --list-frames   list Text and URL id3v2.3 frames
  --list-genres   list standard id3v1.1 genres
  --1 add id3v1 tag only (default both v1 and v2)
  --2 add id3v2 tag only (--1 --2 will add both)
  --fit   add id3v1 + id3v2 if tag does not fit id3v1
  --remove [[desc]]<frame> remove frame(s). accepts wildcards *,?
  --replay-gain   calculate and set replay gain tags
  --apply-gain <gain> change volume. gain=[album|radio]<+dB|-dB>
  --undo-gain undo previous apply-gain
  --info   print detailed mp3/lametag info
  --version   show version info
  --help   show this help
Very strange
IH
EDIT:
I did it again, and the results were the same. I'm using the latest SynthS's react
EDIT:
Now that's weird - Foobar brought errors on the very same files - maybe it's a filename problem?
Code: [Select]
Error writing to file (Encoder has terminated prematurely with code -1; please re-check parameters) : file://C:\Documents and Settings\ibm\Moje dokumenty\@OutRoot@\MP3\Arnold Schoenberg\[] Serenade; 5 Pieces for Orchestra; Ode to Napoleon Buonaparte - Boulez-BBC Symphony-Ensemble InterContemporain-Shirley-Quirk-W\04 IV. Sonett von Petrarca_ 'O konnt' ich je der Rach' an ihr genesen'.mp3

REACT 2 Released

Reply #477
Can we see the cuesheet please?  Surround the text with [CODEBOX] and [/CODEBOX].

LAME is failing to encode the file.  I can only assume that it is a file naming issue.  Does the cuesheet have the track title as "5 Pieces for Orchestra, Op. 16 -- I. Vorgefuhle"?
I'm on a horse.

REACT 2 Released

Reply #478
I can only assume that it is a file naming issue.
That's what I thought. Here's the cuefile

Code: [Select]
REM DISCNUMBER 1
REM TOTALDISCS 1
REM GENRE Classical
REM DISCID C30F6E0D
REM COMMENT "ExactAudioCopy v0.99pb1"
PERFORMER "Arnold Schoenberg"
TITLE "Serenade; 5 Pieces for Orchestra; Ode to Napoleon Buonaparte - Boulez/BBC Sym..."
FILE "Arnold Schoenberg - Serenade; 5 Pieces for Orchestra; Ode to Napoleon Buonaparte - Boulez-BBC Symphony-Ensemble InterContemporain-Shirley-Quirk-W.flac" WAVE
  TRACK 01 AUDIO
    TITLE "Serenade, Op. 24 -- I. Marsch"
    PERFORMER "Arnold Schoenberg"
    INDEX 01 00:00:00
  TRACK 02 AUDIO
    TITLE "II. Menuett"
    PERFORMER "Arnold Schoenberg"
    INDEX 01 04:34:52
  TRACK 03 AUDIO
    TITLE "III. Variationen"
    PERFORMER "Arnold Schoenberg"
    INDEX 01 11:55:20
  TRACK 04 AUDIO
    TITLE "IV. Sonett von Petrarca: 'O konnt' ich je der Rach' an ihr genesen'"
    PERFORMER "Arnold Schoenberg"
    INDEX 01 16:10:05
  TRACK 05 AUDIO
    TITLE "V. Tanzscene"
    PERFORMER "Arnold Schoenberg"
    INDEX 01 19:04:47
  TRACK 06 AUDIO
    TITLE "VI. Lied (ohne Worte)"
    PERFORMER "Arnold Schoenberg"
    INDEX 01 26:10:17
  TRACK 07 AUDIO
    TITLE "VII. Finale"
    PERFORMER "Arnold Schoenberg"
    INDEX 01 28:32:60
  TRACK 08 AUDIO
    TITLE "5 Pieces for Orchestra, Op. 16 -- I. Vorgefuhle"
    PERFORMER "Arnold Schoenberg"
    INDEX 00 33:58:05
    INDEX 01 34:07:55
  TRACK 09 AUDIO
    TITLE "II. Vergangenes"
    PERFORMER "Arnold Schoenberg"
    INDEX 01 36:10:37
  TRACK 10 AUDIO
    TITLE "III. Farben"
    PERFORMER "Arnold Schoenberg"
    INDEX 01 40:52:50
  TRACK 11 AUDIO
    TITLE "IV. Peripetie"
    PERFORMER "Arnold Schoenberg"
    INDEX 01 43:43:10
  TRACK 12 AUDIO
    TITLE "V. Das obligate Rezitativ"
    PERFORMER "Arnold Schoenberg"
    INDEX 01 45:47:05
  TRACK 13 AUDIO
    TITLE "Ode to Napoleon Buonaparte, Op. 41"
    PERFORMER "Arnold Schoenberg"
    INDEX 00 49:17:22
    INDEX 01 49:27:00
Quote
Does the cuesheet have the track title as "5 Pieces for Orchestra, Op. 16 -- I. Vorgefuhle"?"
As you see, it does.
Thanks,
IH

REACT 2 Released

Reply #479
I just used your cuesheet with another WAVE file, using this command line:

Code: [Select]
ACDIR.EXE -o "%n - %~t.mp3" --pipe "LAME.EXE -V3 --vbr-new --noreplaygain - $#o" "Arnold Schoenberg - Serenade; 5 Pieces for Orchestra; Ode to Napoleon Buonaparte - Boulez-BBC Symphony-Ensemble InterContemporain-Shirley-Quirk-W.cue"

All MP3s were created.  I then tried (more similar to the actual line REACT would have executed):

Code: [Select]
ACDIR.EXE --overwrite --output "%n - %~t.mp3" --pipe "TITLE $n/$N mp3 $#T & LAME.EXE -V3 --vbr-new --noreplaygain - $#o & METAMP3.EXE --fit --artist $#a --album $#T --title $#t --track $n/$N --year $q$R{YEAR}$q --genre $q$R{GENRE}$q --comment $q$R{COMMENT}$q $#o" "Arnold Schoenberg - Serenade; 5 Pieces for Orchestra; Ode to Napoleon Buonaparte - Boulez-BBC Symphony-Ensemble InterContemporain-Shirley-Quirk-W.cue"

... and all MP3s were created again.

I'm a bit stumped what to try next!  Have you edited the MP3 track section of the config at all?

Did track 9 work?  Was it only track 8 that failed?  Has it failed repeatedly (i.e.: if you rip the disc again does it always fail on track 8)?  Is it only with this disc that this has happened?

I'm not sure if you can pass on any more information but I'm stumped for now.  The only other thing I could think of for the "Can't init outfile" error would be some sort of disk error...

Edit: Another thought: is it possible somehow that the WAVE has been truncated, so that it was not long enough for track 8 (34:07:55)?  I'm going to test this to see what LAME or ACDIR says in this circumstance.
Edit: Meh.  ACDIR just reports "Failed to open the input file!".
I'm on a horse.

REACT 2 Released

Reply #480
Have you edited the MP3 track section of the config at all?

I do not think I did.

Quote
Did track 9 work?  Was it only track 8 that failed?  Has it failed repeatedly (i.e.: if you rip the disc again does it always fail on track 8)?  Is it only with this disc that this has happened?


All the disc converted fine, except 4&8. I had the same problem with another disc, a Stravinsky with french titles - maybe it's a problem of non standard ASCII characters (>128)? I'm using the polish version of XPs, so maybe there's some code page conflict.
I ripped 12+ discs today, and had errors just on those two - one has German, another French characters
Quote
Edit: Another thought: is it possible somehow that the WAVE has been truncated, so that it was not long enough for track 8 (34:07:55)?  I'm going to test this to see what LAME or ACDIR says in this circumstance


No, wave (flac) is ok, plays ok. What's more, converting by fb2k gave errors on the very same file! So it looks like a LAME problem.
Now ain't that strange?
IH

REACT 2 Released

Reply #481
You may want to check the full filename length. The OS limit is 260 characters (MAX_PATH).

REACT 2 Released

Reply #482
You may want to check the full filename length. The OS limit is 260 characters (MAX_PATH).
I can't believe that I didn't think of that.  Thanks robert.

4 and 8 have the longest track names.

I can replicate it using a long path.

Edit: I have tested, and it seems that you can utilise the GetShortPath tip.

1. At the bottom of your REACT-image.cfg file replace:

Code: [Select]
REM ** Delete this .bat file
DEL %0

... with:

Code: [Select]
REM ** Delete this .bat file:
DEL %0

GOTO :EOF

:GetShortPath
SET %2=%~fs1
GOTO:EOF


2. In the LAME tracks section replace:

Code: [Select]
SET dest="@TrackDir_MP3@"

.. with:

Code: [Select]
SET dest="@TrackDir_MP3@"
CALL :GetShortPath %dest% destShortPath

...and:

Code: [Select]
@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_tag% %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 $#o" "@sourcecuesheet@"

... with:

Code: [Select]
@tools@\acdir.exe --overwrite --output "%destShortPath%\%TrackName%.mp3" --extra-opt "{3}@cover@" --pipe "TITLE $n/$N mp3 $#T & @tools@\lame.exe @Opt_LameMP3@ %ApplyAG_Lame% - $#o & @tools@\metamp3.exe %Fit_tag% %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 $#o" "@sourcecuesheet@"


If my tests are anything to go by this should appease LAME.

Edit: clarified final amend (see post #489).
I'm on a horse.

REACT 2 Released

Reply #483
Hi - I'm new to React and this forum - both are fantastic!

Have got React working nicely thanks to a bit of research, but cannot figure out how to set the bitrate of my MP3 encoding. Always seems to rip using VBR, but would love it to be 192.

Am also trying to figure out exactly what is being done to the FLAC files that React outputs. I am after bitperfect files as exact as possible to the original on the CD. I assume that by their nature, the various 'gain' instructions will impact on the FLAC file produced, thereby making the file louder or softer than the original recording. Is this correct? If it is, what is the best way to ensure a FLAC file that is unadulterated in any way? Are there other processes happening that may also change the file?


Many thanks...

Sorry... also noticed that the MP3 files being produced seem noticeably quieter than the FLAC files with React. When using another program to rip MP3, the comparative volume against FLAC seems almost identical. Any suggestion as to why this may be happening?

REACT 2 Released

Reply #484
Have got React working nicely thanks to a bit of research, but cannot figure out how to set the bitrate of my MP3 encoding. Always seems to rip using VBR, but would love it to be 192.
The LAME settings can be amended using the Opt_LameMP3 setting under the [UserSettings] section in REACT.ini.  However, I would recommend sticking with VBR files, but if you want higher bitrate maybe changing -V5 to -V2.  If you must have 192 CBR then change the line to:

Opt_LameMP3=-b 192 --noreplaygain --nohist

Am also trying to figure out exactly what is being done to the FLAC files that React outputs. I am after bitperfect files as exact as possible to the original on the CD. I assume that by their nature, the various 'gain' instructions will impact on the FLAC file produced, thereby making the file louder or softer than the original recording. Is this correct? If it is, what is the best way to ensure a FLAC file that is unadulterated in any way? Are there other processes happening that may also change the file?
...
Sorry... also noticed that the MP3 files being produced seem noticeably quieter than the FLAC files with React. When using another program to rip MP3, the comparative volume against FLAC seems almost identical. Any suggestion as to why this may be happening?
Your summary of replay gain is essentially correct, although you may want to read up on it in the wiki.  The calculations should only be stored as tags unless you specify ApplyAlbumGain=1 in your INI, in which case the volume will be permanently altered.  There is no concern over having RG tags stored, and your file will be no less lossless.

Perhaps you should post your INI, surrounding it with [CODEBOX] and [/CODEBOX], so we can see how your gain-related settings are currently set.

Edit: RE: gain settings.  It may also be worth looking at this post in this thread
I'm on a horse.

REACT 2 Released

Reply #485
Really appreciate your response!

I would recommend sticking with VBR files, but if you want higher bitrate maybe changing -V5 to -V2.
I like CBR because I know I am listening to a constant. Is the reason you suggest using VBR because it will provide grater quality at a smaller size due to the varied in bitrate? Or are there other benifits?

The calculations should only be stored as tags...  There is no concern over having RG tags stored, and your file will be no less lossless.
Meaning that the tag can be altered easily at a later stage? Didn't know you could set this kind of parameter via tags - pretty impressive. So setting gain to 0 would be the same as the original recording during playback?

Perhaps you should post your INI so we can see how your gain-related settings are currently set.

Code: [Select]
[Settings]
Version=2.0
ImageExt=wav
ImageNaming=$artist$ - $album$
ImageHotKey={F10}
TracksHotKey={F4}
TracksHotVal=+{F5}
VA=Various Artists
CreateAllCuesheets=0
RunCoverDownloader=1
CoverDownloader=C:\Program Files\REACT2\coverdownloader\albumart.exe
EAC=F:\EAC\EAC.exe
Tools=C:\Program Files\REACT2\tools
MinimizeCompressionWindow=1
ProcessPriority=1
Sla_Bks_Col_Qst_Bar_Quo_Ast_Lt_Gt=-|-|-||!|'|#|[|]

[UserTrackFormats]
Flac=1
Wavpack=0
LameMP3=1
NeroAac=0
iTunesAac=0
OggEnc2=0

[UserOutputNames]
OutRoot=@mymusic@\New Rips
ImageDir_Flac=@OutRoot@\FLAC-images\$cdartist$
ImageDir_Wavpack=@OutRoot@\WV-images\$cdartist$
ImageDir_MP3=@OutRoot@\MP3-images\$cdartist$
TrackDir_Flac=@OutRoot@\FLAC\$cdartist$\$album$
TrackDir_Wavpack=@OutRoot@\WV\$cdartist$\$album$
TrackDir_MP3=@OutRoot@\MP3\$cdartist$\$album$
TrackDir_AAC=@OutRoot@\AAC\$cdartist$\$album$
TrackDir_OGG=@OutRoot@\OGG\$cdartist$\$album$
TrackName_SA=$track$  $title$
TrackName_VA=$track$  $title$ [$artist$]
TrackName_SA_acdir=$n  $~t
TrackName_VA_acdir=$n  $~t [$~a]

[UserSettings]
Debug=0
Comment=Created with EAC/REACT2, @curdate@
EmbedCover=1
ReplayGain=0
ApplyAlbumGain=0
AdjustAlbumGain_dB=0
AddCuesheetAG=0
UseWaveGainAG=0
Opt_Flac=-5 -f
Opt_Wavpack=-hmy
Opt_LameMP3=-V5 --vbr-new --noreplaygain --nohist
Opt_NeroAac=-lc -q 0.21
Opt_iTunesAac=-d -s 2000
Opt_OggEnc2=-q 3.0
Ver_Flac=1.1.3
Ver_Wavpack=4.40
Ver_LameMP3=3.97
Ver_NeroAac=1.0.0.2
Ver_OggEnc2=2.83 Lancer aoTuV b5





Thanks again...

REACT 2 Released

Reply #486
Yes.  VBR files will provide better quality for the filesize, as CBR is not efficient (you are using more bits on easily-encoded parts than necessary).

You would not (normally) manually amend RG tags - you either have them set accurately (by some application like metaflac or foobar), or not at all.

I must admit I'm out of my comfort zone with the RG settings, but from what I can see your MP3s are more quiet because you have ApplyAlbumGain set, and that is telling metamp3 to apply the gain to the file, in the same way MP3Gain does.  If you don't like the quieter files then set this to 0 instead.  I believe that your FLAC files will only have the RG tags set, so should be CD volume.  As I say though, not really my field.

Edit: hang on, I just re-read my post and your INI and it seems that you don't have ApplyAlbumGain set!  Did you amend this with your post edit, or was I seeing things?
I'm on a horse.

REACT 2 Released

Reply #487
Yeah sorry - it was part of the edit - changed the ini to test some other settings and forgot I changed gain before the save    Apologies for the confusion. Thank you again for your help, will test the MP3 volume and compare again.

 

REACT 2 Released

Reply #488
If my tests are anything to go by this should appease LAME.


Thanks a lot - they did. Everything is OK now. I'd never do it by myself.
By the way, is there any reason for the hack not being a part of the official pack?
IH

PSI initally just copied & pasted your changes, and this one obviously did not work:
Quote
Code: [Select]
@tools@\acdir.exe --overwrite --output "%TrackName%.mp3" ...

... with:

Code: [Select]
@tools@\acdir.exe --overwrite --output "%destShortPath%\%TrackName%.mp3" ...

as "..." means "whatever comes next".
So maybe you could edit that post so that it includes the full thing just to be copied & pasted? That could be helpful for people looking to solve that problem in the future.
Thanks again - I have a fully functional REACT system now.

REACT 2 Released

Reply #489
I like CBR because I know I am listening to a constant.

You listen to the music instead of the bits, which are the only constant in this case.
Actually, it's the other way round: Constant bitrate = variable quality  ---> variable bitrate = (almost)* constant quality

This is due to the fact that the complexity of your music isn't always the same. A silent strings ensemble is much easier to encode than a loud Thrash Metal-Band playing its guitar riffs, with the drummer banging into his drums like that was the last thing he'd do in his life. The latter needs a lot more bits to encode at a quality level that's comparable to the first example.

You can observe this behaviour on a highly dynamic and diversified VBR-encoded song, while playing it back with a player that displays the currently used bitrate instead of the whole file's average one. During silent parts the bitrate will drop, during more complex ones it will rise, ensuring that the quality level you specified in your encoder can be maintained throughout the whole song.

And that's the problem of CBR: While it wastes bits at the less complex areas of a song, it possibly doesn't get enough of those during the more troublesome moments, resulting in variations of the quality. Of course, it depends on your ears and the CBR bitrate whether these quality variations are audible. But in theory they're always there.

*About the (almost): 100% constancy is a theoretical case, of course. The VBR algorithm of an encoder can also have its flaws, which negatively impact the actual result.

REACT 2 Released

Reply #490
Personally I think that a single violin playing a constant note can be just as demanding as the Thrash Metal band you mention. That single note from the violin has a complexity of sound not unlike the combination of the many colours an oil painter might use to give the impression of clear blue water - though we see that water as a sparkling lake, looking closer reveals an almost chaotic pattern of millions of swirling intermingling hues. For me, MP3 allows me to see the lake, and for portable audio that is all I need. I have not yet convinced myself that FLAC is the perfect replica of a CD it is often touted as being, but my ears have not noticed the difference so far, so I rely on it for quality.

I suppose CBR means I know exactly what quality of sound I will achieve - I like knowing what I can audiably expect from a 192 vs 320kbps file. Perhaps it is just that I am more familiar with CBR than VBR...

REACT 2 Released

Reply #491
Personally I think that a single violin playing a constant note can be just as demanding as the Thrash Metal band you mention.


What, I suppose,  is meant by complexity in this context is NOT the musical complexity, but difficulty to compress the given sound. And as such, loud rock bands are, AFAIK, more difficult to compress.
The measure of such complexity? You provide some sound sample to a number of people and check at which bitrate they won't be able to tell the mp3 from the original.

Quote
I have not yet convinced myself that FLAC is the perfect replica of a CD it is often touted as being, but my ears have not noticed the difference so far, so I rely on it for quality.


Now, be covinced - this is the very same thing. You could as well ask yourself if a zipped file has the quality of the original. After you turn it to wav, you get the very same .wav file you started with - bit per bit.

Quote
I suppose CBR means I know exactly what quality of sound I will achieve - I like knowing what I can audiably expect from a 192 vs 320kbps file. Perhaps it is just that I am more familiar with CBR than VBR...


There's really a lot to be gained from VBR; there a lot of optimisation to be achieved this way.
If you were to use mp3s ona computer it would not be that important - you could use 320kbps; hard disk space is cheap. But if you use a portable players, using a lower bitrate (and VBR will give  you a  much lower average bitrate with the same quality) has a lot of merits: you can put more mp3s on a disk, power consumption is smaller (less disk operatrions).
Have fun,
IH

REACT 2 Released

Reply #492
Personally I think that a single violin playing a constant note can be just as demanding as the Thrash Metal band you mention. That single note from the violin has a complexity of sound not unlike the combination of the many colours an oil painter might use to give the impression of clear blue water - though we see that water as a sparkling lake, looking closer reveals an almost chaotic pattern of millions of swirling intermingling hues. For me, MP3 allows me to see the lake, and for portable audio that is all I need. I have not yet convinced myself that FLAC is the perfect replica of a CD it is often touted as being, but my ears have not noticed the difference so far, so I rely on it for quality.

I suppose CBR means I know exactly what quality of sound I will achieve - I like knowing what I can audiably expect from a 192 vs 320kbps file. Perhaps it is just that I am more familiar with CBR than VBR...

Well, after reading your post above, you have a most mis-informed life regarding FLAC & MP3. It's a very good thing that you came to the HA forum to get educated. Kind of like the Earth is round, the Earth is flat type thing. It took a long time for the correct answer to win acceptance, but in the end it finally did. If you read the forum threads, you will get a good and thorough education regarding digital music. The people who post here know their stuff. Gabriel, Robert, Menno, Garf, Josh, Bryant; these guys know what they are talking about, along with working on the lossless/lossy encoders. Synthetic Soul is a knowledgeable & great resource, so take advantage of what he knows. Experiment & have fun learning. This is a pretty cool place to hang out. 
Surf's Up!
"Columnated Ruins Domino"

REACT 2 Released

Reply #493
By the way, is there any reason for the hack not being a part of the official pack?
I've only heard of one other person experiencing this issue.  I think I did mention at that time though that perhaps REACT could replace file paths with the short name version by default.

PSI initally just copied & pasted your changes, and this one obviously did not work:
Quote

Code: [Select]
@tools@\acdir.exe --overwrite --output "%TrackName%.mp3" ...

... with:

Code: [Select]
@tools@\acdir.exe --overwrite --output "%destShortPath%\%TrackName%.mp3" ...

as "..." means "whatever comes next".
So maybe you could edit that post so that it includes the full thing just to be copied & pasted? That could be helpful for people looking to solve that problem in the future.
I always wonder when I use that technique whether it may throw some people.  OK, I'll edit the original post.

Thanks again - I have a fully functional REACT system now.
You're welcome.  Good luck with the ripping.
I'm on a horse.

REACT 2 Released

Reply #494
I've done a reinstall of eac and react etc and i can now embed album art into mp3 and copy the album art into both mp3 and wavpack album folders, which is a result.
However I'm still unable to embed album art into my wavpack tracks. has anyone actually manged this?

I've taken a look at the react image cfg and can't figure out what part of the script embeds art into the wavpack tracks.

react.ini has EmbedCover=1

So is it possible for react to embed art into wavpack?

REACT 2 Released

Reply #495
Quote
Edit: I have tested, and it seems that you can utilise the GetShortPath tip.
...
If my tests are anything to go by this should appease LAME.


This appeases lame - but not the OS!
The system itself has a lot of trouble communicating with those files. You can't change their filenames, you can't copy them directly (but you can copy the directory...)
It's an incredibly serious bug in Windows - not the first nor the only in the filenames category (codepage problems...)
So, contrary to what I suggested, the 'MS - DOS' should not be integrated to the to the main product, nor - in fact - should it be suggested to users without warning.. It's not the solution's fault, but microsoft's bug, of course.
I suggest that the information about the problem be included in the REACT: Using Short Filenames wiki entry.

REACT 2 Released

Reply #496
So is it possible for react to embed art into wavpack?
MP3Tag will do it, but nothing used in REACT will.  It's a new development.  See here.

This appeases lame - but not the OS!
The system itself has a lot of trouble communicating with those files. You can't change their filenames, you can't copy them directly (but you can copy the directory...)
It's an incredibly serious bug in Windows - not the first nor the only in the filenames category (codepage problems...)
So, contrary to what I suggested, the 'MS - DOS' should not be integrated to the to the main product, nor - in fact - should it be suggested to users without warning.. It's not the solution's fault, but microsoft's bug, of course.
I suggest that the information about the problem be included in the REACT: Using Short Filenames wiki entry.
Hmmm.... very true.  Guess the best idea is to go with shorter paths.
I'm on a horse.

REACT 2 Released

Reply #497
Thanks for the clarification Synthetic Soul, i'm currently using audioshell to embed art into wavpacks but was under the impression react could do it, oh well, looks like react is now doing everything it should so i'm happy.

look forward to these tools developing further, and when foobar can read embed art in my wavpacks

EDIT lazy edit :0

REACT 2 Released

Reply #498
Thanks for the clarification Synthetic Soul, i'm currently using audioshell to embed art into wavpacks but was under the impression react could do it, oh well, looks like react is now doing everything it should so i'm happy.
I see from that thread that MP3Tag uses the same format as AudioShell, so it seems that you are in good hands (if they had differed I may have warned you against it).

I'm sure a command line tagger will get th functionality soon, and then it can be used in REACT.  I doubt I'm up to adding the functionality to Case's Tag, although it would be nice if someone could.
I'm on a horse.

REACT 2 Released

Reply #499
Well, after reading your post above, you have a most mis-informed life regarding FLAC & MP3. It's a very good thing that you came to the HA forum to get educated. Kind of like the Earth is round, the Earth is flat type thing. It took a long time for the correct answer to win acceptance, but in the end it finally did. If you read the forum threads, you will get a good and thorough education regarding digital music. The people who post here know their stuff. Gabriel, Robert, Menno, Garf, Josh, Bryant; these guys know what they are talking about, along with working on the lossless/lossy encoders. Synthetic Soul is a knowledgeable & great resource, so take advantage of what he knows. Experiment & have fun learning. This is a pretty cool place to hang out. 


LOL!!!

Just because a bunch of people write a bunch of info on a topic, doesn't make me believe it more... I can see alot of people in this forum know a great deal more than I do about audio formats - which is why I am here. That said - I like to know for myself rather than blindly accept. I would consider that I am quite well informed on MP3 and FLAC, VBR and CBR, contrary to your beliefs, which is why I understand both sides of the argument, and have heard all of what has been said in this thread regarding these formats before.

I am not suggesting that anyone here is wrong (if anyone is I am sure it will be me  ), just that I have not had the time to prove it all to myself at this stage.

Many people out there still believe the earth is round... nice and big and sperical, rather than the squashed sphere it truly is... Perhaps it won't be long until we learn it is dented in at the poles like a donut - best to keep an open mind just in case...   

Thanks to everyone for putting up with the nonsensical rants of a noob, and your help. Think I am seriously off topic here now - my apologies.