Edius 7 Timeline doesn't scrub

[dstone]

I'm trialing Edius 7 and ran into a problem where the timeline will not scrub, as well as where the entire UI stops responding. I found an old thread (2011) on this, but it didn't have any resolution.

The system is an I7 4970K, 16Gb, NVidia GTX 760 2Gb, with SSDs and fast RAID drives for media. None of the media drives have indexing enabled. This is a dedicated editing system, so no antivirus. The only thing unusual is I have an older NVidia driver (344.75) in order to support my current editor.

The primary problem is that when scrubbing the timeline, the monitor remains frozen on the current frame for 10-20 seconds, then catches up to the timeline position. Sometimes it hangs long enough to go into the unresponsive mode. The timeline and source material is HDV.

It's certainly not a hardware issue. This is a custom built system for editing HD. Is there a known problem with using the older display driver? Or is there some setting somewhere that I should be changing?

[Drbgaijin]

Hello Dave,
Long time - no see

My wife and I have 5 computers between us.
All running EDIUS using the 344.75 drivers and various Geforce GTX cards.
No scrubbing problems on any of them.
Perhaps you could add your computer specs to your signature so that others who may have ideas can see what your setup is.
Regards
Douglas

[antonsvideo]

can you confirm that seek file generation is enabled for Mpeg files

[dstone]

Hi Douglas, Lew convinced me to take a look (he's trying for another convert).

I can confirm that seek generation is enabled.

I moved the media off the raid and onto the SSD drive I use for primary editing, and it still behaves badly. It starts off by being able to scrub, but in short order it starts to hang. The Windows performance monitor shows it performing excessive reads on the drive which contains the media (this happens on the RAID as well as on the SSD).

I'm going to look at the MOBO interrupts and resources and see if I need to move boards around the slots. I use a third party disk controller to add the additional ports needed for all my drives, but the SSDs used for editing and render are on the MOBO ports.

[Jerry]

Is the raid card a 4X card?

[dstone]

The add-on drive port card is PCI Express X2. But the media raid is on the MOBO ports (Intel controller). At this point here I'm reasonably sure it's a system problem; I just have to track it down. But that won't happen before Monday.

[Drbgaijin]

Any progress, Dave?

One thing that people sometimes miss when installing EDIUS for the first time is to make sure that the "Install DirectX" is checked.
I have no idea if missing to do that would have any effect on the timeline scrubbing, but as nobody else has had any further suggestions, I thought it might be worth mentioning.
Regards
Douglas

[Jerry]

The add-on drive port card is PCI Express X2. But the media raid is on the MOBO ports (Intel controller). At this point here I'm reasonably sure it's a system problem; I just have to track it down. But that won't happen before Monday.

When you created the raid on the mobo controller, did you use the actual Raid controller or did you just stripe the drives with Windows. If you are running Raid 0, that is really all you have to do. Then you can move those drives to other Windows machines. My Win 7 raids work in 8.1 Pro and Win 10.
Either way, make sure the Intel chipset drivers are current.

[dstone]

Sorry for the late response, but I've been busy with other projects.

I've simplified the issue by using media only on a single drive (SSD). I've also moved hardware around the MOBO slots to guarantee no conflicts.

The results are still the same. When using MPEG based media (M2T, MP4), scrubbing is intermittent. When the timeline is expanded to show frame-by-frame, I can scrub several seconds before things hang and then have to wait for the system to catch up. If I collapse the timeline, any movement of the timeline cursor and the video hangs. The Windows resource monitor shows excessive command queue length for the drive holding the media.

If I use SD material (even on the HDV timeline), it scrubs perfectly. For the HD material, most of it comes from a Canon XH A1S, either directly from the tape r from a hard-drive recorder attached to the camera. I've also tried samples downloaded from the web, MP4 files from my phone, etc. HD material simply will not scrub cleanly.

Jerry, the raids I use are all hardware based not software. Douglas, I did run the Install DirectX option as I didn't have audio without it.

And just to note, both Resolve and Liquid scrub the same material from the same drives without any issues.

[Perry Tanko]

Hmmm maybe the SSD itself has problems.
Any chance of using a traditional laptop/desktop external HDD to see if the problem still occurs?

i'll bet 10 bucks its the SSD.

[dstone]

Perry, you owe me $10. I take checks, Paypal, or chocolate. :)

This is getting even weirder. I can take the same material, encode it to a QT movie file, and it scrubs fine. I can take a high-bitrate DVCPro HD MXF file and it scrubs fine. It's only the M2T files that won't scrub.

I've got the latest version of Quicktime, I've cleaned out my CODECs, and short of re-installing the OS (which I'm not about to do) I'm at the end of the rope.

I've got a case opened now with GV, so hopefully an engineer there can figure this one out.

[dstone]

“Curiouser and curiouser!” Cried Alice

Just for grins, I tried some other M2T files, and these worked perfectly. So I started looking to see if there's a pattern (capture devices, rendered from something else, etc.) and there doesn't appear to be any.

Much of my material is captured onto Focus Enhancement FS-4HD DTEs, so I thought it might be those. But I have some video on the DTEs that work and some that don't (all of which were captured from the same camera). I have some that were rendered from Media Composer that work, and others that were exported with the same settings that don't. M2V files from Liquid have all worked without problems, as have every MOV file I've tried.

[Drbgaijin]

Dave,
If you take an M2T file that does work and an M2T file that doesn't work, then look at them with Media Info, can you see any differences?
Regards
Douglas

[dstone]

Solved

OK, that was a real pain to figure out. It turns out that the Focus Enhancement FS4's can produce clips with faulty timecode. Which means the MPEG-2 headers are suspect. I retimed the faulty clips using MPEG2 Streamclip (which is very fast as it just recreates the headers) and the clips import and scrub normally.