Stas Oskin wrote:
[...]
> The number of 90000 is specific to RTP, or it's a generic one? This
> could answer me on another issue described below.
The time base for the various RTP payloads is defined in the RFCs
describing the payloads. All the RFCs for all the video payloads I've
seen use 90000.
But in general different file formats use different time bases.
[...]
> Ok, the new issue is that when I wrote the timed frames to disk
> (rather then streaming them, as I hoped it would fix the frame rate
> issues for recorded files too), I got about 5 seconds of video
> recorded as 12 hours. The first picture actually didn't change for the
> entire clip. Moreover, VLC reported the frame rate as 0.003055.
Which file format did you use? Maybe you set the wrong time base?
When using av_write_frame(), you have to use the time base from the
AVStream you are writing to.
> Any idea if the RTP timing method is good for recorded files as well?
What do you mean with "RTP timing method"? When writing to files, you
do not have to respect any particular timing, but you can write frames
as soon as possible. You just need to properly set the timestamp values
in the AVPacket. See output_example.c::write_video_frame for details.
> If not, what are the methods there to deal with changing frame rate?
I'd suggest to start by writing the file without changing the frame
rate: you just need to convert timestamps to the correct time base.
Again, have a look at output_example.c
Luca
_______________________________________________
libav-user mailing list
[email protected]
https://lists.mplayerhq.hu/mailman/listinfo/libav-user
