Forum Replies Created

Page 9 of 117
  • Nigel O’neill

    January 7, 2017 at 11:51 pm in reply to: Best approach for these camera problems?

    [Paul Gregory] “I had been trying to get it to connect to PC using USB again but it would not do so.”

    My experience with Sony cameras is that not all USB cables will work with them. I noticed some ‘connected’ the camera but the PC would not recognise it. I had to go through a few cables to find the one that worked and I labelled it. As for PMB or Play Memories Home, I have had no issues with either since I sorted out the cable problem.

    My system specs: Intel i7 970, GTX570, 12GB RAM, ASUS P6T, Vegas Pro 12 (x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

  • Nigel O’neill

    January 7, 2017 at 11:46 pm in reply to: Printer recommendation

    I use a Canon IP5300 and after printing about 500 discs I have noticed that the DVD tray mechanism is starting to struggle. I also print on Aqua Ace DVD’s, but the rollers leave marks. This happened on the 2 previous Canon’s as well, and would be interested to know if any other brands of printer DON’T do this.

    My system specs: Intel i7 970, GTX570, 12GB RAM, ASUS P6T, Vegas Pro 12 (x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

  • [Bruce Brent] “But, just this past month, I received an update from Nvidia and voila, I know have a working GPU with all its CUDA’s to handle faster renders. “

    Bruce, what Nvidia driver did you download and what version of Vegas are you running? It might be useful to know the pairing.

    My system specs: Intel i7 970, GTX570, 12GB RAM, ASUS P6T, Vegas Pro 12 (x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

  • Nigel O’neill

    November 28, 2016 at 9:58 pm in reply to: Damaged GoPro file won’t open in Vegas 12 or 13

    You could use Handbrake just to grab what you need i.e. cut and render out a section of video.

    I do recommend running MalwareByte’s AntiMalware afterwards. I did notice severe performance issues on my machine after installing Handbrake, like Handbrake would load or would not close after loading, PC became unresponsive, task manager would not run. Malwarebytes found some nasties lurking in my system and removed them. I still use handbrake without issues now. It might have been a huge coincidence or I had something pre-existing on my system already that really upset Handbrake. All other programs otherwise ran fine, including Vegas.

    My system specs: Intel i7 970, GTX570, 12GB RAM, ASUS P6T, Vegas Pro 12 (x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

  • [Craig Meeks] “Magix JUST bought it so everyone is going to have to give them some time to address issues”

    That sale occurred on May 20. If Magix doesn’t pull its finger out and so something really positive fast, it’s at high risk of disenchanting Vegas’ current user base. Once we are gone, we are gone.

    The reason why I have not purchased the v14 upgrade is that there has been no compelling reason to do so. For me, the greatest improvement was when Vegas when to V11. Since then it has been a bit *meh* in the version updates.

    Vegas has been stable for me since v8. I just avoid enabling the video acceleration features.

    I purchased a relatively high end CPU at the time, and performance has not been an issue for me, even if I do have a system I bought in 2009. The CPU has a passmark of 8488, which is still pretty competitive. If I want to breathe new life into my system, I’ll replace all the disks with SSD’s!

    My system specs: Intel i7 970, GTX570, 12GB RAM, ASUS P6T, Vegas Pro 12 (x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

  • Uninstalled the beta, installed 12.5.2. Updated some project preferences for default projects and then quit resolve. Then the fun began. Resolve would not restart and I could not kill it in task manager. Says it is looking for control surface. Everything else on my system jammed up. I could start Chrome, but it would not finish loading. Windows would not even shutdown properly. This has happened twice so far. It’s also spawning a lot of dpdecoder.exe processes. Looks like this is a known issue.

    I did get it up and running again, now need to figure out why it is not seeing m2t files but has no problems with m2ts. Probably have to ingest them or something.

    Just started Resolve again. It’s now hanging on loading media page.

    Not a very encouraging start.

    Given I am on Windows 7 x63 Ultimate, looks like I have no choice but to go to Windows 8.x or 10 to use Resolve. Resolve o installation said the OS was okay, but recommended Windows 8.1 Pro or higher. Pass.

    My system specs: Intel i7 970, GTX570, 12GB RAM, ASUS P6T, Vegas Pro 12 (x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

  • Nigel O’neill

    October 25, 2016 at 4:59 am in reply to: Vegas Pro 13 and UltimateS…

    If you reload Ultimate S from the menu, you should be able to redock it. I usually have Ultimate S as a shortcut icon amongst shortcuts the cuts and fades (as I use Quadcam a lot). I have noticed that if I minimise Vegas or switch to another app for a while, these icons disappear when Vegas is made the main app, but restarting Vegas reinstates them. They are still there because you can click on them, just the buttons are not visible. It’s a liveable quirk.

    My system specs: Intel i7 970, GTX570, 12GB RAM, ASUS P6T, Vegas Pro 12 (x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

  • I was using a 12 Beta! Checking it out now.

    I do use John Rofrano’s excellent Vasst Quadcam tool that comes with Ultimate S Pro 4.1 almost exclusively, so I will need a compelling reason to switch the Resolve. If Magix can get the video acceleration and rendering problems sorted in Vegas 14, I would upgrade. Right now, there’s no compelling reason to drop $250 for something I already have.

    My system specs: Intel i7 970, GTX570, 12GB RAM, ASUS P6T, Vegas Pro 12 (x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

  • I tried it briefly.

    Resolve would not recognise media I had previously used. It’s as though it could not see it anymore. I couldn’t figure out why.

    I also have two identical cameras. It sees the footage of one, not the other. Go figure.

    It does not support multicam, which is what I edit in mainly.

    I did look at Edius. There are certain things it labours over that Vegas does in an instant. Editor colleagues of mine don’t seem to have the crash-happy problems of Vegas. I really like its colour (white) balancing.

    My system specs: Intel i7 970, GTX570, 12GB RAM, ASUS P6T, Vegas Pro 12 (x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

  • Nigel O’neill

    October 10, 2016 at 12:34 pm in reply to: Latest build Vegas 14

    Yes, I have been patiently waiting since version 11 for the GPU acceleration to actually work stably. I diligently upgraded to 12 then 13, but nada. Until that is fixed, I have no compelling reason to cough up another $250+

    My system specs: Intel i7 970, GTX570, 12GB RAM, ASUS P6T, Vegas Pro 12 (x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

Page 9 of 117

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