For 720p I would have to frame-reduce 1080i downconverts (and probably 720p60 originals) to 23.976 fps. 60i (for 1080 and SD) means 29.97 frames which could be 24p pull-downed, 29.97 interlaced and 29.97 progressive with pulldown flag set on h.264 stream. Apparently x264 could set pulldown flag with "--pulldown 23" (might not be fully supported in hbcli) and all streams need to be encoded with --aud and --nal-hdr (the later again might not be supported in hbcli), but overall it looks like AVCHD/BD is still being in its early days after a year of hacking... Additionally, QT cannot play 60i streams but could play 23.976 with pull-down disregard pull-down flag. Thus overall AVCHD/BD is good only for 720p24 and in order to play on both BD standalone and Apple TV everything need to be frame-reduced which is bad. (Theoretically, I could store 720p60, but at 4+xT even on Q6600 and 5Mbps bitrates it ain't worth it).
So there you have it - there is absolutely no reason to encode BD compliant streams and thus BD brings nothing new to viewing HD at home and solution remains the same - encode for storage on NAS and view thru networked TV appliance. Welcome back Apple TV.
Before completely giving up on BD and AVCHD however still try couple things:
- Try Nero Vision 8 to see if it would try to transcode my 720p24. If it would try another 720p24 encoded with --detelecine -r 23.976 -x pulldown=23:aud=1:nal-hdr=1
- Try Nero with 720x480@24p with pull-down and see if motion jerks because of the frame-reduction on say Seige or 60_seconds.
- Try using seek and frames with HB.