Loveclose;
Hard to "inflame" a Troll..we are already so dang cranky!

The suggestion on the video driver was based on my experience with the Card Manufacturer that Yurii was using (Nvidia). EACH manufacturer has it's own issues, but maintaining the most current driver possible is critical to get the best results.

Others here are much more familiar with ATI than I am, so I defer to them for helping you on that.

The issue with pauses, stuttering and screen freezes has been found to be caused by MANY things, often very different causes, depending on the machine specs, clips source/resolution/bitrate, input and output format selection, program preference settings...oh man that list is very long...too long to cover here.

What I was trying to suggest was, the problem is not always "exactly the same problem". It is absolutely the same symptom..but the solution is different for each user (often solved by the other dedicated editors that spend so many hours volunteering here). That is why it is important that each user start their OWN thread/post. So unique and specific attention can be paid to the solution of each "seemingly the same" problem.

MY particular stuttering and freezing and pausing issue was long ago solved by replacing my video GTX260 video card and updating to the latest driver. No, I do not mean that is always the problem, just one of the possible problems.

ALWAYS start your own thread to help the editors focus on your specifics. It is IMPORTANT!!

well, ill do a little testing and rule out hardware. i have several unique pc's i can run the same project on.
i dont think everyone here is having a unique problem.

turning off video preview and using software rendering excludes video drivers.

Bastian74;
I know the opinions vary here, so I am not trying to get a "discussion" started. My opinion is, do not believe that you can bypass the GPU in a Video editing project.

Transcoding and rendering of any kind in an NLE involves the GPU. Transitions, effects, edited/cut clips and any video enhancements, all use the GPU. Even portions of the sound are processed by the GPU. That is why the video drivers include a sound driver update. I KNOW that video drivers have caused many issues, but I don't blame them for everything wrong with PD10. I just suggest that eliminating them as a source is a good approach toward a solution.

If the problem was the PD10 software only, then EVERYONE would be having problems, that's all I am trying to say.

Hopefully someone here can duplicate Yurii's problem and suggest a way to solve it. Since you are doing 1/2 half as many clips as Yurii and 60P at a different resolution from a different hardware source, your problem is different.

My car won't start, but that doesn't mean that if your car fails to start we have the same problem. I am just suggesting that each problem deserves it's own post and attention.

I wish I could provide more help, I hope someone knowledgable comes in to help Yurii.

Quote: Loveclose;
Hard to "inflame" a Troll..we are already so dang cranky!

Good post Fred, even for a dangly cranky Troll!! Found your post very interesting, especially the audio driver part, something I'm going to have to check up on tomorrow now you've mentioned it.

I've just downloaded the latest ATI catalyst driver pack - I'm assuming that if an audio driver is required for my GPU, then it will have been added then?

Loveclose;
Thanks for the comment.
Most video drivers contain an audio component in the update. Not sure if ATI/AMD separates theirs.

There is still an issue with the sound card/chip driver (that is separate) and should be updated from the audio MFR.

Hope that helps.

While it is certainly true that different problems can manifest themselves with similar symptoms it should not be ignored when multiple people have the same symptom. With enough people posting that share the problem one can start to narrow the problem down, with exceptions that some samples may indeed be different problems. More information, and more samples can only help in troubleshooting. I have enough computers to run hardware independent tests, the other poster may not.

Here is the problem as I experienced it:

Skip to 5:20

The source video was playing fine during the transition, but as soon as it is being rendered "on it's own" it freezes until the next clip.

The clip that froze is random, and was different every time I rendered it.

The source video for my clips was 1080 P60 from a Panasonic TM700.

Also, processing video files does not require a GPU at all. Video is just data the same as any other. While you have the option to involve the GPU via CUDA/DirectCompute/Stream, they are not involved if you disable hardware encoding. In this case, as the rendering itself did not hang, only the input stream it seems likely that the video decoding is where the fault was. That leads to further testing of various codecs. I happen to have Shark007 codec pack installed and I cannot deny that that may interact wtih the decoding of h.264 streams. I seriously doubt that PD10 has built-in codecs for decoding video, like VLC has.

While some video cards offer hardware assisted playback of some video streams, not every application is written to utilize that feature. Without knowing how PD10 is written I cannot say whether video card drivers play any roll at all. I can certainly say that you do not NEED video to process a video file. It's just data. I can open a video file in a hex editor if I want and do whatever I want to it.

The reason video card drivers have an audio component in them now is because they include a virtual soundcard driver for providing sound over hdmi cables. Those drivers are only used when you chose to use your HDMI display's speakers.

If the original poster has access to more than one computer, I would encourage him to copy his project files over and see if the results are the same.

@Bastian74 Thanks! I'll try that work around. So do I produce each split part, and hen merge them and re-produce/render?

This movie means a lot to me. It's of my first daughters 9 months. Many hours distilled down to 12min of priceless moments.

@FredB I just tried Intelligent SVRT with and without hardware acceleration (preview off) and no luck. Found 4 frozen clips half way through * I was excited because I hadn't realized that option yet. I agree that everyone has a different set of factors. It just sucks that I had to come here because I'm getting no help with my ticket (still no reply). And it appears I'm not the only one having a similar problem with frozen clips regardless of the factors involved. A system in-place to upload video and test based on different factors would be awesome though.

Correct. Save 4 extra copies of your project, part1 through part4.
Then produce each quarter one at a time until you get four fully functional productions.
Then you can create a new project and splice the 4 video clips together.

This doesn't really work-around the problem, it just makes it so you are more likely to get a functional clip by chance.
The odds of making a error free clip is 4 times better if the clip is 1/4 the duration. Then the final production only has 3 transitions.

As for troubleshooting the actual problem, I would try changing any codecs you've installed, if any. Also, try changing whether or not you use hardware acceleration for VIEWING the video. (in tools / options) If you've installed a codec pack, try uninstalling it. If you haven't installed a codec pack, try installing one. k-lite for windows prior to windows 7, and shark007 if windows 7.

I did render my problematic production on another computer and my first try worked without any freezes. I only ran it one time, so it may be just chance that it worked. Thats the problem with random, it takes a lot of tests to validate anything.

I actually remembered wrong which computer was having the problem. My Laptop is the computer that kept having freezing final results, not my desktop.

My laptop is windows 7 32-bit
I see that I have k-lite codec pack installed, not shark007
CPU is a core-i5
GPU is a nvs-3100 M (nvidia)