Re: Re: being serious about the NG of zinf

Sam Varshavchik wrote:
> Ed Sweetman writes:
> 
>> the time and how to handle filling the buffer at the same time.  What 
>> we could do time the player on a loop that is run in the output plugin 
>> that queries the audio buffer waiting for a 2byte decrease from the 
>> max with initial time's starting at position given by the UI. That 
>> should be sufficient.
> 
> 
> I'm not sure Linux's /dev/dsp has this kind of granularity.  As I 
> recall, you get to choose audio block sizes as an even power of two, I 
> forget the minimum.  And you specify the number of audio blocks the 
> driver will allocate, and dsp will only tell you when it played each block.
> 

/dev/dsp referring to OSS i assume, i'm referring to requesting the 
current buffer size as opposed to the allocated buffer size.  The 
difference being 2bytes when we then go and repeat our read cycle and 
thus update the time and position. I'm not saying to allocate 2 bytes 
only. We should be able to ask how much data is in the buffer and 
compare to the allocated, cant we?  I haven't worked with oss much at 
all, been using alsa since before 2.3 got going.



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf