Allows building with the upcoming Libav 10 release.
@Anton Khirnov (elenril), committed to master with some own modifications to the patches. Mainly to solve compilation error with older FFmpeg. Please give it a try with latest git and submit more patches if something is still broken for you :)
@Brecht Van Lommel (brecht), i successfully compiled blender with own changes to the patches which were partially based on your one. But it still might be something missing for OSX or so. Please also give it a test compilation and let me know if something is to be tweaked.
@Joerg Mueller (nexyon), pretty much sure you'll want to switch to newer API in audaspace anyway. Not so difficult to backport the changes to your repo nyway.
At this point i'll close the task since all the patches are pushed.
Hi, sorry for replying late, but I had a very stressful exam week. Anyway, still I'd like to be asked before stuff like this gets committed. The github audaspace version https://github.com/neXyon/audaspace has this newer ffmpeg API changes for over a month already, so there wouldn't have been a need to recode everything actually and as the implementation here is somewhat different the code keeps diverging. I should probably move audaspace from intern to extern soon, maybe then people will stop committing to it just like that, as it's already the second time this happened.
@Joerg Mueller (nexyon), even if audaspace is in extern/ it is to be maintained and asking to review rather simple compilation error fixes which will take week is not the way to go.
Don't see the issue with local commits either -- if you're moving audaspace to mainly host on github it should be matter of running a script which will re-bundle the whole audaspace into blender (the same exact way as happens for egen, libmv, ceres, carve..).
With those commits and CC you do know what to look into when updating audaspace. You could either use the same patches in your upstream, or replace local changes with upstream version. Don't see any reasons to yell about commits really.
How could a compilation error happen suddenly after changing nothing for a while? The only possible way this happens is through a library update, that could have been discussed first? Anyway the point here was that the code that supports a newer ffmpeg version already existed for a while and didn't have to be recoded again and now you want to add even more work, having to look at which code got changed in blender and update the github code again? That doesn't make sense to me, sorry. Also your suggestion to just run a script to keep github and blender audaspace in sync shows that you might not have read my original email, where I asked people to talk to me before changing code and that the github audaspace is using C++11, being the reason why I have to manually sync them at the moment. I didn't mean to be offensive in any way, but you accusing me of yelling kind of is. :-(