Displaying 20 results from an estimated 1000 matches similar to: "[vorbis] libao on OS X"
2001 Nov 05
2
libao on OS X
OK, wanted to check out the macosx driver for libao on me new iBook.
Everything compiles beautifully (given some utils from the fink project,
like automake), but...
but the dynamic plugin system is broken.
1) on OS X, dll's en in .dylib, not .so, as is hardwired in. this should
be an easy fix.
2) dlopen chokes on opening the .dylib files...so the plugin is never
loaded. i know not enought
2001 Nov 05
2
libao on OS X
OK, wanted to check out the macosx driver for libao on me new iBook.
Everything compiles beautifully (given some utils from the fink project,
like automake), but...
but the dynamic plugin system is broken.
1) on OS X, dll's en in .dylib, not .so, as is hardwired in. this should
be an easy fix.
2) dlopen chokes on opening the .dylib files...so the plugin is never
loaded. i know not enought
2001 Nov 05
1
libao and OS X
I tried sending this once, but it appears my school is having mail server
issues.
I've been playing with libao on OS X; I wanted to check out the macosx
plugin for it, see if I could bend it to my will. Given some utilities
from the fink project (automake comes to mind) I was able to compile it
just fine. But, there was a problem. It cannot load dynamic plugins!
The first reason I found
2001 Nov 05
1
libao and OS X
I tried sending this once, but it appears my school is having mail server
issues.
I've been playing with libao on OS X; I wanted to check out the macosx
plugin for it, see if I could bend it to my will. Given some utilities
from the fink project (automake comes to mind) I was able to compile it
just fine. But, there was a problem. It cannot load dynamic plugins!
The first reason I found
2001 Nov 05
0
libao and other things
Oh boy. My. Re: the gratuitous spamming of the two vorbis groups all I can
say is "oops", "damn", and "I'll be far more careful in the future when
the mailserver is acting flaky". Sorry.
But, back to the business at hand, if you aren't tired of it already =)
One David Gatwood mentioned that there is a libcompat parallel for dealing
with dylibs...does
2001 May 21
1
RE: Presales Question - Customer Service (fwd)
here's the reply from Diamond/SONICblue re: ogg vorbis and rio products.
have fun
dongoodman
%--------------------------------------------deg3@ra.msstate.edu| |bleu|
|`I invented the term 'object oriented', pobox 2516| |----|
|and I can tell you mississippi state ms| | () |
/. |I did not have C++ in mind.'
2001 Oct 23
1
Apple iPod
If you haven't seen, Apple has just announced a portable mp3 player (iPod)
(www.apple.com).
Can't find anything with a cursory search at Apple's Development Center
(developer.apple.com), but I wonder if it can be upgraded to support
Vorbis...and what it would take. Prelimenary thoughts? I know this is a
topic that comes up over and over again on this list, but with Apple
suddenly
2001 Oct 29
2
vorbis players (or lack of) for mac
Perhaps the devel list would be better, but a) i'm not subscribed to it
just now and b) I'm lazy (dons flame-retardant clothing)...
frankly, i'm rather tired of the lack of free ogg vorbis players for Mac
OS; it doesn't look like iTunes is going to support the format anytime
soon (and i have some real issues with its interface, too)...so, since
I've decided to learn Mac OS
2001 Jan 22
3
several (different and seperate) compiling problems
I thought I had seen something about this earlier, but a search through
the archives revealed nothing...
first problem:
Under Windows ME, using VC++6 (sp4), VC does not recognize the project
files in the beta3 source tarball as being valid project files. it complains
that they were not generated by VC++6, and would I like to create a wrapper
for these makefiles? It doesn't work. I checked
2001 Apr 12
5
Windows XP and MP3
if ya' haven't seen it already, check out:
http://www.canoe.ca/MoneyWSJ/wsj2-dow.html
ad, sad, sad. on many fronts. I don't begin to understand how this might
work; I suppose the MP3 degradation only applies to MS encoding software...
*shrug*
this may, however, provide a good leveraging point for Vorbis.
have fun
dongoodman
2001 Jul 13
6
as if you haven't seen this yet
i'm sure most of us are avid slashdot readers, but...
http://slashdot.org/article.pl?sid=01/07/13/1558239&mode=nested
have fun
dongoodman
%--------------------------------------------deg3@ra.msstate.edu| |bleu|
|`I invented the term 'object oriented', pobox 2516| |----|
|and I can tell you mississippi state ms| | () |
/. |I did
2000 Sep 05
1
[kcarnold@xiph.org: [xiph-cvs] cvs commit: vorbis/vorbis-tools/libao ao_alsa.c ao_oss.c audio_out.c audio_out.h]
remember kenneth that libao has moved to the "ao" module, so copy the
changes...
jack.
----- Forwarded message from "Kenneth C. Arnold" <kcarnold@xiph.org> -----
Delivered-To: cvs-outgoing@xiph.org
Delivered-To: cvs@xiph.org
To: cvs@xiph.org
Subject: [xiph-cvs] cvs commit: vorbis/vorbis-tools/libao ao_alsa.c ao_oss.c audio_out.c audio_out.h
Date: Tue, 5 Sep 2000
2000 Aug 12
1
libao patch: Minor clean up / Byte-order proposal
Here is a patch to fix the compiler warnings I mentioned earlier. I've
removed the byte-order changes that don't make sense. (Thanks Michael for
pointing out the error!)
As for the byte-order changes, since some output modules don't have the option
to set the sample byte-order, I would like to standardize libao and ogg123 on
native byte-order. Will this break the ao_wav.c patches
2001 May 08
2
libao AU driver
Hi,
I noticed there was some discussion on this list about the desire
for ogg123 to support output to stdout via Sun's .au file format, so
I decided to give implementing an AU driver for libao a shot. Here
is my first attempt.
To test the driver:
* Apply the patch below (against ao in CVS)
* Copy the attached ao_au.c into ao/src
* Run ao/autogen.sh, compile, and
2001 May 11
2
artifact bug status? / compiling under OpenBSD 2.8
Hi!
On March 17th I posted a message on this list concerning an artifact bug
in beta4 that is audible in all available bitrates. It was this rumbling
sound in the bass area. I made a demo clip, which still is available at
http://www.stud.uni-karlsruhe.de/~us87/ogg/vorbis_bassrumble_demo.rar
and that contains both the original .WAV and an .OGG @ 350kbps. This
archive is 2.1 MB large.
Today, I
2004 Oct 22
0
libao-0.8.5 patch
Hi!
There are some little inconvenience in libao-0.8.5.
- The biggest is may that:
the documentation and the header file declare the ao_file_extension function,
which give a hint for the file extension where the device is realy a sound
file. This function is missing.
-An other: the alsa 0.5 and the alsa 0.9+ drivers short name. It will be better
if the alsa 0.5's name will be alsa05 and the
2002 Jul 27
0
libao patch
I hope this is the right place to submit libao patches -- the
freshmeat page points to ogg vorbis as the homepage for libao.
Currently, at least on my system (SB Live Value!, ALSA .9 branch),
stuff going to alsa sounds *awful* because of too-small buffers.
mpg321 and similar programs are unusable, and none of them seem to
want to let you set the buffer size. This patch lets an environment
2009 Dec 01
1
ggplot legend for multiple time series
Hello All,
I am trying to create a legend for a black-white graph. The package I
use is ggplot2. It can add colors to the legend key but not line types.
Can you please help?
# example from Wickman (2009, ggplot2 - elegant graphics for data
analysis, page 109)
library(ggplot2)
huron <- data.frame(year=1875:1972, level=LakeHuron)
ggplot(huron, aes(year)) +
2010 Jan 31
0
Package ismev, gpd.fit, and interpretation for statistics of extreme values
Dear All,
I have a question about package "ismev", its function "gpd.fit", and
interpretation of the results.
I used the package ismev to do an extreme value analysis on a fire
dataset. Two variables are used in the analysis. The focal variable is
acreage burned per fire, ranging from 1 to 5000 acres per fire. In
total, there are 69,980 observations. The date covers
2009 Oct 06
0
[ao] Two patches for libao2
Hi Heikki,
So libao is currently not maintained upstream. In the appropriate IRC
channels I'm lead to believe that there are better libraries out there
that should be used instead.
If so many debian packages didn't link against it I would seriously
consider dropping it all together.
It doesn't sound like it's worth anyone's time maintaining libao
properly upstream. I do have