11–20 of 66 posts
> native aptX and aptX HD encoder and decoder Sounds great. Is there any meaning to Linux computers that don’t support aptX? Also I am wondering how it is posssible to include the aptX codec since its license term is against GPL?
> native aptX and aptX HD encoder and decoder Sounds great. Is there any meaning to Linux computers that don’t support aptX? Also I am wondering how it is posssible to include the aptX codec since its license term is against GPL?
But FFmpeg have a clean-room implementation, based on the (expired) EP0398973B1 patent and from reverse-engineering the binary library.
> native aptX and aptX HD encoder and decoder Sounds great. Is there any meaning to Linux computers that don’t support aptX? Also I am wondering how it is posssible to include the aptX codec since its license term is against GPL?
https://patchwork.ffmpeg.org/patch/5879/
> Aptx support for linux with FFMpeg and bluez-alsa
https://github.com/Samt43/BluetoothAPTXForLinux https://github.com/Arkq/bluez-alsa/issues/92
I would really like to test AV1 with it.
> native aptX and aptX HD encoder and decoder Sounds great. Is there any meaning to Linux computers that don’t support aptX? Also I am wondering how it is posssible to include the aptX codec since its license term is against GPL?
> The encoder was reverse engineered from binary library and from EP0398973B1 patent (long expired). The decoder was simply deduced from the encoder. https://patchwork.ffmpeg.org/patch/5879/ > Aptx support for linux with FFMpeg and bluez-alsa https://github.com/Samt43/BluetoothAPTXForLinux https://github.com/Arkq/bluez-alsa/issues/92
Lots of hardware acceleration: - Intel QSV-accelerated MJPEG encoding - NVIDIA NVDEC-accelerated H.264, HEVC, MJPEG, MPEG-1/2/4, VC1, VP8/9 hwaccel decoding - Intel QSV-accelerated overlay filter - OpenCL overlay filter - VAAPI MJPEG and VP8 decoding - AMD AMF H.264 and HEVC encoders - VideoToolbox HEVC encoder and hwaccel - VAAPI-accelerated ProcAmp (color balance), denoise and sharpness filters
Confused, as I've been using ffmpeg for HEVC NVDEC already...
Lots of hardware acceleration: - Intel QSV-accelerated MJPEG encoding - NVIDIA NVDEC-accelerated H.264, HEVC, MJPEG, MPEG-1/2/4, VC1, VP8/9 hwaccel decoding - Intel QSV-accelerated overlay filter - OpenCL overlay filter - VAAPI MJPEG and VP8 decoding - AMD AMF H.264 and HEVC encoders - VideoToolbox HEVC encoder and hwaccel - VAAPI-accelerated ProcAmp (color balance), denoise and sharpness filters
>NVIDIA NVDEC-accelerated H.264, HEVC, MJPEG, MPEG-1/2/4, VC1, VP8/9 hwaccel decoding Confused, as I've been using ffmpeg for HEVC NVDEC already...
Awesome, initial AV1 support!
I was trying to do something the other day and couldn’t figure it out, if anyone has any ideas.
The end goal is to provide a set of video files, with time stamps for each, splicing them into one file while removing parts I don’t want.
That is straightforward enough, as long as you’re willing to re-encode the whole file. Otherwise, it seems like ffmpeg is restricted to make cuts at key frames.
It’s rare for the key frame to be placed at the exact spot I would want to make a cut, so the section of the video around the cut would need to be re-encoded. Ideally that would be the only part hat is re-encoded - everything else would be a a straight transcode from key frame to key frame.
I believe this is called ‘smart rendering’, and the pages I could find in the past said ffmpeg isn’t really suited for it, or it’s very difficult.
Does anyone know if that has changed recently, or have found a way to do it?