Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums AJA Video Systems AJA killing my system… and me.

  • Jeron Coolman

    March 20, 2007 at 4:30 pm

    FWIW,

    I did all of those things and none of them helped. Reformatted, reinstalled, removed RAID controller, etc. That is how I came to the original conclusion where I thought it was a conflict with the sound card.

    I am convinced the problem is their drivers. Everything works great without the Xena card and drivers installed 🙂

  • Tim Kolb

    March 20, 2007 at 9:32 pm

    AJ,

    Just out of curiousity, does AJA know you are posting here regarding non-public beta software? I don’t see it generally available from their website so I don’t see how they would have furnished you with the software with the intent of having you talk about it on a public forum…

    Did you sign an NDA?

    A bit of “beta software etiquette” for you: Beta software opens a dialogue between the user and the manufacturer. It’s a great way to work with a manufacturer and make sure they hear your views, but publically disclosing beta activities is usually a great way to remove yourself from that process…and quickly.

    There are many of us at the Cow who beta test for various manufacturers in various capacities, but Non-Disclosure Agreements are very clear on public disclosure of proprietary information…violation of the letter and the spirit of the agreement.

    If you care to comment on trouble-shooting procedures that have to do with released products, please continue to furnish insight to the group here at the AJA Cow.

    I suspect if AJA supplied you with beta software, their intent was that the sole recipient of any comments you have regarding it would be AJA.

    Since you apparently have in your possession, unreleased development-stage software that I doubt AJA will release to just anyone (as a protection to the user because it’s in development and issues need to be worked out), I recommend you refrain from commenting on this forum on whether or not it causes or solves problems as since it’s not generally available, it isn’t ready for release, and these traits are temporary and that is the purpose of the alpha and beta process.

    I am checking with AJA on this situation as typically any non-manufacturer sanctioned conversation regarding proprietary knowledge of unreleased products is not allowed on the Cow as it makes this site a party to the violation of an NDA.

    TimK,
    Director,
    Kolb Productions,

    Creative Cow Host,
    Author/Trainer
    http://www.focalpress.com
    http://www.classondemand.net

  • Jeron Coolman

    March 22, 2007 at 4:05 pm

    Tim, I am not currently beta testing any Aja software and I can’t speak for project17, but in the past when I have beta tested Aja software, it was very informal and I wasn’t asked to sign an NDA (even though I offered to).

    I do agree with you “beta ettiquette” philosophy though and even though I didn’t sign an NDA back then, I still didn’t talk about it and acted as if I did.

  • A.j. Leitch

    March 22, 2007 at 6:31 pm

    I wasn’t asked to sign one either and I was new to the beta ettiquette” philosophy. Never the less, now I’m just looking forward to figuring out a solution to the problem.

    Still haven’t had the time to go through all the steps (clean install, configuration etc.). Once I do, I’ll test it out and see where it takes me.

    AJ

  • Jeron Coolman

    March 23, 2007 at 2:16 am

    I just did some more extensive testing. I hope a clean rebuild helps your problems project17, because I did it twice to no avail.

    I created projects as both Adobe presets and Aja presets. I can only get the Aja presets to “break” like this. I still can’t determine exactly what condition causes it. I tend to be able to “break” it (make Premiere Pro become unresponsive) when using multi-cam more than not.

    This is with the RAID controller pulled out of the system. Whether or not the raid controller is in the computer doesn’t seem to change anything, except what is expected from slower disk I/O.

    The Adobe presets have never demonstrated this behavior, only the Aja ones which makes me believe this is an issue with the Aja drivers. Next I’ll roll back to 2.0 and try that. Oh yeah FWIW, I reported these issues to Aja when 2.5 was released and they “hinted” that it was a hardware configuration or problem with the raid controller as well.

Page 3 of 3

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy