Does the “support for chunked transfer encoding…” mean I don’t need
the extra “chunkin” module to be compiled and linked-in?
Is there a new list of directives I should switch-over to (replacing the
external, chunkin ones)? Maybe there’s a more thorough list of release
notes, I’m just not sure where they are offhand.
On Tuesday 27 November 2012 19:35:34 AJ Weber wrote:
Does the “support for chunked transfer encoding…” mean I don’t need
the extra “chunkin” module to be compiled and linked-in?
Yes.
Is there a new list of directives I should switch-over to (replacing the
external, chunkin ones)? Maybe there’s a more thorough list of release
notes, I’m just not sure where they are offhand.
There are no special directives at all. It just works.
Thanks Will there be an updated version of the SPDY patch as well?
It looks like patch.spdy-53.txt just needs minor adjustments in
src/http/ngx_http.h and src/http/ngx_http_request_body.c (at least it
applies, compiles and runs in my case after doing so) but I am unsure if
there is anything else behind the scenes which might break it sooner or
later.
Unexpectedly compiling fresh 1.3.9 with nginx_upload_module I’ve met
objs -I src/http -I src/http/modules -I src/mail
-o objs/addon/nginx_upload_module-2.2.0/
ngx_http_upload_module.o
…/nginx_upload_module-2.2.0/ngx_http_upload_module.c
…/nginx_upload_module-2.2.0/ngx_http_upload_module.c: In function
ngx_http_read_upload_client_request_body:
…/nginx_upload_module-2.2.0/ngx_http_upload_module.c:2628: error:
ngx_http_request_body_t has no member named to_write
…/nginx_upload_module-2.2.0/ngx_http_upload_module.c:2687: error:
ngx_http_request_body_t has no member named to_write
…/nginx_upload_module-2.2.0/ngx_http_upload_module.c: In function
ngx_http_do_read_upload_client_request_body:
…/nginx_upload_module-2.2.0/ngx_http_upload_module.c:2769: error:
ngx_http_request_body_t has no member named to_write
…/nginx_upload_module-2.2.0/ngx_http_upload_module.c:2785: error:
ngx_http_request_body_t has no member named to_write
…/nginx_upload_module-2.2.0/ngx_http_upload_module.c:2877: error:
ngx_http_request_body_t has no member named to_write
make[1]: *** [objs/addon/nginx_upload_module-2.2.0/
ngx_http_upload_module.o] Error 1
make[1]: Leaving directory `/root/nginx-1.3.9’
make: *** [build] Error 2
any ideas?
Pawe Marzec
Wiadomo napisana w dniu 2012-11-27, o godz. 15:26, przez Maxim D.:
After I replaced the 3rd party h.264 streaming module with the native
one.I found that there was no sound when playing some of MP4 files with
MP3 audio codec. Is there anyway to pseudo-streaming MP4 files with
H.264/MP3 codec by using the native mp4 module.Or any plan to support
this type of MP4 files in the future ?
After I replaced the 3rd party h.264 streaming module with the native one.I
found that there was no sound when playing some of MP4 files with MP3 audio codec.
Is there anyway to pseudo-streaming MP4 files with H.264/MP3 codec by using the
native mp4 module.Or any plan to support this type of MP4 files in the future ?
Could you try nginx version 1.3.5 or newer ?
Changes with nginx 1.3.5 21 Aug
2012
*) Change: the ngx_http_mp4_module module no longer skips tracks in
formats other than H.264 and AAC.
Thanks Igor,I can pseudo-streaming H.264/MP3 files after update from
1.2.5 to 1.3.9.
Do you plan to back port this change to 1.2.x stable version or i have
to wait for the 1.4.x.
Thanks Igor,I can pseudo-streaming H.264/MP3 files after update from 1.2.5 to
1.3.9.
Do you plan to back port this change to 1.2.x stable version or i have to wait
for the 1.4.x.
Don’t worry, it’s indeed minor adjustments while applying.
It should work as well as with the previous nginx version.
Great, thanks for confirmation. If anyone is interested for reasons of
convenience, I applied the patch to nginx 1.3.9, resolved the rejects
and did a fresh unified diff.
Thank you for the patch. I can pseudo-streaming H.264/MP3 files on 1.2.5
now. But I just noticed that still some of H.264/MP3 files converted by
FFmpeg has no sound even testing on 1.3.9. I can send you a sample file
if you need it.
On Wednesday 28 November 2012 13:45:54 Christoph Schug wrote:
On 2012-11-27 23:32, Valentin V. Bartenev wrote:
Don’t worry, it’s indeed minor adjustments while applying.
It should work as well as with the previous nginx version.
Great, thanks for confirmation. If anyone is interested for reasons of
convenience, I applied the patch to nginx 1.3.9, resolved the rejects
and did a fresh unified diff.
Rejects? Are you sure? Could you show me them? Because I see only some
small offsets and two little fuzz:
On Wednesday 28 November 2012 16:14:16 Maxim D. wrote:
and did a fresh unified diff.
Hunk #4 succeeded at 113 with fuzz 1 (offset 10 lines).
and I wouldn’t be surprised fuzz in one of them will be reject in
another one.
Ok, you’re right, I haven’t been thought that this time the problem
is so serious.
On Wed, Nov 28, 2012 at 07:23:25PM +0900, Sheng.Zheng wrote:
Thank you for the patch. I can pseudo-streaming H.264/MP3 files on
1.2.5 now. But I just noticed that still some of H.264/MP3 files
converted by FFmpeg has no sound even testing on 1.3.9. I can send
you a sample file if you need it.
Yes, please provide links to a couple of sample files which
has problems with streaming.
I am not an expert on nginx, but the streaming of “something (mp3,
h.264, etc)” it’s not indipendent from the content/codec, how to
decode the streaming it’s a client/consumer
aspect, or no?
On Wed, Nov 28, 2012 at 9:54 PM, Valeriano Cossu [email protected] wrote:
Hello sheng,
I am not an expert on nginx, but the streaming of “something (mp3,
h.264, etc)” it’s not indipendent from the content/codec, how to
decode the streaming it’s a client/consumer
aspect, or no?