Open GoogleCodeExporter opened 8 years ago
Similar problem. The receiver input stream starts like this:
00 00 00 00 66 74 79 70 33 67 70 34 00 00 00 00 69 73 6F 6D 33 67 70 34 00 00
00 18 00 06 2E 08 66 72 65 65 3F 3F 3F 3F 6D 64 61 74 01 48 20 06
....ftyp3gp4....isom3gp4........free????mdat.H .
The word 'free' is at location 0x32, and the parser thinks that is a 4-byte int
containing the frame-size.
'free' = frame_size: 7497061 =/
Original comment by saama...@gmail.com
on 27 Feb 2011 at 9:37
BTW,
Google Nexus One
Gingerbread - CM7
Original comment by saama...@gmail.com
on 27 Feb 2011 at 9:38
Hi
Do you have a fix for this problem? I would really appreciat your help!!
Original comment by xico.del...@gmail.com
on 25 Apr 2011 at 4:05
Just edit buffer length. note, that you need to edit length in several places.
Original comment by alexe...@gmail.com
on 25 Apr 2011 at 4:20
Thans for your replay. Can you provide me more details on where to change? And
how can I know which is the correct buffer length?
Thanks!
Original comment by xico.del...@gmail.com
on 25 Apr 2011 at 5:09
After some more debugging, i've found that after reading the 32 bytes header,
the next 8 incoming bytes are 0-0-0-0-[mdat].Isnt this an mdat atom without
size? (this, is, still not calculated).I've been looking around the web, and i
know the encoder first writes an empty size header, and later, when the size is
known (ie, the recording is stopped), rewrites it (if output is sent to a
file).How is this managed in this project?
Original comment by dash...@gmail.com
on 29 May 2011 at 11:20
what is the appropriate buffer length for galaxy S? Thanks
Original comment by hicham.b...@hotmail.com
on 13 Jun 2011 at 4:10
the same problem,
pls
thanks
Original comment by rangfeng...@gmail.com
on 23 Sep 2011 at 9:49
Similar problem. The receiver input stream starts like this:
Original comment by ljchat...@gmail.com
on 7 Mar 2013 at 2:27
Attachments:
Original issue reported on code.google.com by
wil...@wjsp.nl
on 20 Feb 2011 at 9:55