On Thu, 18 Aug 2016, Nicolas George wrote:
Le decadi 30 thermidor, an CCXXIV, Marton Balint a écrit :
I remember some other advantages of flushing in blocks as well, which made
me suggest it to Jan:
- It is a good thing if the consumer knows that there was a packet
discontinuity, it can decid
Le decadi 30 thermidor, an CCXXIV, Jan Sebechlebsky a écrit :
> I am not sure if I understand this. Do you mean thread queue function which
> would set
> certain flag that the queue should be flushed and flushed the queue at
> certain point in time (next receive call?)?
That is a bit too specific
Le decadi 30 thermidor, an CCXXIV, Marton Balint a écrit :
> I remember some other advantages of flushing in blocks as well, which made
> me suggest it to Jan:
>
> - It is a good thing if the consumer knows that there was a packet
> discontinuity, it can decide what to do. If you drop packets earl
On 08/16/2016 01:05 AM, Jan Sebechlebsky wrote:
On 08/15/2016 11:50 PM, Nicolas George wrote:
+
+if (just_flushed)
+av_log(avf, AV_LOG_INFO, "FIFO queue flushed\n");
+
+ret = av_thread_message_queue_recv(queue, &msg, 0);
[...]
+if (ret < 0) {
+
+if (!fifo->overflow_flag)
+fifo->overflow_flag = overflow_set = 1;
+pthread_mutex_unlock(&fifo->overflow_flag_lock);
+
+if (overflow_set)
+av_log(avf, AV_LOG_WARNING, "FIFO queue full\n");
+ret = 0;
+goto fail;
Can you explain w
On 08/15/2016 11:50 PM, Nicolas George wrote:
L'octidi 28 thermidor, an CCXXIV, sebechlebsky...@gmail.com a écrit :
[...]
+s@item recovery_wait_streamtime @var{bool}
^
Strange.
Sorry, that is obviously a typo. Strange thing is it had not produced
any kind of warning/error.
[...]
+#def
L'octidi 28 thermidor, an CCXXIV, sebechlebsky...@gmail.com a écrit :
> From: Jan Sebechlebsky
>
> Signed-off-by: Jan Sebechlebsky
> ---
> Changes since the last version of the patch:
> - Fixed documentation (apart from the Marton's suggestions I've
>also changed example, since it used blo
From: Jan Sebechlebsky
Signed-off-by: Jan Sebechlebsky
---
Changes since the last version of the patch:
- Fixed documentation (apart from the Marton's suggestions I've
also changed example, since it used block_on_overflow option
from the earlier version of patch)
- Changed max_recovery_
