Hi,
my stem is a Athlon 1000, with a ASUS 7100
Delux Geforce2 MX Card....
dual boot WIN98/2000 (XP coming soon)
I tested the trial version of resolume and I like it very much....evrything works..even the capture driver (even if the ASUS cap driver is very slow for VJ live input)
but with all avaiable graphics drivers for 98
if I put the output window in the second monitor it gets the framerate goes down, too slow for any live performance or even for recapturing....I tried everything but nothing improved this...and as the second monitor resolution cannot be higer as 800x600 I cannot put the interface on the video out ... so I could use the built in scan vconverter of my video mixer on the main VGA out...
if the RESOLUME interface could work in 800X600 the problem would be solved for me....
In the support it is mentioned that a 2 MX card is ideal for resolume....so maybe this problem is only for the ASUS deluxe ..
what other driver/OS should I use...or is there a trick I do not know...
Other VJ soft like SVD1 or VJO works fast enough on the video out with when I use the new beta driver so I know it is possible with my card...
If this (minor ) bug is resolved I ll directly buy RESOLUME, as it does a lot of things my other VJ software cannot do (yet) , esp the clip speed manipulation and in/out points...
which need dual screens
..I really hope that v 1.1 will not have this bug....as I need RESOLUMES features badly for live shows..
Andy Psynergy
http://www.retina-funk.de
Geforce 2 MX dual head problems
Hi Andy,
We have allready solved this issue by letting the output window take over the second monitor with a fullscreen directX surface. So yes this issue wil be fixed with version 1.1. The problem is that we can not release this version anytime soon. We hope to release 1.1 by the end of februari.
What you can do now is run resolume on win2000. Use the extended desktop on 2048x769. Now you don't have the speed problem with dual monitor. But the dual screen in win2000 is not very flexible.
If you subscribe to our mailinglist we will keep you uptodate on the release of version 1.1.
We have allready solved this issue by letting the output window take over the second monitor with a fullscreen directX surface. So yes this issue wil be fixed with version 1.1. The problem is that we can not release this version anytime soon. We hope to release 1.1 by the end of februari.
What you can do now is run resolume on win2000. Use the extended desktop on 2048x769. Now you don't have the speed problem with dual monitor. But the dual screen in win2000 is not very flexible.
If you subscribe to our mailinglist we will keep you uptodate on the release of version 1.1.
-
Dennis_
-
cTrix_
I'm using a Gigabyte Geforce 2 MX400... and experienced the same problem with frame rates on monitor two initially.
I have the same problem with MS flight sim, which only renders 3D graphics on monitor 1.
It seems that monitor 2 has cut back direct X features, and according to a demo coding friend, this is to do with the way data is buffered to the "second allcation" video RAM when using the second monitor. Monitor 1 is the optimised screen, because when accessing 3D it uses half for video buffering and the other half for textures. (Something like that anyway!)
To fix? Run Resolume on monitor 2, and use monitor 1 as the main output. You should be able to do this without too much of a hassle, and be able to define monitor 1 to output to the SVideo socket too
(tested and it worked!)
I have the same problem with MS flight sim, which only renders 3D graphics on monitor 1.
It seems that monitor 2 has cut back direct X features, and according to a demo coding friend, this is to do with the way data is buffered to the "second allcation" video RAM when using the second monitor. Monitor 1 is the optimised screen, because when accessing 3D it uses half for video buffering and the other half for textures. (Something like that anyway!)
To fix? Run Resolume on monitor 2, and use monitor 1 as the main output. You should be able to do this without too much of a hassle, and be able to define monitor 1 to output to the SVideo socket too
(tested and it worked!)