[Adam Langley]

Hi Reuben,

Thanks for the advice – I have made some progress.
I have ditched OpenRTSP for the time being, and have appended ?tcp to the RTSP url in ffmpeg – this seems to work correctly as far as not getting video corruption (which happens if ffmpeg attempts to use UDP).
I compiled all the software on my macbook pro – and copied the binaries to an Atom machine – so the code is exactly the same.
using a straight “ffmpeg -t rtsp://xxxxx output.mp4″ (with additional transcode options) it works perfectly on my macbook pro – but on the Atom computer, it only outputs 2fps, then dies after 50 or so frames.

The only difference I can see is on this…
Macbook: [libx264 @ 0x101027800] using cpu capabilities: MMX2 SSE2Fast SSSE3 Cache64
Atom: [libx264 @ 0x10110ec00] using cpu capabilities: MMX2 SSE2Fast SSSE3 Cache64 SlowCTZ SlowAtom

So, I assume that libx264 has some significantly different code-paths resulting from “SlowCTZ” and “SlowAtom”.

What can I do to disable these ‘cpu optimizations’? I dont care if it consumes twice as much CPU… if it works!

Thanks again!