Comments

Gary James wrote on 9/11/2012, 3:43 PM
With the unstable state of v11. And when you take into consideration that almost every new version of software is built on top of the current version of software, I'd wait till version 13 or 14 comes out. Maybe by then they'll have the kinks worked out .... that's if they still have any customers left willing to pay good money for iffy software updates that run more like paid beta test software.

If Sony fails to fix version 11 before they release version 12. This is my last ever Sony software purchase. I mean what can they do to me? Not fix my buggy software? Or maybe stop answering my customer support questions? Oh wait ... they already did both!
Tim20 wrote on 9/11/2012, 4:17 PM
I second that! I was finally able to achieve stability in V11 by setting dynamic ram preview to zero and not using the external monitor preview button on my second monitor.

Still there are so many quirks: Doesn't recognize alpha channel on all codecs that have the ability. And one of the latest I have found is sometimes the "space bar" wont start play and I have to reboot the program. But my list is a mile long.

I will wait and see if V12 works and watch the complaints but I am probably going to migrate to Adobe Premiere since they provide continued product support. Especially if I don't see one last bug fix before 12 release.
Laurence wrote on 9/11/2012, 5:32 PM
Thankyou Tim. I just set the RAM preview to zero and haven't had a crash in the last ten minutes. This is the furthest I've ever gotten in V11. It also helps explain the "Attempted to read or write protected memory" error message that I get when I try to render with preview RAM allocated. Thanks.

The only problem is that I have 16GB of RAM and when I'm working with DSLR footage, I use the RAM preview function constantly since the AVCHD footage drops frames even on my quad core i7. My guess is that the preview memory isn't being set aside properly anymore. I work regularly with 2GB+ of RAM preview memory in V10.
Kimberly wrote on 9/11/2012, 10:24 PM
@VideoPod:

My suggestion is to make a good system image or restore point, and then load up a trial of VP 11 and take it for a spin. You have 30 days, right? See if you like it, then wait for VP 12 to come out, then take that for a 30-day test drive. Then take advantage of whatever discounts you can get!

I am one of the rare users who has experienced relatively few problems with VP 11. I have it on my older 32-bit Inspiron 1420 laptop and on my shiny still-new Dell XPS. I cannot explain why I haven't had problems, but glad for it.

Regards,

Kimberly
Tim20 wrote on 9/12/2012, 6:53 AM
@Laurence. Np I have been posting that fix everywhere for the last few weeks since I stumbled onto it. You should also be able to come out of compatability mode and use GPU accl without fear of crashes.

If you get those Vegas hangs that used to be the "look out I'm gonna crash on you in a second" just wait. In every instance Vegas has come back.

I'm with you on the AVCHD, same boat, almost same system. One thing that seems to help is keeping audio down to a single track. FPS seems to go to hell with 2 or more audio tracks. Strange eh?
Laurence wrote on 9/12/2012, 7:48 AM
Batch rendering to XDCAM MXF would keep me from needing to shift-b to check timings. I'd use XDCAM MP4 (same mpeg2 video codec) except that that format has a bug that doesn't include markers in a render.