Re: [FFmpeg-user] ERROR: libvmaf >= 2.0.0 not found using pkg-config

2022-02-04 Thread 桃源老師
Hello,

> 2022/02/04 午後5:55、Gyan Doshi mailto:ffm...@gyani.pro>>のメール:
> 
> 
> 
> On 2022-02-04 01:20 pm, 桃源老師 wrote:

>> 
>> I attached config.log with this message.  Hope someone help me...
> 
> Make sure libvmaf.h is current and exists in only one path (no older copies 
> elsewhere).

Thank you Gyan -san, 

I found an old version of libvmaf.h on include.  Then I removed it but same 
error message occurred. But this time, the error is related with linker.  i.e. 
bunch of libvmaf.a(svm.cpp.o) error.
I confirmed it does not occurred in dynamic linking.  Finally, I get answer 
from Google. That is:

Add -lstdc++ to CFLAGS while compiling FFmpeg

https://github.com/Netflix/vmaf/issues/569 



// Miya

smime.p7s
Description: S/MIME cryptographic signature
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] ERROR: libvmaf >= 2.0.0 not found using pkg-config

2022-02-04 Thread Gyan Doshi



On 2022-02-04 01:20 pm, 桃源老師 wrote:



/var/folders/1d/qk_hczkn68xfv_7gdbkmhwx4gn/T//ffconf.DmkkrFIx/test.c:3:44: 
error: use of undeclared identifier 'vmaf_init'
long check_vmaf_init(void) { return (long) vmaf_init; }

It seems to me that vmaf_init() had existed before, so I'm not sure why
this would happen.

I'm afraid thet is it a bug of macOS...


I attached config.log with this message.  Hope someone help me...


Make sure libvmaf.h is current and exists in only one path (no older 
copies elsewhere).


Gyan
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] ERROR: libvmaf >= 2.0.0 not found using pkg-config

2022-02-03 Thread Paul B Mahol
On Thu, Feb 3, 2022 at 1:11 PM Reindl Harald  wrote:

>
>
> Am 03.02.22 um 13:07 schrieb 桃源老師
> > I experienced funny ffmpeg compille error "ERROR: libvmaf >= 2.0.0 not
> found using pkg-config".  The reason why I feel funny is that ffmpeg commit
> of "06a54a4ec73ea6eb8cec41b7af75367bafb075e0(Date: Sat Jan 22 10:32:34 2022
> +0100)" can configure and make correctly, but current git head can't
> configure.  I suppose something wrong was happened after 2022/01/22
>
> i wonder how that can be given that we are always told here that latest
> git has *always* less bugs than anything else :-)
>

You should be already banned from this list.


> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-user
>
> To unsubscribe, visit link above, or email
> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
>
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] ERROR: libvmaf >= 2.0.0 not found using pkg-config

2022-02-03 Thread 桃源老師
Hello,

> 2022/02/04 午前0:19、Moritz Barsnick のメール:
>
> On Thu, Feb 03, 2022 at 21:07:08 +0900, 桃源老師 wrote:
>> I experienced funny ffmpeg compille error "ERROR: libvmaf >= 2.0.0 not found 
>> using pkg-config".  The reason why I feel funny is that ffmpeg commit of 
>> "06a54a4ec73ea6eb8cec41b7af75367bafb075e0(Date: Sat Jan 22 10:32:34 2022 
>> +0100)" can configure and make correctly, but current git head can't 
>> configure.  I suppose something wrong was happened after 2022/01/22.
>>
>> I'm trying to build ffmpeg on macOS 12.2.
>
> So, what's your actual version of libvmaf? Because _after_ commit
> 06a54a4ec73ea6eb8cec41b7af75367bafb075e0, the requirement was increased
> to 2.0.0.

I installed:
roushinoMacBook-Pro-15:bin roushi$ ./vmaf --version
2.3.0

> If you're using git anyway, you could do a "git bisect".

I didn't know such a git option... Here is:

roushinoMacBook-Pro-15:ffmpeg roushi$ git bisect start 
3d29724c008d8f27fecf85757152789b074e8ef9 
06a54a4ec73ea6eb8cec41b7af75367bafb075e0
Already on 'master'
Your branch is up to date with 'origin/master'.
3d29724c008d8f27fecf85757152789b074e8ef9 is the first bad commit
commit 3d29724c008d8f27fecf85757152789b074e8ef9
Author: Kyle Swanson 
Date:   Fri Dec 24 12:43:50 2021 -0800

avfilter/vf_libvmaf: update filter for libvmaf v2.0.0

 configure|   4 +-
 doc/filters.texi |  82 +++---
 libavfilter/version.h|   2 +-
 libavfilter/vf_libvmaf.c | 682 +++
 4 files changed, 558 insertions(+), 212 deletions(-)

>
>> /var/folders/1d/qk_hczkn68xfv_7gdbkmhwx4gn/T//ffconf.DmkkrFIx/test.c:3:44:
>>  error: use of undeclared identifier 'vmaf_init'
>> long check_vmaf_init(void) { return (long) vmaf_init; }
>
> It seems to me that vmaf_init() had existed before, so I'm not sure why
> this would happen.

I'm afraid thet is it a bug of macOS...

// Miya

smime.p7s
Description: S/MIME cryptographic signature
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] ERROR: libvmaf >= 2.0.0 not found using pkg-config

2022-02-03 Thread Moritz Barsnick
On Thu, Feb 03, 2022 at 21:07:08 +0900, 桃源老師 wrote:
> I experienced funny ffmpeg compille error "ERROR: libvmaf >= 2.0.0 not found 
> using pkg-config".  The reason why I feel funny is that ffmpeg commit of 
> "06a54a4ec73ea6eb8cec41b7af75367bafb075e0(Date: Sat Jan 22 10:32:34 2022 
> +0100)" can configure and make correctly, but current git head can't 
> configure.  I suppose something wrong was happened after 2022/01/22.
>
> I'm trying to build ffmpeg on macOS 12.2.

So, what's your actual version of libvmaf? Because _after_ commit
06a54a4ec73ea6eb8cec41b7af75367bafb075e0, the requirement was increased
to 2.0.0.

If you're using git anyway, you could do a "git bisect".

> /var/folders/1d/qk_hczkn68xfv_7gdbkmhwx4gn/T//ffconf.DmkkrFIx/test.c:3:44:
>  error: use of undeclared identifier 'vmaf_init'
> long check_vmaf_init(void) { return (long) vmaf_init; }

It seems to me that vmaf_init() had existed before, so I'm not sure why
this would happen.

Cheers,
Moritz
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] ERROR: libvmaf >= 2.0.0 not found using pkg-config

2022-02-03 Thread 桃源老師
Hello,

> 2022/02/03 午後9:07、桃源老師 のメール:
>
> Hello,
>
> I experienced funny ffmpeg compille error "ERROR: libvmaf >= 2.0.0 not found 
> using pkg-config".  The reason why I feel funny is that ffmpeg commit of 
> "06a54a4ec73ea6eb8cec41b7af75367bafb075e0(Date: Sat Jan 22 10:32:34 2022 
> +0100)" can configure and make correctly, but current git head can't 
> configure.  I suppose something wrong was happened after 2022/01/22.
>
> I'm trying to build ffmpeg on macOS 12.2.
>
> The seems to error portion on config.log is:
>
> /var/folders/1d/qk_hczkn68xfv_7gdbkmhwx4gn/T//ffconf.DmkkrFIx/test.c:3:44:
>  error: use of undeclared identifier 'vmaf_init'
> long check_vmaf_init(void) { return (long) vmaf_init; }
>   ^
> 1 error generated.
> ERROR: libvmaf >= 2.0.0 not found using pkg-config
>
>
> Any help is appreciated...

I found that the fact was happened on:

commit: 3d29724c008d8f27fecf85757152789b074e8ef9
commit title: avfilter/vf_libvmaf: update filter for libvmaf v2.0.0
commit date: Mon, 24 Jan 2022 04:41:30 +0900 (11:41 -0800)

In that, configure of ffmpeg was changed as:

--- a/configure
+++ b/configure
@@ -3751,7 +3751,7 @@ vaguedenoiser_filter_deps="gpl"
 vflip_vulkan_filter_deps="vulkan spirv_compiler"
 vidstabdetect_filter_deps="libvidstab"
 vidstabtransform_filter_deps="libvidstab"
-libvmaf_filter_deps="libvmaf pthreads"
+libvmaf_filter_deps="libvmaf"
 zmq_filter_deps="libzmq"
 zoompan_filter_deps="swscale"
 zscale_filter_deps="libzimg const_nan"
@@ -6626,7 +6626,7 @@ enabled libtwolame&& require libtwolame twolame.h 
twolame_init -ltwolame
 enabled libuavs3d && require_pkg_config libuavs3d "uavs3d >= 1.1.41" 
uavs3d.h uavs3d_decode
 enabled libv4l2   && require_pkg_config libv4l2 libv4l2 libv4l2.h 
v4l2_ioctl
 enabled libvidstab&& require_pkg_config libvidstab "vidstab >= 0.98" 
vid.stab/libvidstab.h vsMotionDetectInit
-enabled libvmaf   && require_pkg_config libvmaf "libvmaf >= 1.5.2" 
libvmaf.h compute_vmaf
+enabled libvmaf   && require_pkg_config libvmaf "libvmaf >= 2.0.0" 
libvmaf.h vmaf_init
 enabled libvo_amrwbenc&& require libvo_amrwbenc vo-amrwbenc/enc_if.h 
E_IF_init -lvo-amrwbenc
 enabled libvorbis && require_pkg_config libvorbis vorbis 
vorbis/codec.h vorbis_info_init &&
  require_pkg_config libvorbisenc vorbisenc 
vorbis/vorbisenc.h vorbis_encode_init

Here,  I can find out "vmaf_init", might be cause of issue...


// Miya



smime.p7s
Description: S/MIME cryptographic signature
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] ERROR: libvmaf >= 2.0.0 not found using pkg-config

2022-02-03 Thread 桃源老師
Hello,


> 2022/02/03 午後9:11、Reindl Harald のメール:
>
> i wonder how that can be given that we are always told here that latest git 
> has *always* less bugs than anything else :-)

Yes, if it is really a bug, how can we do?

smime.p7s
Description: S/MIME cryptographic signature
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] ERROR: libvmaf >= 2.0.0 not found using pkg-config

2022-02-03 Thread Reindl Harald



Am 03.02.22 um 13:07 schrieb 桃源老師

I experienced funny ffmpeg compille error "ERROR: libvmaf >= 2.0.0 not found using 
pkg-config".  The reason why I feel funny is that ffmpeg commit of 
"06a54a4ec73ea6eb8cec41b7af75367bafb075e0(Date: Sat Jan 22 10:32:34 2022 +0100)" can 
configure and make correctly, but current git head can't configure.  I suppose something wrong was 
happened after 2022/01/22


i wonder how that can be given that we are always told here that latest 
git has *always* less bugs than anything else :-)

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".