Edius 9.5 - File Export Error

[nictau]

Hi,

does anyone else have problems with H.264 and H.265 export? I get the following error message immediately after hitting the start button:

See image attached.

Thanks.

[John Lewis]

Are you over writing a previous export with the same name

[spurfilm]

Are you over writing a previous export with the same name

I regularly overwrite previous exports and EDIUS asks me if I really want to do this. I say yes and EDIUS does the export and overwrites without problem.

However, if a previous export of the same name is open in other software, like VLC media player, it might throw up a nasty error message. I have not tested it though.

I have successfully exported all kinds of formats from WG 9.50, inc H.264. No issues at all.

Nicola, do you have sufficient disk space available to export to the drive you have selected?

[Andreas_Gumm]

Hi,

does anyone else have problems with H.264 and H.265 export? I get the following error message immediately after hitting the start button:

See image attached.

Thanks.

Hi Nicola,

I know about these errors. Edius often locks deletion or overwriting on files created itself before. My impression is that some processes in background do not release the locked files even when the files are not in use on timeline. Suspicious tasks for me are processes who generates waveforms and the QuickTime bridge helper tool. Maybe there are some other processes which I can't sort out from my perspective.
I usually restart the NLE to release or deleted the files If locked. It's really annoying!
GV should sort this out by reviewing processes who are locking files.
It should be always possible to overwrite files who are not on timeline.
Waveform generation should stop at the time of starting overwriting.

Andreas

[spurfilm]

I know about these errors. Edius often locks deletion or overwriting on files created itself before.

Andreas, that is strange. I have been exporting regularly since I first bought EDIUS 11 years ago. Since then I have been working on many EDIUS versions and four different computers. I never experienced this error message. Interesting that both you and Nicola are in Germany. Are there any differences in the German version? Has anybody in any other country experienced this error message? It would be good to know.

[nictau]

Thanks guys for responding. Sometimes it is the little detail that is overseen.
So one little clip on the timeline was blocked by another process.

I appreciate that this forum responds even on small matters!

Thanks again. Problem solved.

[Andreas_Gumm]

Andreas, that is strange. I have been exporting regularly since I first bought EDIUS 11 years ago. Since then I have been working on many EDIUS versions and four different computers. I never experienced this error message. Interesting that both you and Nicola are in Germany. Are there any differences in the German version? Has anybody in any other country experienced this error message? It would be good to know.

Don't think so. And as Nicola told us, a clip was blocked by timeline usage.
Nevertheless my problems are happen sometimes. As I don't have the time to spend much time I didn't investigate more deeper into it.
The problem pops up when I export a huge file and realize that I've set a wrong parameter. To correct this I stop the export, the waveform creation runs (growing ezb file), a new export to overwrite can't be started.
I can't describe the situation on the QuickTime exports since I restart the NLE and it works then for me.
Anyway, these things happens here and I think it's specific to the file format and the waveform render process.

Andreas

[antonsvideo]

yes, there are known issues overwriting MOV files

example: print to file to Anton.mov and then change in and out and print to file Anton.mov you will get overwrite warning, followed by overwrite declined

it has been like that for almost 20 years

[GrassValley_PS]

yes, there are known issues overwriting MOV files

example: print to file to Anton.mov and then change in and out and print to file Anton.mov you will get overwrite warning, followed by overwrite declined

it has been like that for almost 20 years

Which makes prefect sense. An overwrite involves a delete of the original file. If it is deleted, how can you then reference it via the In and Out points for the "new" file?

[antonsvideo]

Which makes prefect sense. An overwrite involves a delete of the original file. If it is deleted, how can you then reference it via the In and Out points for the "new" file?

you are not following :)

if I export a section between in and out to mov and then realize that my out was set wrong, I correct the out and print to mov with the same name to overwrite, EDIUS fails to overwrite

if I do the same with AVI or MPEG etc, all is well

only MOV prevents overwrite

[spurfilm]

only MOV prevents overwrite

Interesting. I never knew that, since I never export MOV files - as a rule.
Thanks, Anton

[David Clarke]

Actually I get the same with MP4 files. I once read here that it was because QuickTime refuses to let go of a clip once it is made. Once a clip is made it goes in the bin and EDIUS write the waveform cache.

Since I always have use quicktime enabled in the EDIUS settings I do not know what happens without QT enabled.

[John Lewis]

I can also get it with mp4 hence my first reply
renaming the export works

[Andreas_Gumm]

Once a clip is made it goes in the bin and EDIUS write the waveform cache.

I like to collect my exports in BIN, just to keep the overview over what is exported and what is not! Since exports usually are not intended to use it inside the project again I would prefer to prevent them from generating waveforms. For the small number of situations where the user wants it on timeline the waveforms could be generated then.
In batch list it's possible to deselect Waveforms which is actually senseless if you want them in BIN! An option to prevent exports from waveform generation even if those will be sent to BIN would be very welcome.

Andreas