<div class="gmail_quote">On Wed, Aug 11, 2010 at 8:35 PM, Another Sillyname <span dir="ltr"><<a href="mailto:anothersname@googlemail.com">anothersname@googlemail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="h5">Because Gavin nuvexport doesn't handle AC3 or H264 particularly well,</div></div>
and I don't code in perl.<br>
<br>
If you don't want to use it that's fine but don't criticise people<br>
trying to at least add to functionality.<br></blockquote><div><br></div><div>I see. So the *two* H.264 exporters I added recently don't handle particularly well? OK then.</div><div><br></div><div>Nobody said you'd need to code in perl. Working with people doesn't always mean giving patches, you know. A simple ffmpeg/transcode/mencoder/whatever command line that does what you want would go a long way.</div>
<div><br></div><div>If you'd like to add functionality rather than just fragment the support, working with those who already got a good start on it is usually a better plan than reinventing the wheel differently. Especially if claims of superiority get involved. </div>
<div><br></div><div>I'd be happy to create a new exporter based on what you've found to work for you. It seems like you've gone through a lot of trouble to tweak things to how you want them, including reinventing pretty much all of nuvexport, and for little or no gain to the rest of the community over simply asking one of us to add it to nuvexport in the first place...</div>
<div><br></div><div>But whatever works, you are always welcome to make your own scripts. It's likely to be more supported in nuvexport though.</div></div>