VEGAS Pro 15 Update 4 (build 321) - General Discussion

Comments

Reyfox wrote on 5/10/2018, 12:52 PM

@Vliegvisser , I didn't understand that post either...... I can understand those having issues with those codecs and those that use AMD cards (I am one of them). I don't know the finances behind BlackMagic nor Magix/Vegas, but i would wager BM has the financial resources and have created a synergistic product with their cameras and an editor... something that Sony could have/should have done.

What can be said as to why Vegas does not have public beta, can be said about Avid, Adobe, Edius, FCP and every other editor I am aware of. This is BM's model and it works for them. I can't see it working for a product that is only based upon sales of one product. But that's me. My loyalty and money go where ever I think is the best value for my "dollar" and works with what I choose to edit with.

Vliegvisser wrote on 5/10/2018, 1:06 PM

What can be said as to why Vegas does not have public beta, can be said about Avid, Adobe, Edius, FCP and every other editor I am aware of. 

Indeed you're not, as a long time user I can remember many public beta's for Vegas Pro 12.😇

marc-s wrote on 5/10/2018, 1:13 PM

I was responding to the person who said they were getting crashing in Resolve 15 with XAVCs footage. It's quoted above my original comment. But yes Magix probably does not want posts here talking about how great Resolve handles this type of footage. I get it.

Vliegvisser wrote on 5/10/2018, 1:14 PM

A) Resolve handles XAVC-S and XAVC-L better then Vegas and makes good use of AMD hardware.

That shows the it can be done and should have been done along time ago, XAVC is not a new codec.

Not my fault that I have no problems using those files on my laptop and desktop. Both without AMD , but with Nvidia GTX 1050 which I bought both after the releases of VPro 15 and experience the same with VMS pl 15. Am I lucky or just in time?

vkmast wrote on 5/10/2018, 1:35 PM

But yes Magix probably does not want posts here talking about how great Resolve handles this type of footage. I get it.

The user you may be referring to is not a Magix employee, neither are any of the volunteer moderators. The opinions expressed here are their own, not Magix's. Some of the related threads may have been moved to Offtopic though.

AVsupport wrote on 5/10/2018, 6:05 PM

I'm prioritizing the team's work based on the feedback I'm getting.

Thanks for the encouraging words @gary-rebholtz. The feeling I get from reading these forum posts, there is a high level of frustration and abandonment. Since the first 'wave' of quick consecutive updates, not much has happened since, not even lip service, until now, and no one knows why. I think it could help, being the Captain, letting your customers know which way you intend to steer the ship, what the priorities are, what next updates we can look forward to. I think this could buy you a lot of needed patience and added loyalty.

Last changed by AVsupport on 5/10/2018, 6:07 PM, 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.

Fiola wrote on 5/10/2018, 7:20 PM

I'm prioritizing the team's work based on the feedback I'm getting.

Thanks for the encouraging words @gary-rebholtz. The feeling I get from reading these forum posts, there is a high level of frustration and abandonment. Since the first 'wave' of quick consecutive updates, not much has happened since, not even lip service, until now, and no one knows why. I think it could help, being the Captain, letting your customers know which way you intend to steer the ship, what the priorities are, what next updates we can look forward to. I think this could buy you a lot of needed patience and added loyalty.


Exactly, thank you very much @GaryRebholz, as far as I remember, VEGAS in hands of MAGIX is on pretty great way continue to grow. I think that we just all need more open information, that's it. Nobody is asking for "NDA" stuff here :). I think nobody wants to know exact dates or exact promises, but just to know what's next. Or maybe creation of some open issue-tracking (like mantis, or JIRA could help too), so we can somehow talk with you more easily and with knowing that our feedback is not voided or maintained on the phorums as "unofficial bug reports" but "very official bug reports". :)

I personally don't want to switch to any other software, I am postponing that moment as I can... because, and that's true, in a own way, there isn't any NLE with such freedom of editing on the timeline (workflow) as VEGAS. :) Don't let go this great stuff and let's fix that together. Tell us how we can help you more.

gary-rebholz wrote on 5/11/2018, 9:38 AM

Thanks for the gentle reminders @Fiola and @AVsupport.

I must admit that I have let some of the relentless negativity on these pages push me away from being as engaged as I used to be. I'm not talking about the legitimate reporting of problems or asking the community for help. I'm talking about the other approach.

I will thicken my skin once again and keep reminding myself that there are reasonable users here who just want and need help.

It is tricky to figure out what information to share and what not to share. If I say something and then that doesn't happen, it is virtually guaranteed that someone will start a thread how I "promised" something in order to "trick" them into buying the software, and then I didn't keep my promise. Then new people will read those comments and decide they don't want to buy from such dishonest people.

So I try to make general assurances that I'm listening and that we continue to work on the issues you guys are reporting. We are working on another free update (Update #5) now. It will be a strong update with nearly 30 fixes, including one of the ones that has gotten the most noise here. It will be available "within the next weeks."

What I hope most readers realize is that many of the problems that get the loudest noise here are quite specific to certain combinations of project complexity, hardware configurations, file formats, and other variables. That's why one guy here says he can't work with his Such-and-Such footage, and the next guy reports that he has no problem with the same type of footage. When one reads these forums, it's easy to believe that VEGAS Pro is nothing but a package of headaches and problems. In reality, VEGAS is doing better than ever, and by a long shot, most users are editing happily and effectively. That's not to minimize specific problems you guys are experiencing, and so we keep working with you--sometimes putting you in direct touch with our developers so you can share files, projects, information, and so forth to work to a resolution.

I continue to be very proud of the VEGAS team. We want your experience to be wonderful. We want to make the best software ever. We want to keep you from moving to another tool, and if you already have, we want to bring you back because we believe there is no better way to edit video than with VEGAS Pro. That is not the experience some are having, and that motivates us to solve as many problems as we can as quickly as possible. We'll keep working.

Kinvermark wrote on 5/11/2018, 1:24 PM

I must admit that I have let some of the relentless negativity on these pages push me away from being as engaged as I used to be

EXACTLY how I feel too! This is an unfortunate side effect of the internet age where anonymity leads to antisocial behavior. There is also a huge emphasis placed by certain individuals on their unique problems, without recognition that professional, competent users do have some responsibility for adopting workable, pragmatic solutions to some of these "problems." It is not a fair reflection of Vegas' performance or of its user base. I use Vegas regularly to produce high quality projects and have had very few problems; none of them serious.

fr0sty wrote on 5/11/2018, 4:49 PM

"So I try to make general assurances that I'm listening and that we continue to work on the issues you guys are reporting. We are working on another free update (Update #5) now. It will be a strong update with nearly 30 fixes, including one of the ones that has gotten the most noise here. It will be available "within the next weeks.""

This has been a big concern, as with Vegas 14, there were some pretty big bugs I was still having to deal with, hoping for an update, and then 15 got announced. Because we're nearing the point in the year where you announced 15 last year, I was getting a bit nervous that another update wasn't in the plans. Good to hear it is.

My problems have not been isolated to a specific set of codecs or project complexities, I mention those problems more often as they are the most often to hold up some of my more important productions, but I have experienced issues with just about every codec under the sun. It is honestly at the point where it is rare to not have Vegas hang on me at least once or twice during a production. Over the years I've learned workarounds to keep it doing what I need it to do, and how to avoid it crashing to begin with (such as... always pause video before deleting it with the delete key! Vegas doesn't like it when you delete a clip it is currently playing), but I've always dreamed of the day I'd get to see Vegas' beautifully designed UI running at least mostly bug-free with all of the latest video tech under the hood. You're making progress, I know you had a mess to clean up when you got into this... Just keep us in the loop. You don't have to make promises, you can just give us a general idea of things like you did here. We don't need to know exactly what features an update might have, only that it is coming and a rough time frame. Maybe even teasing a few features you are considering for 16 wouldn't hurt either, getting some feedback from the community on which features to focus on would also be something I'd recommend. Maybe a survey we could all take?

What Vegas does right, it does better than any other NLE. There is a reason that I have stuck with it since version 4, I've developed an attachment to the software that is hard to break. I hope this next update gives me the promise I've seen in previous updates, such as the speed improvements on both the timeline and rendering, before I had to disable to keep things flowing smoothly. Thanks for hanging in there despite all the criticisms, understand that we too want to see Vegas thrive, but it can be frustrating to pay top dollar for a product that stumbles when you need it to run. I look forward to the update! I look forward more to seeing what 16 has to offer. Honestly I'd be more than happy if you just put some love into the color correction tech with HDR support (including writing the required metadata to the files), improved render and playback performance, improve support for 32 bit pixel format in the native plugins, and maybe added a nicer built in title generator that worked with more font types. I'm sure others here have a list of stuff they want to add... but this would get me lined up on day one to buy.

bitman wrote on 5/13/2018, 4:33 AM

If possible, for the next update, please change the behavior (it is not a bug) of the "Video Event FX" window.

One of my main frustrations with Vegas is that that I have to close that window after deleting the last FX by removing that FX (or via undo). My point is I have to do an extra mouse or keyboard action to the state before I add an FX if I wish to undo or get rid of an FX. Especially with FX's I tend to experiment a lot, and that extra action is unnecessary (I already suffer from "mouse arm" RSI). If I add an FX and do an undo I am not necessary interested in the pan crop stuff of the Video event FX window. And please do not tell me no-one is bothered by this small nuisance.

Current system: VP 17 post (build 353), VP16 (suite) build 424, (uninstalled VP 13,14,15), Vegasaur, Magix Video Pro X (VPX11), Corel VS ultimate 2019, a lot of NEWBLUE plugins, Titler Pro 6, Mercalli 4.0, Respeedr, Vasco Da Gamma 12, VASST stuff, Production Assistent pro3, Boris Continuum 2020, Davinci Resolve Studio 16,...

  • OS: Windows 10 Pro 64, version 1903
  • CPU: i9900K stepping R0 (since October 2019), previously, der8auer i7-8700K (advanced edition), default speed (no overclock), Cooler: Noctua NH-D15s
  • RAM: G.Skill Trident Z 3200C14 DDR4 64GB, XMP set to profile 1 in BIOS
  • Videocard: NVIDEA RTX 2080Ti (Founders edition), NVIDEA studio drivers
  • Monitor: LG 38 inch ultra-wide (21x9) - Resolution: 3840x1600
  • C-drive (games & APPS): Samsung NVMe SSD 2TB 960 pro

  • Current Video source work drive: Samsung NVMe SSD 2T 970 EVO plus

  • Mass Data storage & Backup: WD gold 6TB + WD Yellow 4TB

  • MOBO: Gigabyte Z370 Aorus Gaming 7, BIOS F14
  • PS: Corsair HX1200i, Case: Silverstone fortress 2,
  • Misc: Logitech G910, Evoluent Vertical Mouse, shuttlePROv2

 

Former users wrote on 5/13/2018, 5:24 AM

Speaking of small nuisances, would it be possible to allow more than the default 8 list items in the “Customise toolbar” lister?

I checked out “internal” but found nothing there, and the lister is fixed in size, doesn’t allow changing vertical height.

ritsmer wrote on 5/13/2018, 8:00 AM

@bitman maybe I do not understand your issue correctly - but here I just keep the Video Event FX window open - and add and delete FX'es without having to close/open that window after each addition/deletion ?. (Vegas 15 build 321)

mjry wrote on 5/15/2018, 2:45 AM

Hello friends, has anybody noticed this issue of CPU rendering with Sony MXF codec in Vegas Pro 15? Can anybody prove it, eventually add to a bug list? Thank you and have a nice day.

dream wrote on 5/16/2018, 4:14 AM

vegas-pro-15-update-4-build-321- i feel no issue ,looks stable for me

mjry wrote on 5/17/2018, 7:11 AM

vegas-pro-15-update-4-build-321- i feel no issue ,looks stable for me

Have you tried rendering to Sony MXF HD EX codec with CPU in VP15 already?

JoeAustin wrote on 6/4/2018, 2:37 PM

Well poop! I was hopeful that the issue with the so4 plugin would have been among the fixes. Seems the answer is no. Still getting black screens with MP4 footage from my GH5. I ended up disabling it again.

simon-bauer wrote on 7/4/2018, 1:07 PM

When working with longer video projects the application will continually fail without notice just as in the previous versions. This happens just after movie a single clip next to another and clicking onto the adjacent clip. No error code is ever given, it just freezes and fails. This is a broken product.

Fiola wrote on 7/5/2018, 8:04 AM

When working with longer video projects the application will continually fail without notice just as in the previous versions. This happens just after movie a single clip next to another and clicking onto the adjacent clip. No error code is ever given, it just freezes and fails. This is a broken product.

Install the 361 version then.

JoeAustin wrote on 7/5/2018, 8:27 AM

When working with longer video projects the application will continually fail without notice just as in the previous versions. This happens just after movie a single clip next to another and clicking onto the adjacent clip. No error code is ever given, it just freezes and fails. This is a broken product.

Do you have GPU acceleration on in the Video properties tab? If so, try disabling it.

Kinvermark wrote on 7/5/2018, 10:38 AM

@simon-bauer

You should work methodically through troubleshooting guide(s):

https://www.vegascreativesoftware.info/us/forum/vegas-pro-faqs-and-troubleshooting-guides--104787/

Very likely you can find a solution there. The product is not generically broken, as you imply. In other words "works fine here." :)

AVsupport wrote on 7/5/2018, 4:50 PM

@simon-bauer, if you're using an internal GPU and a dedicated graphics card, try to disable the IGPU one entirely in the Bios. This helped me stabilize my system too. /edit: can you pls add your system specs to your profile

Last changed by AVsupport on 7/5/2018, 4:51 PM, 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.

dream wrote on 7/7/2018, 8:19 AM

i dont know its issue or .. but when the timeline curser is moving and i cut (s-key) backwords to the timeline curser its hangs , it doesnt hangs when i cut forwards.

i dont edit like this but it just happend when i am in hurry or i dont know about it.

no big deal to me,it happend 2-3 times in month.

fr0sty wrote on 7/7/2018, 4:08 PM

I've had similar bugs for years with Vegas, where if you delete an event it is currently playing, it hangs.