Automation (?) causes Virus TI to Crash DSP using Mavericks but not Windows 7

    Hi,
    My Virus TI has been working great until I purchased a new MBP running Mavericks 10.9.4.


    Upon setting up the new Mac I installed the latest 5.1.1 (2) update. I hadn't really used the Virus with the Mac previously. After the update everything seemed fine until I began to create complex patches with automation within Ableton 9.1.6 (both 32 & 64 bit). Within about 1 to 10 minutes the Virus would begin to emit an uninterrupted unpleasant pulse-wave sounding noise on all outputs - usb, audio and headphones. The odd numbered parts become unresponsive but even numbered parts continue to function and output audio together with the buzzing sound. Virus Control remains responsive. After shutting down the Virus the LFO LEDs remain on. I also encountered the problem of not being able to see my personal library and having constant synchronisation issues.


    I assumed that this problem was because of the update, so reverted back to 5.0.8. However the problem still occurs, with the added problem of occasionally encountering corrupted sounding (bit/sample rate reduced) audio via the USB, or losing audio altogether accompanied by a completely unresponsive TI unit (power cable has to be removed to reboot). I have tried different USB ports, cables, and also USB2 inputs of Thunderbolt Display, plus a USB Hub (not the Belkin), to no avail. I also run at 44.1 kHz.


    In contrast, the Virus TI with my original Windows 7 workstation continues to function more or less perfectly as far as I can tell, with no DSP crashes and great sound and synchronisation via USB. So it seems to me that this is (hopefully) not a Virus hardware problem.


    The crash seems to happen when I use the Formant Complex Oscillators, with the simultaneous automation of the F-Shift, F-Spread, Wavetable Index, combined with simultaneous automation of the Comb Filter Frequency. Using complex modulations and LFO's to control these parameters has ( I think - from memory) produced a crash but seems more stable than automation, though I have only done limited testing. It also appears to function fine when using MIDI control, but automation of the Filterbank and other parameters is complicated so I haven't fully tested that functionality either.


    Anyone ideas would be appreciated.


    Thanks
    P

    Zitat von Marc


    willbanks - in another post you write that cubase crashes for you. so what is actually crashing for you? the virus, cubase or both?


    When i am editing automation cubase crashes.(This only happens when editing automation for the Virus)
    Also, if the Virus is on when I start open a cubase project, the project freezes.
    Also, randomly sometimes the Virus VST will just freeze as it is attepting to open. It hangs saying 'starting up...'


    That's just 3 different ways it crashes. (also the arps don't work - they are all out of time. I have given up on every using the arps and now I use the BlueARP VST - which works perfectly.)


    I am using OSX 10.9.5, latest iMac, VIRUS OS 5.1.1, Cubase 7.5


    I have already emailed my Cubase crash report to support. It is the Virus MIDI server seems to have issues...


    Process: MIDIServer [2119]
    Path: /System/Library/Frameworks/CoreMIDI.framework/Versions/A/MIDIServer
    Identifier: MIDIServer
    Version: 89.3
    Code Type: X86-64 (Native)
    Parent Process: launchd [202]
    Responsible: MIDIServer [2119]
    User ID: 501


    PlugIn Path: /Library/Audio/MIDI Drivers/Virus TI MIDI Driver.plugin/Contents/MacOS/Virus TI MIDI Driver
    PlugIn Identifier: de.access-music.virusti.driver.midi
    PlugIn Version: 1.7.0.0 (1.7.0.0)


    Date/Time: 2015-05-19 20:25:13.768 +1000
    OS Version: Mac OS X 10.9.5 (13F1077)
    Report Version: 11
    Anonymous UUID: 59164062-98EC-66FE-B22E-6FB76FC404CA


    Crashed Thread: 0 Dispatch queue: com.apple.main-thread


    Exception Type: EXC_BREAKPOINT (SIGTRAP)
    Exception Codes: 0x0000000000000002, 0x0000000000000000


    Application Specific Information:
    *** CFRelease() called with NULL ***


    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
    0 com.apple.CoreFoundation 0x000000010de6f4c4 CFRelease + 724
    1 de.access-music.virusti.driver.midi 0x0000000114b8b45f 0x114b88000 + 13407
    2 de.access-music.virusti.driver.midi 0x0000000114b8bd8f 0x114b88000 + 15759
    3 de.access-music.virusti.driver.midi 0x0000000114b90a30 0x114b88000 + 35376
    4 de.access-music.virusti.driver.midi 0x0000000114b8d92b 0x114b88000 + 22827
    5 com.apple.framework.IOKit 0x000000010e1d8a1d IODispatchCalloutFromCFMessage + 160
    6 com.apple.CoreFoundation 0x000000010ded59c4 __CFMachPortPerform + 388
    7 com.apple.CoreFoundation 0x000000010ded5829 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__ + 41
    8 com.apple.CoreFoundation 0x000000010ded579e __CFRunLoopDoSource1 + 478
    9 com.apple.CoreFoundation 0x000000010dec67d6 __CFRunLoopRun + 1830
    10 com.apple.CoreFoundation 0x000000010dec5e75 CFRunLoopRunSpecific + 309
    11 com.apple.CoreFoundation 0x000000010df7b811 CFRunLoopRun + 97
    12 com.apple.audio.midi.CoreMIDI 0x000000010d62c02b MIDIServerRun + 794
    13 MIDIServer 0x000000010d614ed4 0x10d614000 + 3796
    14 libdyld.dylib 0x000000010e6a05fd start + 1

    Just wanted to revive this one because its similar to the hardware crash I recently had, but on Win7 with Ableton 9.5


    Never had it happen the same before or since (yet) and didn't get any dumps or anything, but the screen showed "Rom" in the wrong place, some random pixels lit up and while it received midi clock (lfo's synced and re-synced) wouldn't voice any notes. It required a total reboot of the system to get it to have full communication with the hardware again. That issue hasn't persisted but now it will crash the daw if I don't shut it down before closing the daw every time.



    Pretty odd, possibly from resetting/clearing automation after a patch is loaded making the hardware o/s lose track of where a bunch of parameters are suppose to be? That's the closest guess I have because it seems that I have a lot of weird disconnect issues when it runs through clips with many simultaneous parameter changes going clip to clip.