Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Deivit]

Perhaps it could be interesting to know at any stage which are the third plug-ins that work fine, cause problems or do not work at all with MC.12.

To my own experience and the things I've read so far, I could tell that:

Plug-ins that work fine with MC.12.030:

- Rhinobanga's Playing Now
- DXF for JRiver, Version 7.2

Plug-ins that do not work with MC.12.030:

- KingSparta Lyrics Finder V. 2.0.2
- Mr. Chriz's Evyl Lyrics V. 0.1.0.0

Plug-ins that are causing problems with MC.12.030:

- Scthom's FLAC plug-in

Feel free to make any additions/corrections when new builds are coming up, so that we can have this info updated and handy.

Thank you.

[KingSparta]

Most of my plug-ins May Not work with MC12

the file SDK file "Media Center.tlb" has changed

where it would ref MJAutomation Now It Is Ref MCAutomation

where it would ref MediaJukebox Now It Ref MediaCenter

where it would ref MJCurPlaylistAutomation Now Ref IMJCurPlaylistAutomation

There Maybe Other Changes Down The Road And Is So This Will Continue To Brake Things. I Feel At This Point It Would Be A Wast Of Time To Do Any Mods To the Programs.

What I Find Is Weird Is Why Change Some Of The Refs And Not Others, Now You have A Mix Of MC And MJ Refs In The SDK.

[KingSparta]

Where This Would Work Under The Old SDK It Errors Out When Using The New SDK

CurrentFilePath = MJFile.Get("Filename (path)", False)

I Have A Feeling This Is The Beginning Of A Overhaul

[Alex B]

For some reason the following MC11.1 plug-ins show up in MC12 even they are not installed in MC12:

Cover Art Finder 3
ReplaceMaster
MCXMLexport


EQdb is present only in MC11.1.


Clicking the Tivo Server plug-in item in the tree crashes MC12.

[KingSparta]

For some reason the following MC11.1 plug-ins show up in MC12 even they are not installed in MC12:

when looking at the registry it looks like this may change to the following location

HKEY_CURRENT_USER\Software\JRiver\Media Center 12\Plugins\Interface

[Alex B]

The MC12 path is clean.

The plug-ins are visible only in
HKEY_CURRENT_USER\Software\JRiver\Media Center 11\Plugins\Interface

[KingSparta]

The MC12 path is clean.

J Rivers Plug-ins should be there.

[Alex B]

They are.

I meant "clean" of MC11.1 plug-ins.

Probably not everything is updated to use the new locations only.

[KingSparta]

some of that was to be backward compatible, but Matt said basically at some point they will need to update or clean up.

it seems this is the time since the sdk is changing from MJ to MC.

I kind of wish they would take out the MJ And The MC in the sdk to maybe prevent name changes in the future.

Like "JRCurPlaylistAutomation" and not "IMJCurPlaylistAutomation"

or

JRAutomation And Not MCAutomation

then in the future there would be no need to change the sdk even if the product name changes or they produce other products and they also use a SDK for 3rd party plug-ins

[Deivit]

At this point, what I really hope is that more plug-ins will work OK with MC.12 in the coming builds and that the ones that work now will not cease to do it.

[Mr ChriZ]

- Mr. Chriz's Evyl Lyrics V. 0.1.0.0

Peculiar, I've been using it fine all week!
Although I've not tried installing it, it just automatically picked it up from
version 11.

I'm running version 0.2.0.0 which appears to inadvertently show itself
as 0.1.1.0 in MC plugin manager.

I've updated 0.2 to release now with version number 1.0.0.0.

Edit: I've also tried installing it again, and it still works fine.

Are you sure:
x EvilLyrics is still installed
x latest .NET Framework 2.0 is installed.

[Mr ChriZ]

C# Script also appears to work, but must be installed
in MC12 plugins directory rather than V11,
which i imagine means it won't work with
both versions at the same time.

[Deivit]

Peculiar, I've been using it fine all week!
Although I've not tried installing it, it just automatically picked it up from
version 11.

I'm running version 0.2.0.0 which appears to inadvertently show itself
as 0.1.1.0 in MC plugin manager.

I've updated 0.2 to release now with version number 1.0.0.0.

Edit: I've also tried installing it again, and it still works fine.

Are you sure:
x EvilLyrics is still installed
x latest .NET Framework 2.0 is installed.

Hi Mr. Chriz,

I assumed it did not work, since I got the message "EvylLyrics interace plug-in could not be found or created" upon starting-up MC.12. Since that message popped-up every time I started MC I decided to "hide" the plug-in from the Plug-in Manager.

Will try unistalling and reinstalling to see what happens.

Thank you.

[EDIT] Uninstalled and reinstalled the latest version from the download thread. It installed OK and the error message has disappeared. The plug-in starts OK with MC. However it does not search lyrics and the message "start your media player" could be read on the lower status bar of Evyl Lyrics. I've tried closing MC and opening it again, with the same results.

[Mr ChriZ]

May seem like a dumb question, but is the plugin definitley in enabled mode?
It's on the main interface of the plugin.
Make sure it's in enabled mode, then close both
MC and EvilLyrics and open them again.
Failing that, try reinstalling EvilLyrics...

[Deivit]

May seem like a dumb question, but is the plugin definitley in enabled mode?
It's on the main interface of the plugin.
Make sure it's in enabled mode, then close both
MC and EvilLyrics and open them again.
Failing that, try reinstalling EvilLyrics...

There are never dumb questions, Mr. Chriz 
Yes, I tried enabling and disabling the plugín, closing and starting-up MC to no avail. I've finally unistalled Evil Lyrics (the program) and reinstalled it... still the same problem. Dont' worry anyway, it must be something dumb from my end.
Tnak you.

[KingSparta]

it may depend on the file: Media Center.tlb

Since This Is The File That Is Changing And The SDK Is Based On This File

[Mr ChriZ]

it may depend on the file: Media Center.tlb

Since This Is The File That Is Changing And The SDK Is Based On This File

Quite possible, although it's peculiar it's working on my machine.
See if I can do some more testing later!

It's all a bit weird with .NET tho, cuz the .NET plugins don't
actually use the TLB file that comes with MC,
they need to use a wrapped up DLL which complicates things
slightly.

[KingSparta]

it's all a bit weird with .NET tho, cuz the .NET plugins don't
actually use the TLB file that comes with MC,

It should be in the reference files

[Doof]

Both of my plugins seem to be working fine. I didn't do anything special.

I couldn't get any of King's plugins to work (the ones I had been using anyway). I just got a message saying it wouldn't work. I assumed it was a hard coded version check that King was doing that was getting in the way.

[KingSparta]

I assumed it was a hard coded version check that King was doing that was getting in the way.

Yes it is

The latest version of Rename Master May Work

[Mr ChriZ]

It should be in the reference files

My earlier explanation was a bit vague:

What happens is .NET can't just reference MFC DLL's like that.
So they have to be wrapped up in an assembly file.
The assembly file is then referenced by each plugin using it.
This was one of the stumbling points of some of the people that tried
to do .NET plugins before me.  The assembly also has to be (or should be) strong named.
I really don't get the purpose of this, since under MFC they never were strong named.
Because the TLB files are wrapped up, they have to be shipped with the
plugins instead of just referencing the TLB file that comes with MC.

So effectivley the MC11 .NET plugins are using the MC11 TLB File
to work with MC12.  For the moment it appears to be working,
but I think it would be wise to be cautious and do a fair amount
of testing before allowing the public to try them with MC12.

So far I've tested EvilLyrics and C# Script almost daily
since moving to MC12 with no issues at all.

Eventually when things quiet down I'll put out
a new assembly file to ship with the .NET plugins
with the updated TLB file.

While I think what Kings plugins do with the version check is a good thing
In someways I wonder if the Version check should be with MC, rather than
the plugins, if it is needed?  That would be more failsafe.

[KingSparta]

While I think what Kings plugins do with the version check is a good thing
In someways I wonder if the Version check should be with MC, rather than
the plugins, if it is needed?

I am Not sure what would happen when it worked in one and not in a newer version. it could have catastrophic results if data is being changed.

[Mr ChriZ]

To Matt/JR: all in all I'm quite suprised the .NET plugins still work.
I don't know enough about the MFC side of things to truley understand what's
happening.  You've shipped a new TLB file with MC.
However is it possible that you've left the code in MC to deal with
the old TLB?

The TLB file is after all just an interface, with all the different types defined.  ?
If so then obviously no harm is going to come from using the .NET plugins
as they are.  If it just works by some weird and wonderful coincidence
it's probably more dangerous. 

On the other hand... once it's got to the compiled stage all the names go out the window...
lol I don't know 

[Matt]

We add new functions to the end of the interface.  This maintains backwards compatibility.

[Mr ChriZ]

Ah brilliant cheers