English > Scripts and Templates
Export template for J River Media Center
raldo:
--- Quote from: nostra on March 26, 2009, 08:17:32 pm ---You want to get only one (first?) file for arecord or what?
If so then define the template link like this:
--- Code: ---{%value=27 template="pages\files.ptm" maxvalues="1"}
--- End code ---
--- End quote ---
maxvalues="1" results in the number two filename (alphabetically) being exported. I think the solution above is good enough for now...
Nostra, are you the owner of PVD? If yes, would you be interested in cooperating towards making a JRMC plugin where PVD serves JRMC's needs for meta data? JRMC has a pretty comprehensive API, look here: http://wiki.jrmediacenter.com/index.php/Media_Center_Automation.
On your side, I'd guess you'd have to develop another plugin type, a database Server of some sort. I work as a programmer, and I'd be interested in trying something like this.
rick.ca:
--- Quote ---Yeah, I guess I can live with some extra semicolons.. Since the MPL file can be reimported, I guess I can do it all over again if those semicolons start bothering me!
--- End quote ---
You could just use two templates—one for list fields, one for other. Now that you got the export/import down to one automated step, surely it would be twice as gratifying to run two of them! ;)
--- Quote ---I'm pretty sure they'll come around with a proper list of meta data for movies. As far as I understand, they're also working on theater view meta display view for movies.
--- End quote ---
Yes, they've made it clear they will come up with something for Theater View. But when it comes to making changes to handle different types of data (e.g., ordered lists of [name] - [role]/[function] for credits) and they ask for a list of fields needed for movies, I have to wonder if they really understand the unique requirements for movies. MC already allows custom fields, so we don't really need them to add any "standard" fields for movies. What we need are a few new field types that do not currently exist.
--- Quote ---It'd be interesting to know how the various online databases overlap and differ wrt. meta data. Has anyone done a survey?! The intersection between these services + some of the "Good differences" I guess should be the standard for what they end up with...
--- End quote ---
Actually, my primary concern is many MC users, and the developers, may think this is what needs to happen. My experience here tells me that approach will only satisfy those who don't really care much about the information, as long as it "appears" automatically. I wouldn't bother arguing that is "wrong," as a majority of MC users may be quite happy with that. But my interest is in collecting and maintaining my own personal set of information about movies. It comes from several sources, and I'm sure it's substantially different than what anyone else is collecting. And it's the only information I'm interested in seeing in MC. My hope is more MC users will come to appreciate using something like PVD—even if just as a tool for collecting the meta data—is a better solution than any one-size-fits-all approach. Then, maybe they'll find a way to accommodate both approaches.
rick.ca:
--- Quote ---I work as a programmer, and I'd be interested in trying something like this.
--- End quote ---
I'm having trouble keeping up with you... I should think anyone willing to augment our overworked Development Division is most welcome. ;)
Excuse me if I'm clueless about such things, but wouldn't your MC plugin just access the Firebird database directly? Why would you need a plugin on the PVD side? To enable the update of PVD from MC, I suppose. Would it be possible to defer this aspect if nostra is to busy to do anything immediately on this end? Could it still be a two-way update—as long as PVD is not running at the same time? And I don't know if there are any meaningful parallels, but have you looked at Kroozbox - PVD to media theatre solution?
I imagine this would be something that would necessarily determine all the fields used in a particular PVD database, and facilitate the mapping of any or all those fields to fields in a particular MC database. Right?
raldo:
--- Quote from: rick.ca on March 27, 2009, 12:22:27 am ---types of data (e.g., ordered lists of [name] - [role]/[function] for credits) and they ask for a list of fields needed for movies, I have to
--- End quote ---
Do you mean the annoying reordering of lists into alphabetical order? I agree that there should be another ordered list type.
I don't understand the syntax "[name] - [role]/[function]". Is this a new field type?
--- Quote from: rick.ca on March 27, 2009, 12:22:27 am ---Then, maybe they'll find a way to accommodate both approaches.
--- End quote ---
Yes, I agree with you on this.
Do you want to start a new thread on this in the MC forums? The timing is correct now...
raldo:
--- Quote from: rick.ca on March 27, 2009, 12:50:34 am ---Excuse me if I'm clueless about such things, but wouldn't your MC plugin just access the Firebird database directly? Why would you need a plugin on the PVD side? To enable the update of PVD from MC, I suppose.
--- End quote ---
Yup, that may be a way to access the data. The reason why I think something must be done on the PVD side is, as you suggest, that MC needs to be able to tell PVD that action must be taken, I.e. update the database.
I was just suggesting a generic approach ("New Plugin Type") but a simpler solution may work as well.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version