Thanks to this offloading-the-encoding-to-the-GPU, OBS can encode video as it's shot (say, of what you're doing on your desktop, including desktop sound effects, and including you narrating into your microphone as you go), and the file is saved right at the time you end the recording (no matter how long the video clip was).
#Minitube player code
And it was apparently really hard to code (after watching an interview with the OBS lead developer on the Linux Action Show, but I can't find that episode to link to, sorry). I think there is one really noteworthy, awesome app in the i386/i686/amd64 world, which does this offloading (of video encoding) to the GPU, which is OBS. The developers might be thinking "let's just allow the CPU to do the brute force work for us, which will make our jobs as developers much easier". Perhaps there is little motivation in the i386/i686/amd64 world (to painstakingly offload encoding/decoding to the GPU), since the CPU is so powerful. In fact, the use of HW acceleration for video is not very common yet on most desktop i686 systems, but much more common in the "ARM world". Why is it such an uphill battle for Raspbian/Debian/Linux/Open Source developers on ARM, when it comes to multimedia? I ran into many comparable multimedia woes once I painstakingly installed Debian Jessie onto my 2012 Samsung Chromebook (replacing ChromeOS). It would seem the ARM architecture seems to have some sort of multimedia "curse" on it (when using any Linux Distro, ignoring Android/ChromeOS/ChromiumOS here). ALSA (where most sound-reliant apps depend on the newer PulseAudio, but only apps that support the older ALSA have any good odds of having sound work at all). What is it with the ARM architecture, whereby it seems to be so "allergic" to multimedia applications in general? I know a similar major annoyance exists when it comes to PulseAudio vs. OK, can somebody please explain why video hardware acceleration has to be built-in on an app-by-app basis on the Pi (or on any ARM SBC, it would seem)? I'm much more accustomed to how things work on the i386 or amd64 architectures, where once you get x.org working with hardware acceleration whatsoever, then any and all x.org-reliant apps gain hardware acceleration (which want it). Fruitoftheloom wrote:OmxPlayer is the only Media Player Hardware Accelerated.
0 kommentar(er)
