MantisBT - ParaView
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0014215ParaView(No Category)public2013-08-07 03:022016-08-12 09:59
Reporterhamidnt 
Assigned ToKitware Robot 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionmoved 
PlatformOSOS Version
Product Version4.0 
Target VersionFixed in Version 
ProjectTBD
Topic Name
Typecrash
Summary0014215: Paraview 4.0.1 does not compile with FFMPEG 2.0
DescriptionFFMPEG 2.0 has changed CodecID to AVCodecID. This makes paraview compile to fail when ffmpeg is enabled. Making the mentioned change in the file VTK/IO/FFMPEG/vtkFFMPEGWriter.cxx will remove the issue.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2013-08-07 03:02hamidntNew Issue
2013-08-19 16:25Marcus D. HanwellNote Added: 0031487
2013-08-23 15:48hamidntNote Added: 0031493
2013-08-23 15:49hamidntNote Edited: 0031493bug_revision_view_page.php?bugnote_id=31493#r649
2016-08-12 09:59Kitware RobotNote Added: 0038434
2016-08-12 09:59Kitware RobotStatusbacklog => closed
2016-08-12 09:59Kitware RobotResolutionopen => moved
2016-08-12 09:59Kitware RobotAssigned To => Kitware Robot

Notes
(0031487)
Marcus D. Hanwell   
2013-08-19 16:25   
I hit this last week, and hope to find some time to get to it. It is an API change in ffmpeg, but we would like like to retain support for the old and new API.
(0031493)
hamidnt   
2013-08-23 15:48   
(edited on: 2013-08-23 15:49)
As far as I encountered, since this API change effect is very local (only one place in the file vtkFFMPEGWiter.cxx uses CodecID), both new and old ffmpeg can be easily supported via a c++ macro definition and the necessary test condition in the CMakeLists.txt file. However, coding standards of the Paraview project may require more elaborate solutions, which I am not aware of.
(0038434)
Kitware Robot   
2016-08-12 09:59   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current ParaView Issues page linked in the banner at the top of this page.