waave-user Mailing List for waave

2015-10-02 10:29 GMT+02:00 Tom Lawson <mr....@gm...>:

> Hi all,
> I am trying to download the minGW32 compiled waave library but when I
> follow the link on the waave website it appears the file is mising on
> sourceforge. I have tried all afternoon to compile it myself and was
> wondering if anyone knew where I could get that file.
>
> Thank you
>
> *Tom Lawson*
>
> ----------------------------------------------------------------------------------------------------------------------------
>
> Please consider the environment before printing this email.
>
> *Main Email*:  *to...@to... <to...@to...>*
> *YouTube Email*:  *t <http://goog_1416165716>**omb...@gm...
> <omb...@gm...>*
>
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Waave-user mailing list
> Waa...@li...
> https://lists.sourceforge.net/lists/listinfo/waave-user
>
>

Hello Tom !

I don't provide the MinGW build anymore because the SDL and FFMPEG
libraries are rebuild to often. You need to build the library yourself.

Read this following procedure :

http://waave.sourceforge.net/index.php?page=mingw

And give me the errors you get while compiling the library.

Maybe I can help you.

Baptiste.

Hi all,
I am trying to download the minGW32 compiled waave library but when I
follow the link on the waave website it appears the file is mising on
sourceforge. I have tried all afternoon to compile it myself and was
wondering if anyone knew where I could get that file.

Thank you

*Tom Lawson*
----------------------------------------------------------------------------------------------------------------------------

Please consider the environment before printing this email.

*Main Email*:  *to...@to... <to...@to...>*
*YouTube Email*:  *t <http://goog_1416165716>**omb...@gm...
<omb...@gm...>*

<mailto:waa...@li...>Looks like 'AVCODEC_MAX_AUDIO_FRAME_SIZE' is deprecated in recent versions of ffmpeg.  I am having trouble compiling waave lib with newer versions of ffmpeg.

waave_ffmpeg.c: In function ‘WV_resampleAudio’:
waave_ffmpeg.c:223:35: error: ‘AVCODEC_MAX_AUDIO_FRAME_SIZE’ undeclared (first use in this function)
waave_ffmpeg.c:223:35: note: each undeclared identifier is reported only once for each function it appears in
audio_decoder.c: In function ‘seekAudioStream’:
audio_decoder.c:817:33: error: ‘AVCODEC_MAX_AUDIO_FRAME_SIZE’ undeclared (first use in this function)
audio_decoder.c:817:33: note: each undeclared identifier is reported only once for each function it appears in
audio_decoder.c: In function ‘decodeAudio’:
audio_decoder.c:958:32: error: ‘AVCODEC_MAX_AUDIO_FRAME_SIZE’ undeclared (first use in this function)
audio_decoder.c: In function ‘WV_addAudioStream’:
audio_decoder.c:1233:18: error: ‘AVCODEC_MAX_AUDIO_FRAME_SIZE’ undeclared (first use in this function)
make[2]: *** [waave_ffmpeg.lo] Error 1
make[2]: *** [audio_decoder.lo] Error 1

2013/1/10 Shane Mueller <smu...@ob...>:
> Hello waave folks:
>
> I just released version 0.13 of the Psychology Experiment Building
> Language (PEBL, http://pebl.sourceforge.net), which will include support
> for movie and audio file playback via waave. PEBL is a programming
> language that is designed to run simple computerized experiments for
> psychology and neuroscience.  I've already used the waave  interface on a
> few studies in my own lab, and it worked perfectly--thanks. BTW, it uses
> SDL 1.2, not 2.0.
>
> PEBL gets 1000-2000 downloads per month, so I thought you'd be happy to
> know that waave will soon be on a lot of psychologists and neuroscientists
> computers.  WAAVE will be supported only on PEBL for windows and linux.  I
> haven't looked into building a framework for OSX, but it should be
> possible, right?
>
> There is one issue I've noticed but don't know how to deal with yet: to
> draw the screen, I have a set of SDL_surface structures that get copied to
> one another in sequence and eventually to the main window, using copy and
> SDL_FLip commands to render to the screen.  When I use waave,  the movie
> rendering goes on in the background on its own, outside my rendering
> steps.  If I try to issue my own drawing sequence while playback is
> happening (i.e., stopping the waave handler then doing my drawing, then
> starting waave again) , it causes jitter and flashes in the smoothness of
> the video rendering because the rendering misses an update. This makes it
> essentially impossible for me to update simple playback status bar
> rectangle (i.e., using sdl_gfx), or do other dynamic things while the
> video is playing without artifacts.  I'm guessing I'll need to customize
> the streaming object or some related handling code so that my screen
> rendering happens within that process, but this is a dark art to me.  Any
> pointers, especially involving working code, would be appreciated.
>
> For example, adding to the demo player something simple like a progress
> bar update using a couple bitmaps could be done in straight SDL, and would
> be really helpful to me.
>
> Thanks,
> Shane
>
> _______________________________________________
> Waave-user mailing list
> Waa...@li...
> https://lists.sourceforge.net/lists/listinfo/waave-user

Hi shane ! I will try to answer all the points ! I hope you will
understand my English....

First, thank you using waave and reporting your problems. Doing this
you have initiated the majority of waave's improvements ! Personally I
don't have the time for testing all the waave functionalities, so
thanks again !

Next I don't really understand what you mean about the waave's SDL
support. Since waave 2.01 you can compile it for SDL1.2 or SDL2.0. I
don't have a OSX system to try to build the library but with macport
you can probably easily compile waave with the corresponding SDL and
FFmpeg packages. The difficulty is to pack the binary and the
libraries in a mac ".app". May you know how to do this ? I don't know
how you have made your OSX version of the PEBL.

Concerning your question. The problem come from the SDL's YUV overlays
implementation. An overlay use a separate rendering pipeline and
render directly on the front buffer (if you use double buffering). So
the display car occur after the SDL_flip call even if you call
WV_refreshVideoFrame before. In theory you can't mix RGB surface and
YUV overlay rendering in the same space. So to solve your problem :

-> You can make your progress bar under the video frames and not over.
-> You can make a progress bar with an YUV overlay

-> Simplest method : I have added a new SDL streaming object that use
surfaces to stream the video. With this the rendering will occur in
the back buffer and you can flip when you want. But surface are 2
times slower than overlays (on my system the CPU load change from 6%
to 12%). Compile a linux and windows version of the waave-3.01 library
and say me if it solve you problem. Use :

WV_getStreamSurfaceObj (SDL_Surface *targetSurface, SDL_Rect
*destRect, int updateFlag)
WV_resetStreamSurfaceOutput (WVStreamingObject *streamObj, SDL_Surface
*targetSurface, SDL_Rect *destRect)
WV_freeStreamSurfaceObj (WVStreamingObject *streamObj)

(see the documentation)

Thanks
Baptiste.

Hello waave folks:

I just released version 0.13 of the Psychology Experiment Building
Language (PEBL, http://pebl.sourceforge.net), which will include support
for movie and audio file playback via waave. PEBL is a programming
language that is designed to run simple computerized experiments for
psychology and neuroscience.  I've already used the waave  interface on a
few studies in my own lab, and it worked perfectly--thanks. BTW, it uses
SDL 1.2, not 2.0.

PEBL gets 1000-2000 downloads per month, so I thought you'd be happy to
know that waave will soon be on a lot of psychologists and neuroscientists
computers.  WAAVE will be supported only on PEBL for windows and linux.  I
haven't looked into building a framework for OSX, but it should be
possible, right?

There is one issue I've noticed but don't know how to deal with yet: to
draw the screen, I have a set of SDL_surface structures that get copied to
one another in sequence and eventually to the main window, using copy and
SDL_FLip commands to render to the screen.  When I use waave,  the movie
rendering goes on in the background on its own, outside my rendering
steps.  If I try to issue my own drawing sequence while playback is
happening (i.e., stopping the waave handler then doing my drawing, then
starting waave again) , it causes jitter and flashes in the smoothness of
the video rendering because the rendering misses an update. This makes it
essentially impossible for me to update simple playback status bar
rectangle (i.e., using sdl_gfx), or do other dynamic things while the
video is playing without artifacts.  I'm guessing I'll need to customize
the streaming object or some related handling code so that my screen
rendering happens within that process, but this is a dark art to me.  Any
pointers, especially involving working code, would be appreciated.

For example, adding to the demo player something simple like a progress
bar update using a couple bitmaps could be done in straight SDL, and would
be really helpful to me.

Thanks,
Shane

2012/7/24 Shane Mueller <smu...@ob...>:
> Thanks--I'll try that.
>
> BTW,
> void WV_resetStreamOverlayOuput
>
> should probably be:
>
> WV_resetStreamOverlayOutput
>


This was corrected in waave-2.01. So download the latest version
(waave-2.02). Moreover since 2.01 you can set the target rectangle on
the screen surface with WV_getStreamOverlayObj() and
WV_resetStreamOverlayOutput() (and now 2.02 have
the "private", "extern C" and "const char*" correction).

Thanks for helping me to update the library !

Baptiste.

2012/7/23 Shane Mueller <smu...@ob...>:
>
> Thanks!  I did need to add the extern stuff to allow it to compile in c++.
>
> I now have it compiled  (SDL 1.2) and am able to load a movie that works
> in the demo program, but it segfaults within waave:
>
> Program received signal SIGSEGV, Segmentation fault.
> WV_refreshVideoFrame (event=0xbfffa260) at video_decoder.c:538
> 538         specialRefresh(event);
> (gdb) bt
>
> #0  WV_refreshVideoFrame (event=0xbfffa260) at video_decoder.c:538
>
>
> A little debugging and it looks like it really crashed on
>
>   WVStreamingBuffer* frameBuffer = videoStream->frameBuffer;
>
> within the  SpecialRefresh function.  I know it won't be much help, but I
> do all the following with the class that loads/plays the movie:
>
>     WV_waaveInit(WAAVE_INIT_AUDIO|WAAVE_INIT_VIDEO);
>     char* fname = (char*)(filename.c_str());
>     mStream = WV_getStream(fname);  //shouldn't this be const???
>
>     int streamType = WV_getStreamType(mStream);
>
>
>
> #if SDL_BYTEORDER == SDL_BIG_ENDIAN
>     rmask = 0xff000000;
>     gmask = 0x00ff0000;
>     bmask = 0x0000ff00;
>     amask = 0x000000ff;
> #else
>     rmask = 0x000000ff;
>     gmask = 0x0000ff00;
>     bmask = 0x00ff0000;
>     amask = 0xff000000;
> #endif
>
>     mSurface = SDL_CreateRGBSurface(SDL_SWSURFACE, width, height, 32,
>                                     rmask, gmask, bmask, amask);
>     mStreamObj = WV_getStreamOverlayObj(mSurface);
>
>     WV_setStreamingMethod(mStream,mStreamObj);
>
>     WV_loadStream(mStream);
>
>
> when I run it, I get the following on the console:
>
> [wmv3 @ 0x82dce40] Extra data: 8 bits left, value: 0
> Input #0, asf, from './tcp.wmv':
>   Metadata:
>     Application     : Windows Movie Maker 6.0.6002.18005
>     WM/ToolVersion  : 6.0.6002.18005
>     WM/ToolName     : Windows Movie Maker
>     WMFSDKVersion   : 11.0.6002.18049
>     WMFSDKNeeded    : 0.0.0.0000
>     IsVBR           : 1
>     VBR Peak        : 133
>     Buffer Average  : 441
>   Duration: 00:01:44.70, start: 0.000000, bitrate: 649 kb/s
>     Stream #0.0(eng): Audio: wmav2, 48000 Hz, 2 channels, s16, 192 kb/s
>     Stream #0.1(eng): Video: wmv3 (Main), yuv420p, 640x480, 482 kb/s, 30
> tbr, 1k tbn, 1k tbc
> [wmv3 @ 0x82dce40] Extra data: 8 bits left, value: 0
>
>
>
> Any ideas?  Other than using c++, it seems like the main difference is I'm
> using a SDL_Surface other than the screen--Am I doing it right?
>
> Thanks,
> Shane
>
>> 2012/7/23 Prunk Dump <pru...@gm...>:
>>> 2012/7/23 Shane Mueller <smu...@ob...>:
>>>> When compiling a c++ project I'm trying to use waave in, I get an error
>>>> regarding:
>>>>
>>>> expected unqualified-id before ‘private’
>>>>
>>>> which points to lines in the WAAVE.h file that define a member called
>>>> void* private (lines 284 and 513).
>>>>
>>>> 'private' is a reserved keyword in c++, and so can't handle this in .h
>>>> files it uses.  Maybe there is a way to tell the c++ compiler that the
>>>> .h
>>>> file is really  a plain-c .h file so it won't choke, but I don't know
>>>> how
>>>> to do that.  Instead, I tried changing the struct member name (to
>>>> 'privateX'), which required changing a half-dozen uses of that data
>>>> structure in streamingObject and streamOverlay files (I think both .c
>>>> and
>>>> .h files), and it no longer gives that error.  (I haven't yet succeeded
>>>> in
>>>> getting everything to work, but at least it no longer gives that
>>>> error!)
>>>>
>>>> Thanks!
>>>>
>>>> Shane
>>>>
>>>> p.s.; An unrelated stylistic issue; I noticed that  WV_GetStream(char*
>>>> filename) is not WV_GetStream(const char* filename).  I don't think
>>>> WV_GetStream should need to modify filename, so I'd expect filename to
>>>> be
>>>> const. Because it is not a const, I need to make a copy of my const
>>>> filename or cast it to a non-const.  Not a big deal, but maybe
>>>> something
>>>> to consider changing in a later revision.
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Live Security Virtual Conference
>>>> Exclusive live event will cover all the ways today's security and
>>>> threat landscape has changed and how IT managers can respond.
>>>> Discussions
>>>> will include endpoint security, mobile security and the latest in
>>>> malware
>>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>>>> _______________________________________________
>>>> Waave-user mailing list
>>>> Waa...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/waave-user
>>>
>>> The WAAVE.h file does not contain the
>>>
>>> extern "C" {
>>> ...
>>> }
>>>
>>> keyword. Have you tried to add it on the waave's header ? Or when you
>>> include it ? (like this)
>>>
>>> #include <SDL.h>
>>> extern "C" {
>>> #include <WAAVE.h>
>>> }
>>>
>>>
>>> This will be fixed shortly (and the const char* also ! thanks !)
>>
>>
>> No you're right ! The extern keyword don't change the problem ! I will
>> send a corrected version shortly ! Give me the other errors you get.
>>
>> Baptiste.
>>
>
>

Yes you can only use the screen surface. This is due to the
SDL_CreateYUVOverlay behavior (see the ffmpeg's documentation, this is
specified in the waave's reference). But for a SDL application, this
is not really a problem because you can set the target SDL_rect.

May I don't understand what you really want to do :)

Thanks!  I did need to add the extern stuff to allow it to compile in c++.

I now have it compiled  (SDL 1.2) and am able to load a movie that works
in the demo program, but it segfaults within waave:

Program received signal SIGSEGV, Segmentation fault.
WV_refreshVideoFrame (event=0xbfffa260) at video_decoder.c:538
538	    specialRefresh(event);
(gdb) bt

#0  WV_refreshVideoFrame (event=0xbfffa260) at video_decoder.c:538


A little debugging and it looks like it really crashed on

  WVStreamingBuffer* frameBuffer = videoStream->frameBuffer;

within the  SpecialRefresh function.  I know it won't be much help, but I
do all the following with the class that loads/plays the movie:

    WV_waaveInit(WAAVE_INIT_AUDIO|WAAVE_INIT_VIDEO);
    char* fname = (char*)(filename.c_str());
    mStream = WV_getStream(fname);  //shouldn't this be const???

    int streamType = WV_getStreamType(mStream);



#if SDL_BYTEORDER == SDL_BIG_ENDIAN
    rmask = 0xff000000;
    gmask = 0x00ff0000;
    bmask = 0x0000ff00;
    amask = 0x000000ff;
#else
    rmask = 0x000000ff;
    gmask = 0x0000ff00;
    bmask = 0x00ff0000;
    amask = 0xff000000;
#endif

    mSurface = SDL_CreateRGBSurface(SDL_SWSURFACE, width, height, 32,
                                    rmask, gmask, bmask, amask);
    mStreamObj = WV_getStreamOverlayObj(mSurface);

    WV_setStreamingMethod(mStream,mStreamObj);

    WV_loadStream(mStream);


when I run it, I get the following on the console:

[wmv3 @ 0x82dce40] Extra data: 8 bits left, value: 0
Input #0, asf, from './tcp.wmv':
  Metadata:
    Application     : Windows Movie Maker 6.0.6002.18005
    WM/ToolVersion  : 6.0.6002.18005
    WM/ToolName     : Windows Movie Maker
    WMFSDKVersion   : 11.0.6002.18049
    WMFSDKNeeded    : 0.0.0.0000
    IsVBR           : 1
    VBR Peak        : 133
    Buffer Average  : 441
  Duration: 00:01:44.70, start: 0.000000, bitrate: 649 kb/s
    Stream #0.0(eng): Audio: wmav2, 48000 Hz, 2 channels, s16, 192 kb/s
    Stream #0.1(eng): Video: wmv3 (Main), yuv420p, 640x480, 482 kb/s, 30
tbr, 1k tbn, 1k tbc
[wmv3 @ 0x82dce40] Extra data: 8 bits left, value: 0



Any ideas?  Other than using c++, it seems like the main difference is I'm
using a SDL_Surface other than the screen--Am I doing it right?

Thanks,
Shane

> 2012/7/23 Prunk Dump <pru...@gm...>:
>> 2012/7/23 Shane Mueller <smu...@ob...>:
>>> When compiling a c++ project I'm trying to use waave in, I get an error
>>> regarding:
>>>
>>> expected unqualified-id before ‘private’
>>>
>>> which points to lines in the WAAVE.h file that define a member called
>>> void* private (lines 284 and 513).
>>>
>>> 'private' is a reserved keyword in c++, and so can't handle this in .h
>>> files it uses.  Maybe there is a way to tell the c++ compiler that the
>>> .h
>>> file is really  a plain-c .h file so it won't choke, but I don't know
>>> how
>>> to do that.  Instead, I tried changing the struct member name (to
>>> 'privateX'), which required changing a half-dozen uses of that data
>>> structure in streamingObject and streamOverlay files (I think both .c
>>> and
>>> .h files), and it no longer gives that error.  (I haven't yet succeeded
>>> in
>>> getting everything to work, but at least it no longer gives that
>>> error!)
>>>
>>> Thanks!
>>>
>>> Shane
>>>
>>> p.s.; An unrelated stylistic issue; I noticed that  WV_GetStream(char*
>>> filename) is not WV_GetStream(const char* filename).  I don't think
>>> WV_GetStream should need to modify filename, so I'd expect filename to
>>> be
>>> const. Because it is not a const, I need to make a copy of my const
>>> filename or cast it to a non-const.  Not a big deal, but maybe
>>> something
>>> to consider changing in a later revision.
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Live Security Virtual Conference
>>> Exclusive live event will cover all the ways today's security and
>>> threat landscape has changed and how IT managers can respond.
>>> Discussions
>>> will include endpoint security, mobile security and the latest in
>>> malware
>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>>> _______________________________________________
>>> Waave-user mailing list
>>> Waa...@li...
>>> https://lists.sourceforge.net/lists/listinfo/waave-user
>>
>> The WAAVE.h file does not contain the
>>
>> extern "C" {
>> ...
>> }
>>
>> keyword. Have you tried to add it on the waave's header ? Or when you
>> include it ? (like this)
>>
>> #include <SDL.h>
>> extern "C" {
>> #include <WAAVE.h>
>> }
>>
>>
>> This will be fixed shortly (and the const char* also ! thanks !)
>
>
> No you're right ! The extern keyword don't change the problem ! I will
> send a corrected version shortly ! Give me the other errors you get.
>
> Baptiste.
>

2012/7/23 Prunk Dump <pru...@gm...>:
> 2012/7/23 Shane Mueller <smu...@ob...>:
>> When compiling a c++ project I'm trying to use waave in, I get an error
>> regarding:
>>
>> expected unqualified-id before ‘private’
>>
>> which points to lines in the WAAVE.h file that define a member called
>> void* private (lines 284 and 513).
>>
>> 'private' is a reserved keyword in c++, and so can't handle this in .h
>> files it uses.  Maybe there is a way to tell the c++ compiler that the .h
>> file is really  a plain-c .h file so it won't choke, but I don't know how
>> to do that.  Instead, I tried changing the struct member name (to
>> 'privateX'), which required changing a half-dozen uses of that data
>> structure in streamingObject and streamOverlay files (I think both .c and
>> .h files), and it no longer gives that error.  (I haven't yet succeeded in
>> getting everything to work, but at least it no longer gives that error!)
>>
>> Thanks!
>>
>> Shane
>>
>> p.s.; An unrelated stylistic issue; I noticed that  WV_GetStream(char*
>> filename) is not WV_GetStream(const char* filename).  I don't think
>> WV_GetStream should need to modify filename, so I'd expect filename to be
>> const. Because it is not a const, I need to make a copy of my const
>> filename or cast it to a non-const.  Not a big deal, but maybe something
>> to consider changing in a later revision.
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Waave-user mailing list
>> Waa...@li...
>> https://lists.sourceforge.net/lists/listinfo/waave-user
>
> The WAAVE.h file does not contain the
>
> extern "C" {
> ...
> }
>
> keyword. Have you tried to add it on the waave's header ? Or when you
> include it ? (like this)
>
> #include <SDL.h>
> extern "C" {
> #include <WAAVE.h>
> }
>
>
> This will be fixed shortly (and the const char* also ! thanks !)


No you're right ! The extern keyword don't change the problem ! I will
send a corrected version shortly ! Give me the other errors you get.

Baptiste.

2012/7/23 Shane Mueller <smu...@ob...>:
> When compiling a c++ project I'm trying to use waave in, I get an error
> regarding:
>
> expected unqualified-id before ‘private’
>
> which points to lines in the WAAVE.h file that define a member called
> void* private (lines 284 and 513).
>
> 'private' is a reserved keyword in c++, and so can't handle this in .h
> files it uses.  Maybe there is a way to tell the c++ compiler that the .h
> file is really  a plain-c .h file so it won't choke, but I don't know how
> to do that.  Instead, I tried changing the struct member name (to
> 'privateX'), which required changing a half-dozen uses of that data
> structure in streamingObject and streamOverlay files (I think both .c and
> .h files), and it no longer gives that error.  (I haven't yet succeeded in
> getting everything to work, but at least it no longer gives that error!)
>
> Thanks!
>
> Shane
>
> p.s.; An unrelated stylistic issue; I noticed that  WV_GetStream(char*
> filename) is not WV_GetStream(const char* filename).  I don't think
> WV_GetStream should need to modify filename, so I'd expect filename to be
> const. Because it is not a const, I need to make a copy of my const
> filename or cast it to a non-const.  Not a big deal, but maybe something
> to consider changing in a later revision.
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Waave-user mailing list
> Waa...@li...
> https://lists.sourceforge.net/lists/listinfo/waave-user

The WAAVE.h file does not contain the

extern "C" {
...
}

keyword. Have you tried to add it on the waave's header ? Or when you
include it ? (like this)

#include <SDL.h>
extern "C" {
#include <WAAVE.h>
}


This will be fixed shortly (and the const char* also ! thanks !)

When compiling a c++ project I'm trying to use waave in, I get an error
regarding:

expected unqualified-id before ‘private’

which points to lines in the WAAVE.h file that define a member called
void* private (lines 284 and 513).

'private' is a reserved keyword in c++, and so can't handle this in .h
files it uses.  Maybe there is a way to tell the c++ compiler that the .h
file is really  a plain-c .h file so it won't choke, but I don't know how
to do that.  Instead, I tried changing the struct member name (to
'privateX'), which required changing a half-dozen uses of that data
structure in streamingObject and streamOverlay files (I think both .c and
.h files), and it no longer gives that error.  (I haven't yet succeeded in
getting everything to work, but at least it no longer gives that error!)

Thanks!

Shane

p.s.; An unrelated stylistic issue; I noticed that  WV_GetStream(char*
filename) is not WV_GetStream(const char* filename).  I don't think
WV_GetStream should need to modify filename, so I'd expect filename to be
const. Because it is not a const, I need to make a copy of my const
filename or cast it to a non-const.  Not a big deal, but maybe something
to consider changing in a later revision.

You can now download the waave's MinGW development library on the
"download" section of the website.

(see http://waave.sourceforge.net )

Detailed installation instruction can be found at the same page. You
can also download a waave demo here :

http://sourceforge.net/projects/waave/files/waave-demo/

You can now stream video using sdl 2.0 renderers ! See the new waave's
streaming objects in the waave reference. A video player using
SDL_Renderer can be found in the test/ folder (waaveplayer20.c).

http://waave.sourceforge.net

Le mardi 17 juillet 2012, Shane Mueller a écrit :

> Has anybody tried getting waave work on windows and/or OSX?
>
> Thanks,
> Shane Mueller
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Waave-user mailing list
> Waa...@li... <javascript:;>
> https://lists.sourceforge.net/lists/listinfo/waave-user
>

I will give how to compile waave on windows soon. I never tried to make it
works on macos

Has anybody tried getting waave work on windows and/or OSX?

Thanks,
Shane Mueller