July 25, 2008  
1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31

[01:07:05] *** barra_ has quit IRC
[01:35:01] *** Proteus has joined #openal
[01:35:01] *** ChanServ sets mode: +v Proteus
[01:49:20] *** Proteus_ has quit IRC
[01:58:59] *** wild13 has quit IRC
[02:00:24] *** wild13 has joined #openal
[02:00:24] *** ChanServ sets mode: +v wild13
[02:30:59] *** wild13 has quit IRC
[03:16:42] *** makr has quit IRC
[05:45:47] *** wild13 has joined #openal
[05:45:47] *** ChanServ sets mode: +v wild13
[07:19:01] *** wild13 has quit IRC
[10:53:23] *** barraAway has joined #openal
[10:53:23] *** ChanServ sets mode: +v barraAway
[10:54:33] *** barraAway is now known as barra_
[11:24:24] * KittyCat is away: sleep
[16:01:09] *** kb1ooo has joined #openal
[16:01:09] *** ChanServ sets mode: +v kb1ooo
[16:54:29] *** Rain|code has quit IRC
[18:55:38] <Rivorus> (3:07:21 PM) KittyCat: Rivorus, it can. but you'd manually need to split the 5.1 buffer into 6 seperate streams
[18:55:38] <Rivorus> (3:07:43 PM) KittyCat: alSourcePlayv is gauranteed to start a specific number of sources at the same time
[18:55:54] <Rivorus> so they're guaranteed to play at the same time, even in all implementations?
[18:56:06] <Rivorus> as in perfectly in sync?
[18:56:40] <Rivorus> cuz i dont see that in the programmers guide at least
[18:57:35] <Rivorus> ill probably do that anyway though, thanks
[19:29:26] *** barra_ is now known as barraAway
[20:23:07] *** barraAway is now known as barra_
[21:14:35] <KittyCat> Rivorus, it says in the spec: "The functions [alSourcePlay, etc] are also available as a vector variant, which guarantees synchronized operation on a set of sources."
[21:22:44] * KittyCat is back.
[21:37:24] *** juanmabc has joined #openal
[21:37:24] *** ChanServ sets mode: +v juanmabc
[22:00:18] <Rivorus> cool thanks
[22:00:36] <Rivorus> i always just refer to the programmers guide but it seems to leave out stuff like that :/
[22:01:45] <KittyCat> yeah, having both on hand is handy. some things the spec misses are in the guide, and some things not in the guide are in the spec.
[22:05:46] <Rivorus> yer not a sa goon are you?
[22:06:57] <KittyCat> no
[22:08:03] <Rivorus> ah, cuz just 2 weeks ago i posted on sa asking if people had experience with libavcodec and libavformat because i was trying to use it with openal
[22:08:36] <Rivorus> and then all of a sudden a few days later on the mailing list i saw the ffmpeg post
[22:09:36] <KittyCat> heh. nah, I had a need for using ffmpeg through openal myself in a project. the code I made came out nice so I fixed it up, made it C (from C++), and gave it out for people to benefit from
[22:11:12] <Rivorus> ya thanks for that. i only wish i didnt decide to use ffmpeg until after your post because i had already devoted a few hours to getting an implementation up based on the [somewhat poor] ffmpeg documentation/examples
[22:12:44] <KittyCat> heh. I tend to avoid doxygen-like docs. it's not too bad as a reference, but not a library documentation
[22:13:52] <Rivorus> ya
[22:36:29] *** qknight has quit IRC
[22:36:32] *** qknight has joined #openal
[22:36:32] *** ChanServ sets mode: +v qknight
[22:40:57] *** qknight has quit IRC
[22:46:54] *** qknight has joined #openal
[22:46:54] *** ChanServ sets mode: +v qknight
[23:51:45] *** kb1ooo has quit IRC
[23:58:38] *** Rivoru1 has joined #openal
[23:58:38] *** ChanServ sets mode: +v Rivoru1

top