[Koying]

We need to decide whether to render the GUI as half-SBS, half-TAB, full-SBS or full-TAB.
full-SBS/full-TAB is pretty expensive (16M for the framebuffer, and on Pi it is triple buffered). It would also reduce the gui FPS in this mode, so currently we use "half" modes on Pi.

HTAB is probably the most compatible. Full requires frame packing if not mistaken, and TAB is better for passive 3D TV.

It would be nice to detect 3D support (through ffmpeg) before playback starts, so matching filenames is not required and file is automatically identified.
Automatically detecting if file is left-right or right-left would be useful. It appears the MVC bitstream doesn't contain that information, but I suspect it is somewhere within ISO.

I've got an embryo of an ffmpeg patch with detects MVC based on the h264 NAL encountered (14, 15, 20 -> MVC).
I would somewhat assume that the eye order is always the same for BD3D, isn't it?

E.g. ssif stream looks like:
[ R R R R R R R R ] [ L L L L L L L L ] [ R R R R R R R R ] [ L L L L L L L L ] [ R R R R R R R R ] [ L L L L L L L L ]
L : left eye + audio + subs
R: right eye

After reading:
[ R R R R R R R R ] [ L ]
You can produce [ LR ], and as each L picture is parsed you emit a new [ LR ]

We believe this new [ LR LR LR LR LR LR LR LR ] stream will be handled by ffmpeg's mt2s parser.

Do you mean the sequence (I assume those are packets) is
[ R1 R2 R3 R4 R5 R6 R7 R8 ] [ L1 L2 L3 L4 L5 L6 L7 L8 ]
and that
[L1 R1] [L2 R2] ... has to go out of the demuxer?