Skip to main content

Notice

If you are using a Hotmail or Outlook email address, please change it now, as Microsoft is rejecting all email from our service outright.
Topic: foo_discogs (Read 909806 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

Re: foo_discogs

Reply #2900
Hi there,
i'm using this plugin since maybe 2016 or 2017, but never took time to come and thank the developers.
So, thanks a lot for this wonderful plugin, it helps me a lot to keep my audio library clean!
Cheers!

Re: foo_discogs

Reply #2901
Hi there,
i'm using this plugin since maybe 2016 or 2017, but never took time to come and thank the developers.
So, thanks a lot for this wonderful plugin, it helps me a lot to keep my audio library clean!
Cheers!

I agree as well!!! Amazing work. This plugin really helps me with my library.

Re: foo_discogs

Reply #2902
How do I use this plugin when playing a 2 CD album?

See attached image of the issue.

Seems it wants all the tracks listed.

Re: foo_discogs

Reply #2903
You just select and remove unwanted Discogs entries using the interface


how to fetch extraartists information?

Reply #2905
Hello,
how can I fetch those extraartists information,
like here?
and put them into the Discogs track formatting string in the Configuration's Matching tab?
Thanks!

Re: foo_discogs

Reply #2906
Is there an option to apply hidden tracknames ?
i.e.
https://www.discogs.com/Actress-88/release/15631339

The above shows as:
01 - 88  (Blurring Celt) [+ 21 Hidden Tracknames]

Whereas if I split a full album of hidden tracks, it would be awesome if there were a way to use the hidden tracks as singular ones (if wanted).

Cheers.
c.

ps. oh, actually found the option in the preferences. Nevermind. Thanks for implementing this! Never knew that was around now.

Re: foo_discogs

Reply #2907
Hello,
how can I fetch those extraartists information,
like here?
and put them into the Discogs track formatting string in the Configuration's Matching tab?
Thanks!

Those extraartists are exposed via CREDITS on the tracks. I think it should be possible to access them in the matching tab formatting string.

Re: foo_discogs

Reply #2908
I need to know if I could customize, how multiple values are formatted when writing the tags.
For example release with more labels writes them as comma separated list (Warner Records, Arnold Stiefel Entertainment), while I need to use different divisior literal, slash or semicolon, not comma. This value can be however nowhere set.

Re: foo_discogs

Reply #2909
I need to know if I could customize, how multiple values are formatted when writing the tags.
For example release with more labels writes them as comma separated list (Warner Records, Arnold Stiefel Entertainment), while I need to use different divisior literal, slash or semicolon, not comma. This value can be however nowhere set.
$join() function can change that. ", " is just the default.

Re: foo_discogs

Reply #2910
Curious if any other users of this plugin are experiencing multiple copies of artwork being downloaded when tagging. As of a few days ago every time I tag using the discogs plugin in foobar, artwork is downloaded for each individual track (IE for a 10 track release, when I tag using discogs in foobar, artwork is downloaded 10 times into the folder, each of which is assigned a "track number" corresponding the each track, but is identical). Don't believe I changed any setting or preference. Any help appreciated, with thanks..

Re: foo_discogs

Reply #2911
Curious if any other users of this plugin are experiencing multiple copies of artwork being downloaded when tagging. As of a few days ago every time I tag using the discogs plugin in foobar, artwork is downloaded for each individual track (IE for a 10 track release, when I tag using discogs in foobar, artwork is downloaded 10 times into the folder, each of which is assigned a "track number" corresponding the each track, but is identical). Don't believe I changed any setting or preference. Any help appreciated, with thanks..
What is the "File prefix" configured as? If track number is part of it, that should be removed to avoid duplicating the artwork.

Re: foo_discogs

Reply #2912
Curious if any other users of this plugin are experiencing multiple copies of artwork being downloaded when tagging. As of a few days ago every time I tag using the discogs plugin in foobar, artwork is downloaded for each individual track (IE for a 10 track release, when I tag using discogs in foobar, artwork is downloaded 10 times into the folder, each of which is assigned a "track number" corresponding the each track, but is identical). Don't believe I changed any setting or preference. Any help appreciated, with thanks..
What is the "File prefix" configured as? If track number is part of it, that should be removed to avoid duplicating the artwork.
Thanks - %_filename%_cover%IMAGE_NUMBER% and it is returning artwork for each track;

Re: foo_discogs

Reply #2913
Curious if any other users of this plugin are experiencing multiple copies of artwork being downloaded when tagging. As of a few days ago every time I tag using the discogs plugin in foobar, artwork is downloaded for each individual track (IE for a 10 track release, when I tag using discogs in foobar, artwork is downloaded 10 times into the folder, each of which is assigned a "track number" corresponding the each track, but is identical). Don't believe I changed any setting or preference. Any help appreciated, with thanks..
What is the "File prefix" configured as? If track number is part of it, that should be removed to avoid duplicating the artwork.
Thanks - %_filename%_cover%IMAGE_NUMBER% and it is returning artwork for each track

Correction - it is NOT retruning with this 'file prefix". It seems to have sorted it self - believe it did so when I re installed the plug in. Thanks and apologies.

Re: foo_discogs

Reply #2914
Thanks very much for this great plugin, been using it for years, will donate :)

Re: foo_discogs

Reply #2915
How can I get this to work in the first place?
As it seems, it needs to be authorized, confirmed and probably blessed by a priest or something but nothing of this crap works, even though everyone can look up things on discogs without even having an account.
I do have one but still there is an error message telling me the following after clicking on Authorize in the discogs plugin settings:
(FATAL) Error: Network exceptionNetwork authentication error (80090302) (url: https://api.discogs.com/oauth/request_token)

[ESCAPE to close]

Is the server down or why doesn't it work?


Re: foo_discogs

Reply #2916
{"message": "An internal server error occurred (code: c811abe5cd164e948ede85ae69b6fc4f)."}
Quis custodiet ipsos custodes?  ;~)

Re: foo_discogs

Reply #2917
But that's always the case.


Re: foo_discogs

Reply #2918
How can I get this to work in the first place?
As it seems, it needs to be authorized, confirmed and probably blessed by a priest or something but nothing of this crap works, even though everyone can look up things on discogs without even having an account.
I do have one but still there is an error message telling me the following after clicking on Authorize in the discogs plugin settings:
(FATAL) Error: Network exceptionNetwork authentication error (80090302) (url: https://api.discogs.com/oauth/request_token)

[ESCAPE to close]

Is the server down or why doesn't it work?
Do you have TLS 1.2? You could try searching this thread.

Re: foo_discogs

Reply #2919
Hello @zoomorph
when you're submitting new bits to discogs often, copy/paste errors often sneak in. So, upon first tagging, these copy paste errors are much easier to spot on the files than the discogs input UI... (extra spaces, etc)
Unfortunately, the current caching & timing between discogs & foo_discogs on recently tagged/cached releases means one might have to wait a few hours up to a day, until recent changes of a release will also show in foo_discogs.
Is there a way to force a re-cache of the latest discogs data, and if not - any chance to add a 'force re-cache' button & functionality into the 'Match Tracks' window ?
Cheers.
c.

Re: foo_discogs

Reply #2920
what is the different between 'write, ''update' and 'write & update') ?
simple as this: ;-)
- write will only write, not update. (if no tag exists, write a tag. if a tag exists, don't overwrite/update it.)
necro bump on this - I always had troubles with this for some reason.
And I tested around after installing the lartest 2.23 version, and for me - having a field set to 'write' (on a field that eg already holds a release date value of 2017, whereas it has been changed on discogs since to be unique for the digital release, i.e. 2020) - this still/again acts like I expect 'write + update' to work... i.e. 2017 is updated with 2020, despite only having 'write' set as the appropriate behaviour for %RELEASE_YEAR%.

Any double checks that 'write' & 'write + update' do behave as expected, and 'write' does NOT update an existing field, would be much appreciated, as for me, they behave the same...!?

Cheers.
c.

Re: foo_discogs

Reply #2921
Hello @zoomorph
when you're submitting new bits to discogs often, copy/paste errors often sneak in. So, upon first tagging, these copy paste errors are much easier to spot on the files than the discogs input UI... (extra spaces, etc)
Unfortunately, the current caching & timing between discogs & foo_discogs on recently tagged/cached releases means one might have to wait a few hours up to a day, until recent changes of a release will also show in foo_discogs.
Is there a way to force a re-cache of the latest discogs data, and if not - any chance to add a 'force re-cache' button & functionality into the 'Match Tracks' window ?
Cheers.
c.
Caching is on the Discogs side, so there's no way around that other than to wait. foo_discogs does caching too, which can be cleared in the settings.

Re: foo_discogs

Reply #2922
necro bump on this - I always had troubles with this for some reason.
And I tested around after installing the lartest 2.23 version, and for me - having a field set to 'write' (on a field that eg already holds a release date value of 2017, whereas it has been changed on discogs since to be unique for the digital release, i.e. 2020) - this still/again acts like I expect 'write + update' to work... i.e. 2017 is updated with 2020, despite only having 'write' set as the appropriate behaviour for %RELEASE_YEAR%.

Any double checks that 'write' & 'write + update' do behave as expected, and 'write' does NOT update an existing field, would be much appreciated, as for me, they behave the same...!?

Cheers.
c.
That does appear to be a bug.

Re: foo_discogs

Reply #2923
That does appear to be a bug.
Thanks for the info!
Out of curiousity - if you can you reproduce iton your end - are there plans to fix or leave as is ?
Just wondering, as I'll then keep checking back regularly here an on the component update - as I would love to switch a lot of fields to a reliable 'write' without update.

Cheerio.
c.

 

Re: foo_discogs

Reply #2924
Unfortunately, I have no plans to continue working on foo_discogs at this time. If I were to do so, I'd have to migrate my development environment to Linux which I now use exclusively.

 
SimplePortal 1.0.0 RC1 © 2008-2020