[uae] Re: Source code snapshot
- From: SukkoPera <enjoy.the.silence@xxxxxx>
- To: uae@xxxxxxxxxxxxx
- Date: Wed, 15 Mar 2006 01:19:50 +0100
Hi Rich, thanks for the quick reply!
Alle 07:06, lunedì 13 marzo 2006, Richard Drummond ha scritto:
> Hi Giorgio
>
> You certainly shouldn't see a 1 second lag!
>
> What have you got sound_maxbuf= set to in your config?
I've started with a brand new configuration (i.e.: rm .uaerc), and now the
situation is better: on 32-bit Slackware, everything is fine. On 64-bit
Ubuntu, there is still a small lag. I've tried lowering sound_maxbuf to 4096,
but it made no difference. I don't know how alsa is configured under ubuntu.
I just know that I got no asoundrc file, neither in /etc nor in my homedir. I
tried killing esd and the gnome mixer applet, but the situation is still the
same. BTW, I am no gnome expert, so if there is more to kill just tell me.
BTW, I have two soundcards on my computer, how do I tell uae which one to use?
> > Also, how do I save and restore states, now that this should be
> > supported?
>
> It's half-supported at the moment. ;-)
> Then you can press F12+Numpad 0 to save state to that file and F12+Right
> Shift+Numpad 0 to load from that file.
There's a small problem in here, with that most F12 shortcuts don't work
anymore. The only one which is still working is F12+Q to quit emulation,
while I can't switch to fullscreen anymore (with F), nor use this state
saving/loading functions. This happens both on Slackware and Ubuntu.
Two more things:
- The CVS doesn't build.
- The default configuration sets x11.use_mitshm=true. If I don't switch it to
false, uae creashes right before the initial emulation unpausing, with an
X-window error:
(...)
Using MIT-SHM extension.
Sound driver found and configured for 16 bits at 44100 Hz, buffer is 4096
bytes
reset at 0
PAL mode, 50Hz (h=227 v=312)
The program 'UAE' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
(Details: serial 42 error_code 2 request_code 146 minor_code 3)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Again, this is happening both on Slackware and Ubuntu.
Take care!
--
Giorgio
------------ Slackware GNU/Linux 10.2 user -------------
ICQ: 10238408
MSN: sukkopera@xxxxxxxxxx
Web: http://www.nogood.it/sukkopera/
--
Giorgio
------------ Slackware GNU/Linux 10.2 user -------------
ICQ: 10238408
MSN: sukkopera@xxxxxxxxxx
Web: http://www.nogood.it/sukkopera/
Other related posts:
