search for: 18sec

...e is nothing to do. I am afraid my timings speak for themselves: CP-A MAKE local disk < 5sec < 0.3sec NFS (100MBit) 55sec+-2sec < 2sec glusterfs (I) 4m29sec 17sec glusterfs (II) 4m05sec 18sec (I) unpatched fuse.ko, (II) patched fuse.ko, both over the same network as NFS. Note that in (II) the modified kernel module was used with the default (distribution provided) libfuse library. Measurements are fairly reproducible, i.e., variations are at most +- a few seconds. As you can see from...

Hi there Thanks Thomas. I was hoping to avoid remuxing as my objective is to run an extremely lightweight server. Just tested and the CPU runs between 9% and 23% for a lecture of 90 minutes - took 18sec. Yes it's a lightweight server, but like I said, that's the objective, and quite a nice challenge :-) CPU = cost and if you have to remux for 1000 clients in a day, integrity of live streams currently running are at risk. Going to put some more thinking into it. *You mentioned:* "Does...

Dear all I am streaming live with webm with ffmpeg to icecast 2.4.2. After the stream ends, I am unable to determine the duration of the file using ffprobe or mediainfo. Not sure but it seems that this has to do with headers? Should icecast be writing the duration into the header or should this somehow be passed from ffmpeg? The requirement is really to determine the duration of the streamed

Dear all I am streaming live with webm with ffmpeg to icecast 2.4.2. After the stream ends, I am unable to determine the duration of the file using ffprobe or mediainfo. Not sure but it seems that this has to do with headers? Should icecast be writing the duration into the header or should this somehow be passed from ffmpeg? The requirement is really to determine the duration of the streamed