From: Simone Karin Lehmann
Signed-off-by: Simone Karin Lehmann
---
libavcodec/videotoolboxenc.c | 54
1 file changed, 42 insertions(+), 12 deletions(-)
diff --git a/libavcodec/videotoolboxenc.c b/libavcodec/videotoolboxenc.c
index 400401550a..e8cbc9dd4d
ory or the amount of
memory while transcoding?
Or building a 64bit version would fix this issue?
Any help would really be appreciated.
Thank you,
Simone.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
> 2019-03-14 11:28 GMT+01:00, Simone Donadini :
> > Hi there,
> > we are developing a transcoder using ffmpeg based on the transcoding example
> > https://www.ffmpeg.org/doxygen/4.1/transcoding_8c-example.html and we are
> > encountering some problem with memory usage t
emory on a 64bit
OS.
Do you have any advice on how to reduce the memory footprint of FFMPEG?
Kind Regards,
Simone Donadini
From: ffmpeg-devel [ffmpeg-devel-boun...@ffmpeg.org] on behalf of Carl Eugen
Hoyos [ceffm...@gmail.com]
Sent: Thursday, March 14,
Hi Ronald,
yes, we are using our own codec wrapped inside FFmpeg.
Thank you for your suggestion, i will try with limiting the number of threads
launched by FFmpeg.
Simone.
From: ffmpeg-devel [ffmpeg-devel-boun...@ffmpeg.org] on behalf of Ronald S.
Bultje
i set some flag too?
I tried also to set the output context flag to AVFMT_FLAG_SHORTEST but i am not
getting the same result.
Thank you,
bye,
Simone.
________
From: Simone Donadini
Sent: Friday, March 15, 2019 11:42 AM
To: FFmpeg development discussions and
Somehow it seems, that this patch never got onto the mailing list. So may I
kindly ask you to review it.
--
Stay hungry, stay foolish
> Am 26.01.2022 um 17:31 schrieb Simone Karin Lehmann :
>
>
> The patch adds an option to the hevc_videotoolbox encoder to prioritize speed
>
rQuality property: %d\n", status);
>>> +return AVERROR_EXTERNAL;
>>> +}
>
> If its called to priotize speed over qual, why not just print a warning and
> continue without this option?
You’re right. A warning seems much better. Changed this too.
since the SDK states that this property
defaults to FALSE for h264 and hevc and to TRUE for ProRes I didn’t add it to
the COMMON_OPTIONS but to each encoder options, because I didn’t want to make a
regression to the ProRes or enabling it by default for h264 and hevc. Hope
that’s ok.
Here’s th
mer patch from me still there in your source tree?
Simone
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
> Am 23.04.2022 um 21:56 schrieb Thilo Borgmann :
>
> Am 23.04.22 um 17:42 schrieb Simone Karin Lehmann:
>>> Am 23.04.2022 um 17:07 schrieb Thilo Borgmann :
>>>
>>>
>>> If that works I'd be happy. Does not apply for me anymore (on HEAD), thou
anging for different codecs
> or different OS versions. It could also be moved into COMMON_OPTIONS in
> this case.
oh yes, that’s way better. I didn’t think of that in the first place. Thanks
for the hint.
Here’s the modified patch
Simone
0001-add-options-to-h264-hevc-and-prores-e
Hi,
may I kindly ask you to check, if this patch could now be applied?
Regards
Simone
Von meinem iPad gesendet
> Am 25.04.2022 um 22:33 schrieb Simone Karin Lehmann :
>
>
>
>>> Am 25.04.2022 um 21:14 schrieb Rick Kern :
>>>
>>>
>>> {
Hi,
… I’m so sorry, the patch I recently sent didn’t test the prio_speed bool. This
corrects it.
I really sorry. :-/
Regards
Simone
0001-add-options-to-h264-hevc-and-prores-encoders-to-prio.patch
Description: Binary data
> Am 01.05.2022 um 20:25 schrieb Richard Kern :
>
>
>
14 matches
Mail list logo
