Hi! Before I write a bugreport, I'd like to ask the community if they can confirm this issue. First of all: You maybe should know sth. about my setup. It's an ASUS A8V Deluxe Board with an AMD Athlon64 3000+, running 64studio 3.0 Beta3. I'm using (guess it's) a Matrox G400 Dual-Head graphic adaptor (doesn't matter - same problem with nVIdia 5200 FX) with an Acer LCD on Port 1 and an EIZO CRT on Port 2. The very special about my setup is, that one monitor is on top of the other. This is because my computer with the LCD is build into a 19''-rack - call it a very heavy laptop with PCI-expansion-slots. :) When I'm at home, I'm putting the CRT on the rack, so the LCD is below the CRT.
I configured the monitors with displayconfig-gtk. Got a nice big Gnome-Desktop. But if I start Ardour, the main window doesn't seem to like this config. Normally I like to put the mixer window on my LCD and the main window on the CRT. If I have too much tracks or if I blow up a track too much (Shift+Mousewheel), the main window starts overlapping the mixer window on the LCD, although it is maximized to the CRT. The window is not resizable (at least to make it smaller - no problem to get it bigger), no matter if it is maximized or not. No scrollbar appears. Somehow, if the main window reaches about half the size of the LCD (added to the hole CRT, of course), it stops getting bigger and the scrollbar is finally usable. Don't know if it has got sth. to do with dual-head - it seems strange, but it only appears in a dual-head configuration: Right now, I'm mixing a live recording and I'm using the C*Plate-Plugin. I get an Ardour-crash if I change the automation in the main window while ardour is playing. This crash doesn't appear, when not using Dual-Head and if I change the automation of the other tracks. Greetings Mitsch _______________________________________________ 64studio-users mailing list [email protected] http://lists.64studio.com/mailman/listinfo/64studio-users
