search for: bolson

Displaying 4 results from an estimated 4 matches for "bolson".

Did you mean: olson
2002 Jan 02
2
macosx (lots of little changes)
happy new year. a day off is a day to pick up a new project, so I wrestled my way through making ogg vorbis work on macosx. first, libao (not entirely a proper patch, but 2 source file diffs and a diff of a configure'd Makefile to one that works.): http://bolson.org/pub/libao-0.8.2-diff.tar.gz libogg and libvorbis compiled without incident. vorbis-tools were more complicated. I think this ERROR sholudn't be an error, maybe it should be a warning. My above changes mean libao doesn't need dlopen(). I was unable to get dlopen() working on macosx,...
2002 Jan 02
2
macosx (lots of little changes)
happy new year. a day off is a day to pick up a new project, so I wrestled my way through making ogg vorbis work on macosx. first, libao (not entirely a proper patch, but 2 source file diffs and a diff of a configure'd Makefile to one that works.): http://bolson.org/pub/libao-0.8.2-diff.tar.gz libogg and libvorbis compiled without incident. vorbis-tools were more complicated. I think this ERROR sholudn't be an error, maybe it should be a warning. My above changes mean libao doesn't need dlopen(). I was unable to get dlopen() working on macosx,...
2002 Jan 03
3
Suggestion for libvorbisfile: scaling
I've been experimenting with the ideas of Replay Gain[1] and find that ogg123 doesn't have a way of specifying the scaling applied to replayed samples (like -f in mpg123). Looking at libvorbisfile, I see no function exactly matching this possibly desirable behaviour. ov_read() scales by either 128 (byte output) or 32768 (word output), but there's nothing in between. ov_read_float()
2010 Sep 10
0
[LLVMdev] small patch for llvm-ld, script improvement
New to llvm and hopefully this will be a welcome small improvement. The shell script wrapper generated by llvm-ld only works when the current working directory is the same as where the script and the bitcode file is. This can be fixed pretty easily by putting `dirname $0`/ in front of the bitcode file name and should work as long as the bitcode and wrapper script live in the same directory.