FIXED: garbled param window from MMB too quickly ?

[cod65]

oFten times I end up with a garbled interface, after changing parameter values with MMB. My parameter window wont fix and I need to restart touch. Dunno what else to say, except I've added a screen grab. Could this have to do with my video cards config ?

[selina]

what graphics driver are you using?

I'm actually inclined to think it is a bug, although I'm not sure how it can happen yet. you say it happens quite often for you. is it a particular file or do you get the same thing in a fresh session? if you have a reproducible file, can you send it to support?

Selina

[Achim]

i had these artifacts as well, but haven't seen them in a while, so it might be a driver issue

btw, if you manage to MMB on the parameter that initially open the value ladder, then you can get it fixed without restarting touch

[cod65]

thanks for replies,

I'm vnc'ing into my machine so i cant access nvidia control panel, but it looks like touch says the sygraphics driver version is 285.62, if that makes sense... I also note that there seems to be a new driver available and presume that is a good place to start addressing this issue on my end.
I mentioned my gpu cards setup first, becasue I am using a combo of unequal nvidia cards, as mentioned in my sig. The idea is I use the 9500 for interface and the 250 for output, presuming that my output would use the newer card. I dont know if this is an unwise strategy as, in the past I was advised to use 2 of the exact same cards- didnt do this for economic reasons at the time ....

But I must note I had the same issue on a friends' rack PC when I grabbed at the 'ladder' on his machine.
I will try and post a crash report or project later on today...

The one incident that comes to mind as when I was 'wildly' adjusting the size of an audioin buffer- it seemed like that was a no-no.....

Achim , yes I have on occasion been able to 'exit the ladder' by finding my way back to the parameter. Sometimes if I go to a new op I can get it to leave that stuff behind and open a fresh ladder. More often than not though it just wont leave without a restart.

thks all. more later
cod

[malcolm]

Using two Geforce's isn't recommended, even if they are the same model, unless you are using them for SLI. If you are looking to add more monitors to your system you need to use Quadros or video splitting devices such as Matrix Dual/Triple Heads or DataPath X4.

Another untested option is starting to use the AMD EyeFinity tech, which I hope to look into more soon now that our AMD cards work correctly with TD.

[cod65]

Thanks, malcom
is this true, even if my intention is a single monitor/card for video output(gts250) and a single monitor/card(9500) for user interface ? i.e. I dont expect the audience to see the UI, just the single output from the 250.

[malcolm]

Hey Cod,
Yes it's true for your case. The issue is there is only 1 driver, which needs to manage all the data for all the cards. If I give a movie frame to the driver it doesn't know which GPU needs it, so it'll send it to both cards, hopefully. Other cases I'm updating GPU data but again there isn't a way for me to tell the driver which GPU I want to update the data on, so it's possible it'll go to the wrong card. This is why GPU affinity exists on Quadros.

[keithlostracco]

I've just gotten the messed up ladder problem again twice in the past couple of days. I noticed it happens when your drag the value so far onto another app's window that it highlights something in that app.

If you are looking to add more monitors to your system you need to use Quadros or video splitting devices such as Matrix Dual/Triple Heads or DataPath X4.

cod65-
I'm using a couple of dual heads and they work great. I found if you use more than one window you get pretty big performance hit. If you use one window across all the monitors and then have your UI in one part of the window (on one monitor) and then your output on the other part of the window (output monitors) you'll get the best performance. The one downfall of this is that the monitors should all be the same resolution.

Another solution that I use mostly is to use Max for the UI and send OSC to Touch to control parameters. I find this works really well with the least amount of impact on performance. With Max you also have access to the pattrstorage objects which makes creating presets for Touch super easy.

[selina]

tried reproducing the messed up ladder issue by dragging the value really far out, but no dice. do you get it consistently when you do that?

the other odd thing in your statement though, is that even when you drag it that far out, TD should still have focus, so I'm not sure why its highlighting something in a different app..

Selina

[keithlostracco]

Yesterday I was able to make it happen consistently by dragging it onto a separate render view window, tonight it's not happening at all. When I tried to make it happen tonight I noticed that the mouse pointer disappears when dragging the ladder (which I think is normal). Yesterday when I was able to make it happen consistently I'm pretty sure the pointer was visible when dragging.

Yesterday I was working with a relatively large project that I had open most of the day without closing it and reopening it , maybe that has something to do with it. Tonight I just loaded everything up so maybe later on I'll be able to reproduce it.

I was also getting the ui redraw problem (where ops leave parts of there display behind when the network focus is moved) alot the past few days but tonight it doesn't seem to be happening either.

I haven't updated graphics drivers in a while so maybe I'll do that tonight as well.

cheers
Keith