Single MP3+CUE vs. multiple MP3s

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Ian Whalley

    Single MP3+CUE vs. multiple MP3s

    My MP3 server gets used for two things -- first, to
    stream to SLIMP3s (duh!); second, to get copied onto
    iPods for mobile use.

    iPods don't do .CUE files, but the SLIMP3 does (and
    does them jolly well, nice work). So for some albums,
    it would be ideal for me to be able to store both the
    single-huge-mp3-with-matching-cue, _and_ the
    one-mp3-per-track versions. This has a rather
    unfortunate doubling effect when the SLIMP3 sees both
    versions.

    Obviously, one solution is to store the
    one-mp3-per-track versions outside the directory that
    the SLIMP3 thinks of as the music root. This would
    work great, but I don't really want to do it (the
    collection lives, carefully sorted, on a RAID5 volume
    set).

    What I'd really like is to do this:

    pink floyd - the wall / the_wall.mp3
    the_wall.cue
    separate / 1.01 - in the flesh.mp3
    1.02 - the thin ice .mp3
    [ ... ]
    2.13 - outside the wall.mp3

    And then be able to tell the SLIMP3 server to ignore
    everything underneath all directories called 'separate'
    in the collection (presumably one would do this by
    regexp).

    Is there some way to do this with the current server
    software? Or some other way to have the server
    'prefer' CUEed versions of an album over unCUEed
    versions of the same album?

    Cheers;

    inw

    --
    Ian Whalley <first name> @ <last name> . org
  • Ian Whalley

    #2
    Re: Single MP3+CUE vs. multiple MP3s

    [Sean:]
    >>Is there some way to do this with the current server
    >>software? Or some other way to have the server
    >>'prefer' CUEed versions of an album over unCUEed
    >>versions of the same album?

    >One idea OTOH would be to add an id3 tag which
    >indicates that the individual files should be ignored.


    Indeed. I don't feel qualified to invent new tags, but
    that'd be nice too. Yet a third option is to have the
    server ignore single-MP3 versions of tracks in the same
    directory as CUEed files containing those same tracks
    (just match the artist, track name, and track number).

    I'm sure there are other approaches as well.

    inw

    --
    Ian Whalley <first name> @ <last name> . org

    Comment

    • Ian Whalley

      #3
      Re: Single MP3+CUE vs. multiple MP3s

      >>And then be able to tell the SLIMP3 server to ignore
      >>everything underneath all directories called 'separate'
      >>in the collection (presumably one would do this by
      >>regexp).
      >>Is there some way to do this with the current server
      >>software? Or some other way to have the server
      >>'prefer' CUEed versions of an album over unCUEed
      >>versions of the same album?

      >I work around this by not putting any tags at all in the
      >album mp3. Then it doesn't show up when browsing, as long
      >as you are browsing by tags and not directory.


      I think this is a different problem -- I was talking about
      having both the single huge "album mp3" (with CUE file next
      to it) for the SLIMP3 to use _and_ separate per-track MP3s
      for iPods to use.

      I agree that when using a CUE file, you should not tag the
      MP3 that the CUE file indexes -- things work better that
      way.

      inw

      --
      Ian Whalley <first name> @ <last name> . org

      Comment

      Working...