-
Videoon 10/7/2020
VEGAS Pro 18 Update 1 (Build 334) - General Discussion
I tried to import *.mov files - but I failed, though I had enabled the deprecated Quicktime plugin feature - did I miss anything? Having the same issue. Cannot import MOV animation files with alpha ,exported from Adobe Media Encoder. even after enabling deprecated quicktime plugin support from preferences tab, I get a warning to download the latest quicktime version from apple website. No need to say that this also happens after updating to the latest version of quicktime. UPDATE - Solved : uninstalled quicktime completely, reinstalled it again, restarted computer and everything is good again!
-
Messageson 8/19/2019
[Release] VEGAS Pro 17 – The fastest NLE. For passionate creatives.
first impressions : - had to remove boris fx plugin to lunch the Vegas 17 - trimmer timeline height not scalable. it's too short right now. - usual and frightening crashes with GH5 4k 60fps 8bit. with SO4 setting TRUE or FALSE - not able to import MOV files with alpha channel. it says an error occurred. say you are opening a project from VEG16 that had MOV files with alpha (rendered in AME with QuickTim > Animation> RGB+Alpha), it wont import that file and you are forced to open MP4 Variation and use "Screen" composition mode. Disappointing! EDIT :- Undo Performance is a huge pain. it takes too long to undo and sometimes give an error message relating to undo buffer.
-
Videoon 6/11/2018
VEGAS Pro 15 Update 5 (build 361) - General Discussion
@OldSmoke Any preliminary observations about preview performance improvements with VCE in Vegas 15? VCE like NVENC does not improve preview performance, it is primarily for rendering. NVENC is still a mess - at least for me. I had to revert to the older Mainconcept encoder as using NVENC causes random white flashing of some of my footage. I've attached a sample without audio that shows what I'm referring to. I will admit - this update to Vegas 15 seems about as solid as I've EVER experienced. Still laggy on playback when using some intensive FX applied (Neat Video, motion title graphics, etc), but this release is really a breath of fresh air and has me excited about editing again. I was really dreading rebuilding the projects I had done in Vegas over to Premiere Pro CS6 - which I believe I may finally be able to retire. My deepest gratitude and thanks to all the programmers who worked on this update! Random white flashes here too. It occurs independently of preview quality settings. "Magic bullet Look" and "Filmconvert" applied to track. all plugins and VGA driver are up to date. GTX 1080 Ti Did you try to disable Dynamic RAM at 0? 1. Zero dynamic RAM 2. Restart Vegas 3. Render project Haven't tested render yet. But preview in editing is the major problem here.
-
Videoon 6/11/2018
VEGAS Pro 15 Update 5 (build 361) - General Discussion
@OldSmoke Any preliminary observations about preview performance improvements with VCE in Vegas 15? VCE like NVENC does not improve preview performance, it is primarily for rendering. NVENC is still a mess - at least for me. I had to revert to the older Mainconcept encoder as using NVENC causes random white flashing of some of my footage. I've attached a sample without audio that shows what I'm referring to. I will admit - this update to Vegas 15 seems about as solid as I've EVER experienced. Still laggy on playback when using some intensive FX applied (Neat Video, motion title graphics, etc), but this release is really a breath of fresh air and has me excited about editing again. I was really dreading rebuilding the projects I had done in Vegas over to Premiere Pro CS6 - which I believe I may finally be able to retire. My deepest gratitude and thanks to all the programmers who worked on this update! Random white flashes here too. It occurs independently of preview quality settings. "Magic bullet Look" and "Filmconvert" applied to track. all plugins and VGA driver are up to date. GTX 1080 Ti
-
Videoon 2/28/2018
VEGAS Pro 15 Update 3 (build 311) - General Discussion
Can somebody please explain to me what are the benefits of SO4 in comparison to old compoundplug? I see there is much trouble keeping that enabled. EDIT: BTW I am facing app crash while rendering for export again.
-
Videoon 2/26/2018
VEGAS Pro 15 Update 3 (build 311) - General Discussion
I was in the middle of a large project on build 261 with SO4 disabled. Lots of Panasonic and Canon footage. It crashed every hour or so but I was used to Ctrl+S every few minutes so I could live with that happily. But after updating to 311 no matter SO4 disabled or enabled, when I hit Ctrl+S and instantly continue to edit and moving events, everything from Preview to playback becomes too laggy and unusable. I found that it is related to Magic Bullet Looks plugin. when I disable the FX, the playback is normal again. I hadn't have this problem in 261. in 311 this occurs when hitting Ctr+S or importing a new footage to the timeline and will not come back to normal until I restart Vegas. Win10 latest Update - i7 7700k - 980GTX TI - 32G Ram - All footage on SSD
-
Videoon 11/22/2016
M2TS Sometimes Pixelation and Artifacts, Vegas Pro 14, Build 178
Yes Confirmed. the problem is solved in Build 201. Thanx to Community and Magix Team
-
Videoon 11/12/2016
M2TS Sometimes Pixelation and Artifacts, Vegas Pro 14, Build 178
Hi. I mostly see this flaw in rendered clips from Vegas and Aftereffects or downloaded from youtube. My GH4 and BMCC and 6D footages look good. I guess this is due to compressed and low bitrate footages that this build of vegas behaves differently.
-
Videoon 11/10/2016
M2TS Sometimes Pixelation and Artifacts, Vegas Pro 14, Build 178
A project finished in VP13 has good quality but in VP14 build 189 has this issue.both GPU acceleration ON and all same settings. all drivers updated. win10 rendered demo using vp13 : https://drive.google.com/open?id=0BxpdhyFfpxcFend6UzZGejRIRTA rendered demo using vp14 Build189 : (pay attention to the sky and ground) https://drive.google.com/open?id=0BxpdhyFfpxcFRm9vSkJsTkxTbFE I see the difference, but when I test this myself I'm unable to see any difference in picture quality, file size or properties at MediaInfo.Can you give us a screenshot of your rendertemplate in VP 14? As I said before, it doesn't relate to render settings because I have this issue in preview and trimmer windows while editing. here are 2 screenshots of vp13 and vp14 Build 189 workspace: EDIT : added screenshots
-
Videoon 11/9/2016
M2TS Sometimes Pixelation and Artifacts, Vegas Pro 14, Build 178
@hessam, @appv Are these interlaced or progressive h264 files? Can you link to a sample? @happy You don't have to debug the software. In fact, you (we) shouldn't - leave that to the pros! Support HAS to follow a fairly ridgid / methodical approach or they could never manage the backlog of service requests efficiently. This is normal for all software support departments. Progressive - H264 - mp4 A project finished in VP13 has good quality but in VP14 build 189 has this issue.both GPU acceleration ON and all same settings. all drivers updated. win10 rendered demo using vp13 : https://drive.google.com/open?id=0BxpdhyFfpxcFend6UzZGejRIRTA rendered demo using vp14 Build189 : (pay attention to the sky and ground) https://drive.google.com/open?id=0BxpdhyFfpxcFRm9vSkJsTkxTbFE
-
Videoon 11/9/2016
M2TS Sometimes Pixelation and Artifacts, Vegas Pro 14, Build 178
After long hours of testing different settings and conditions, as a long time vegas user I gave up and went back to latest build of VP13. and since vp13 doesnt open vp14 projects I had no choice but to start my project from scratch. Here are my findings: - most h264 mp4 files will have that block artifacts in vp14 (trimmer, preview, render) and it doesn't relate to preview quality setting. - It is most likely to have those artifacts when working on low bitrate h264 clips. - If the original low bitrate clip is re-encoded with Adobe Media Encoder to something like H264 / mp4 / 12Mbps then the vp14 build 189 will play the clip with no problem. - I had some crashes in vp14 build 189 while rendering and by disabling GPU Acceleration I could prevent that.
-
Videoon 11/8/2016
M2TS Sometimes Pixelation and Artifacts, Vegas Pro 14, Build 178
Sorry I was not clear. The file I shared earlier was the original unprocessed camera clip, in case someone wanted to try to render in Vegas Pro 13 and 14 and see for themselves the artifacts that result from Vegas Pro 14 processing. This is one of a number of clips used to compile a video. I started compiling with Vegas Pro 14 when I noticed the artifacts. Now I went back to Vegas Pro 13 to finish the project. Following your suggestion below two links to the clips rendered (same settings/no gpu) with Vegas Pro 13 and 14. The one rendered with Vegas Pro 14 shows artifacts after about 1 second in, as you can see for yourself, doesn't matter which media player... Sample Vegas Pro 13: https://drive.google.com/file/d/0B25cOGH1nL7mck9aak5JR1JNSFU/view?usp=sharing Sample Vegas Pro 14: https://drive.google.com/file/d/0B25cOGH1nL7meVNCc0RONFRyN1U/view?usp=sharing Hope all clear... Just tested your original clip in vegas 14 Build 189 with different settings. exact same problem. then compressed it in Adobe Media Encoder with different bitrate and h264 codec and mp4 container, then it showed up good in vegas strange
-
Videoon 11/8/2016
M2TS Sometimes Pixelation and Artifacts, Vegas Pro 14, Build 178
I have this problem too on build 189 with h264 clips. but with build 161 there was no problem. after testing with different settings I came up with this: - only some h264 clips will have this block artifacts problem in vegas (preview/render/trimmer...) - no matter what setting in vegas you have, the problem still there. - if I compress the original clip using Handbrake with highest setting : problem still there - if I compress the original clip using Adobe Media Encoder whit exact same settings as Handbrake : clips look good in vegas. - I uninstalled k-lite Codec Pack : no difference, problem still there. - I opened some previous complex projects that had been done in VP13 and they have thi sproblem in VP14 build 189. I guess somehow this problem relates to codecs used in build 189 ...
hessam
Offline, Last login 9/18/2021, Member since 11/8/2016