Created attachment 177899 [details]
v0 + commit message
Build log: http://sprunge.us/daRc
Can you check runtime?
Thanks for this patch. Please allow me time to give it a test.
I will commit the change as soon as possible.
I tested it using an old RM set of mine, while sthe software compiles and runs it's unable to generate mpeg videos from the medical images (it can generate "fly through" videos).
When I try it gives this error:
Total number of movie frames to do: 450 increment 0.180073
[mpeg1video @ 0x81642f300] AVFrame.format is not set
[mpeg1video @ 0x81642f300] AVFrame.width or height is not set
And pops up a window saying frame 0 failed. Do you have any insight?
Created attachment 178246 [details]
I have modified your patch slightly, trying to address the problem. I fixed the error message I was getting but generating the video fails anyway.
I'm attaching my modified patch.
I don't know much about the ffmpeg APIs. Are you able to help me make it work again?
Comment on attachment 178246 [details]
I did a similar change but remembered it didn't fix a regression from bug 207547. Can you try building against ffmpeg 2.8.x (either rollback or use 2016Q4)? If the issue is the same it may be worth to bisect ffmpeg commits.
(In reply to Jan Beich (mail not working) from comment #4)
> Comment on attachment 178246 [details]
> I did a similar change but remembered it didn't fix a regression from bug
> 207547. Can you try building against ffmpeg 2.8.x (either rollback or use
> 2016Q4)? If the issue is the same it may be worth to bisect ffmpeg commits.
I tested using a 2016Q4 ports checkout, but installing dependencies from official packages, in a VirtualBox VM.
It fails with 2.8.x the same as it does with 3.x.
I don't know how the ffmpeg repos are managed, what should I bisect? this will take some time to do.
I have found this message on the amide mailing lists archives:
so there should be working patches here:
I'll test these and report back.
One question I must answer to though is, what copyright and license (if any) are these patches subject to and if such license is acceptable for importing in the source tree.
(In reply to Guido Falsi from comment #6)
> One question I must answer to though is, what copyright and license
> (if any) are these patches subject to and if such license is
> acceptable for importing in the source tree.
According to debian/copyright file the patches are under GPLv2+ much like AMIDE itself. So, treat like any other upstream patch: either use PATCH_SITES + PATCHFILES or copy under files/ directory + document origin.
Dropping a quick note to inform you I have a working patch based on the debian ones.
I'll commit this update in a little while.
A commit references this bug:
Date: Mon Jan 2 22:41:15 UTC 2017
New revision: 430414
Modify amide port to use ffmpeg 3.x
Actual patch is a mix of work from subitter and my modifications
based on debian patch from 
While here, fix the DCMTK option.
Submitted by: jbeich
Obtained From: https://anonscm.debian.org/viewvc/debian-med/trunk/packages/amide/trunk/debian/patches/libav10.patch?view=markup&pathrev=16327 
Thanks for your input!