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 - blue334

Pages: [1] 2
Feature Suggestions / Re: Improved screenshot maker
« on: September 19, 2009, 09:35:54 am »
I recommend updating the bundled (and seemingly very old) ffmpeg.exe for proper matroska/x264 support. The successrate of the automatic screenshot maker appears to have improved from around 50% (on mkv/matroska files encoded with x264) to 100% after I replaced the bundled ffmpeg.exe with the latest available build.

Development / Re: PK's MovieDB dynamic website template
« on: September 03, 2009, 05:55:17 pm »

Try deleting [RIPPER,] and  ['{%value=Ripper custom="true"}',] in the pk_sql.ptm file.
RIPPER is a custom field in my database.

Development / Re: PK's MovieDB dynamic website template
« on: June 22, 2009, 04:20:00 pm »
That depends, if you have apache+mysql+php running on your server and know what these do, you shouldn't have too much trouble. I think my description is pretty thorough.

The files I've made available is my unedited template, it won't work perfectly out of the box since your PVD database most probably isn't structured excactly like mine. Be prepared for a little work correcting for those differences.

Development / Re: PK's MovieDB dynamic website template
« on: June 21, 2009, 05:48:19 pm »

About you first post, I'm unsure whether you think I'm the original author of the PK template - I'm not. Just this modified version and one earlier version for AMC (of course you could be referring to the latter as the one you've been using).

1) I've never had to deal with asian characters, but I have no trouble with special characters from e.g. Turkish or Icelandic. Just make sure the exported sql file is saved as unicode, and that the database is also unicode.
Or are you referring to text in the template itself, like headers?

2) I've only recently noticed this as a problem, I don't think it used to be like that. Maybe something changed at imdb lately? It is certainly annoying, and I will try to dig up the fix from the AMC thread.

3) I currently use only one custom field, "Ripper". Refers to the ripper tag of course. All the fields actually used by the template are listed in the "Fields.sql" file in one of the zip files.

About the people pages suggestion, would that be something similar to people view in pvd?
I should say that I actually suck at php coding too. I'm not alienated by it though so I can usually make minor changes or fixes. Not sure I will be able to code new functionality from scratch though.

Feature Suggestions / Improved screenshot maker
« on: June 06, 2009, 03:20:12 pm »
It would be nice if the quality of screenshots could be tweaked. The jpg-compression is currently too high for my taste, as demonstrated by the comparison below. Maybe three different quality settings, low, medium, high. I would regard the current compression level as "low".

Frame in Virtualdub vs screenshot fetched by PVD (bottom), both frames zoomed 200%.

While I'm at it, there is still room for improvement of the automatic screenshot maker. It fails to create proper screenshots for a lot of movies, not limited to the matroska files. A common error seems to be that all frames are grabbed from the first few seconds of the movie, regardless of setting to "fixed interval" or "random frames". Sometimes they are all grey, and sometimes the scanner just fails to create any (ffmpeg often crashes in those cases). The basic functionality seems to be in place however, I can easily create proper screens for problem files using the manual scanner.

Typical bad screenshot result:

Support / Re: IMDb import
« on: June 06, 2009, 12:20:41 pm »
Can't import more than 9 imdb records at at time without a "http bad request" error. Is anyone else having this problem? Is it the website blocking batch requests or is something wrong with the plugin? Using version

Development / Re: PK's MovieDB dynamic website template
« on: May 31, 2009, 09:50:16 pm »
Fixed the first post so the thread is a little more welcoming.

About suppressing items, that may be difficult though I see your point. The left side panels do have a "threshold value", but that only applies to the unfiltered selection.

Development / Re: PK's MovieDB dynamic website template
« on: May 31, 2009, 05:14:42 pm »
Since we have a release now I have some updated files. Also made some changes, like bigger posters.
Link to my site based on these files is in my sig.

Needed files: for - website -  sql

The files are just proof of concept and will have to be adapted for other databases. Ask me if you decide to try.

EDIT: Updated first post with a step-by-step description and the new files

Scripts and Templates / Re: (movies)
« on: April 04, 2009, 09:28:14 pm »
Found it I think, the error is related to web address formatting:

Example: - error - no error

But addresses without www are ok if the MPAA field is not enabled, seems the script requires www only for that particular field

Scripts and Templates / Re: (movies)
« on: April 04, 2009, 08:47:02 pm »
I can't see any pattern, and maybe it doesn't even have to do with ratings. I was guessing as much because the rating field is not updated for those entries which show this error.

Scripts and Templates / Re: (movies)
« on: April 04, 2009, 11:22:21 am »
It seems this script isn't working at the moment (yes I have the latest version).
I doesn't retrieve correct titles for any movie starting with a common word. I'm also getting a lot of division by zero errors on the ratings.

Development / Re: PK's MovieDB dynamic website template
« on: January 05, 2009, 11:47:31 pm »
you'll need an updated export template for the beta version, since there are many changes.
I have one working already for my own site, I'll try to tidy it up and upload it tomorrow.

Development / Re: PK's MovieDB dynamic website template
« on: January 05, 2009, 05:38:35 pm »
sorry for the late reply, I forgot about the thread.
The template is the correct one, for ver output. Regardless of version, I don't quite understand why the output is being truncated like that. Can you check if the [);] closing of each statement) is also missing in the sql script (the export output file), or just in the mysql error message?

Development / Re: PK's MovieDB dynamic website template
« on: January 02, 2009, 02:05:21 pm »
The sql query does not appear to close each statement properly - each line of the query should close with [);] whereas yours close with [,'] . This will cause malfunction. Maybe you could post the sql export script you're using?

Support / Re: Scan folders/file scanner confusion
« on: December 08, 2008, 11:02:49 am »
I think what you're asking can largely be acheived using the current export plugin.
What you're describing is essentially an advanced html export template.

Where you lose me is where you suggest this kind of information storage should be read by PVD directly. PVD is after all a database app, you cannot acheive anything like the current functionality outside the database engine. A browser would be better suited.

Development / Re: PK's MovieDB dynamic website template
« on: November 26, 2008, 09:33:57 am »
The template available for download (on page 2 of this thread) is up to date except for tags and allmovie rating/link. Unless these are very important to you I'd rather wait until I can make a working template for 0.9.9.X before uploading more files (the sql export template works for version only).

Development / Re: PK's MovieDB dynamic website template
« on: November 06, 2008, 11:31:29 pm »
Added allmovie rating/link to the template (also as sort option). Tags have also been added, as mentioned in an earlier post.
Will wait for an updated export plugin allowing the export of actor's role before posting new files.

Here's what my current template/page looks like:

Development / Re: PK's MovieDB dynamic website template
« on: October 29, 2008, 06:20:54 pm »
Seems you already figured out how to enable/disable the side panels in The files that contain the html code reside in the templates/default folder. 
detail_view.tpl is the main view and details.tpl is the detailed view. If you know a little html you shouldn't have any problems with these. Not sure if they will open in a wysiwyg editor though.

The colors are all defined in the stylesheet style.css with the single exception of the main background color which is defined in index.php. I think the easiest way to edit the colors is to make a screencap of the web page and open it uncompressed in photoshop or similar software. Using the eydropper tool you can identify the various colors in the stylesheet, this is easier than trying to interpret the various pointers in the stylesheet directly. Then just tweak colors as you wish using replace color in photoshop, identify the new color value and search-replace those values in the stylesheet.
There are some gif files in templates/default/images which naturally aren't tweaked using the stylesheet, you will need to edit these manually. The logo also resides here, I suspect you don't want to keep my walking egg.

Development / Re: PK's MovieDB dynamic website template
« on: October 29, 2008, 10:42:06 am »
Well if that is the case you can't use the data in the ID field (which correctly is the short field before "Title"). If there is information in this field you want to display on the web page, you must manually move it to the "Original Title" field (if that is what it is)
Apparently PVD allows characters to be typed in the ID field, but the export plugin accepts only numbers (which is why all your ID fields are assigned ID=0 in the exported file)

You should not remove anything from the export template unless you fully understand the structure. Each '{%value=XX}' has a counterpart database field, and they're sorted in the same order.
That means for example that the 9th database field ORIGINALTITLE corresponds to the 9th export variable '{%value=3}'. If you remove one but not the other your data will end up in the wrong fields.

Development / Re: PK's MovieDB dynamic website template
« on: October 28, 2008, 06:51:59 pm »
The problem is your database entries aren't numbered. The ID number (the first value) is assigned as the "primary key" in the database, which probably means it has to be unique. I wasn't even aware that PVD would allow duplicate IDs.
Fortunately the internal PVD database has an internal ID you can use as a replacement value. Make the change shown with red to the sql.ptm file before exporting, this should assign the internal ID number instead:

filter="SQL Files|*.sql"
replace="#13#10<-> "
replace="#13<-> "
replace="#10<-> "
%OPTIONS%INSERT INTO movies (NUM, CHECKED, MEDIA, MEDIATYPE, SOURCE, DATEADD, BORROWER, RATING, ORIGINALTITLE, TRANSLATEDTITLE, FORMATTEDTITLE, DIRECTOR, PRODUCER, COUNTRY, CATEGORY, YEAR, LENGTH, ACTORS, URL, DESCRIPTION, COMMENTS, VIDEOFORMAT, VIDEOBITRATE, AUDIOFORMAT, AUDIOBITRATE, RESOLUTION, FRAMERATE, LANGUAGES, SUBTITLES, FILESIZE, DISKS, VIEWDATE, PICTURENAME) VALUES ('{%value=0}', '', '{%value=47}', '', '', '{%value=17}', '', '{%value=9}', '{%value=3}', '{%value=2}', '', '{%value=53}', '{%value=56}', '{%value=45}', '{%value=44}', '{%value=5}', '{%value=19}', '{%value=52}', '{%value=8}', '{%value=15}', '{%value=16}', '{%value=23}', '{%value=24}', '{%value=43}', '{%value=25}', '{%value=21}', '{%value=22}', '{%value=48}', '{%value=49}', '{%value=26}', '{%value=29}', '{%value=33}', '{%value=63}');

I suspect the date values formatted like "21st July 1979" will end up as "0000-00-00" in the mysql database. It should be possible to fix this using regular expressions, let me know if it becomes a problem.

EDIT: forget the last part, seems the alternative date formatting I spotted is part of a descripton text and not a date field.

Pages: [1] 2