Skip to main content

Topic: Any reasons NOT to use FLAC? (Read 11056 times) previous topic - next topic

0 Members and 1 Guest are viewing this topic.
  • greynol
  • [*][*][*][*][*]
  • Global Moderator
Any reasons NOT to use FLAC?
Reply #25
I guess it's possible you could do that via some other method?

I guess that's the main reason why I'm still in the Apple ecosystem, using iTunes to manage my iPod and lossy library.  Embedding art is something I deal with manually and only as needed when the iTunes store can't do it for me.
Your eyes cannot hear.

  • garym
  • [*][*][*][*][*]
Any reasons NOT to use FLAC?
Reply #26
re: embedding artwork. One of the things I like about dbpoweramp, is that I can batch convert my FLAC files to mp3 (or other lossy) and retain all metadata AND artwork. And I can have it automatically take my cover.jpg or folder.jpg artwork files in each album folder (which might be as large as 1000x1000) and automatically resize these to something like 300x300 before embedding the art in the mp3 files.

  • DonP
  • [*][*][*][*][*]
  • Members (Donating)
Any reasons NOT to use FLAC?
Reply #27
2. If you're doing batch conversion you'd be far better using something like foobar as it'll do all this for you  It won't copy album art unfortunately (or at least the folder.jpd) which is what pushed me to dbPoweramp. I guess it's possible you could do that via some other method?


Foobar also loses embedded cover art.

  • greynol
  • [*][*][*][*][*]
  • Global Moderator
Any reasons NOT to use FLAC?
Reply #28
The post you quoted already says that.
Your eyes cannot hear.

Any reasons NOT to use FLAC?
Reply #29
Don't forget, TAS says FLAC is bad 

  • Porcus
  • [*][*][*][*][*]
Any reasons NOT to use FLAC?
Reply #30
But, I don't want to compress it so much that some players have trouble playing it.  Is it possible to compress a FLAC so tightly that a system has trouble streaming it?


FLAC needs approximately the same resources to decode a -8 stream as a -5.  So if you use the official encoder, and stay away from the --lax switch, you should be fine. (Except some devices have been reported not to conform, although off the top of my head I don't remember which, and a brief web search does not indicate it is any Blueberry.)

  • BFG
  • [*][*][*]
Any reasons NOT to use FLAC?
Reply #31
FLAC needs approximately the same resources to decode a -8 stream as a -5.  So if you use the official encoder, and stay away from the --lax switch, you should be fine. (Except some devices have been reported not to conform, although off the top of my head I don't remember which, and a brief web search does not indicate it is any Blueberry.)

Yep, I've had absolutely no problems - other than some brief static/jitters at the start of playthrough--on my Blackberry so far with -8 compression.  (I even added -p on top of it, and am considering adding -r 7 or -r 8.)  Decode time has been < 2 seconds per song.  I can definitely live with that.

P.S. I'm not sure what a Blueberry is but I want one

  • Oby
  • [*]
Any reasons NOT to use FLAC?
Reply #32
(1) Is there a list somewhere of all the tag options (TOTALTRACKS, etc.) that FLAC supports?  I haven't had any luck finding one.


http://wiki.xiph.org/VorbisComment#Recommended_field_names


Document which helped me the most to make good decisions for tagging
is not available anymore, but some good soul made it available online again:
Ogg Vorbis (and FLAC) Comment Field Recommendations
  • Last Edit: 19 November, 2012, 11:00:52 AM by Oby

  • BFG
  • [*][*][*]
Any reasons NOT to use FLAC?
Reply #33
Thanks for the tips; those links proved to be extremely useful.  They also helped me find a couple of errors in EAC's default FLAC commandline

  • greynol
  • [*][*][*][*][*]
  • Global Moderator
Any reasons NOT to use FLAC?
Reply #34
Which errors are those?
Your eyes cannot hear.

  • BFG
  • [*][*][*]
Any reasons NOT to use FLAC?
Reply #35
Which errors are those?

Disregard.  I was unable to reproduce the error just now.

Originally, the problems were
1.  The %albuminterpret% tag was being used for both the BAND and the ALBUMARTIST tags
2.  %composer% was being used instead of %albumcomposer% for the COMPOSER tag
3.  The syntax for the album picture tag (%hascover% section) was incorrect, and resulted in an error code from FLAC

However, since I can't reproduce them now, it's obviously due to something other than EAC.  Maybe I made the mistakes myself or copied a suggestion from somewhere in the HA forums.