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: 0.9 compatible 3rd party components (Read 52966 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

0.9 compatible 3rd party components

Reply #25 –
Extremly useful thread !

any clue for a compatible release of foo_winamp_spam ?
Thanks !

0.9 compatible 3rd party components

Reply #26 –
Quote
Extremly useful thread !

any clue for a compatible release of foo_winamp_spam ?
Thanks !
[a href="index.php?act=findpost&pid=317822"][{POST_SNAPBACK}][/a]


Yes, for the nth time. Almost all third party plugins will only be updated once the SDK is public. Which is when 0.9 goes final. Which is NOT YET. When will it be final? When it's ready.

So maybe than foo_winamp_spam will be updated then as well,....

Hopefully it won't though. 

0.9 compatible 3rd party components

Reply #27 –
Quote
Updated for beta 6:

foo_dbsearch
[{POST_SNAPBACK}][/a]

Hi foosion,

first, let me thank you for this convenient component.

I have two requests:

Do you think you could implement "send to current playlist and play" and "add to current playlist" commands? This would allow to find and play related tracks a little faster. Being able to double click on a track in the results to play it would be really useful.

I'm sometimes using multiple artist fields on a track, and thus %artist% would return "Artist1, Artist2". How would I manage to search for tracks with either Artist=Artist1, Artist=Artist2 or both using the "Search for same" context menu? I've experimented with the different modes, but none of them seems to do exactly what I want. "Find any word" is close to it, but also displays artists which only share the same first or last name with one of the artists in the tag. Looks like I'm asking for a more sophisticated method, one that compares all existing fields with the same name with each other.

One other minor isse: "Reset page" doesn't have any effect on the format presets.

I've also added a note about your component to one of my foobar2000 articles: [a href="http://www.audiohq.de/index.php?showtopic=1214]Dateibehandlung, Media Library, Playlists[/url] (German)

0.9 compatible 3rd party components

Reply #28 –
Update:
- channel mixer
- fixed one broken link

0.9 compatible 3rd party components

Reply #29 –
Channel mixer isn't 0.9 compatible yet.

0.9 compatible 3rd party components

Reply #30 –
I fund this post But it is apparently just coincidence of same version numbers.

0.9 compatible 3rd party components

Reply #31 –
Just because the component version was bumped to 0.9 doesn't mean that it works with foobar2000 0.9 imho. Did you try this release with foobar2000 0.9? I did (because I got confused about you addding it to the list) and it doesn't work (at least here).

0.9 compatible 3rd party components

Reply #32 –
Yep it doesn't  here too. I was too fast  . I missunderstood that post.

0.9 compatible 3rd party components

Reply #33 –
I think that list needs a refresh, as beta 7+ broke all .9 components.
</signature>

0.9 compatible 3rd party components

Reply #34 –
That's why there is reminder in the first post. But eventually components will be updated on their pages.

0.9 compatible 3rd party components

Reply #35 –
Updated for beta 9:

foo_dbsearch
foo_lnk
foo_playlist_manager
foo_random
foo_shn
foo_tradersfriend
foo_utils
foo_vis_vu_meter

Get all of the above in a handy package.

foo_freedb has been recompiled as well.

The "Search for same" command in foo_dbsearch now uses dynamic info (only when using one the presets directly, "Search for same/More..." still only uses static info). The problem that occurred when opening the search window while foobar2000 was minimized (you had to use the global hotkey twice) should be solved.

There have been a couple of tagging related fixes in foo_shn.

You can now assign a custom title to a randomized entry in foo_random.

Finally, there have been minor changes in foo_tradersfriend.

0.9 compatible 3rd party components

Reply #36 –
When will PSF and SPC support be added to a version of foobar 0.9 again?

0.9 compatible 3rd party components

Reply #37 –
Quote
[...] Almost all third party plugins will only be updated once the SDK is public. Which is when 0.9 goes final. Which is NOT YET. When will it be final? When it's ready.

0.9 compatible 3rd party components

Reply #38 –
Updated:
- foosionpack content (foo_random was missing)
- link to foosion's post (b9 changelog)

0.9 compatible 3rd party components

Reply #39 –
Quote
You can now assign a custom title to a randomized entry in foo_random.
[a href="index.php?act=findpost&pid=329258"][{POST_SNAPBACK}][/a]

Thank you foosion, you're so awesome.

0.9 compatible 3rd party components

Reply #40 –
How are these plugins getting updated w/o the SDK?
hi

0.9 compatible 3rd party components

Reply #41 –
Quote
How are these plugins getting updated w/o the SDK?
[a href="index.php?act=findpost&pid=331542"][{POST_SNAPBACK}][/a]


they cheat.

0.9 compatible 3rd party components

Reply #42 –
No really...
hi

0.9 compatible 3rd party components

Reply #43 –
Quote
How are these plugins getting updated w/o the SDK?
[a href="index.php?act=findpost&pid=331542"][{POST_SNAPBACK}][/a]

Foosion is a foobar2000 developer afaik, kode54 has alway been in close contact with the main developer (and seems to have his trust) and columns ui perhaps simply earned enough respect to get some special treatment. Just some speculation from my side.

0.9 compatible 3rd party components

Reply #44 –
They should release the SDK to the audioscrobbler team...I've been going ages with zero updates
hi

0.9 compatible 3rd party components

Reply #45 –
The whole point of not releasing the sdk to the general public yet is to prevent bug reports for shoddy plugins from diluting the reports of actual player-related issues. (This has been mentioned several times already)

An early port of plugins like the audioscrobbler one which doesn't exactly have a track record of being particularly stable is the exact opposite of what we want to achieve by not letting the SDK out too early.
A riddle is a short sword attached to the next 2000 years.

0.9 compatible 3rd party components

Reply #46 –
what about albumart?

0.9 compatible 3rd party components

Reply #47 –
Quote
what about albumart?
[a href="index.php?act=findpost&pid=343983"][{POST_SNAPBACK}][/a]


How about no untill the sdk is public?

0.9 compatible 3rd party components

Reply #48 –
some people just never quite get the meaning of such a simple word

-daz