Comments

TheHappyFriar wrote on 2/27/2014, 9:00 AM
All bugs are NEVER fixed.

Have you ever stopped working on a video even though you said "You know, I could do this better..." :)
Carlos Werner wrote on 2/27/2014, 9:22 AM
At least "my" bugs are not fixed...
NormanPCN wrote on 2/27/2014, 9:25 AM
I know the fonts problem in Titles and Text is still unfixed, and that was acknowledged as a known bug a year ago.

I know of an acknowledged bug in the XAVC encoder.

Hitfilm integration with subclips has an acknowledged bug.

The slip trim keyboard shortcut keys item was recently acknowledged in this forum.

I have a submitted report of a GPU accel bug with the HSL plug-in saturation slider. I reported that a month ago with a VEG file to demonstrate. We'll see if Sony responds to that and possibly acknowledge it existence.

These are things that I know about. The list of "official" bugs probably has more items on it than you have fingers and toes with some multiplier factor.
dxdy wrote on 2/27/2014, 9:46 AM
Many years ago, when IBMs OS 360 ruled the world, IBM's president was speaking before its big user group. Someone asked him how many bugs remained in OS 360. After a short pause, he replied "twelve".

Back in the 1960s, I was a student employee at the University of Michigan computing center, where we had a 360/67 (serial number 2), the timesharing version of the 360/65. A small band of grad students created MTS (Michigan Time Sharing) OS, which was supposed to be a stop gap until VMS came out. It ran for many, many years.

Michigan had earlier created MAD the Michigan Algorithm Decoder for the 7090. Students ran on the 7090 until MTS was solid. MAD would print a portrait of Alfred E. Neumann with every core dump (students like to divide by zero).

I am not trying to minimize the problems that some of this forum's hard working members are dealing with. Just a little history.
set wrote on 2/27/2014, 5:34 PM
Speaking of bugs,
Just had trouble with it yesterday, as this is the first time using 770 build, in the middle of rendering 'a bit complicated' project, 'Problem Report' box pop-out.
First, rendering to AVCHD M2TS with situation 6 app of Vegas opened (https://www.dropbox.com/s/hvspdgt5l6lid6n/VP12-crash-20140226---6app-RAM90.jpg)
and second time, after restart, render to Blu-ray AVC format.

I monitor my PC via Win gadget : http://addgadgets.com/all_cpu_meter/ and noticed the Page was rising. I can't be sure if this is the problem because I didn't take note for it during previous build.

Restarting didn't help, then, I shut down, disconnect the cable for a second (in some ways it did the trick), and for safe, I rendered them all first to intermediate MXF then render to avchd m2ts and Bluray AVC.

Whether this caused by Page memory or due to complicated project, not sure.

Set
VidMus wrote on 2/27/2014, 7:16 PM
I got an email from VASST that the NAB Show is from April 5 to 10 2014 for conferences and April 7 to 10 2014 for exhibits. Las Vegas, Nevada.

http://www.nabshow.com/

So maybe the next version of Vegas will be announced then?

LOL!!! Only the shadow knows!!! LOL!!!


ushere wrote on 2/27/2014, 8:49 PM
so, i presume the 'render as' whiteout will get carried across to the next version?

i hadn't realised till rainer mentioned it in my 'render as' thread that this problem has been around for a very, very long time apparently. this actually prompted my failing memory into recalling having this problem in both 9 and 10, and in one iteration of 11. in all cases it seemed to disappear with a point release.

could a single corrupt vegas file cause such problems?

anyway, not in a hurry to part with anymore money to scs while i suffer this bug...
i am erikd wrote on 2/28/2014, 3:49 AM
Just want to add a couple of bugs in V12 that are harmful to my workflow.

1) The fact that you can't add tags to subclips in V12 is a huge drag. As editors we want to get our bins tight with editing options and the best way to do that is with subclips. You can create the subclips and put them in folders, etc., but when you reopen V12 ALL of the work with subclips just disappears!

2) V12 continues the bug that started with V10 where regions and markers added in the trimmer window are not permanently saved to the original file. I am shocked that others don't use this feature as much as I do as I find it indispensable for marking in and out points with my descriptions. Workaround is to bring the clip into V9 (which does work as it is supposed to) and add the markers, regions and comments there. Then when bringing the clip into V12 it will see the markers as expected.
OldSmoke wrote on 2/28/2014, 8:46 AM
Saving marker and regions in the trimmer works fine in VP12 when enabled.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

i am erikd wrote on 2/28/2014, 8:59 AM
That is not the case for clips I'm using such as MPEG-4. This is a known issue acknowledged by Sony..

What types of video are you able to get the markers and regions to stick and stay?
OldSmoke wrote on 2/28/2014, 9:58 AM
I just tried with files from my Canon HF G30, 1920x1080 MP4 60fps @35Mbps and it works as advertised. I used Vegasaur afterwards to promote the media markers & regions back to timeline markers & regions. I also tried one of my MC AVC MP4 files rendered our from Vegas and works there too. Also note that CTRL+SHIFT+K toggles the markers on/off.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

i am erikd wrote on 3/2/2014, 12:46 PM
Interesting report and glad it works for you, Ironic that the Sony XDCAM mp4 proxies do not retain the markers. Known bug since V10. Painful that Sony has ignored their own XDCAM workflow in Vegas all these years.
OldSmoke wrote on 3/2/2014, 4:27 PM
I don't quite follow. Why do you want to retain the media markers in the proxy file? If I work in the proxy mode, preview set below "Good", then all markers I make in the trimmer on any file are stored in the original file which is where they are supposed to be. Vegas uses the proxies only for preview. I don't see the bug.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)