Forum Replies Created

Viewing 1 - 10 of 1,171 posts
  • Nigel O’Neill

    August 31, 2021 at 1:32 pm

    I tried upscaling my video for no real improvement, but I suspect the plugins are like snake oil salesmen 🙂

    I have heard of some TV’s that can upscale and ‘clean up’ SD video but there’s no way to export the video.

  • Nigel O’Neill

    August 31, 2021 at 1:25 pm

    Turns out an update to SVP18 had clobbered the Ultimate S Pro 4.1 Plugin, and as John Rofrano is no longer maintaining it, I had to recreate the project in SVP15 by copying the markers and timelines and reapplying FX, colour grading. Rendered fine in multicam after that.

  • Nigel O’Neill

    August 1, 2021 at 10:31 am

    I used Catalyst browse to transcode to mxf, avc-L, avc-i, AVCHD, and I ran into the same issue everytime that camera footage is referenced in the export/render stage.

    The only thing I can think of is the Ultimate S Pro 4.1 plugin I am using for multicam is not compatible with Vegas Pro 18, but I have never ever seen anything like this before. Usually converting the footage fixes it, but not this time. I am stumped.

  • Nigel O’Neill

    July 24, 2021 at 12:46 pm

    I did some digging and did a MediaInfo on the files where it was hitting a slowdown and it uses a CODEC called isom (iso4/avc1/isom) with a writing library of Quicktime. The MP4 file came off a BlackMagic ATEM ISO Pro live capture, so it looks like a CODEC used by BlackMagic, but I have no idea of how to get Vegas to process it better it during renders. As soon as it hits the cut to the camera using this CODEC, the CPU drops to 13% at less than <1 fps, but as soon as it hits an MXF file in the camera cuts in Vegas, it jumps back up to 60% and 30+ fps.

    I don’t want to have to edit this project in DaVinci Resolve nor wait 25 days for a render. I do have DaVinci Resolve Studio legitimately installed on my system and I was still learning it, but it doesn’t seem to help, other than Vegas does understand the file and was able to ingest it.

  • Nigel O’Neill

    July 24, 2021 at 10:13 am

    I disabled Smart Resample which had no effect whatsoever.

  • Nigel O’Neill

    June 4, 2021 at 3:36 am

    After copying the required DLL as per the above, the Toolbar icon has to be re-added through menu: Options > Customise Toolbar, the look for PluralEys 4 then click on Add. Works in Vegas Pro 18 too

  • Nigel O’Neill

    June 2, 2020 at 1:59 pm

    Your rig is fairly decent if you were still editing SD or 1080 files back in 2011 using Vegas 11. Adding RAM may help. You don’t mention if you are using an SSD, or what source of video you are editing. H264 and H265 can slow down Vegas, particularly in a multicam edit, on older rigs.

    You might want to consider a whole system replacement, but if that is not an option, replacing your mechanical with an SSD breathes new life into an aging system.

    Your O/S is most likely Windows 7 which is no longer supported or getting security updates.

    I replaced my 2009 vintage i7 laptop in Jan 2020 with a Lenovo IdeaPad S145 and what a difference it has made. Reinstalling software was a pain but a worthwhile one ☺

    If you are getting a laptop, note that not all models have the same specs! Check the specs! For the ‘saving’ of $100 you often get short changed with a smaller or lower res screen, slower CPU or lower capacity SSD. My Lenovo was a classic case and luckily I noticed the subtle differences.

    My system specs: Intel i7 7700k 4.20 GHz, GTX1060, 16GB RAM, Gigabye Z170 HD3, Vegas Pro 13 (x64), Windows 10 x64 Pro, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, VASST Infiniticam 1.7, Neat Video Pro 2.6

  • Nigel O’Neill

    November 20, 2019 at 10:28 pm

    Hence why I use Vasst Ultimate S 4.1 Quadcam…which preserves event level FX

    My system specs: Intel i7 7700k 4.20 GHz, GTX1060, 16GB RAM, Gigabye Z170 HD3, Vegas Pro 13 (x64), Windows 10 x64 Pro, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, VASST Infiniticam 1.7, Neat Video Pro 2.6

  • Nigel O’Neill

    May 26, 2019 at 12:19 am

    [Cindy Hberg] “Or, I may switch to Premiere.”

    Just be aware of Premiere’s ransomware subscription model. If you don’t pay, it doesn’t play i.e. if your subscription lapses, you cannot access your projects. Baulk away ☺

    DaVinci Resolve is free but has a steep learning curve. It does require a reasonably high end video card.

    Be aware that Premiere can be quite finicky when it comes to ingesting media, much moreso than Vegas. Vegas ingest most media well. That’s my experience with Premiere anyway.

    When my current Windows editing system dies, I am switching to FCP!

    My system specs: Intel i7 7700k 4.20 GHz, GTX1060, 16GB RAM, Gigabye Z170 HD3, Vegas Pro 13 (x64), Windows 10 x64 Pro, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, VASST Infiniticam 1.7, Neat Video Pro 2.6

  • Nigel O’Neill

    May 21, 2019 at 1:25 pm

    OK let me clarify. Final Cut Pro and iMovie natively edit MOV like a hot knife thru butter. I have had numerous issues with MOV files and the advice I was given by a Cow leader was to convert them to MP4, be it Sony, DJI drone footage or iPhone footage in MOV.

    It’s possible that I am getting source footage from particular devices that Vegas doesn’t like. It’s mainly Sony and DJI files I have had problems with. I can’t comment on Canon files as no one has given me footage shot off a Canon yet! Perhaps it’s my Vegas version which is still on 13 because of the plugins I have and still use.

    I been in situations where I have placed multiple MOV clips on the timeline and started editing them, only for them to suddenly become unviewable.

    As soon as I convert them from MOV to MP4, my timeline issues disappear.

    My system specs: Intel i7 7700k 4.20 GHz, GTX1060, 16GB RAM, Gigabye Z170 HD3, Vegas Pro 13 (x64), Windows 10 x64 Pro, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, VASST Infiniticam 1.7, Neat Video Pro 2.6

Viewing 1 - 10 of 1,171 posts

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy