Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: foo_discogs (Read 1368784 times) previous topic - next topic
0 Members and 3 Guests are viewing this topic.

foo_discogs

Reply #750 –
Quote from: VyRuZ on
OK, I figure I could put this out there, too...

For releases like this, where there's 2 tracks credited for just one physical track, can foo_discogs be made to combine them? Just a '/' between the two would be great!

I've been retagging a lot of parts of my collection, and I've stumbled upon this case a few times. My solution was to remove one of the two...


I also do it like this (combine the tags for both tracks in one manually). It´s a rare case so I think it´s ok. I´m afraid it´s too much for this component to develop some kind of "artificial intelligence"

foo_discogs

Reply #751 –
Hey again bubbleguuum!

I actually use your plugin to write Remixer information to my tags.
I recently noticed that very often on discogs there are releases which have remixer information but also other roles simultaneously.
Like: "Remix, Producer [Additional] - Alex Breuer , DJane Barb-Wire Sue".
Same for vocals.
As soon there are multiple roles at once, this information is not written anymore.

Is there any way this can be enabled?

foo_discogs

Reply #752 –
v 1.22

- fixed configuration dialog embedding and context menu compatibility with foobar2000 1.0.0+.
- Discogs context menu now appears under Tagging


get it on foobar2000 component site as there is a problem withthe link on my www server right now:

http://www.foobar2000.org/components/view/foo_discogs

foo_discogs

Reply #753 –
Quote
- fixed configuration dialog embedding and context menu compatibility with foobar2000 1.0.0+.


Dumb question... but shouldn't Discogs be placed under "Tagging"? If foo2k forces new, structured menu... it would be nice if it were at least a bit logical...

foo_discogs

Reply #754 –
Quote from: lwiczek on
Quote
- fixed configuration dialog embedding and context menu compatibility with foobar2000 1.0.0+.


Dumb question... but shouldn't Discogs be placed under "Tagging"? If foo2k forces new, structured menu... it would be nice if it were at least a bit logical...



Now appears under Tagging, redownload the component (didn't changed version number)

foo_discogs

Reply #755 –
Quote
Now appears under Tagging, redownload the component (didn't changed version number)


Thanks a million!

(btw. another tiny favour to ask -- would it be possible to distribute your plugin as archive, 7z for example?)

foo_discogs

Reply #756 –
I think I found one bug and besides it I also have one question:

Question: I have seen some post in the same topic about two different labels and therefore to different catids for the same release. The plugin will write them both (both label names and both catids). Is there a change to ask which label would I like to use - catid would be added according to user's choice of label? If not; does foobar at least shows somewhere inside the software the folder that has been named with two different label names or is the only chance to see it when we ''manually'' look at the folder names outside of foobar? Example: http://www.discogs.com/%C3%82me-Rej-EP/release/528435

Possibility of a bug: Sometimes, before the plugin is used,  are position numbers (such as A1 or 01) wrong but names of the track are correct comparing to how the track sounds. After using plugin, the names and positions are the same as on discogs but, in this situation, the name of the tracks comparing to how the tracks sound will be wrong. For example:

Wrong datas: 02 - Track EX, 03 - Track TR. 01 - Track VM, 04 - Track CP. The name of the tracks (as how they are produced) are correct but positions are wrong.
Correct datas (after using the plugin): 01 - Track TR, 02 - Track EX, 03 - Track VM, 04 - Track CP. Now everything ''looks'' correctly but track ''Track VM'', now actually becomes the track with the name ''Track TR''.  Could be this a bug or not?

foo_discogs

Reply #757 –
Hello,

The Discogs component is very useful and powerful, however I found some few bugs about the artist art and album art, recently :
- The artist art and album art are no longer written (found ?)
- The "View artist art page" and "View album art page" menu options lead to erroneous page. For example it leads to http://www.discogs.com/viewimages?what=A&obid=795 for De-Phazz artist art.

I guess that these two bugs are related to bad urls and that Discogs have been updated with some new url scheme. It shouldn't be difficult to fix the component.

Best regards,

Gabriel H.

foo_discogs

Reply #758 –
Quote from: gabsoftware on
Hello,
I guess that these two bugs are related to bad urls and that Discogs have been updated with some new url scheme. It shouldn't be difficult to fix the component.



Looks like you're right, discogs changed the URL scheme. Will fix in next version.

foo_discogs

Reply #759 –
Thank you, waiting for the new version with impatience 

Moderation: Removed useless full quote of the preceding post.

foo_discogs

Reply #760 –
bubbleguuum, are there any features that you're currently hoping/planning to implement, now that the project seems a bit more active again?

foo_discogs

Reply #761 –
Hello,

I'm trying to compile foo_discogs 1.21 to adapt it to my needs, but I have a missing header file as you mentioned before, it's http_client.h who is attended to be in the SDK folder.
Could you upload this file somewhere ?

Thank you.

Regards

foo_discogs

Reply #762 –
New API, will be included in the 1.0 SDK.
Full-quoting makes you scroll past the same junk over and over.

foo_discogs

Reply #764 –
I'm keep getting crash caused by discogs under foo v1 beta 5 when using latest version of this component. I'm unable to see console but first the window pop out and says "Visual C++ Runtime error R6025"and after that pops out and says "foobar has stopped working..etc" Here's the details of the crash..

Problem signature:
  Problem Event Name:   APPCRASH
  Application Name:   foobar2000.exe
  Application Version:   1.0.0.0
  Application Timestamp:   4b2bd341
  Fault Module Name:   foo_discogs.dll
  Fault Module Version:   0.0.0.0
  Fault Module Timestamp:   4b06f642
  Exception Code:   40000015
  Exception Offset:   0003c977
  OS Version:   6.1.7600.2.0.0.256.48
  Locale ID:   1050
  Additional Information 1:   3b9a
  Additional Information 2:   3b9ae90c5136cc833c756d21b81b4c1b
  Additional Information 3:   0747
  Additional Information 4:   074722d141fe9cb4760285756930e995

Never had any problems with it 'till today..
Disregard the constabulary.

foo_discogs

Reply #765 –
It's me again with another question. Perhaps someone can help me.

Many artists are listed under multiple artist name variations on discogs but also seem to always have one primary name.
Now my question is:

Is there a way store both, the artist name variation as it is listed on the release but also the primary artist name (only if it varies from the listed name)?
I hope you can understand what I am trying to ask.

I will give you an example:
On my CD cover an artist is listed like that: "2XLC". For this certain release the artist is also listed as "2XLC" on discogs but with a * like this: "2XLC*". This indicates that the artist is usually known under another name. For this certain artist it is "Talla 2XLC".

This is how I want to store the values:

%artist% = "Talla 2XLC"
(primary artist name)

%artist_variation% = "2XLC"
(as listed on release, only stored if varies from %artist%)

Please also consider that I do not want to store ALL artist name variations all the time. I know this is possible.

Thank you.

foo_discogs

Reply #766 –
Quote from: SpaceAgeHero on
Is there a way store both, the artist name variation as it is listed on the release but also the primary artist name (only if it varies from the listed name)?
I hope you can understand what I am trying to ask.


It is not possible without modifying the plugin.
As artist name you can either store the primary artist name or the variation (ANV) but not both.
Of course you can store all ANVs but this is not what you want.

foo_discogs

Reply #768 –
This plugin needs big modifications....

Biggest problem is that it has 0 customization which is quite against the spirit of fb2k. What this plugin should do is parse a list of data, and then have a list of tags it writes based on that data even supporting operations on the data first. Then you could create your own tags naming them whatever you wanted and store any data into any tag you liked.

foo_discogs

Reply #770 –
Oooh, my mistake. I see this plugin works really nice now. Thanks a lot! Will give me something to do to tag my entire collection..... hah.


But maybe you could make it a little more user friendly?



Any of these would greatly save my eye sight!
- Option to guess track order by name rather than size (need not be too complex)
- Option to sort the list so it's much easier to see if any number is out of place

I noticed there's a lot of wrong guesses from the track length. Stuff this like should be simple to guess from file name, but a couple tracks with lengths within 10s:

foo_discogs

Reply #771 –
Quote from: blargblarg on
I noticed there's a lot of wrong guesses from the track length.


Do not select this feature then. It works just fine most of the time without. That is, if your filenames start with the track number.

Adriaan.
 

foo_discogs

Reply #772 –
Quote from: dreadroach on
I'm keep getting crash caused by discogs under foo v1 beta 5 when using latest version of this component. I'm unable to see console but first the window pop out and says "Visual C++ Runtime error R6025"and after that pops out and says "foobar has stopped working..etc" Here's the details of the crash..*snip*

I have been getting this too, but I suspect it is foobar2000, not the plugin, and only under 64bit OSs (I've had it in Vista and Win7). I suspect foobar2000 itself because in the past, I have removed the discogs component and the error then triggers to another component. No troubleshooter issues detected, btw. It continues in the latest foobar v1.0 release.

Playing normally, not even interacting, at seemingly random times, critical error sound and this (more errors if ignored):


pressing ok, this is received:

the rest of that output follows:
Code: [Select]
Problem signature:
  Problem Event Name:    APPCRASH
  Application Name:    foobar2000.exe
  Application Version:    1.0.0.0
  Application Timestamp:    4b486cb3
  Fault Module Name:    foo_discogs.dll
  Fault Module Version:    0.0.0.0
  Fault Module Timestamp:    4b06f642
  Exception Code:    40000015
  Exception Offset:    0003c977
  OS Version:    6.1.7600.2.0.0.256.1
  Locale ID:    1033
  Additional Information 1:    a399
  Additional Information 2:    a3995047d98d11ce9e011f04930db211
  Additional Information 3:    95c5
  Additional Information 4:    95c5e5524800cd0d812cc881b6ce3a5b

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt


and finally, pressing either close the program button give the  the R6025 error others have mentioned at various places on the forums:


If the error boxes are ignored, foobar2000 continues to work fine in every way and will close normally without error, saving configuration. The previous error boxes disappear as if they didn't exist.

foobar version: 1.0.0.0
Windows version: Win7 64bit Ultimate with all current updates Important or higher installed.

foo_discogs

Reply #773 –
I think it's not foobar crash or foo_discogs crash. Removing the foo_uie_lyrics2 solved the issue for me. But when it crashes it says that foo_discogs did it, i don't know why.
Using Win7 x64, too.
Disregard the constabulary.

foo_discogs

Reply #774 –
Quote from: dreadroach on
I think it's not foobar crash or foo_discogs crash. Removing the foo_uie_lyrics2 solved the issue for me. But when it crashes it says that foo_discogs did it, i don't know why.
Using Win7 x64, too.



The cause of these mysterious crashes have been found (thanks Yirkha). The component was blaming itself for crashes of other components, randomly.
Will be fixed in updated version soon.