-
Videoon 5/12/2020
bonus. Get a free BCC title studio and more music, audio effects.
I signed up for this - it's worth doing it for the full version of BCC Title Studio for free (or a donation to charity). The only word of warning is that it is for the current version of BCC Title Studio - you will not be able to keep any older Boris plugins you may have as the installer will overwrite them with the current Continuum versions which your licences may not support. As I have FXHome Ignite (and the stock Vegas plugins) to cover my effects and don't use other older Continuum products I used to have much (if at all), I was happy to go ahead and just get Title Studio, but it's just worth knowing before you go ahead!
-
Offtopicon 4/14/2020
Grazie and Corvid19
Sorry to hear you've been hit with Covid Grazie... And glad to hear that you're recovering! Thank goodness for the NHS! Wishing you speedy recovery Grazie 🙂
-
Videoon 10/2/2019
[BUG] VP17 Warp Flow transition crash with GPU acceleration
Seems fine on my Radeon RX570 system too with GPU enabled. Perhaps it's specific to Radeon HD series cards?
-
Audioon 9/5/2019
How to delete background PC/UPS fans from a voice track?
If you can afford it I'd get iZotope RX (even the basic Elements edition would be fine) as it has a very useful Voice Denoiser VST plugin that works a treat in VP17. To completely remove the fan without cutting things like sighs might be tricky though as these are likely falling into the same noise floor as the fan (although if they're significantly louder you might be able to gate out the fan with a very fast gate). If you've got room reverb in there that you need to get rid off you might need a higher version of iZotope RX (not elements) to get de-reverb or if you have access to Adobe Audition that can do it (or Accusonics ERA plugins but they are very expensive for the average user). Audacity can do some things for denoising too, but is offline and destructive editing - using iZotope RX would be non-destructive if you wanted to change anything. Oh and there is a denoiser in Resolve (Free) in the Fairlight page if you have that?
-
Videoon 8/26/2019
Happy Otter Scripts for Vegas Pro
@AVsupport I too, the HOS creator, received a warning from Windows Defender for a 1.0.2.60 download that I had done awhile back just a couple of days ago. Running the original file through the virus scan showed clean. Apparently, some update to either Win 10 or Defender led to that update as containing suspected "malware". Googling the suspected malware showed quite a few threads about false positives. The only major change in 1.0.2.60 was the new FrameServer from Satish, plus updates from Rigaya (for QSV and Nvenc) and VirtualDub. There were no new app updates in 1.0.2.61. HOS seems particular vulnerable since all of these are "unsigned". Additionally, all updates are stored on DropBox which often leads Windows to block such downloads unless they are "unblocked". I don't think there's a problem, but If you're worried just delete it. I would be interested if anyone else is having such problems since this is potentially a showstopper. Just tried to download 1.0.2.61 and Windows Defender keeps blocking it as having "Trojan:Win32/Zpevdo.B" embedded. Not sure whether to proceed and allow it through as I trust @wwaag to have not put in anything dodgy (and I did have a previous version in VP16 - thanks for the awesome tools!), but it's relatively easy to insert code on download servers I believe...
-
Videoon 8/23/2019
Vegas Pro HDR Creations
Just watched the Mobile Bay trailer... Looks absolutely stunning in HDR on my Samsung S10e's AMOLED panel. Awesome cinematography too! Well done @fr0sty! Thanks for sharing it.
-
Videoon 8/14/2019
Crash Report
I've had problems with Bezier masking tracking in VP17 recently with similar crashes. It seemed limited to when I created custom masks and tracked ~5 minute clips (tried h264 original clip and a transcoded cineform version to eliminate the possibility that it was related to heavily compressed codecs). The tracking would proceed fine then crash VP17 at 100% tracked without saving the tracking data. For very short clips or for other mask types (oval, rectangle and diamond even on the long clip) it was fine. It's never restarted my PC though. After messing about a lot I found that I could get a successful tracked mask if I increased the keyframe slider so it was only creating a point every couple of seconds - not ideal, but it was fine for what I needed. I wonder whether it's a memory thing? I could see my GPU being utilised for the tracking (in task manager) but it would still crash even if I disabled the GPU. In either case I didn't seem to be getting anywhere near either my GPU memory (4GB of Radeon RX570) or my system RAM (16GB of DDR4 3000MHz), but as reducing down the number of keyframes tracked seems to work and reducing the complexity of the tracker (from custom Bezier to simple shape) it makes me think there may be a memory issue, and if it's crashing your whole machine that could point in that direction too but it's pure speculation on my part! I have put in a ticket to Magix support with my issue, so I'll update here if anything comes of that. I've not tried the slow-mo plugin yet so I can't comment as to whether that works on my system...
-
Videoon 7/31/2019
Advice on specs please
@jrb101 FYI, In Vegas timeline accel. = Open CL; never been CUDA. Was a time long past where Mainconcept encoder used CUDA. No longer. V17 may add other timeline GPU accel. but very much doubt that will include CUDA as it's ancient. CUDA isn't ancient - it's at v10.1 at the moment (2019 release) but I'll concede that using actual CUDA cores for video encoding like Mainconcept used to is a ancient technology - it's now done by NVENC on a specific chip on NVidia cards... But this is all way off-topic so I'm going to stop here and point back to the original question: @Jack S - do you have a budget in mind for an upgrade?
-
Videoon 7/31/2019
Advice on specs please
I thought NVENC is for encoding, CUDA is for computing. So, for timeline acceleration Cuda or OpenCL is necessary. Am I wrong here? That's right. @j-v - yep NVENC (AMD's VCE) is used for encoding, but I'm fairly certain that any timeline playback acceleration would be handled by CUDA (or OpenCL) as it is in Resolve or Premiere Pro. I wasn't referring to CUDA encoding as you're right that NVENC has replaced this function.
-
Videoon 7/31/2019
Advice on specs please
If it's just 1080p without plans to go to 4K you won't need anything outrageous. For 1080p, my Ryzen 2200G (with 16GB RAM and an AMD Radeon RX570) handles things fine. That said, once you start adding a load of grades and/or effects it can slow down... Something more Ryzen 5 or recent Intel i5 should be more than adequate to keep 1080p smooth with effects or grades added I would think (although others may correct me on this). @j-v and @Dexcon are both right about making a decision based on the particular version - 15 and 16 can use GPU acceleration for rendering out a video and the various reveals for 17 suggest that it will have GPU timeline playback acceleration but until it's released we won't know if it favours NVidia (CUDA and OpenCL) or AMD (OpenCL only) I guess! To be fair, you could probably keep your existing system and upgrade the RAM to 16GB, upgrade the graphics card to an Nvidia 10xx series or Radeon RX5xx (70 or above) or Radeon VEGA (56 or 64) and put in an SSD (if you're not already using one) and see some good performance with the more recent Vegas Pro versions - you'd get NVENC encoding with the Nvidia for H264 (AVC) and H265 (HVEC) or AMD-VCE encoding with the Radeons for the same codecs. In VP17 this would hopefully extend to timeline acceleration on both cards but if Magix have implemented CUDA timeline acceleration only then it would be NVidia exclusive. Having gone through all that - what is your budget as that will determine what is ideal for you?
-
Videoon 7/27/2019
Vegas Pro 16 + 17 upgrade offer
@OndrejPopp @vkmast @Marco. Hi guys. I am one of the VEGAS developers. The moderators do a great job. Please do not take everything so seriously and help each other. This forum is mainly maintained by experienced users (moderators) and we all should help new users to improve their way of working with VEGAS. That's why we're all here. We all love VEGAS and want to design it (with new ideas) into our VEGAS. It is absolutely right that the developers follow this forum very closely and we are in a good email contact with the moderators. Some of you (like @jrb101) may have noticed that we take the wishes of you very seriously and try to deliver them in one of the next updates or releases. Some facts: Gary Rebholz is the product owner (no developer) of the VEGAS group and is reading all your posts/emails and is the connection between your wishes and the Magix marketing team in Germany (and the "German bosses") VEGAS is not only developed in Madison. Sebastian and I work in Berlin (Germany) and you can meet our small team at Facebook. This month you can find some facts about Blake. He is really cool and he is led the development of the Screen Capturing feature (released in Movie Studio Platinum update) we are not allowed to comment VP17 or VEGAS POST yet but VP17 has the longest feature list VEGAS has ever seen we (developers, product owner, tester, marketing team, Magix family and the "German bosses" 😉) are very excited about the release date to show you all the new stuff Thanks @VEGASPascal - I did notice that my wishlist seemed to be answered! I'm pleased I took a bet on 16+17 before knowing what features would be in it... Thanks for keeping up the development of Vegas Pro - despite the other options around I can still edit way faster in Vegas Pro as it fits my way of thinking!
-
Videoon 7/26/2019
Vegas Pro 16 + 17 upgrade offer
Just watched the preview... Not the slickest presentation, but showed 2 things that I regularly switch to Resolve and Premiere Pro for (Resolve-like colour grading workflow) and easy switching nested projects. And mentioned something that I use fairly regularly in my YouTube talking head videos - Warp-Flow transitions (assuming that the same as the Warp Cut or Smooth Flow of Premiere and Resolve respectively). I'm sold. Assuming it all works well enough (probably after the first bug fix release!) I'll happily ditch my Creative Cloud sub and free up some space on my disks by deleting Resolve. I'm by no means a power-user or professional editor, but for hobbyists like myself I think the Vegas developers may have nailed it - add an FXHome-powered Vegas Post and I think Vegas Creative Software are very much back in the game!
-
Videoon 5/29/2019
Help Grazie spend his dosh!
Update...Update . .. Update. Your feedback on the following PC is most welcome: 1] 650W Corsair RMx Fully Modular RM650X ATX PSU/Power Supply 2] Corsair Hydro Series H100x 240mm Radiator, Dual 120mm PWM Fans, Liquid CPU Coo 3] Intel Core i9 9820X s2066, 16.5 MB CACHE, 10Core/20Thread, 4.1GHz 4] Samsung 860 PRO 512GB 2.5” SATA SSD/Solid State Drive 5] Corsair 64GB Vengeance LPX DDR4 2666MHz RAM/Memory Kit 4x 16GB 6] ASUS NVIDIA GeForce RTX 2070 8GB TURBO EVO Turing Graphics Card Nice setup - but that PSU seems low wattage for the rest of the specs... Looking at https://outervision.com/power-supply-calculator you're likely to be in the region of ~600-620W power draw if you're pushing the parts regularly (which is kind of what video editing does!). For the PSU you typically want to run at ~80% load or lower for maximum efficiency, so maybe you might want to consider upping it to a 750-1000W PSU - it'll give you some scope for upgrading GPUs (or running multiple GPUs) at a later date. All said though, the 650W will power it, so you can get away with that!
-
Videoon 5/28/2019
Video experiment
Awesome video and great playing! - and I agree with @Musicvid that just a light compression on the guitar part will level things out nicely for a smoother presentation. At 2:1 it shouldn't destroy the dynamics though, so they'll still be in there, and the limiter at broadcast standards should just level it off at a consistent "full" volume (whilst retaining the dynamics in the playing). Stylistically, you may also want to EQ the nature sounds and guitar parts around each other (e.g. slightly cut the nature sounds in the frequency range of the guitar) so the guitar comes through with a little more clarity, but it's by no means wrong as it is, and as I say it would just be my stylistic choice (and we're all different in our music!) that said, the way you have it currently it all folds together which may actually be more suitable for relaxation sounds... so perhaps ignore that last comment! 😂 What's the pedal? Sounds like a compressor (for those long tails) and a subtle chorus, tremolo or uni-vibe type effect for the modulation...
-
Videoon 5/28/2019
MAGIX Video Pro X vs. MAGIX Vegas Pro
I've used both VPX8+10 and Vegas Pro 15+16 (amongst other NLEs too)... They perform a similar role, but some of the differences I can think of off the top of my head (in no particular order): There is no obvious way to re-order effects in VPX - if you want to change the order it's a case of deleting all of the effects on a clip and putting them back in the way you now want them. Vegas allows easy re-ordering VPX generates background proxies for faster playback perfectly with no user intervention necessary (although you can tweak various settings if you want). VPX runs with an internal 16-bit colour (as of the most recent versions) vs selectable 8-bit or 32-bit in Vegas Vegas allows FX to be applied at the clip, track or master level, VPX is only at clip level as far as I remember (but it does have a couple of "Master FX" for output colour-correction etc.) Both NLEs use OFX, but vendors have to "enable" use of the OFX package in a given NLE - they do this for Vegas as a matter of course, but some don't for VPX! VPX tends to be more GUI-based for things like FX, Colour-Grading etc. (i.e. drag-and-drop interface, tweaking FX on the preview etc.) where Vegas often has input boxes for things (although there are plenty of examples of GUI-based things in Vegas and textbox entry in VPX) Vegas makes better use of AMD graphics hardware (for acceleration and decode/encode etc.), for NVidia and Intel I think both are pretty similar. VPX tends to need less user intervention to make things "work", i.e. no random so4compoundplug-type issues - but like all NLEs it has various bugs (just look at the Magix.info forum for them) There are more "presets" in VPX for text effects, motion effects and transition effects, but if you're not into presets and are happy creating your own then that's a bit of a moot point! Tracks in VPX a multi-purpose and make no distinction between type - however, if a video with audio is dropped onto the timeline the default is to make a single track with both the video and audio (this can be switched to creating a video track and a separate audio track in the preferences) Neither NLE separates the video and audio into separate V1, V2, V3 and A1, A2, A3 etc. tracks above and below a virtual centreline as is the case with Resolve, Premiere Pro, Avid Media Composer etc. - they both put an audio track next to the video that contains the audio (assuming the default behaviour has been set to separate video and audio tracks in VPX!) In terms of core functionality, they're both about the same overall (as are most NLEs) with the ability to cut, stabilise video, perform tracking (as of Vegas 16...), colour correct and grade, do basic compositing (although I think Vegas has a slight edge here) and render out video. Neither has optical flow for fancier retiming or morph-cut/smooth-cut style transitions though, which is slightly frustrating as when it's used properly it looks great! As others have said though - they're both a bit overkill for first-time editors and not cheap! And picking up on a point of using one NLE from starting out to professional use, (don't flame me for saying this) they may want to look at something like Avid Media Composer, Premiere Pro or Davinci Resolve if they intend to work at a studio etc. as these are more "standard" - it's irrelevant if the user is intending to be an independent film maker as then you can use whatever you want! Basically all "pro" level NLEs will get the job done and it's just personal choice as to which "feels" right to the user. Obviously, this is just my opinion and I'm happy to be corrected on any of the points above! 😉
-
Videoon 5/23/2019
Vegas 17 Feature Requests
+1 for any kind of Optical Flow retiming (I'm aware that HOS has implemented this, but it would be nice to be native) I'd also like to see a similar transition to the Premiere Pro "Morph Cut" / Resolve "Smooth Cut" that uses Optical Flow to smoothly transition between 2 clips - it's ideal for avoiding jump cuts when doing youtube talking head stuff (or I could just get better at not fluffing my lines, going off-topic etc. ;-) ) Another +1 for some updated lower thirds, titles motion graphics etc. - I know I could craft my own (and I do), but it's nice to have some presets for fast-turnaround or even as a basis to customise. Vegas is super fast to cut with, but does fall short in some areas in comparison to the "big" alternatives, so it would be nice to see some of their toys (e.g. optical flow) implemented and then it would be the only NLE I'd need to consider using. Third-party plugins go some way to fixing this, but more native stuff would be good so I don't need to buy more stuff.
-
Videoon 11/5/2018
Color Grading in Resolve, from a Vegas edit
OK - so it actually didn't pass through the grades! I'd just shot the original well enough that when I corrected it, the correction was so subtle that I didn't notice the difference in Resolve due to slight differences in the in-built view windows of Vegas and Resolve... I'll go and be suitably embarrassed now 😂.
-
Videoon 11/5/2018
Color Grading in Resolve, from a Vegas edit
@jrb101 Thanks. PS Sorry, one more question: which Vegas color grading effects carried through? I'm not at my computer right now, but I think it was the basic color corrector plugin (really I should have used the term colour correction rather than colour grading as that implies significant changes rather than just "tuning up" footage!) I'll check when I get the opportunity and let you know the full details.
-
Videoon 11/5/2018
Color Grading in Resolve, from a Vegas edit
@zdogg There is a link in this article: https://www.moviestudiozen.com/free-tutorials/sony-vegas-pro/592-render-cineform-video-from-vegas-pro-movie-studio#a5 @jrb101 Did you use Vegas' export XML for Davinci? What media types did you use (test)? I found Vegas won't pick up the clip timecode from my GH5 MP4 files but will read it from cineform files exported from Resolve. Another niggling problem for me is how to handle animated stills, but this is really a Resolve issue rather than a Vegas export issue. The clips were h264/AVC files in a mov container, from my Olympus PEN EPL6, and Cineform in an AVI container. I did use the Final Cut/Resolve XML export option. Strangely enough, the h264 files were fine in Resolve, but I had to manually resync the Cineform files (they had Alpha channels though, so maybe that confused Resolve?) And that is also exactly where I got the Cineform codec from 😂.
-
Videoon 11/5/2018
Color Grading in Resolve, from a Vegas edit
How are you folks getting your Cineform codec, are you installing Go Pro? Cineform shows up in my render options, but if I try to use it it says it is not to be found....thanks in advance people. Yeah - I installed the older GoPro Studio on my system to get Cineform. Works a treat!
-
Videoon 11/5/2018
Color Grading in Resolve, from a Vegas edit
I actually did this process recently, and found the trickiest bit was getting Resolve to conform the clips due to Resolve's weird limitation on "Project" framerate (makes sense in a distribution context, but not so much if you're not working on Film/TV projects). The things that worked well: All cuts were maintained Timeline positioning was good for all clips Colour correction from Vegas Pro was actually maintained on import to Resolve (for further grading) Vegas-Specific video transitions were replaced by crossfades to maintain accurate timeline edits Things that didn't work so well: Stereo audio was split to dual mono and panned to centre (not unexpected, but slightly annoying - see next point!) Left and right audio channels were slightly out of sync (but there seems to be some issues with Resolve's audio system at the moment...) Audio crossfades were not replicated properly in Resolve - Fairlight is good, but still not up to Vegas' native audio engine... Some video assets were missing/offline and had to be manually relinked to imported assets (but Resolve did have frame-accurate placeholders for the missing assets, so it was easy enough to relink) In the end, I got so fed up of the audio import issues that I rendered the audio as a wave file in Vegas and replaced the Resolve timeline audio with the rendered version. That worked great (until export, where there were some sync issues, but that is a problem in Resolve I've encountered before and nothing to do with Vegas Pro!) Kinvemark is spot on with his comments and suggestions though - if you can flatten things before export to Resolve and then reslice for the sections you want graded, that would probably be the easiest way to do it, and would maintain timeline consistency (and AV sync) throughout!
-
Videoon 11/1/2018
Vegas Pro 16 and Windows 10
vkmast wrote on 10/31/2018, 3:13 AM:Many of us use Windows 10 successfully. But then there are others. I am not trying to stir the pot. My experience, via free upgrade to Win 10 from 7, had me turning back in horror (there is a return to Win 7 built in, did not work so great, ended up fresh re-installing Win 7 which is always a good thing to do anyway after a couple of years or so)..As with everything in software lately, it pretends to be more "user friendly." Really more 'locked down' (as it makes decisions 'for you) so adjustments and tweaks one might usually make became really convoluted, even changes for your monitor running on two or three screens became a convoluted nightmare, at least for me. Partially, yes, unfamiliar territory, but almost nothing is instantly accessible, WYSIWYG, the operating system is "protecting itself" from too stupid (we might assume?) users, there is the now expected (with all software, phones so forth) intrusiveness, asking for this information, all the cloud tie ins, it is just too oppressively invasive, and that is just my initial take, but it had me RUNNING back. I absolutely hated Win 10..Tell me what I might be missing, if anything, or how I might have gotten it wrong. The biggest thing you are missing is a current fully supported product from Microsoft 😉 On a serious note, Windows 7 is now in the "Extended Support" cycle, rather than mainstream support, therefore only security updates are provided, and support for new products (e.g. new processor architectures, new graphics card architectures etc.) is not available from Microsoft and you're at the mercy of the manufacture to offer support - which they might not officially (e.g. AMD Ryzen). Yes, Windows 10 has some "quirks", but overall it's a more stable (and in a lot of cases faster) system these days.
-
Videoon 10/30/2018
VEGAS Pro 16 Update 2 (build 307) - General Discussion
So, how how do you create a subclip? What does it mean? Just had to look this up myself in the manual - page 142! You can create a subclip by either viewing the media clip in the trimmer window and selecting in and out points, then click on the "Create Subclip" button in the trimmer window and give it a name in the subclip dialog box OR You cut the video on the timeline, then right-click on the portion you've cut to your needs and select "Create Subclip" from the context menu. I never knew about this before and it looks like it could be a real time-saver with the stabilizer!
-
Videoon 10/30/2018
VEGAS Pro 16 Update 2 (build 307) - General Discussion
So far with Vegas 16 (365 ed), since update 261 and also 307 I've been enjoying buttery smooth timeline playback (using so4compound and GPU acceleration on!) and no crashes that weren't the fault of a 3rd-party plugin. I'm actually really impressed with Vegas Pro now, and after toying with going back and forth between Vegas and Davinci Resolve 15, I think I might settle on using Vegas for the vast majority of my projects. Well done Vegas Pro developers - you're doing a great job pushing forward on the product and trying to squash any bugs that get reported! Lots of people seem to hate on Vegas for being buggy or crashing a lot, but I've found it to be just as stable as other NLEs when set correctly - just look at the forums for Premiere Pro, or Resolve and see how many issues they have too - the main issue is that it's not always obvious what the "right" settings are for anyone's particular setup (e.g. so4compoundplug seems to cause a lot of issues in however it's decoding AVC for a lot of people) I don't know if there is a "Suggestions"/"Feature Requests" post that I could add to, but if there is I'd like to add a couple of requests as there are a couple of features in Resolve that I do miss in Vegas (but not enough to push me away from it): 1) Native optical flow retiming/resampling - it's not perfect and can lead to odd artefacts, but it is a really useful method in other NLEs 2) A version of "Morph Cut" (PPro), "Flow" (FCPX) or "Smooth Cut" (DVR) transition, which is reliant on optical flow to create new frames (and face-tracking in the case of PPro's Morph Cut) - it's a reasonably specialised requirement, but I say "errr" and "ummm" lots in my videos and using this kind of transition means I can cut all of these out and have a nice smooth talking-face/vlog video without a million jump cuts! 3) Planar tracking, corner pinning and "track backwards/track forwards" for the tracking module (unless I'm missing the options) - the new tracker is great and I hope it continues to get developed further. Overall I'm really impressed with how far Vegas has come in the last couple of years and where it seems to be going.
jrb101
Offline, Last login 1/18/2021, Member since 8/2/2018