[Richard Milner]

Paul,,

I’d like to lobby them prior to NAB and on the floor. The question is who do you call? Does anyone know who will actually listen?

[Richard Milner]

Alex,

I’m not familar enough with Bridge’s capabliities to know if this would work or not.

thanks,

Richard

[Richard Milner]

Bill,

Thanks for the info. Come Monday, I will explore.

[Richard Milner]

Is anyone else having a problem with timecode autodetect?

[Richard Milner]

Alex,

Much of my information I gleaned about bridge came from a demo DVD that comes with 2.0.

[Alex Udell] “since the data seems to be porject based and there’s nothing overseeing all the linkages…there’s no way to really determine external dependencies….”

I think that bridge is the overseeing software that sees all the elements. Remember with this verison of PP, XMP data is embedded into the captured media files(Adobe’s version of a portable metadata container ala XMF).

“So adobe needs another layer of application to track all this…or do like I plan to…make additional copies of “library” material to a differnt location. being able to identify material based on meta data search is important to this process….so that’s where I see Bridge being useful.”

In the 1.5 version of PP if you open up the the project file with a word processor, you’ll see that PP project tracks iterations of clips. It will be interesting to find out:
1. Does Bridge track all iterations(children) of a media file?
2. Does the header XMP data of the iteration contain ID information about the parent clip?

Does anyone know?

[Richard Milner]

Alex,

Let’s get someone else to verify this, but I believe that you can delete files with bridge as well as preview the clip. I don’t know about moving, but I assume it can.

I have some hope that bridge functionality will be beneficial to a San environment. I’m looking at SAN usage too. I haven’t worked with bridge, but this is my understanding. (or should I say the way I wish it works)

When a piece of media is digitized into premiere, it becomes part of Bridge too. Bridge is a standalone piece of software. If you want to use clips that are shown in bridge, you just open bridge in premiere and pull down clips into your project.

Bridge itself has metadata search tools that you can use key words as well as other fields that you can do boolean searches on.

When the metadata is downloaded into your project, the essence doesn’t move from it’s place on the SAN, so it’s there for anyone else to use by loading the metadata information into their app that points to the essence’s location.

Let’s get others to give their 2cents

[Richard Milner]

Dave,

Thanks,

I will check it out.

[Richard Milner]

Do you know what kind of network it is? Is it a SAN?

[Richard Milner]

[Ralph Keyser] “Sony already has an MXF-XML dictionary out. Avid and Final Cut already support MXF, yet I haven’t seen any hint of MXF support in Adobe’s latest release. If Adobe wants to play as a “serious” NLE, I don’t see how they not support this format.”

Ralph,

When the final MXF-XML dictionary comes out from SMPTE, Sony will have to revise it if they are going to stay compatible. Work done now without it, risks being non- compliant. This may not be a big deal for Sony, but obviously it is for Adobe.

I think it’s a bigger thing for Adobe because they have to make it jive with XMP- their version of a MXF wrapper. So it’s not only an XML issue at that point.

I believe that not too much after SMPTE’s sign-off on MXF-XML, Adobe will do the MXF thing.

If they have no intention of supporting MXF soon,

A. you are right. They aren’t serious about Pro level stuff.
or
B. They plan to try and push XMP to the forefront- hoping that their market share will force XMP to be a co-existing defacto standard to MXF. Then it will be up to 3rd party software suppliers to “bridge” the gap.

Of course, this is all speculation. Does this seem plausible to you?

[Richard Milner]

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