gmane.comp.audio.libsndfile.devel

Re: Music format requests

2013-05-20T14:39:59

Unfortunately current build seems to be not really functional regarding 
ALSA, also I see quite a lot of advantages if I could use libsndfile.
To be honest, I thought about it, but in my little free time I'd be 
happy not to spend as much hours it probably will take to work me into 
the question and debug why it is not working correctly with ALSA. as I 
have no idea about how ALSA works internally yet. Also mikmod seems to 
be blocked in output somehow by the OpenAL output, which could be a 
related problem with the ALSA implementation of it. With libsndfile I 
wouldn't have such an issue from the beginning.
However, I already sent a mail to the current maintainer, maybe 
something can be worked out.

Anyway, thanks for the answer, it's very much understandable, I can 
imagine the implementation would be rather time consuming.

Smirftsch

Re: Music format requests

Erik de Castro Lopo — 2013-05-20T14:00:08


Why replace MikMod?


It doesn't support *any* tracker music formats, only the XM sample
format.


I think this is beyond the scope of libsndfile. Its certainly not
something I would sink any of my time into and would require quite
a bit of my time just to validate the design and implementation of
someone else.

Why not improve or fork and improve MikMod?

Erik

Re: Music format requests

jpff — 2013-05-20T09:43:57

I am not sure how tracker formats fit with libsndfile, but I found this 
specification
http://hackipedia.org/File formats/Music/Sample based/html/s3mformat.html

Difficult to read.....
It does not seem to define sounds but scores.
==John ff

On Mon, 20 May 2013, developer-8p+X3QGnu5YS+FvcfC7Uqw< at >public.gmane.org wrote:

Music format requests

2013-05-20T09:28:36

I'm watching libsndfile for quite some time already and I am very 
impressed about the dedication and accuracy this project is maintained. 
Unfortunately it never fit all I needed, so never came around to use it. 
But I read on the page "Other file formats may also be added on request. 
" - so I am giving it a try now :)
I am looking for a library fully able to replace MikMod. In my current 
solution I am using FMod, which is unfortunately closed and commercial 
and I wanted to replace it with something free and open. Libsndfile came 
directly into my mind, but from what I see it only supports partially 
some of the old tracker formats.

"Mikmod support for the following modules formats:
*669* (Composer 669, Unis 669), *AMF* (DSMI Advanced Module Format), 
*AMF* (ASYLUM Music Format V1.0), *APUN* (APlayer), *DSM* (DSIK internal 
format), *FAR* (Farandole Composer), *GDM* (General DigiMusic), *IT* 
(Impulse Tracker), *IMF* (Imago Orpheus), *MOD* (15 and 31 instruments), 
*MED* (OctaMED), *MTM* (MultiTracker M

Re: Stack Protector

Richard Ash — 2013-05-16T21:43:58

On Wed, 15 May 2013 10:42:04 -0700
Erik de Castro Lopo <erikd-GkEtBYYK+uT2eFz/2MeuCQ< at >public.gmane.org> wrote:

It is patched, but it's 1.0.24 with some backported fixes from
subsequent releases. I'm too lazy to pull the current release into our
SVN if there is another one in the pipeline.

If available, we might fall back to ffmpeg/libav as importer - certainly
it's what I'd try using to read the file.

Richard

Re: Stack Protector

Erik de Castro Lopo — 2013-05-15T17:42:04


Really?


That was my understanding too. Maybe Audacity has a patched version of
libsndfile, maybe it has a fallback handler for files that don't open
with libsndfile.


Is it possible to put the file on dropbox or something so I can have
a look at it? If its small you could probably also email it directly
to me.

Cheers,
Erik

Re: Stack Protector

Bartosz Bielawski — 2013-05-15T14:28:13

Nice, thanks :)


I know what you mean. The curious thing is that I opened the same
damaged file with Audacity 2.0 (which I believe uses libsndfile for
file IO) and it did not complain, while my program (vanilla
libsndfile) does not allow to open such file.

Bartek

Re: Stack Protector

Erik de Castro Lopo — 2013-05-15T14:20:57


It will be fixed for the next release:

    https://github.com/erikd/libsndfile/issues/42


For this specific case, its relatively easy, but files can be malformed
in an infinite number of different ways and its not possible to cope
with the infinite number of ways they can be broken.

Cheers,
Erik

Stack Protector

Bartosz Bielawski — 2013-05-15T12:00:54

Hi,

I've just cloned repo from GitHub and tried to build dynamic library
(Win32 DLL) using mingw32 under MacOSX. The build fails due to
unresolved symbols pointing at the stack protector. I tried to force
-fno-stack-protector flag during ./configure, but the
"-fstack-protector" follows in the CFLAGS cancelling the previous
setting.

The 1.0.25 version from tar.gz builds fine.

I've seen Erik's post on devel list for FLAC library about adding a
configure switch to disable stack protector. Is something like this
planned also for the new release of libsndfile?

And another quick question. I just run into a malformed mono WAV file.
It it's PEAK chunk it has too many records - 6 pairs (value, position)
instead of one. Is there any way to know libsndfile to go on with
reading as far as possible discarding all non-critical chunks?

Regards,
Bartosz

SV: Re: Create static .lib file

Lars Palo — 2013-05-14T16:32:20

Hi!



I suspect that few are inclined to answer as your question is not especially well phrased and libsndfile is rather expected to be dynamically linked especially if your code is not free/open source. From the license info on libsndfile homepage:

You can use libsndfile with Free Software, Open Source, proprietary, shareware or other closed source applications as long as libsndfile is used as a dynamically loaded library and you abide by a small number of other conditions (read the LGPL for more info). With applications released under the GNU GPL you can also use libsndfile statically linked to your application. 


So, what you really want to do is to statically link libsndfile to your application (assuming it's released under GNU GPL). It's certainly possible to do but you'll have to read up on your compiler in order to learn how to do it. A starter would be a web search for "statically link library c++" or something similar.

Kind regards

Lars P

Re: Create static .lib file

Rahul Maji — 2013-05-14T08:54:44

Kindly help please!! URGENT

On Tue, May 14, 2013 at 1:40 PM, Rahul Maji <rahulmj92-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org> wrote:

Re: Create static .lib file

Rahul Maji — 2013-05-14T08:19:07

Hi,
I want to create a static .lib file (libsndfile-1.lib) instead of a .dll
file using MSVC++. Kindly help me to do so.

A quick reply shall be appreciated.

Thanks,
Rahul.


On Tue, May 14, 2013 at 1:40 PM, Rahul Maji <rahulmj92-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org> wrote:

Re: Plans to release 1.0.26

olivier tristan — 2013-05-14T07:51:10

Le 14/05/2013 03:55, Erik de Castro Lopo a écrit :
oki doki.

Thanks !

Re: Plans to release 1.0.26

Erik de Castro Lopo — 2013-05-14T01:55:03


Very definitely, but I'm really snowed under at the moment. I'm currently
travelling for work and back home on the 25th. Then plan to get FLAC 
released and then libsndfile.

Erik

Plans to release 1.0.26

olivier tristan — 2013-05-13T08:00:58

Hi Erik,

Is there any plan to release version 1.0.26 of libsndfile ?

Thanks,

Re: Large file support and the ultimate sanity check on Android

Erik de Castro Lopo — 2013-04-30T10:44:11


Done.


I can recreate that in a 32 bit Debian chroot.

Having looked at this a little more, this is an incredibly complex
problem. Even when all the warnings are fixed, with off_t being only 32
bits, the biggest file that can be accurately and reliably read is 2
gigabytes.

Erik

Re: Large file support and the ultimate sanity check on Android

Felix Homann — 2013-04-30T09:53:59

2013/4/30 Erik de Castro Lopo <erikd-GkEtBYYK+uT2eFz/2MeuCQ< at >public.gmane.org>


Thanks Erik, for diving deeper into this issue. I'm preparing a blog post
on how to build and test native libraries for Android. I hope to finish it
by tomorrow so you would not need to resort to a chroot environment.

I don't understand your code good enough to sort the compiler warnings out
even though I would really love to do so. I'll try my best nevertheless
hoping that I get it managaged some time. And maybe you will change your
mind on this...

In the meantime, it would probably be best to remove the claim that
libsndfile "has been compiled and tested [...] on [...]
arm-linux-androideab (Android phones OS)" from your website to prevent
people from stepping into the same trap that I did. And, more important, to
prevent them from using it without knowing it may fail in undefined ways.

For the record, here's a list of the compiler warnings I get when building
libsndfile for Android:

sndfile.c: In function 'guess_file_type':

Re: Large file support and the ultimate sanity check on Android

Erik de Castro Lopo — 2013-04-30T01:59:04


I've tried configuring with --disable-largefile in a 32 bit chroot. When
I compile I get dozens of warnings. Every single one of those warnings needs
to be looked at and probably fixed. By fixed I mean fixed in a way so that 
it doesn't break for platforms that do support 64 bit file offsets. This is
a non-trvial task and I doubt I have the patience for it.

Erik

Re: Large file support and the ultimate sanity check on Android

Erik de Castro Lopo — 2013-04-30T00:09:45


Ok, I'm probably wrong about that. Looks like Android does not have large
file support.

I removed explicit support for systems without large file support some time
ago because maintaining it was a huge pain in the neck.

Adding it back in would also be a huge pain in the neck and then I'd have
to maintain it again.

Erik

Re: truncation errors in VOX ADPCM codec

Steve Underwood — 2013-04-29T23:54:07

Adobe Audition started life as Cool Edit, and I believe that was one of 
the popular tools for producing broken Dialogic files in the 90s.

Steve


On 04/30/2013 01:07 AM, Chris Rienzo - Grasshopper wrote:

FW: truncation errors in VOX ADPCM codec

Chris Rienzo - Grasshopper — 2013-04-29T23:53:33

-----Original Message-----
From: Rob Sykes [mailto:aquegg-/E1597aS9LT10XsdtD+oqA< at >public.gmane.org] 
Sent: Monday, April 29, 2013 4:39 PM
To: Chris Rienzo - Grasshopper
Subject: Re: [libsndfile-devel] truncation errors in VOX ADPCM codec

Sorry Chris, despite Erik having told me that the posting problem has been fixed, it obviously isn't yet...
Please could you forward this one to the list? Thanks in advance, Rob

----- Original Message -----

Hi Steve,

That's not what I think -- I have a few files that I believe came from a Dialogic installation disc (they say things like "Thank you for calling Dialogic Corporation, etc. "); and a few files from users, requesting that their files, purportedly from vox recorders (but I didn't enquire as to the manufacturer), be decoded correctly.

The code is currently the way it is in order to satisfy previous user-requests (who didn't seem to consider their files to be junk!)  The  patch aims to continue to satisfy such users, whilst adding support for files like