Hi
Im using the mp4 module quite heavily, and very occasionally (once
every minute or so on a busy website) there is an error written to
error.log and status 500 returned in the access log
[error] 42078#0: *5510811 start time is out mp4 stts samples in …
(mostly this error)
[error] 42072#0: *5524976 start time is out mp4 stsc chunks in …
(sometimes this error)
It happens on different videos and only when ?start is after a certain
time point (different for each video)
Given that the mp4 module works remarkably well on the whole, where
should I look to find the cause of these rare errors? (and what do they
actually mean :))
nginx version: nginx/1.2.9
built by gcc 4.2.1 20070831 patched [FreeBSD]
TLS SNI support enabled
configure arguments: --with-debug --with-http_ssl_module
–with-http_stub_status_module --with-file-aio --with-http_flv_module
–with-http_mp4_module --with-http_geoip_module
–add-module=…/…/…/lua-nginx-module
Given that the mp4 module works remarkably well on the whole, where
should I look to find the cause of these rare errors? (and what do they
actually mean :))
nginx version: nginx/1.2.9
I would suggest you upgrade nginx. Between nginx/1.2.9 and a recent
releases
there are 4 bugfixes in the mp4 module.
On Sat, Jun 22, 2013 at 10:40:53AM +0100, Richard K. wrote:
It happens on different videos and only when ?start is after a
certain time point (different for each video)
Given that the mp4 module works remarkably well on the whole, where
should I look to find the cause of these rare errors? (and what do
they actually mean :))
Messages suggest an attempt was made to seek to a time which isn’t
in media track metadata, thus seek isn’t possible. This usually
happens when time in “start=” is just too big.
Hi
I’ve been able to test a few videos myself and can see it happening
Just to be clear, 99%+ seem to be fine and can seek right up to the end
But on very few, seeking is only possible up to X seconds (X could be at
any point in the video)
To seek after X, the error always happens
However if I watch the video from start to end, it downloads the full
thing and can be watched to the end (the file isn’t truncated)
At this point I suppose it’s either an error while creating the metadata
at the encoder software, or some odd circumstance which nginx doesn’t
like
The question is, which?