Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - darichman

Pages: 1 [2]
Scripts and Templates / Re: Theater View Skin
« on: May 12, 2009, 09:32:01 am »
Ah, but it's so near perfect as it is... ;D

Would be good to create multiple custom boxes for different types of fields... is that allowed?
I'll make like nostra and add this to my "to do" list ;)

Scripts and Templates / Re: Theater View Skin
« on: May 12, 2009, 03:30:48 am »


Scripts and Templates / Re: Some questions regarding export plugins...
« on: April 10, 2009, 02:16:17 pm »
Thanks! I haven't seen that thread - will check it out.

Scripts and Templates / Re: Some questions regarding export plugins...
« on: April 10, 2009, 01:38:38 pm »
I'm working on something these days, maybe you'll see something within a few weeks :)

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:

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 ;)

Scripts and Templates / Re: (movies)
« on: March 22, 2009, 03:18:57 am »

Oh wow, I've never seen some of those fields up there! haha

Yeah, I'd like that extra info too... I wonder how it would be best presented though - maybe in a note/memo field. I'll have a look - but my approach so far has been similar to yours... look at the existing script and trying to adapt it without breaking it. I've broken it a few dozen times now :)

Thanks, that was really helpful... I agree that it's nice to know where the data came from. Up until now, I've been using IMDb for all standard fields, with AMG fields all belonging to custom fields with a "AMG " prefix. It's hard to get the best of both worlds... custom fields don't work too well with "People" fields...

A template to decide which order fields are displayed in would work really well, for both standard and custom fields I think...

Some feedback... works great! A few little niggly bits I've noticed so far...

1. Box Office doesn't format correctly in the standard field. Works fine as a "short text" custom entry
Code: [Select]
//Box office
 AddCustomFieldValueByName('Box Office', HTMLValues(HTML,
                             '<span>Box Office</span>', '</table>',
                 '<li>', '</li>',
                 ', ', EndPos));

2. Your MPAA + Reason formatting works okay, but if there is no reason listed, you get an output of "Rated M for ." etc

3. I added support for the "Region" field in AMG. It's being used more and more frequently on the site, but many older movies don't have it populated.
Code: [Select]
 AddCustomFieldValueByName('Region', HTMLValues2(HTML,
                             '<span>Premiere</span>', '</table>',
                 '<a href="', '</a>',
                 ', ', EndPos));

4. I seem to get a rating of 10 for every movie... must have a closer look.

Also, I'm not sure if it was you or Nostra who added the Reviews and Producion Credits functionality, but that's awesome - thanks :)

Scripts and Templates / Re: (movies)
« on: March 21, 2009, 02:49:32 am »
Okay I have a few days off now, so I'm revisiting my movie metadata (yay!)

First of all, thanks for updating the allmovie script, nostra. I'll see how I go...

Rick, this is great - thanks for sharing.

Just wondering, do you mainly use allmovies for your metadata? I was trialling a system with custom fields a while ago to attempt to maintain both IMDb and AMG fields in the same database (Used standard fields for IMDb and a whole bunch of custom fields for AMG - AMG Director, AMG Synopsis etc etc). It was getting a bit unwieldy.

There are a few situations where AMG is incomplete compared to IMDb or vice versa... what's your system?

Support / Re: IMDb user comments
« on: August 17, 2008, 09:43:18 am »
I think what suggests is the ideal solution here ~ it's really hard to cater for everybody's own needs, so some configurability would be the way to go. Sounds like it'd be a bit of work though ...  ;)

Feature Suggestions / Re: Gratitude List
« on: August 09, 2008, 12:58:57 am »


Scripts and Templates / Export Template for J River Media Center
« on: July 31, 2008, 11:30:47 am »
I don't know if anyone here uses J River Media Center (, but here is an export template that will output to an MPL file. MPL is the main database format that Media Center (MC) uses. MC is great as an organisational/playback/home theatre setup, but lacks online metadata lookup for movies, so this is where PVD comes in for me :)

First of all, set up the export template in PVD-
go to tools > preferences > plugins > plain text/export > add > (call it what you want) > and then copy and pase the following:
(i pull the info from AMG, so my fields are named accordingly, but you can rename them to whatever you want)

Code: [Select]
filter="MPL Files|*.mpl"
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<MPL Version="2.0" Title="ChrisRulz">
<Field Name="Filename">{%value=27}</Field>
<Field Name="AMG Year">{%value=5}</Field>
<Field Name="AMG Genres">{%value=44}</Field>
<Field Name="Themes">{%value=46}</Field>
<Field Name="AMG Synopsis">{%value=15}</Field>
<Field Name="MPAA">{%value=6}</Field>
<Field Name="Actors">{%value=52}</Field>
<Field Name="Director">{%value=53}</Field>

You can add as many entries of: <Field Name="XXX">{%value=YY}</Field>  as you want
(just replace my ones with the names of your fields, but you MUST leave the Filename one at the top!)

XXX is the name of the field in MC (the field has to already exist in MC for this to work)
YY is the two digit number PVD uses to refer to fields:

Once you've saved the script, select the movie entries you want to export, go to tools > export > select your new template and name the mpl file.

From MC, select File > Import Playlist > Open the MPL file
The appropriate fields should now be populated in your MC database (yay!)
For this to work properly, both the PVD and MC databases need to point to the correct path and filename for your files.

Thanks to for recommending PVD to me :)

Pages: 1 [2]