Thread: [ReZound-users] drop outs in version 0.8.3beta
Status: Beta
Brought to you by:
ddurham
From: Gerhard Z. <Gerhard.Zintel@Mrs-Thomas.de> - 2003-07-17 21:17:18
|
Hello Davy, after a bit playing around with the new version (0.8.3beta) I have realized= =20 the following. Moving the mouse pointer during play back causes drop outs=20 from time to time. Moreover changing into another window makes things worse= =2E=20 =46rom time to time there are drop outs without doing anything. I have not found this draw back in version 0.7.??. Playing with the old=20 version on the same system (AMD Duron, 800 MHz, 256 MB Memory) is much more= =20 "stable". Switching off the level meter, the phase meter and the analyzer makes thing= s a=20 bit better but not much.=20 Pressing the pause button stops playing but the information=20 "Playing: 00:01:34s"=20 is flickering all the time. There seems to be a lot of screen update althou= gh=20 no new information is to be shown. You can not see this flickering with the= =20 last version (0.7). Maybe you'll get an idea where this high load does come from. Gerhard =2D-=20 =2D---------------------------------------------------------------- Gerhard Zintel Gerhard.Zintel<at>mrs-thomas.de =2D---------------------------------------------------------------- |
From: Davy D. <dav...@ar...> - 2003-07-17 22:16:11
|
This is very dependant on the version of FOX you're using. He's actively changing/fixing the amount of CPU that is involved in even waving the mouse around on the screen (a goofy issue he's working on). Also, are you using either of the two pre-compiled binaries? If not, try either of those if you can. They were compiled with the latest FOX. I am going to work on the drop-outs by attempting to buffer up much more data to the sound card that I currently am. Buffering is easy, but the harder part is knowing where to accurately draw the play position since you've already written the data to the sound card, you don't quite know what's coming out of the speakers. Now, you can very closely calculate that by knowing the sample rate of playback and comparing that with the current time (you'd know how much of the buffered data has been played since last time). But the issue becomes even MORE complicated when you consider that looping is a possibility.. and the loop points may have changed since the last time you drew the play position. I'm simply going to have to keep track of the positions in the data that have been buffered and each time I draw the play position determine how many of those positions have expired since the last time and draw the most recent one (or something like that). Currently, you can probably improve the drop-outs by editing ~/.rezound/registry.dat and change DesiredOutputBufferCount to something much higher (like 10 or 20). This will make the play position much less accurate, but the gaps should go away. -- Davy On Thu, 2003-07-17 at 16:15, Gerhard Zintel wrote: > Hello Davy, > > after a bit playing around with the new version (0.8.3beta) I have realized > the following. Moving the mouse pointer during play back causes drop outs > from time to time. Moreover changing into another window makes things worse. > >From time to time there are drop outs without doing anything. > > I have not found this draw back in version 0.7.??. Playing with the old > version on the same system (AMD Duron, 800 MHz, 256 MB Memory) is much more > "stable". > > Switching off the level meter, the phase meter and the analyzer makes things a > bit better but not much. > > Pressing the pause button stops playing but the information > "Playing: 00:01:34s" > is flickering all the time. There seems to be a lot of screen update although > no new information is to be shown. You can not see this flickering with the > last version (0.7). > > Maybe you'll get an idea where this high load does come from. > > Gerhard |