archiving m2t renders

TU

Thanks,I have got it now.

[STORMDAVE]

Aren't those files really tiny?

[Claire]

Great, thanks, well I have a Core 2 Duo (E6700) which is pretty fast so I just won't bother keeping the seek files.

[GrassValley_KH]

Yes, that's right, so long as the .ESE file was fully generated from the associated .M2T file.

If there's a difference, EDIUS will simply generate a new seek file. (this happens in the background, and only affects realtime performance on slower systems)

[Claire]

Thanks, I had missed these settings.

So do I assume that If the seek files are present alongside the m2t files that they would be re-used by Edius to provide accelerated seek if I open these mt2 files at a later date?

[Aristotelis]

These files are only nessesary when you edit mpeg files inside edius... they keep seek information

If you delete them and then you import the m2t files in edius it will regenerate them automaticaly in background. however there is an option to disable that in plug in settings -> mpeg importer

PS3 do not need these files

[Claire]

I'm rendering 20 minute sections of the Edius 4 timeline to m2t transport stream using Edius Speed Encoder plug-in. These HDV files go onto ordinary DVD-R data disks both for for archiving purposes and for viewing in Hi Def using my PlayStation 3. (nice toy)

Curiously for every transport stream file there is an accompanying ".ese" file.
eg: San Francisco Part 1.m2t and San Francisco Part 1.m2t.ese
Windows Explorer reports the .ese files as "EDIUS Seek Information File".

What purpose do these serve? I didn't add them to my DVD-R disks, the PS3 doesn't object, it plays fine.

Okay, so now I want to delete the projects and renders from my hard drive. QUESTION, is it safe to delete these seek files or could I be needing them for something in the future?