[Dennis Radeke]

[Andrew Kimery] “Personally I’d love it if all apps (even from different vendors) could integrate the way Adobe’s apps do (or the way some of the Final Cut Suite apps did). Having to use third party apps like Automatic Duck or interchange formats like XML is kludgey because it’s rarely a 100%, seamless exchange of information.”

Not that I think this is what you’re looking for but Adobe has ‘content panel’ technology that allows third party vendors to integrate with Adobe video products.

As for Automatic Duck, XML, AAF, etc. they are good for what they do because they seek to resolve how different companies handle media, timelines and the like. Granted they’re not perfect, but they are generally acceptable. To truly get the kind of deep or ‘perfect’ integration you seek, my personal opinion is that there would only be one company in the market in order for that to happen. That frankly wouldn’t be good for anybody.

My 2 cents,
Dennis

[Dennis Radeke]

[Alok Agrawal] “I have played around with Adobe Premiere but I didn’t really like it. I mostly had trouble with the fact that it wouldn’t snap to edit points in the timeline.”

Premiere Pro supports snapping to edit points, perhaps you just needed to turn it on.

PS – dang the retina display when screen grabbing – it’s all gi-normous.

[Dennis Radeke]

must…resist…temptation…

😉

[Dennis Radeke]

[Scott Witthaus] “What about stability and varying systems?”

Well, we obviously put a strong emphasis on stability with every single feature and release we do with any product. Also, with our agile development model, it encourages stability through its method.

[Scott Witthaus] “Also, how does a subscription set-up push Adobe to keep pace with development and releases? Seems to me that there would be no rush as the annual fees have already been paid.”

Exactly the opposite! If we are providing valuable features that are important to users (like each of you) on a regular basis (average 2-3x per year) then you hopefully are happy with the subscription model that we provide. It’s the classic buyer/seller contract – if we are giving you a good service, then you are a satisfied customer. With the subscription model, we have an ongoing requirement to maintain your satisfaction. If we don’t, you have no reason to maintain your subscription.

Dennis – Adobe guy

[Dennis Radeke]

Good points as always Herb. Ultimately, we try as best we can and as you said, it is good for many people. Can we do better? Always! Within the support pages there is feedback and contacting support – both of which could be vehicles to improve a specific topic. I’ll ask to see if there are other ways to have users provide specific details on improving the support/help pages.

Thanks

[Dennis Radeke]

All of the documentation went online several versions ago. There was a decreasing need for manuals and customer feedback supported the idea that more people were looking online and other means for finding answers to your questions. Granted, a small portion of customers still really like this method. For them, I encourage printing a hard copy of the PDF materials.

Our answer these days is primarily this:

Essentially, all menu items and the manual and extra content and curated third party content are to be found here.

Here’s the link: Premiere Pro Help

Here is the reference PDF: https://helpx.adobe.com/pdf/premiere_pro_reference.pdf

At almost 600 pages, I hope it is enough for most people. 😉

Dennis

[Dennis Radeke]

[Paul Neumann] “Adobe seems to be going all in.”

Adobe has been an agile shop, utilizing scrum since CS5 but you couldn’t see the results until we switched to the Creative Cloud model

I think it’s been a fantastic model for development of features and workflows. It’s definitely benefited our customers.

[Dennis Radeke]

a clip span is where a single clip spans two separate media targets. IOW if you recorded RED and drive #1 fills up to 100%, drive #2 starts without ever notifying you.

I would remove the clips entirely from the project, save it, reimport, re-edit and see if it fixes it. Also if you used Warp Stabilizer on it, that might cause the conflict as well. In that case, you would have to render the clip and then apply the speed changes/ramp.

[Dennis Radeke]

Assuming you’re using CC?

Are you on the latest release?
Are you syncing via audio or timecode?
Can you sync in any way?
If trying to sync audio and failing, perhaps try normalizing the separate audio feed and try again? Maybe the level is too low.

[Dennis Radeke]

To my knowledge the answer is no.

What’s more is that all of the tracking/stabilization data is saved in the project, making it very large. If you have that many clips, I’d recommend doing it in After Effects and rendering them out via AME.