Forum Replies Created

Page 1 of 2
  • Thanks for linking me to this bill.. it helps to commiserate. I too and am doing this on the side… however with a 7 month old and a full time job… every deadline is too close… but I work hard and get things done and, IMHO the end products come out great for how long I’ve been doing this (5 months, though I’ve been doing pro audio and photography work for years and am very technically inclined).

    Where are you setting your ram levels higher? Also, I love the notion of turning off gpu acceleration unless you’re rendering, i’ll try that.

    I have 16 GB’s of Ram and I’ve had the ‘shift-b’ ram preview just stop on or just after a BASIC transition for some reason, and not finish the full selection I made. What are your thoughts on what could be causing that.

    I have so many ‘workaround’ with vegas, it’s annoying. What’s funny is that I had SVP10 working on my older audio computer fine, I invested in this new computer and software, etc.. and i’m wasting time left and right with all this. ugh.

  • Thanks for linking me to this bill.. it helps to commiserate. I too and am doing this on the side… however with a 7 month old and a full time job… every deadline is too close… but I work hard and get things done and, IMHO the end products come out great for how long I’ve been doing this (5 months, though I’ve been doing pro audio and photography work for years and am very technically inclined).

    Where are you setting your ram levels higher? Also, I love the notion of turning off gpu acceleration unless you’re rendering, i’ll try that.

    I have 16 GB’s of Ram and I’ve had the ‘shift-b’ ram preview just stop on or just after a BASIC transition for some reason, and not finish the full selection I made. What are your thoughts on what could be causing that.

    I have so many ‘workaround’ with vegas, it’s annoying. What’s funny is that I had SVP10 working on my older audio computer fine (but with longer rendering times), I invested in this new computer and SVP11 to speed everything up… now.. i have LONG editing time (due to crashes) and shorter rendering times. I’ve gained nothing but debt and frustation.

    SVP really needs to fix all this as a powerful NLE is only as good as it’s weakest link.. and for SVP11 and NB, there are MANY weak links it seems.

  • Shaun Laframboise

    April 4, 2012 at 12:04 am in reply to: New Blue Titler Pro + Sony Vegas 11 = Crash

    glad that’s working for you.. my issue seems to be different, it crashes once I’m in newblue.

  • Shaun Laframboise

    March 31, 2012 at 3:26 pm in reply to: New Blue Titler Pro + Sony Vegas 11 = Crash

    I have one going at Newblue, but the help is sporadic and hasn’t gotten me anywhere.

    I’m posting here in case anyone has met a similar issue and found a remedy.

  • Shaun Laframboise

    March 30, 2012 at 8:22 pm in reply to: New Blue Titler Pro + Sony Vegas 11 = Crash

    Build 120208

    I’m losing my mind with this. It’s SOOOOOOOO finicky! I build this computer around what Vegas and NewBlue suggest and it doesn’t work. So frigging frustrating. I have minimal time to work on editing and I spend it opening and closing programs that cost hundreds of dollars… getting NOWHERE.

    First I returned my RAM, and got other RAM, that seemed to help, but now… I don’t think it did. I open Newblue and can do what I want, but once I click on library… it freezes vegas and i have to shut the program down.

    Please someone tell me there’s a dumb fix to this i’m missing… i’m truly losing my gord.

    ugh.

  • Shaun Laframboise

    March 21, 2012 at 4:25 pm in reply to: New Blue Titler Pro + Sony Vegas 11 = Crash

    I have the newest version of all of them, the only one I’m not 100% sure on is the NewBlue as I couldn’t figure out how to find out the build number of the one I have, however I did just download it from the site 2 weeks ago, so unless there was a recent release in that time, I have the newest build.

    Any other ideas? It’s SUCH a great tool, I’d love to poke around it in more and learn about it, but it crashes if I’m in there for more than 3-4 minutes!

  • Shaun Laframboise

    March 21, 2012 at 3:46 am in reply to: New Blue Titler Pro + Sony Vegas 11 = Crash

    So I found it to be the RAM in my system. This is a new build and I had to take out the expensive faster RAM, and put in the regular RAM, both G.SKill, but the CAS 9 latency ram works, the CAS 7… no go.

    Still though, I’m getting some issues where it kills vegas if I poke around in there too much. So I make quick edits, close the fx box, save the entire session and go back into newblue fx box… its’ REALLY annoying…

    anyone have any ideas on what makes vegas and newblue so buggy and how to fix it!

  • Shaun Laframboise

    March 20, 2012 at 1:31 pm in reply to: Vegas 11 + Multicam editing = Crash

    So I heard from Sony about the two monitors thing, this is their reply:

    Thank you for writing back. One of our leads on the Vegas team let me know that they haven’t specifically tested it, but for the shipping version of Vegas it shouldn’t any difference whether you have two displays on one GPU, or two GPUs and two displays. This could change with future versions as we use the GPU for more and different work (it will be better to use the same GPU for processing and display).

    If you have multiple GPUs we show each in the Preferences > Video tab; you can pick which one to use for video processing.

    As for using Vegas on two monitors, it’s possible to do now if you stretch the window across both displays. The windows can always all be arranged, and then saved in View > Window Layouts for future use.

    If you still have a follow-up question on this particular incident, please feel free to update it. If you have a completely different question, please create a new incident.

    ________________________
    So it’s probably not the two monitors on one card thing, but I’ll continue to play around with that just in case.

    HOWEVER, the RAM switch I did def. fixed a number of issues. I’m still getting NewBlue crashing on me, causing Vegas to go down with it. But at least I can render and edit now, including multicam, so it seems like that was that was the majority of my issue.

    Now… another thread for NewBlue. sigh

  • Shaun Laframboise

    March 17, 2012 at 2:17 pm in reply to: Vegas 11 + Multicam editing = Crash

    Hey Jim!!!

    I remembered you got the corsair… the Ram I got was the cas 7 high end, so I think it just didn’t like my rig. I already bought the regular ram (cas 9) of G.skill as I hadn’t heard about what you mention.. if I get any errors, I’ll def. get corsair..

    Also, not sure about setting the dynamic ram preview to 0. I’ll have to get my hands in there and find that setting and see if it does anything. Thanks!!! 🙂

  • Shaun Laframboise

    March 16, 2012 at 5:04 pm in reply to: Vegas 11 + Multicam editing = Crash

    It’s def. not thermal, temps are super low, nothing is even firing at more than 50% when I’m working/editing or rendering.

    I think I found the issue though.

    RAM.

    I spent twice the money on Cas 7 g.skill ram which caused issues from the start, but I thought I though I had those issues fixed with a bio tweak of dialing in the ram cas settings, something I don’t think you have to do with standard cas 8 or cas 9 Ram…

    anyway.. my unit is now awaiting the replacement RAM that’s to arrive today. Going to install it and run RAM Test and see what it finds.

    I agree on the two monitors on one card thing… i think it’s totally fine to do that, in fact I read on ‘videoguys’ website that Sony was one of the few programs optimized TO run two monitors off one dual port video card… of course… that ‘optimization’ could be buggy… but who the hell knows.. i’m asking sony and still no reply…

    will keep y’all posted.

Page 1 of 2

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