-
SVP 12 and Panasonic P2
Posted by Bruce Miller on October 8, 2012 at 7:43 pmI am hardly the expert here, but I downloaded Vegas Pro 12 today with an eye on a big project shot on P2. SVP 12 felt much more nimble but I never really got to the point of editing. Loading P2 files into the system was inexplicably buggy. Drag and drop was inconsistent getting the audio files sync’d in. Import Media seemed better. A few files wouldn’t import at all. Had to restart the program many times. Turned off graphic acceleration for good measure.
I can’t give a conclusive explanation because everything almost works. Maybe the Sony/Panasonic war isn’t quite over — or maybe it’s my system.
I had no problems with Raylight Ultra and SVP 11 which for sanity’s sake is where this project will likely end up.
If there is a resident Vegas/P2 expert, would love to learn more.
Bruce
David Bilodeau replied 13 years, 1 month ago 5 Members · 19 Replies -
19 Replies
-
Steve Rhoden
October 8, 2012 at 8:25 pmor maybe it’s my system.
Ingest P2 formats, AVC-Intra into Vegas 12 with absolutely
no issues, multiple and large file sizes.Steve Rhoden
(Cow Leader)
Film Editor & Compositor.
Filmex Creative Media.
1-876-832-4956 -
Mark Krueger
October 16, 2012 at 1:22 amI am a user of P2 cards. I used the plug in from DV Films to import my files prior to SVP 12. In SVP 12 they are importing seemlessly with no problems without any plug ins. The only problem I am having is being able to sort the clips in my media bin. For some reason they do not import in perfect sequence in SVP from the video files. I do not see any sort options in the media bins. Are there any? Mark
-
Alex Kidd
October 17, 2012 at 5:33 pmI am having some P2 problems as well. If I try and drag and drop P2 files (as I’ve always done in the past with Raylight) it will recognize the video and two streams of audio, but the audio will be blank. There is audio there, and if I use the Device Manager import it generally works, but the problem with Device Manager is that during the import it creates a huge convoluted folder structure for every single clip, rather than keeping them all in the same VIDEO folder that they are in while on the P2 card. I’m hoping this is just a bug and they either get the drag and drop fixed or let us import without having to essentially duplicate my MXF file into a convoluted folder hierarchy. Oh, and recognizing 24PA pulldown would be nice, too…
-
Alex Kidd
October 17, 2012 at 9:01 pmAfter editing my first project here on the new Vegas 12 P2 workflow, I’ve also noticed some bugs with audio dropping out randomly or coming completely out of sync, even on footage that I imported using the suggested Device Manger workflow. I’d have to close and re-open the program multiple times, with each time exhibiting a completely different and random result until the audio would work. If I ever went out of the program and back into it, the audio would usually mess up also. I’m on a new i7 laptop and neither the RAM or the processor were demonstrating anything close to peak levels, so it has to be some bugs with the new program. After experiencing bugs on the last few Vegas upgrades, I think I’m through being an early adopter for Sony, even with the discount incentive.
-
Bruce Miller
October 18, 2012 at 3:17 amThis is very similar to what I have been experiencing with the audio. I would have to re-open, re-start dozens of times before it would render P2 without losing sync or crashing. Building proxies had no beneficial effect.
I was convinced my high-power system wasn’t up to snuff.
-
David Bilodeau
December 21, 2012 at 4:42 amI imported P2 files which were copied for me from the P2 card to a USB drive, folder structure intact.
The files import fine – video and audio – but playback and especially rendering full HD is a train wreck.
Interlacing is so bad that pans and tilts are very jumpy and blurry.
My el-cheapo JVC and Sony prosumer cams are flawless.
Anyone have any suggested settings changes to fix this? I’ve tampered with Upper and Lower Field order (makes an individual frame, which otherwise is badly interlaced, look ok but the final product is still terrible).
I tried to post this question a moment ago and the forum seemed to kick it out. Sorry if this is duplicate.
-
Mark Krueger
January 21, 2013 at 7:57 pmDavid, Have you figured this out yet, or gotten any help form Sony. I have gone back to SVP 11 and Raylight!
-
Bruce Miller
January 21, 2013 at 9:31 pmSony released a new build a month or so ago that specifically addresses the audio/crashing issues with P2. All my problems went away.
-
David Bilodeau
January 21, 2013 at 11:05 pmBruce, I have SVP 12 Build 394 for 64-bit. That’s the last version the system says is available for 64-bit, and the P2 issue remains.
I have not yet heard back further from Sony support on this question…they seem to be running several months behind on answering tickets on the SVP 12 release.
-
David Bilodeau
January 21, 2013 at 11:07 pmMark, I see your post and what you have done, namely to go back a version with the 3rd party product. That’s not an option for me.
Support has not responded to me on this issue. They finally started responding on the GPU processor issue after a nearly 2-month silence so I am going to work that one first and then see what happens with this.
Hopefully they’ll eventually get all the bugs worked out and release a new version.
Meanwhile we’ll keep each other informed as warrants develop. I remain committed to the product but this release has been a royal disappointment.
Reply to this Discussion! Login or Sign Up