Anyone getting crashes with the still image exporter in v4.24

[Malcolm]

Hi all,

Can some of you try exporting a sequence of .tif files and tell me if Edius crashes for you at the end of the render?
I just tried with targas and it crashes too.

Grrr....

I'm also finding that the resulting still images are more pixelated than the displayed clip in Edius. I see a very distinct increase in aliasing, as if there was less actual resolution or some sort of filtering missing in the still image.

I'd really appreciate some help with this: if anyone is willing to try this out and tell me they see it too, that would be a beginning!

Thanks!

Malcolm

[Malcolm]

Ok, ignore the part about the aliasing. The version of shake I have does a very poor job of displaying images when they are not 1:1. Hitting home makes the still display identically to what I would expect.

Phew, one thing scratched off the list :)

M.

[skier-hughes]

I'm running 4.11 and I've just done sequences of 2 frames to 50 and used .psd and .tiff and all saved successfully and quickly.

Graham

[Aristotelis]

That might be an HD issue as well...
exporting uncompressed still images might require a good write performance from the hard drive...
Try to export in jpg and see if you get the same problem

[Malcolm]

Theoretically at least, write performance should not be an issue since unlike capture, exporting a sequence of frames has no performance threshold to try to live up to. The app should simply write out a frame, wait for it to finish, then write out the next one.

Another thing that makes me feel this is not drive performance related is that the entire export works: the crash occurs when the render window closes and focus tries to return to the Edius window.

Anyone with the latest v4.24 of Edius able to try exporting some .tifs from a 1080 clip?

Thanks!

M.

[Malcolm]

I'm running 4.11 and I've just done sequences of 2 frames to 50 and used .psd and .tiff and all saved successfully and quickly.

Graham

Thanks Graham! Lucky you :)

M.

[Malcolm]

Latest update: I get the same crash when rendering out a 1080 dvcprohd avi partially composed of a sequence of .tif images on the timeline.

This is starting to become a big problem because I have many shots to spit out as image sequences, work on, then reintegrate into the project.

It would be nice if someone from Canopus has something to say about this.

M.

[Aristotelis]

Just a few thoughts...

1) Try to reinstall quicktime...
2) Try to set in and out points and export between in and out
3) Defrag you Hard drives

[GrassValley_KH]

I've tried to make this crash, but it just won't bug on me. Aristotelis has some good points.

We need some more info:

- Version info of Quicktime
- Amount of RAM in the system
- Amount of RAM allocated to the buffer (i.e. buffer size for EDIUS)
- Any image handling being used? (filtering, aspect ratio, etc)

If the images/AVIs are being rendered correctly, and you're just getting dumped out after it's done, then it could be that EDIUS falls down at the point where it auto-adds the newly rendered file to the bin window. Where are you saving the clips? Local or networked drive? External media/drive?

PS. Please don't spam the User-reported issues forum - once is quite enough for our people to look at it. :)

[Malcolm]

I've tried to make this crash, but it just won't bug on me. Aristotelis has some good points.

Thanks for looking into this.

We need some more info:

- Version info of Quicktime

Quicktime 7.1.6
Is the stills exporter connected to quicktime in some way?

- Amount of RAM in the system

2gb

- Amount of RAM allocated to the buffer (i.e. buffer size for EDIUS)

Not sure where to check for this.

- Any image handling being used? (filtering, aspect ratio, etc)

The clip being exported to stills is just a straight clip with no effects, no frills.
The stills exporter is set to adjust aspect ratio.
The stills being rendered out as a dvcprohd clip are untouched resolution wise.

If the images/AVIs are being rendered correctly, and you're just getting dumped out after it's done, then it could be that EDIUS falls down at the point where it auto-adds the newly rendered file to the bin window. Where are you saving the clips? Local or networked drive? External media/drive?

My C drive.
Is there a way of disabling this auto-add (which is actually undesirable for me)? This would be a way to test this theory.

PS. Please don't spam the User-reported issues forum - once is quite enough for our people to look at it. :)

I don't think it would be fair to say I spammed the User-reported issues forum. I believe I sent one post before I had actually typed much at all in it, by mistake (I'm a human being). I then typed out the full post and sent it again.

If there was a previous post to that forum about this issue from me, it was days ago and never appeared in the forum so I can be excused for trying again. Your approval process for posts is a black box, and some messages simply never make it on to the forum, with no word back on why they didn't make it there.

Thanks
M

[pjsssss]

There is no "approval process" for most of the forums. I believe Feature Request and User Reported Issues are the only ones that go through mods before appearing.

[Malcolm]

Just a few thoughts...

1) Try to reinstall quicktime...

I'll give this a shot. Does Edius use quicktime to import and export stills?

2) Try to set in and out points and export between in and out

That's how I have been doing the export.

3) Defrag you Hard drives

The drive being written to was defragged last week. I'd be surprised if this was the cause of a crash once the export has already finished. It definitely seems to be a problem with what happens after the export is done and control is being handed back to Edius.

M.

[Malcolm]

There is no "approval process" for most of the forums. I believe Feature Request and User Reported Issues are the only ones that go through mods before appearing.

That is also my understanding. KH said I had spammed the User Reported Issues forum. I think he and I differ on what spam is :)

M.

[GrassValley_KH]

The top three posts in my view of that particular forum, were from you about this topic. Hence my comment.

As it is, we don't get a huge amount of time to test everything and confirm things as soon as the posts arrive.

Typically I will go through the two moderated forums on Fridays and activate what I can. The User Reported Issues forum is still a little bit of an unknown entity as far as responsibility goes (since none of the Mods are in Tech Support, so we're actually not supposed to be bug testing - it has to be treated as a spare time thing).

As a rule of thumb, if your issue cannot be solved and other people can follow your steps to successfully reproduce the error, then you should definitely post in the User Reported Issues forum.

Back to the topic. To answer your questions:

- Stills (apart from Targa and SGI) need Quicktime to import/export
- Have you tried not adjusting the AR of the exported still sequence? If only to check?
- No option to prevent adding to bin after a render (that I can find)

Also, is this only happening with DVCPRO HD 1080-to-still and still-to-1080 DVCPRO HD? Or are there other scenarios that reproduce the error?

[Malcolm]

The top three posts in my view of that particular forum, were from you about this topic. Hence my comment.

As it is, we don't get a huge amount of time to test everything and confirm things as soon as the posts arrive.

Typically I will go through the two moderated forums on Fridays and activate what I can. The User Reported Issues forum is still a little bit of an unknown entity as far as responsibility goes (since none of the Mods are in Tech Support, so we're actually not supposed to be bug testing - it has to be treated as a spare time thing).

As a rule of thumb, if your issue cannot be solved and other people can follow your steps to successfully reproduce the error, then you should definitely post in the User Reported Issues forum.

Thanks for the clarification.

Back to the topic. To answer your questions:

- Stills (apart from Targa and SGI) need Quicktime to import/export
- Have you tried not adjusting the AR of the exported still sequence? If only to check?
- No option to prevent adding to bin after a render (that I can find)

Mmm, I get the crash with sgi and targa images too. So it seems we can rule out quicktime.

Yes, even with the adjust AR not selected, the crashes occur.

Also, is this only happening with DVCPRO HD 1080-to-still and still-to-1080 DVCPRO HD? Or are there other scenarios that reproduce the error?

So far these are the only scenarios that produce this type of crash for me.

I have some SD footage handy: I'll see what happens with that.

Thanks!
M.