пн, 20 мая 2024 г., 22:43 Phyllis Smith :
> Also, it was suggested that we (cinelerra-gg) can create different git
>> branch < named, say, "testing" > for "potentially unstable" patches, like
>> current ffmpeg 7.0 patchset and then merge back to main/stable when feature
>> is deemed ready.
>>
>
>
> ... I believe that Andrea uses it frequently also with no new reported issues.
Since you provided the patches I have always used CinGG compiled with
ffmpeg 7. I have not found any problems. I have done rendering,
background rendering and batch rendering without any problems. I have
not done rend
P.S. although there have not been very many users testing ffmpeg 7.0, I
have found no problems with it and I believe that Andrea uses it frequently
also with no new reported issues. I am in the process of outlining a set
of tests to run, i.e. a "test suite", when a library like ffmpeg is updated
b
>
> Also, it was suggested that we (cinelerra-gg) can create different git
> branch < named, say, "testing" > for "potentially unstable" patches, like
> current ffmpeg 7.0 patchset and then merge back to main/stable when feature
> is deemed ready.
>
+2 for testing branch. (wink, wink).
Actually
>Also, it was suggested that we (cinelerra-gg) can create different git
branch < named, say, "testing" > for "potentially unstable" patches, like
current ffmpeg 7.0 patchset and then merge back to main/stable when feature
is deemed ready.
+1 for testing branch.
Best regards,
Andrey
пн, 20 мая
News item at linux.org.ru - because official one just few lines without any
picture :)
https://www.linux.org.ru/news/multimedia/17621213
Also, it was suggested that we (cinelerra-gg) can create different git
branch < named, say, "testing" > for "potentially unstable" patches, like
current ffmpeg
6 matches
Mail list logo
