similar to: Sound glitch when using libvorbisfile and libao

How can this problem be reproduced? If you have an specific .ogg file that gives problems it would be helpful to have them so we can try to reproduce them. Kind regards, Gunter. On So, Jun 14, 2015 at 7:10 , Marshall Mason <marshallmason2 at gmail.com> wrote: > Hi there, > I've been grappling with this for some time, so I'm finally breaking > down and trying this

Hi Gunter, Thank you for your quick response. As I mentioned in the email, I cannot dependably reproduce it. It comes and goes, and I just have to wait for it to come up before I can try to debug it. I've found it tends to happen when I've been taxing my sound driver, but this isn't consistent either. My inability to consistently reproduce this has made it a nasty bug for me to

Hi Gunter, I think this problem started happening when I upgraded from Debian Wheezy to Debian Jessie. If nothing looks amiss in my code, it probably is a sound driver problem. But since it works 100% of the time in ogg123, I feel I must have missed some corner case. My audio driver is almost always active. I usually have my music player going in the background when I do my testing. The problem

Hi Gunter, I've solved the sound glitch. Since it was hard to reproduce, it took me a while, but I eventually figured it out. What I needed to do was fill the buffer with more data before handing it off to ao_play. It requires lots of bookkeeping, pointer arithmetic, and a sufficiently large buffer. First, the bigger buffer. I just pulled this code from ogg123: #define PRIMAGIC

Dear Marshall, I spent most of yesterday finding out that wxWidget's wxStringArray sometimes drops whitespace in a new entry depending on the character the last entry ended with - so I know what you mean. But your code looks clean and after listening to the bell for what felt too long I started using your program as a regular audio player. I too assume the problem lies in the audio driver

I am wondering if buffer size for my decoding to pcm can be predicted dependably as follows. So far, the one problem I have had is when I have played a file of only about 5k. The buffer was a little less than 10% too small. I "solved" that by padding the result with an extra 20 percent. However, I have been told that I should be able to rely on the value of ov_pcm_total. char*

Hi, I've just installed libao-1.1.0 on a new Debian install. I also have alsa 1.0.27.1 installed. Debian is running under VirtualBox 4.2.12 under OSX 10.6.8, on a MacBookPro. libao does not work in stereo for the sampling rate of 44100, but it does for 8000, 11025, 22050and 48000. When I send it two channel output at a sampling rate of 44100, the result includes what sounds like skips,

Xiph.Org is pleased to announce the release of libao version 1.1.0. This release consists of minor functionality improvements and several important bugfixes. The 1.1.0 API/ABI is fully backwards compatible with 1.0.0; All users of libao are encouraged to upgrade to the 1.1.0 release. Bugfixes in this release include: * Fix Mac OS X AUHAL support to properly handle suspend/wakeup,

Xiph.Org is pleased to announce the release of libao version 1.1.0. This release consists of minor functionality improvements and several important bugfixes. The 1.1.0 API/ABI is fully backwards compatible with 1.0.0; All users of libao are encouraged to upgrade to the 1.1.0 release. Bugfixes in this release include: * Fix Mac OS X AUHAL support to properly handle suspend/wakeup,

Hello Hope you don't mind another newbie's question. Further to GIE's email about problems compiling decoder_example.c example (MS VC 7) using debug static ogg/vorbis libs, we'd appreciate any help getting the example files to compile on MS VC 6. The zip files we have downloaded are: libao-0.8.2.zip libogg-1.0rc3.zip libvorbis-1.0rc3.zip vorbis-sdk-1.0rc3.zip

Hello Vorbis Developers. I'm in the proccess of writing an OggVorbis audio player using libao and libvorbisfile. I've greatly appreciated the simplicity of the API and good documentation with the souce of the libraries. I've descided that I really want a mixer on my player, and I'm unsure how to best go about it. LibAO (unless I'm absolutely blind) doesn't

[Oops. Sent this to the wrong list.] Kenneth already appears to have committed a byte order fix for the WAV output driver. Attached is a patch to fix byte order in the OSS and ALSA drivers. The other output drivers seem to just use the native byte order (which libvorbisfile uses). As I do not have anything but Linux systems on Intel hardware at my disposal, I would really appreciate it if

Again, Hi All, Thanks for your replies. I probably should've mentioned that I'm not subscribed to the list but I found your answers on the archives. I just wanted to go on record and mention that I do in fact have all the original CD's and that by re-encoding I meant repeating the entire process of ripping the original CD's (with cdparanoia (of course ;)) and then encoding them

Hi All, For my new file (and thus mp3) server I've decided to switch completely to Ogg Vorbis. This means having to reencode ~30GB worth of 128Kb MP3's, but i figured that it would all be worth the effort. So I downloaded the sources for libogg, libvorbis and vorbis-tools and fired up my trusty old compiler. libogg and libvorbis built and installed like a charm. Not so for

I have a test program that loads an AIFF or WAV file with libsndfile and plays then using libao. After running around in circles for a while, I found and fixed the problem, but I'm still confused as to why the solution works. Would someone please explain this to me so I don't trip over this again later in my project? I used sf_open_fd() to get a SNDFILE* pointer and an AF_INFO

Ok, I managed to compile the Ogg and Vorbis libs. Then, after modifying the file audio_out.c as follows: original: #include <dlfcn.h> modified: #include <win32/include/dlfcn.h> I was able to (finally!) compile libao. Then I tried to compile the module vorbis-tools, but uninvited problems came to my party. [...] > /usr/bin/ld: multiple definitions of symbol _getopt >

While trying to compile libao 0.8.0 under OS X 10.1, I got the following problems: > [localhost:ecc/Sources/libao-0.8.0] root# ./configure > creating cache ./config.cache > checking for a BSD compatible install... /usr/bin/install -c > checking whether build environment is sane... yes > checking whether make sets ${MAKE}... yes > checking for working aclocal... found >

Why has ao been changed so that there are now two open() functions ? IMHO the original ao_open() was fine - if you wanted to set the filename for output, you could add an option via ao_append_option and if you wanted to avoid overwriting an existing file, you could stat() it yourself. Having ao_open_live() and ao_open_file() just makes more work for the user of the library for no gain, AFAICT.

Why has ao been changed so that there are now two open() functions ? IMHO the original ao_open() was fine - if you wanted to set the filename for output, you could add an option via ao_append_option and if you wanted to avoid overwriting an existing file, you could stat() it yourself. Having ao_open_live() and ao_open_file() just makes more work for the user of the library for no gain, AFAICT.

I'm working on getting the Darwin/Mac OS X port of Vorbis up and running again and have run into problems building libvorbisfile. I have installed the latest libtool (1.3.5) and modified it to handle Darwin/Mac OS X better (to create shared libraries, dylibs, that can be linked against other dylibs instead of creating bundles which cannot be used as input to the linker). But, when it tries