David Bilodeau
Forum Replies Created
-
Sony 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.
-
Mark, 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.
-
GPU acceleration on or off? Try disabling…very problematic in Vegas 12…even the new build, not yet sure but playback frame rates lock at source rate on Best/full during playback in the new build with accel off and I have not tested yet for program hang with accel on.
Get the very latest beta video drivers…seems never to hurt and has helped me a couple times these frustrating months since 12 was released…a real train wreck version for Sony…I have been on since v4 and this is the worst yet.
What kind of source footage? New version fixes some P2 bugs but the release notes say you have to re-import the source media. My tests last night after uograde are promising but incomplete.
Thread aetting? No more than one less than the total # of cores in the system. 4 cores? 3 rendering threads. And set memory buffer size to 500 or 750…no more or Vegas will page swap.
Also, can you try a render to a physical disk instead of Ssd? There are some reports around about Ssd issues unrelated to Vegas but related to corruption of data…
Just some random thoughts to suggest…
-
I 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!
-
From 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. -
Vegas 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 -
Mark, 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.
-
Bruce, 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.
-
My two cents’ worth:
There are two kinds of 1394 Firewire interfaces…those with the Texas Instruments chipset, and those without.
Vegas will only “reliably” support the TI chipset, and it’s more a Windows issue than a Vegas issue.
I battled this problem some years back with an earlier version of Vegas Pro and it was finally resolved when I broke out my old TI 1394 board from my mothballed computer and put it in my new PC, which had the non-TI 1394 interface.
Worked perfectly ever since.
-
Mark, I just did something a little off the wall with regard to the P2 footage I have and my preliminary results are promising enough, thought I’d pass this along and see if you have similar results if you try it.
I have my original .mxf files in the timeline. Previously if I rendered them for BluRay directly, I got the awful results.
I started looking at other formats for an interim render. First I tried Sony MXF XDCAM SR (*.mxf) and got bad results.
Just now I tried Sony MXF, the “HD EX 1920×1080-24p” format, and the result of this rendering looks ok.
I think MAYBE an interim (extra!) step to re-render, maybe the Sony codec is able to process the footage correctly between these types and then the resulting file can be rendered down for BluRay.
I also set my render quality to Good-Full instead of Best-Full and I don’t know if that made a difference or not…really too many variables, but the point is, I am at least no longer ready to pull my hair out because I seem to have stumbled, with some trial & error, on a method that – while taking the extra step and thus more time – might get me over the hump for now.
Sony remains totally unresponsive. I plan to try and call after Christmas and see what they say.
Good luck! Let me know if you experiment and have similar results.