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 1359145 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

foo_discogs

Reply #350
If I don't misunderstand your problem, it seems to me you want foo_discogs to automatically select the right tracks on a release by itself. For now, this isn't available - you'll have to align the corresponding tracks manually.

foo_discogs

Reply #351
If I don't misunderstand your problem, it seems to me you want foo_discogs to automatically select the right tracks on a release by itself. For now, this isn't available - you'll have to align the corresponding tracks manually.


You have missunderstand it. I pick the track manually.

For example: You have to pick track five out of a album of 10 songs. foo_discogs (also MP3Tag) use the first song to tag. Even when you have select the fifth song. This happens to me on every song. Only when i move up the fifth song to the first position and then use it to tag, the result is what i expect.

foo_discogs

Reply #352

If I don't misunderstand your problem, it seems to me you want foo_discogs to automatically select the right tracks on a release by itself. For now, this isn't available - you'll have to align the corresponding tracks manually.


You have missunderstand it. I pick the track manually.

For example: You have to pick track five out of a album of 10 songs. foo_discogs (also MP3Tag) use the first song to tag. Even when you have select the fifth song. This happens to me on every song. Only when i move up the fifth song to the first position and then use it to tag, the result is what i expect.



I'm not sure I understand, but keep in mind that files are tagged with the corresponding aligned discogs track and you can change this order with "move up" "move down" buttons.

So if you want to tag a single track (is that your problem?), it'l be displayed alone in the right pane and you'll have to move the corresponding discogs track to the first position of the left pane.

foo_discogs

Reply #353
I can't get this to work at all. It installed fine, and I can get to where you select the release, and then go Okay, but it always just comes up with an html parse error for the release. :x

I tried searching the thread, but didn't see anyone else not able to get any releases at all.

foo_discogs

Reply #354
I can't get this to work at all. It installed fine, and I can get to where you select the release, and then go Okay, but it always just comes up with an html parse error for the release. :x

Here too 
I would guess they have changed the HTML Layout, since it was working about a week ago.
I hope the plugin's author will fix it soon!

foo_discogs

Reply #355

I can't get this to work at all. It installed fine, and I can get to where you select the release, and then go Okay, but it always just comes up with an html parse error for the release. :x

Here too 
I would guess they have changed the HTML Layout, since it was working about a week ago.
I hope the plugin's author will fix it soon!


Yep, seems they have changed the code just a few hours (max 1 day) ago.
It give "discogs error: release id:xxxxx html parse error"
No matter what disk I select.
It have been working OK since today.

foo_discogs

Reply #356
Damnit. And of course, the day that I decide to give this thing a go.

Just my luck.

foo_discogs

Reply #357

foo_discogs

Reply #358
Paging bubblegummm  Any update on the development of an API-aware version of this component?

foo_discogs

Reply #359
I'm going to release a fixed version of the plugin ASAP. I knew some day they would change the html layout, looks like it's today. Hopefully this should be trivial to fix.

I'll start working on a more future proof version using the new XML API. Now that discogs devs released the API, they'll have less reluctancy changing the html layout.

foo_discogs

Reply #360
Quote
I'm going to release a fixed version of the plugin ASAP. I knew some day they would change the html layout, looks like it's today. Hopefully this should be trivial to fix.

I'll start working on a more future proof version using the new XML API. Now that discogs devs released the API, they'll have less reluctancy changing the html layout.


ah thanks for the sugar in my coffee

foo_discogs

Reply #361
Version 1.01 fixing parsing issues posted (see first post for link)

Tested with 200 random releases and found no issue, but if you find one let me know.

v 1.01
--------

- fix html parse errors due to small discogs html changes
- fix parse errors with tracklisting containing placeholder artist such as "No Artist" or "Various" (such as releases 204297 or 336752)
- fix a crash with this release: 891416 (don't remember the cause)

foo_discogs

Reply #362
Works perfectly. Thanks

foo_discogs

Reply #363
Version 1.01 fixing parsing issues posted (see first post for link)

Tested with 200 random releases and found no issue, but if you find one let me know.

v 1.01
--------

- fix html parse errors due to small discogs html changes
- fix parse errors with tracklisting containing placeholder artist such as "No Artist" or "Various" (such as releases 204297 or 336752)
- fix a crash with this release: 891416 (don't remember the cause)


Thanks so much for this quick fix, it's much appreciated! In general things are back working, but the html parse error for 204297 is still there. Could it be another change to the layout and not the original issue?

foo_discogs

Reply #364

Version 1.01 fixing parsing issues posted (see first post for link)

Tested with 200 random releases and found no issue, but if you find one let me know.

v 1.01
--------

- fix html parse errors due to small discogs html changes
- fix parse errors with tracklisting containing placeholder artist such as "No Artist" or "Various" (such as releases 204297 or 336752)
- fix a crash with this release: 891416 (don't remember the cause)


Thanks so much for this quick fix, it's much appreciated! In general things are back working, but the html parse error for 204297 is still there. Could it be another change to the layout and not the original issue?


Still working OK for me (after the last fix).

foo_discogs

Reply #365
I'm going to release a fixed version of the plugin ASAP. I knew some day they would change the html layout, looks like it's today. Hopefully this should be trivial to fix.

I'll start working on a more future proof version using the new XML API. Now that discogs devs released the API, they'll have less reluctancy changing the html layout.

Does this mean that fields like "Remixer" and "Producer" could be parsed in the future??
Can't wait for a HD-AAC encoder :P

foo_discogs

Reply #366
Awesome. Everything's working great now! Thanks!

foo_discogs

Reply #367
I can't see albumart, is this normal?
Because it was really nice to download the albumart directly from discogs via this plugin.
Anyways, thanks a lot for the quick fix!

foo_discogs

Reply #368
Hey bubbleguuum!

Thanks very much for the prompt update!
It is one of the most useful fb2k plugins.

I'm still missing a couple of things though...

previously it was showing a release year when previewing discogs album list. Can we have this feature back by any chance?

+ would it be possible to add horizontal scrollbar to the album list to be able to see long album name endings (sometimes the album has the same name but different year or media that doesn't fit to the preview window)

++ and a very minor thing is to skip tracks marked as video... or do not add such tracks to the number of audio tracks... or just mark them differently when showing.

Thanks!

 

foo_discogs

Reply #369
v 1.02
-------

- fixes html parse error with placeholder artists for good (ex: release 204297)
- fix missing year in release list
- add horizontal scrollbar in release list to see long release names.


@Stryng: you see album arbt by configuring foo_uie_albumart. If you mean you don't see the small art preview
in the tag dialog, just activate it in the preference (it's disabled by default)

@ odyssey: yes

foo_discogs

Reply #370
Great, Thanks!!!

IT WAS QUICK!!!




v 1.02
-------

- fixes html parse error with placeholder artists for good (ex: release 204297)
- fix missing year in release list
- add horizontal scrollbar in release list to see long release names.


@Stryng: you see album arbt by configuring foo_uie_albumart. If you mean you don't see the small art preview
in the tag dialog, just activate it in the preference (it's disabled by default)

@ odyssey: yes

foo_discogs

Reply #371
v 1.02
-------

- fixes html parse error with placeholder artists for good (ex: release 204297)
- fix missing year in release list
- add horizontal scrollbar in release list to see long release names.


@Stryng: you see album arbt by configuring foo_uie_albumart. If you mean you don't see the small art preview
in the tag dialog, just activate it in the preference (it's disabled by default)

@ odyssey: yes


bubbleguuum, you rock! All sorted now. Thanks so much for this, it's very much appreciated.

foo_discogs

Reply #372
I didn't see if it was requested (there is no feature request page or anything similar) but accepting tags to store artist pictures would be terrific (cause having 10067_1 is not explicit  )

I would like to use something like
$replace($replace(%path%,%filename_ext%,),%directoryname%,) to store my albums

In fact something like you did for the album art would be OK.

BTW really great plugin !! I use it as often as I can !!

foo_discogs

Reply #373
Thanks for the quick update  very useful component, I use it all the time

foo_discogs

Reply #374
I didn't see if it was requested (there is no feature request page or anything similar) but accepting tags to store artist pictures would be terrific (cause having 10067_1 is not explicit  )

I would like to use something like
$replace($replace(%path%,%filename_ext%,),%directoryname%,) to store my albums

In fact something like you did for the album art would be OK.




I second this suggestion. It's nice not to create duplicates, which, as far as I can remember, was your reason for not doing this in the first place. However, how about naming them like this?

Code: [Select]
#$num(%ID%,n)# %artist%


As well as keeping them at a non-ducplicate state, they can more easily be retrieved.



Another thing I would like to add/re-request, is a better navigating system. Releases with many tracks/screwed up sorting, are pains in the neck to sort.