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 -

Pages: 1 ... 113 114 115 116 117 [118]
Feature Suggestions / Re: Vote: Features for 0.9.9
« on: July 10, 2008, 09:35:58 am »
...I cannot find it.

Have you checked Preferences - People - Show people added from movie credits? If not, and your database includes many people who have not been updated, just select them all and update.

Feature Suggestions / Re: Vote: Features for 0.9.9
« on: July 07, 2008, 09:54:53 am »
I assumed it was a typo for Tag

Oh. I thought he had discovered a new standard for video tags.  ::)

Feature Suggestions / Re: Vote: Features for 0.9.9
« on: July 07, 2008, 01:32:35 am »
Printing     - 2 (3.2%)

I'm feeling a little sad for this feature. What, exactly, did you have in mind, considering you've already provided for the export of HTML reports (which can then be printed)?

Feature Suggestions / Re: Vote: Features for 0.9.9
« on: July 07, 2008, 01:27:08 am »
Еag export/import (like ID3 for mp3)

Never heard of this... What does EAG stand for? Any useful links for explaining what this is?

Feature Suggestions / Re: Vote: Features for 0.9.9
« on: July 04, 2008, 08:51:11 pm »
I think I'll make some kind of skins engine working with xml files where you can define positions, sizes, colors etc. for different UI controls.

Is this going to be user-friendly enough for those of us who go brain-dead in face of anything vaguely resembling code? I suppose I'm thinking of my experience with other "skinnable" software. It rarely makes any difference to me because I don't believe I have the ability or patience to create my own skin. Note I'm speaking from complete ignorance. Perhaps a skin specified as an xml file is the sort of thing I can figure out by following an example or template.

Feature Suggestions / Re: Vote: Features for 0.9.9
« on: July 04, 2008, 08:36:55 pm »
Customizable views would be very useful, for exampe I would like to have a feature to define the ciriteria movies of an actor are sorted in the people view. At the moment they are sorted by year, but how about sorting by Rating or by Alphabet?

See the Sort by and Group by items on the View menu and the list pane context (right-click) menu.

Feature Suggestions / Re: Vote: Features for 0.9.9
« on: July 03, 2008, 10:50:00 pm »
Grid view is not quite as important to me as it was, but I think it deserves to be at the top of your list.

My remaining votes went to the following three items, and I would like to express more directly what I'm hoping for. Now that I've created a database I'm very pleased with, my interest is shifting to making the best possible use of the information. For me, the ability to use the program in a home theatre environment (i.e., viewing at 3 metres, using a remote control) would offer the greatest improvement to it's utility. The addition of a typical Media Centre-like "theatre view" is far too much to ask, and is probably not exactly what I'm looking for anyway. I'm hoping the interface customization features will be implemented in a way that will allow me to create my own PVD "theatre view" that includes as much information as possible—enlarged to readable size. The result would not only allow me to select a movie for viewing (as media centre software would—based on attributes, covers, etc.), I would be able to see most of the movie information, read a review, etc.

I'm sure I'm overlooking some complications, but this capability doesn't seem to involve much more than the ability to increase the font size and maybe rearrange some of the fields to better accommodate the larger font. It would require the ability to save customized views and switch between them easily (e.g., a shortcut that toggles normal/"theatre" views). Most of the navigation issues can be dealt with in programming the remote. In other words, I can imagine a "customizable views" feature that would satisfy my specific need, as well as the more general desire to tailor the interface to one's own preferences.

More features:

A fundamental feature that sets PVD apart from others is the handling of people in a proper relational database. I think it would be wise to highlight this by offering a third panel or pop-up that shows the (complete people view) information for any person selected in movie view. This would make the people information much more "accessible" than it is now. The time lag in switching views is a significant deterrent to viewing people records on a slower machine. I suspect it's at least an annoyance at times on a fast machine—having to switch views just to see some information about a person in a movie. I suppose the same should be considered for movies in people view, but this would not interest me nearly as much.

Well, okay, it's not a new feature, but... On behalf on new users, I would like to vote for any improvements that will make import/export routines easier to use. The obvious thing that comes to mind is the ability to read headers of input files and present a field mapping dialog populated with the fields found. Many potential new users are going to have existing data they are very attached to. Even though the existing routines are effective, some are not going to even try PVD unless they see a clear and easy path for converting/importing their existing data.


Support / Re: Scan folders/file scanner confusion
« on: June 21, 2008, 07:42:08 am »
I had assumed that it was proposed a server version on PVD would need to be run...

No, no, no! I know it's confusing, but this is a three-way conversation. My recommendations are never the same as nostra's.  ;D

I understand why you would prefer not to run a server version of PVD. I was agreeing with you in recommending each user run PVD stand-alone, using their own separate database. I was merely pointing out it would not be as much work to create those separate databases as you seemed to think it would be.

The only way I can see this being achieved is if the manual selections made during the initial scan are stored with the movie file.

Again, I'm not questioning the means, I'm questioning the objective. Your scheme is only necessary in the event one needs to rebuild a database starting with nothing but the movie files. This is not necessary if you are just changing the location of files—the rescan function works with 100% accuracy (I tested it since my last post). It is not necessary if you are creating a new database that is a subset of an existing one (your vacation scenario).

I understand you want any user to be able to build a database by selecting files and letting PVD do the rest. I've already suggested your request may be easy to implement. Please don't think I'm arguing this because I don't think you should have the feature you want. Nostra is perfectly capable of weighing the pros and cons and the amount of effort required. I'm countering your implication there is something fundamentally wrong with PVD when it's actually performing extremely well—according to its intended purpose. If any further effort is required in this area, I have to wonder if it should not be directed to making the initial scan more accurate. Everyone would benefit from that.

Support / Re: Scan folders/file scanner confusion
« on: June 20, 2008, 02:14:35 pm »
I do not think movie file tagging is widely used or standardised yet...

That seems to be the case. I just spent hours trying to get image tag information into MC—it seems hopeless. I recall abcAVI Tag Editor saves IMDb information in AVI's, but I suspect the tags are the author's creation, and he's just writing them as a block into the file. So maybe the answer is it's easy to write information into AVI's, it won't affect other software that needs to read them, but there's little chance the information could be shared in any way.

Master databases worry me...

I was assuming this would be a one-time thing—just for getting started. I meant "master" only in the sense it would include all movies on the server, and users would start their own database using a copy of it.

I suppose your vacation scenario might be an example of where this functionality is required on an ongoing basis. But I wonder about that too. Wouldn't you just copy your database to the laptop, and then run scan folders for changed paths, pointing to the new file location? Yes, you want 100% accuracy, but in this case, the program only needs to check for changed paths—not new files. If it's trying to match the title directly to the new path while ignoring the filename already recorded, I'd say the code needs to be revised to take the old filename into account. I can't imagine why anyone would move files and change file names and expect PVD to rematch everything all at the same time. Furthermore, even though you can't drag a server with you on vacation, there's no reason not to take your entire database. This would be much easier and faster than rebuilding a new database. PVD will do a good job of telling you what's available to watch, and what you left behind.

Yes the files would need to be copied together if movie files were moved, but I already do that with subtitled movies.

I have no doubt you can do it—you're the one running an industrial network in your home! Other users don't where or how there files are stored. For them, separate files increases the risk of things going wrong. But then they're not likely to be interested in this feature, are they?

Support / Re: Scan folders/file scanner confusion
« on: June 20, 2008, 03:55:44 am »
Has writing cataloguing data back to the movie files been considered...

When I first read this, I found the idea appealing. It would offer greater peace-of-mind PVD would not be "confused," should I move or rename movie files. I'm trying out Media Center, and one of my disappointments is I cannot import PVD data into it. Probably just as well—I don't want to be maintaining two databases. But if PVD could write back to the movie files, I suspect MC would read the information automatically. In stark contrast, I've always maintained my music information in ID3 tags, and all of it is seamlessly available in whatever software I choose to use.

I'm not familiar with the tagging convention, but a lot of meta information can be saved in AVI files. I imagine the first issue here is MediaInfo (the DLL PVD uses to get information from movie files) only reads, does not write information. So nostra would have to figure out how to do that. And what about other file formats? While writing only to AVI's for this limited purpose may not be difficult, it opens the door to what could be a major new feature that would probably not be easy to support: What about other programs using the same information? Being able to get my PVD information into MC would be great, for example, but what would PVD do when MC wrote its version of the information back to the tags?

Movie files are stored on a file server and accessed by multiple users / computers within the home...

I suppose each user would want to maintain their own database, but based on the same store of movies on the server. Nevertheless, would it not make sense to built a "master" database of all movies on the server? Then each user could start with a copy of that, and delete the movies they're not interested in.

Probably the easiest way to achieve this is if PVD had "*.id3" export and import formats.

I thought ID3 was for music only. Much of the information is the same, but does it provide for tags unique to movies? I suppose a tagging convention—if that's what it is—doesn't necessarily address the issue of how such tags are included in various file types. Thus your suggestion the information could be saved to separate files. I've never come across anything, however, that would suggest other programs could make use of information saved this way. Even if this works for your specific purpose, saving the information in the movie files removes the risk of the files getting separated.

Development / Re: Language files
« on: June 14, 2008, 02:49:30 am »
Thanks for the update. You seem to be raising the bar on yourself. I've come to expect you'll fix anything that need fixing in "a week or so." Now you're implementing mere suggestions in less than 24 hours!  ;D

Support / Re: Scan folders/file scanner confusion
« on: June 13, 2008, 05:52:45 pm »
but it is possible to enable users to setup how PVD should parse the file names.

But then it would be my fault if it didn't work!  ;D

Development / Language files
« on: June 13, 2008, 06:20:45 am »
Being hopelessly anglo, I can't help you with translations, but here are some corrections for the English file:

  504, "Also know as{IFCTRL}:" --> "Also known as{IFCTRL}:"
  511, "Aditional Rating{IFCTRL}:" --> "Additional Rating{IFCTRL}:"
  512, "Aditional Rating Name" -->  "Additional Rating Name"
  856, "Put at the begining of the title" --> "Put at the beginning of the title"
  881, "(Warning these changes can not be undone easily)" -->  "(Warning: These changes can not be undone easily)"
1037, "Series with expisodes" -->  "Series with episodes"
1043, "Selected Series with expisodes" -->  "Selected series with episodes"
1453, "Aditional Information" -->  "Additional Information"
1908, "An Error occured while connecting to the server.#13%s" -->  "An Error occurred...
1914, "An Error occured while getting file information.#13%s" -->  "An Error occurred...
1918, "An Error is occured while saving data.#13%s" -->  "An Error is occurred...
1919, "...Are you shure you want to proceed?" -->  ...Are you sure you want to proceed?"
1927, "...The file %s already exsists." -->  ...The file %s already exists."
2462, "Tommorow" -->  "Tomorrow"

And while I'm at it, a suggestion... There's nothing wrong with the filters menu, but I find it helps if it is as simple and logical as possible. Following is an excerpt from my custom language file. By naming each filter group in the form "All—Attribute—Not attribute," it's much easier to take in the status of all filters at a glance, and still understand from the position/context what each one means.

 402, "&All"
 403, "&Not viewed"
 404, "&Viewed"
 405, "All"
 406, "Owned"
 407, "Not owned" (i.e., on wish list)
 408, "All"
 409, "Loaned"
 410, "Not loaned"
 411, "All"
 412, "Online"
 413, "Not online"
 414, "All"
 415, "Bookmarked"
 416, "Not bookmarked"
 417, "All"
 418, "Movies"
 419, "Series"
 431, "No poster"
 432, "No photo"
 433, "No cover"
 434, "No screenshot"
 430, "Advanced filters"
 435, "All"
 436, "Visible"
 437, "Not visible"

Users, of course, can have it their own way by using a custom language file, as described here:

Support / Re: Scan folders/file scanner confusion
« on: June 13, 2008, 12:22:27 am »
The scanner has a complex algorithm for detecting where to put files and how to combine them, but it is certainly not perfect...

Your programming skills never cease to amaze me, but I have a hard time seeing how this ever will be perfect. I think you have the "right" to dictate to users a file naming convention to be used for files to be recognized by the program. Hopefully it would be flexible, but surely you need some degree of consistency. And users need to know what will be recognized. Some will have large collections named in a manner that doesn't comply, but it's not very difficult to rename files using a batch renaming utility (or a "home-made" batch file).

In the case of episodes, there are so many different ways they may be organized and named, it's probably easier for all if you decided how it should be done. I like Dadeo's ..\Title\Title.S02E01.episodename.avi, especially if, with that format, your routine could consistently identify titles—whether the episode files are in a separate sub-folders or not.

Support / Re: Importing from Excel
« on: May 25, 2008, 06:12:09 pm »
PVD accepts length as hh:mm:ss or a number of minutes without text after or before it.

Thanks. You saved me from more testing.  :P

...So, the most effective way to deal with this sort of situation is to convert the form of the data using Excel. In this case, =TEXT(LEFT(Length,LEN(Length)-4),"0") would do the trick (replace Length with a reference to the cell with length in the form "123mins").

"hh:mm:ss" is another matter. If the data is already in this form, in text, the plugin will recognize it. If it is not text, but a time-value the cell is formatted to display like this, it will need to be converted to text with =TEXT(Length,"hh:mm:ss").

Once the new column with the formulae is displaying the data in the correct format, use Copy-Paste Special-Values to convert it to text. Now that it no longer relies on the original data, that column may be deleted.

Support / Re: Importing from Excel
« on: May 25, 2008, 12:47:02 pm »
Nostra said i'd need to keep the plugin configured for all fields...

This really isn't that complicated. What nostra was trying to say, and what I attempted to clarify with my previous post, was you must configure the plugin exactly according to the columns that exist in your Excel file. It doesn't matter whether you have two columns or twenty. The plugin has no way of determining which field the data in each column should be put unless you tell it—for each and every column.

If i only selected to import title and length then surley the length would end up in my 'B' column which is my description column.

Maybe the reason you're not getting this is that you think your Excel file is "fixed." When I suggest you can import just the length field, I'm assuming you will make a copy of your Excel file, delete all the columns except title, year and length, and then save this new file for importing to PVD. If you insist on importing from your original Excel database each time, you will have to be very careful that your plugin configuration is correct. Furthermore—as you have discovered—if anything goes wrong, it's much more difficult to figure out what happened.

About the 'Length' columns, i have simply typed in the runtime like this: 60mins, 54mins etc.

I'm not sure exactly what format the plugin is expecting (i.e., "hh:mm" or "mmm"). I'd be surprised if it understood "60mins" (and, it seems you have already found it does not). I see PVD exports length in minutes ("mmm"), so let's assume the import plugin will recognize that. Since you're not comfortable using formulas, try this: Select your length column, Edit-Replace "mins" with nothing (i.e., delete all occurrences of "mins"), and format the column as text. This is confusing, but... what you want your minutes to look like numbers, but to actually be text.

Support / Re: Importing from Excel
« on: May 24, 2008, 11:23:29 pm »
...and what title you'd like to select for each column.

I think you understand, but this is not literally correct. The plugin will ignore whatever titles you put on the first row of the worksheet. The plugin configuration assigns valid PVD fields to each column. All that matters is that those fields are listed in the same order at the columns appear.

Maybe this should be added to a future help file...

Perhaps. In the meantime, consider this forum to be a help file that TALKS BACK TO YOU.  ;)


Aside from the matter of this data needing to be converted to text, the simplest import of additional information to movies already existing in the database would require two columns—one to identify the record (Title) and one for the additional information (e.g., Length). Remember what I said about this before...

Each time you use the import plugin, include the movie title and year so the correct record in PVD can be identified. It won't matter what other records are in the database at the time, or what order they are in. If you change any titles in PVD, you might have to take care to make the same changes in your Excel file so any future imports will work correctly. I suppose it would be a good idea to refrain from changing titles in PVD until you have finished all your importing.

there is no need to save the data you have enetered into the database, it saves automatically

This is not "autosave." This is how "true" database software works—all changes are immediately written to disk. This is not something that can be "turned off." I suppose some kind of "undo" feature is feasible, but it may not be what you expect. Many changes are going to be so pervasive, it would not be possible to maintain reliable undo information for very long. (When you add a movie, about 20 people—maybe many more—will be added. For each of those, a complete filmography may be included. So adding one movie can easily involve 500 records being added to/updated in the database. You're right, frequent backup is probably the only answer. Perhaps some kind of backup reminder can be added.

Support / Re: Importing from Excel
« on: May 24, 2008, 10:19:16 pm »
The plugin must always be configure for all fields.

That is, all columns in the Excel file.

Change the type to "Text".

Nostra, does it matter whether the text is in the form "hh:mm:ss" or just "hh:mm" or "mmm"?

If the data in Excel is a number displayed as time, then make a new column using =LEFT(TEXT(TimeCell,"hh:mm:ss"),8). Select the new column, Copy it, and Paste-Special-Values it to another column (or on top of itself, if you like). This column will be text you can import (subject to what nostra may say about format).

Support / Re: Importing from Excel
« on: May 24, 2008, 01:24:51 am »
It may take me years, but eventually I'll reverse-engineer this masterpiece of yours!  ;D

Support / Importing from Excel
« on: May 24, 2008, 12:59:37 am »
Time to start a new topic—continued from Where do i begin??? Help File???

I don't think I've seen this behaviour before, but maybe I never tried importing something with blanks in it. Can you run a test with a small sample (e.g., three records—two "good" ones, with a "problem" one in between) to isolate the problem? Maybe it's a bug. And maybe you'll discover a workaround is just to put something (like a "-") in otherwise blank fields.

I tried testing the Excel import plugin—to see if I could replicate ruffa's problem and to answer some of my own questions about how it works. This is what I have learned...

It seems the plugin is not dependent on headings in the Excel file. As long as the configuration has the correct sequence of columns specified, it will work even if there is no heading row. On the other hand, it does recognize the first row is headings, if that's what they are. So I'm not sure what the implications are of excluding it. My preference is to include headings to help keep track of what I'm doing. Attached is a screenshot illustrating how I view my Excel file while entering the configuration. The Excel headings are not necessary for the plugin, but I do need to list the fields in the configuration in exactly the same order as the columns in Excel.

When importing additional information to existing records, the attached confirmation dialog appears. It may seem straightforward, but can be a little confusing when one appreciates the import works on a field level, not just for each record as a whole. This is what each option does:

Update adds source (Excel) field if destination record exists (as determined by matching ID, Title/Year or URL); otherwise does nothing.

Merge adds source (Excel) field if destination field (PVD) is null; otherwise leaves destination data intact.

Add adds all the source fields to a new duplicate record; the existing record is unaffected.

Do not add skips the record; continues the import with the next record.

Overwrite replaces the destination field with the source field; if the source field is null, the destination field is left unchanged.

Cancel terminates the import.

This dialog will appear for each record already in the database unless "do not show again is checked"—then the response is applied to all records imported.

It's easy to assume all records will be "updated" when choosing Overwrite. It can be important to recognize blank fields in import records will not cause existing data to be "deleted." If this is what is intended, blank cells in Excel should be changed to "null" or "delete me," which can be deleted in PDV after importing (if available for the field, using multiple movie editor).

Now, back to ruffa's problem: I was unable to replicate the problem with any combination of blank cells or special characters (like common field delimiters) in the data. Once the import was properly configured, it worked without error both initially, and when used again to add or change data. I only found this kind of error (data in wrong field for some records, not others) when changing columns the Excel file and not making the same change in the plugin configuration (or vice versa). For the reasons already mentioned, the corruption resulting from this can be difficult to interpret because some records are affected and others are not (e.g., a record is not updated because the import field is null, or the destination is not). Furthermore, for the same reasons, if the configuration is then fixed, running the import again will not fix the corruption unless all the affected fields are included, none of them are null, and the overwrite option is used. In most cases, it would be easier to restore from backup or start a new database than to "undo" an import that has run amuck.

[attachment deleted by admin]

Pages: 1 ... 113 114 115 116 117 [118]