New XW8200, but performance can be smoother

J

JKL

Well-known member
When I navigate fast through the timeline, it may hang severall times on some parts for just a tiny moment. I have 2 firewire drives in a chain connected to the XW8200.

And Avid Xpress HD 5.2.1 quits or hangs when I do a fast rewind in the timeline.
On my old computer I didn't have that problem. What can I do about it?
 
Well, it's Xeon, but single processor. I wil check if Hyperthreating is disabled.
It has to be disabled when working with Avid Xpress HD?
 
Cancel that. If you have a single processor system then Hyperthreading SHOULD be enabled. So, check and make sure that it is. :)

Are you running a Mojo?
 
I have checked it, and Hypertreathing is OFF. I will set it to ON.
And yes, I use a mojo, it is connected to the internal firewire port, and my external firewire drives are connected to a firewire card on pci slot 5.
 
Hm ... everything sounds good with your Mojo and drives. Hopefully turning HT on will fix it. Post back if it's still a problem.
 
Well, I have set Hypertreathing ON, and yess, it runs smooth now.
But Avid will still quit without warning sometimes when I rewind back in timeline.

And when I play video and I stop it, then I see on my external monitor connected to mojo that the video jumps back several frames, is that normal? On my computer monitor it doesn't.
 
Well, one problem down, right? :)

To be honest on the other problems I'm clueless. This is a new computer, right? Did you run into any problems or quirks during the install?
 
Ya, one problem down!

No problems with install, except for the firewire card, the first time I installed it, it was seen by the system, but the connected firewire drives where not seen.
So I have disconnect the the firewire card and reinstall it again, now the drives are seen by the system.

But in Avid Xpress HD 5.2.1 I get those messages, and Avid hangs:

- Exception: GetFreeHeap timeout. Possible corrupt heap.

- The system is runnig low on memory (100% full)
Try closing bins etc.
 
The corrupt heap message can be caused by corrupted media files. Good luck tracking that down though. Was the project you're working on transfered from the other computer? Do you get these same errors on brand new projects with footage captured with your XW8200?
 
The footage and all the projects was tranfered from my old computer to the
xw8200.
So I have to try new projects out if I get the same errors.

But is version 5.2.1 of avid the most stable one? Because have have been worken for a long time with version 4.5.1 of avid xpress pro, because of errors in newer versions. So maybe a older version of avid xpress HD gives less errors?
 
I've had really good performance with 5.2.x Xpress Pro. In fact I can't recall a single error that I've had with those 5.2 versions. I wouldn't assume that going back to 4.5.1 would solve this problem, but I've been wrong before.

I'd say try a new project, just a test one with some newly captured footage and see if you get the error. If not, then you've got a corrupt media file somewhere. If you do, then we can troubleshoot some more.
 
Well, on the Avid forum I see a lot of people having the same errors as I get, today I just getting this one:

Unable to allocate memory for operation

Some people say going back to version 5.1.5 will solve the problem.
BTW, which version of Avid supports quicktime 7?
If I try to going back to 5.1.5 do I have to install 6.5 of quicktime?

Because there still no solution for the memory errors on the Avid forum.

And just another question, can I set a second pagefile to a second internal harddrive?
Will it work better?
 
I believe that 5.2.1 is the first version that supported QT 7. If you go back to 5.1.5 you'll need to reinstall QT 6.5.

I hadn't seen this error before and I check the Avid forums almost daily. Sorry I missed that for you and led you on a wild troubleshooting goose chase. :)

Regarding Pagefile, I'm really not sure. I'm not up to date on my Windows knowledge.
 
I have installed Avid Xpress HD 5.1.5
No errors so far, think I am gonna keep this version for a while 'till things get fixed in the newest version. I don't like it when every two hours a error pops up and I have to restart the app.

But hey! Thanx for your help.
 
You must log in or register to reply here.
Back
Top