Forum Replies Created

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

    May 19, 2019 at 4:28 am

    MOV files are problematic with Vegas. I always convert them to MP4 using QWinFF and then edit.

    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 19, 2019 at 4:25 am

    If you want borders left and right that makes me think you should be working in 4:3 and not 16:9. You don’t want the wide screen template as suggested.

    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

    February 16, 2019 at 11:11 pm

    Perhaps a little bit off-topic but perhaps related, I had to install Quicktime 7.6.5 before Vegas would recognise any of my H.264 MP4 files, as counter-intuitive as it sounds. The Quicktime version number is important, no higher, no lower. Quicktime installs the necessary MP4 CODECs Vegas needs. Avoid using K-lite CODEC packs like the plague as they mes up Vegas.

    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

    February 16, 2019 at 11:00 pm

    I convert all my iPhone footage in bulk to MP4 using qwinff, which is 100% free and really easy to use. It is the only method that has worked for me.

    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

    December 19, 2018 at 9:28 pm

    [Bruce Brent] “A Canopus PCI card”

    I remember that hardware and software package but it was too expensive for me at the time, so I settled on the original windows movie maker (WMM) before Pinnacle Studio 8 which could render to DVD as WMM could not. I did my first major project in pinnacle studio 8 but after 100 hours of editing, it would not render. I tried Premiere but it constantly crashed. I then learned Vegas 9 and re-did the entire edit and it has never failed me since

    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

    December 19, 2018 at 1:09 pm

    [John Rofrano] “whole dark UI stuff but it’s definitely hostile to us older folks”

    LOL!

    [John Rofrano] “Coming from Vegas Pro 12 the UI will be a BIG shock!”

    I am only on 13 even though I upgraded to 15. The new UI is hard to get used to, plus I am just not seeing the preview benefits I was hoping for. The upgrade to an NVidia 1060 from a 570 has had zero benefit in any version of Vegas. Plus your excellent UltimateS Pro plugin does the job for me for my multicam editing in 13.

    I am dabbling in PowerDirector 16 for the movie club I run because it is inexpensive and powerful in features for what you pay for, and reminds me of Pinnacle Studio 8, which was my first editing program. Gosh…I am giving my age away by admitting to that!

    My system specs: Intel i7 7700k 4.20 GHz, GTX570, 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 23, 2018 at 11:17 pm

    Vegas loads the most recently edited project and audio peaks at start up. It can take 5 minutes for me with a 3 hour multicam project. I have noticed that DISK I/O, not CPU or memory, is the bottle neck. If you are editing in 4K, that could slow down the peak loading process. It would appear that detrimental code in Magix Vegas 16 was accidentally introduced or deliberately changed with the build 307. If this is not helpful, you should direct your question to the official Magix forum:

    https://www.vegascreativesoftware.info/us/vegas-pro-forum/

    My system specs: Intel i7 7700k 4.20 GHz, GTX570, 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

    June 6, 2018 at 1:02 pm

    [Dhanen Moteuchi] “GSpot scan of one of the files that SV doesn’t opens”

    According to your screengrab, even G-spot can’t even determine the codec, which is curious. You could attempt to convert the file using QWinFF into an MP4 format that Vegas should understand.

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

  • Nigel O’Neill

    June 6, 2018 at 12:54 pm

    [Dhanen Moteuchi] “I’ve tried with Quick Time 7.7.5 and didn’t worked neither”

    I didn’t say that. I said I had to roll back to Quicktime 7.6.5

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

  • Nigel O’Neill

    June 5, 2018 at 2:05 pm

    [manuel pimentel] “my head is about to explode, everything says I “Should” be able to play the file, but I Can’t, “

    When I had this problem using footage from an iPhone, I used QWinFF to convert my MOV files to MP4. They imported fine then into Vegas.

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

Viewing 11 - 20 of 1,171 posts

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