Well Folks, I've spent even more time on this PTT issue. And Chienworks's "Gut feeling" is still ringing in my ears, So "Humble Pie Time" - saving files and the defaults didn't cut it. I don't know where I saw the drop from 60% to 30% of processor usage, but since I posted the message I have not been able to repeat the success. Oh dear!
ANYWAYS.....
Ahem.... I've interrogated the Sytem Monitor for hours to see if there are any clues to my situation.
I am still getting "drop-out" on freshly rendered clips and at different places on those clips. However, this sometimes happens - it is not a consistent "fault". Sometimes I can PTT for 2,3 or 4 PTTs on the trot, then maybe on the 5th attempt drop-out. Then onwards through 6,7 etc and no problem. There is something Hit 'n Miss about what I'm doing. Because of these successful PTTs am I right in thinking that the timecode is not the issue?
All I want to do is be "secure" in the knowledge that I can rely on PTT happening and, if "drop-out" is case, also be knowledable enough to take preventative measures to ensure PTT being succesful.
Getting back to System Monitor - here's the thing. I am registering Disk Cache Misses at around 900/second. I don't know if this is a large number or it is something I should ignore? Is RAM taking up the slack and therefore being "overrun" with Disk Cache call-outs?
If the PTT process is in fact dependant on making correct write-to-disk then I may have "stumbled" on the reason for my problem. What do you think?
Could someone do a PTT test with System Monitor running and tell me if they are getting the type of DIsk Cache "misses" that I am? If they are, then I need to go back to the drawing board! If it can be proved that my 900/sec misses are the reason then I need to somehow envoke a way of eliminating this.
I can tell you that I am not aware of my on board C: drive taking up any of the slack. That is I am not aware that the C: drive is "handling" any Cache writing - I don't see my red light flickering on my C: drive - yeah I'm not very high tech. My external F: drive is flickering nicely - this is where I've got the VF video files. All my VF programme files on the C: drive.
Next question: Does VF in PTT make use of a Windows Temp file or other Disc Cache writing procedure to ensure the fidelity of the PTT process? Is this "temp" file/directory set-up by VF? If not how do I force this to happen?
Please get back to me. I know I'm nearly there with this wonderful NLE package, I just need to go that last inch.
Grazie
ANYWAYS.....
Ahem.... I've interrogated the Sytem Monitor for hours to see if there are any clues to my situation.
I am still getting "drop-out" on freshly rendered clips and at different places on those clips. However, this sometimes happens - it is not a consistent "fault". Sometimes I can PTT for 2,3 or 4 PTTs on the trot, then maybe on the 5th attempt drop-out. Then onwards through 6,7 etc and no problem. There is something Hit 'n Miss about what I'm doing. Because of these successful PTTs am I right in thinking that the timecode is not the issue?
All I want to do is be "secure" in the knowledge that I can rely on PTT happening and, if "drop-out" is case, also be knowledable enough to take preventative measures to ensure PTT being succesful.
Getting back to System Monitor - here's the thing. I am registering Disk Cache Misses at around 900/second. I don't know if this is a large number or it is something I should ignore? Is RAM taking up the slack and therefore being "overrun" with Disk Cache call-outs?
If the PTT process is in fact dependant on making correct write-to-disk then I may have "stumbled" on the reason for my problem. What do you think?
Could someone do a PTT test with System Monitor running and tell me if they are getting the type of DIsk Cache "misses" that I am? If they are, then I need to go back to the drawing board! If it can be proved that my 900/sec misses are the reason then I need to somehow envoke a way of eliminating this.
I can tell you that I am not aware of my on board C: drive taking up any of the slack. That is I am not aware that the C: drive is "handling" any Cache writing - I don't see my red light flickering on my C: drive - yeah I'm not very high tech. My external F: drive is flickering nicely - this is where I've got the VF video files. All my VF programme files on the C: drive.
Next question: Does VF in PTT make use of a Windows Temp file or other Disc Cache writing procedure to ensure the fidelity of the PTT process? Is this "temp" file/directory set-up by VF? If not how do I force this to happen?
Please get back to me. I know I'm nearly there with this wonderful NLE package, I just need to go that last inch.
Grazie