RBO2

11 ms·

1.
by RBO2 11mo ago
These are good points but no name is ever perfect. Just felt that secc was more memorable and would offer more levarage to this great project :-)
2.
by RBO2 11mo ago
Why not call it secc ("sexy") ?
3.
by RBO2 2y ago
Correct. Progressive MP4 also do the trick. Many open-source tool such as ffmpeg (generalist), gpac (specialized in this and leveraging ffmpeg), etc. in the area.
4.
by RBO2 3y ago
I love the idea of static recompilation. It is a promising way to make statically linked code more reusable/sustainable!
5.
by RBO2 8y ago
I don't know who downvoted you but you're correct. The point is that most devices embed an HEVC hardware decoder.
6.
by RBO2 8y ago
I agree with you but hey JPEG also had its own patent issues ( https://en.wikipedia.org/wiki/JPEG#Patent_issues ).
7.
by RBO2 8y ago
HEIF (based on HEVC and support on MacOS/iOS + Android + Windows) is already way better than JPEG. It also provides HW acceleration. HEIF is made by MPEG. HEIG is extensible (see AVIF fusing the AV1 royalty-free codec). Also an applica
8.
by RBO2 8y ago
How different is this from Chromium and Chrome?
9.
by RBO2 8y ago
Note that this is a Apple requirement for HLS. Most people don't realize that the GOP size doesn't impact the latency, but it impacts start-up time.
10.
by RBO2 8y ago
> I've heard from colleagues that this won't be possible with DASH due to the switch to fMP4 format. That's incorrect. With DASH the latency depends on the fragment duration, not the segment duration. You can start sending
11.
by RBO2 9y ago
I think they're almost there in two ways. 1) is https://github.com/gpac/gpac/issues/790 . 2) is to extend FFmpeg to include the MP4Box muxer: http://www.gpac-licensing.com/signals/
12.
by RBO2 10y ago
Also I use ccache on all my projects. Rebuilds times are now at 10s for a 50 kloc project.
13.
by RBO2 10y ago
Unfortunately these codecs still have a few important issues ( http://www.gpac-licensing.com/2016/07/12/vp9-av1-bitstream-f... ). I wish AV1 can fix those but they want to go for such a tight timeline...
14.
by RBO2 10y ago
That's mostly partial acceleration. Chips now support a lot of codecs. And aside H264/AVC chips makers cannot afford to use so much hardware surface for codecs that are not so popular.
15.
by RBO2 10y ago
Agreed. Some opponents of DRMs say this is the beginning of the end of open computers. We've heard recently about the Intel Management Engine. On the other hand, almost all DRMs were broken because the content is available in clear: h
16.
by RBO2 10y ago
You're right, I meant "contributors". It is not only a question of money: these companies can dedicate people to lead the standardization tasks and push their own interests. That's mostly visible at MPEG with patents (ye
17.
by RBO2 10y ago
Agreed. That's one of the reason why this initiative stalls. However the back idea is to standardize a DRM protocol that would be accepted by the copyright owners and that's a step in the right direction.
18.
by RBO2 10y ago
> the organizations that develop the most influential browsers do The problem here is that 3/4 browser makers are also DRMs makers (Apple, Microsoft, Google) and are also the biggest W3C donators.
19.
by RBO2 10y ago
W3C did this move because its biggest sponsors are the DRM makers (Google, Microsoft). To make it acceptable they made it optional. But in practice all major browsers implemented it. The right answer is now to standardized the W3C CDM black
20.
by RBO2 10y ago
These area are huge. Switzerland is 41,285 km^2, Belgium is 30,528 km^2, The Netherlands is 41,543 km^2.
21.
by RBO2 10y ago
The main question is: who pays to make the standards? W3C's biggest sponsors are corporate companies such as Google or Microsoft. It gives these companies a lot of weight.
22.
by RBO2 11y ago
> Scott Meyers has written lots of good stuff on how to use C++ properly. Scott Meyers "retired" from C++ in December 2015 ( http://scottmeyers.blogspot.fr/2015/12/good-to-go.html / https:/&
23.
How Google Works book review(gpac-licensing.com)
1 points by RBO2 11y ago|0 comments
24.
by RBO2 11y ago
Yes that's exactly what it is about! Unfortunately, our current result shows that it still requires much time to model the spec correctly. Any help appreciated, my contact is available on the message above :)
25.
by RBO2 11y ago
Thanks! I'm contributing to an open-source project where we do a lot of standardization (including MP4). We're trying to improve the parser generation by using a model from the specification. We even have some funding for this. I&
26.
by RBO2 11y ago
Very interesting. How can we get more info on this? Is there any public code or product out there?
27.
by RBO2 11y ago
Why wait for Rust when D is already there?
28.
by RBO2 11y ago
It is not a hasard to have this kind of laws in France. France hasn't known dictatorship for long. French representatives don't know what a Stasi-like security state would look like. It would be harder to have such a law in German
29.
by RBO2 12y ago
+1 LLVM is a background topic for me. Your newsletter is both informative and joyful on my Monday morning.
30.
A 10 year multimedia OSS to stream your videos using DASH(gpac.wp.mines-telecom.fr)
2 points by RBO2 13y ago|0 comments

More ›