Raise your hand if you have worked hard building an honest product that does what it says, only to see another business rise up to claim the same thing but based on smoke and mirrors. Must be an age-old trick, maybe akin to the octopus pretending to be a plant so it can catch prey, or the angler fish's glowing trap in the dark.
I've also seen Source-Nexus, that has plugins for Pro Tools as well as VST/AU, and you can make multiple named drivers. It would work pretty well with Loopback it seems.
Currently in the mobile space everyone is behind at least one double-NAT at least, and you can order business level access for your wireless data account and get an IPv4 address allocated to you. AT&T does this for a single $500 fee for example, Sprint as a monthly $3 fee. I imagine this will become common with ISPs - you'll need to upgrade to a gaming/business class in order to make use of port-forwarding etc and for everyone else, some programs will cease to work or not connect as quickly/easily.
And we can't switch to IPv6 ourselves? This this problem need to accelerate user switching (even if just the advanced users) or switching at the ISP level?
Chrome supports its own streaming method, MPEG-DASH with H.264 which is what Youtube runs on where possible. Firefox stated it won't support H.264 on principle (although it does now, for WebRTC). Android supports HLS, as does iOS, out of the box. HLS was designed to supersede RTSP however we also have the equally-ubiquitous RTMP, which Flash supports natively. You can get an HLS stream via Flash with an add-on to some clients so now this will work on IE, Chrome Firefox, and there are also some custom, proprietary clients out there for h.264/HLS. It's not a pleasant ecosystem right now..
- Chrome (and other browsers) support MPEG-DASH via javascript through the Media Source Extensions (MSE) (which Safari actually supports[1])
- Firefox does not "bundle" H.264 (because of licensing) but has recently supported it where the OS provides it[2].
- HLS and MPEG-DASH are fairly similar in theory, but in practice HLS requires complete (with header/metadata) chunks whereas MPEG-DASH can "arbitrarily" chunk a video file and just feed into a MSE video stream. Both work with manifest files detailing different resolutions/qualities and chunk sizes + offsets.
Firefox supports H.264 via system codecs, and supports MPEG-DASH as of version 41 (currently beta, will be stable in a few weeks). MPEG-DASH is a more open standard, and has better support for adaptive bitrate streaming, so I think it's likely to become the defacto standard in the future. It's fairly new so isn't supported everywhere yet, but it's getting there, and seems to have a lot more industry support than other options.
and the code is better than I expected from a commercial project, it even uses may_alias properly. I wonder why the decoder doesn't support CPU multithreading, though? Slice threads are pretty simple to add.
>every couple years, go off and do something completely different
You mean, like take a vacation? You are saying exactly the same thing but with the time-scale different. I agree on that: work hard for 10 months, no days off. 2 months completely out of the office. But that assumes excellent health and no family.
Ah yes, Florence Foster Jenkins being the famous example [1] who was wealthy and hired Carnegie hall for a concert, in spite of being tone deaf thought she would sing Mozart's difficult Queen of the Night aria: and record it. [2]
She is famous for saying "people may say I can't sing but no one can ever say I didn't sing".
Media players: browsers don't have native support for H.264 over HLS or RTMP, and MPEG-Dash seems native to Chrome only. If the browsers could accept these natively, this would certainly speed flash's demise. Until then, what are the alternatives?
