At Kulabyte we have an encoder that delivers both RTMP Flash and iOS HTTP streams with H.264/AAC codec. I am able to send RTMP to a Wowza server to produce iOS HTTP and then play that back on the Roku box - both as a single stream or as adaptive streaming with a .smil file. If I try to play the exact same stream (i.e. same H.264/AAC stream data) on the Roku using our native HTTP served by an Apache server or Akamai, the streams do not play at all - sometimes the debug message will pop up saying "Playing 1.5Mb stream on your 5Mb connection" and then it goes right back to the menu. I've tested this with a 2.6 firmware as well as 2.8b1158. Also, it is worth noting that iPad and iPhone and Quicktime on the Mac play both the Wowza stream and Kulabyte stream just fine.
I'm wondering if the Roku box is not liking something in the .m3u8 file from the Kulabyte encoder. Below are examples:
The only differences I see are EXT-X-ALLOW-CACHE and the fact that Kulabyte is putting the relative path on the .ts file whereas Wowza is putting no path on the .ts file. Again, the Apple devices play both Wowza and Kulabyte streams fine and we've run our streams through Apple's media stream validator and they are pretty clean.
What's the best way debug this further? Is there a super secret logging capability that will tell me more about what the player does not like?