<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">something like that might be enough:<div>GIT repository: <a href="mailto:git@github.com">git@github.com</a>:NicolasRannou/VTK.git</div><div><br></div><div>I just added 2 variables BitRate and BitRateTolerance in the vtkFFMPEGWriter.cxx.</div><div>They are initialized to 0.</div><div><br></div><div>If they they are not modified( i.e. equal 0), the vtkFFMPEGWriter would work exactly in the same way as before.</div><div>If we modifify one of the value, we would use the modified values:</div><div><br></div><div>c->bit_rate = BitRate rather than</div><div>c->bit_rate = preset value</div><div><br></div><div>and</div><div><br></div><div>c->bit_rate_tolerance = BitRateTolerance rather than</div><div>c->bit_rate_tolerance = c->bit_rate/this->FrameRate;</div><div><br></div><div>Let me know if it is enough.</div><div>It worked fine for me but more modification might have to be done (not sure since I am not a FFMPEG expert).</div><div><br></div><div> Nicolas</div><div><br></div><div><div><div>On Jul 29, 2010, at 4:41 PM, Dave Partyka wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">In the past there were no versions of FFMPEG (until just recently) other than svn revisions. So we just picked an arbitrary revision that worked on all of our platforms and stuck with it. Also, we use one of the most basic and mature codecs (mjpeg) which I don't think has changed much? Anyway, keep us posted.<br> <br><div class="gmail_quote">On Thu, Jul 29, 2010 at 4:37 PM, Nicolas Rannou <span dir="ltr"><<a href="mailto:Nicolas_Rannou@hms.harvard.edu">Nicolas_Rannou@hms.harvard.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto; "> <div style="word-wrap:break-word">I think that if the ancient FFMPEG is working with the current VTK git master it should still work after.<div>I'm currently using the FFMPEG deb package provided with ubuntu 10.04.<div> <br><div>I'll fork the VTK git master, commit the changes and let you know as soon as it is done then we can give it a try with Paraview.</div><div><br></div><div>Is there any reason about using the ancient FFMPEG in Paraview?</div> <div><br></div><font color="#888888"><div> Nicolas</div></font><div><div></div><div class="h5"><div><br><div><div>On Jul 29, 2010, at 3:38 PM, Dave Partyka wrote:</div><br><blockquote type="cite">I don't have any objections but would like to know if that change is compatible with the ancient FFMPEG we typically release ParaView with.<div> <br></div><div><a href="http://www.vtk.org/files/support/ffmpeg_source.tar.gz" target="_blank">http://www.vtk.org/files/support/ffmpeg_source.tar.gz</a></div> <div><br><br><div class="gmail_quote">On Thu, Jul 29, 2010 at 3:21 PM, Nicolas Rannou <span dir="ltr"><<a href="mailto:nicolas_rannou@hms.harvard.edu" target="_blank">nicolas_rannou@hms.harvard.edu</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto; "> Hi all,<br> <br> We are experimenting issues regarding the usage of vtkFFMPEGWriter.cxx.<br> It occurs at least on Mac and Ubuntu 10.04.<br> You can reproduce the error turning VTK_USE_FFMPEG ON and running the<br> associated test. (ctest -R FFMPEG)<br> <br> ERROR:<br> [mjpeg @ 0x2db2f30]bitrate tolerance too small for bitrate<br> Generic Warning: In /home/nr52/GITROOT/VTK/IO/vtkFFMPEGWriter.cxx, line 197<br> Could not open codec.<br> <br> The problem is located at /VTK/IO/vtkFFMPEGWriter.cxx:179, where the bit_rate_tolerance is defined as:<br> c->bit_rate_tolerance = c->bit_rate/this->FrameRate;<br> <br> Then, this error ("bitrate tolerance too small for bit-rate") can easily be solved decreasing the FrameRate.<br> <br> Moreover, there is no convenient method to set the bit-rate.<br> So far, can only choose between 3 predefined bit-rates, which is quite restrictive.<br> <br> So here is my question: Is there any reason for not creating variables BitRate and BitRateTolerance?<br> If there is no objection, I can take care of it.<br> <br> Thanks<br> <br> <br> Nicolas<br> <br> <br> _______________________________________________<br> Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br> <br> Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br> <br> Follow this link to subscribe/unsubscribe:<br> <a href="http://www.vtk.org/mailman/listinfo/vtk-developers" target="_blank">http://www.vtk.org/mailman/listinfo/vtk-developers</a><br> <br> </blockquote></div><br></div> </blockquote></div><br></div></div></div></div></div></div></blockquote></div><br></blockquote></div><br></div></body></html>