Menu

#44 Tag dsd/wavpack problemi in 1.1.7

1.x.x
open
nobody
None
1
2019-12-05
2019-11-20
Anonymous
No

I just put the latest version of the sacd decoder (1.1.7) and the dsd tags in wavpack are back to having problems, Foobar no longer sees them as a bebeebebeeebebbebeebebeeebee but as id3v2.3, in fact there is a lot of information that I put in the tags. I hope we can fix it please.

Discussion

1 2 > >> (Page 1 of 2)
  • Anonymous

    Anonymous - 2019-11-20

    I apologize for the badly typed character "bebeebebeeebebbebeebebeeebee" I wanted to write that Foobar again sees the dsd file tags in wavpack in id3v2.3 and not in ape, but the previous version was fine. or can it be solved in another way?
    Thanks

     
  • Maxim V.Anisiutkin

    Is it multitrack WavPack? Anyway, please share such file/files.

     
  • Anonymous

    Anonymous - 2019-11-21

    No, they are not multitrack files, they are all stereo, I can also share a file but I assure you that they are all like this, the tags are seen as id3v2.3 and not as ape, even reloading the whole library are all seen as id3, with the previous version 1.1.6 instead everything ok, all seen as ape .......
    Thanks

     
  • Maxim V.Anisiutkin

    Please share.

     
  • Anonymous

    Anonymous - 2019-11-21

    This is a file in which foobar sees id3v2.3 tags instead of ape but as I have already told you all are seen as id3 ..... The version of Foobar I use is 1.5 beta 21
    Thanks for your assistance

    https://www.dropbox.com/s/t2v2mzgf9o8tbj1/12%20-%20Time%20On%20My%20Hands.wv?dl=0

     
  • Maxim V.Anisiutkin

    If you remove foo_input_sacd plugin will it show tags properly? I can't see any difference between 1.1.6 and 1.1.7.

     
  • Anonymous

    Anonymous - 2019-11-22

    Before I had 1.1.6 and it worked correctly, as I put this 1.1.7 it started again to see the dsd / wavpack tags in id3v2.3, so it's strange that they are the same ...... you tried the file that have I shared? With Foobar 1.5 beta 21 and 1.1.7 plugins are the tags seen correctly?
    Thanks

     
  • Maxim V.Anisiutkin

    With 1.1.6 and 1.1.7 I see the same tags.

     
  • Anonymous

    Anonymous - 2019-11-22

    I instead see the id3 tags, I don't know how to go about seeing the ape, I have to put back 1.1.6? I don't understand why sometimes this thing happens, usually when a new version comes out ......

     
  • Anonymous

    Anonymous - 2019-11-22

    I also installed Foobar 1.5 beta 21 at a friend's house with 1.1.7 plugin, I loaded the library from scratch and even he sees the incorrect tags, ie id3 and not ape ......

     
  • Maxim V.Anisiutkin

    Could you attach the picture of what you see?

     
  • Anonymous

    Anonymous - 2019-11-22

    I am attaching a screenshot where you can see the file I sent you in which the tag is recognized as id3 while in the previous versions of the plugin (1.1.6 and 1.1.5) instead of id3 there was ape, when it is seen by foobar as id3 there is a lot less information because the wv files I tag them and all that is in the ape tag is not seen, you only see what is in the previous dsf file with id3 tag ..... The same thing also happens to a friend of mine who has the same version of foobar and the same 1.1.7 plugin, even from him the tags are incorrect .... now I'm sharing a file that before being converted into wv was a dff (so without tag ) and in fact in that file I don't see any tag because it is displayed in id3, if foobar saw it as a bee I would see the tags, the file I am uploading, by tomorrow I see to share it .... in the meantime you can check in the technical information if from do you see the tag as id3 or ape?
    Thanks again for your patience

    https://postimg.cc/7bsjB0QY

     
  • Anonymous

    Anonymous - 2019-11-22

    This file that I share before you wv was a dff therefore without tag, the tag I put it after I transformed it into wv, now Foobar with this file does not see any tag due to the fact that it is seen as id3 while Ti I assure you that if it were seen as a bee the tags would see them, in fact if I reproduce it with DeaDBeef it's all normal with the right tags .....

    https://www.dropbox.com/s/zoqm2cysil4irsq/05%20Hey%20There.wv?dl=0

     
  • Maxim V.Anisiutkin

    What happens with tags when you remove foo_input_sacd plugin?
    Do you have any other tag hadling plugins installed?

     
  • Anonymous

    Anonymous - 2019-11-23

    As soon as I have a moment I try to remove the foo_input_sacd plugin and I'll let you know what happens ... in the meantime you checked the last wv file I shared? You see the tags? I don't see any tags on that file but actually there are if Foobar recognized it as a bee and not id3 ......

     
  • Maxim V.Anisiutkin

    I see APE tags.

     
  • Anonymous

    Anonymous - 2019-11-23

    So I did some tests and discovered several things, first of all the plugin with which I see the right tags is 1.1.5, 1.1.6 I skipped it and I went directly from 1.1.5 to 1.1.7, from several years I use an application for Android to control Foobar called Foobarconn https://play.google.com/store/apps/details?id=com.wan.foobarconpro&hl=it is on the application that with version 1.1.7 I see the wrong tags, while instead with the 1.1.5 I see them right, so by force of circumstances between 1.1.5 and 1.1.7 you changed something, now I'm using 1.1.5 and everything works fine, I also discovered a 'other thing that I have always blamed on a Foobarconn bug instead it was not, in the information of the dsd file I always saw 24bit instead of 1bit, if I remove foo_input_sacd plugin the tags work perfectly in ape and instead of seeing 24bit I see 1bit but obviously the problem is that the dsd are played in PCM and not in DSD, at the time I put the 1.1.5 plugin back and everything worked a bene so if you can please check what's different between version 1.1.5 and 1.1.7, I hope with your help to solve these problems ......
    Thank you so much

     
  • Maxim V.Anisiutkin

    Please try the one put in Interim folder. If it still doesn't show tags untick "Std Tag Editor" in SACD preferences panel.

     
  • Anonymous

    Anonymous - 2019-11-24

    Thank you very much for your help .... then, I put the plugin you put in the temporary folder and the tags are seen but in the technical information of my app Foobarcon writes on dsd64 id3v.2.3 on dsd128 does not write anything, if I replace the version 1.1.5 but all right, it also gives me the information of the codec profile and on tag type writes apev2 as it should be. It always continues to see the dsd at 24bit instead of 1bit but it's not a problem, at the time I put the version 1.1.5 because it is the one that gives the most correct information, I can keep it or there are differences in performance with 1.1.7? I am attaching three screenshots, two are referred to the last one you put in the temporary folder, the one where you see codec profile "high" and "apev2" is version 1.1.5.
    P.S: in Foobar's SACD settings on the PC I don't find "Std Tag Editor", where is it?

    https://postimg.cc/gallery/12bbwfadm/

     
  • Maxim V.Anisiutkin

    It's only in 1.1.7-1 that is put in interim folder. When unticked tag handling should work just like in 1.1.5. Don't forget to press "Reload Info" every time you change plugin versions. The main difference between 1.1.5 and 1.1.7 is in tag and album art hadling. No sound issues involved;)

     
  • Anonymous

    Anonymous - 2019-11-24

    That option from me is not there ......
    https://postimg.cc/y3cRbg98

     
  • Anonymous

    Anonymous - 2019-11-24

    However 1.1.5 and 1.1.7-1 are not the same, as you can see from me 1.1.5 from all the correct information (except 24bit on the dsd) but for the rest it's all correct, instead the 1.1.7-1 sees id3v2 .3 on dsd64 and nothing on dsd128 .....

     
  • Maxim V.Anisiutkin

    Must be not 1.1.7-1 then... And you need to do Properties->Tools->Reload info.

     
  • Anonymous

    Anonymous - 2019-11-24

    What should I do to get the STD Tag Editor option ...... I can't get them in any way those options I see in your screenshot .....

     
  • Maxim V.Anisiutkin

    First check File->Preferences->Components... foo_inpur_sacd version should be 1.1.7-1.

     
1 2 > >> (Page 1 of 2)

Anonymous
Anonymous

Add attachments
Cancel