sorry, i thought i was replying to the listserv. I have not been on one in
years.
I will get my stuff together and try again.
On Mon, Jan 31, 2022 at 3:10 PM Michael Koch
wrote:
> Am 31.01.2022 um 05:03 schrieb Mark Filipak (ffmpeg):
> >
> > During the past year, I've developed a set of true st
Am 31.01.2022 um 05:03 schrieb Mark Filipak (ffmpeg):
During the past year, I've developed a set of true stream primitives
that are object oriented (frames, pictures, ...), plus a notation to
describe encodings and "mechanical" manipulations that are useful and
that are fairly easy to read an
On 2022-01-31 03:38, Michael Koch wrote:
Am 31.01.2022 um 05:03 schrieb Mark Filipak (ffmpeg):
During the past year, I've developed a set of true stream primitives that are object oriented
(frames, pictures, ...), plus a notation to describe encodings and "mechanical" manipulations that
are u
>
>> Writing the docs took a long time and lot of work. Is there any appetite
>> here for them?
>>
>
> I'd like to read it.
>
+1
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit li
Am 31.01.2022 um 05:03 schrieb Mark Filipak (ffmpeg):
During the past year, I've developed a set of true stream primitives
that are object oriented (frames, pictures, ...), plus a notation to
describe encodings and "mechanical" manipulations that are useful and
that are fairly easy to read an
On 2022-01-30 20:03, Mark Filipak (ffmpeg) wrote:
During the past year, I've developed a set of true stream primitives
that are object oriented (frames, pictures, ...), plus a notation to
describe encodings and "mechanical" manipulations that are useful and
that are fairly easy to read and und
During the past year, I've developed a set of true stream primitives that are object oriented
(frames, pictures, ...), plus a notation to describe encodings and "mechanical" manipulations that
are useful and that are fairly easy to read and understand. Can the notation be used as a frontend
t
