Menu

#55 First track mistagged for most DSD ISOs, starts from track 2 + first second of each track cuts off

1.x.x
open
1
2022-01-31
2020-06-21
No

I'm using the latest version of foo_input_sacd
1) as shown in the picture below, the first track is "missing", but just the tag. Track 2 is actually track 1, 3 is 2, 4 is 3 etc.

2) the first second of any DSD track is cut off. this can get really annoying when there's no recorded silence in the beginning of a track. most of the time you miss the opening chord

what's the problem? am I the only one experiencing this?

1 Attachments

Discussion

  • Anonymous

    Anonymous - 2020-06-23

    Did you just updated your SACD plugin? This could be your problem:

    05/26/19:
    Version 1.1.3 - Subsong indexing changed from 0-based to 1-based. Song infos need to be reloaded.

     
    • Borna Karanusic

      Borna Karanusic - 2020-06-30

      Not quite sure what you mean by "reloaded". As in, add the file to the playlist again?

      And no, it wasn't newly updated, I had the newest version since the beginning

       
  • Anonymous

    Anonymous - 2020-07-11

    I am using version 1.2.3 of foo_input_sacd. I have exactly the same problem i.e. track 1 is missing, track 2 is actually track 1, etc.

     
  • Anonymous

    Anonymous - 2020-07-13

    Using 1.1.9 Version, has the same problem.

     
  • Jorgo

    Jorgo - 2020-07-15

    Search the tickets, this has been answered countless times. Nobody has time to write the same stuff again and again for lazy users....

     
  • Anonymous

    Anonymous - 2020-07-16

    Exactly. I had the same problem and I corrected it by searching for the problem. I even posted the answer I found but people don't bother to read it:

    05/26/19:
    Version 1.1.3 - Subsong indexing changed from 0-based to 1-based. Song infos need to be reloaded.

    Revert to any version BEFORE 1.1.3. Even the problem is solved, it means you have to RELOAD your playlist. Don't be lazy. Google it.

     
  • Anonymous

    Anonymous - 2021-03-14

    loading a previous version loses the added benefits of 1.1.3 or later through 1.3.4 as of 3/13/2021. Pick your poison, your choices are:
    a)names out of order BUT with latest mods or
    2)roll back to an earlier release 1.1.2 or earlier and lose the added benefits of the version 1.1.3 to the current release but have the tracks in order.
    Best to read the readme.txt and decide for yourself within the Zip file

     
  • Anonymous

    Anonymous - 2021-03-14

    PS Unable to get any releases past 1.1.0 to work properly where the track order on an ISO / DSD encoded is in proper playlist order. Just tested every single one. This includes 1.1.1, 1.1.2 and 1.1.3 on version 1.64 of Foobar. Version 1.1.0 of the components within foo_input_sacd-1.1.0.zip resolved the track order issue and is the last release (best I can tell) that works with ISO files. Losing the 1.3.4 benefits however.

     
  • Anonymous

    Anonymous - 2021-03-21

    Reload your playlist. If you are not sure what that means, google it.

     
  • Anonymous

    Anonymous - 2022-01-30

    to "reload playlist", I had just to rename the main folder, waiting foobar sync it, then rename back..
    and all is in order ;)
    hey, the team ! so hard to say that !?
    btw I had this trouble switching from a previous version to the last one at this day (1.4.7).
    Don't remember the previous version, perhaps 1.3.x ?

     
    • Roman Orekhov

      Roman Orekhov - 2022-01-31

      to "reload playlist", I had just to rename the main folder, waiting foobar sync it, then rename back

      Brilliant, thank you! I wasn't able to edit tags of my ISO SACD any longer after a version update (from 1.1.4 or 1.1.8 to 1.4.7). Renaming the file didn't help for some reason. Selecting files - Properties - Reload info was saying the same as if I tried to edit a tag - file format not supported.

      @manisiutkin

      Can you please add correct reloading mechanism info to readme? Also there are a lot of tagging options already, only 1 explained in the readme

       
  • Maxim V.Anisiutkin

    See Bug #124.

     
    • Roman Orekhov

      Roman Orekhov - 2022-01-31

      Yeah, I see that you haven't put this workaround for a common problem to readme almost two years ago :))

       

Anonymous
Anonymous

Add attachments
Cancel