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: old plugin, new SDK = no luck (Read 9644 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

old plugin, new SDK = no luck

Hello every1!

I've been away for a while and during that time I have received a lot of e-mails saying that my foo_cue_ex plugin stopped working with a new foobar2000 version 0.8.3. So finally I got my hands back on to Visual Studia to check what's wrong and found no apparent reason for the problem!
foo_cue_ex is based on a cue.cpp file from foo_input_std library. So I recompiled the whole thing under new SDK. No luck. The plugin loads in and shows under loaded plugins in foobar2000 preferences but does nothing (I was testing it by inserting a call to a MessageBox inside my functions). So I decided to start from scratch. I've copied the project file from one of the projects included in SDK as tutorial suggested. Then I inserted the original cue.cpp from SDK foo_input_std to the new project and added a simple call to a MessageBox at the begining of the file parser. Still no luck :/
What am I doing wrong?
B KaCKe.

old plugin, new SDK = no luck

Reply #1 –
If you add a service that handles a filetype that is already handled by another service, it will depend on the component loading order which service gets a chance to handle files of that type at runtime. So if you want your extended cue sheet parser to work reliably, use another file extension.

old plugin, new SDK = no luck

Reply #2 –
Quote
If you add a service that handles a filetype that is already handled by another service, it will depend on the component loading order which service gets a chance to handle files of that type at runtime. So if you want your extended cue sheet parser to work reliably, use another file extension.


Aaah. Ok. Thanks.
Though the next logical question would be - is there actually a way to unload certain components? 

[span style='font-size:8pt;line-height:100%']Added[/span]
Arrrgh.. It would not do, cause the original cue parser is in foo_input_std. So the question transforms to a more narrow and noobish one: Is there a way to cycle through declared service_factory'ies and disable those? And track_indexer?
B KaCKe.

old plugin, new SDK = no luck

Reply #3 –
Service factories cannot be disabled, especially not by another component DLL. Posting a component that tries to do this would be considered a violation of forum rule 15 ("Posting third party foobar2000 components").

old plugin, new SDK = no luck

Reply #4 –
Quote
Service factories cannot be disabled, especially not by another component DLL. Posting a component that tries to do this would be considered a violation of forum rule 15 ("Posting third party foobar2000 components").
[a href="index.php?act=findpost&pid=317342"][{POST_SNAPBACK}][/a]

So to sum it all:
At present there is no way of anyone supplying replacement for the original CUE parser inside a foobar2000. I mean without actually asking users to change extensions of their files.
Shame.
B KaCKe.

old plugin, new SDK = no luck

Reply #5 –
Perhaps it would be a better idea to find a better format. Matroska and MPEG-4 can probably handle that everything-in-one-file fetish which seems to be creeping around, and take care of full tagging as well.

old plugin, new SDK = no luck

Reply #6 –
WigBaM, have you any news about how your cue_ex plugin works with the later foobar 0.9 betas? (i.e. 12)
I presume it'll need an update.

For the record, I'm pretty sure that I'm using your plugin with 8.3 and it's working fine with .cue files.  the .cux thing will surely be a pain for me.

An even better solution would be for the foobar2000 developer to make the cuesheet handling aspects of foobar a little more modular so that you can add support for extended cuesheets without a 3rd party plugin.  Is this a widely required feature that would warrant it? Personally, I'd love to see it.

old plugin, new SDK = no luck

Reply #7 –
Quote
WigBaM, have you any news about how your cue_ex plugin works with the later foobar 0.9 betas? (i.e. 12)

Ahem, how shall he know that with no SDK for 0.9 being available?


How often does this need to be explained?

[span style='font-size:13pt;line-height:100%']3rd-party plugin developers cannot compile foobar 0.9 plugins until it goes out of beta[/span]

- Lyx
I am arrogant and I can afford it because I deliver.

old plugin, new SDK = no luck

Reply #8 –
Damn.  I just installed 0.9 to try out the cuesheet handling in it, and being unsatisfied with that, reverted to 0.8.3, only to encounter this problem.  Is there any way to go back to my golden Foobar of pre August 2005 days (i.e., can I download older versions of Foobar anywhere?)?  This workaround is pretty obnoxious, and I've been depending on this component pretty seriously in FLACing all my CDs.  :-(

old plugin, new SDK = no luck

Reply #9 –
I'm really dependent on this component for my lossless material as well.  Apparently WigBaM was trying to get the developers of foobar to incorporate the extended cuesheet handling into foobar natively, but he got no sign of interest.  That's really too bad

Hopefully now that the SDK is out, he'll update it for the new version.  I personally have never had to use the .cux thing, but that would be a little less than convenient, no doubt.
 

old plugin, new SDK = no luck

Reply #10 –
I spoke with WigBaM via IM several months ago in regards to foo_uie_albumart and he stated that he was no longer using FB2K, so it's unlikely he'll be releasing any updates, but I did just contact him and request the source (if he's amenable and/or responds) so that I can try and port/compile it myself.

I am in pretty much the same boat with 0.9.2, as I only have .cue and .ape and as we know, FB2K won't write any special tags, such as RATING or LAST_PLAYED to the .cue and now that the database updates its cache AFTER updating the tag (which won't happen w/ .cue), those tags are never saved.

This is probably the biggest barrier I've found to switching completely to 0.9.x--I've gotten everything else in order, minus some customization, so...  I hope he responds...

Quote from: Supacon on
I'm really dependent on this component for my lossless material as well.  Apparently WigBaM was trying to get the developers of foobar to incorporate the extended cuesheet handling into foobar natively, but he got no sign of interest.  That's really too bad

Hopefully now that the SDK is out, he'll update it for the new version.  I personally have never had to use the .cux thing, but that would be a little less than convenient, no doubt.