Geez thanks John... I just want the bugs fixed... Very helpful though...
@marshall-t - Notwithstanding @john_dennis "on-mission" comment, please list the Bugs you are seeing? I note you joined today, and subsequently come out with all guns blazing! Do you have a relevant or even an apposite question?
Thanks Grazie. Yes I have used Vegas from Vegas 7. First in Audio then High end Video. I use 18 and 19 on multiple computers with similar bugs. Single track of 4 k video from Two Canon R5s. Sometimes the track can't be seen in the preview window. Sometimes a single track wont render out on all computers. Sometime's however it will render.
Pre-rendering a simple Samsung 4k Codec will also do the same. Forget about even using multi Codecs as 17 would do well. I admit it had bugs but I could work around it
All computers are Good machines optimized for video. 18 core Xeon 6240 128 DDR4 Ram nvidia graphics 3080 ti Etc.I've checked the comp resources everything from that point of view is fine.
In addition, provide detailed descriptions of the bugs you mention, along with the steps needed to reproduce them. That's Troubleshooting 101, and many reports turn out to be based on prior expectations, or PEBCAC,
"Please fix all the bugs..." without detailed info of how to reproduce or other supplied info is hard to trace and where to find. On the other side, I'm enjoying more of editing with latest VP19.
ok... so the clue we currently know is that, you are using Canon R5
VEGAS Troubleshooting 101... To fix these bugs, start by doing these things.
1. I always recommend this first, run the driver update utility in the VEGAS help menu. If it recommends new drivers for your GPU, install THAT driver and update to it, do not just go to Nvidia's site and snag whatever driver they have, there are particular drivers that work best with VEGAS (namely, studio drivers for Nvidia). Even if you already have one installed, I'd still check that utility to see if maybe another version works better.
2. Mediainfo is VITAL for us to help you. Download it, it's a free app, then run it on the problem causing clips (right click on the clips to run it). It will generate a report. Set the view to text or HTML, it shows the most info (stuff we need). This is very important for us to help.
3. We also need to know your project settings, whether or not you are using GPU timeline acceleration (in the video tab of preferences), GPU decoding (in the file i/o tab of preferences), and if you have the legacy decoders for AVC/HEVC (also in file i/o) enabled or not (don't, they usually do more harm than good).
From there, detailed specs of the system you are running it on (you've provided enough info here already), and what version (and build) of Windows you are using.
Once we have all this, we will be able to hone in on the cause of your issues much faster.
One more thing to consider... this is a user help forum, run by fellow users. One of our rules is we only allow posts seeking help, not to just blow off steam, so let's please keep this thread to requests for help that include descriptions of your problems and the requested info above. We're glad to help, but we're not counselors who are here to calm your frustrations... While bugs are frustrating, please chill yourself out before posting, you'll get help much faster when you're not stressing us out trying to read it. We're just users like you, and are not being paid by Magix to help you, please remember that.
Magix is pretty hands-off with these forums, as VEGAS is actually developed by VEGAS Creative Software, which is owned by Magix. The staff of VCS do use these forums, they do read and occasionally reply to the posts (however, they need to be keeping their heads focused on coding bugfixes and updates, so we usually do this for them), and many of us have a direct line of communication with them if we need to make them aware of a bug that any users are experiencing that we are not able to solve, so even if we get stumped, there's a good chance we can reproduce the problems you are having and notify the dev team so they can get an update out that solves your issue as soon as possible. We have a really good track record of resolving user issues, so work with us, we'll gladly work with you, and will likely get you up and running in no time.
Thanks Frosty. All my drivers are current. Computers are maintained to the point of madness. Mother board is also up to date. Win 10 Pro Build 19043. GPU acceleration is turned off as it's way to slow compared to my CPU rendering. I use Nvidia studio drivers and all up to date.
AVC/HEVC decoders aren't enabled as I have had problems with rendering the codec before.
The biggest issue right now is Premier, After effects and Resolve all work fine.I just prefer Vegas as the workflow is incredibly intuitive and fast from an editing perspective.
Thanks for your insight. You're right, frustration shouldn't dictate my words.
@marshall-t - So, your Litmus test is that those “other” three NLEs, if the Media works in them, then, all things being equal, the Media should now work in VP? Am I correct in my assumption of your logic? Yes?
So, what are the characteristics of your Media, as reported by MediaInfo? If you’ve already posted your MediaInfo above, my apologies. If you haven’t, please do. It could help us in not chasing our tails.
@marshall-t Out of interest have you used Resolve17 with your chosen media? It's a very good NLE with an easy licencing setup with good tutorials on program useage. Indeed if VP is so buggy why persevere with it. Time is money.
VP has a great forum community but patience is also an asset . You must be specific and state problems clearly. Your readers are not clairvoyants.
Grazie... No absolutely not.. I have trained people In SONY in Vegas when Roland Corp brought in Sony Vegas to Australia. So in saying that I know the program well.
I know computers extremely well as I put together computers for multiple clients as well as training in-house video people.
It absolutely could be user error on my part as I am very aware that no-one knows everything.
In the same breathe, I also realize that most people in forums don't have the pressure of having to deliver real time Pro Video to a deadline.... When I sit up for 36 hours on a deadline and my main NLE crashes a bunch of times for unknown errors.. I'm sure you can understand that.. Although it may well be my fault. It can get a tad overwhelming.
I truly appreciate all of your comments and help. To have to change all of my editing into another program that I would prefer not to use can be horrific to say the lease...
As far as my language may have not been the best at the beginning... I really am just looking for a fix.
I also realize that the tribal nature of people uniting behind one piece of software may well work in a world where people don't make money out of filming and editing. However this is where I make my money. So I have to use multiple pieces of software. As again, I'm sure you're aware. Vegas doesn't do everything...
I use 18 and 19 on multiple computers with similar bugs. Single track of 4 k video from Two Canon R5s. Sometimes the track can't be seen in the preview window. Sometimes a single track wont render out on all computers. Sometime's however it will render.
Pre-rendering a simple Samsung 4k Codec will also do the same. Forget about even using multi Codecs
That's it? There is no such thing as a random error that happens again. "Sometimes it does, sometimes it doesn't" always means we're not getting the full story. How about starting with one problem, tell us how to cause it, and provide source footage and a project if asked? The link that Nick gave you is golden around here:
@diverG Yes mate.. I use Resolve 17... It's been fantastic.. The front end is similar to Premier in respects. However the colour correcting is absolutely unbeatable.. The reason for me joining the forum in the first place is the multi track editing in both audio and video in vegas. I've recorded more than one hundred tracks of audio seamlessly in Vegas as well as 15 camera tracks 11 4k and 4 HD Cams seamlessly until recently... Hence the problems....
Please keep in mind that GPU acceleration doesn't have anything to do with rendering... the acceleration in the video tab of preferences is timeline acceleration, it accelerates effects like text, generated media, and all of the effects that are in the "GPU accelerated" effects folder in VEGAS. Turning this on will speed up your renders, because it speeds up the time it takes to actually render the frame, but your CPU is still doing the encoding unless you select one of the NVENC render presets in the "render as" dialog. The GPU decoding in file I/O is similar, it doesn't affect rendering, but it can still speed it up because it offloads decoding the video files (for supported formats, GPUs can't decode everything) of the CPU. When you go to render, the CPU still does the encoding, again, unless you select one of the NVENC render templates.
Some formats decode poorly with a CPU (HEVC, for instance). If you use GPU decoding on these formats, you will notice your timeline performance goes way up when playing back files on the timeilne, as the CPU isn't struggling to deocde the video.
Only those NVENC render templates have anything to do with the GPU actually doing the encoding. So, you may notice big performance improvements by enabling GPU accel in the video and file i/o tabs of preferences, and you can still let your CPU do the heavy lifting when it comes to encoding.
I was using17 then bought 18. Just too many bugs in 18. Crashed all the time. Now you want to sell me 19. Good luck, fix 18 first. Too much money and time involved with Vegas to keep on investing. Upgrade should be free if that fixes the bugs. Why should I upgrade if the current version is buggy? And yes, I reported the bugs a while back, but support was so frustrating. GOD ALMIGHTY have good tech support. I mean at least chat online, email back and forth and going to forums is a big waste of my time.
All versions of VEGAS offer a free demo so you can see if it works well on your system before you buy it.
If you want help, post the issue you are having (in its own thread) along with the info requested here. If you're just here to blow off steam, there is a community rule against that, so your posts and account will be removed if that continues. This is a user forum, we're fellow VEGAS users just like you. Complaining to us accomplishes nothing... but if you give us the info we need, 9/10 times we'll be able to help you sort your issue out.
You'll notice the OP never found a solution to their problem... Perhaps because they weren't actually interested in finding a solution to their problem, they just wanted to whine about it. They did absolutely nothing to provide the info we requested.
You can't go into the hospital complaining about your body not working the way you want, but not giving the doctors the slightest clue about what is ailing you, and expect them to be able to cure you. Same applies here.