BluOS 2.6.1 composer tags are incorrectly processed

Answered

Comments

16 comments

  • Official comment
    Avatar
    Tony W. - Product Support Manager

    Hi Ad

    Please update to BluOS 2.8.3 released today - this should resolve all Composer tag issues reported. You may have to rebuild your index once installed.

    Comment actions Permalink
  • Avatar
    Tony W. - Product Support Manager

    Hi Ad

    We would like to see the system log file from your index. Can you please forward it to us by selecting Send Support Request from the Help menu and follow the on screen prompts.

    We will then be in touch.

    Thanks in advance

    0
    Comment actions Permalink
  • Avatar
    Tony W. - Product Support Manager

    Hi Ad

    Me again - ignore what I said as I just spoke with our QA Team. The separation you are seeing is caused by a misplaced comma in the Composer field. We are very aware of it and already have a resolution. We will be addressing it in our next software update.

    We are very sorry about that and thank you for your patience.

    Thanks for #LivingHiFi

    0
    Comment actions Permalink
  • Avatar
    Ad Dieleman

    Hi Tony,

    Great, I'll just wait for the next update, glad I don't have to revise all my flac files.

    Thanks, Ad.

    1
    Comment actions Permalink
  • Avatar
    Ad Dieleman

    Hi Tony,

    Today I received an update for the Node 2 players but the issue with the composer tags isn't resolved yet, correct?

    Thanks, Ad.

    0
    Comment actions Permalink
  • Avatar
    Pascal Scholl

    Ich besitze einen Vault2. Das Problem besteht weiterhin. Eine Lösung ist dringend. Danke

    0
    Comment actions Permalink
  • Guten Tag Pascal (et al)

    Please excuse my English response...

    We have been investigating the solution a little further and I have found out some things from our engineering team. The comma is in fact acting like a delimiter - thus breaking up the composer field to multiple composers... So if you put a comma in the composer field it will show up as two composers...

    Example of the Bad; Beethoven, Ludwig Van shows up under both Beethoven and under Ludwig Van a phantom composer...

    -BUT-

    Example of the Good; Rodgers, Hammersmith or Rodgers, Hart would return both musical results under Rodgers...

    Our obvious intention was the second desired result as it was asked for by many but understand the confusion the first result may be causing...

    Our QA team is looking at options to find the more correct solution to this but it may take some time given this piece of information.

    0
    Comment actions Permalink
  • Avatar
    Ad Dieleman

    So why not go back to the way it was before update 2.6.x? Never had a problem then...

    0
    Comment actions Permalink
  • ...Actually we did. As I mentioned many were asking for the second result. It is also more significant than that as the new Library Structure resolves many other issues such as memory management, doubles our song limit and allows for some other items we are currently looking into.

    Don't worry though, we will get to the bottom of it and have a solution for ALL as soon as we can. 

    1
    Comment actions Permalink
  • Avatar
    Pascal Scholl

    Thanks for your quick answer. But it isn't really helpful. When I'm tagging now all my music, what will happen with your new solution: Try it again?

    I fear you forget a little, that there are also friends of classic music.

    1
    Comment actions Permalink
  • Avatar
    Ad Dieleman

    Hi Tony,

    Apparently a new BluOS version has been distributed yesterday with a different behaviour of the Composer tab: now all albums of a composer are shown under Beethoven as well as under Ludwig van in case the composer tag of the audio files is filled with Beethoven, Ludwig van

    So this behaviour is still not the same as it was a few versions ago, before BluOS 2.6. Please tell me that this will be fixed, names like Ludwig van should not appear in the list of composers.

    1
    Comment actions Permalink
  • Avatar
    Tony W. - Product Support Manager

    Hi Ad Dielman

    It will be fixed. I had a chat yesterday with our Quality Assurance manager and another with one of our Sr. Developers. They have found the problem and are testing it this morning. It will be resolved in our next set of updates.

    By resolved I mean the functionality will be restored to what it was in BluOS 2.2.x and earlier versions.

    Thanks for your patience and for bringing it to our attention.

    0
    Comment actions Permalink
  • Avatar
    Ad Dieleman

    OK, thanks, anxiously waiting for the update.

    1
    Comment actions Permalink
  • Avatar
    Ad Dieleman

    Hi Tony,

    Just updated my players and controllers and on a quick check the Composer tab seems to be working fine again. So far, so good. Thanks!

    1
    Comment actions Permalink
  • Avatar
    Pascal Scholl

    It works. Great. Thanks a lot

    1
    Comment actions Permalink
  • Avatar
    Robert Haag

    Hi Developers

    I still have this problem with BluOS 2.8.3 installed on m M12 player. It makes it impossible to find any classical piece in my collection. It was working in a previous version though. Could you please fix that or provide the previous version, where it was working? Thanks.

    Kind regards
    Rob

    0
    Comment actions Permalink

Please sign in to leave a comment.