Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Panasonic Cameras P2 Log Software for Mac

  • P2 Log Software for Mac

    Posted by Pada01 on September 3, 2006 at 4:53 am

    Since the P2 Viewer is Windows only, we have tried P2 Log from Imagine Software as viewer and QT import-conversion software. It is simple to use and makes clip re-naming and storage easy. However, we have had a problem with the last frame or so of audio being garbled.

    Has anyone else had this problem?

    Pada01 replied 19 years, 9 months ago 4 Members · 7 Replies
  • 7 Replies
  • Noah Kadner

    September 3, 2006 at 6:59 pm

    I’d contact the folks at Imagine directly. They are very responsive to issues. OF course this is labor day so don’t expect a response before Tuesday morning.

    https://www.imagineproducts.com/support_links_page.htm

    Noah

  • Pada01

    September 4, 2006 at 2:55 pm

    Noah,

    I did contact Imagine and they did reply on Labor Day!

    Imagine is waiting for a fix from Apple. However, until then it definitely has an audio problem.

  • Richard Sutcliffe

    September 4, 2006 at 8:58 pm

    Thanks for posting this, we have found similar issues with some of our clips. Its worth noting particularly in interview situations where grabs span two cards. Have you determined whether it is the end of clips ie button off or end of cards where the garbling occurs?

  • Pada01

    September 5, 2006 at 6:36 am

    First, there is NO audio problem with clips that were recorded on cards or the Firestore FS-100 AND imported using FCP. The audio is perfect when FCP’s import P2 function is used, even when a clip bridges two P2 cards or two files on the Firestore.

    We only had the audio problem when importing the clips using P2 Log from the Firestore. (We did not try our cards.) We tested this using the same 10 clips and importing them using both FCP and P2 Log on two Mac’s.

    The audio problem at the end of the clip only showed up on clips imported using P2 Log. We have seen it primarily in long clips that have been broken into two clips by the 2.2 gig file size limit on the FireStore FS-100. There was music playing in the background and the audio problem was audible when listening to them in QT. The problem was also still there after we brought the QTs that had been imported with P2 Log into FCP to put them up in a sequence to put them together. As recollect, the problem existed both in “bridged clips” and in clips where the Rec/pause button had been pushed. When the same clips were imported using FCP, no problem.

    Imagine is working on the problem, but according to them, they are dependent on Apple to fix something.

  • Jan Crittenden livingston

    September 5, 2006 at 6:51 pm

    So which version of the Mac OS and Quicktime are you running? I have not heard of this problem, seems odd to be coming up now?

    Best,

    Jan

    Jan Crittenden Livingston
    Product Manager, DVCPRO, DVCPRO50, AG-DVX100
    Panasonic Broadcast & TV Systems

  • Pada01

    September 6, 2006 at 4:56 am

    Hi Jan,

    Tests were done on two Macs, both running versions 10.4.6, and one Mac running 10.3.9. All machines had the QT 7 and the DVC Pro HD codec.

    The identical 10 clips were shot on a Firestore and imported with both FCP’s “Import Panasonic P2” function and P2 Log on all three Mac’s. About 50% of the clips imported via the P2 Log had an glitch in the audio in the final few frames. Could be user error, but we replicated the problem on three machines doing three different imports. We have imported hundreds of clips from the Firestore on the same machines using FCP with no problems with the audio at the end of the clip.

  • Pada01

    October 20, 2006 at 9:38 pm

    Further testing revealed that it is likely that it is the FireStore we are using that is causing the problem. The problems started to appear in other applications too.

    Thanks to the folks at Imagine Software have dug in and look at the problem and provided updates, but it appears that the problem was NOT with P2 Log.

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