[En-Nut-Discussion] Bug in NutSegReadCommit

[Harald Kipp]

Pavel,

it can't work. That's 16kByte/s and Internet often
hangs for more than just a second. Beside that,
streaming servers initially send a buffer of 100kByte
or more. Due to lack of memory, the old routines had
to through it away. The old "crap" worked reliably
up to 32kBit only, while the new VS1001K driver
can even stream 56kbit over GSM with a very good
connection.

Nevertheless, I'll check my changes to your code.
I remember, when writing it, I thought by myself
"Oh, let's do it this way. If it's wrong, Pavel will
protest". :-)

Harald

At 15:28 26.11.2004 +0100, you wrote:


>Harald Kipp wrote:
>
>>Pah! But the current version streams 128kbit streams
>>from the Internet for hours, which had been almost
>>impossible with this old crap unless you got a local
>>streaming server or a very good connection.
>
>Yes, I believe it works for streaming though I hve not thoroughly tested it.
>The problem I mentioned rather makes problems when separate MP3 files are 
>played one by one
>- the flushing at the end of a track does not work as it should.
>
>Pavel
>_______________________________________________
>En-Nut-Discussion mailing list
>En-Nut-Discussion at egnite.de
>http://www.egnite.de/mailman/listinfo.cgi/en-nut-discussion