On 02/02/11 00:55, Kieran Kunhya wrote: > See http://x264dev.multimedia.cx/archives/286
ooh *awesome*. > You could even make the application talk to the 3G driver > (possibly by reading /proc/whatever now and then, so that it can adapt > based on the signal strength/type). If there's packet loss you can also > use periodic intra refresh mode which will give you some error > resiliency. I'd recommend also using UDP because 3G latency is pretty > rubbish. There's a slice-max-size option which means you could put a single > H.264 slice inside a UDP packet, though your decoder will have to support > doing this. Yes. This is a good plan. I was hoping there was something slightly more developed already but this is the best answer I've had so far across several lists and has provided considerable food for thought. :D > (And if you really wanted to go the full shebang you could have a main > receiver communicate with the transmit server to invalidate reference frames > which the decoder didn't receive...) indeed. Thanks again! :D - Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html. Unofficial list archive: http://www.mail-archive.com/backstage@lists.bbc.co.uk/
