Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro Does Bridge Really Help PPro?

  • Does Bridge Really Help PPro?

    Posted by Richard Milner on January 22, 2006 at 8:55 pm

    If you look at the top ten improvements in PPro, they mentioned Bridge.

    OK what does bridge do within the PPro App?

    In a previous post I expanded on this.

    Could someone please comment on XMP- Bridge?

    Adobe has invested lots of time and money into bridge which is built on XMP. I have far from a complete understanding of XMP, but XMP data is formated in XML. This data becomes part of the header information.

    Are there tangible benefits for PPro 2.0 users derived from XMP data?

    Right now, what can I do now with the Bridge-XMP that I couldn’t do before?

    Richard Milner replied 20 years, 3 months ago 3 Members · 7 Replies
  • 7 Replies
  • Mark Palmos

    January 23, 2006 at 2:42 pm

    Hello Richard,

    I like PP2 a lot, but bridge is absolute crap.
    It is very slow and adds nothing but time to the process.
    There is no use for it in PP at this time.

    Mark.

  • Richard Milner

    January 23, 2006 at 5:46 pm

    Mark,

    Good to hear from you. Hope 2006 is starting off well for you.

    I am awaiting my first copy of PP2.0. How does Bridge slow stuff down? Can you envision it doing something in the future? If so, what?

    Richard

  • Mark Palmos

    January 23, 2006 at 11:17 pm

    hello richard,

    well, bridge is about as connected to your PP project as windows explorer.
    there is no practical use for it, the first and last time I looked at it, it was so slow I never went back, it took ages, and then I could not see the time code of my clips.
    using bridge with adobe after effects was also a big waste of time.
    I expected to be able to browse the text effects presets and see animated picons to show what each effect would do, but instead I got some generic picon for all the presets.
    there were some other complete misses, and not a single “ah, that’s nice…” so for now I see it as an alpha code experiment of something that may become useful sometime in the future.

    besides all that, what a good nle should have is great INTERNAL media management, no need to open a separate app, unless it was a way to drag and drop timelines, bins and other assets from one job to another ala Discreet Jobnet.

    till later,

    mark.

  • Steven L. gotz

    January 24, 2006 at 4:02 am

    Well, I thought I should mention that Bridge is quite useful if you are inclined to change the meta data of clips you are importing into a project before you import them. That way, more of the columns in the project window become useful.

    Steven
    http://www.stevengotz.com

  • Mark Palmos

    January 24, 2006 at 8:14 am

    [Steven L. Gotz]
    Well, I thought I should mention that Bridge is quite useful if you are inclined to change the meta data of clips you are importing into a project before you import them. That way, more of the columns in the project window become useful.”

    Hi there Steven,
    Yeah, but then again this is the kind of thing one should be able to do in PP, not have some clunky outside app to do it.

    Speaking of metadata, do you know if Bridge can add the kind of Metadata which Media Encoder in PP misses?

    Mark.

  • Steven L. gotz

    January 24, 2006 at 10:27 pm

    What gets missed in Adobe Media Encoder?

    I think this is apples and oranges. One is import, the other deals with transcoding. Oh, and this stuff can be added in Premiere Pro 2 also.

    Steven
    http://www.stevengotz.com

  • Richard Milner

    January 25, 2006 at 10:22 am

    Mark,

    [mark palmos] “besides all that, what a good nle should have is great INTERNAL media management, no need to open a separate app, unless it was a way to drag and drop timelines, bins and other assets from one job to another ala Discreet Jobnet.”

    I agree totally about the interal MM. Good idea about dropping assets into another Project (Job in discreet lingo 🙂 ). This could be what the future of bridge holds.

    But as someone here as said, you can’t see timelines –only projects. This might be a feature that requires the XML version of AAF. I’m not sure if that it is in SMPTE committee for approval or not. AAF has had their editing protocol for a while now.

    So,IMHO, XML versions of AAF and MXF are the technologies that will enable more functionality to Bridge. Does this make sense?

    [mark palmos] “so for now I see it as an alpha code experiment of something that may become useful sometime in the future.”

    I agree with you about becoming more useful in the future. Right now I assume that in the current release has each clip digitized into premiere has the XMP header information. Most of the illustrations of it’s use are about metadata that doesn’t have much to do with day-to-day editing.

    In a multi-user networked situation, a useful feature when there are hundreds or thousands of clips in a project would be if you open an existing project for the first time on a workstation and instead of manually relinking, the bridge would automatically search out the clips that are needed. You are ready to edit now rather than spend hours searching out the clips.

    Does anyone else have some ideas about additional functionality for Bridge?

    Richard

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy