-
40. Re: Top 15 Issues/Fixes Needed in the next Premiere Pro release/update (CS6.5 or CS7)
MonkeyEatsMonkey Apr 7, 2013 11:01 AM (in response to DMH79)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.
-
41. Re: Top 15 Issues/Fixes Needed in the next Premiere Pro release/update (CS6.5 or CS7)
Fuzzy Barsik Apr 8, 2013 3:37 AM (in response to SteveHoeg)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)?
-
42. Re: Top 15 Issues/Fixes Needed in the next Premiere Pro release/update (CS6.5 or CS7)
ZachRosing Apr 8, 2013 8:21 AM (in response to SteveHoeg)SteveHoeg wrote:
We've only announced a preview of the next version, but it is a big release.
Steve,
What can you comment on AVCHD spanned clips? You have 8 pages of angry people in this thread: http://forums.adobe.com/thread/1004369 who feel like, once again, Adobe has abandoned them. We paid hundreds of dollars for software--in my case chosing to buy CS6 flat out instead of Creative Cloud, and have wasted this money because our software is unusable. I only edit long shows--I cannot use CS6, where as CS5 worked flawlessly. And now it's becoming pretty clear that Adobe has no plans to make this right for all these people.
Adobe still offers the option to buy versions of CS--it isn't required to buy Creative Cloud. So is it too much to ask that advertised features will actually work, and we won't find ourselves stuck with broken software?
-
43. Re: Top 15 Issues/Fixes Needed in the next Premiere Pro release/update (CS6.5 or CS7)
jstrawn Apr 8, 2013 3:05 PM (in response to ZachRosing)The best way to stay on top of the adobe-specifc announcements coming out of NAB this week is probably here:
http://tv.adobe.com/show/adobe-at-nab-2013/
So if you want to bookmark that and check it throughout the week, you will have all the latest public information about the new version od PrPro.
-
44. Re: Top 15 Issues/Fixes Needed in the next Premiere Pro release/update (CS6.5 or CS7)
DMH79 Apr 8, 2013 3:40 PM (in response to jstrawn)Thank you. I'll definitely do that. I haven't been around Adobe long enough to know how long after these "sneak peaks" users should expect to see the new version. I'm sure the kinks are being worked out but I'm curious if there's a ballpark release time? Just excited is all
Thanks again jstrawn for the tv.adobe.com link!
-
45. Re: Top 15 Issues/Fixes Needed in the next Premiere Pro release/update (CS6.5 or CS7)
jasonvp Apr 9, 2013 5:48 AM (in response to jstrawn)jstrawn wrote:
The best way to stay on top of the adobe-specifc announcements coming out of NAB this week is probably here:
No offense meant to you at all, but you didn't answer Zach's question. In fact, it seems as though Adobe is dodging it for some oddball reason.
You guys have to realize you're going to have a hard sell for this newer version if the rest of us CS6/AVCHD guys aren't thrown a bone of some sort...
-
46. Re: Top 15 Issues/Fixes Needed in the next Premiere Pro release/update (CS6.5 or CS7)
ZachRosing Apr 9, 2013 8:40 AM (in response to jasonvp)Jason Van Patten wrote:
You guys have to realize you're going to have a hard sell for this newer version if the rest of us CS6/AVCHD guys aren't thrown a bone of some sort...
Thank you Jason. If you look at that thread, Adobe has known about this bug since shortly after CS6 was released. That's almost a year ago. Those of us who purchased the software and work with long AVCHD clips have been largely unable to use the software since that time, but kept it on the hopes that it was a simple bug that would get taken care of--especially since we've had no problems since CS5. That is clearly not the case, and make many of us wonder why we should ever trust them with our money again.
Not only are they not giving us any feedback regarding this for CS6, but no one will comment on the situation for this next version.
-
47. Re: Top 15 Issues/Fixes Needed in the next Premiere Pro release/update (CS6.5 or CS7)
jstrawn Apr 9, 2013 9:47 AM (in response to jasonvp)No offense meant to you at all, but you didn't answer Zach's question. In fact, it seems as though Adobe is dodging it for some oddball reason.
You guys have to realize you're going to have a hard sell for this newer version if the rest of us CS6/AVCHD guys aren't thrown a bone of some sort...
The reason is not oddball or conspiratory in some way. Simply put, it is not appropriate for individual staff members to discuss features publicly before they are publicly announced. I also can't accurately speak about the prioritization of AVCHD spanning or other specifc bug fixes and/or feature requests, because it's not a decision I have personally been part of. But the good news is that this is NAB week, which is typically when most things get announced for Adobe's Digital Video/Audio product line. I only chimed in on this thread to provide that link, which is probaby the best way to stay up do date this week, unless of course you happen to be in Vegas right now.
One thing I can say is that these forums do get looked at by people who make those decisions and announcements and that your concerns have been and will continue to be heard whether everyone's top requests are imminently addressed or not.
-
48. Re: Top 15 Issues/Fixes Needed in the next Premiere Pro release/update (CS6.5 or CS7)
ZachRosing Apr 9, 2013 11:23 AM (in response to jstrawn)I respect that you Jason may not have knowledge to comment on this subject. When can we expect *someone* from Adobe to comment on it? I'm not interested in a paid upgrade to the newest version of CS to fix a known serious bug that kept me from using the current version.
This whole thing makes me wonder why I should ever trust Adobe with my money ever again. What's the next feature to break and not be addressed?
-
49. Re: Top 15 Issues/Fixes Needed in the next Premiere Pro release/update (CS6.5 or CS7)
Alan Craven Apr 9, 2013 11:44 AM (in response to ZachRosing)Zach seems to be the only person voicing dissatisfaction with Adobe for their policy of failing to correct faults in their software, and then expecting their customers to pay a high price for the next newest, greatest ever version - particularly now this has become an annual pick-pocketing exercise!
I can assure any Adobe employee who reads this thread that there will be a great many more dissatisfied customers out there, of which I am one.
My particular concern is the bug in the Warp Stabilizer which results in grotesque project file sizes. Again this was trumpeted a year ago as the new wonder of the age.
-
50. Re: Top 15 Issues/Fixes Needed in the next Premiere Pro release/update (CS6.5 or CS7)
joe bloe premiere Apr 9, 2013 1:21 PM (in response to Alan Craven)My observations:
Firewire output worked in CS4.
Firewire output was broken in CS5 / CS5.5.
Firewire output is fixed in CS6.
Firewire output will not be back-ported to CS5 / CS5.5.
CS5 can not output MPE to external DV device
http://forums.adobe.com/thread/640820
CS5.5 & External Monitoring - is there anything new?
http://forums.adobe.com/thread/836581
Firewire output of Hardware MPE - I give up
-
51. Re: Top 15 Issues/Fixes Needed in the next Premiere Pro release/update (CS6.5 or CS7)
JSS1138 Apr 9, 2013 1:27 PM (in response to Alan Craven)My particular concern is the bug in the Warp Stabilizer which results in grotesque project file sizes.
I'm not sure that's a bug. The analysis data is stored in the project file, and it's that data which causes the project file size to grow.
-
52. Re: Top 15 Issues/Fixes Needed in the next Premiere Pro release/update (CS6.5 or CS7)
JSS1138 Apr 9, 2013 1:30 PM (in response to joe bloe premiere)Firewire output was broken in CS5 / CS5.5.
It wasn't 'broken'. It just wasn't made compatible with the new hardware acceleration capabilities until CS6. That's a very different viewpoint.
-
53. Re: Top 15 Issues/Fixes Needed in the next Premiere Pro release/update (CS6.5 or CS7)
joe bloe premiere Apr 9, 2013 1:45 PM (in response to JSS1138)Okay... inoperable with MPE.
The point is nobody is planning to retroactively make
IEEE1394 output of MPE possible in CS5 or CS5.5.
-
54. Re: Top 15 Issues/Fixes Needed in the next Premiere Pro release/update (CS6.5 or CS7)
JSS1138 Apr 9, 2013 1:53 PM (in response to joe bloe premiere)That's probably true. Adobe doesn't often go back and add new features to older versions.
That's not the same as not correcting a fairly significant bug in the previous version, though. I think the AVCHD spanning issue qualifies as a fairly significant bug. The problem is probably one of economics. Assuming a fix is available in the new version, what would it cost to retrofit the 'fix' into CS6? As a publicly traded company, Adobe is required by law to put it's investors and their profit shares ahead of it's customers.
Capitalism at it's finest.
-
55. Re: Top 15 Issues/Fixes Needed in the next Premiere Pro release/update (CS6.5 or CS7)
Fuzzy Barsik Apr 9, 2013 2:05 PM (in response to joe bloe premiere)The point is nobody is planning to retroactively make IEEE1394 output of MPE possible in CS5 or CS5.5.
That's for the safety sake: if fireware gets fixed in CS5/CS5.5, spanned AVCHD clips get broken.

-
57. Re: Top 15 Issues/Fixes Needed in the next Premiere Pro release/update (CS6.5 or CS7)
Alan Craven Apr 9, 2013 10:58 PM (in response to JSS1138)Jim Simon wrote:
My particular concern is the bug in the Warp Stabilizer which results in grotesque project file sizes.
I'm not sure that's a bug. The analysis data is stored in the project file, and it's that data which causes the project file size to grow.
Bug or not, the Warp Stabilizer is un-usable in its present form, unless each clip to which it is applied is exported as an intermediarte and re-imported.
-
58. Re: Top 15 Issues/Fixes Needed in the next Premiere Pro release/update (CS6.5 or CS7)
Alan Craven Apr 9, 2013 11:02 PM (in response to JSS1138)If Adobe has developed fixes for some of the problems with CS6 during the lifetime of CS6, then it is surely unethical, and possibly a breach of consumer protection legislation, to fail to provide this to purchasers of CS6. This is especially so if they include these fixes in CS6+ and require their customers to pay for the fix.
We have yet to see if this is the case with this new release, but I should be surprised if some at least of the several problems are not fixed in the new release..
-
59. Re: Top 15 Issues/Fixes Needed in the next Premiere Pro release/update (CS6.5 or CS7)
JSS1138 Apr 10, 2013 8:40 AM (in response to Alan Craven)Warp Stabilizer is un-usable in its present form
Well, a new version of Warp Stabilizer that didn't require the analysis data would be a new feature, found in a new version. That's something I think Adobe can expect people to pay for, and very different from leaving genuine bugs (AVCHD) uncorrected.
-
60. Re: Top 15 Issues/Fixes Needed in the next Premiere Pro release/update (CS6.5 or CS7)
Alan Craven Apr 10, 2013 9:45 AM (in response to JSS1138)Jim Simon wrote:
Warp Stabilizer is un-usable in its present form
Well, a new version of Warp Stabilizer that didn't require the analysis data would be a new feature, found in a new version. That's something I think Adobe can expect people to pay for, and very different from leaving genuine bugs (AVCHD) uncorrected.
I do not want a new version of the Stabilizer - I want the one I paid for which was an advertised feature of CS6. The one I have needs work-arounds to use, that was not part of the CS6 deal.
I shall not comment further on this. It is a waste of time given your obvious commitment to Adobe.
-
61. Re: Top 15 Issues/Fixes Needed in the next Premiere Pro release/update (CS6.5 or CS7)
JSS1138 Apr 10, 2013 11:12 AM (in response to Alan Craven)I do not want a new version of the Stabilizer
You seem to want it to work without storing the data in the project file. That would be a new version.
-
62. Re: Top 15 Issues/Fixes Needed in the next Premiere Pro release/update (CS6.5 or CS7)
DMH79 Apr 10, 2013 11:31 AM (in response to Alan Craven)Alan Craven wrote:
Jim Simon wrote:
Warp Stabilizer is un-usable in its present form
Well, a new version of Warp Stabilizer that didn't require the analysis data would be a new feature, found in a new version. That's something I think Adobe can expect people to pay for, and very different from leaving genuine bugs (AVCHD) uncorrected.
I do not want a new version of the Stabilizer - I want the one I paid for which was an advertised feature of CS6. The one I have needs work-arounds to use, that was not part of the CS6 deal.
I shall not comment further on this. It is a waste of time given your obvious commitment to Adobe.
Actually, Alan I'd love to hear your thoughts on Warp Stabilizer. Its one of the top 1 or 2 features that's essential to my personal workflow. I use it several hundred times a week actually (no exaggeration) so I know it pretty well. I voiced my issues with it both in bug reports and feature requests as well as in my "Top 15" list at the start of this thread (#3 and #5 on the list). It has it's issues for sure. I've found it to be very effective however. Especially compared to FCP7's smoothcam where it would have to analyze the whole clip and not just the portion you are using. I'd love to see the end of the error messages and freezes that Warp Stabilizer causes as well as I have personally found the default "method" (in the settings) to be much less efficient than another option (which I stated in #5 on my list). I'm crossing my fingers and we'll just have to wait and see I guess.
Since it's something I use more than 100 times per project my project sizes are genrally in the 100-200mb range. Never bothered me much I guess because I just figured that's cuz the data is stored there. What was a pain is every time I open a project I get an error (see #3 on the list) and have to hit continue between 300-450 times (on average). I like how Adobe is "enhancing" the feature within After Effects, however I do hope the issues with Premiere Pro's version of Warp Stabilizer are resolved in the new release. If you had a hard copy of CS6 instead of Creative Cloud, and they charge for the update, I can see how that would be frustrating. Bug fixes related to the current version "should" be free IMO. Creative Cloud takes care of both bug fixes and feature upgrades which is really nice...although even Creative Cloud has room to improve in my opinion (see #14 on my list).
-
63. Re: Top 15 Issues/Fixes Needed in the next Premiere Pro release/update (CS6.5 or CS7)
Alan Craven Apr 10, 2013 12:11 PM (in response to DMH79)Warp is the most effective of the seven or so Windows/Premiere Stabilizers that I have used over the past decade or more. I currently have Mercalli 2, and before that Steadymove Pro, but Warp can achieve what none of the others has ever managed for me and that is to have a stable rocky shoreline in front of a moving sea. All the others had jello rocks!
Lke you, I can live with the bloated project files, up to a point. But if the file gets too big then saving becomes very slow - you can have a coffee while Premiere does an autosave, and then as you say in 5c, you come back and find Premiere frozen in the Autosave!
The ticktime.cpp-207 error I have only seen a couple of times - but I do not use multi-cam. 5b, the toggle error is an irritant, when you forget to avoid it as you say.
Your 5d was a revelation to me - I had not discovered that you could improve the already really good performance by so much until I tried it.
As I have said elsewhere, I tend to export a stabilized clip using Lagarith or Avid DNxHD when I am happy with it, and then import that as a replacement for the original. This shows up another problem - the time taken for Premiere to react to a cut command on the clip to which the Stabilizer has been applied can seem interminable.
Despite the problem, I find I am using it much more in preference to Mercalli 2, simply because the results are so good
Creative Cloud would be expensive for me as I do not live in the USA, and in Europe we pay premium prices compared with USA users. Adobe once told me that this was due to the inevitable costs of translation! Time was when you could run Premiere in UK English but recent versions are US English only. Also I have no interest in any other Adobe software than Premiere, Encore, Audition and Photoshop.
-
64. Re: Top 15 Issues/Fixes Needed in the next Premiere Pro release/update (CS6.5 or CS7)
KGCW Apr 11, 2013 12:54 PM (in response to Alan Craven)I think Warp stabilizer might deserve a thread of its own about how to yeld best results with it. It's incrediby powerfull if you dig into the parameters.
-
65. Re: Top 15 Issues/Fixes Needed in the next Premiere Pro release/update (CS6.5 or CS7)
KGCW Apr 11, 2013 12:51 PM (in response to Alan Craven)Regarding prices in Europe : annual cloud subscription here (in France) is 61,5 € / month, roughly 80,5 $. My cloud subscription is 61% more expensive because of language packs that I never ever used or will use, without any possibility given to me of getting the english only version of the softwares. I work with english versions because :
- 90% of the learning content for Adobe softwares is in english, with english UI.
- 99,9% of all the technical audio and video stuff I personally read / watch is in english.
- Creative softwares use loads of technical terms and a lot of them just don't translate well at all in french.
Even if cloud subscription is way cheaper and more versatile than paying the whole license up front, I still don't like being left with no choice but to pay for stuff I don't use because I'm on the wrong side of the Atlantic ocean.
-
66. Re: Top 15 Issues/Fixes Needed in the next Premiere Pro release/update (CS6.5 or CS7)
srukweza Apr 11, 2013 4:26 PM (in response to KGCW)So basically if we can sync with the waveform that means Plural eyes is no longer worth paying for!
-
67. Re: Top 15 Issues/Fixes Needed in the next Premiere Pro release/update (CS6.5 or CS7)
srukweza Apr 11, 2013 4:37 PM (in response to srukweza)Is Speedgrade intergrated into Adobe Premier with the dynamic link in the upcoming version?
-
68. Re: Top 15 Issues/Fixes Needed in the next Premiere Pro release/update (CS6.5 or CS7)
srukweza Apr 11, 2013 4:40 PM (in response to srukweza)Also not forgetting exporting 5.1 surround sound for DVD without the 3rd part plug in....
-
69. Re: Top 15 Issues/Fixes Needed in the next Premiere Pro release/update (CS6.5 or CS7)
Kevin-Monahan Apr 12, 2013 11:21 AM (in response to PierreLouisBeranek)PierreLouisBeranek wrote:
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!
Yes, I just tested it. It does remember the last state used.
-
70. Re: Top 15 Issues/Fixes Needed in the next Premiere Pro release/update (CS6.5 or CS7)
Kevin-Monahan Apr 12, 2013 11:34 AM (in response to srukweza)srukweza wrote:
So basically if we can sync with the waveform that means Plural eyes is no longer worth paying for!
According to a presentation I saw at NAB from Jason Levine, Plural Eyes can still provide a few workflows the new sync with audio feature cannot. I can't recall exactly what they are, but if I do see them described in one of our NAB video presentations, I can list them. For most purposes, the new sync with audio feature will be fine for most multicamera synching, clip synching and merge clips workflows.
-
71. Re: Top 15 Issues/Fixes Needed in the next Premiere Pro release/update (CS6.5 or CS7)
Kevin-Monahan Apr 12, 2013 11:48 AM (in response to srukweza)srukweza wrote:
Is Speedgrade intergrated into Adobe Premier with the dynamic link in the upcoming version?
Not exactly. We will have the Lumetri effect which can import .look or LUTs from SpeedGrade into Premiere Pro, though. Pretty cool. Keep requesting full Dynamic Link support between the applications here: http://www.adobe.com/go/wish
SpeedGrade booth at NAB was slammed the entire time, so I think a lot of people will enjoy the upcoming version.
-
72. Re: Top 15 Issues/Fixes Needed in the next Premiere Pro release/update (CS6.5 or CS7)
DMH79 Apr 12, 2013 12:14 PM (in response to Kevin-Monahan)Hey Kevin!
I've seen just about every blog and post and thread on the next release. Very exciting. Still eagerly waiting to hear about certain bug fixes (namely #3 and #5 on my list), but from the littlest adjustments/refinements to the bigger additions, the feature updates look amazing. So two quick questions for you:
1) Have they named it yet? I see it referred to as Premiere Pro "Next" but is that just a filler until it's later named CS 6.5 or CS7? Or will we follow the odd iPad naming and just call it "The New Premiere" (kidding).
2) And do you have a ballpark release date yet (April? May? Tomorrow? )
Just excited is all.
-
73. Re: Top 15 Issues/Fixes Needed in the next Premiere Pro release/update (CS6.5 or CS7)
Kevin-Monahan Apr 22, 2013 9:28 PM (in response to DMH79)DMH79 wrote:
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.
Hi DMH79,
Here is a screenshot of my Timeline. I have a Warp Stabilizer effect on all the clips, including multicam clips. I was not able to reproduce this behavior.
After reopening the project, I did not encounter the error you spoke of.
Is that what you were looking for?
DMH79 wrote:
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
a) I don't see this error in my tests.
DMH79 wrote:
b) Toggle OFF the effect after it’s applied and then hit Analyze again and PPro crashes. (easy to avoid but annoying bug)
b) If I toggle the effect on or off, Analyze is disabled. How do you Analyze again without resetting the effect?
DMH79 wrote:
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.
c) I would need to test that one. Time to crank up the Auto Save frequency.
Naming stuff and release date? I have no info on that right now.
-
74. Re: Top 15 Issues/Fixes Needed in the next Premiere Pro release/update (CS6.5 or CS7)
SMG720 Apr 26, 2013 10:41 PM (in response to Kevin-Monahan)Hi Kevin,
Just so we're clear, you guys don't have line of sight on the TickTime.cpp error? I'm seeing this also and am using the Warp Stabilizer effect. There was a thread a while back where someone was requesting project files and it looked like they had reliable steps to reproduce.
-
75. Re: Top 15 Issues/Fixes Needed in the next Premiere Pro release/update (CS6.5 or CS7)
DMH79 Apr 27, 2013 7:26 PM (in response to Kevin-Monahan)Kevin Monahan wrote:
Hi DMH79,
Here is a screenshot of my Timeline. I have a Warp Stabilizer effect on all the clips, including multicam clips. I was not able to reproduce this behavior.
After reopening the project, I did not encounter the error you spoke of.
Is that what you were looking for?
b) Toggle OFF the effect after it’s applied and then hit Analyze again and PPro crashes. (easy to avoid but annoying bug)
b) If I toggle the effect on or off, Analyze is disabled. How do you Analyze again without resetting the effect?
From your test it looks like that ticktime.cpp error is gone because normally what you have in your timeline would cause the error upon reopening. We'll know for sure soon but that's a great sign.
Regarding the disabling of analyze, the button is disabled once the analysis is completed. But try adjusting the clip a bit (eg. reduce its size by one frame) and the Analyze button will reappear...now toggle off and hit analyze...wait for it and in CS6 within moments you get a "serious error" and it crashes. Does this happen on the NEXT version of Premiere?
Finally, is the default "method" in the warp stabilizer's settings still "Subspace Warp"? Or did switch it to "Position, Scale, Rotation" after realizing that that method works MUCH better 90% of the time?
-
76. Re: Top 15 Issues/Fixes Needed in the next Premiere Pro release/update (CS6.5 or CS7)
PierreLouisBeranek Apr 30, 2013 7:35 AM (in response to Kevin-Monahan)Hi Kevin,
I have a couple questions about Premiere Pro Next:
- Will it allow editors to finally slip a clip without slipping the clip's keyframes as well? After Effects 'gets it', by allowing users to slip a clip without moving its keyframes out of place vis-à-vis the Timeline (or Comp). When we slip a clip, we don't want our keyframes to slip along with the clip! That's because the vast majority of the time, keyframes are set relative to the Timeline (i.e. music/sound beats, titles, other clips, etc) and NOT relative to the contents of the clip itself. Editors get this. Hopefully the Premiere team finally 'got it' and in Premiere Pro Next we can slip clips the way we can in After Effects... the intelligent way.
- Will it allow users to open 2 or more instances of the Effects window? The ability to open several Project windows by CTRL-clicking on a bin is a great feature, but unfortunately it wasn't added to the Effects window. Here's why it would be useful: If I have my 'Favorites' custom bin twirled down so I can easily access its collection of effects, but then I do a search for an effect, upon clicking the 'x' icon to remove the search entry, my 'Favorites' custom bin is now twirled closed out of view. This is extremely annoying, so I'm praying that the Premiere team has finally fixed this inconvenient workflow. There's many ways this could be fixed, but one simple solution that would require very little programming effort, would be to duplicate the Project window's ability to open a bin in a new window, thereby allowing 2 or more Effect windows: one small one used just for searching effects, another one used for displaying a custom bin of favorite effects (that doesn't get knocked out of view every time a search is made), and perhaps even a third one for audio effects.
I've sent Adobe FRs for these things several times. Hopefully they were able to get around to it in CS Next!
-
77. Re: Top 15 Issues/Fixes Needed in the next Premiere Pro release/update (CS6.5 or CS7)
Kevin-Monahan Apr 30, 2013 11:28 AM (in response to PierreLouisBeranek)PierreLouisBeranek wrote:
Hi Kevin,
I have a few more questions if you don't mind.
- 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?
It's rather like in FCP 7, when you Command drag a sequence from the Viewer to the Canvas. You can do the same in Avid Media Composer.
More on that here: http://lfhd.net/2010/05/26/fcp-tip-cutting-in-footage-from-another-sequence/
PierreLouisBeranek wrote:
- 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.)
I had that issue too until I discovered Preferences > Trim > Allow Selection tool to choose Roll and Ripple trims without modifier key. Now, I do not have to deselect one tool to select another. Try it now in Premiere Pro CS6 and see if that works for you. I think it's pretty cool.
PierreLouisBeranek wrote:
- 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).
Are you talking about effects presets? You can do that now in Premiere Pro, unless I'm missing what you're talking about.
PierreLouisBeranek wrote:
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.
I'm glad you like what you see.
I have nothing to do with future pricing or rules for upgrades. You should address your future concerns on the feature request form: http://www.adobe.com/go/wish
Thanks,
Kevin
-
78. Re: Top 15 Issues/Fixes Needed in the next Premiere Pro release/update (CS6.5 or CS7)
Kevin-Monahan Apr 30, 2013 11:54 AM (in response to PierreLouisBeranek)PierreLouisBeranek wrote:
Hi Kevin,
I have a couple questions about Premiere Pro Next:
- Will it allow editors to finally slip a clip without slipping the clip's keyframes as well?
No, sorry you cannot. I suggest you copy and paste attributes after slipping to work around that issue.
PierreLouisBeranek wrote:
- Will it allow users to open 2 or more instances of the Effects window?
Now, it will not. Sorry.
Sounds like you've already made your requests, so encourage others that have the same idea to file their requests.






