Top 15 Issues/Fixes Needed in the next Premiere Pro release/update (CS6.5 or CS7)

Enthusiast ,
Mar 27, 2013

Copy link to clipboard

Copied

I’m excited for what’s coming next in Premiere Pro CS6.5 or CS7 (whichever update is next). As a former FCP7 user myself, Premiere CS6 was a quick and necessary switch (especially after changing the main keyboard shortcuts back to what I was used to). I’ve since gone back to FCP7 on occasion for certain things and I can tell you that I’m so glad I’ve switched. For all the headaches and serious errors that I still get daily/weekly with Premiere Pro CS6, it’s still definitely a big step up. I'm encouraged by staff members like Mitch W. that have expressed confidence that many of these issues will be resolved in the next release. Here is my personal list of “Top 15 issues/fixes” needed in the current Premiere Pro CS6…

(Adobe STAFF...feel free to print this out and hand it to the engineers responsible for making changes )

1) The infamous multicam FLAW. Needing no introduction…when you are editing your video in the multicam window and you hit pause or stop Premiere has decided that’s a great time to make a cut on your timeline and also switch angles back to the original angle whether you like it or not. You cannot stop ever while editing multicam without Premiere making these unwanted cuts and angle changes. Awful. Multicam in PPro is otherwise pretty nice, but this issue is terribly counter-productive especially when you are editing longer complex multicam sequences. Imagine if every time you hit pause or stop in the regular timeline it made a cut there and switched clips. Ugh. You get my point.

2) The audio meters/levels do not work while in the multicam window. A staff member in the forums (I think it was you) said this was a bug. Hope it will get fixed. The audio levels work in every other window and its essential to be able to keep an eye on the levels while editing multicam.

3) Ticktime.cpp-207 error. Ugh. What a nightmare. I have confidence that it will be fixed soon. Mitch W. from the forums is my new hero for taking on this error. How to replicate it?…simply have 6 (or 7) or more clips with the warp stabilizer effect added on the same timeline as a nested multicam clip and you get this error upon reopening your project. The more warp stabilizers you use, the more times you’ll have to hit “continue” to get through the error before you can open your project or export it to AME. I deal with this every single day because all my projects use these two elements. Most of my projects I have to hit “continue” on the error message upwards of 350-450 times to open my projects. Gets old fast.

4) Icon View order control. When you display all your clips in icon view instead of a list view (In the project window), there is no metadata to allow you to put the clips in order somehow (or at least maintain the order that you have in the list). There are roundabout workarounds, but c’mon.

5) Warp Stabilizer fixes…it is an AMAZING tool (far, far, far better than smoothcam in FCP7) BUT…it has it’s issues. Since I use hundreds of times/week (no exaggeration) I know it’s functions/flaws really well. The issues with Warp Stabilizer:
a) #3 above
b) Toggle OFF the effect after it’s applied and then hit Analyze again and PPro crashes. (easy to avoid but annoying bug)
c) If a clip is in the middle of stabilizing (not just analyzing…but the final step labeled “analyzing”) when Auto-save comes up…most of the time PPro freezes and crashes.
d) The DEFAULT “method” (in the settings for Warp Stabilizer) should NOT be “Subspace Warp”…it should be “Position, Scale, Rotation”. Why? It’s FAAAAARRRR better and more efficient. 95 out of 100 times it causes MUCH less “wobble” in the final stabilized clips AND most importantly 95 out of 100 times it scales the video less. Way better method.

6) The ability to open multiple projects simultaneously. As simple as FCP7 had it…or even better…as cool and efficient as FCPX does it would be nice.

7) The ability to mark a clip and not just a point on a timeline (because if you move the clip, the marker doesn’t go with it). I know you can use “Clip Marker” but it's very limiting, can't be moved, can't add notes, can't advance to the next marker (as far as I know). Also a marker list like FCPX has would be nice so you can see your markers all in a list at a glance and adjust them as needed.

8) Ability to select a clip in the Project window and find out where it’s used in the timeline. I LOVE how you can do the reverse and take a clip in the timeline and “Reveal in Project Window” but it would really help to go the other way around. Dealing with several hundred clips for every project I’ve missed this feature from time to time (FCPX handles this really well).

9) Add a through-edit indicator in timeline and “re-join clips” option. If you cut a clip but keep both clips together it’s just one continuous clip. But I really hope Premiere adds the not only an indicator of some sort (like FCP7s way of having two small red triangles facing each other on that cut) so you know it’s one continuous clip BUT ALSO the ability to right-click and “re-join” the two clips into one.

10) When clip is double-clicked in timeline, CTI position in source viewer should match location in timeline. This one is pretty annoying and a fix would be incredibly helpful. The way it is now is very counter-productive. Definitely hope this gets fixed ASAP.

11) Better border controls for images/videos. Can’t do much with images right now in PPro. At least allow to customize the color and size/strength of it’s borders and shadows.

12) Better support for Mac/Apple's top end computers/GPU's. I'm still surprised that 2011 top of the line iMac cards (AMD 6970M) that have 2gb of ram are not supported. I’m sure/I hope 2012 iMac’s will be supported with their new Nvidia GPU’s…but I’ll hold out hope that the top iMac (up until 3 months ago) is supported at least at it’s full power. All around better Mac support would be great considering the wave of new users coming over from FCP.

13) Opacity/Transparency issues with EXPORTED videos with Cross Dissolves, etc. For some odd reason videos exported from Premiere CS6 have issues with cross dissolves or minor transparency. I’ll try to explain…in the program window of PPro CS6 cross dissolves look fine. Also, if you take a clip and stack it on top of another clip and put the top clip at say 99% opacity instead of 100 it looks like it should in PPro. But, if you export the clips you’ll quickly see that there are issues. It’s almost like the exported videos dissolve from 5 to 95. They skip the subtle beginning (0-5%) and subtle end (95-100%) of any fade. A clip in PPro as described above that is on top of another but set at 99% will look more like 90-95% in the exported file ESPECIALLY if the two clips are contrasting (eg. top layer dark, bottom layer with bright elements). It’s like the opposit of ease-in/ease-out. I have to ease-in/ease-out of every dissolve to avoid this issue…and even then, it’s not THAT much of an “ease” as one would hope. Another user in a forum once posted a video that shows how abruptly exported videos end their transparency changes…see: THIS SAMPLE VIDEO  Perhaps this is a GPU/processing issue with AME vs. Premiere Pro but whatever it is, it should be fixed so videos you export look like the videos you edited!

14) Better control in Creative Cloud over which devices are “activated/deactivated”  We have 3 computers and it would be nice if one could log in to their Creative Cloud account and see a list of which devices they have and just toggle on/off which one’s are activated/deactivated. This is especially helpful when you are mobile and forget to deactivate one of your two home/office devices so you’re stuck now until you get back to the home/office to deactivate it. This is not a Premiere thing, but just a general wish.

15) Ability to sync multicam clips automatically using the audio. Plural eyes apparently does this well. Would be nice to have it built into Premiere like FCPX does. Select all the shots you want to sync, One button click, wait a few seconds, done.

That’s my top 15. Everything else is awesome in my opinion for what I do 10 hours a day 6-7 days a week. I’ve included bug reports/feature requests for all of these at one point but if you are someone else reading this go to the following link and ask for these issues to be fixed: FEATURE REQUEST/BUG REPORT

I wish Adobe did smaller updates more often. Because even if they were smaller updates, we’d at least know you are working on fixing some of these issues that have plagued this NLE for years. Holding off fixes for one or two big “updates” every year is tough to deal with in a world of the ever updating apps we live and play with daily on our phones. I realize Premiere is a much larger scale and far more professional than a phone app, but hopefully you get my point. Here’s to hoping the next release (NAB 2013?) resolves all my top 15 issues. Here’s to hoping that these issues will be resolved sooner than later so I can stop raising hell in various forums. I’m honestly ready to start praising and defending Premiere Pro instead of griping about it’s bugs and flaws. It’s a fantastic program “on the way” to being the best. I hope.

Views

35.6K

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Top 15 Issues/Fixes Needed in the next Premiere Pro release/update (CS6.5 or CS7)

Enthusiast ,
Mar 27, 2013

Copy link to clipboard

Copied

I’m excited for what’s coming next in Premiere Pro CS6.5 or CS7 (whichever update is next). As a former FCP7 user myself, Premiere CS6 was a quick and necessary switch (especially after changing the main keyboard shortcuts back to what I was used to). I’ve since gone back to FCP7 on occasion for certain things and I can tell you that I’m so glad I’ve switched. For all the headaches and serious errors that I still get daily/weekly with Premiere Pro CS6, it’s still definitely a big step up. I'm encouraged by staff members like Mitch W. that have expressed confidence that many of these issues will be resolved in the next release. Here is my personal list of “Top 15 issues/fixes” needed in the current Premiere Pro CS6…

(Adobe STAFF...feel free to print this out and hand it to the engineers responsible for making changes )

1) The infamous multicam FLAW. Needing no introduction…when you are editing your video in the multicam window and you hit pause or stop Premiere has decided that’s a great time to make a cut on your timeline and also switch angles back to the original angle whether you like it or not. You cannot stop ever while editing multicam without Premiere making these unwanted cuts and angle changes. Awful. Multicam in PPro is otherwise pretty nice, but this issue is terribly counter-productive especially when you are editing longer complex multicam sequences. Imagine if every time you hit pause or stop in the regular timeline it made a cut there and switched clips. Ugh. You get my point.

2) The audio meters/levels do not work while in the multicam window. A staff member in the forums (I think it was you) said this was a bug. Hope it will get fixed. The audio levels work in every other window and its essential to be able to keep an eye on the levels while editing multicam.

3) Ticktime.cpp-207 error. Ugh. What a nightmare. I have confidence that it will be fixed soon. Mitch W. from the forums is my new hero for taking on this error. How to replicate it?…simply have 6 (or 7) or more clips with the warp stabilizer effect added on the same timeline as a nested multicam clip and you get this error upon reopening your project. The more warp stabilizers you use, the more times you’ll have to hit “continue” to get through the error before you can open your project or export it to AME. I deal with this every single day because all my projects use these two elements. Most of my projects I have to hit “continue” on the error message upwards of 350-450 times to open my projects. Gets old fast.

4) Icon View order control. When you display all your clips in icon view instead of a list view (In the project window), there is no metadata to allow you to put the clips in order somehow (or at least maintain the order that you have in the list). There are roundabout workarounds, but c’mon.

5) Warp Stabilizer fixes…it is an AMAZING tool (far, far, far better than smoothcam in FCP7) BUT…it has it’s issues. Since I use hundreds of times/week (no exaggeration) I know it’s functions/flaws really well. The issues with Warp Stabilizer:
a) #3 above
b) Toggle OFF the effect after it’s applied and then hit Analyze again and PPro crashes. (easy to avoid but annoying bug)
c) If a clip is in the middle of stabilizing (not just analyzing…but the final step labeled “analyzing”) when Auto-save comes up…most of the time PPro freezes and crashes.
d) The DEFAULT “method” (in the settings for Warp Stabilizer) should NOT be “Subspace Warp”…it should be “Position, Scale, Rotation”. Why? It’s FAAAAARRRR better and more efficient. 95 out of 100 times it causes MUCH less “wobble” in the final stabilized clips AND most importantly 95 out of 100 times it scales the video less. Way better method.

6) The ability to open multiple projects simultaneously. As simple as FCP7 had it…or even better…as cool and efficient as FCPX does it would be nice.

7) The ability to mark a clip and not just a point on a timeline (because if you move the clip, the marker doesn’t go with it). I know you can use “Clip Marker” but it's very limiting, can't be moved, can't add notes, can't advance to the next marker (as far as I know). Also a marker list like FCPX has would be nice so you can see your markers all in a list at a glance and adjust them as needed.

8) Ability to select a clip in the Project window and find out where it’s used in the timeline. I LOVE how you can do the reverse and take a clip in the timeline and “Reveal in Project Window” but it would really help to go the other way around. Dealing with several hundred clips for every project I’ve missed this feature from time to time (FCPX handles this really well).

9) Add a through-edit indicator in timeline and “re-join clips” option. If you cut a clip but keep both clips together it’s just one continuous clip. But I really hope Premiere adds the not only an indicator of some sort (like FCP7s way of having two small red triangles facing each other on that cut) so you know it’s one continuous clip BUT ALSO the ability to right-click and “re-join” the two clips into one.

10) When clip is double-clicked in timeline, CTI position in source viewer should match location in timeline. This one is pretty annoying and a fix would be incredibly helpful. The way it is now is very counter-productive. Definitely hope this gets fixed ASAP.

11) Better border controls for images/videos. Can’t do much with images right now in PPro. At least allow to customize the color and size/strength of it’s borders and shadows.

12) Better support for Mac/Apple's top end computers/GPU's. I'm still surprised that 2011 top of the line iMac cards (AMD 6970M) that have 2gb of ram are not supported. I’m sure/I hope 2012 iMac’s will be supported with their new Nvidia GPU’s…but I’ll hold out hope that the top iMac (up until 3 months ago) is supported at least at it’s full power. All around better Mac support would be great considering the wave of new users coming over from FCP.

13) Opacity/Transparency issues with EXPORTED videos with Cross Dissolves, etc. For some odd reason videos exported from Premiere CS6 have issues with cross dissolves or minor transparency. I’ll try to explain…in the program window of PPro CS6 cross dissolves look fine. Also, if you take a clip and stack it on top of another clip and put the top clip at say 99% opacity instead of 100 it looks like it should in PPro. But, if you export the clips you’ll quickly see that there are issues. It’s almost like the exported videos dissolve from 5 to 95. They skip the subtle beginning (0-5%) and subtle end (95-100%) of any fade. A clip in PPro as described above that is on top of another but set at 99% will look more like 90-95% in the exported file ESPECIALLY if the two clips are contrasting (eg. top layer dark, bottom layer with bright elements). It’s like the opposit of ease-in/ease-out. I have to ease-in/ease-out of every dissolve to avoid this issue…and even then, it’s not THAT much of an “ease” as one would hope. Another user in a forum once posted a video that shows how abruptly exported videos end their transparency changes…see: THIS SAMPLE VIDEO  Perhaps this is a GPU/processing issue with AME vs. Premiere Pro but whatever it is, it should be fixed so videos you export look like the videos you edited!

14) Better control in Creative Cloud over which devices are “activated/deactivated”  We have 3 computers and it would be nice if one could log in to their Creative Cloud account and see a list of which devices they have and just toggle on/off which one’s are activated/deactivated. This is especially helpful when you are mobile and forget to deactivate one of your two home/office devices so you’re stuck now until you get back to the home/office to deactivate it. This is not a Premiere thing, but just a general wish.

15) Ability to sync multicam clips automatically using the audio. Plural eyes apparently does this well. Would be nice to have it built into Premiere like FCPX does. Select all the shots you want to sync, One button click, wait a few seconds, done.

That’s my top 15. Everything else is awesome in my opinion for what I do 10 hours a day 6-7 days a week. I’ve included bug reports/feature requests for all of these at one point but if you are someone else reading this go to the following link and ask for these issues to be fixed: FEATURE REQUEST/BUG REPORT

I wish Adobe did smaller updates more often. Because even if they were smaller updates, we’d at least know you are working on fixing some of these issues that have plagued this NLE for years. Holding off fixes for one or two big “updates” every year is tough to deal with in a world of the ever updating apps we live and play with daily on our phones. I realize Premiere is a much larger scale and far more professional than a phone app, but hopefully you get my point. Here’s to hoping the next release (NAB 2013?) resolves all my top 15 issues. Here’s to hoping that these issues will be resolved sooner than later so I can stop raising hell in various forums. I’m honestly ready to start praising and defending Premiere Pro instead of griping about it’s bugs and flaws. It’s a fantastic program “on the way” to being the best. I hope.

Views

35.6K

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Mar 27, 2013 0
168 Replies 168
Adobe Employee ,
Mar 27, 2013

Copy link to clipboard

Copied

Great list!

--Adobe Premiere Pro Engineering

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Mar 27, 2013 0
Adobe Employee ,
Mar 27, 2013

Copy link to clipboard

Copied

Also, for #8 there are a few ways to locate where clips from the project panel are used in the timeline:

1) In thumbnail view you can click on the orange filmstrip/waveform in the bottom right corner of the icon.

2) In list view enable the audio/video usage columns then click the down arrow.

3) In either view enable the preview area and see the down arrows next to usage indication.

Any one of these will open a menu with all the timecodes the clip is used at, and clicking it will take you to that location.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Mar 27, 2013 0
Enthusiast ,
Mar 27, 2013

Copy link to clipboard

Copied

SteveHoeg wrote:

Great list!

--Adobe Premiere Pro Engineering

...............

Also, for #8 there are a few ways to locate where clips from the project panel are used in the timeline:

1) In thumbnail view you can click on the orange filmstrip/waveform in the bottom right corner of the icon.

2) In list view enable the audio/video usage columns then click the down arrow.

3) In either view enable the preview area and see the down arrows next to usage indication.

Any one of these will open a menu with all the timecodes the clip is used at, and clicking it will take you to that location.

Thanks SteveHoeg!

I'm thankful for your feedback and just to know that someone from the Engineering team has seen it makes me calm.

And take #8 off my list! Sure it could maybe be a tad easier but it works. I always have the Video Usage column right next to the name of the clip as it's very important to me (because I hire other editors to work on my projects as well and need to see at a glance which clips are used and which are not when they hand over the project to me). I can't believe I never clicked that arrow. I got my other two editors to switch over to Premiere as well (former FCP7 users as well) so I'll be sure to pass that along to them.

I do have a tiny substitute for #8 then... ...it's such a minor thing, but hey, why not...

#8 (substitute): Presets should NOT be able to be re-named by just clicking on them. I've created presets which I use quite a bit. As in hundreds of times per project (don't ask) and it happens a lot that I'll click on the Preset, add it to the project and somehow in the speed of things I'll have clicked on it again or something because occasionally when I come back later I've deleted it's name. Hitting space bar to play the video after the name is accidentally highlighted and the replaced name will be blank. Takes only a few seconds to rename it but I wish that you had to right-click to "rename" it to prevent accidental renaming. I feel a little crazy wrtiing this but because my other editors use the same presets I know I'm not the only one this happens to as they've expressed the same issue. Not a big deal at all but it would be nice.

Again, thanks for your time and attention to this list!

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Mar 27, 2013 0
LEGEND ,
Mar 27, 2013

Copy link to clipboard

Copied

I sort of had anticipation of "popping a bubble," when I saw the title, but that did not happen.

I agree with most of what you took the time to write, and the rest was just not part of my normal workflow, so I have no comment. The bulk - great, and thank you for taking the time.

Looks like some from "The Mother Ship," have seen the list.

Good luck,

Hunt

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Mar 27, 2013 0
Explorer ,
Mar 27, 2013

Copy link to clipboard

Copied

Very insightful thread so thanks for posting your thoughts, OP.  To add to your list, I'd like to see full GPU support as it seems the current implementation is more limited than other NLEs like Sony Vegas.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Mar 27, 2013 0
Enthusiast ,
Mar 27, 2013

Copy link to clipboard

Copied

Bill,

I knew that there are some that simply do not have the same workflow but I figured I'd at least put this out there. Just another transfer from FCP, happy I made the jump, but looking to tighten a few spots up that need it and improve upon things that are already awesome.

By the way, on a total side note...I just saw you have 53,271 posts???!!!  That is absolutely amazing. If my math is correct that's almost 15 posts a day every day for 10 years. Holy crap. Kudos.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Mar 27, 2013 0
People's Champ ,
Mar 27, 2013

Copy link to clipboard

Copied

We love Bill and we would hold an intervention for his addiction if he wasn't so handy at answering tough questions. We realize that laying golden eggs is bad for the goose, but who can afford to cure him of such a minor flaw.

artofzootography.com

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Mar 27, 2013 0
Enthusiast ,
Mar 28, 2013

Copy link to clipboard

Copied

Nice list, however it does seem a little bit like you may be hoping that Adobe provides the Final Cut 8 package that Apple never delivered on. Having edited primarily with P-Pro for the last decade, I hope Adobe focuses more on getting the next release to run as smooth as CS5x does, strangling and crucifying all the codec and playback bugs that arose in CS6. To me, it appeared that too many of the changes in CS6 were semantic or cosmetic, meant to give a FCP user more familiarity. Why change the name of an edit function from "overlay" to "overwrite" after 15 years? Because it enhances the product, or because that is what Apple called the function in FCP? If Adobe renames the Program Monitor to the "Canvas" with the next release, I think that I might be sick. There were nice additions to the Creative Suite as a whole, but I hope the next Premiere release reverses some missteps made in CS6, and focuses more on stability and enhanced functionality. I also really hope that they have an open ear towards criticism; Apple did not and their users ended up with FCP-X

It saddens me that the fixes I want most in a future release were purposeful changes between CS5x and CS6x.

1) Provide the options for transport controls in the source and program monitors. All of the users at my office hate that the jog and shuttle were removed in CS6. JKL was an option prior to CS6 and if we liked it we would have used it. I keep reading the justification that this change was meant to save space and streamline the UI. I can't express cordially how much this bothers me to look at the empty wasted space in my CS6 UI where the transport controls should be. The experiment has gone on long enough.

2) Restore the 3 Way Color Corrector to its previous functionality. The 3 way color corrector has been effectively neutered in CS6. Where in CS5x and earlier releases one could separately target the input/output levels of Highlights, Midtones, and Shadows, CS6 has only a master input/output level control. Why is less control better? Is it a 3-Way Color Corrector or a 1-Way Color Corrector?

3) Restore Clip and Timeline markers to their previous functionality. I don't even.... I can't. A user shouldn't have to do work arounds to create a modicum of functionality. This again was an attribute that wasn't broken in earlier releases.

4) Simplify the the task of pasting media into a targeted track. As it is now, pasted items will always go to the lowest activated track instead of the targeted track.

Lastly I would like the Adobe Premiere teams to consider what an amazing accomplishment Premiere CS5x was. Upon CS5's release, a good portion of competitor's workflows became obsolete. CS5.5 refined, stabilized, and expanded functionality.

CS6 changed the UI around, moving or deleting buttons, changed keyboard shortcuts, and renamed functions. Oh, and added hoverscrub, you know...like FCPX. In exchanged there was loss of functionality, stability issues and broken codecs.

I really hope the next release is more like CS5x and less like FCPX

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Mar 28, 2013 0
New Here ,
Mar 28, 2013

Copy link to clipboard

Copied

Stephen_Spider wrote:

I hope Adobe focuses more on getting the next release to run as smooth as CS5x does, strangling and crucifying all the codec and playback bugs that arose in CS6.

I'll second that, and specifically call out the cache buffering issue between cs6 and nvidia cards, which I've posted on elsewhere, that has yet to be formally acknowledged by Adobe.  Once this fundamental flaw gets ironed out, PPro will be the most user-friendly platform I've edited on.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Mar 28, 2013 0
Enthusiast ,
Mar 28, 2013

Copy link to clipboard

Copied

Stephen_Spider wrote:

Nice list, however it does seem a little bit like you may be hoping that Adobe provides the Final Cut 8 package that Apple never delivered on. Having edited primarily with P-Pro for the last decade, I hope Adobe focuses more on getting the next release to run as smooth as CS5x does, strangling and crucifying all the codec and playback bugs that arose in CS6.

...

I really hope the next release is more like CS5x and less like FCPX

Stephen,

I actually agree with the things on your list. In fact, your #1 should have been on my list. Not having any way to jog or shuttle is something that's bothered me too. So here...

16) Add the ability to "jog" and "shuttle" clips in the source and program monitors.

Regarding wanting to make it the FCP8 that never was, although that's not my true intention, why not? Years and years ago I taught myself how to edit using Premiere but then switched to FCP in 2007 when offered a job at MLB and they used FCP. There are things that I always wished FCP would adopt that I loved so much more in Premiere, but eventually you get over that. Coming back now to Premiere, it's advanced so much and I remember the little things that I loved so much. But I would say that I genuinely are hoping for more of a CS7 than a FCPX...for sure. I did give FCPX a good 60 days and there are REALLY GREAT things that Adobe could learn from, but in the end, I wanted to pull my eyes out of my head so I came happily over to Premiere CS6. Truthfully FCP7 and Premiere Pro CS6 are very close to each other. My goal is to fix what's broken here in CS6 and to improve upon what other NLE's already do much better. How Adobe decides to do it is up to them. And why not improve upon FCP7? It was a very successful program that's very similar to CS6 and making a few of Apple's ideas better is what Google has been doing for years with their phones and they're a huge success. I actually agree with all 4 of your points because they are legitimate improvements and that is what I was going for as well. So thank you for adding to this list!

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Mar 28, 2013 0
Adobe Employee ,
Mar 28, 2013

Copy link to clipboard

Copied

DMH79 wrote:

16) Add the ability to "jog" and "shuttle" clips in the source and program monitors.

My goal is to fix what's broken here in CS6 and to improve upon what other NLE's already do much better.

Regarding what needs to be fixed and other NLEs do much better:

  • Do Avid Media Composer, FCPX, Edius, Smoke, Vegas, Media 100, Lightworks, or even Windows Movie Maker or iMovie have jog-shuttle controls? Answer: No. No modern NLE has them.
  • Do users complain about jog/shuttle missing in those products?: Never seen a complaint. Some users looking for that feature are looking for hardware alternatives, but are not really complaining.
  • Considering these things, it could be suggested that removing jog-shuttle controls are what modern NLEs are doing right and we followed suit.

This does not discount the fact that you and some of your colleagues are missing having the feature, or might not be able to manipulate playback as you'd like to with JKL.

Sorry to disappoint you, but ss I've mentioned in the past, I doubt that the controls are coming back. However, feel free to request it: http://www.adobe.com/go/wish

One of the bigger problems I see is not listed: support for AVCHD spanned clips. That is definitely a top issue since it worked fine in previous versions.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Mar 28, 2013 0
Advocate ,
Apr 04, 2013

Copy link to clipboard

Copied

Kevin Monahan wrote:

One of the bigger problems I see is not listed: support for AVCHD spanned clips. That is definitely a top issue since it worked fine in previous versions.

This is something I'll need to see fixed in CS6 before I pay any money for future versions, for what little it may be worth.  I paid a chunk of money for CS6 and I simple can not use it; I basically wasted my money.  My hope was that you guys would have figured it out reasonably quickly, but that didn't turn out to be the case.

I can't realistically justify handing you any more cash until it's fixed.  It does look like the next version has some great and useful features, but...

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 04, 2013 0
Engaged ,
Apr 04, 2013

Copy link to clipboard

Copied

Jason Van Patten wrote:

Kevin Monahan wrote:

One of the bigger problems I see is not listed: support for AVCHD spanned clips. That is definitely a top issue since it worked fine in previous versions.

This is something I'll need to see fixed in CS6 before I pay any money for future versions, for what little it may be worth.  I paid a chunk of money for CS6 and I simple can not use it; I basically wasted my money.  My hope was that you guys would have figured it out reasonably quickly, but that didn't turn out to be the case.

I can't realistically justify handing you any more cash until it's fixed.  It does look like the next version has some great and useful features, but...

Unfortunately I don't think that is going to happen.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 04, 2013 0
Adobe Employee ,
Mar 28, 2013

Copy link to clipboard

Copied

Stephen_Spider wrote:

CS6 changed the UI around, moving or deleting buttons, changed keyboard shortcuts, and renamed functions. Oh, and added hoverscrub, you know...like FCPX. In exchanged there was loss of functionality, stability issues and broken codecs.

I really hope the next release is more like CS5x and less like FCPX

Sometimes, in the name of progress, things like this happen. Established users get annoyed at changes like you mentioned, and that's no small thing. For that, we apologize.

I wouldn't say that Premiere Pro has much in common with FCPX, except the scrubbing, but even that's different. I would say, that I as a former FCP guy, LOVE the UI refresh. I was put off with so much clutter, taking away from the user experience. For me, anyway. I know some stuff got broken, but we do know about the issues, and are working hard to fix them.

It's kind of interesting that all the things that annoy you are welcomed by folks like me. I came to Premiere Pro in CS5 and didn't like what I saw at first glance. Since CS6:

  • The UI is way cleaner. This is the one thing that turned me off prior to CS6.
  • I don't use buttons much, like most editors, I'm keyboard driven. I don't mind them being removed as long as a shortcut exists. The bonus is a cleaner UI.
  • Keyboard shortcuts are more standard in CS6, meaning they've migrated to shortcuts Avid and FCP might have had in common. Editors new to Premiere Pro like this. Established Premiere Pro editors probably do not.
  • Regarding renaming items to industry standards, it's a welcome change for most. For exemple, most editors moving to Premiere Pro are used to the term Overwrite and are confused by the term Overlay. Overwrite is used in all other NLEs except Premiere Pro prior to CS5.5, not just FCP.
  • Regarding Jog Shuttle, it was not only to save space. Feedback we got from users from the product improvement program showed us that people did not really use the controls much. See my response above or this blog post: http://blogs.adobe.com/kevinmonahan/2012/07/24/alternatives-to-the-jog-shuttle-controls-in-premiere-...
  • Regarding markers, they do need to improve, but the way they were implemented (numbered markers, etc.), is probably not going to return. For sure, make feature requests about how they should be improved. "Put it back the way it was," is not as helpful. Link: http://www.adobe.com/go/wish

Thanks!

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Mar 28, 2013 0
Participant ,
Jun 27, 2013

Copy link to clipboard

Copied

I couldn't disagree more with 1 and 2, and I completely agree with 3 and 4.

My very first thought when I tried out CS5.5 was: Why would a modern NLE waste so much screen real estate with those transport controls that no one has touched since 1999? I always believed they were only included in the first place to look cool to editors who were coming from linear systems (myself among them). I stand corrected that no one used them, but for me, J-K-L does the trick.

In my very first post in this forum, I mentioned the above. I also said everything you said in #2 except precisely the opposite. I suggested they simplify the primary functions of the 3-way color correction effect, putting the main adjustments up top and keeping the rarely used adjustments out of the way. To your chagrin, Adobe took “my advice.” I could never determine what the individual highlights/mid-tone/shadows drop-downs were even connected to. I have no doubt that they were useful, now that someone has mentioned missing them, but it seemed incredibly convoluted to me.

I don't actualy know how the clip and timeline markers used to work. I just know that clip markers are not very functional now.

I completely agree with #4. The fact that they haven't changed this is even more glaring now that they have simplified track targeting for everything else. The lowest selected track was always very arbitrary.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jun 27, 2013 0
Adobe Employee ,
Mar 28, 2013

Copy link to clipboard

Copied

DMH79 wrote:

I’m excited for what’s coming next in Premiere Pro CS6.5 or CS7 (whichever update is next)....

Really appreciate this post, thanks so much! I added it to my top issues notes.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Mar 28, 2013 0
Enthusiast ,
Mar 28, 2013

Copy link to clipboard

Copied

Kevin Monahan wrote:

DMH79 wrote:

I’m excited for what’s coming next in Premiere Pro CS6.5 or CS7 (whichever update is next)....

Really appreciate this post, thanks so much! I added it to my top issues notes.

Kevin, MUCH appreciated!

(and thanks for the heads up on the Product Improvement Program).

As for Spanned AVCHD clips that you mentioned above, no doubt that is a large issue that affects many NLE's. I don't personally run into it even though I edit only footage from AVCHD cams, but it's no doubt one that is very important to many users so hopefully a fix is in the works. Again, I appreciate your adding my list to your "top issue notes". You've always been a very empathetic helper given your history with FCP so thank you for this post.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Mar 28, 2013 0
Adobe Employee ,
Apr 04, 2013

Copy link to clipboard

Copied

The next version just revealed should hopefully cross quite a few items off your list:

  • New audio clip mixer
  • Icon view sort options
  • Audio meters update during multicam
  • No more cut on multicam stop
  • Browse multiple Premiere Pro projects in the media browser
  • Option to control linear colour for GPU cross dissolves and opacity
  • Expanded GPU support
  • Through edit indicators
  • Sync by audio waveform
  • Simplified track targeting

Plus lots more: 

http://adobe.ly/14lWrrL

http://adobe.ly/16qm3jV

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 04, 2013 0
People's Champ ,
Apr 04, 2013

Copy link to clipboard

Copied

Should we be thinking in terms of CS6.5 or in terms of CS7? Was there anything in there that deserved a new number to the left of the decimal point?

artofzootography.com

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 04, 2013 0
Adobe Employee ,
Apr 04, 2013

Copy link to clipboard

Copied

We've only announced a preview of the next version, but it is a big release.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 04, 2013 0
Advocate ,
Apr 04, 2013

Copy link to clipboard

Copied

Great, but have you corrected the outstanding significant faults in CS6, e.g. the project bloating Warp Stabilizer, the AVCHD problem, the multi-cam difficulties, to list just a sample?  And how many of the new features will themselves introduce new problems?

Sorry to be negative about this, but you will walk away from CS6 leaving those who purchased it, like myself , with a slew of unsolved problems.  Just as you do with every new release.

You would do well to separate your major new releases by a greater time, and get the outstanding problems with the existing release patched, and hopefully the new release better beta tested.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 04, 2013 0
Engaged ,
Apr 04, 2013

Copy link to clipboard

Copied

It's strange how they will not mention which version they are calling it.  I wonder when it will be available.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 04, 2013 0
Enthusiast ,
Apr 04, 2013

Copy link to clipboard

Copied

Steve,

You are Santa Clause.

Your post this morning reminded me of how I felt on Christmas morning as a kid. Now, perhaps that's because I'm currently still up working on an editing project (never went to sleep last night) but I think it's also because I'm genuinely grateful for the fixes and excited for the enhancements. Honestly, my number one hope was the multicam fixes and it appears that's now fixed. I can't tell you how much I appreciate that. I'm not sure what "option to control linear colour for GPU cross dissolves and opacity" means, but I'm excited to find out. Can't wait to see the other improvements and hopefully fixes (warp stabilizer bugs (#3 and #5) squashed??) and see what you all mean by expanded GPU support. I'm guessing there's countless mac users out there like me just dying to hear Adobe elaborate on that one. What a great morning. The birds are chirping, my video is now exporting, and I can't see straight anymore. Thank you Santa. Thank you!

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 04, 2013 0
Adobe Employee ,
Apr 04, 2013

Copy link to clipboard

Copied

DMH79 wrote:

Honestly, my number one hope was the multicam fixes and it appears that's now fixed. I can't tell you how much I appreciate that.

Yes, it is. We made sure of that!

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 04, 2013 0
New Here ,
Apr 04, 2013

Copy link to clipboard

Copied

Have the choppy playback/cache buffering issues also been addressed?  This may not be as sexy as adding a whole bunch of new features, but it does impact a core functionality for many users.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 04, 2013 0
Enthusiast ,
Apr 04, 2013

Copy link to clipboard

Copied

Alan Craven wrote:

Great, but have you corrected the outstanding significant faults in CS6, e.g. the project bloating Warp Stabilizer, the AVCHD problem, the multi-cam difficulties, to list just a sample?  ...

My guess (hope) is that right now they're not fully disclosing all the bug fixes because it's less sexy to talk about than what's new and improved. For example, when the newer Toyota Camry's came out they weren't exactly advertising it by saying "Come buy the new Camry...the gas peddle no longer sticks to the floor causing the car to fly at top speed uncontrolably without stopping"

That's my hope anyway.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 04, 2013 0
Contributor ,
Apr 04, 2013

Copy link to clipboard

Copied

Kevin Monahan wrote:

DMH79 wrote:

Honestly, my number one hope was the multicam fixes and it appears that's now fixed. I can't tell you how much I appreciate that.

Yes, it is. We made sure of that!

ALLELUIA!!!  The broken Multicam in CS6 was one of my biggest gripes, and also the reason I checked out FCPX (only to come running back to Premiere since everything considered, it's soooo much better!)

Kevin, are you at liberty to shed any light on the 'Subclip scandal'?  Will be finally be able to create subclips with easily trimmable in/out points?

'Join through edits', Dupe detection in the Timeline, integrated 'Plural Eyes', excellent news!!!  Thanks for sharing.  Feels like Christmas!

One last thing: does "Option to control linear colour for GPU cross dissolves and opacity" mean that cross dissolves will finally be smooth (i.e. 0-100% fades instead of a choppy 5-95%)?  If so, YES!!!!  FINALLY!!

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 04, 2013 0
Adobe Employee ,
Apr 04, 2013

Copy link to clipboard

Copied

PierreLouisBeranek wrote:

Kevin Monahan wrote:

DMH79 wrote:

Honestly, my number one hope was the multicam fixes and it appears that's now fixed. I can't tell you how much I appreciate that.

Yes, it is. We made sure of that!

ALLELUIA!!!  The broken Multicam in CS6 was one of my biggest gripes, and also the reason I checked out FCPX (only to come running back to Premiere since everything considered, it's soooo much better!)

It's really cool we were able to fix this little glitch, I hope it improves your workflow. No more Multicam Monitor, you work all in the Program Monitor. It's much more elegant.

PierreLouisBeranek wrote:

Kevin, are you at liberty to shed any light on the 'Subclip scandal'?  Will be finally be able to create subclips with easily trimmable in/out points?

I don't know of a scandal, but yes, you can now create subclips without limits. Just uncheck the Restrict Trims To Subclip Boundaries box in the Make Subclip dialog box.

Screen Shot 2013-04-04 at 4.24.54 PM.png

PierreLouisBeranek wrote:

'Join through edits', Dupe detection in the Timeline, integrated 'Plural Eyes', excellent news!!!  Thanks for sharing.  Feels like Christmas!

We're really excited too. Glad you approve of our new features.

PierreLouisBeranek wrote:

One last thing: does "Option to control linear colour for GPU cross dissolves and opacity" mean that cross dissolves will finally be smooth (i.e. 0-100% fades instead of a choppy 5-95%)?  If so, YES!!!!  FINALLY!!

I assume so, but I should ask around before I can say that occurs.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 04, 2013 0
Contributor ,
Apr 04, 2013

Copy link to clipboard

Copied

Even better news Kevin!  Now that Premiere can create subclips without hard in/out points, it's a (big) step closer to being all it can be: the best NLE available!

Hopefully that checkbox remembers the last state used, so you don't have to uncheck it everytime you create a subclip.  Do you know the answer to that?  Outstanding news! 

BTW, I'm guessing you knew that this feature is coming up but never hinted at it in the thread I posted about subclips (as per NDA agreements).  Very well played. hehehe

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 04, 2013 0
Contributor ,
Apr 04, 2013

Copy link to clipboard

Copied

Hi Kevin,

I have a few more questions if you don't mind.

  1. In the Adobe Premiere Pro Preview PDF, it states: "Source sequences can now be edited into other sequences without nesting, retaining all of their component tracks and clips."  It sounds like this just means the equivalent of a copy/paste of all contents when dragging a sequence from the Project window into another sequence that's open in the Timeline.  Is this correct or does it mean that nests can be unnested/renested the way they can in FCPX?
  2. Has the persistent trim tool selection problem been fixed? (i.e. if a user click-selects an edit point with the Selection Tool (red indicator), they can't toggle that selection to the Ripple Tool (yellow indicator) without first unselecting the selection.  This is a royal pain for many, myself included, so hopefully this has or still can be fixed.)
  3. Can subclips be created with imbedded effects? (i.e. the way FCP7 allows users to drag/drop clips from the Timeline to a bin, with all applied effects/keyframes preserved, for use later down the road).

By the way, you were right when you wrote that you thought I'd be happy with this upgrade.  From what I've seen so far, it seems like a solid upgrade!  Just the fixes to multicam and subclips alone make it worthwhile for me.  My only concern is that I feel Adobe shouldn't use bug fixes to force users to upgrade.  For example, the well known multicam problem should have been fixed in a free update, IMO, rather than only included in the next version of PP (thereby forcing users who depend on proper multicam tools to upgrade).  I will be upgrading as soon as it's released, so it doesn't affect me, but I'm thinking about those who use multicam but won't/can't upgrade until later.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 04, 2013 0
Contributor ,
Apr 04, 2013

Copy link to clipboard

Copied

I forgot 1 big item:

4. Has the Track Matte effect finally been fixed?  (So that you can scale/reposition the clip with the Track Matte effect without having to nest it first.  Currently if you use the effect directly on a resized/repositioned clip (instead of nesting the altered clip and applying the Track Matte effect the nest), it messes up the composite's positioning and scale.)

Thanks!

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 04, 2013 0
Enthusiast ,
Apr 06, 2013

Copy link to clipboard

Copied

PierreLouisBeranek wrote:

One last thing: does "Option to control linear colour for GPU cross dissolves and opacity" mean that cross dissolves will finally be smooth (i.e. 0-100% fades instead of a choppy 5-95%)?  If so, YES!!!!  FINALLY!!

I assume so, but I should ask around before I can say that occurs.

Hi Kevin!

I too would love to know exactly what Steve meant when he said that as well. Interestingly I borrowed a co-worker's laptop that has an approved GPU and I noticed today that when GPU accleration is turned off in my project settings (so it says software only) those cross dissolve/opacity "5-95%" issues do NOT seem to appear in the project window ...BUT they do appear in the project window when GPU acceleration is turned on in the project settings. The opacity issue was also passed on to the exported video in most cases (depending on project and export settings). I know it's only been a short time so far since this little "reveal" but I'm curious if you've been able to ask around yet and find out what exactly Steve meant by his opacity quote above and if the issue I described above (#13 on my list) is resolved.

Like I said before, the new upcoming release looks outstanding. It appears that many of my top 15 are checked off and more. I'm still curious if some of the warp stabilizer issues (#3 and #5 on the list) as well as this opacity issue (#13) on my list above have been addressed but from what I've seen so far Adobe has done an amazing job of not only listening to their customers over the last year but also taking the lead in new and creative ways to expand and streamline the ways in which Premiere and other Adobe programs can be used individually and together. So be sure to thank the engineers for all their hard work. Can't wait!

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 06, 2013 0
Adobe Employee ,
Apr 06, 2013

Copy link to clipboard

Copied

DMG79 - Yes, this sounds exactly like the opacity behavior this new sequence setting gives you control over.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 06, 2013 0
LEGEND ,
Apr 06, 2013

Copy link to clipboard

Copied

  • Has the persistent trim tool selection problem been fixed? (i.e. if a user click-selects an edit point with the Selection Tool (red indicator), they can't toggle that selection to the Ripple Tool (yellow indicator) without first unselecting the selection.  This is a royal pain for many, myself included, so hopefully this has or still can be fixed.)

Thats not true.  I have a Toggle set up to do exactly what you are saying.

In my case  Shift-Z.  ( Custom KB Setting)

This toggles thru any of the edit Modes

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 06, 2013 0
Contributor ,
Apr 06, 2013

Copy link to clipboard

Copied

You're right shooternz, you can toggle through every edit Mode with a shortcut.  So I should have been more specific.  What I want to know is if the new version allows users to immediately toggle back and forth between the left trim and the left ripple edit modes by hitting/releasing the Ctrl modifier, for example.  Not being able to do this is counter intuitive and very annoying IMO.  The current toggle isn't a good enough work around since it can require several keystrokes to reach the desired tool instead of just one, in which case it's often faster to simply deselect and reselect the edit point with the desired tool.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 06, 2013 0
LEGEND ,
Apr 06, 2013

Copy link to clipboard

Copied

I u nderstand your point entirely ...because the Default...would not be my choice as default ....but I customised it to Shift -Z so its ergo efficient and convenient for the purpose.

Actually I can zip thru the modes faster than I can even remember which one ...in which direction ...that I want or need at the time. A minor delay lets mybrain catch up with my fingers. 

Dont think my head  would cope having  a separate shortcut for all the modes.

Editing does not have to be about speed...its  craft.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 06, 2013 0
Enthusiast ,
Apr 06, 2013

Copy link to clipboard

Copied

SteveHoeg wrote:

DMG79 - Yes, this sounds exactly like the opacity behavior this new sequence setting gives you control over.

Thanks Steve...excited to see how it works.

I'll cross my fingers for #3/5 on my list. Awesome improvments. Everyone is excited. Thank you.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 06, 2013 0
Participant ,
Apr 07, 2013

Copy link to clipboard

Copied

Speaking of multicam fixes, one thing I noticed while watching the Lynda.com series on the new Premiere features was that while the person presenting the course was cutting a multicam clip, the audio appeared to stay intact! 

It's possible that the audio was a separate clip and I'm just fantasizing here, but this would be a much welcomed change in the behavior of multicam.  It's always baffled me why there wasn't at least an option to leave the audio alone.  And too many cuts to the audio always caused Premiere to have to "render required files", which also threw me for a loop.  Along with the way that instead of mixing the audio from the source sequence, it only played back what was on track one.  Truly quirky behavior.

So I'm hoping what I saw in that Lynda series was an indication that this stuff got ironed out. 

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 07, 2013 0
Contributor ,
Apr 07, 2013

Copy link to clipboard

Copied

shooternz wrote:

Editing does not have to be about speed...its  craft.

But anything that gets in the way of an editor's creative flow does hinder the craft.  Of course we can get around this, but it's undeniable that the more an NLE gets out of the way by offering fast, intuitive tools, the better it is at supporting our craft of editing.

PPCS6's stubborn edit point selections, that can't be toggled between trim and ripple with a simple press of the Ctrl key, is a clear instance of the NLE getting in the way of the editor's workflow.  This current behavior is illogical and frustrating.  Using a keyboard shortcut as you do to toggle between all of the trim edit modes is not intuitive and efficient, since it requires learning yet another shortcut, and it isn't nearly as fast as pushing/releasing the Ctrl key, which can be accessed 'blindly' (i.e. without diverting one's attention from the screen) due to its favorable position in the bottom left corner of the keyboard.  IMO, one of the best things about PP is that you can instantly toggle between the trim and ripple tools on the fly with the Ctrl key.  This was workflow genius on Adobe's part!  But to not allow the same brilliant toggle once an edit point is selected?  Sorry to say, but that's just down right stupid.

There shouldn't even be a debate about 'if' Adobe should fix this.  It's a workflow haste that needs to be fixed for the sake of efficiency and allowing us to do our craft without getting in our way with unnecessary restriction.

Then again, maybe it has already been fixed in PP Next.   Can anyone confirm this?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 07, 2013 0
Enthusiast ,
Apr 07, 2013

Copy link to clipboard

Copied

MonkeyEatsMonkey wrote:

Speaking of multicam fixes, one thing I noticed while watching the Lynda.com series on the new Premiere features was that while the person presenting the course was cutting a multicam clip, the audio appeared to stay intact! 

It's possible that the audio was a separate clip and I'm just fantasizing here, but this would be a much welcomed change in the behavior of multicam.  It's always baffled me why there wasn't at least an option to leave the audio alone.  And too many cuts to the audio always caused Premiere to have to "render required files", which also threw me for a loop.  Along with the way that instead of mixing the audio from the source sequence, it only played back what was on track one.  Truly quirky behavior.

So I'm hoping what I saw in that Lynda series was an indication that this stuff got ironed out. 

Hi...you can edit multicam in the current version of Premiere without the audio being edited for sure. I'm sure there are several ways to do this but what I normally do is stack all my clips on top of each other (sync'd of course) and then alt+select the video tracks only and then right-click and hit "NEST". Then right-click and select "MULTICAM>ENABLE". Done. Now you have all your audio tracks sitting there and only the video tracks are multicam enabled. Like I said, I'm guessing there are other ways to do this but I've never had an issue with audio following video in my mulitcam cuts. My issue was always that audio meters/levels didn't work and when you hit stop or pause during a multicam edit PPro would make a cut in the timeline and sometimes switch angles but it looks like both of those issues are resolved in the upcoming version...thank god! Hope that helps!

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 07, 2013 0
Participant ,
Apr 07, 2013

Copy link to clipboard

Copied

DMH79 wrote:

I'm sure there are several ways to do this but what I normally do is stack all my clips on top of each other (sync'd of course) and then alt+select the video tracks only and then right-click and hit "NEST". Then right-click and select "MULTICAM>ENABLE". Done.

I never even thought to try this!  I usually just drag and drop the entire sequence full of synced clips into another sequence (audio and all) and use the whole thing as my multicam clip.  But this actually works!  Thanks for the tip. 

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 07, 2013 0
Guide ,
Apr 08, 2013

Copy link to clipboard

Copied

Steve, could you shed some light on Smart Rendering: will it work in a scenario with Adobe Dynamic Link involved?

Here is the workflow. When I'm done with complex dynamically linked comp, and it's ready for rendering digital intermediate, there are two options:

- send the composition to After Effects Render Queue;

- send the composition to Adobe Media Encoder.

Pros for the latter one:

- an ability to keep working in After Effects while AME is rendering.

Cons:

- AME doesn't include the After Effects project link into the media file metadata. Hence, it's impossible to use 'Edit Original' option in PrPro timeline.

So as to enjoy the best of both worlds, I render out dynamically linked comp in AME and then set that digital intermediate as a proxy for the comp.

Pros:

- no needs to import and replace anything in PrPro project;

- an ability to keep working in After Effects while AME is rendering;

- an ability to use 'Edit Original' option in PrPro timeline.

Cons:

- since dynamiclinkmanager is involved, there is slight performance worsening: without rendering preview the playback in full resolution may be jittery (at least on my machine, which is not a modern multicore beast, but that's not an issue at all though).

So, the question is: will Smart Rendering be able to recognise my digital intermediate set as a proxy for dynamically linked comp and, therefore, not to re-encode the piece (considering the DI's and the final output formats are identical)?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 08, 2013 0
Participant ,
Jun 27, 2013

Copy link to clipboard

Copied

I have been unabashedly pushing for Premiere Pro to become more like FCP7.

When I tried Premiere Pro CS5.5 a year and a half ago, it was somewhat Windows-y and had so many silly and seemingly easily correctable flaws that I almost gave up on it. (And those visual jog controls took up a crazy amount of space for controls that no one had touched since 2000 if they knew about J-K-L.)

But the overall editing paradigm was very similar to Final Cut Classic's. So I submitted my feature requests, posted a long blog article, and lo and behold, Adobe took some wonderful steps in the right direction with CS6. I guess I wasn't the only one clamoring for those things.

With CC, I think the Final Cut Pro 8 I've been not-so-patiently waiting for has pretty much arrived. Now that it has, I hope Adobe concentrates on stability, another hallmark of FCP7.

My list of 88 gripes has been reduced to 63: Premiere Pro CC: Wish List Scorecard

Back to DMH79's original post:

1, 2) That's great that the multicam flaws has apparently been corrected.

3, 5) Warp Stabilizer has been very buggy from the start. It's super awesome when it's not causing crashes. I haven't had a chance to test it extensively in CC. How's it looking?

4) The Project panel is still pretty slipshod when it comes to arranging and previewing clips. I second everything you said.

Additionally, when you double-click a bin, it never remembers the window size. Is this version 1.0?

Here's what I would really like to see also: get rid of the tiny little thumb in the Preview Area and make it so that a single click on a clip displays the clip in the Source Monitor panel. I tend to leave the Project viewer in list mode. I would love to use the arrow keys or click on clips — utilizing the sorting and info that comes with list view in tact — and immediately see the clip in the nice big Source Monitor panel.

6) The ability to open multiple projects simultaneously has been on just about everyone's list for a long time. Yes, please!

7) Clip marking: It drives me absolutely crazy that you can't simply select a clip and mark a frame.

8) As far as the ability to select a clip in the Project panel and find out where it’s used in the timeline, that would definitely be nice. The only thing is that I want them to rethink the whole manner in which clips in the Project panel are connected to clips in the Timeline.

For instance, if you change the name of a clip in a bin, it doesn't change the name in the timeline. That's fine. Yet, I can't delete a clip from a bin if it's been used in any sequence in the entire project without removing it from that Sequence. Are they connected or not?

This brings me to another big gripe, which someone mentioned above, which is that you can't drop an effect or keep effects attached to clips in the bins. That seems pretty basic to me coming from FCP.

9) They added a “Join Through Edits” if you right click on a through edit. Just note that you have to turn on “Show Through Edits” in the Timeline settings to see them.

10) I can't help but notice that this is the exact wording of my gripe #51! Double clicking a clip in the timeline should definitely move the CTI in the Source panel to the same frame. It's super annoying.

11) Better border controls for images/videos: Yeah, how about any border controls? It's great that I can jump right into Photoshop to add a border to a still, but that would be like having to Dynamic Link over to After Effects to add a vignette. Oh, wait…

12) Better support for the GPUs of top-of-the-line iMacs has been literally #1 on my list since making the switch. I have given up hope on this one. The very latest iMacs have NVIDIA cards, but not the ones from just a year or two ago.

13) Opacity/Transparency issues with EXPORTED videos with Cross Dissolves: I haven't come across this one, but it sounds irritating. I generally export to ProRes and then do my compression in Apple Compressor, because Media Encoder's H.264/QuickTime compression is visibly inferior at the same bit rates.

14) This makes sense. Have there been any improvements to activation/deactivation controls in Creative Cloud?

15) They added syncing by waveform for Merged Clips. I have not had any luck with this yet. It didn't work when I tried to use it, but maybe I'm doing something wrong.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jun 27, 2013 0
Enthusiast ,
Jun 27, 2013

Copy link to clipboard

Copied

Hi Dax!

Thanks for "bringing it all back home" again after this thread went in many directions. I've only limited PPro experience so far with a lot to like, but I had to stop and go back to CS6 due to the multicam bug mentioned below. See my responses underlined in bold below. Thanks!

Dax Roggio wrote:

I have been unabashedly pushing for Premiere Pro to become more like FCP7.

When I tried Premiere Pro CS5.5 a year and a half ago, it was somewhat Windows-y and had so many silly and seemingly easily correctable flaws that I almost gave up on it. (And those visual jog controls took up a crazy amount of space for controls that no one had touched since 2000 if they knew about J-K-L.)

But the overall editing paradigm was very similar to Final Cut Classic's. So I submitted my feature requests, posted a long blog article, and lo and behold, Adobe took some wonderful steps in the right direction with CS6. I guess I wasn't the only one clamoring for those things.

With CC, I think the Final Cut Pro 8 I've been not-so-patiently waiting for has pretty much arrived. Now that it has, I hope Adobe concentrates on stability, another hallmark of FCP7.

My list of 88 gripes has been reduced to 63: Premiere Pro CC: Wish List Scorecard

Back to DMH79's original post:

1, 2) That's great that the multicam flaws has apparently been corrected.  Definitely nice not to have to deal with these two issues any more. Tested, and approved. HOWEVER, a new bug has infected and crippled the new CC multicam: http://forums.adobe.com/thread/1236698?start=0&tstart=0

3, 5) Warp Stabilizer has been very buggy from the start. It's super awesome when it's not causing crashes. I haven't had a chance to test it extensively in CC. How's it looking? I have only used it about 10-15 times on one project but I then stopped the project because of the multicam issue above and went back to CS6. But the ticktime error is gone I believe. It still has "Subspace Warp" as the default method in the settings which is unfortunate for the reasons I mentioned. I use multicam and stabilizer so much and really I have enjoyed the warp stabilizer experience outside of the few little gripes and I'm excited to try out VFX in AE soon.

4) The Project panel is still pretty slipshod when it comes to arranging and previewing clips. I second everything you said.

Additionally, when you double-click a bin, it never remembers the window size. Is this version 1.0?

Here's what I would really like to see also: get rid of the tiny little thumb in the Preview Area and make it so that a single click on a clip displays the clip in the Source Monitor panel. I tend to leave the Project viewer in list mode. I would love to use the arrow keys or click on clips — utilizing the sorting and info that comes with list view in tact — and immediately see the clip in the nice big Source Monitor panel.  I actually think those are two great ideas! Single click display and arrow key navigation would be awesome. Make a feature request and maybe in 2015 we'll see them! I kid of course...sort of.

6) The ability to open multiple projects simultaneously has been on just about everyone's list for a long time. Yes, please!  The 15th post in this thread mentions that you can browse multiple PPro projects using the media browser. Haven't tried yet, but it's better than nothing. It's no FCPX in this regard, but again, better than nothing I guess.

7) Clip marking: It drives me absolutely crazy that you can't simply select a clip and mark a frame. Markers have been improved but again, I stopped messing around with CC when I hit the multicam wall, so I've yet to see if this is possible. Others in this forum probably know more about this.

8) As far as the ability to select a clip in the Project panel and find out where it’s used in the timeline, that would definitely be nice. The only thing is that I want them to rethink the whole manner in which clips in the Project panel are connected to clips in the Timeline.  You actually can do this. I just didn't know at the time. See post #2 in this thread.

For instance, if you change the name of a clip in a bin, it doesn't change the name in the timeline. That's fine. Yet, I can't delete a clip from a bin if it's been used in any sequence in the entire project without removing it from that Sequence. Are they connected or not?

This brings me to another big gripe, which someone mentioned above, which is that you can't drop an effect or keep effects attached to clips in the bins. That seems pretty basic to me coming from FCP.

9) They added a “Join Through Edits” if you right click on a through edit. Just note that you have to turn on “Show Through Edits” in the Timeline settings to see them.  Yes. Seems to look and work real nice in my limited time with CC. Great!

10) I can't help but notice that this is the exact wording of my gripe #51! Double clicking a clip in the timeline should definitely move the CTI in the Source panel to the same frame. It's super annoying.  It IS the exact wording from your site because I wrote this post after reading through yours and I never knew how to describe this until I read your post so I copied . Not sure if this made it into CC.

11) Better border controls for images/videos: Yeah, how about any border controls? It's great that I can jump right into Photoshop to add a border to a still, but that would be like having to Dynamic Link over to After Effects to add a vignette. Oh, wait…  Not sure about this yet. Still have to check. I saw drop shadow in CC, but that might have been in CS6. But yeah, more border controls would be nice.

12) Better support for the GPUs of top-of-the-line iMacs has been literally #1 on my list since making the switch. I have given up hope on this one. The very latest iMacs have NVIDIA cards, but not the ones from just a year or two ago. They do now support all GPU's with more than 1GB of VRAM and so my 2011 iMac with the AMD 6970M w/ 1GB VRAM is now GPU accelerated. That's nice. I'm surprised this card (which was the highest end card of 2011-late 2012's iMac's didn't get officially "supported" but at least it works now.

13) Opacity/Transparency issues with EXPORTED videos with Cross Dissolves: I haven't come across this one, but it sounds irritating. I generally export to ProRes and then do my compression in Apple Compressor, because Media Encoder's H.264/QuickTime compression is visibly inferior at the same bit rates.  I haven't tested this one either on the new CC. Post #15 did mention something about this being helped in CC, but it's a hard one to describe so I'll have to check myself if its solved. It's crazy that an export would look different than what you see on the timeline.

14) This makes sense. Have there been any improvements to activation/deactivation controls in Creative Cloud?  No. Adobe was nice about my issue and gave me a free month which I didn't ask for, but honestly I'd rather pay for that month and have the ability/control so that I don't get "locked out" of my own projects ever again. This solution seems reasonable and efficient. I won't hold my breath, but you never know.

15) They added syncing by waveform for Merged Clips. I have not had any luck with this yet. It didn't work when I tried to use it, but maybe I'm doing something wrong.  The one long timeline I sync'd by audio did work. So that's nice. I never double checked it was perfectly sync'd but it looked good to me. Again, I stopped working on CC, when I re-opened my multicam project and it was completely messed up due to the multicam bug in the link above (#1)...so I'm back on CS6 for now. Sigh.

My only new gripe in limited use so far (beyond the new awful multicam bug described above) is that if you change the "appearance" to a lighter background in Premiere Pro CC, you can't see the in and out markings/area in the source and project window. In CS6, changing appearance changed the color of that "work area" to light blue to work with the lighter background, but it seems as if Adobe didn't optimize the lighter background for actual use as the in/out area in PPro CC remains light in color and basically is invisible when you change appearances. Now, I agree that the dark background looks MUCH cooler and I really do like it, but it's hard on my eyes after 10hrs. a day - 6 days/week so I kind of need to change it to light background...but sadly, Premiere Pro CC's version of the light background is not so great. I submitted a feature request...but since it's not a bug report, I may be at the back of the line.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jun 27, 2013 0
Contributor ,
Jun 27, 2013

Copy link to clipboard

Copied

Think of PPro as more usage than simply editing and how many plugins there are. Lots people never truly leave PPro.

DMH79

This brings me to another big gripe, which someone mentioned above, which is that you can't drop an effect or keep effects attached to clips in the bins. That seems pretty basic to me coming from FCP.

I know everyone has different workflows and habits but I would am this one more at the Source Monitor. Depending on where you get the clips is an important thing. I have seen some editors pull the full reals into the project as bins. I dont use this method I prefer to use the media browser so that the clips that end up in my asset window are actually in the sequence or have been used in the sequence.

This gives me the a raw file that is always there and can be reused or recut. It still references the file on hdd but is in many ways its on source within the project.

Why i am this at the source monitor is that is that once a clip has been semi graded or CC'ed, when it is dbl clicked it loads with no effects even though when you switch to the effects window you can tweak that grade and see changes in the sequence monitor.

Having it load to the souce monitor with the effect on it is more efficient for matching light grades without ganging another monitor to the sequence. That can be really good for multi-screen editors who would prefer to have one monitor with near uniform color across the screen. I know that you should use an external but for me it is faster to get a light grade and then use my external through and I/O to finalize.

Here's what I would really like to see also: get rid of the tiny little thumb in the Preview Area and make it so that a single click on a clip displays the clip in the Source Monitor panel.

I actually prefer having to toggle from source to effects. Because there are no effects seen on a clip when double clicked to load in the source monitor from the sequence. there is a lot of dependancy on the sequence monitor to see how you are effecting the clip. This is why i gang an extra monitor to the sequence monitor and put it on my second screen for reference. I toggle it from ganged to unganged to hold shots.

If you have a single click load video to the source monitor, what happens when your primary concern is the effects?

Currently in cs6 you can click a point in the sequence and see whats in the sequence monitor. When you click once you get the effects for that clip if that is the last tab used in the source monitor. Add this feature to the 3rd monitor and you get reference for your effects.

Its not everyones style but i am sure there are other who do the same. I used fcp until FCPX then i held on to FCP7 until i got use to premier.


Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jun 27, 2013 0
Participant ,
Jun 27, 2013

Copy link to clipboard

Copied

I didn't know about the increased support for AMD GPUs with 1 GB of VRAM. Sweet.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jun 27, 2013 0
Adobe Employee ,
Dec 12, 2013

Copy link to clipboard

Copied

DMH79 wrote:

My only new gripe in limited use so far ... is that if you change the "appearance" to a lighter background in Premiere Pro CC, you can't see the in and out markings/area in the source and project window.

The contrast of selected track and the In/Out range has been changed in the CC7.2 update. More to your liking?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Dec 12, 2013 0
Enthusiast ,
Dec 12, 2013

Copy link to clipboard

Copied

Yes, thank you. A very small change but it makes a difference. Really appreciate it Mark.

I'd have to say though that while I'm SOOOO glad that the AME Bluray bugs were squashed (THANK YOU AME Team!!!) now we're just hoping this bug when saving a project is taken care of that has gone through 4 releases now. It's KILLING us!:

BUG FIX REQUEST (still around since 7.0):

"Warp Stabilizers are the cause of Premiere freezing up when a project is Saved (or Auto-Saved)"

http://forums.adobe.com/thread/1278013

Because we use warp stabilizer a lot, every 30 minutes I have to stop working for close to one minute while my GPU accelerated timeline "resets" from RED to YELLOW (during that time you cannot edit) if you toggle between sequences. It's easily repeatable and cross-platform as you see in the link above. I cannot stand it. Please Mark, put in a good word on this one and kill it. I know many people don't see it because they may not use this effect as much as we do, but can you imagine your NLE temporarily freezing up basically every 30 minutes. It's maddening.

Finally...

LINGERING FEATURE REQUEST:

Drag/Drop should override Source Patching.

http://forums.adobe.com/message/5572713#5572713

(see post #37)

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Dec 12, 2013 0
Adobe Employee ,
Dec 12, 2013

Copy link to clipboard

Copied

Since you say "still around," I gather you've tested this warp stabilizer issue in 7.2, but I wanted to confirm that. I thought it might have been fixed along with this bug: "Significant delays loading projects or exporting projects with Warp Stabilizer."

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Dec 12, 2013 0
Enthusiast ,
Dec 12, 2013

Copy link to clipboard

Copied

Mark Mapes wrote:

Since you say "still around," I gather you've tested this warp stabilizer issue in 7.2, but I wanted to confirm that. I thought it might have been fixed along with this bug: "Significant delays loading projects or exporting projects with Warp Stabilizer."

Hi Mark. Yes, it's still around from 7.0 thru 7.2

The other issue I don't think I mentioned in a forum thread. I actually pointed it out to Steve Hoeg in a PM and he was able to reproduce the issue and said that they'd fix it. Sound like they did which is great. It was a delay with sequences with multiple warp stabilizers where when you hit export in 7.1 (not present in 7.0.1) there would be a delay of SEVERAL MINUTES before the dialog box would open. The more warps, the longer it took. Really glad that's gone now. )

But yeah, the bug/issue with saving projects as mentioned in that thread above is still here in 7.2  ...

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Dec 12, 2013 0
LEGEND ,
Jun 27, 2013

Copy link to clipboard

Copied

make it so that a single click on a clip displays the clip in the Source Monitor panel.

Oh, I would hate that.  If I want a clip loaded, I'll load it.  I don't want it done by default.  Otherwise my Source Monitor would get loaded with all kinds of clips I actually don't want to see when I'm moving between them.

you can't simply select a clip and mark a frame.

You're leaving out that all important step of finding the frame to mark, and where is that best done?  Source Monitor!  Which is where you set markers quite easily.  So I'm a little confused about exactly what you're looking for here.

For instance, if you change the name of a clip in a bin, it doesn't change the name in the timeline. That's fine. Yet, I can't delete a clip from a bin if it's been used in any sequence in the entire project without removing it from that Sequence. Are they connected or not?

I believe the current behavior is the most useful.  It makes little sense to have it in a sequence without being in a bin, so let's keep that.  And since you can rename clip instances in the sequence, it'd be frustrating to have those all suddenly change because you changed the name of the clip in a bin after you laid down (and possibly renamed) those instances.  (Take note that any instances laid down after the rename do show the new name.)

you can't drop an effect or keep effects attached to clips in the bins.

You can get there with nesting for the time being.

Double clicking a clip in the timeline should definitely move the CTI in the Source panel to the same frame.

It does.

Media Encoder's H.264/QuickTime compression is visibly inferior at the same bit rates.

"Adobe Media Encoder is much easier to use than Compressor, encodes faster, and produces much higher quality output, as you can see in the video that accompanies this article."

http://www.eventdv.net/Articles/News/Feature/Tutorial-Encoding-H.264-Video-in-Adobe-Media-Encoder-CS...

They added syncing by waveform for Merged Clips. I have not had any luck with this yet. It didn't work when I tried to use it, but maybe I'm doing something wrong.

It hasn't yet successfully synced for me either.  Though the levels were admittedly low, and there was no 'clap' to work from, just room noise and dialog.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jun 27, 2013 0
Participant ,
Jun 27, 2013

Copy link to clipboard

Copied

Oh, I would hate that.  If I want a clip loaded, I'll load it.  I don't want it done by default.

Well, I would find it extremely useful. A similar feature is one of the better aspects of FCPX. I would want it to be a mode that could be toggled on or off though.

You're leaving out that all important step of finding the frame to mark, and where is that best done?  Source Monitor!


Finding the frame to mark? That's the point. Having stopped the CTI in the timeline, I want to mark that frame in that clip. Opening it in the source viewer is an extra and needless step.

I believe the current behavior is the most useful.  It makes little sense to have it in a sequence without being in a bin, so let's keep that.  And since you can rename clip instances in the sequence, it'd be frustrating to have those all suddenly change because you changed the name of the clip in a bin after you laid down (and possibly renamed) those instances.

It makes little sense to have zero connection between a clip in the bin and a clip in the timeline OTHER than not being able to delete the one in the bin. If the two instances contained any other kind of link at all, such as maintaining the same applied effects, correspondence of file name changes, or correspondence of changes to the in/out point, I might understand the thinking.

I regularly place copies of clips into temporary bins. When I'm done with a bin, I can't delete it if I used even just one of the clip copies, even if the original clip still exists in another bin. I end up creating a “Trash” bin, which seems silly, since it's all non-destructive. All clips are really just symbolic links to media files. I'm not trying to delete the actual file.

You can get there with nesting for the time being.

I suppose that's true. It could be simpler.

It does.

It doesn't.

Not after the first time. The very first time you open a timeline clip in the Source panel, it corresponds. Any time after that, it does not. This would be less of an issue if I could mark a clip directly in the timeline, per my other point. Instead, if stop the CTI in the timeline and want to work with that frame in the Source panel, I have to visually find it. I can't just mark it and I can't just double-click it to get it to match.

"Adobe Media Encoder is much easier to use than Compressor, encodes faster, and produces much higher quality output, as you can see in the video that accompanies this article."

If we pretend for a second that that article was some kind of unbiased, scientific test, I can only say that in my personal experience, Media Encoder does not output QuickTime files with the same quality as Compressor. I agree that Media Encoder is easier to use. I like it, actually. And it may very well be faster or perform better with certain codecs and wrappers.

It hasn't yet successfully synced for me either.

I'm glad to hear that I'm not the only one who wasn't able to get the waveform sync to work. In my case, there were very clear sticks and the audio of both tracks was pretty good.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jun 27, 2013 0
Guide ,
Jun 28, 2013

Copy link to clipboard

Copied

It makes little sense to have zero connection between a clip in the bin and a clip in the timeline OTHER than not being able to delete the one in the bin. If the two instances contained any other kind of link at all, such as maintaining the same applied effects, correspondence of file name changes, or correspondence of changes to the in/out point, I might understand the thinking.

An item in the Project panel is a reusable asset, which may (footages, stills, audio files) or may not (sequences, synthetic assets) refer to a file on a disk. An item in the timeline is an instance of a particular asset in the Project panel, it doesn't refer to anything other than this asset. You may have several different items in the timeline, which refer to the same asset in the Project panel. Deleting this asset in the Project panel should and does delete its instances within sequences. Not sure how it can be clearer and why you want to delete an asset, which you used in the project, without deleting its instances within sequences.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jun 28, 2013 0
Participant ,
Jun 28, 2013

Copy link to clipboard

Copied

The limited comparison I did between AME and Compressor made me feel that AME output H.264 files that are marginally better looking than those of Compressor, so that might depend on what you feed them. But it mostly showed that AME is way, way faster.

Fuzzy Barsik > that's the way it worked in FCP, actually I got used to the way Premiere works, except one thing : when you import a sequence that reference assets you already have loaded in your project, Premiere should be able to detect it and link to them (in the same way Resolve does for instance) instead of importing the assets again and leaving you with two or more different instances of the same assets.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jun 28, 2013 0
Guide ,
Jun 28, 2013

Copy link to clipboard

Copied

Better yet it should ask how you want to import project assets: whether to create duplicated copies or merge with those already in the project.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jun 28, 2013 0
Participant ,
Jun 28, 2013

Copy link to clipboard

Copied

That would be perfect indeed.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jun 28, 2013 0
Participant ,
Jun 28, 2013

Copy link to clipboard

Copied

You hit upon the heart of my issue with the Premiere system. Even if you're not importing a sequence, you can end up with many different instances of the same asset.

I've adjusted my workflow for Premiere, but I prefer the FCP way. It allows me to keep my Project panel much more streamlined and organized.

The way I like to work is to copy clips into different bins to categorize them. The same clip may be in “closeups,” “interviews,” “opening montage,” etc. It could be in 20 different bins. I may decide I don't need the “closeups” bin but I can't delete it if I used one of those instances, even though it could just as easily come from “interviews” or someplace else.

At a more basic level, I just like to delete a clip from a bin after I use it in many cases, leaving behind just the clips I'm still trying to place. It's annoying not to be able to do that, especially if I have still have another instance of the clip stored in another bin anyway. I end up with a bunch of “used clips” bins in addition to all the original categories. Sometimes they fill up with multiple instances of the same clip.

Also, I save versions of sequences. Sometimes I want to delete a bin, but if a clip was used in some old sequence I either have to figure out which clip it is and move it somewhere else or accept that it will disappear from that sequence. That's a problem if I ever want to reference that earlier version.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jun 28, 2013 0
Guide ,
Jun 28, 2013

Copy link to clipboard

Copied

Even if you're not importing a sequence, you can end up with many different instances of the same asset.

That's rather an advantage.

The same clip may be in “closeups,” “interviews,” “opening montage,” etc. It could be in 20 different bins.

That's what metadata are for.

I may decide I don't need the “closeups” bin but I can't delete it if I used one of those instances, even though it could just as easily come from “interviews” or someplace else.

You can easily detect how many times an asset in the Project panel is used and where exactly: click the triangle on the right of the asset description next to the small preview icon in the Project panel, select an item from the list and you'll be brought directly to the according place in the timeline. Here you can easily replace it with an asset from another bin. And no, that's not any sort of inconvenience and extra steps to accomplish a simple operation, that's the matter of both PrPro greater flexibility and your decision how to organise (reorganise) your project.

I just like to delete a clip from a bin after I use it in many cases, leaving behind just the clips I'm still trying to place. It's annoying not to be able to do that...

That's the sole matter of your habits. There is nothing wrong with PrPro here. I would hate if it behaved differently.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jun 28, 2013 0
LEGEND ,
Jun 28, 2013

Copy link to clipboard

Copied

Having stopped the CTI in the timeline, I want to mark that frame in that clip. Opening it in the source viewer is an extra and needless step.

I can see that.  Just add a modifier key to set a Clip Marker instead of a Sequence Marker.  But it's still two keystrokes, same as now.  (F for Match Frame, and M for Marker.)

The very first time you open a timeline clip in the Source panel, it corresponds. Any time after that, it does not.

That's because you're no longer loading it into the Source Monitor.  It's already there.  To get what you want, use Match Frame. (F)

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jun 28, 2013 0
LEGEND ,
Jun 28, 2013

Copy link to clipboard

Copied

I just like to delete a clip from a bin after I use it in many cases, leaving behind just the clips I'm still trying to place. It's annoying not to be able to do that...

That's the sole matter of your habits. There is nothing wrong with PrPro here. I would hate if it behaved differently.

I agree.

Likes