problems with ffmpeg

[Robert]

Hi,

I'm trying to get familar with Echoprint Codegen. I followed the
"Codegen windows compilation instructions" described on the GitHub-
Page. I use taglib-1.7.1, zlib-1.2.6 and boost1_49_0.
Work fine so far. Thanks to Aybe for the video.

But when I execute the Codegen solution, I get the error ("could not
decode")
I had also downloaded ffmpeg (32Bit - shared - 2012-04-03) using the
link in readme and set the windows PATH.
Using command line, I can call ffmpeg out of every path, so settings
should be correct, right?!

Why do I get this error?

Thanks in advance,
Robert

[Andrew Nesbit]

Will look into this.

Andrew

[Andrew Nesbit]

Hi Robert,

Can you run ffmpeg by itself from the command line, i.e., ignoring codegen for now? For example, can you convert an MP3 to a WAV file like this:

ffmpeg -i example.mp3 example.wav

from any directory? Are the results listenable, i.e., can you confirm that it's decoding properly?

Do you have the appropriate ffmpeg build? The instructions on the download page suggest using the static build unless you actually need the shared build. Choose 32- or 64-bit build as appropriate.

I have just tested the codegen build procedure in windows/README.md from scratch and can confirm that everything works as expected on Windows 7 inside a 64-bit virtual machine with VC++ 2010 Express and the 64-bit static build of ffmpeg.

Andrew


On Fri, Apr 13, 2012 at 12:47 PM, Robert <rm06...@googlemail.com> wrote:

[Robert]

Hi Andrew,

thanks for your reply.

I can use ffmpeg from every directory.
Conversion works, converted audio file sounds good to me.

I changed to the newest version of ffmpeg (64 Bit, Static,
2012-04-16).
Now I can also use codegen without getting the error message.
Thanks for the hint.

One further question:
I want to use echoprint to identify very short audio files (duration
of only a few seconds).
Do you know the minimum duration for proper and reliable
identification?

Best regards,

Robert

[Andrew Nesbit]

Hi Robert,

Good to hear that it is now working for you.

We recommend a minimum query length of 20 seconds for music files. Several seconds for a query is very short. Depending on your application and the type of audio you are fingerprinting you may or may not get acceptable results with such short queries. The only way to know would be to run some evaluations and see what happens.

Andrew

[Alessandro Radovini]

ffmpeg -i example.mp3 example.wav

how should it work, Andrew?

ffmpeg -i example.mp3 example.wav

i wrote this in my terminale on Ubuntu:

root@radovini-VirtualBox:~# ffmpeg -i Today.mp3 Today.wav

ffmpeg version 0.8.5-4:0.8.5-0ubuntu0.12.04.1, Copyright (c) 2000-2012 the Libav developers

  built on Jan 24 2013 18:03:14 with gcc 4.6.3

*** THIS PROGRAM IS DEPRECATED ***

This program is only provided for compatibility and will be removed in a future release. Please use avconv instead.

Today.mp3: No such file or directory

°_°

[Andrew Nesbit]

The Libav project split off from FFmpeg for various reasons. For one explanation of the story look here: http://blog.pkh.me/p/13-the-ffmpeg-libav-situation.html

Your message seems to indicate that FFmpeg is still operational on your system. Does it still work for you?

--
You received this message because you are subscribed to the Google Groups "echoprint" group.
To unsubscribe from this group and stop receiving emails from it, send an email to echoprint+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Alessandro Radovini]

I'm reading the link that you gave me and seems that FFmpeg is still working:

Packaging

The Debian/Ubuntu packager is on Libav side (see by the way the distribution status on their site), and obviously they distribute Libav packages. But they are also using this to spread a very destructive lie:

1 2 3 4 5

ffmpeg version 0.8.3-6:0.8.3-4, Copyright (c) 2000-2012 the Libav developers built on Jun 26 2012 09:26:41 with gcc 4.7.1 *** THIS PROGRAM IS DEPRECATED *** This program is only provided for compatibility and will be removed in a future release. Please use avconv instead. [...]

This is obviously false, and even more wrong in the sense that they are still using the "ffmpeg" name for the package. It looks like it's been "fixed" on Ubuntu but it's still present on Debian here.

[Prabhat Gupta]

Hi

I was able to compile the windows code for codegen on Visual Studio 2013 in 32 bit configuration. Now when I run the codegen executable, I get the error:
[
{"error":"could not decode", "tag":0, "metadata":{"filename":"C:\Maid.mp3"}}
]

When I debug the code, it seems the issue is in the function -
codegen_response_t codegen_file(char filename, int start_offset, int duration, int tag)

at the following lines

int numSamples = pAudio->getNumSamples(); //In my code I get 0 samples
if (numSamples < 1) {
char* output = (char*) malloc(16384);
sprintf(output,"{\"error\":\"could not decode\", \"tag\":%d, \"metadata\":{\"filename\":\"%s\"}}",

My machine is a Windows 8.1 - X64.
I installed FFMPEG (32 bit) in the path and checked it invoking from command line and it identifies the command.

Please advise if there could be any other issue.

Thanks
Prabhat