– Radeon HD 4890 1GB
– GeForce GTX 275 896MB

If anyone has any experience using any of the two, please let me know.

+ can anyone provide me with the optimal specifications that a ‘jitter-graphic-card’ should have (for a heavy opengl use).

Thanks a lot!

I’d like to ask if anyone has experience of using the Matrox TripleHead2Go with a dual head card, to get 4 seperate outputs? Does this really work with Jitter? Is it better to use Windows XP or Vista? If someone has experience with a particular setup and can say, “yes, this definitely works” I’d be glad to hear – a few years ago I tried a Parhelia card for multiple monitor setup and just couldn’t get it to work with Max/MSP/Jitter..

Any suggestions much aprieciated!

thanks

Andy

Jitter plays well with 8 series and 9 series evga/nvidia cards as long as you handle the jit.windows well. The matrox is also fine as far as windows and jitter is concerned but I have to say I have had some issues with thier robustness in general regardless of weather they are running on my jitter system, a d3 system, or screen AV. I dont use the cards in SLI mode so far but I cant say that Ive done much testing because I havent needed to. Multiple discreet outputs is what I need the most. The most stable way to use gl in windows with jitter is by denoting the rect attribute of your jit.window and never reference the fullscreen commands at all. this also is the best way to use a matrox in my experience. slice your content up with jitscissors, then send out to jit.windows in the case of a composite application, or just drag and drop onto different parts of the matrox split if your doing single screen work. I have an I7 based system right now built on an asus workstation board with a 9600 and an 8800 in it and have had great framerates out of multiple 1024×768 windows across multiple cards, some sending DVI and others sending rgb and Svideo to the broadcast guys plus my control monitor running at 1680. Yes mixed resolutions and output types can be done with windows, with acceleration. With a three card system for a club I have had 15 screens plus a control screen running on one rack. It did get a bit slugish and very hot after a while but I know this was also due to some messy coding because of the speed that the project had to happen. In short, stick to NVIDIA and read up on jit.displays if your going to use GL in windows. also for my money, XP is by far the best. vista works but you really have to lean it down to get the performance your going to want, and windows 7 crashes max everytime I instantiate any type of jitter display object. even jit.qt.movie! Still hoping 7 will play nice with jitter because 7 is alot better than vista on all other fronts that I have found.

Good luck!

With the Nvidia chip based cards, presumably the main thing to take notice of is the number (ie 8800, 9600, 275, etc)? For example I’ve seen the 8800 as 8800GT and 8800GTS – any difference as far as it will affect use with Jitter? With so many different end-product manufacturers choosing a graphic card seems a bit of a lottery..

I’ll certainly be trying out the Matrox TripleHead2Go – certainly a good and easy solution without installing multiple graphic cards.

Thanks again – Andy

One big no no in my experience is dont try and put nvidia cards onto a motherboard that is set up for ati crossfire. Although these configurations work for normal type computing I had many headaches with one system I built where I didnt care about sli or crossfire and I didnt think it would matter if I wasnt engaging that technology. I had many issues with trying to run a patch on a display on one card slot that utilized a different card for output. the most reliable setup I have used has been with SLI ready chipsets and EVGA brand nvidia cards. I have had good results with 8000 and 9000 series cards of many types. I am currently having a great time with my I7 based system. It has an 8800 and a 9600 in it.

Another little tidbit comes with using ethernet to DVI boxes like the magenta or the geffen dvi extenders. Stick with boxes that you know send DDC info back to the source. I have alot of trouble getting GL to draw onto a window if its not recieving this info. Windows will show a desktop and I can drag the jitwindow onto it but no drawing. As soon as you drag it back onto your primary its drawing again. Swapped out the magenta for a straight VGA run and presto, had drawing again. Same thing happened when I was running the Gefen boxes on just the single ethernet video send line. as soon as I added the second ethernet line for the gefen to return the DDC info, jitter started drawing to that window fine.