From: Misha Aizatulin <mihhail.aizatulin@gmail.com>
To: "FFmpeg development discussions and patches"
<ffmpeg-devel@ffmpeg.org>, "Tomas Härdin" <git@haerdin.se>
Subject: Re: [FFmpeg-devel] looking to hire expert for a short project: lossless screen and sound capture 4k@60hz
Date: Tue, 1 Aug 2023 01:24:51 +0100
Message-ID: <0e6228d9-9f68-322d-246f-b564b3f84476@gmail.com> (raw)
In-Reply-To: <273ece4615367af9a87177343085a418ae98ce1f.camel@haerdin.se>
> I would suggest using .kkapture: http://farbrausch.de/~fg/kkapture/
Interesting - I haven't tried .kkapture because I thought that it only works for demos that are
using the API as of when the tool was created - which means a lot of the newer demos won't work with
it. But maybe I'm wrong? I'll poke around.
I tried Capturinha (https://github.com/kebby/Capturinha), but couldn't make it work for lossless
- it might be an easy code change though.
I also tried OBS and almost succeeded. The only remaining problem with OBS is the colour space
conversion which is not lossless. More precisely, trying NV12 gives me wrong colours and trying
anything else gives me "Encoding Overloaded" for no apparent reason (all performance indicators, CPU
and GPU look mild).
>> My only theory is that GPU memory might be getting full
I checked, it wasn't.
>> Maybe I should use hevc_nvenc with lossless setting
Tried, ran into the same problem as with hwdownload->utvideo. Maybe something about the grabber?
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2023-08-01 0:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 1:49 Misha Aizatulin
2023-07-31 15:35 ` Tomas Härdin
2023-08-01 0:24 ` Misha Aizatulin [this message]
2023-08-18 22:55 ` Misha Aizatulin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0e6228d9-9f68-322d-246f-b564b3f84476@gmail.com \
--to=mihhail.aizatulin@gmail.com \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=git@haerdin.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git