[Ross Daly]

Following up, it seems that my issue is with multiclip footage, (or possibly specifically) 1080@24 h.264 5D mk III footage in a multiclip sequence.

My applescript ran all weekend just fine, so I had to switch it up. I made a new applescript that would:

select clip under playhead
copy clip
cut under playhead
jump ahead random frames
paste clip
jump ahead random frames

loop

This ran flawlessly on one track of video (5D footage above) and on 3 tracks of video, but when I multiclipped it and ran the script on the multiclip sequence it started beachballing pretty quickly. If I have time I’ll test this same feature on a prores multiclip, because some people seem to be having better luck with different codecs.

At least I have an idea of what to avoid now, but it’s pretty sad that this is such a glaring bug in one of their important features.

[Ross Daly]

As a test I’ve fixed permissions per your blog, and created an applescript that

renders my 6 minute sequence
plays it back for 100 seconds
delete render files in to out
plays it back for 100 seconds
and then loops

I set it to run all weekend long at work, and I’ll report back on monday.

As a side note – does everyone else have adobe qt server 32 become unresponsive on premiere boot? I’ve seen this on other posts, but it doesn’t seem to have much relation to the actual app crashing.

[Ross Daly]

[John Pale] “Are you, by any chance running the Creative Cloud Desktop app (in the menu bar) at startup.”

Hi John, no I’m not running that. I’ve only been on ethernet as well though, so I can’t speak to how well wifi changes stability. It seems like that app is used for licensing. I’m on a site license and/or own license server (I believe) so I don’t think I need to have that running. Thanks for your thoughts, though. I’m surprised at how many people are fighting with this.

[Ross Daly]

“if you’re getting repeatable crashes”
I think this is part of why I’m frustrated. They are very frequent crashes, but caused by such common things (like playing footage, scrolling, and pasting clips) that there’s almost no way for me to know for certain what caused any one crash. I’ve submitted 30+ bugs/crashes for other apps in the last 2 months, but this behavior is almost independent of user input. (and consequently hard to submit a proper reproducible bug report)

I’m going to turn off opencl acceleration and see how it goes. I’ll also try the documents folder permissions fix that I have seen mentioned often.

Thank you all for you help and thoughts. I’m not at all frustrated with this community, just the performance. I appreciate everyones contributions.

[Ross Daly]

The third machine had a factory fresh mavericks install, and the only additions were cc 2014 and outlook.

Disabling gpu is on my list of things to try, but at this point I’m so far down the list that the journey has been really disheartening. And regarding apple’s gpu drivers – it’s weird that I don’t get these glitches in anything else, AE, fcp7, nuke studio.

[Ross Daly]

I have also gotten halo like that before from shooting in low light with a uv filter on. It can be caused by light bouncing between the parallel surfaces of the image sensor and the filter. No idea if you had one on, but I doubt you needed one if you did.

[Ross Daly]

Hmm… that’s a weird one.

If it works out to an even frame increment then I would export it to a still image based workflow and just delete every nth frame manually.

Alternately, you could create a slug that is 3.24 sec long, and then one that is 1 frame long. Copy and paste that a bazillion times into v2 of your comp and use it as a template for cutting the original track. down arrow, cut, down arrow, cut.

If you have the option of recapturing the source, then that may very well be the best way to deal with this. It also may be much less of a headache.

_Ross

[Ross Daly]

Hi David,

I’m sorry if this goes unsaid, but are you talking about playback in the AE timeline, or in the export? If it is playback, what happens when you select “audio from here forward” from the right click menu in the timeline?

If export; do you have it set to export with audio?

_Ross

[Ross Daly]

Hi Jonathan,

I think that may be caused by one of two things, and both of them have to do with your camera. I don’t remember if ae lets you toggle the 3d layer switch on a precomp. If so then you need to have that on. It sounds a bit like you may have a 2d layer in a 3d comp.

The other thing is that your precomp will smash all of your 20 layers onto one flat plane. The camera will see them all as one element with one x,y,z position. I think that is not what most people expect when they precomp a 3d layer. They will all move together, which can break things if you have a camera move, or individually animated layers.

Once you get those screen shots up I may have more ideas.
Good luck,

_Ross Daly

https://learningnuke.com

[Ross Daly]

Hi Raza,

I’ve never run into that look when they weren’t actually on the same z depth. I’ve also never run into it when layers are perpendicular. Sorry to be of no help. At least you aren’t alone in being surprised by that behavior.