osalp-dev

[Osalp-dev] CVS Update

[Darrick S. <da...@dc...>]

I added a config.h file so there isn't so many defines on the command line 
when you compile.

added 
   static const list<aflibFileItem*>&  
        returnSupportedFormats();

I cleaned up configure.in a bit more.

I also looked at Anthony's suggestions for compiling for AIX.

The changes Anthony made to ltconfig and Makefile.in should be sent to the 
maintainers of libtool and automake respectively.  

-- Darrick

[Osalp-dev] Is it good for Linux embedded

[Ashish G. <as...@it...>]

Hi there,

I was just going through the documentation of the open source audio
library. I was wondering if you also have a version for the embedded
linux, or if you are planning for one.

I will appreciate your reply on this.
Thanks,
- Ashish

Re: [Osalp-dev] problem with .wav

[Bruce F. <for...@tn...>]

garbe nicolas wrote:
> 
> Hi,
> I used the osalp 's player and i have a problem with file .wav....
> When I push on the pause 's button , the player don't stop immediately....
> When I use a file .mp3 , when I push on the pause's button, the player stop
> immediately...
> Why is there a difference between mp3's files and .wav's files ?
> best regards,
> nicolas


The difference is in the buffering that is done in the audio device
driver on your computer. There should be no difference between
mp3 and wav format though. There might be a difference between
audio files that contain more data per second that others. For
instance an 8 bit 22050 mono audio file as compared to a 16 bit
44100 stereo file. There is a function called setItem in
aflibDevFile that allows one to set an item called
AFLIB_DEV_ITEM_BUFFER that will change the amount of buffering
done.

Bruce Forsberg

[Osalp-dev] problem with .wav

[garbe n. <ga...@et...>]

Hi,
I used the osalp 's player and i have a problem with file .wav....
When I push on the pause 's button , the player don't stop immediately....
When I use a file .mp3 , when I push on the pause's button, the player stop 
immediately...
Why is there a difference between mp3's files and .wav's files ?
best regards,
nicolas

Re: [Osalp-dev] installation problem

[Bruce F. <for...@tn...>]

garbe nicolas wrote:

> I cast the argument 3 with (void (*) (_WidgetRec *, void *, void *))
> and it's good...
> What version of lesstif will be good for you....???
> My lesstif's version is lesstif-0.93.9-1 and my gcc's version  is  2.96
> best regards ,
> nicolas.

If possible see if Mandrake has a package called Open Motif. It is the
offical Motif and is much better then lesstif. I used to use lesstif
because the offical Motif was not available except for a price. If
Mandrake does not have an Open Motif package then your fix is a good
one.

Bruce

Re: [Osalp-dev] installation problem

[garbe n. <ga...@et...>]

Le Mardi  2 Octobre 2001 00:09, Bruce Forsberg a =E9crit :
> Nicolas Garbe wrote:
> > My name is nicolas garbe and I am trying to use the Open Source Audio
> > Library Project beta VO.7.2....
> > So I downloaded osalp7.2  and I installed the library...
> > I'm working on LINUX mandrake 8.0.....
> > I tried to used the player's example but I couldn't compile.....
> > there is an error message
> > make
> > g++ -g -Wall -fguiding-decls -I/usr/local/include/g++ -I/usr/include/=
g++
> > -I/usr/include/X11 -I/usr/X11R6/include -I/usr/local/include
> > -I/usr/local/include/aflib -I. -c gui.cc
> > cc1plus: warning: -fguiding-decls is no longer supported
> > gui.cc: In function `void gui_build (int, char **)':
> > gui.cc:270: cannot convert `void (*) (_WidgetRec *, char *,
> > XmScaleCallbackStruct *)' to `void (*) (_WidgetRec *, void *, void *)=
'
> > for argument `3' to `XtAddCallback (_WidgetRec *, const char *, void
> > (*) (_WidgetRec *, void *, void *), void *)'
> > gui.cc:288: cannot convert `void (*) (_WidgetRec *, char *,
> > XmScaleCallbackStruct *)' to `void (*) (_WidgetRec *, void *, void *)=
'
> > for argument `3' to `XtAddCallback (_WidgetRec *, const char *, void
> > (*) (_WidgetRec *, void *, void *), void *)'
> > make: *** [gui.o] Erreur 1
> >
> > Do you have any idea of what could be the problem ?
>
> Can you tell me what version of g++ you are using? You should
> be able to do:
>
> g++ --version
>
> Also what Motif are you using. The offical version or lesstif?
>
>
> Thanks,
> Bruce Forsberg
I cast the argument 3 with (void (*) (_WidgetRec *, void *, void *))
and it's good...
What version of lesstif will be good for you....???
My lesstif's version is lesstif-0.93.9-1 and my gcc's version  is  2.96
best regards ,
nicolas.

Re: [Osalp-dev] installation problem

[garbe n. <ga...@et...>]

Le Mardi  2 Octobre 2001 00:09, vous avez =E9crit :
> Nicolas Garbe wrote:
> > My name is nicolas garbe and I am trying to use the Open Source Audio
> > Library Project beta VO.7.2....
> > So I downloaded osalp7.2  and I installed the library...
> > I'm working on LINUX mandrake 8.0.....
> > I tried to used the player's example but I couldn't compile.....
> > there is an error message
> > make
> > g++ -g -Wall -fguiding-decls -I/usr/local/include/g++ -I/usr/include/=
g++
> > -I/usr/include/X11 -I/usr/X11R6/include -I/usr/local/include
> > -I/usr/local/include/aflib -I. -c gui.cc
> > cc1plus: warning: -fguiding-decls is no longer supported
> > gui.cc: In function `void gui_build (int, char **)':
> > gui.cc:270: cannot convert `void (*) (_WidgetRec *, char *,
> > XmScaleCallbackStruct *)' to `void (*) (_WidgetRec *, void *, void *)=
'
> > for argument `3' to `XtAddCallback (_WidgetRec *, const char *, void
> > (*) (_WidgetRec *, void *, void *), void *)'
> > gui.cc:288: cannot convert `void (*) (_WidgetRec *, char *,
> > XmScaleCallbackStruct *)' to `void (*) (_WidgetRec *, void *, void *)=
'
> > for argument `3' to `XtAddCallback (_WidgetRec *, const char *, void
> > (*) (_WidgetRec *, void *, void *), void *)'
> > make: *** [gui.o] Erreur 1
> >
> > Do you have any idea of what could be the problem ?
>
> Can you tell me what version of g++ you are using? You should
> be able to do:
>
> g++ --version
>
> Also what Motif are you using. The offical version or lesstif?
>
>
> Thanks,
> Bruce Forsberg
My version of g++ is 2.96
I'm using  lesstif-0.93.9-1 and lesstif-devel-0.93.9-1.....
nicolas garbe

Re: [Osalp-dev] installation problem

[Bruce F. <for...@tn...>]

Nicolas Garbe wrote:
> My name is nicolas garbe and I am trying to use the Open Source Audio
> Library Project beta VO.7.2....
> So I downloaded osalp7.2  and I installed the library...
> I'm working on LINUX mandrake 8.0.....
> I tried to used the player's example but I couldn't compile.....
> there is an error message
> make
> g++ -g -Wall -fguiding-decls -I/usr/local/include/g++ -I/usr/include/g++
> -I/usr/include/X11 -I/usr/X11R6/include -I/usr/local/include
> -I/usr/local/include/aflib -I. -c gui.cc
> cc1plus: warning: -fguiding-decls is no longer supported
> gui.cc: In function `void gui_build (int, char **)':
> gui.cc:270: cannot convert `void (*) (_WidgetRec *, char *,
> XmScaleCallbackStruct *)' to `void (*) (_WidgetRec *, void *, void *)'
> for argument `3' to `XtAddCallback (_WidgetRec *, const char *, void
> (*) (_WidgetRec *, void *, void *), void *)'
> gui.cc:288: cannot convert `void (*) (_WidgetRec *, char *,
> XmScaleCallbackStruct *)' to `void (*) (_WidgetRec *, void *, void *)'
> for argument `3' to `XtAddCallback (_WidgetRec *, const char *, void
> (*) (_WidgetRec *, void *, void *), void *)'
> make: *** [gui.o] Erreur 1
> 
> Do you have any idea of what could be the problem ?


Can you tell me what version of g++ you are using? You should
be able to do:

g++ --version

Also what Motif are you using. The offical version or lesstif?


Thanks,
Bruce Forsberg

[Osalp-dev] installation problem

[Nicolas G. <ga...@et...>]

Hi,
My name is nicolas garbe and I am trying to use the Open Source Audio
Library Project beta VO.7.2....
So I downloaded osalp7.2  and I installed the library...
I'm working on LINUX mandrake 8.0.....
I tried to used the player's example but I couldn't compile.....
there is an error message 
make
g++ -g -Wall -fguiding-decls -I/usr/local/include/g++ -I/usr/include/g++
-I/usr/include/X11 -I/usr/X11R6/include -I/usr/local/include
-I/usr/local/include/aflib -I. -c gui.cc
cc1plus: warning: -fguiding-decls is no longer supported
gui.cc: In function `void gui_build (int, char **)':
gui.cc:270: cannot convert `void (*) (_WidgetRec *, char *,
XmScaleCallbackStruct *)' to `void (*) (_WidgetRec *, void *, void *)'
for argument `3' to `XtAddCallback (_WidgetRec *, const char *, void
(*) (_WidgetRec *, void *, void *), void *)'
gui.cc:288: cannot convert `void (*) (_WidgetRec *, char *,
XmScaleCallbackStruct *)' to `void (*) (_WidgetRec *, void *, void *)'
for argument `3' to `XtAddCallback (_WidgetRec *, const char *, void
(*) (_WidgetRec *, void *, void *), void *)'
make: *** [gui.o] Erreur 1


Do you have any idea of what could be the problem ?

Best regards,
Nioclas.

[Osalp-dev] CVS Update

[Darrick S. <da...@dc...>]

I updated the following today:

08/24/2001    Bug fix for AU-ALAW and AU-ULAW file writing.
08/24/2001    Added support for stdin and stdout in Sox File Module.
08/24/2001    Cleaned up and commented configure.in.
08/24/2001    Have aflibFile return AFLIB_CANT_AUTO_TYPE if file type is
                not supported rather then printing dlopen error.

Thanks
-- Darrick

[Osalp-dev] More AIX checkins

[Bruce F. <for...@tn...>]

I have checked into CVS several more changes submitted by
Anthony Zawacki. These are type castings for the sox
module.

Bruce Forsberg

[Osalp-dev] Checkins

[Bruce F. <for...@tn...>]

I have checked into CVS several changes submitted by
Anthony Zawacki. They are namespaces have been added
and changes to the audiofile library for AIX. More
AIX changes will be forthcoming.


Bruce Forsberg

Re: [Osalp-dev] Application Design Clarification

[Darrick S. <da...@dc...>]

My thoughts:

1.  You'll get the audio data in buffers.  So this means the file modules 
will need to handle a stdin stream.  I could very easily do this.  Another 
option is to setup the file modules to accept a data buffer and read from 
that rather then opening a file.

2.  Output is much more simple.  You open a aflibAudioFile with the input as 
parent after setting the config to what you want.  You should be able to 
choose what format you want too.  Write it to /dev/null.  Currently we don't 
have a raw 8kHz ULAW format.  The sox module can handle it but it's not 
currently listed in the exported formats.  I'll fix that.  

so

aflibAudioFile* output = new aflibAudioFile( input, "8kHz U-LAW", 
"/dev/null", config, status);

then:

aflibData* data;

while( no_samples){
	data = output->process(status,-1,no_samples,FALSE);
	do_something_with_data( data );
}


On Monday 20 August 2001 10:52, Anthony Zawacki wrote:
> Hello,
>
> I'm seeking a bit of clarification on how to use OSALP in my application.
>
> A brief background:
> My module will receive audio data in buffers, read from an HTTP source
> (though I am not responsible for the reading.)  This data must then be
> converted to 8kHz AU-ULAW with the header stripped.  What I was planning to
> do is build an audio device that requires 8khz AU-ULAW.  It would then
> start by stripping off the header, and write the data out to a set of
> buffers.  Other portions of the application will read those buffers and do
> the actual writing to the audio device through it's API.  I thought that an
> aflibAudioMemoryInput class would do the trick, but as far as I can
> understand it, the data must already be in the "correct" format as noted in
> section 4.2.10 of the Audio Library Programmers Manual.  It's not clear to
> me what is the "correct" format.
>
> My input data could be one of:
> Raw (headerless) 8kHz 8-bit mu-law [PCM] single channel*
> Raw (headerless) 8kHz 8-bit a-law [PCM] single channel*
> WAV (RIFF header) 8kHz 8-bit mu-law [PCM] single channel*
> WAV (RIFF header) 8kHz 8-bit a-law [PCM] single channel*
> Others we specify as supported(MP3, ...)
>
> The item's marked by an (*) are required.  I need to convert these formats
> to 8kHz Raw (headerless) 8-bit mu-law [PCM] single channel, which is what
> our audio device understands.  The input data format I was hoping for is
> all of the required items, plus additional formats as supported by OSALP
> (plus any additional we may want to create supporting our audio device.)
>
> In general, I know which of the input types I will be getting from the
> content-type in the header.  The question is, after I recognize that the
> file is MP3, how do I put an MP3 decoder into the audio chain so that the
> device writer can get the correct input.
>
> If anything is not clear, let me know, and I'll try to explain better.
>
> Thanks,
> Anthony
>
>
> _______________________________________________
> Osalp-dev mailing list
> Osa...@li...
> http://lists.sourceforge.net/lists/listinfo/osalp-dev

[Osalp-dev] Application Design Clarification

[Anthony Z. <zw...@us...>]

Hello,

I'm seeking a bit of clarification on how to use OSALP in my application.

A brief background:
My module will receive audio data in buffers, read from an HTTP source
(though I am not responsible for the reading.)  This data must then be
converted to 8kHz AU-ULAW with the header stripped.  What I was planning to
do is build an audio device that requires 8khz AU-ULAW.  It would then
start by stripping off the header, and write the data out to a set of
buffers.  Other portions of the application will read those buffers and do
the actual writing to the audio device through it's API.  I thought that an
aflibAudioMemoryInput class would do the trick, but as far as I can
understand it, the data must already be in the "correct" format as noted in
section 4.2.10 of the Audio Library Programmers Manual.  It's not clear to
me what is the "correct" format.

My input data could be one of:
Raw (headerless) 8kHz 8-bit mu-law [PCM] single channel*
Raw (headerless) 8kHz 8-bit a-law [PCM] single channel*
WAV (RIFF header) 8kHz 8-bit mu-law [PCM] single channel*
WAV (RIFF header) 8kHz 8-bit a-law [PCM] single channel*
Others we specify as supported(MP3, ...)

The item's marked by an (*) are required.  I need to convert these formats
to 8kHz Raw (headerless) 8-bit mu-law [PCM] single channel, which is what
our audio device understands.  The input data format I was hoping for is
all of the required items, plus additional formats as supported by OSALP
(plus any additional we may want to create supporting our audio device.)

In general, I know which of the input types I will be getting from the
content-type in the header.  The question is, after I recognize that the
file is MP3, how do I put an MP3 decoder into the audio chain so that the
device writer can get the correct input.

If anything is not clear, let me know, and I'll try to explain better.

Thanks,
Anthony

Re: [Osalp-dev] Question on compiler options

[Darrick S. <da...@dc...>]

Well I have some questions about this.

How well does configure run? any errors from that?

Try regenerating all the Makefile.in files by using automake on your machine.

The -Wall flag is my fault look in configure.in and you'll see a line that 
says

CXXFLAGS="$CXXFLAGS -Wall "

delete that.

this macro in configure.in defines inline = __inline

AC_C_INLINE

delete that.

To set things up on your machine you should really start from configure.in 
just go through it line by line and see what each macro does.  use info 
automake or info autoconf or info libtool to find info on the macro.  dnl 
will comment out the line.

Good luck.

-- Darrick

[Osalp-dev] Question on compiler options

[Anthony Z. <zw...@us...>]

Hello,

As some of you may remember, I am attempting to get OSALP to run using xlC
(VisualAge 5.0) on AIX 4.3.3.  Things are going "sort of ok."  In the aflib
and the individual file type directories under formatlib, there is a line
in the Makefile.in that looks like:

%.lo: %.c
        @echo '$(LTCOMPILE) -c $<'; \
        $(LTCOMPILE) -Wp,-MD,.deps/$(*F).pp -c $<
        @-sed -e 's/^\([^:]*\)\.o[      ]*:/\1.lo \1.o :/' \
          < .deps/$(*F).pp > .deps/$(*F).P; \
        tr ' ' '\012' < .deps/$(*F).pp \
          | sed -e 's/^\\$$//' -e '/^$$/ d' -e '/:$$/ d' -e 's/$$/ :/' \
            >> .deps/$(*F).P; \
        rm -f .deps/$(*F).pp

My real question is what does the -Wp,-MD,.deps/$(*F).pp option(s) do?  I
believe this limits the makefiles to g++ only.  I'm not sure exactly what
these lines do, other than to say it is obvious they are attempting to
generate some dependency information from the source files.  I'm thinking
for the short term in my case, to remove all dependency generation, and
just make clean in between changes to the files.

Any suggestions are helpful.

Thanks,
Anthony

[Osalp-dev] V0.7.2 released

[Bruce F. <for...@tn...>]

Version 0.7.2 of OSALP has been released.

Bruce Forsberg

Re: [Osalp-dev] Source Code Compatibility

[Bruce F. <for...@tn...>]

Anthony Zawacki wrote:
> 
> Hello,
> 
> I am attempting to use osalp in an AIX-4.3.3 / Visual Age 5.0 environment.
> Recognizing that this isn't a supported configuration, I expected to need
> to work on the sourcecode to get everything to work right.
> 
> I thought I would share some observations as I've started looking through
> the source code.
> 
> o  Something is setting the command line parameters strangely, such as my
> flags to include -Wall even though I specified a different compiler (xlC).
> -Dinline=__inline even though it should be just inline, so I remove this
> -D.
> 
> o  Some places #include <map> while other places include "map.h".  These
> may or may not be the same files.  In my case, they are not.  (other stl
> classes have similar issues, such as set.)
> 
> o  Several places have code that looks like this:
> #if __GNUC__ >= 3
> using std::string;
> using std::list;
> using std::map;
> #endif
> 
> This should probably be something more generalized to the extent of having
> something like #define OSALP_NAMESPACES __GNUC__ >= 3 and then changing the
> using section to:
> #if OSALP_NAMESPACES
> using std::string;
> using std::list;
> using std::map;
> #endif
> 
> This would allow a configuration file to defile OSALP_NAMESPACES for a
> given platform/compiler.
> 
> Any thoughts or suggestions for this type of porting effort is appreciated.
> Does it make sense for me to continue down this route?
> 

I think these are all good suggestions. All STL references should be of
the
form <map> and not map.h. I will fix this in CVS and check in the
changes
tonite. 

As far as namespaces, I not not too sure if all compilers are at
namespaces
yet. If they are then we should just use them everywhere, otherwise I
agree
with your change.

As far as Makefile type stuff I am not an autoconf, automake expert by
any means so I am not too sure what the fix is. 

Any effort to port to other platforms is very wellcome.

Bruce Forsberg

[Osalp-dev] Source Code Compatibility

[Anthony Z. <zw...@us...>]

Hello,

I am attempting to use osalp in an AIX-4.3.3 / Visual Age 5.0 environment.
Recognizing that this isn't a supported configuration, I expected to need
to work on the sourcecode to get everything to work right.

I thought I would share some observations as I've started looking through
the source code.

o  Something is setting the command line parameters strangely, such as my
flags to include -Wall even though I specified a different compiler (xlC).
-Dinline=__inline even though it should be just inline, so I remove this
-D.

o  Some places #include <map> while other places include "map.h".  These
may or may not be the same files.  In my case, they are not.  (other stl
classes have similar issues, such as set.)

o  Several places have code that looks like this:
#if __GNUC__ >= 3
using std::string;
using std::list;
using std::map;
#endif

This should probably be something more generalized to the extent of having
something like #define OSALP_NAMESPACES __GNUC__ >= 3 and then changing the
using section to:
#if OSALP_NAMESPACES
using std::string;
using std::list;
using std::map;
#endif

This would allow a configuration file to defile OSALP_NAMESPACES for a
given platform/compiler.

Any thoughts or suggestions for this type of porting effort is appreciated.
Does it make sense for me to continue down this route?

Thanks,
Anthony

[Osalp-dev] More Changes

[Bruce F. <for...@tn...>]

I have made a change to both the aflibConverter and
aflibAudioSampleRateCvt classes
that allows one to set the amplitude of the output. This only works for
the small
and large filter settings. Since these filters operate on a history of
the audio
data it is possible for the output to be larger then the input. This
allows one to
adjust the output. The following functions have changed:

aflibConverter::initialize
aflibSampleRateCvt::setFactor

Existing programs will still work. If no extra parameter is specified
then 1.0
will be used as a default. In the past 0.95 was hardcoded as the gain
factor.

Bruce Forsberg

[Osalp-dev] Changes

[Bruce F. <for...@tn...>]

I have made two changes to CVS.

1. I have fixed the function aflibData::convertToSize. Many conversions
were not correct. Especially when the data endian was different than the
hosts data endian. This is now fixed.

2. Changed aflibConverter and associated classes to use base types
instead of
WORD, UWORD, HWORD, and UHWORD. These cause a conflict with windows. If
you
use these in your software you will need to change them to:

WORD - int
UWORD - unsigned int
HWORD - short
UHWORD - unsigned short
BOOL - bool


Bruce Forsberg

[Osalp-dev] New data type

[Bruce F. <for...@tn...>]

I have added to the aflib library a new data size type. It is
called AFLIB_DATA_32S. It is for audio data that needs
32 bit signed data. It has been checked into CVS.

Bruce Forsberg

[Osalp-dev] New class added

[Bruce F. <for...@tn...>]

I have added a new class to the aflib library. It is
called aflibAudioMemoryInput. It is designed to be
used at the start of an audio chain and provides the
ability for the user to insert audio data from memory
into an audio chain. It has been checked into CVS.

Bruce Forsberg

[Osalp-dev] library now compiles with gcc 3.0

[Bruce F. <for...@tn...>]

Thanks to Per =D8yvind Hvidsten, the library now
compiles with gcc 3.0. This has been checked into
CVS.

Bruce Forsberg

[Osalp-dev] email address change

[Bruce F. <for...@tn...>]

Just a quick note to let you all know that I have
changed my email address. I changed the files in
CVS to reflect my new email address as well. It is

for...@tn...


Thanks,
Bruce Forsberg