Maybe my question is not correct. If both encode H.265 but I thought the
performance ability (to create compression ratio) should be the same or at
least comparable.
That means CUDA version is only for some purposes and traditional open
libx265 version for others? I guess, the CUDA is only for str
Different implementation of same standard should not behave way different I
assume, or not have same features or performance (at least).
Could you describe a little more or at least give source?
What are you suggesting by different implementation exactly then?
I guess from your short message tha
Am 05.08.22 um 17:02 schrieb jatmvp ctf:
I have problem with understanding why my ffmpeg with nVidia features (as
v:c hevc_nvenc) generate way larger file in comparison to libx265
because it's a different implementation
___
ffmpeg-user mailing list
Hello,
I have problem with understanding why my ffmpeg with nVidia features (as
v:c hevc_nvenc) generate way larger file in comparison to libx265.
For the case I tried to reencode H.264 video and MP3 to AAC with merging it.
video.mp4 is H.264
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'video.mp4':
On Fri, 5 Aug 2022 at 13:55, Christian wrote:
> Hello,
>
> sorry, I wasn't specific enough with my last mails. I try again and be
> more specific:
>
> I like to stream to Youtube. The source is my Outdoor-Camera which is
> connected via an antenna to my Router. The camera sends an h.264 encoded
>
Hello,
sorry, I wasn't specific enough with my last mails. I try again and be
more specific:
I like to stream to Youtube. The source is my Outdoor-Camera which is
connected via an antenna to my Router. The camera sends an h.264 encoded
RTSP-Stream. FFmpeg v4.1.9 runs on a Raspberry Pi4 with Rasp
