Comments on: Confusion and video editing http://eugenia.gnomefiles.org/2008/01/22/confusion-and-video-editing/ Sat, 22 Nov 2008 18:23:05 +0000 http://wordpress.org/?v=2.2.2 By: Eugenia http://eugenia.gnomefiles.org/2008/01/22/confusion-and-video-editing/#comment-5464 Eugenia Tue, 22 Jan 2008 23:40:28 +0000 http://eugenia.gnomefiles.org/2008/01/22/confusion-and-video-editing/#comment-5464 For pixel aspect ratios all it needs for people to get it, is a visual representation as to how things change when they choose a different ratio. Vegas' project properties is very good for what it is, but a visual representation would make it even better. For pixel aspect ratios all it needs for people to get it, is a visual representation as to how things change when they choose a different ratio. Vegas’ project properties is very good for what it is, but a visual representation would make it even better.

]]> By: Cesar http://eugenia.gnomefiles.org/2008/01/22/confusion-and-video-editing/#comment-5461 Cesar Tue, 22 Jan 2008 17:32:31 +0000 http://eugenia.gnomefiles.org/2008/01/22/confusion-and-video-editing/#comment-5461 Deinterlacing is the most difficult thing to get it done right when your footage is a high motion 60 fields per second scene. Deinterlacing is the most difficult thing to get it done right when your footage is a high motion 60 fields per second scene.

]]> By: Dominique http://eugenia.gnomefiles.org/2008/01/22/confusion-and-video-editing/#comment-5459 Dominique Tue, 22 Jan 2008 16:06:34 +0000 http://eugenia.gnomefiles.org/2008/01/22/confusion-and-video-editing/#comment-5459 Thanks. As a starting hobbyist, I appreciate your of outlining some of the minor pitfalls. Thanks.

As a starting hobbyist, I appreciate your of outlining some of the minor pitfalls.

]]> By: Richard http://eugenia.gnomefiles.org/2008/01/22/confusion-and-video-editing/#comment-5456 Richard Tue, 22 Jan 2008 13:50:00 +0000 http://eugenia.gnomefiles.org/2008/01/22/confusion-and-video-editing/#comment-5456 And the really tricky part is designing a User Interface for setting Pixel-Aspect Ratios and such stuff. Especially if you are totally sure that the majority of the users won't have the slightest clue what the Application is asking. I've recently posted a proposal for a "User Interface" solution to this problem to the cinelerra Mailinglist: So, Framesize, Interlacing and Pixel-Aspect are hard problems. In my humble Opinion the only serious attempt to solve that problem in a fashion that is at least somehow universial, is the following. You need several tools, One Tool would be like the unix "file" utility. A tool that scans a video source and makes a good guess about what kind of Interlacing and Pixel-Aspect is being used. The Second Tool is some kind of machine readable Knowledge-Database, that is filled with rules and heuristics about common frame-sizes, their assorted pixel-aspects, and how and when and when certain formats are used, and how they should be converted to other formats when necessary. This information will likely be useful to the "Source-Analysis-Tool" as well, as mentioned in the paragraph above. Additionally the Knowledge Base should also be sprinkled with human readable information, Such as: "You are exporting a 24p file to 29.97i, a 3:2 Pulldown will be performed for conversion, for more information about that, click here...". Ideally the knowledge base should have information available for most of the common cases. In case there are conflicting rules, or two equally likely options, the database should have enough information available to ask the user the question whether he prefers A or B. --8 And the really tricky part is designing a User Interface for setting Pixel-Aspect Ratios and such stuff. Especially if you are totally sure that the majority of the users won’t have the slightest clue what the Application is asking.

I’ve recently posted a proposal for a “User Interface” solution to this problem to the cinelerra Mailinglist:

So, Framesize, Interlacing and Pixel-Aspect are hard problems. In my humble Opinion the only serious attempt to solve that problem in a fashion that is at least somehow universial, is the following.

You need several tools, One Tool would be like the unix “file” utility. A tool that scans a video source and makes a good guess about what kind of Interlacing and Pixel-Aspect is being used.

The Second Tool is some kind of machine readable Knowledge-Database, that is filled with rules and heuristics about common frame-sizes, their assorted pixel-aspects, and how and when and when certain formats are used, and how they should be converted to other formats when necessary. This information will likely be useful to the “Source-Analysis-Tool” as well, as mentioned in the paragraph above.

Additionally the Knowledge Base should also be sprinkled with human readable information, Such as: “You are exporting a 24p file to 29.97i, a 3:2 Pulldown will be performed for conversion, for more information about that, click here…”.

Ideally the knowledge base should have information available for most of the common cases. In case there are conflicting rules, or two equally likely options, the database should have enough information available to ask the user the question whether he prefers A or B.

–8

]]>