ok, thanks. Yeah. The problem only seems to happen with some machines.
I think it's related to certain inbuilt sound cards. On Mon, Mar 24, 2008 at 10:31 AM, Bo Jangeborg <[EMAIL PROTECTED]> wrote: > Did try * 6, now I even tried 1024*9, still sounds awful. > Have you tested 44k output on XP ? > > René Dudfield skrev: > > > > Thanks for your testing Bo. > > > > I guess if you used 1024 * 3 * 2 for 44K sound then it wouldn't be > > scratchy too. This is because you need twice the buffer size to avoid > > scratchyness as compared to 22K sound - which is half the size of the > > 44K sound. > > > > Thanks for the tip about the Sound object not raising an exception. > > I'll add a few more unit tests for the sound stuff. > > > > > > cheers, > > > > > > On Mon, Mar 24, 2008 at 8:27 AM, Bo Jangeborg <[EMAIL PROTECTED]> wrote: > > > >> The buffer setting doesn't seem to make a differens. > >> The key seem to be the sampling rate. Lots of scratching at 44k sound > >> but OK at 22k. But even then I get scratches if I start some way into > >> the music > >> rather then at the start. The later problem I had in pygame 1.7 too. > >> > >> In pygame 1.7 music worked OK in Vista at 44k. > >> I have tried both ogg and mp3 in pygame 1.8. > >> Have you tried playing music at 44k on XP machines? Maybe this is a more > >> general problem. > >> > >> Another thing that seem to have changed is that if a path to a sound file > >> is wrong it doesn't cause an exception. Instead it returns an empty > >> sound object.. > >> Is that really intended ? > >> > >> > >> > >> René Dudfield skrev: > >> > >> > >> > >>> yeah, I think generally increasing the buffer size helps people. > >>> > >> > > >> > For rc5 I increased the default buffer size to 1024 * 3... which has > >> > worked in the past to fix things up on most peoples computers. > >> > > >> > Unfortunately increasing it over 3*1024 starts to make the sound lag > >> > noticable... at least to me. So I think it will have to be a per > >> > game, or per user setting until it gets fixed propperly. > >> > > >> > > >> > If someone could lodge a bug report at: > >> > http://bugzilla.libsdl.org/ > >> > > >> > That would be greatly appreciated. > >> > > >> > I think it's best to fix this properly in SDL_mixer... but for now the > >> > work around is to increase the default buffer size on a per computer > >> > basis. > >> > > >> > cheers, > >> > > >> > > >> > > >> > On Sun, Mar 23, 2008 at 8:54 AM, FT <[EMAIL PROTECTED]> wrote: > >> > > >> >> Hi! > >> >> > >> >> I think there was also an issue of pre-init for any init would > wipe out > >> >> any settings. So the pre-init was setup to prevent the loss of any > settings > >> >> besides the size of the buffer to hold the data. The issue comes up > all the > >> >> time and is in the specs on the mixer and sound. Where it recommends > >> >> increasing the buffer size and warns about the init of pygame and > any mixer > >> >> settings. > >> >> > >> >> Bruce > >> >> > >> >> > >> >> > >> >> > >> >> Did you get scratchy sound playback with the same application on the > >> >> same computer but pygame 1.7? > >> >> > >> >> does it make a difference if you set the SDL_AUDIODRIVER environment > >> >> string to waveout ? > >> >> > >> >> On Sat, Mar 22, 2008 at 6:37 AM, Bo Jangeborg <[EMAIL PROTECTED]> > wrote: > >> >> > I have just tried the RC5 build from > >> >> > http://www3.telus.net/len_l/pygame.htm . > >> >> > Graphicly everything seem to work well so far but the music output > >> >> > sounds really awful. Very scratchy sound. > >> >> > I am running on python 2.5 , Windows Vista, and the machine is > >> >> > an Intel core 2 cpu 6700 2.66 Ghz. Soundcard is a Soundblaster > X-Fi. > >> >> > > >> >> > My standard setting is pygame.mixer.pre_init(44100, -16, 2, 2048) > >> >> > Been trying different setting but it does not sound good, default > >> >> settings > >> >> > was a bit better but still very scratchy. Any ideas ? > >> >> > > >> >> > Regards > >> >> > Bo Jangeborg > >> >> > > >> >> > >> >> > >> >> > >> >> > >> >> -- > >> >> No virus found in this incoming message. > >> >> Checked by AVG. > >> >> Version: 7.5.519 / Virus Database: 269.21.8/1338 - Release Date: > 3/21/2008 > >> >> 5:52 PM > >> >> > >> >> > >> >> > >> > > >> > > >> > >> > >> > > > > > >
