Vienna Symphonic Library Forum
Forum Statistics

200,697 users have contributed to 43,206 threads and 259,116 posts.

In the past 24 hours, we have 1 new thread(s), 7 new post(s) and 68 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro (legacy)
  4. R.I.P Vienna Ensemble

  • R.I.P Vienna Ensemble

    S
    S
    I love VE and I love VSL... so I hate saying this... but I am completely done using VE unless someone can solve this...
    I load my template, it crashes anywhere between 5-6GB of ram, I load VE, then add individual tracks and VI-P instances... and I get to around 7GB and crash.
    I get only one error, and only some of the time...
    "The Instruction at 0xff9cb349 referenced memory at 0x00000130. The memory could not be read. Click okay to terminate the program"
    I love VE and I LOVE VSL so I hate saying this... but I simply can't use it anymore. I wanted VEP, but unless this is fixed... I can't plan on getting that either... I don't realy have the money for VEP right now anyway, but I doubt it would change anything. I'm just tired of troubleshooting and constant crashing, now not even being able to use VE at all. Any help would be appreciated... otherwise I'm completely lost!
    -Sean
  • W
    W
    Hi Sean,

    are you on MAC or PC?

    I gladly share my experience,if you use MAC,because I NEVER have problem with VSL products

    or maybe you should contact support directly,to get a specific answer from the VSL expert.

    Please do not quit VSL product.Its the best in the market, I've used it and never look back. best, Willy
  • S
    S

    Oh, I'm not quitting VSL - I LOVE vsl and that isn't changing. I just can't use VE regularly... I can try loading my template 50 times and I'm lucky to get it loaded once. It's very frustrating. I'm using a PC and the rest of the specs are in my signature...

    I will have to use Cubase in the meantime to load VI Pro instances... I can't spend my time working this out... but hopefully with newer versions of VE I won't have to deal with it and trust me... then I would switch back to VE instantly. I prefer VE for many reasons. Ultimately I'll want VE Pro, but with these problems I can't committ to VE right now.

    Because Intel is supported by MIR and the fast amount of people on here seem to practically worship Intel, and because a few other applications are Mac only... I have decided to get a Mac Pro, but that is down the line... way down I'm afraid as I'm poor, but then I will be happy to use VE all the time.

    -Sean
  • W
    W
    last edited
    last edited

    @iscorefilm said:

    will have to use Cubase in the meantime to load VI Pro instances

    Aah,that is why I never have problems,because I use only Cubase for MIDI and ProTools for my audio. I Quit PC since XP Pro 64 and never try again , forcing myself to buy secondhand MAC intel,that was worthy the efford!!.

    I haven't got MIR yet,because my MAC will not be able to handle those "RAM eater Programs" incl MIR and Hollywoodstrings willy
  • N
    N

    By chance, have you run any memory tests?  Could it be that you have a stick of memory that has gone bad, and that the issue is not related at all to VSL?
  • S
    S

    Yes, I intended to include that in my post and forgot. I have run a couple software tests (can't remember as I deleted them) and I ran a Windows test where it reboots and scans without Windows loaded. All showed no errors.

    I found another website that mentioned the error I provided (but with different code numbers) and it mentioned disabling an Internet Explorer active-x memory function that is meant to be secure. I did this and no change. I deleted the cache files for VI and VI-Pro, nothing. I'm still willing to try any ideas, I just can't spend time trying to figure it out on my own at this point. So any insightful comments I welcome completely, thus I posted it (and for some feedback).

    Thanks,

    Sean
  • G
    G
    I would still suspect a defective ram stick. I've had numerous times when all ram tests wouldn't report issues but it still turned out to be bad ram. Try leaving only 8 GB of ram and changing ram sticks one by one until, hopefully you spot the one causing the crash.
  • M
    M

    Sean,

    please send a message to support@vsl.co.at and put "To Martin" in the subject line. I will help you to investigate this issue.
  • M
    M

     Sean,

    Tech support will help you get it sorted out. These kinds of things errors are usually fixable.
  • BillB
    BillB

     That's a very generic Windows error, and unlikely to have anything to do with bad RAM.

    Dorico, Notion, Sibelius, StudioOne, Cubase, Staffpad VE Pro, Synchon, VI, Kontakt Win11 x64, 64GB RAM, Focusrite Scarlett 18i20, August Forster 190