[Kell Smith]

Mountain Lion – kind of afraid to update because you never know what it will affect. I do have some older software on here.
Probably we’ll never know what happened exactly – just curious about whether others have experienced this.

*here is an added issue – may or may not matter but I”ll post it – I’m also noticing interlace lines in progressive footage in the source monitor. Haven’t hunted down the issue yet. I’ll check the camera tomorrow to see if it was inadvertently recorded that way but I could swear it was progressive.

[Kell Smith]

Ok, it appears that I am talking to myself in here. Hence the echo. However, I wanted to post back in case someone has this issue in the future.
I exported the source MTS files as Mpeg 2s, put them in the stream folder along with the new xmp files, and it is recognizing them.
Settings I used were
ntsc, 640×360,29.97, quality 3.1,progressive VBR, 1 pass, min 4.00, target bit rate 10.42,
audio mpeg 1, 224 kbps, 48 khz, 16 bit, dual channel mode

A shot in the dark but seems to be working.
If anyone ever visits the thread and has a better recommendation please post it.

However, this only brought this file size down from 7.98 to 4.24, which is still too large, so I’ll probably tweak the settings for a lower size on the next card. There are three and two of them are much larger.

I’ll post back if anything changes and any problems come up in the edit or export. Otherwise, you can safely assume if I don’t post back in a week or two that all is well.

>EDIT< I was able to bring the file size of the proxies down somewhat, but in the end decided to just edit with the source AVCHD and eat the drive space. Just for simplicity's sake. So not sure if this would have worked properly or not, but it looks like it would since the files were recognized.

[Kell Smith]

Anyone out there? help…? thx

[Kell Smith]

Hi guys,
I could have sworn I posted back in here thanking you for your replies. Must have gotten distracted after writing the post or for some reason it didn’t “take.” Anyway, so thank you for your responses.
I proceeded to try and do this different ways through my system, slowly as suggested, which helped. But the process is such a MAJOR hassle.
I’ve tried several methods – in Premiere, speeding up the footage to drop frames, and also some attempts in After Effects which caused a monstrous file size for one small clip.
It seems that there should be a simple way to do this without it being such a major undertaking. It’s not a small project, there are a number of hours of footage.
THere should be a simple way to take AVCHD MTS files, capture every 30th or so frame, export it to a still, automatically, then reimport into a timelapse that doesn’t take many resources or drive space. I don’t seem to be able to find a way. Am i missing something obvious?
Is the solution right in front of me? Seems like this should be an easy task.
Thanks…

[Kell Smith]

Hmmm did I ask a really dumb question? Or a question that no one is sure how to answer? Seems like it should be right in front of me.

[Kell Smith]

Yes, what I found was that when I double-clicked the audio clip in the timeline, loading it into the source monitor, and then added markers on the fly, the clip stopped. But when I double-clicked the actual clip in the project panel, opening it in the source monitor, the markers were easily added with no stopping.
I’m working in a buggy old copy of CS5.5 and there are a lot of little derailments like this – but I’m working the way through each one.
Hope this helps someone out there.

[Kell Smith]

Thanks, I’ll check that out =)

[Kell Smith]

Checking back…anybody out there have some thoughts on this?

[Kell Smith]

Thank you so much everyone,
I somehow managed to miss a few posts from you guys further back so I’m going back through them.
I’m still working on getting the basics down, and am going to put the specific sections into practice next.
Thank you all for your encouragement. I intend to master this program one way or another.
I’m noticing a lazy streak during this that didn’t used to be there, and I don’t like it. I think I’ve gotten used to the comfort zone without realizing it. I’ve always been one who was willing to dive into the manual or do what needed to be done. The expectation was that, having become familiar with FCP, I would just glide into Avid, and I seem to have forgotten the effort that went into starting from scratch way back when. The learning curve isn’t easy, and I have found Avid to be particularly frustrating, totally non-intuitive, and since it also involves learning a new approach to editing on my part, it’s also going to require a new approach to organization.
So really, starting from scratch.
That said, it’s starting to move along.
I’ll check in and update with progress/questions/concerns.

[Kell Smith]

Thanks very much,
The basics are coming along and now I’m going to start working on this. Will post back.