Hi,
Our file ingest solution handles P2 media by assembling a clip with multiple source files for each track (or filler for missing p2 segments). The AAF file (created with AAF toolkit) that is built represents clips with tracks that are multiple segments. When attempting to check in the AAF for such a clip with Web Services 3.6 or 3.7 (latest patches) the video files are not checked in and the clip is denoted audio only. A re-checkin with Web Services 3.5 (from our application) or an AAF import with Interplay Access (version 3.6) resolves the issue. Importing the clips into several editor version also shows no issue so we are confident it is a change introduced in WS 3.6... There appears to be some change that is not handling these clips the same.
I want to attach an AAF representing an AVCI clip with 2 chunks but the forum does not allow AAF files to be attached. Please let me know how I can provide a file for evaluation. This is very repeatable and has just been found.
Any advice is appreciated. The AAF structure we create for these clips has been the same for years. If there is something wrong, please advise... The AAF is ok up to IPWS 3.5 and with other means of importing AAF files.
Thanks!
Rich
Hi Rich,
Thanks for the detailed description and samples. I've downloaded the files and removed the links from your post.
In my lab I see no issues with the AAFs provided. First I've checked-in both AAFs using Interplay Access 3.7.3 and verified in MC 8.8.2 that both segments are visible in both cases.
Then I deleted the assets and retried with IPWS 3.7.1 which shows no issues as well.
Could you please see if Interplay Access works in your case? Have you tried to restart the IPWS service before check-in?
Thanks,
Vadym
Hi Vadym,
I did verify that importing the AAF in with Interplay Access works (Several versions). Our ingest application uses IPWS and when checking in with IPWS 3.5, the clips show in Access as audio and video with all files. When we check the same AAF in with IPWS 3.6 or 3.7, the clips do not show up in Access correctly. They show as audio only (In Access) and the file locations tab in Access does not show the files.
In all cases, the clips are OK on the editor when played on the MC Interplay Window. The clips show all tracks and the whole clip plays. When the check in occurs with IPWS 3.6 and 3.7, subsequent IPWS calles to get remote files for the assets DO NOT return the video files.
To summarize:
Import AAF with Interplay Access - clip is ok everywhere
Import AAF to editor BIN - clip is ok everywhere
Check In AAF with IPWS 3.5 - clip is ok everywhere
Check in AAF with IPWS 3.6/3.7 - Interplay Access does not show all video or shows audio only clip, GetRemoteFiles does not return video files - Editor Plays clips ok... File Locations tab on Access does not show all video files
Perhaps tomorrow we can share one of our desktops and I can show you? It is very strange and repeatable. Or I can provide you with our ingest software which made the AAF files and uses IPWS to check in? I'll put together some screen shots tomorrow to show you what we are seeing.
Ah, its Access only, now I see what you're saying. Let me run this through Jira
Despite tracks column shows V1 is in there its not on the list of tracks.
Ok. Thanks for confirming. Sorry for not being detailed enough!
I was just curious if engineering has had time to look at the check in issue with these AAF files? We have advised our P2 customers using AutoIngest to not update to IPWS 3.6 or higher for now. (Note that we found a similar issue with DV100 media checking in as audio only using IPWS 3.6 or 3.7 too)
The fix is scheduled for the 3.8 release at the moment.
Thanks
Thank for the status update Vadym. I think that our customers will be ok with IPWS 3.5 until the 3.8 release is available.
Have a good weekend.
-Rich
Hi again Vadym,
We recently installed IPWS 3.8.0 and the issue with check in of spanned clips does NOT seem to be resolved. This seems to be a problem with AAF checkin of master clips that have segmented media tracks.
Is this scheduled for a later release?
We have tested the spanned AAFs we have from the last time and see no issues with IPWS 3.8
Could you please provide a fresh set of clips that you still experience issues with in 3.8?
We had been testing IPWS 3.8 with IPE 3.7 and just updated to IPE 3.8. We will restest (unless you don' think the IPE version makes a difference). The issue arises after you right click on the asset in Access and "Update From Media Indexer". IF we still see the problem with IPE 3.8 I will post new AAF files with media.
Thank you
3.7 PAM engine should not have influence. On the other side what is the MI version in you environment. This may have some impact after update from MI is triggered.
My report that there was still an issue with IPWS 3.8 was a miscommunication with the person doing the testing. The recently reported problem with spanned clips showing up as audio only OR missing some video files when view on the Interplay Access FILES tab HAS been resolved.
The confusion was because he thought that a problem that began showing up with earlier IPE 3.x builds that did not exist in IPE 2.x was fixed too. This problem is that ALL spanned media that we check in shows up as "partial offline" (BLUE media status icon) AFTER you do "Update Status from Media Indexer" with Interplay Access. The QM_TRACK_INFO shows that all tracks are the same length and when the spanned clip is brought into Media Composer there is no offline media.
The same clip on an IPE 2.78 system here retains the "green" online status (Regardless of IPWS version). There doesn't seem to be any harm to the customers other than the "blue" partial status on Access.
IPE v278 - WS < 3.60 and > 3.7 - ok - spanned clips stay green (
IPE v350 - WS < 3.60 and > 3.7 - spanned clips turn blue with update from media indexer
If this is something that can be looked at, we (and I'm sure our P2 clients) would appreciate it. I can post media and an AAF for an example.
Please let me know...
Thanks for the update.
Please go ahead and open a separate topic on the partially online status (blue) in a matching forums section. We would need both AAF and media for that to investigate.
As this is more likely a product issue rather than API I'd also recommend customers to go through the Avid's customer success department as this issue could have been reported previously.
© Copyright 2011 Avid Technology, Inc. Terms of Use | Privacy Policy | Site Map | Find a Reseller