[Bram Tulloch]

I’m no expert when it comes to that stuff.
I’d ask AJA support if you have any concerns.
support@aja.com

Email them and send them your specs.

First thing I’d be doing though is getting rid of those 4.1.3 drivers! 🙂

Our company has a deal with HP so we’ve got those machines and monitors everywhere so I don’t have any experience with other machines (other than a few Dells and Macs)

Good luck!

[Bram Tulloch]

Vista 64-bit Business Service Pack 2
HP xw6600
Dual quad core Xeon CPU @ 2.50GHz
8GB RAM
Nvidia Quadro FX1700
Adobe Production Premium CS4
Media Vault 4120 FC array.

The xw6600 isn’t an AJA listed solution but it’s so close to the xw8600 as to not be a problem.
I did intensive testing before committing to this machine. We have A lot in our building so it also kept costs down.

[Bram Tulloch]

Yeah maybe with your old card it did that, but with my AJA Xena 2k card it’s been like that even with CS3. Not a problem for us as we always monitor the embedded SDI audio anyway. Works out for us.
If we’re using DV or anything that’s not related to our AJA card, we simply change the audio hardware to windows audio.

As for your graphics card, I have no idea if that’s a problem. I’d contact AJA support about that one.
They only list Nvidia drivers on their site, but that’s not to say other cards won’t work, just that maybe they haven’t tested with others.

[Bram Tulloch]

Do you have Sync going to your AJA card? Like genlock sync?

Or are your playback settings set to “free run”?

I guess if you can’t get to your playback settings then you may not be able to answer that.

I’d check that you’ve uninstalled 4.1.3 AJA drivers properly before you installed the 4.1.4 drivers. You did UNINSTALL 4.1.3 BEFORE you installed 4.1.4 right? With a reboot of the system after every step?

Sorry if that’s a silly question, but it just sounds like the issues that AJA reported in the 4.1.3 drivers are still lingering in your system.

Might pay to try uninstalling the AJA stuff and trying again.
Or even go back to the 4.1.1 drivers. I didn’t have any problems with that one either.
4.1.3 however didn’t last longer than 10 minutes on my set up.

[Bram Tulloch]

I certainly don’t have that problem with 4.1.4 AJA and my Xena 2k card. (i.e. AJA Playback settings panel not opening up)

re: Sync
What audio monitoring are you using?
If mine is set to Windows audio, the audio is in sync with what’s in my preview window on my computer monitor in Premiere, but not my broadcast monitor.
If I set it to AJA audio hardware, it’s in sync with my broadcast monitor (as my monitor uses the embedded audio from the HD-SDI stream)

Your graphics card may not be a problem but your graphics card drivers may be. Check compatability on the AJA website.
Not saying this is the problem, just have been screwed by the wrong Nvidia driver version in the past, not just with this system but with other higher end grading and compositing systems.

[Bram Tulloch]

I can’t confess to know the solution to all your problems but I had HUGE problems with the AJA 4.1.3 drivers and Premiere CS4.

The “AJA setup button” problem was a known issue and is now fixed in the newly released 4.1.4 AJA drivers.

I suggest you update to these immediately and see how your other problems pan out.

The Machina problem you suggest, where you have no picture in Machina check this:
When in the “Play” tab, check your “Display Options”. There should be a setting to “Display To Desktop”. You should have 4 options there. It sounds like maybe you’ve got this setting set to “off”.

Machina freezing when you maximise could be 2 things.
Firstly, I’d try updating to the 4.1.4 AJA software and see if that fixes it.
Secondly, check your graphics card drivers, and see if they are a supported version on the AJA site.
https://www.aja.com/support/xena/xena-graphics-cards.php

Hope this helps.
I don’t know anything about ASIO but thought I’d chime in on the stuff I do have an idea about.

Bram

[Bram Tulloch]

Go to the Kona Applications and check your firmware.

We’ve had a similar problem in the past and the firmware update fixed it. With a fresh install, it may not have updated the firmware which is something you have to do manually. Installing the latest drivers doesn’t automatically update firmware.

[Bram Tulloch]

Didn’t look like it worked. Trying again.

[Bram Tulloch]

Not sure if this worked but here it is.
The field options are greyed out but it’s definitely progressive.

[Bram Tulloch]

Yep.
25 fps