Well ,thanks very much ! it sounds a good idea to it together.
-邮件原件-
发件人: ffmpeg-user 代表 Ted Park
发送时间: 2019年7月8日 10:45
收件人: FFmpeg user questions
主题: Re: [FFmpeg-user] Decode Error
> On Jul 7, 2019, at 8:51 PM, Hu Saijun wrote:
>
> Hi,dear friends, recently I have a task which need
> On Jul 7, 2019, at 8:51 PM, Hu Saijun wrote:
>
> Hi,dear friends, recently I have a task which need cut the long videos to
> many segments. The concrete code I used as follow:
>
> 1. First I convert all video to mpeg4 codec. Use
> [cid:image001.png@01D53569.052114F0]
>
> 2. Second
Am 07.07.19 um 22:30 schrieb Reindl Harald:
>
> Am 07.07.19 um 22:27 schrieb Ulf Zibis:
>> Am 07.07.19 um 22:24 schrieb Ulf Zibis:
>>> Am 07.07.19 um 22:12 schrieb Paul B Mahol:
./configure --toolchain=gcc-asan
>>> I get:
>>> $ ./configure --toolchain=gcc-asan
>>> gcc is unable to create an
Am 07.07.19 um 22:27 schrieb Ulf Zibis:
>
> Am 07.07.19 um 22:24 schrieb Ulf Zibis:
>> Am 07.07.19 um 22:12 schrieb Paul B Mahol:
>>> ./configure --toolchain=gcc-asan
>> I get:
>> $ ./configure --toolchain=gcc-asan
>> gcc is unable to create an executable file.
>> If gcc is a cross-compiler,
Am 07.07.19 um 22:12 schrieb Paul B Mahol:
> ./configure --toolchain=gcc-asan
I get:
$ ./configure --toolchain=gcc-asan
gcc is unable to create an executable file.
If gcc is a cross-compiler, use the --enable-cross-compile option.
Only do this if you know what cross compiling means.
C compiler
On 7/7/19, Ulf Zibis wrote:
>
> Am 07.07.19 um 21:27 schrieb Reindl Harald:
>>
>> Am 07.07.19 um 21:23 schrieb Ulf Zibis:
>>> Am 07.07.19 um 21:16 schrieb Paul B Mahol:
Nope, bug is in your code.
Build ffmpeg with address sanitizer and you will see it.
>>> Thanks, no problem.
>>>
>>>
Am 07.07.19 um 21:27 schrieb Reindl Harald:
>
> Am 07.07.19 um 21:23 schrieb Ulf Zibis:
>> Am 07.07.19 um 21:16 schrieb Paul B Mahol:
>>> Nope, bug is in your code.
>>> Build ffmpeg with address sanitizer and you will see it.
>> Thanks, no problem.
>>
>> What is an address sanitizer, and how can
Am 07.07.19 um 21:23 schrieb Ulf Zibis:
>
> Am 07.07.19 um 21:16 schrieb Paul B Mahol:
>> Nope, bug is in your code.
>> Build ffmpeg with address sanitizer and you will see it.
> Thanks, no problem.
>
> What is an address sanitizer, and how can I build with that?
Am 07.07.19 um 21:16 schrieb Paul B Mahol:
> Nope, bug is in your code.
> Build ffmpeg with address sanitizer and you will see it.
Thanks, no problem.
What is an address sanitizer, and how can I build with that?
-Ulf
___
ffmpeg-user mailing list
On 7/7/19, Ulf Zibis wrote:
>
> Am 07.07.19 um 14:20 schrieb Ulf Zibis:
>>> If you can, install and use valgrind to help you debug such problems.
>> Good idea, I will do that ... guess it needs some time to understand how
>> it works.
>
> I now also have tried valgrind. To me this seems, that the
Am 07.07.19 um 16:30 schrieb Ulf Zibis:
> Here it is
> Please excuse the "under construction" state. The command line t use:
>
> ./ffmpeg -y -v warning -i CYD_1.5m_x264.mp4 -vf
> lineshiftrecover=10:-564:60:-60:report=shifts -q 5 out.mp4
>
> I can send you the in.mp4 I use.
Here is the video for
Am 07.07.19 um 14:20 schrieb Ulf Zibis:
>> If you can, install and use valgrind to help you debug such problems.
> Good idea, I will do that ... guess it needs some time to understand how
> it works.
I now also have tried valgrind. To me this seems, that the cause is
outside of my code:
Am 07.07.19 um 15:45 schrieb Paul B Mahol:
> Could you just send whole patch?
Here it is
Please excuse the "under construction" state. The command line t use:
./ffmpeg -y -v warning -i in.mp4 -vf
lineshiftrecover=10:-564:60:-60:report=shifts -q 5 out.mp4
I can send you the in.mp4 I use.
-Ulf
On 7/7/19, Ulf Zibis wrote:
>
> Am 07.07.19 um 15:31 schrieb Ulf Zibis:
>> So it should be "sizeof(*s->shifts_sums)" aka "sizeof(*int16_t)" which
>> is 8.
>
> Sorry, typo, I meant (**s->shifts_sums).
>
Could you just send whole patch?
> -Ulf
>
> ___
>
Am 07.07.19 um 15:31 schrieb Ulf Zibis:
> So it should be "sizeof(*s->shifts_sums)" aka "sizeof(*int16_t)" which
> is 8.
Sorry, typo, I meant (**s->shifts_sums).
-Ulf
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
Am 07.07.19 um 15:07 schrieb Paul B Mahol:
> On 7/7/19, Ulf Zibis wrote:
>> Am 07.07.19 um 14:29 schrieb Paul B Mahol:
>>> On 7/7/19, Ulf Zibis wrote:
Am 07.07.19 um 13:51 schrieb Paul B Mahol:
> There is av_calloc, it calls memset for you after allocation
Thanks for the hint. I
On 7/7/19, Ulf Zibis wrote:
>
> Am 07.07.19 um 14:29 schrieb Paul B Mahol:
>> On 7/7/19, Ulf Zibis wrote:
>>> Am 07.07.19 um 13:51 schrieb Paul B Mahol:
There is av_calloc, it calls memset for you after allocation
>>> Thanks for the hint. I now have:
>>> if (s->report >= R_SHIFTS) {
>>>
Am 07.07.19 um 14:29 schrieb Paul B Mahol:
> On 7/7/19, Ulf Zibis wrote:
>> Am 07.07.19 um 13:51 schrieb Paul B Mahol:
>>> There is av_calloc, it calls memset for you after allocation
>> Thanks for the hint. I now have:
>> if (s->report >= R_SHIFTS) {
>> s->shifts_sums =
On 7/7/19, Ulf Zibis wrote:
>
> Am 07.07.19 um 13:51 schrieb Paul B Mahol:
>> There is av_calloc, it calls memset for you after allocation
> Thanks for the hint. I now have:
> if (s->report >= R_SHIFTS) {
> s->shifts_sums = av_malloc((s->lines + 1) *
> sizeof(*s->shifts_sums));
This
Am 07.07.19 um 13:51 schrieb Paul B Mahol:
> There is av_calloc, it calls memset for you after allocation
Thanks for the hint. I now have:
if (s->report >= R_SHIFTS) {
s->shifts_sums = av_malloc((s->lines + 1) *
sizeof(*s->shifts_sums));
for (int l = s->lines; l >= 0; l--)
On 7/7/19, Ulf Zibis wrote:
>
> Am 07.07.19 um 12:42 schrieb Ulf Zibis:
>> Hi,
>>
>> when running my code, at the end I irregularly get messages like this:
>> [.]
>> [Parsed_lineshiftrecover_0 @ 0x55e5afb83e80] start freeing memory ...
>> [Parsed_lineshiftrecover_0 @ 0x55e5afb83e80] filler
Am 07.07.19 um 12:42 schrieb Ulf Zibis:
> Hi,
>
> when running my code, at the end I irregularly get messages like this:
> [.]
> [Parsed_lineshiftrecover_0 @ 0x55e5afb83e80] start freeing memory ...
> [Parsed_lineshiftrecover_0 @ 0x55e5afb83e80] filler and shifts freed!
>
On 7/7/19, Ulf Zibis wrote:
> Hi,
>
> when running my code, at the end I irregularly get messages like this:
> [.]
> [Parsed_lineshiftrecover_0 @ 0x55e5afb83e80] start freeing memory ...
> [Parsed_lineshiftrecover_0 @ 0x55e5afb83e80] filler and shifts freed!
> [Parsed_lineshiftrecover_0 @
Hi,
when running my code, at the end I irregularly get messages like this:
[.]
[Parsed_lineshiftrecover_0 @ 0x55e5afb83e80] start freeing memory ...
[Parsed_lineshiftrecover_0 @ 0x55e5afb83e80] filler and shifts freed!
[Parsed_lineshiftrecover_0 @ 0x55e5afb83e80] now start freeing
shifts_sums
Thanks for this prompt reply.
I'll be testing the recompiled-reactivated 24 bit encoder so that MLP can
be added to the free DVD-Audio authoring software dvda-author (
http://dvd-audio.sourceforge.com), which is currently being improved.
Hopefully Jai can fix remaining issues and let me know.
Best
Hi guys,
Thanks a lot for your responses. Based on the suggestions here I was able
to figure out what libx264 uses, but I would like to go a step further and
attempt to grasp basic understanding of how changing these values could
impact the output. Please forgive me if the question sounds too
26 matches
Mail list logo
