INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: CUE file problem  (Read 1967 times)

HiFiTubes

  • Citizen of the Universe
  • *****
  • Posts: 1123
CUE file problem
« on: January 23, 2010, 05:55:22 am »

1. FLAC .cue show up with 2 iterations of an album. All tracks are listed twice:

J:\Transients\Muddy Waters - Fathers and Sons (1969) [flac] {Speakers Corner 180g, 24-96}\A1 - All Aboard.flac
J:\Transients\Muddy Waters - Fathers and Sons (1969) [flac] {Speakers Corner 180g, 24-96}\A1 - All Aboard.flac;1

2. On some albums, all tracks are listed correctly, but in two seperate iterations as above, and in one group, each unique song plays the same track, track 1.
Logged

Alex B

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 10121
  • The Cosmic Bird
CUE file problem
« Reply #1 on: January 23, 2010, 06:30:23 am »

1. FLAC .cue show up with 2 iterations of an album. All tracks are listed twice:

J:\Transients\Muddy Waters - Fathers and Sons (1969) [flac] {Speakers Corner 180g, 24-96}\A1 - All Aboard.flac
J:\Transients\Muddy Waters - Fathers and Sons (1969) [flac] {Speakers Corner 180g, 24-96}\A1 - All Aboard.flac;1

2. On some albums, all tracks are listed correctly, but in two seperate iterations as above, and in one group, each unique song plays the same track, track 1.

How did you import them? Are the tracks listed like that immediately after the import or do the incorrect duplicates appear later? Is Library Server involved?

When I import a cue sheet I drop it into Playing Now and right-click import from there. The tracks show up only once and have correct filenames with ;n (n=track number) after the regular filename extension. I never use auto-importer for importing cue tracks.
Logged
The Cosmic Bird - a triple merger of galaxies: http://eso.org/public/news/eso0755

HiFiTubes

  • Citizen of the Universe
  • *****
  • Posts: 1123
CUE file problem
« Reply #2 on: January 23, 2010, 07:16:32 am »

LS is not involved. Is manual import of my 500+ .cue files necessary?

This has always been troublesome with MC. I prefer not to use .cue, but I have many vinyl archives in this format. Is it in the Wiki? If this is the level of .cue support offered, that's fine, I would just like to know if it is a bug or not.

If manual import is needed, that means I am supposed to manual exclude any .cue from get pulled in via auto-import. Sounds like a lot of work.

BTW - they appeared this way after 1st import as far as I know.
Logged

Alex B

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 10121
  • The Cosmic Bird
Re: CUE file problem
« Reply #3 on: January 23, 2010, 07:47:28 am »

I am not saying that "manual" import is the only way. I just explained how I do it.

Since I import only a few cue sheets at a time at most, manual importing works for me. If I need to copy cue tracks from a library to another I use MPL export/import. MPL contains all library fields. MC does not update cue files and and in any case cue sheets can contain only the very basic fields. In addition to regular library backup files I always export cue tracks to MPL so that I have the tags stored in separate physical files. I have created a library field that indicates if the track is imported from a cue sheet.

What do you have enabled in the import options? Do you have the cue albums in an isolated location so that you can set the import settings separately from regular audio tracks? Do you have several cue sheets or playlists in the file folders?

Perhaps you could find the reason for the behavior by creating a test library that monitors a separate location. Place only a few cue albums there.
Logged
The Cosmic Bird - a triple merger of galaxies: http://eso.org/public/news/eso0755

HiFiTubes

  • Citizen of the Universe
  • *****
  • Posts: 1123
Re: CUE file problem
« Reply #4 on: January 23, 2010, 08:10:07 am »

Okay, I understand your advice.

What about a new user that imports an entire library of 100K files, 25K of which are in .cue?

I won't be able to test anything in depth as we are awaiting the birth of our 2nd any day.

From the persepctive of the new user, .cue support does not exist. Pretty sure the same behavior results with .ape/cue.

My .cue files are in albums folders in artist folders on disc which means they are spread out all over the place.

Again, I'm not a fan of .cue files but it seems like they should work "out of the box".

A can see a new user uninstalling MC demo over this and going to something like MM without a second thought.

hifi
Logged

BinCZ

  • Recent member
  • *
  • Posts: 11
Re: CUE file problem
« Reply #5 on: January 23, 2010, 08:32:07 am »

Hello HiFiTubes,



the Problems with cue-sheets are well known.


Look here:

http://yabb.jriver.com/interact/index.php?topic=54763.0


Your second iteraton causing the "Always Track 1" - effect is based an a CueSheet with multiple file-entries for every single track, which MC can't handle. It can be preventet by the following trick: Rename the "*.cue" to i. e. "*.cue_".

In case of a cue for one big image file, MC will import the single tracks correctly, but the whole image is been imported as track too. That can only be solved by manually deleting it from the database and setting import option "Don't import deleted files".

No automation possible, despite computer. I did an accordingly suggestion for solving or self scripting, but got no answer up to now. Seems, things like mobile synchronization, skins and other toys for click-click-kids are much more important.


Kind regards

BinCZ
Logged

HiFiTubes

  • Citizen of the Universe
  • *****
  • Posts: 1123
Re: CUE file problem
« Reply #6 on: January 23, 2010, 11:01:22 am »

Sound simple. Could a filter be developed on the MC end?

Quote
Your second iteraton causing the "Always Track 1" - effect is based an a CueSheet with multiple file-entries for every single track, which MC can't handle. It can be preventet by the following trick: Rename the "*.cue" to i. e. "*.cue_".
Logged
Pages: [1]   Go Up