In our project we successfully created stream context from one thread and read packets from separated threadpool. It looks like nothing depends on specific thread.
On Thu, Aug 18, 2022, 14:35 Olzhas Zhumabek < [email protected]> wrote: > > With threads you want parallelism not sequential access so to me it > doesnt make too much sense to have it moved around. > > At the moment I have a task scheduling framework that schedules tasks to > idle threads. The ffmpeg encoding/decoding is thus sliced into tasks and > those get picked up by idle threads. I just wanted to know if I need to > have a deeper look into my code or if accessing AVFormatContext from > different threads (without simultaneous access) is not okay. > > I have a working version that uses only one thread created manually > outside of the framework (thus it ensures that AVFormatContext will always > be accessed from the same exact thread). > _______________________________________________ > Libav-user mailing list > [email protected] > https://ffmpeg.org/mailman/listinfo/libav-user > > To unsubscribe, visit link above, or email > [email protected] with subject "unsubscribe". >
_______________________________________________ Libav-user mailing list [email protected] https://ffmpeg.org/mailman/listinfo/libav-user To unsubscribe, visit link above, or email [email protected] with subject "unsubscribe".
