header image
 

Updates

2008/7/27

  • Fixed the LAME command line settings. The formatting got screwed when i converted the guide to a wordpress page.
  • Updated link to the latest version of LAME, which is 3.98, from 3.97.
  • Updated link to the latest verion of FLAC, which is 1.2.1, from 1.1.4.
  • Updated EAC download link to v 0.95 beta 4 from 0.95 beta 3.

2008/7/31

  • Removed color coding from the LAME V0 command line. That or the <strong> tag, or both rendered <pre> null, so it appeared to be missing a few hyphens.
  • Removed -sector-align from the level 8 compression FLAC command line. Command line now reads as -8 -A tukey(0.25) -A gauss(0.1875) -b 4096 -V -T "artist=%a" -T "title=%t" -T "album=%g" -T "date=%y" -T "tracknumber=%n" -T "genre=%m" %s

2008/8/10

2008/09/13

  • Installed the WPUNTEXTURIZE plugin as recommended by Shaid to prevent wordpress from displaying the incorrect quotation marks.

13 Responses to “Updates”

  1. Hey

    great tutorial, but I have a little problem. I have checked and re-checked all my settings but the external compressor doesn't work. It doesn't open up at all. Even when I try to run the lame encoder as a standalone application it pops up for a milisecond before instantly closing.
    I was wondering if you have any ideas what's going wrong?
    If you have some ideas can you email me back at email removed.

    Thanks for your help, Rob

    Rob said this on July 31st, 2008 at 6:42 am

  2. thanks for the tutorial,
    one qusetion left: from where can i dl the shaft in africa cd :)

    ordinary guy said this on August 15th, 2008 at 3:56 am

  3. iTunes?

    jiGGafellz said this on August 15th, 2008 at 9:25 am

  4. Why EAC v0.95 beta4 and not v0.99 prebeta4?

    Breydel said this on August 25th, 2008 at 3:19 am

  5. Why EAC v0.99 prebeta4 and not v0.95 beta4?

    jiGGafellz said this on August 28th, 2008 at 8:25 pm

  6. Hello,
    I have the same problem as Rob. I am trying to use FLAC encoder, already have tried both command line options lines. Have you found the solution with Rob?
    Thank in advance for your help.

    Sugyi said this on September 1st, 2008 at 9:48 am

  7. Yes. Rob's problem was different than yours. The LAME.exe wasn't encoding the files because the wordpress formatting I had added altered the command line. You're saying that the flac.exe is doing the same exact thing? Hmm.. I'm not sure what your problem could be. Those command lines work with the latest version of FLAC.

    jiGGafellz said this on September 1st, 2008 at 11:40 am

  8. Yes, the same exact thing. I have downloaded even the .zip file as well as the .exe file and installed flac or just extracted the .zip file and used the flac.exe in the bin directory. It does the same. To check myself, I have tried to use LAME encoder as Rob did and it worked well for me with the commands in the lame section of the guide.
    It seems to be something with those commands. I have already tried to solve them out, but no success yet. EAC leaves the .wav files in the desired directory, instead of encoding them.
    I have already tried to convert those .wav files with the FLAC Frontend.exe which was bundled in the installation and it worked fine.
    Is there a simplier command line to put in, so I can try if EAC and flac.exe are communicating well? Or do you have any other idea?
    Great appreciation for your help.

    Sugyi said this on September 1st, 2008 at 2:04 pm

  9. I've followed the instructions (thank you very much for this, jiggafellz) in this tutorial step-by-step wanting to encode to V0 using EAC and LAME and ran in the same problems like Rob and Sugyi.
    Watching the command prompt window pop and disappear without actually seeing anything didn't help so I was trying to make it stick, but no success. I opened a command prompt and entered the path to the lame.exe and looked at the help.
    Trying to start an encoding process by entering the file name like created by EAC, it became clear the problem was the spaces.
    Renamed a .wav file by using dots/underscores and then it worked. Also needed to get rid of any spaces in the path to the .wav files.
    Twas only a workaround for me to do some quick testing. But I guess if you don't use spaces when setting up EAC, the whole thing should work right from the start?

    HTH
    and keep up the good work! :)

    poppy said this on September 6th, 2008 at 6:14 pm

  10. Hey there,

    The issue people are having with the FLAC / etc compressors not running is due to how WordPress is formatting the quotation marks (") in your commandline argument examples.
    Wordpress is using the fancy versions which face different directions (“ and ”), while you need a standard one for EAC.

    So, assuming WP doesn't screw with my post, try this command line for FLAC:

    -8 -A tukey(0.25) -A gauss(0.1875) -b 4096 -V -T "artist=%a" -T "title=%t" -T "album=%g" -T "date=%y" -T "tracknumber=%n" -T "genre=%m" %s

    Cheers!

    Shaid said this on September 13th, 2008 at 3:44 am

  11. Welp, it fucked with mine too. There's a plugin for wordpress to remove that from it, a quick google for WPUNTEXTURIZE will sort it out.

    So, for those with trouble, just go and replace all the quotation marks in EAC yourself, by hand.

    Cheers

    Shaid said this on September 13th, 2008 at 3:46 am

  12. Thanks Shaid. I'll grab that plugin.

    jiGGafellz said this on September 13th, 2008 at 10:56 am

  13. still the best

    TT said this on October 19th, 2008 at 10:00 am

Leave a Reply