English > Scripts and Templates
Export plugins for J River Media Center
raldo:
--- Quote from: rick.ca on April 09, 2009, 01:48:30 am ---Version 1.1 has to be at least a year away, so I hope you don't plan on waiting. I realize you probably want to do it your way, regardless of my opinion. But might the "simpler approach" be something like what I suggest, and still be something you can build on later? If so, you might consider a successful "phase 1" plugin might generate enough interest to make things happen faster.
--- End quote ---
I'm working on something these days, maybe you'll see something within a few weeks :)
raldo:
--- Quote from: patch on April 09, 2009, 12:41:19 pm ---To use PVD as a silent web retrevial engine would just give your sister & husband the impression it doesn't work.
--- End quote ---
As I said earlier in this thread, PVD should ideally feed info/disambiguation back to MC.
I've also noted that PVD has certain rules for "cleaning up" filenames. Once you learn those rules, the results become a lot better (Example: use "(1of2)" instead of "part 1" in the filename)
darichman:
--- Quote from: raldo on April 10, 2009, 11:34:01 am ---I'm working on something these days, maybe you'll see something within a few weeks :)
--- End quote ---
I've not been too active here lately, but I'll watch this thread with interest. A quick and easy way to pull PVD database info into MC would be a useful tool!
I'm sure you're aware that you can use PVD's export feature to generate an MPL file which can then be imported into MC. That's the way I've been doing it for a while - works great but requires the manual step of exporting from PVD and importing into MC. If what you propose doesn't work out perhaps you might find a way to automate this process somehow as a solution.
It might also be worth considering sending fields to PVD and not filenames. If you have accurate fields in MC this bypasses the need for cleaning up filenames. I export [Name] and [Filename] from MC to [Title] and [Path] in PVD.
Like Rick, it seems to me that MC's approach to video metadata is certainly less than inclusive (although recent trends indicate this may change at some point)... for me, at least at the moment, maintaining a PVD database as well as a MC database seems the best option. The closer we can get the integration the better, however ;)
The way PVD refers to fields has changed since this post, but it shows how you can go about creating an mpl from PVD: http://yabb.jriver.com/interact/index.php?topic=47538.msg326313#msg326313
If the resultant MPL were in a folder that MC could pick up in auto-import? I know it's not exactly what you had in mind, but we'd be halfway there at least...
Until Nostra swoops in and saves the day, of course ;)
raldo:
--- Quote from: darichman on April 10, 2009, 01:38:38 pm ---Like Rick, it seems to me that MC's approach to video metadata is certainly less than inclusive (although recent trends indicate this may change at some point)...
--- End quote ---
I gather you're talking about displaying video metadata? Yes, it's completely incomprehensible.
I wonder why they haven't released the theater view SDK yet. That would have speeded up things a little..
--- Quote ---The way PVD refers to fields has changed since this post, but it shows how you can go about creating an mpl from PVD: http://yabb.jriver.com/interact/index.php?topic=47538.msg326313#msg326313
If the resultant MPL were in a folder that MC could pick up in auto-import? I know it's not exactly what you had in mind, but we'd be halfway there at least...
--- End quote ---
Check out this thread too (in the PVD forum): http://www.videodb.info/forum_en/index.php?topic=1238.0
In there, I outline a way of making MC import the exported playlist "automatically" and immediately. It's not a "good" method, but it works.
darichman:
Thanks! I haven't seen that thread - will check it out.
Navigation
[0] Message Index
[*] Previous page
Go to full version