2009/12/1 Atte André Jensen <span dir="ltr"><<a href="mailto:atte.jensen@gmail.com">atte.jensen@gmail.com</a>></span><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi<br>
<br>
A friend of mine has invited me to compose for some videos he's planning<br>
on making. We haven't started yet, but I thought it might be good to be<br>
a bit ahead, especially since I haven't done this before and I know next<br>
to nothing about video...<br>
<br>
The noise making apps will be running ontop of jack. Google suggest I<br>
should look into xjadeo with the -i switch. Is that it? Anything<br>
(formats, codecs, framerates, interlaces other-stuff-I-dont-get) that I<br>
should ask for or try to avoid?<br>
<br>
Any input, including links, tips, thoughts, would be highly appreciated!</blockquote><div><br></div><div>:O</div><div><br></div><div>You're asking for a walkthrough on Sound for Film!</div><div><br></div><div>To start you off, frame rate is the most important. But of course, on Linux, we have more than enough tools to convert foreign sources into workable formats. On something like Pro Tools, if there is a frame rate mismatch with source and project, the track's apparent rate will be highlighted in red.</div>
<div><br></div><div>Formats, Codecs: You are limited to what the video syncing application supports, but it's not a big issue since you don't need to worry about it. Again, frame rate _is_ an issue and we assume it is taken care of properly when converting.</div>
<div><br></div><div>(De)interlacing: Nothing to do with audio, but you should get to know it.</div><div><br></div><div>xjadeo + ardour isn't the most intuitive of workflows, but for some people it just works :)</div>
</div>
<br clear="all"><br>-- <br>GPG/PGP ID: B42DDCAD<br>