-
Ah, I can answer some of my own questions after taking a look at the stream specs. Seems to be a roughly 250kbps VBR stream using H264 video (that accounts for the good picture quality). I personally find the 60 fps and 48000 Hz stereo AAC to be overkill on mobile devices... both can probably be lowered without any noticeable difference if you wanted to save bandwidth, unless it's for compatibility purposes. Whatever encoder you're using works pretty well- very little movement pixelation. I'm guessing it was processed with multi-pass. And doh! My videos on demand are webhosted, so of course require large buffer times. Obviously you're using an RTSP server, so don't have that issue
Should have realized that, I wasn't thinking. A proper server is always better; as you said, fast forward and rewind work.
The 2G here is quite miserable. Supposedly it's Edge, but on a good day it's nearly twice dial-up speed. Even audio streaming is difficult. I wish that Verizon offered the Bold 9700 so I could switch from T-Mobile to a decent carrier.
Do you have any plans to offer live streams?08-28-10 05:20 AM - Sorry, maybe my app was wrong. I just guesstimated the bitrate based on the reported high and low bandwidth peaks. I did see your protection system, which is very important. I've noticed other stream services switching to similar methods to avoid unauthorized sharing of rtsp links. While it might not be important to end-users, from a host's point of view it's essential for protecting the content value (not to mention bandwidth).
150k is really impressive. I started playing around with low-bandwidth streaming years back as a hobby (probably silly and outdated now, but as I did this half a decade ago, it was pretty cutting-edge). About six months after that, I was using an x264/AAC NSV concoction at 200k. Amazing results for its day, but of course back then it wasn't nearly mainstream enough for widespread mobile use.
Audio streams in ACC are very nice- even 32k or lower streams can sound quite acceptable. Things have sure changed from the days of MP3- or heaven forbid, Real Media
08-29-10 01:19 PM - We are playing with the servers at the moment and I am going to make some 2G tests later as soon the service is running. At the moment we are focused on 3G and up but I know what pain 2G can be (I have T-Mobile too) but I am always happy with Sprint or Verizon in these areas.
We have some RTT1x Networks (2G) that will support the stream. The major problem is the bitrate on EDGE vs. 1x, which supports higher speeds (on a continues level)
We let the network find its optimum speed but require a baseline of 150kbs.
This will be quite important for the end user as we can work with very low prices if we don't loose money due to piracy. We have to pay for content and need to make sure the bottom line is okay as well.I did see your protection system, which is very important. I've noticed other stream services switching to similar methods to avoid unauthorized sharing of rtsp links. While it might not be important to end-users, from a host's point of view it's essential for protecting the content value (not to mention bandwidth).
I started in 2006 with streaming and we started with 2G streaming and early 3G streaming. Good times... but I don't miss 48Kbs streams. Look at MobiTV, they still use 128Kbs to offer their service.150k is really impressive. I started playing around with low-bandwidth streaming years back as a hobby (probably silly and outdated now, but as I did this half a decade ago, it was pretty cutting-edge). About six months after that, I was using an x264/AAC NSV concoction at 200k. Amazing results for its day, but of course back then it wasn't nearly mainstream enough for widespread mobile use.
We use higher audio quality than 32k just because it completes the audio/visual experience.Audio streams in ACC are very nice- even 32k or lower streams can sound quite acceptable. Things have sure changed from the days of MP3- or heaven forbid, Real Media 08-30-10 01:06 PM
