[Kell Smith]

There may be a way to find “date created” for sequences – looking for it this morning but have not found one. The bin column by that name is blank.
Here’s what I’ve been doing as a workaround. I have a bin called “sequences-old.” So for the sequence “My Project,” I work in that main one, leaving it accessible in the main project window, but before each major revision, save a backup named “My Project 001” 002 etc in the bin. Then put a note on there (i.e. “before changing the titles to green.”
I wish I had included dates on the revisions though because that would come in handy this morning. When you get that many revisions going way back, it would be helpful especially with about 30 different past sequence versions.

[Kell Smith]

>No, I just meant, did you ever intend to use the 60fps as slow motion…slowing it to 30fps frame for frame for smooth 50% speed. <

Sorry Shane for the confusion, I was responding both to your comment about the slow motion and Dave’s comment about the 59.94 vs 60.

>You aren’t downconverting…that’s when you decrease the frame size, say from 1920×1080 to 720×480. You are doing a frame rate conversion. Now, why don’t you want to? DVDs are 30fps only…retaining the 60fps really doesn’t do anything.<

Incorrect terminology!
I was planning to transcode the footage to DNXHD in Premiere and then bring it into MC – due to problems with spanned files in MC – and just wanted to clarify whether to do that either at 29.97, which was my first thought, or at 59.94 (leaving it as is, per your and Dave’s suggestions, and letting Avid just import it in).

>If you EVER intend to go digital…then best to go Progressive. Deinterlace the other footage. <

Currently the project is interlaced, with the progressive footage ( now 29.97 DNXHD) brought in. It would be a hassle, but not a major shakeup to recreate the project. Is it best to go ahead and create a new progressive project then, and transcode the interlaced footage to DNXHD 145 1080p 29.97 (and 709 colorspace?) for import into Avid? If it will make a difference in the final product I will do that.

Thanks for your thoughts on this, really appreciate it. I was reading your blog yesterday by the way and learned a few little Avid tricks, so thanks for that too.

[Kell Smith]

Thank you Dave and Shane,
Yes I stand corrected, it is 59.94. No slow motion.

I was having some problems transcoding from Avid, so I was going do the conversion in Premiere and then bring the DNXHD into Avid. So to be clear, don’t downconvert to 29.97, keeping the current frame rate is preferred and the project will handle it fine?

Also, with about half and half interlaced and progressive footage, going to dvd (and maybe digital also), is it better to
do the project interlaced from the start, and bring in the progressive footage, or vice versa?

Many thanks!
(note: now that I’ve looked in Premiere (cs6) there’s not an option for dnxhd 1080p59.94 in the settings)

[Kell Smith]

Thank you John, no – it’s on an external drive.

Surprisingly, I just went in to finish another project started in Premiere . AVCHD, event footage primarily and some audio files. It’s working fine, provided the audio tracks are collapsed and it doesn’t have to render waveforms. I’ve been in it for about two hours without any crashes or problems. It has crashed a few times in the past (there are 7 or 8 “Recovery copy of recovery copy X” projects), but seems okay right now.

The other one? Could barely even get into it to export the old sequences. As stated earlier, that’s mostly images and mattes, many done via replace edit from bin. Crashes like crazy even after rebuilding from scratch to make sure everything’s in order and there are no flaky file issues.

So I’m thinking there’s some other issue with Premiere not liking something about those mattes and replaced images. It will probably be fine for regular projects.
It also seems to freak out if you move too fast, or sneak up on it and do something sudden. One quick wrong move of the CTI and yo’uve got the spinning ball of death.

[Kell Smith]

Thank you Tero,

Really I’m kind of done doing major troubleshooting in Premiere at this point. If you see something that doesn’t look right, I”ll check it out, that would be great. It’s getting just getting to the point where it keeps crashing and never gets solved. It’s possible it’s mainly this project and what I am doing with the titles and mattes. The last two (AVCHD) projects before it were more stable.
The primary question is that I’m just wondering if people are still having these types of issues in later versions.

But here are the specs involved:
___________________________________________________________

Project(s) media info:

The system might be slightly outdated but should be adequate. Especially for a project consisting of fifteen second sequences edited with pictures and titles, and one five second video clip on the end. This last one was rebuilt from scratch giving special attention to make sure all the media was in the proper format and frame rate.
Avid seems to be running just fine with the same material in the project. Stable and smooth.

As for past projects that have crashed, different projects have had different material. The one right now has basically images – mostly jpegs, tiffs and color mattes, and titles. Effects are only cross dissolves and fades, on the same track.
Audio is aiff 48k. There are some motion backgrounds, only one of which I’ve used, that have all been converted to Pro Res.

Prior projects that crashed a lot were AVCHD but at some point I started converting to Pro Res and editing with that. No speed or sluggish issues since. I also try to use as few other system resources as possible when editing, freeing up all the space for the project.
One project did have constant problems which I attributed to mixed frame rates. The projects after it didn’t have frame rate issues.

Once I started collapsing audio waveforms, the problem seemed mostly solved.

_____________________________________________________

Mercury Playback Engine GPU Acceleration (open CL)

Processor Speed: 2.7 GHz
Processor Name: Intel Core i7
Total Number of Cores: 4
L2 Cache (per Core): 256 KB
L3 Cache: 8 MB
Memory: 16 GB
Boot ROM Version: MBP101.00EE.B09
SMC Version (system): 2.3f36

Graphics card
Intel HD Graphics 4000:
Chipset Model: Intel HD Graphics 4000
Type: GPU
Bus: Built-In
VRAM (Total): 512 MB
Vendor: Intel (0x8086)
Device ID: 0x0166
Revision ID: 0x0009
gMux Version: 3.2.19 [3.2.8]

Plenty of space available on the drive

[Kell Smith]

Hello Dave,
It’s on Mountain Lion. Could that be the issue?
There have been an awful lot of threads about crashes so it looks like people are having a variety of issues in a variety of versions.
In my case, I thought the crash issue was resolved, when after extensive troubleshooting, it turned out that Premiere didn’t like open audio waveforms. Making sure they were collapsed unless making a change seemed to solve the issue. Got through an entire wedding and another project without too much madness.
Then I started a project that had a lot of replaced images, titles, mattes and such. It started crashing constantly, and rebuilding from scratch didn’t help.
So… it’s all good. I needed to learn Avid anyway and was putting it off because Premiere is so nice to work in… when it works.
Do you think it could be an OS issue?

[Kell Smith]

Yep. Just did it again. It’s happening when my thumb is resting on the trackpad and one of the other fingers brushes over and touches the trackpad slightly.
Mystery solved. Hope this is helpful to someone else.

[Kell Smith]

Hmmm that’s possible although it seems to happen when my fingers are around the trackpad. It’s even happened in Preview where suddenly I will inadvertently rotate a picture.

UPDATE – Not completely sure, but I think it’s a Mac “gesture,” where you twist one finger and thumb across the trackpad. Not completely sure though, because this action can be undone with cmd-z, but it seems that the other times, cmd-z had no effect and I had to go in and reset the rotation manually. So it may still be something different.

[Kell Smith]

Thank you Ann,
No luck there either. It will only recognize the existing sequence as mono, and only recognize as stereo, or dual mono, when the source clip is dragged into the sequence.
Is there any way I can replace each edited clip as I go, and have it recognize the same in and out along with the proper audio tracks? The ways mentioned above aren’t working.

I was originally going to export these timelines to a proxy format to speed things up – but that may make things even more of a mess given these audio issues.

In the end it may not be too bad as not all of the footage had two mics, only certain areas.

—-EDIT—
All worked out – I was able to just re-edit and everything worked out. Thanks…

[Kell Smith]

Nope. Sun and exposure changes in both.