-
Mark Krueger
January 22, 2013 at 12:40 amDavid, Do you have this issue with P2….
When you place clips on the time line and you have the Vegas properties set to display the beginning and ending Time Code (This really helps to ensure you have the right sequence of events, given the strange sequencing of P2 clips in the bin.) The clips on the time line show simply the same beginning and ending Time Code.
I placed the same clips in SVP 11 and the correct time codes were displayed. So this is another issue with P2 and SVP 12.
Mark -
David Bilodeau
February 1, 2013 at 2:29 amVegas Support responded to my ticket today, relating to the P2 issue. Release notes are included in the download link area.
Hi David,
Thank you for contacting Sony Creative Software.
An update of Vegas Pro 12 was released today which resolves issues related to this incident. You may download the update here. https://www.sonycreativesoftware.com/download/updates/vegaspro
If you still have a follow-up question on this particular incident, please feel free to update it. If you have a completely different question, please create a new incident.
Sincerely,
Eric D.
Customer Service & Technical Support
Sony Creative Software Inc
https://www.sonycreativesoftware.com -
David Bilodeau
February 1, 2013 at 2:35 amFrom the release notes (P2 users, instructions to re-import P2 files after upgrading, so take a look):
2.0 What’s New
Notable fixes/changes in version 12.0 (Build 486)
Added support for exporting nested Vegas Pro projects as compound clips when exporting to Final Cut Pro X format.
Added support for importing compound clips as nested Vegas Pro projects when importing from Final Cut Pro X format.When importing a Final Cut Pro X project, a Vegas project is created for the main project using the same base name as the .fcpxml file, and separate nested Vegas projects are created for each compound clip and for each clip that contains an audio and a video stream.
Added Anchor point setting to the Titles & Text plug-in. Text now scales relative to the anchor point, which does not move.
Added support for reading and rendering up to 16 channels of audio in HD MXF files.
Added support for reading Sony XAVC files. You can use the Device Explorer window to browse and import clips from XAVC disc images.
Added support for timecode in P2 MXF files. If you’re using a project that was created in version 12.0 (build 394) or earlier, please update P2 clip timecode as follows:
If you imported the clip from a disc image, right-click the clip in the Project Media window, choose Replace, and then select the clip from the disc image.
If you imported the clip using the Vegas Device Explorer, delete the .mxf file from the C:UsersDocumentsImported Media folder and reimport the clip using the Device Explorer.
The Documents library and custom libraries from Windows Explorer are now available in the Vegas Pro Explorer.
File Open dialogs have been updated to allow you to browse and open files from mobile devices.
Fixed a bug that prevented the Sony Stabilize plug-in from working when 32-bit floating point (video levels) or 32-bit floating point (full range) was selected in the Pixel format drop-down list in the Project Properties dialog.
Improved performance when using audio preview through SDI video preview devices.
Fixed a bug that prevented the Sony Stabilize plug-in from being applied during playback.
Fixed a bug that could cause Vegas Pro to crash when loading some projects.
Fixed a bug that could reset event effect automation envelopes when splitting events.
Fixed a bug that prevented some fonts from previewing correctly when using the Titles & Text plug-in.
Fixed a bug that could start a different version of Vegas Pro when right-clicking a nested project and choosing Edit in Vegas from the shortcut menu when multiple versions of Vegas Pro are installed.
Fixed a bug that could cause the incorrect images to be displayed for selected Mute and Solo buttons in the Assignable FX dialog.
Fixed a bug that prevented the Plug-In Chooser from closing when Esc is pressed.
Fixed a bug that could cause all HDCAM SR templates to be marked as favorites in the Render As dialog when selecting a single template as a favorite.
Fixed an issue that could cause the “None of the files dropped on Vegas Pro could be opened” error message to be displayed incorrectly in the Vegas Explorer.
Fixed a bug that could cause a crash when using the FBmn Software White Balance plug-in.
Fixed a bug that could cause Stereoscopic 3D Camera settings to be displayed in the Track Motion window when working with 2D projects.
Fixed a bug that prevented the Use audio-capable preview device during external video preview setting from being saved when exiting Vegas (Preferences > Audio Device).
Fixed a bug that could cause Vegas Pro to hang when rendering MVC video for a Blu-ray Disc.
Fixed a bug that could cause Vegas Pro to hang when dragging a .mov file from the Vegas Explorer to the timeline if QuickTime was not installed.
Fixed a bug that could — in some circumstances — prevent the application from starting after registering.
Fixed a bug that could cause image sequences to have black frames in Video Preview and rendered output after zooming in with the Event Pan/Crop plug-in and time compressing.
Fixed a bug that could cause P2 MXF video to be opened without its associated audio streams.
Fixed a bug that could prevent the application from being uninstalled properly.
Fixed a bug that could prevent the application from entering expanded edit mode when pressing 5 on the numeric keypad.
Fixed a bug that could cause the first frame of an MVC file to appear briefly at the end when previewing the file from the Explorer window.
Fixed a bug that could cause XDCAM clips to have an incorrect timecode.
Fixed a bug that could cause the Video Preview window to flash when starting playback.
Fixed a bug that could cause doubled audio to be recorded after changing a track’s input monitoring mode.
Fixed a bug that prevented regions being dragged from the Explorer window to the timeline.
Fixed a bug that could cause the application to freeze when changing the capture device in the Capture Preferences dialog.
Fixed a bug where the timeline did not show only the current edit track (at the default track height) when entering expanded edit mode for some screen resolutions and for user-modified track heights.
Fixed a bug that could cause the current edit track height to decrease after exiting and then re-entering expanded edit mode.
Fixed a bug that could cause application extension windows to be hidden after loading an extension. -
Mark Krueger
February 1, 2013 at 12:10 pmDavid, I am going to download the upgrade today. Do you know if it addresses the jerkiness of P2 video in motion scenes that we talked about before in this forum? Mark
-
David Bilodeau
February 1, 2013 at 1:41 pmI ran a quick test last night. I noticed that with gpu acceleration DISABLED P2 playback locked in at 29.97 fps in the timeline on best/full…first time for that and it seemed pretty good… Did not seem so badly interlaced or jerky. Then I rendered a short segment to another format and it does not seem as bad. I dont think it is perfect but that might just be its nature when panning on the PC. Need to render BluRay and play on TV to say for sure. With GPU accel enabled, playback frame rate slowed and jumped around and I did not test long enough to see if it recovered and locked in or caused a hang of the program. Further tests this weekend. Let me know what you observe and based on our results I will update the ticket, which I updated asking Sony to leave open a couple weeks for further testing. They close in 2 days after responding if we do not update again…good way to keep their ticket stats looking good even if the issue is not solved when the customer fails to respond immediately, even though they can take 2 months to respond themselves!
-
Mark Krueger
February 2, 2013 at 1:02 pmI imported some P2 footage in a new SV12 project after the update, and the first thing I noticed was the Timecode was now displaying correctly on the clips in the timeline. So they got that one fixed!
I had the GPU accelerator DISABLED also and the footage seemed to be playing smoothly. But I need to render out and playback to see if the problem still exists. I will let you know. -
David Bilodeau
February 2, 2013 at 4:44 pmMark, my preliminary testing of my problematic P2 footage is very promising. I’m still unsure about what I am seeing on my PC screen from that camera of interlacing during panning, compared to my other el-cheapo prosumer cameras which are flawless but the jury’s still out.
Anxious to hear of your results, and if you have certain good results would you mind sharing your precise configuration and step-by-step setup? Maybe it’s just a case of finding the right filter and other settings to insure proper results.
-
Mark Krueger
February 3, 2013 at 10:59 pmIn an earlier post I indicated that the timecode appeared to be fixed with the new build. I take that back! I must have been using SVP 11. Here are two screen shots. They both are showing the same two clips on the timeline. Notice the timecodes at the end of clip one and the start of the second clip. In Vegas 11, They show a continous timecode. In the new build of Vegas 12 the timecodes start at 0 for each clip. According to the release notes that should have been fixed!
-
David Bilodeau
April 5, 2013 at 11:26 pmSony released build 563 (64-bit) and I just installed it today.
The Panasonic P2 shakiness/interlacing issues seem to be resolved.
The release notes about this mention a fix specifically toward the P2 so maybe they finally got it right.
Reply to this Discussion! Login or Sign Up

