Robert Withers
12
COW Coins
8
Premiere Pro Coins
Forum Replies Created
-
Thank you Dennis, I didn’t mean to get up on a high horse. You and other Adobe folks have been very helpful in these discussions. There are a lot of things that work well with the software which is why I continue to use it.
All best regards,
RobertRobert Withers
Independent/personal/avant-garde cinema, New York City
-
Thanks for the helpful information, Dennis. I’ll file it away and meanwhile quicken my plan to upgrade my Mac laptop memory to beyond the officially supported 8 Gigs.
Best,
RobertRobert Withers
Independent/personal/avant-garde cinema, New York City
-
Dear Dennis,
Thanks for your response.
I know you Adobe guys (and gals?) have good reasons for whatever your decisions are with the software and justifications for why you are right.
The feedback here is worth whatever it is worth to you, if only to give opportunity to justify your decisions.
What I’ve never heard from any Adobe guy or gal is a response like, “Hmmn, I understand how you might think that. Here’s what we’re thinking.”
Point is, some of us don’t agree with all the decisions. But the Adobe business model seems to be working quite well so there’s no need to change, is there? And I’m a very “small” individual customer.
I post in these sessions more to interact with other editors than to expect to influence Adobe in any way.
Meanwhile, I’m working with Pr CC “January” 2014 for reasons stated above.
I hear Avid is known as a very stable NLE.
Best regards,
RobertRobert Withers
Independent/personal/avant-garde cinema, New York City
-
Thank you, Chris. I switched from FCP7 to Premiere because Apple jettisoned the idea of compatibility of editing tools over time. And now have learned that Adobe is taking the same approach with the frequent revisions that change functionality and interface. I’m still using Pr 7.0.1 “2013” because of issues with 2014 and because issues with further “upgrades” echo all over the discussion groups with each release. Unlike some, my cinema projects don’t develop as fast as Adobe’s software. And I need to be able to access them over years, not months.
Documentation and training is a real problem too, since neither Adobe nor third parties seem able to keep up with the changes. Features and buttons appear and disappear, and you are more likely to learn about them through the grapevine than any other way.
Robert Withers
Independent/personal/avant-garde cinema, New York City
-
Here’s what I found so far, with a new question. The Effect Controls in the Source Panel would not display if all clips in a video tracer were selected. It would display if one clip were selected and I could apply such controls as Field Interpolation and Field Smoothing.
So I did this to one clip.
Then I selected all clips and dragged the Frames Effect onto them from the Effects Tab in the Media Panel.
They wanted to render for an hour.Then I wanted to see what effect had actually been applied to all the clips–if the Field Smoothing of 25 had been applied, for example.
Sequence settings did not show this–showed the info about the original DV NTSC footage.
How can I asses whether the footage is now deinterlaced progressive?
Sequence into doesn’t say–clip properties don’t say–file properties freezes with no info.
Is there any way to read the current properties of the sequence after this apparent Effects processing and confirm what they now are?
Many thanks.Robert Withers
Independent/personal/avant-garde cinema, New York City
-
My screen resolution is not good enough to read your screen shots but I watched a great tutorial on how to set up a new sequence in Pr with the multiple channels you want and to set the mixer to direct the outputs to different stems.
This isn’t the one I watched but there’s a little movie in this post that seems to cover the same thing.
https://forums.creativecow.net/thread/3/937811Robert Withers
Independent/personal/avant-garde cinema, New York City
-
I had some issues using XML to transfer a timeline from FCP7 to Premiere CC.
Major failure after a certain point in the timeline.
What I had to do was export the second half of the timeline in a separate file to get it to import in Premiere.
This was a 40 minute timeline.
Try doing segments of your FCP7 timeline. Good luck.Robert Withers
Independent/personal/avant-garde cinema, New York City
-
The Clipwrap worked fine for me on Mac OS 10.8.5 for the Sony XAVC format at 60p converting to ProRes.
And then a further adventure:
I got handed some Sony XAVC-S footage via the new firmware for the same camera and the Clipwrap didn’t work for that.
divergent media recommended their EditReady 1.1.2 for the XAVC-S but it doesn’t seem to work on the Mac OS 10.8.5–wants a higher OS. (Apparently a lot of people are having trouble with this new XAVC-S format.)
I ended up bringing the XAVC-S footage into either Premiere Pro or Adobe Media Encoder CC and exporting to ProRes.
Quite a workaround but the footage came into FCP7 just fine. Of course I just happen to have Premiere cause I’m transitioning to it. If you don’t need to deal with XAVC-S you’re lucky.Robert Withers
Independent/personal/avant-garde cinema, New York City
-
Some of us are using Studio 3 FCP 7.03 on a Mountain Lion OS 10.5 with no problems. Installed FCP 7.0 from disks on the OS 10.8.5 systems, then updated to 7.03. No Aja IoHD with its drivers, though. I’m thinking this combo will run in its bell jar as long as we need it.
Robert Withers
Independent/personal/avant-garde cinema, New York City
-
I’m also using a 2012 pre-retina book running 10.8.5 with an NVIDIA GeForce GT 650M. No problems. I’m going to stick to this combo as long as I can. I’m also using CC 2013? 7.2? Good luck.
Robert Withers
Independent/personal/avant-garde cinema, New York City