VEGAS Pro 14 Update 3 (build 201)

Comments

ed-sharpe wrote on 11/19/2016, 12:29 PM

I have  titler 3 will that even  work if we upgrade?  we also need an  unconfused infto   generous upgrade price.. our Communications and broadcast museum is on very limited   funds Thanks Ed - couryhouse@aol.com

I also have a mostly non working NewBlue Titler 3 Pro on Vegas 14 Pro Suite even after the build 201 update.  The Titler works great unless I push the library button.  About 70% of the time this crashes the Titler within Vegas.  I found the Titlerstandalone.exe at  programs / NewBlueFX / Titler /Titlerstandalone.exe on my computer.  I just made a shortcut of it to the desk top.  Outside of Vegas for me the Titler works perfectly as a standalone.  I have been doing all of my Titler work on the standalone, save and then within Vegas I drag the Titler as normal then open the title that I worked on, works.  I can still do all of the fine tuning within Vegas on the titler as long as I don't push the library button.  This works for me as a workaround until NewBlue comes up with a update.  Hope this helps. 


Issues with Titler Pro require New Blue to fix.  TP 4 does not work but TP 5 does.  New Blue has acknowledged issues with v. 4 but no timetable for a fix.

 

I have  titler 3 will that even  work if we upgrade?  we also need an  unconfused infto   generous upgrade price.. our Communications and broadcast museum is on very limited   funds Thanks Ed - couryhouse@aol.com

I also have a mostly non working NewBlue Titler 3 Pro on Vegas 14 Pro Suite even after the build 201 update.  The Titler works great unless I push the library button.  About 70% of the time this crashes the Titler within Vegas.  I found the Titlerstandalone.exe at  programs / NewBlueFX / Titler /Titlerstandalone.exe on my computer.  I just made a shortcut of it to the desk top.  Outside of Vegas for me the Titler works perfectly as a standalone.  I have been doing all of my Titler work on the standalone, save and then within Vegas I drag the Titler as normal then open the title that I worked on, works.  I can still do all of the fine tuning within Vegas on the titler as long as I don't push the library button.  This works for me as a workaround until NewBlue comes up with a update.  Hope this helps. 


Issues with Titler Pro require New Blue to fix.  TP 4 does not work but TP 5 does.  New Blue has acknowledged issues with v. 4 but no timetable for a fix.

 

ok this is  not  good  about titler  3 then... any chance there will be  a  fix  for this?  thasnk Ed Sharpe archviist  for SMECC

fr0sty wrote on 11/19/2016, 12:33 PM

Thank you for very quickly addressing the ProRes judder issue... I was able to report the bug and you guys had a patch out before my project was even due. That's good service! Adding ProRes rendering support was icing on the cake. Excellent update. 

glovercover wrote on 11/20/2016, 12:29 AM

VEGAS team, thanks for this update. Now need to add DNxHD for pros. Personally i need powerfull Сolorgrading tool with LUTs, LumetriColor good example :)
And now i can say, if you still have not update to Vegas Pro14? Its Time ! 

p.s. Nick, these forum rules, remind me of my childhood in the Soviet Union. :) 

 

igniz-krizalid wrote on 11/20/2016, 12:29 AM

Great! new enhancements for V14, thanks so much for this!

Main PC:

MSI X370 Pro Carbon, R7 1800X, OC Nitro RX 480 4Gb, 2X8GB DDR4 3200 CL 14, 850 EVO 500GB SSD, Dark Rock 3 cooler, Dark Power Pro 11 650W Platinum, Serenade PciE CM8888 Sound Card, MultiSync 1200p IPS 16:10 monitor, Windows 10 Pro 64bit

Second PC:

Z170XP-SLI, i7 6700K, Nitro R9 380 4Gb, 2X8GB DDR4 3200 CL 16, MX200 500 SSD, MasterAir Pro 4 cooler, XFX PRO 650W Core Edition 80+ Bronze, Xonar D1 7.1 Ch Sound Card, NEC MultiSync 1200p IPS 16:10 monitor, Windows 10 pro 64bit

Jam_One wrote on 11/20/2016, 6:41 AM

Marveltastic!!! 😀
It's a pleasing news to hear! 🙃
(Can't wait to test the new 'sharpness' behavior.)
_______________________________________________________________

Oh, wait!...

  • Removed a Render Alpha Channel checkbox that mistakenly appeared when rendering to a CineForm AVI file (which does not support an alpha channel)

...But the full paid version of Cineform codec does really support alpha! 😉

_______________________________________________________________

Update:
OK, you finally fixed that 'Sharpen' plugin! Thank you very much, now it is totally usable!

Update 2:
Wow, MAGIX ProRes !!! 😲 It's a miracle!
...So, it was you who bought Miraizon? 😎

 

Last changed by Jam_One on 11/20/2016, 7:45 AM, changed a total of 6 times.

Win 7 Ultimate | Intel i7-4790K @ 4GHz | nVidia GTX 760 4GB * 2

SSD | 32 GB RAM | No Swap file | No Overclock | GPU-in-CPU OFF

t.A.T.u. F.o.R.e.V.e.R.!

 

Nick Hope wrote on 11/20/2016, 7:51 AM
...But the full paid version of Cineform codec does really support alpha!

I don't think there even is a full paid version available any more, is there? I thought it was discontinued. But if the legacy paid Cineform products support alpha channel then it would be a shame not to allow it.

I was surprised that the box was completely removed in build 201 rather than grayed out, like it is for the other VFW formats that don't support alpha channel.

That RGBA 4444 option is also shown with the current free version of Cineform ( https://shop.gopro.com/International/softwareandapp/quik-%7C-desktop/Quik-Desktop.html ). If alpha channel isn't supported then why is it there?

I guess someone who knows what they're doing with alpha channels (i.e. not me) could test it in a previous Vegas version where the "Render alpha channel" box is still available.

Jam_One wrote on 11/20/2016, 11:05 AM

...Well... I have tested Alpha behavior in Vegas 14. It works. Yet.

Cineform AVI does really support an alpha channel.
Take a note of a quirk: Cineform media, imported into Vegas, gets automatically assigned "None Alpha" status. One has to change it manually to Premultiplied.

This is Cineform 4:4:4:4 - a file with alpha:  https://yadi.sk/d/ySaSDxugz5nJV

Original image used in demonstration - a PNG with alpha - courtesy Detonation Films: http://www.detonationfilms.com/free_stuff_page_3.htm

Control shot - a file, rendered in 4:4:4 mode to make sure the black background can not be misinterpreted for alpha channel: https://yadi.sk/d/4X5iQ7QEz5oyx

_______________________________________________

Hence a request to Vegas Creative Team:
Dear Vegas Creative Team, please don't kill that functionality completely! 😉
Cheers!

Jam_One wrote on 11/20/2016, 11:32 AM

I don't think there even is a full paid version available any more, is there? I thought it was discontinued. But if the legacy paid Cineform products support alpha channel then it would be a shame not to allow it.

Yep, the sales are no longer with us.
But the sold software was not demolished from computers of Cineform's customers, and it is still absolutely operational. With its "First Light" with non-destructive metadata editing "on the fly", and LUTs, etc.
I was not able to test the newest free versions from GoPro and for this reason I'm "afraid" of installing it - "afraid to damage my licensed installation", let's say so.

Nick Hope wrote on 11/20/2016, 8:36 PM
This is Cineform 4:4:4:4 - a file with alpha:  https://yadi.sk/d/ySaSDxugz5nJV

Just tested it and even the current free version of Cineform will re-render that file with an alpha channel in RGB 4:4:4:4 in VP13, but now not in VP14.

So it is unfortunate that this functionality has been removed. Hopefully we can get it restored in the next update.

AVsupport wrote on 11/21/2016, 1:13 AM

geez, I thought I had subscribed, why don't I get notified about those releases..been waiting (for titler fix, mp3 fix...) hmm maybe an rss feed button somewhere? what am i missing..?

 

Last changed by AVsupport on 11/21/2016, 1:14 AM, changed a total of 1 times.

my current Win10/64 system (latest drivers, water cooled) :

Intel Coffee Lake i5 Hexacore (unlocked, but not overclocked) 4.0 GHz on Z370 chipset board,

16GB (2x8GB Corsair Dual Channel DDR4-2133) XMP-3000 RAM,

Intel 600series 512GB M.2 SSD system drive running Win10/64 home automatic driver updates,

4TB 7200RPM NAS HGST data drive,

Intel HD630 iGPU - currently disabled in Bios,

nVidia GTX1060 6GB, always on latest [creator] drivers. nVidia HW acceleration enabled.

main screen 4K/50p 1ms scaled @175%, second screen 1920x1080/50p 1ms.

Former users wrote on 11/21/2016, 3:20 AM

I have a problem after this build 201 update. After rendering there seems to be dublicated frames in video. I have tried at least Sony XAVCS and Prores (29.97p). By checking rendered video frame by frame the issue can be seen.

Maybe it is my computer or videofiles, but Vegas Pro 14 worked before update. My GPU is old GTX460. My camera is Samsung NX1 (HEVC 4k files).

EDIT: I checked again with EOS M files and they seems to render correctly. But my HEVC 4k files don't.

set wrote on 11/21/2016, 3:41 AM

I have a problem after this build 201 update. After rendering there seems to be dublicated frames in video. I have tried at least Sony XAVCS and Prores (29.97p). By checking rendered video frame by frame the issue can be seen.

Maybe it is my computer or videofiles, but Vegas Pro 14 worked before update. My GPU is old GTX460. My camera is Samsung NX1 (HEVC 4k files).

EDIT: I checked again with EOS M files and they seems to render correctly. But my HEVC 4k files don't.

Possible to share a small sample ? (A lot of Motion if possible), and what render target format & specs you are rendering to ?

Former users wrote on 11/21/2016, 4:09 AM

I just render a clip and it really seems that my HEVC 4k files are not supported now correctly. Every, lets say 8-10 frame is a dublicate as far as I can understand because the video is not moving then. When I render I just choose the output format (e.g. Sony XAVCS or Prores (29.97p).). All else default.

I quess one can't upload videos here in this forum? But If Magix asks I can upload to them.

 

AVsupport wrote on 11/21/2016, 4:44 AM

just tested: MP3 import/export working FINE ;-) thank you.

packaged titler still old problems...

my current Win10/64 system (latest drivers, water cooled) :

Intel Coffee Lake i5 Hexacore (unlocked, but not overclocked) 4.0 GHz on Z370 chipset board,

16GB (2x8GB Corsair Dual Channel DDR4-2133) XMP-3000 RAM,

Intel 600series 512GB M.2 SSD system drive running Win10/64 home automatic driver updates,

4TB 7200RPM NAS HGST data drive,

Intel HD630 iGPU - currently disabled in Bios,

nVidia GTX1060 6GB, always on latest [creator] drivers. nVidia HW acceleration enabled.

main screen 4K/50p 1ms scaled @175%, second screen 1920x1080/50p 1ms.

set wrote on 11/21/2016, 4:55 AM

I quess one can't upload videos here in this forum? But If Magix asks I can upload to them.

Upload to dropbox / google drive / wetransfer, then share the link.

Btw, I'm curious to search on the internet for Samsung NX1 downloadable file...

Does this one similar to yours?

http://www.imaging-resource.com/news/2014/11/19/samsung-nx1-4k-video-samples-and-new-full-res-frame-grabs-available-for-do

Former users wrote on 11/21/2016, 5:24 AM

 

http://www.imaging-resource.com/news/2014/11/19/samsung-nx1-4k-video-samples-and-new-full-res-frame-grabs-available-for-do

I am downloading one of them and test it. Should be similar file.

set wrote on 11/21/2016, 5:31 AM

Ok - btw - let's continue discuss about this Samsung NX1 HEVC issue here:

https://www.vegascreativesoftware.info/us/forum/samsung-nx1-hevc-4k-files-issue--104568/

Former users wrote on 11/21/2016, 5:33 AM

Tested. Same problem exists.

yvid_SAM_0231-HQQuality.mp4 was the file.

Former users wrote on 11/21/2016, 5:35 AM

Ok - btw - let's continue discuss about this Samsung NX1 HEVC issue here:

https://www.vegascreativesoftware.info/us/forum/samsung-nx1-hevc-4k-files-issue--104568/

Ok.

zulqar-cheeema wrote on 11/21/2016, 6:09 PM

Cheers big ears, good news  😎

RogFromTheGarage wrote on 11/21/2016, 6:50 PM

I just wanted to say "Thank you" for picking up where Sony left off. V14 of Vegas seems to be very stable and my render times are amazing.

Cosmin_Gurau wrote on 11/21/2016, 7:43 PM

I am pleased to see that real work is being done to fix bugs and add features. I have more and more hope now that VEGAS will be rising from its ashes. I am grateful for such a dedicated team. However, I must stress that some of these improvements are not complete. No half measures, gentlemen, please. It is only through uncompromising quality that the PRO in VEGAS PRO will be taken seriously. And GOD I hope it will be. I have made a video pertaining to the whole improvement of the prores importing process. It is clear that some progress was made, but it is not enough. Without further ado: 

set wrote on 11/22/2016, 2:38 AM

I am pleased to see that real work is being done to fix bugs and add features. I have more and more hope now that VEGAS will be rising from its ashes. I am grateful for such a dedicated team. However, I must stress that some of these improvements are not complete. No half measures, gentlemen, please. It is only through uncompromising quality that the PRO in VEGAS PRO will be taken seriously. And GOD I hope it will be. I have made a video pertaining to the whole improvement of the prores importing process. It is clear that some progress was made, but it is not enough. Without further ado: 

Cosmin_Gurau, since you have so many ProRes media here, can you try convert all these files to Sony XAVC Intra / Long by using free Sony Catalyst Browse ?.

ProRes is MOV-wrapped, and so far I remember, Vegas is trouble keeping up when you have too many MOV files in your project. After all your media successfully converted, do you have trouble putting these converted media to VP14 ?