[CinCV TNG] H.264 export broken - users should be aware

Einar Rünkaru einarrunkaru at gmail.com
Thu Oct 22 13:53:21 CEST 2015


On 22 October 2015 at 14:39, igor_ubuntu <sitelve at gmail.com> wrote:

> I propose to consider a specific examples.
>
> 1-
> Suppose that company source.ffmpeg.org released a new stable version of
> the ffmpeg - 2.9-stable.
> At this time user  goes and removes the directory of source codes
>  /home/user/builds/cin-cve (then he does git clone ... )
> or
> removes ffmpeg directory from cinelerra sources (
> /home/user/builds/cin-cve/ffmpeg )
>  In this case (as you says)   the current version of ffmpeg is cloned by
> configure. Ok.
> But what version is cloned (in this case) - 2.8.*-stable or 2.9-stable ?
>

When this happens after needed changes in cinelerra are done and user does
git pull in the cin-cve configure clones 2.9.x

When cinelerrra has not needed changes configure clones 2.8.x


> 2-
> Suppose that company source.ffmpeg.org released a new stable version of
> the ffmpeg - 2.9-stable.
> At this time there were changes in сve-git
> User makes  git clone ..   ./autogen   ./configure
> User does not remove directories /home/user/builds/cin-cve/ffmpeg
> Herewith 2.9-version is not cloned. User works with 2.8*
>  Do I understand correctly?
>

Yes.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cinelerra-cv.org/pipermail/cinelerra/attachments/20151022/82ee7f4b/attachment.html>


More information about the Cinelerra mailing list