PP CC 2014 and P2 Audio Problem?!?

I have the same problem on 6! different workstations, Mac and windows PC. It happens occasionally, very frustrating. No solution yet. Posted on the creative cow and some other editors have the same problem. A post on the adobe pp blog was deleted. So, no answer or response from adobe yet. We are editing with the CC 2013 instead. I think adobe don't care, because not so many editors are working with P2 material and already using CC 2014. But we are a small in-house production for a big company and this is a serious bug with adobe software for us. We are starting now to edit some projects to FCP X. And FCP X start shining.......

Michael

Hi Micheal,

Sorry about this. I'll try to find out what's going on here.

Thanks,

Kevin

Hi Kevin @ Wide eye and Michael,

Sorry you have encountered this issue. We were able to reproduce this issue and are now in the process of determining the cause. Please understand that this is not always a quick and easy process.

We will do our best to provide a fix as soon as we're able.

Again very sorry for the inconvenience.

Could you let me know what camera generated these files?

Peter Garaway

Adobe

Premiere Pro

These audio issues are completely unacceptable. We use the Panasonic HVX 200s and capture to P2 for a 30 min weekly sports show that airs on national TV. I have a two day turnaround including the shoot to get this show out and these P2 issues have nearly cost me my deadline multiple times. I also get tend to get some random audio pops in my multicam cuts in export. PLEASE FIX THIS ISSUE! THIS IS RUINING MY LIFE AND MY HEALTH!!!

The only saving grace is that we never uninstalled CC, otherwise I couldn't possibly get this show out. PEOPLE ACTUALLY USE THIS SOFTWARE TO MAKE A LIVING. WHY IS THIS FIX TAKING SO LONG.

Hey Horned King,

Are these P2 sources very long in duration?

Thanks,

Kevin

Hi HK,

Your answer was blank. Please try again.

Thanks,
Kevin

Thanks for calling attention to this issue, Horned King. Your post prompted Peter and me to revisit the matter. We were able to isolate two related scenarios that led to a condition similar if not identical to what the OP reported.

Scenario A: Clip was touched by 7.x

1. Import a spanned P2 clip (AVC-I or DVCPRO) into CC7.x.
2. Insert a clip marker or revise any XMP metadata. (This results in an XMP file being written to the CLIP folder under CONTENT.)
3. Import the same P2 clip into CC2014.x.

Scenario B: Clip has an XMP file but no media cache files (specifically the .pek files)

1. Import a spanned P2 clip without an XMP file into CC2014.x
2. Insert a clip marker or revise any XMP metadata.
3. Save and close the project.
4. Clear the media cache files
5. Either reload the same project, or create a new one and import the same spanned P2 clip.

In both of these scenarios, we observed two issues:

A) the audio waveform is incomplete

B) no audio plays for the segment of the clip without a waveform.

In our testing, closing and reloading the project fixed the issue with the missing audio at the end of the clip. However, the waveform remained incomplete.

A workaround to get the full waveform is to delete the XMP file and the .pek files for the affected clips. Be aware that clearing the XMP will erase all markers and other metadata that is saved to the XMP file.

Just to emphasize, the issues we identified are limited to P2 clips that span two or more MXF files in CONTENT/VIDEO.

Please let us know if neither of the scenarios above apply in your case, if complete audio isn't restored by closing & reloading the project, or if deleting the XMP and .pek files does not yield a complete audio waveform.

Greetings, I wanted to say thanks for taking the time to respond to this

issue. Sorry I couldn't respond sooner, things have been hectic here.

Opening and closing the project worked to restore audio. I saw no changes

after deleting the xpm and .pek files unless zoomed in extremely close on

the timeline.

I appreciate the workaround but really do hope this issue will be addressed

and corrected in future updates. At this point I feel I'm using "buggy

software" and it makes me extremely hesitant to upgrade to future versions,

or even refer other editors to CC 2014.

Once again, thanks for your time and for addressing this issue and

providing a somewhat usable workaround.

On Thu, Sep 25, 2014 at 10:49 PM, Mark Mapes <forums_noreply@adobe.com>

Hi Mark,

I currently have this same condition on a project I am working on. I have loads of information that may be helpful. Here is the rundown:

The clip in question runs 6:38;03

The audio (all four channels) drops out at 5:00;11

in Premiere Pro the waveform disappears as well at 5:00;11

in Prelude, the waveform disappears at the same timecode, however the audio still plays.

The clip was originally imported using Prelude in its original P2 format as well as transcoded to Apple ProRes 4:2:2. The original footage still resides on the P2 card. The clips were also copied over a network to backup storage which is now at another location. I do not know if the condition followed.

I have imported the P2 clip from my hard drive, the original P2 clip from the card and the ProRes clip from my hard drive using the media browser for all three.

Both P2 clips drop out at the same time

The Pro Res clip has all the audio.

There has been no restarts or project opening closings since discovering the problem. I can maintain the current condition if you would like to use my situation for troubleshooting. Please let me know ASAP so I can plan accordingly.

Peter

Thanks, PJM460. I think we have a good handle on the bug and engineering is working on a fix, so we don't need any additional info at this time.

Unfortunately, the update that's been announced does not include a fix for this issue. When the bug was first reported both by a beta tester and here on the forum, we were able to repro initially but not a few days later, so we concluded that a couple of changes in related code had fixed this bug. In fact, the second test failed to repro because we did not yet have a full handle on the bug, and one of the conditions was not met. By the time we revisited the matter (at Horned King's prompting), it was too late to get the fix into this update. So the best we can do is recommend the workarounds I posted previously.

ok  good luck