<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Feb 29, 2008, at 2:43 PM, Corey Wirun wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: 'Bitstream Vera Sans'; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0; "><div bgcolor="#ffffff" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><font face="Arial" size="2">Thanks Brad! How much reasonably should bitrate be bumped up (in the recording profile)? And where is the mpeg2->mpeg2 profile you mention?</font></div></div></span></blockquote><div><br class="webkit-block-placeholder"></div>I use a bitrate of 6000 and max of 8500 and I'm happy with that quality. YMMV. I can be pretty picky about how something looks and I have 3.2TB of storage so I don't have to worry about it.</div><div>Actually, I think the mpeg2 cutting profile will be in 0.21 when it's released. This might have been added after 0.20 was released. Sorry about that, but it's a very compelling reason to upgrade. :)</div><div>You might be able to run a manual (or scripted user job) ffmpeg command to get what you need but someone else would have to help you with that.</div><div><br class="webkit-block-placeholder"></div></body></html>