Posts by ChrisCabbage

    Update: I've actually got reasonable-ish results in Cubase 10.5.11, using the external outputs, but timing isn't completely consistent and there's a fair bit of timing jitter.

    Here's what I'm having to do:

    Plug-in set up with analogue outputs, into one of my RME Mulitfaces.

    Live mode on the plug-in checked. This is the crucial bit! ...and you'll need to check it every session, since it doesn't get remembered.

    Virus set up as an External Instrument in Cubase (you'll have to check the guides on how to do that).

    MIDI channel sending to plug-in (e.g. 01. Virus TI - Midi In).

    To test, I have a group channel, with the External Instrument instance routed into it. Then an audio channel, with input as the group channel. I then record the audio on that channel and check the start timing. I'm using an Init patch, with Osc Phase Init set to 1.

    It's not straight-forward, but it's kind-of useable. Hope that helps!

    According to several posts by Marc , MIDI should work fine, which means you'd only have to get Audio back in via your RME Interface.

    There's another thread where sombody asked whether that would work. It would be nice if you could try and post back.

    MIDI works without the plug-in. ...but if you’re using the plugin, then the DAW tries to apply PDC to the round-trip of MIDI event to incoming audio. That can mostly be removed by hitting the Live button on the plug-in GUI, but I still can’t get it right going that route.

    I don’t think it’s possible to send MIDI to Virus “Synth”, whilst running the plug-in. If I’m wrong, please someone let me know!

    I’ve already commented on one other post, do you have a link? I might have missed it.

    For info, I've now moved to Catalina. VirusTi plug-in is obviously not working, but I'm going to continue with the Mystery Islands editor until and unless Access get things going.

    If Access want me to try new drivers, just let me know.

    Since I tested on a separate partition, I had a fair bit of confidence that all of my software and hardware otherwise works OK. Obviously, the 32 bit software is broken, but I have Parallels running Mojave and Windows 10 for most of that.

    Again incorrect. Your audio interface should tell the DAW how much latency the driver and A/D have. Some interfaces have inaccurate drives, but then you use the recording offset in the DAW which all DAWs have. Do a loopback test to find out if the interface is reporting incorrect latency.

    If you have a MOTU interface it definitely will be, their drivers are way off.

    I don't think you're understanding the issue. My audio interfaces (RME Multifaces) work fine and I use multiple external synths - very low latency and spot-on timing.

    When the Virus TI plug-in is running, PDC applies and there's latency, which is compensated for by PDC.

    When the plug-in is running, you can't send MIDI direct to the Virus, it can only go through the plug-in.

    "Beta" Software in general has the meaning that you shouldn't use it in your productive environment, unless you're prepared to lose large parts of your work due to software errors (e.g. erasing your main drive because of a wrongly parsed preset file name), often have to update your working environment, and probably lose settings between versions. Good enough for hobbyists. Not good enough for professionals with a tight schedule and fixed deadlines.

    Again - no guarantees that non-beta software won't do that. E.g. I could introduce you to people who lost data on Akai's current MPC systems due to bugs on official non-beta software. I'd recommend never ever trusting any software, or even hardware platforms (e.g. disk controller firmware) to not corrupt or remove your data - that includes operating systems. Always have a backup strategy,

    40+ years of programming and software engineering under my belt (yes - I'm that old). Like I say - being out of beta is no guarantee of being bug free, even in terms of losing data.

    If only it were that simple!

    Ploytec, the company who's audio code makes the Virus plug-in work, are working on a Core Audio driver, to replace the depreciated HAL audio code. I'd keep an eye on this webpage LINK as when they have their own driver it'll be there, I can't imagine that the Virus driver will be far behind. Unless it's never going to be updated of course. Who knows? Well, Access do but it's still radio silence...

    Elektron also use the Ploytec base drivers for Overbridge. Overbridge 2 has now been working on Catalina for weeks. Not saying it’s straightforward, but someone’s done the initial spade-work.

    All, I’m thinking about dipping my toes into writing a MIDI editor for several synths (including Virus Ti).

    Any tips for starting points? I’m mainly Mac and Xcode. Resources for widgets for dials and sliders...? Useful libraries? Open source examples...?


    I was considering buying another Ti as backup / insurance against future problems.

    Do we know if the Ti is still being made? Stocks seem low at the various distributers.

    I think there were suggestions that the DSP devices may start to be in short supply soon too...?

    I'm still on a Mojave host, but have just tried setting up a Mojave VM under Parallels.

    Seems to work and could be the future solution for me. G2 editor also works.

    Still, it's not heartening to see that support has stopped for this application.

    For what it's worth, Cubase does do some things differently to other DAWS.

    MIDI on my 3 Hammerfall Multifaces has an issue. Ableton allows me to use the MIDI ports properly, but Cubase gets confused between system reboots as to which port is which and I have to manually re-assign the ports.

    When I queried this with Steinberg, they told me that Cubase doesn't support MacOS aggregate audio devices. Aggregation, is the only mechanism I have for combining the 3 Multifaces. It's supported in Ableton, but not Cubase.