My guess would be that 2147483647 is considered acceptable because it is
in range. As an integer it is the maximum possible number in (signed) 4
bytes. Next time round, it will add 1 which will be -2147483648 which is
definitely less than the upper limit - and so it goes on.
My suggestion would be to set the maximum to 2147483646 - which would
give the software a chance to find a number greater than the limit.
On 19/04/18 03:04, quang_openstack wrote:
> Hi everyone,
> I am now working with multifilesink, but the index of file keep increase to
> 2147483647 then index of next file is -2147483648. This this very strange
> because index's rang is "0 - 2147483647".
> Is there any way to limit index???
> For example index is started from 0 and increaseed for each time to 5 then
> it is back to 0 ... (splitmuxsink can do this).
>
> Thank in advance.
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
Locked
