<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Moooving Pictures</title>
	<atom:link href="http://www.jonobacon.org/2008/01/18/moooving-pictures/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.jonobacon.org/2008/01/18/moooving-pictures/</link>
	<description>At home with Jono Bacon, Community Manager and Author</description>
	<lastBuildDate>Tue, 16 Mar 2010 22:28:50 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: troy_s</title>
		<link>http://www.jonobacon.org/2008/01/18/moooving-pictures/comment-page-1/#comment-125536</link>
		<dc:creator>troy_s</dc:creator>
		<pubDate>Sun, 21 Sep 2008 18:01:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.jonobacon.org/?p=1102#comment-125536</guid>
		<description>&lt;p&gt;@Dries:
Sorry on the P2 slang.  I was referring to Panasonic&#039;s HVX200 -- which was commonly referred to as the &#039;P2&#039;.  I guess we should be a little more careful throwing the term &#039;P2&#039; around now that there are more models out there.&lt;/p&gt;

&lt;p&gt;The HVX200 dumps down DVC100 to disk.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>@Dries:
Sorry on the P2 slang.  I was referring to Panasonic&#8217;s HVX200 &#8212; which was commonly referred to as the &#8216;P2&#8242;.  I guess we should be a little more careful throwing the term &#8216;P2&#8242; around now that there are more models out there.</p>

<p>The HVX200 dumps down DVC100 to disk.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Dries Desmet</title>
		<link>http://www.jonobacon.org/2008/01/18/moooving-pictures/comment-page-1/#comment-125534</link>
		<dc:creator>Dries Desmet</dc:creator>
		<pubDate>Sun, 21 Sep 2008 10:16:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.jonobacon.org/?p=1102#comment-125534</guid>
		<description>&lt;p&gt;@troy_s: &quot;Which is why no professional house does effects work on an Avid or any other cutting tool. The work flow doesnâ€™t expect a single tool to do it all. There are editors and visual effects supervisors with their respective houses / teams.&quot;&lt;/p&gt;

&lt;p&gt;Which is why I mentioned Nuke, Shake and Houdini in my previous post. I think Avid is crap at effects, but for editing, it&#039;s one of the best out there: excellent media management, simple mark in/mark out approach, robust and nice trimming. I suspect the robustness and trimming responsiveness has a lot to do with the codec all avid video gets converted to. There is simply too much cruft in video codecs and container formats, not only in the FOSS world, but also on Windows. Like or dislike quicktime, but at least it feels like os x is consistent in media production formats. My hope is that mxf will rise as a cross platform professional container format, that can hold DV, but also h264,mpegHD, and so on.&lt;/p&gt;

&lt;p&gt;P2 is just a medium, it has nothing to do with container format nor codec.&lt;/p&gt;

&lt;p&gt;Not sure about Panasonic, but Sony Broadcast camera&#039;s already record directly to .mxf files.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>@troy_s: &#8220;Which is why no professional house does effects work on an Avid or any other cutting tool. The work flow doesnâ€™t expect a single tool to do it all. There are editors and visual effects supervisors with their respective houses / teams.&#8221;</p>

<p>Which is why I mentioned Nuke, Shake and Houdini in my previous post. I think Avid is crap at effects, but for editing, it&#8217;s one of the best out there: excellent media management, simple mark in/mark out approach, robust and nice trimming. I suspect the robustness and trimming responsiveness has a lot to do with the codec all avid video gets converted to. There is simply too much cruft in video codecs and container formats, not only in the FOSS world, but also on Windows. Like or dislike quicktime, but at least it feels like os x is consistent in media production formats. My hope is that mxf will rise as a cross platform professional container format, that can hold DV, but also h264,mpegHD, and so on.</p>

<p>P2 is just a medium, it has nothing to do with container format nor codec.</p>

<p>Not sure about Panasonic, but Sony Broadcast camera&#8217;s already record directly to .mxf files.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: troy_s</title>
		<link>http://www.jonobacon.org/2008/01/18/moooving-pictures/comment-page-1/#comment-118659</link>
		<dc:creator>troy_s</dc:creator>
		<pubDate>Sun, 09 Mar 2008 17:36:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.jonobacon.org/?p=1102#comment-118659</guid>
		<description>&lt;p&gt;Blender.  It is our only glimmering hope for professional editing at this point.&lt;/p&gt;

&lt;p&gt;@Dries Desmet:
&quot;if you wanted the overlay text to be animated over a cut, you have to be able to put it on top of both clips at once. An effect is something that is done to a single clip.&quot;&lt;/p&gt;

&lt;p&gt;Which is why no professional house does effects work on an Avid or any other cutting tool.  The work flow doesn&#039;t expect a single tool to do it all.  There are editors &lt;em&gt;and&lt;/em&gt; visual effects supervisors with their respective houses / teams.&lt;/p&gt;

&lt;p&gt;Generally, &lt;em&gt;all&lt;/em&gt; effects work is done in a compositor, and the best of the best are &lt;em&gt;all&lt;/em&gt; available for Linux.  And yes, they are proprietary.  Nuke, Shake, Houdini, etc.  Don&#039;t expect to find a layer in Nuke.  It&#039;s all nodes all the time.&lt;/p&gt;

&lt;p&gt;That said, &lt;em&gt;shock&lt;/em&gt;, Blender too has a nodal compositor.  Cut your work in the NLE then apply your effects in the Nodal compositor.  Don&#039;t try and do too much in the editor.  Lord knows we have all seen enough of that rubbish on YouTube with the wonderful text overlays as someone shoots someone in Halo.  Woo.&lt;/p&gt;

&lt;p&gt;If we are serious about pushing FOSS, we &lt;em&gt;really&lt;/em&gt; need the final patches to get into ffmpeg&#039;s SVN for DVC100, and other details as they happen. ( See http://lists.mplayerhq.hu/pipermail/ffmpeg-devel/2008-January/039966.html  )&lt;/p&gt;

&lt;p&gt;That helps plenty on the P2 front, which has made a serious dent into professional television production -- the P2 is a standard tool for quickie shots that don&#039;t require visual effecting.&lt;/p&gt;

&lt;p&gt;The proprietary war to be fought on the Panavision Genesis and Arri&#039;s 35mm feature film replacement products is yet to be seen, and I don&#039;t know much about the format being laid to tape / disk, but I suspect that with Sony involved in the Genesis at one point (and now with their own camera -- the one which shot Speed Racer) that it is proprietary.  I would need to do a little more chit chat with the folks that are in the know on that sort of thing.&lt;/p&gt;

&lt;p&gt;Sincerely,
TJS&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Blender.  It is our only glimmering hope for professional editing at this point.</p>

<p>@Dries Desmet:
&#8220;if you wanted the overlay text to be animated over a cut, you have to be able to put it on top of both clips at once. An effect is something that is done to a single clip.&#8221;</p>

<p>Which is why no professional house does effects work on an Avid or any other cutting tool.  The work flow doesn&#8217;t expect a single tool to do it all.  There are editors <em>and</em> visual effects supervisors with their respective houses / teams.</p>

<p>Generally, <em>all</em> effects work is done in a compositor, and the best of the best are <em>all</em> available for Linux.  And yes, they are proprietary.  Nuke, Shake, Houdini, etc.  Don&#8217;t expect to find a layer in Nuke.  It&#8217;s all nodes all the time.</p>

<p>That said, <em>shock</em>, Blender too has a nodal compositor.  Cut your work in the NLE then apply your effects in the Nodal compositor.  Don&#8217;t try and do too much in the editor.  Lord knows we have all seen enough of that rubbish on YouTube with the wonderful text overlays as someone shoots someone in Halo.  Woo.</p>

<p>If we are serious about pushing FOSS, we <em>really</em> need the final patches to get into ffmpeg&#8217;s SVN for DVC100, and other details as they happen. ( See <a href="http://lists.mplayerhq.hu/pipermail/ffmpeg-devel/2008-January/039966.html" rel="nofollow">http://lists.mplayerhq.hu/pipermail/ffmpeg-devel/2008-January/039966.html</a>  )</p>

<p>That helps plenty on the P2 front, which has made a serious dent into professional television production &#8212; the P2 is a standard tool for quickie shots that don&#8217;t require visual effecting.</p>

<p>The proprietary war to be fought on the Panavision Genesis and Arri&#8217;s 35mm feature film replacement products is yet to be seen, and I don&#8217;t know much about the format being laid to tape / disk, but I suspect that with Sony involved in the Genesis at one point (and now with their own camera &#8212; the one which shot Speed Racer) that it is proprietary.  I would need to do a little more chit chat with the folks that are in the know on that sort of thing.</p>

<p>Sincerely,
TJS</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Alderweireldt</title>
		<link>http://www.jonobacon.org/2008/01/18/moooving-pictures/comment-page-1/#comment-115670</link>
		<dc:creator>Nick Alderweireldt</dc:creator>
		<pubDate>Thu, 07 Feb 2008 16:15:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.jonobacon.org/?p=1102#comment-115670</guid>
		<description>&lt;p&gt;NLE might be only &#039;nearly there&#039; but at least I get done what I want (using kino for capturing and cinelerra and kdenlie for editing). I have seen a lot of progress last couple of years (kino is solid, kdenlive came, ...).&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>NLE might be only &#8216;nearly there&#8217; but at least I get done what I want (using kino for capturing and cinelerra and kdenlie for editing). I have seen a lot of progress last couple of years (kino is solid, kdenlive came, &#8230;).</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Dries Desmet</title>
		<link>http://www.jonobacon.org/2008/01/18/moooving-pictures/comment-page-1/#comment-115310</link>
		<dc:creator>Dries Desmet</dc:creator>
		<pubDate>Wed, 23 Jan 2008 11:41:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.jonobacon.org/?p=1102#comment-115310</guid>
		<description>&lt;p&gt;I agree that titles should be a separate layer: if you wanted the overlay text to be animated over a cut, you have to be able to put it on top of both clips at once. An effect is something that is done to a single clip. You should be able to apply effects on a whole edit as well though. In avid, this is achieved by dropping an effect on an empty layer on top of your completed edit.&lt;/p&gt;

&lt;p&gt;Something I always liked in avid as well is collapsing of layers. Double clicking and you can go in, add as many layers as you want.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I agree that titles should be a separate layer: if you wanted the overlay text to be animated over a cut, you have to be able to put it on top of both clips at once. An effect is something that is done to a single clip. You should be able to apply effects on a whole edit as well though. In avid, this is achieved by dropping an effect on an empty layer on top of your completed edit.</p>

<p>Something I always liked in avid as well is collapsing of layers. Double clicking and you can go in, add as many layers as you want.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Eugenia</title>
		<link>http://www.jonobacon.org/2008/01/18/moooving-pictures/comment-page-1/#comment-115309</link>
		<dc:creator>Eugenia</dc:creator>
		<pubDate>Wed, 23 Jan 2008 09:49:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.jonobacon.org/?p=1102#comment-115309</guid>
		<description>&lt;blockquote&gt;
  &lt;p&gt;why do you have to create text as a seperate video when you want to overlay, rather than an effect?&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;It is more correct to have it as separate video because  this way it allows for more modifications and customization and animation. It might require from you to learn to use it a bit more, but in the long run, it is the right decision.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<blockquote>
  <p>why do you have to create text as a seperate video when you want to overlay, rather than an effect?</p>
</blockquote>

<p>It is more correct to have it as separate video because  this way it allows for more modifications and customization and animation. It might require from you to learn to use it a bit more, but in the long run, it is the right decision.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: mrben</title>
		<link>http://www.jonobacon.org/2008/01/18/moooving-pictures/comment-page-1/#comment-115297</link>
		<dc:creator>mrben</dc:creator>
		<pubDate>Mon, 21 Jan 2008 15:28:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.jonobacon.org/?p=1102#comment-115297</guid>
		<description>&lt;p&gt;I&#039;ve been doing various bits of editing under Linux for 3+ years now. When I first started Cinelerra just wouldn&#039;t work for me, but Kino did, and was surprisingly reliable. I think you can actually do most things in Kino that you can do in kdenlive, but it&#039;s not nearly as intuitive. &lt;/p&gt;

&lt;p&gt;That said, there are bits of kdenlive that I find annoying - for instance, why do you have to create text as a seperate video when you want to overlay, rather than an effect? It makes it very confusing when you&#039;re trying to crossfade to other video having overlaid. For a relatively simple video (just still images with overlaid text) I ended up using 4 video tracks. &lt;/p&gt;

&lt;p&gt;Still - kdenlive seems to be the current best, but I am hopeful that things &lt;em&gt;are&lt;/em&gt; moving forward, albeit slowly, because we are in a better state than 3 years ago....&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been doing various bits of editing under Linux for 3+ years now. When I first started Cinelerra just wouldn&#8217;t work for me, but Kino did, and was surprisingly reliable. I think you can actually do most things in Kino that you can do in kdenlive, but it&#8217;s not nearly as intuitive. </p>

<p>That said, there are bits of kdenlive that I find annoying &#8211; for instance, why do you have to create text as a seperate video when you want to overlay, rather than an effect? It makes it very confusing when you&#8217;re trying to crossfade to other video having overlaid. For a relatively simple video (just still images with overlaid text) I ended up using 4 video tracks. </p>

<p>Still &#8211; kdenlive seems to be the current best, but I am hopeful that things <em>are</em> moving forward, albeit slowly, because we are in a better state than 3 years ago&#8230;.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Dries Desmet</title>
		<link>http://www.jonobacon.org/2008/01/18/moooving-pictures/comment-page-1/#comment-115292</link>
		<dc:creator>Dries Desmet</dc:creator>
		<pubDate>Mon, 21 Jan 2008 11:30:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.jonobacon.org/?p=1102#comment-115292</guid>
		<description>&lt;p&gt;I&#039;ve come to the same conclusion like many of you regarding video editing on linux. I&#039;m not willing to give up just yet though. I have been most impressed with the diva project, although dead by now, it had the right approach. It doesn&#039;t mean that a community driven editing app is not ever going to emerge. I see a few pitfalls:
- There currently isn&#039;t a fully working well documented editing framework. We need this first. This actually is the sole point why diva came to a stop. The developer started with gstreamer, but the gnonlin part of that framework wasn&#039;t and still isn&#039;t ready to start building a well establised editing app. Have to look into this, but it&#039;s not even sure that gstreamer is the right approach at all. It was never meant as an editing framework, but in linux that is no reason to rule it out either.
- We need to concentrate on very basic editing first: cut cut editing has to work superstable. No fancy video filters or transitions are necessary at the beginning. They just should be plug-in-able afterwards.
- We need to concentrate on 1 video container format, that is not limited to 1 codec. Preferably open source, but no idea if .ogg is ready for this. I would actually opt for a professional open format that is called mxf. It can contain multiple video and audio layers and is interchangeable between all professional apps.
- Do not try to include all the features of professional apps but do follow professional standards. Consumer formats tend to change and wave off in different directions and are unmaintainable because of that. If necessary, implement import export filter, but work in a common base system. Avid, for example, reencodes or rewraps all input sources to a common base system. Allthought I agree there is overhead when you want to mix different formats by doing so, but at least it keeps things consisent.
- Don&#039;t overload the ui. Editing is done with keyboard shortcuts only, nothing more. Gigantic play and pause buttons just 
- Good trimming: frame accurate trimming is EVERYTHING in editing. This has it&#039;s influences in the codec to be used. I don&#039;t care if file sizes are bigger, as long as good trimming and scrubbing video is rock solid.
- Consider titling and other effects to be a completely different module or even a completely different app. There are far more possibilities with node based input-output workflows a la fusion, shake and nuke than trying to cram everything on a timeline based editing package.
- Bake in the possibility of doing offline and online editing. This may sound &#039;professional&#039; but really  is nothing more than implementing a low quality codec and a full quality coded&#039;. If relinking mediaclips is well organized and consistent, than this is a feature that can be very usefull for home videos as well. Just use different terms for online or offline if that is the thing that scares you.
- Since the target audience for an app like this is rather limited in the linux world, it would be a nice plus to be able to run it on os x or windows alike.  I note that most of the existing editing apps actually don&#039;t use the native os gui: Avid, Premiere,Shake,Nuke,...&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I&#8217;ve come to the same conclusion like many of you regarding video editing on linux. I&#8217;m not willing to give up just yet though. I have been most impressed with the diva project, although dead by now, it had the right approach. It doesn&#8217;t mean that a community driven editing app is not ever going to emerge. I see a few pitfalls:
- There currently isn&#8217;t a fully working well documented editing framework. We need this first. This actually is the sole point why diva came to a stop. The developer started with gstreamer, but the gnonlin part of that framework wasn&#8217;t and still isn&#8217;t ready to start building a well establised editing app. Have to look into this, but it&#8217;s not even sure that gstreamer is the right approach at all. It was never meant as an editing framework, but in linux that is no reason to rule it out either.
- We need to concentrate on very basic editing first: cut cut editing has to work superstable. No fancy video filters or transitions are necessary at the beginning. They just should be plug-in-able afterwards.
- We need to concentrate on 1 video container format, that is not limited to 1 codec. Preferably open source, but no idea if .ogg is ready for this. I would actually opt for a professional open format that is called mxf. It can contain multiple video and audio layers and is interchangeable between all professional apps.
- Do not try to include all the features of professional apps but do follow professional standards. Consumer formats tend to change and wave off in different directions and are unmaintainable because of that. If necessary, implement import export filter, but work in a common base system. Avid, for example, reencodes or rewraps all input sources to a common base system. Allthought I agree there is overhead when you want to mix different formats by doing so, but at least it keeps things consisent.
- Don&#8217;t overload the ui. Editing is done with keyboard shortcuts only, nothing more. Gigantic play and pause buttons just 
- Good trimming: frame accurate trimming is EVERYTHING in editing. This has it&#8217;s influences in the codec to be used. I don&#8217;t care if file sizes are bigger, as long as good trimming and scrubbing video is rock solid.
- Consider titling and other effects to be a completely different module or even a completely different app. There are far more possibilities with node based input-output workflows a la fusion, shake and nuke than trying to cram everything on a timeline based editing package.
- Bake in the possibility of doing offline and online editing. This may sound &#8216;professional&#8217; but really  is nothing more than implementing a low quality codec and a full quality coded&#8217;. If relinking mediaclips is well organized and consistent, than this is a feature that can be very usefull for home videos as well. Just use different terms for online or offline if that is the thing that scares you.
- Since the target audience for an app like this is rather limited in the linux world, it would be a nice plus to be able to run it on os x or windows alike.  I note that most of the existing editing apps actually don&#8217;t use the native os gui: Avid, Premiere,Shake,Nuke,&#8230;</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Odin / Velmont</title>
		<link>http://www.jonobacon.org/2008/01/18/moooving-pictures/comment-page-1/#comment-115291</link>
		<dc:creator>Odin / Velmont</dc:creator>
		<pubDate>Mon, 21 Jan 2008 09:15:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.jonobacon.org/?p=1102#comment-115291</guid>
		<description>&lt;p&gt;I&#039;m a professional video editor (as in: that&#039;s where I earn my money). I&#039;ve been tracking Cinelerra for a long time, because I really want to trash my Mac with Final Cut Pro. I&#039;ve found out that this won&#039;t happen in a long time; however, this yule I sat down with Cinelerra, to really give it a fair try.&lt;/p&gt;

&lt;p&gt;And my oh&#039; my was I ever impressed. I &lt;em&gt;can&lt;/em&gt; actually be used for video editing; I made a cut of a DV-tape I had lying around - and it was rather painless once I understood that you don&#039;t have tools in Cinelerra, you must use RMB, MMB and LMB for different trimming-options.&lt;/p&gt;

&lt;p&gt;I can&#039;t switch to Cinelerra as my work platform (but I never expected that), however I&#039;ll use it for all my personal stuff in the future. Because it actually works, and works well.&lt;/p&gt;

&lt;p&gt;BTW: My laptop has 512MiB RAM and 1.5Ghz processor, so the Â«requirementsÂ» are just bull - use the CV-version. 
I tried kdenlive, but too unstable and crashy. 
lwn.net has a article series on video editing now soon; you should really read that when it is published.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I&#8217;m a professional video editor (as in: that&#8217;s where I earn my money). I&#8217;ve been tracking Cinelerra for a long time, because I really want to trash my Mac with Final Cut Pro. I&#8217;ve found out that this won&#8217;t happen in a long time; however, this yule I sat down with Cinelerra, to really give it a fair try.</p>

<p>And my oh&#8217; my was I ever impressed. I <em>can</em> actually be used for video editing; I made a cut of a DV-tape I had lying around &#8211; and it was rather painless once I understood that you don&#8217;t have tools in Cinelerra, you must use RMB, MMB and LMB for different trimming-options.</p>

<p>I can&#8217;t switch to Cinelerra as my work platform (but I never expected that), however I&#8217;ll use it for all my personal stuff in the future. Because it actually works, and works well.</p>

<p>BTW: My laptop has 512MiB RAM and 1.5Ghz processor, so the Â«requirementsÂ» are just bull &#8211; use the CV-version. 
I tried kdenlive, but too unstable and crashy. 
lwn.net has a article series on video editing now soon; you should really read that when it is published.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Richard</title>
		<link>http://www.jonobacon.org/2008/01/18/moooving-pictures/comment-page-1/#comment-115278</link>
		<dc:creator>Richard</dc:creator>
		<pubDate>Sat, 19 Jan 2008 23:42:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.jonobacon.org/?p=1102#comment-115278</guid>
		<description>&lt;p&gt;Open Movie Editor Developer here, happy to hear all your problems, and provide all the help necessary to get you up and running with it. ;-)&lt;/p&gt;

&lt;p&gt;Cheers
-Richard&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Open Movie Editor Developer here, happy to hear all your problems, and provide all the help necessary to get you up and running with it. <img src='http://www.jonobacon.org/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>

<p>Cheers
-Richard</p>]]></content:encoded>
	</item>
</channel>
</rss>
