That’s a good call on running the Snow firmware and what I’ll likely do myself. I don’t need huge voice counts. If I can get 2-3 instances with maybe 10-12 voices in total, I’m completely happy. I don’t have any problem with rendering to audio if needed.
Just having this period I’m willing to make whatever sacrifice or compromise that’s needed. I’m still mind blown it even exists.
my main issue so far seems to be with 3rd (4th?) party skins tbh. All of which pretty much seem to crash it!
not noticed any CPU issues (yet) but quite limited experience so far.
Windoze though so maybe not relevant anyway.
That’s weird, I’m using the Virus TI for OsTIrus skin (I fear change!) and it’s working without any major issues outside of the amp/filter envelope graphic displays not working… which isn’t a big deal for me.
For what it’s worth, I’m using the plug-in in conjunction with a Polar Ti 2 and it’s really amazing what they’ve pulled off here. Outside of a couple of little issues (no random patch generation as far as I can tell, some knobs display incorrect parameters when twiddled) it’s really quite remarkable. Feels like the best of both worlds now - I can use the Polar standalone when I want to, but I get all the convenience of running it as a proper, fully software plug-in when using a DAW with the added bonus of having a lovely controller that works pretty much 1:1 with it.
I’m on it - thanks!
I’ve been testing for them for some time.
I’m on a 2019 MacBook Pro, with the 8 core Intel CPU. 6 instances are very stable at 256 sample buffer size, 48kHz on Ableton 12.
What was really hitting me, was my insistance in trying to use an aggregate audio device. That had been working for me for some time, but OsTirus was much more susceptible to CPU spikes using that than other plugins.
So, I’m now exclusively using my A&H QU24 in the studio and it’s running great. Only downside, is the hard-limit of 48kHz.
The main feature I could really use, but isn’t there yet, is - being able to switch patches using program change messages. That would be ideal for my Ableton live sets.
I’ve been low-key adoring the OsTIrus emulator, however…
It worked like butter on my Macbook Air 2020 8gb RAM, but since upgrading to a Macbook Pro 2021 16gb RAM it now crackles like a mofo. Just having it loaded onto a track makes all audio on the MBP crackle, including YouTube. The CPU meter in Live is barely breaking a sweat though. And I can only load the VST3 version - the AU version don’t show up in Live’s browser. Tried the Snow emulation as well, still the same. Accepted the security prompts for both versions.
I’ve scanned through the poists on here and can’t see anything to suggest M1 Pro is incapable of running OsTIrus vs the base M1. Any suggestions would be greatly appreciated!
Edit: got it working on the M1 Pro without issue - my Live buffer size was 32. It still crackles on 64, even does it a bit on 128. But it’s smooth on 256. That’s too high a buffer speed for my liking but it’s acceptable if I can use OsTIrus to sample from.
If you can, and maybe you already are, try using it in the ‘Ti Snow’ mode, which has less DSP and, thus, lower CPU. That might help you use a lower buffer size, but 32 or 64 will probably be rough on most systems. I imagine it’ll get better in time with newer CPU’s and possibly improvements to their DSP emulation.
Everyone is different, but for me, I’ll never need the number of parts and polyphony the full version can provide. I’m just using one or two parts, usually rendering to audio.
Can I use this emulator as a patch manager for my Virus Ti?
Only in the sense that you could load up soundbanks (likely more easily and faster) to preview and edit them. There’s no transfer functionality to send patches directly to the hardware or manage them remotely though.
ok, that is what i found. Anyway, I’m using VirusCenterControl and it seems that I can upload some banks…maybe that’s enough for now. Thanks!
Thank you! Somehow I had a buffer of 32 working on the MacBook Air and I just got used to it. More than happy to sit between 128/256 for a software Virus. 
Kinda! You can make patches on it, then send those patches to the Virus, you’d need to just grab the patches from the OsTIrus folders and SysEx it over to the Virus hardware.
Is it just me, or is it really hard to send patches you made with Ostirus to the actual Virus?
Is Sysex the only way? The Browser makes it feel like you should just be able to save them into the Patches folder and open them, but this seems impossible?
Probablty “Read the Manual” I guess?
ok, someone explained the new browser function to me, but when I export the user banks, they look blank in the Access plug in. Weird.
Anyone using ableton figure out a way to save the Ostirus preset in saved clips?
paralely while trying to solve this problem, im talso considering to give up hardware and replace it with Ostirus vst. Ostirus has no synchronisation problem, it really works fine, BUT, its program change options is useless since it affects only ROM banks which are factory sounds and which are not possible to rewrite. Or am I wrong?
So, ive tried also with chains option in ableton in a way to automatically trig (on/of) particular chain for which you need multiple instances of Ostirus loaded in your project. Chain option usually works for me when I use multiple mastering fx chain for each track in live project, but with Ostirus it is not stable: each on/off gives high cpu spikes causing glitches and cracks, and event worst, disrupts Ostirus in a way that it losses the saved sound and load the default one. Is this last said related to Ostirus, and some of its potential bugs? Ive tried the latest beta version, and also the official one - it is the same. Im on Apple M2 Pro, Ventura Any thougtht on how to automatically trigger custom patches on the Ostirus within Ableton?
Trouble shooting may be better directed to the emulators discord server.
You can find a link to it on the emulator website
You can report bugs there too
Strictly speaking, you’re meant to own the hardware to legitimately use the ROMs on the emulator.
thanks for reply. I have hardware, and use its firmware.bin, but anyways, all banks shown in ROM banks are factory one, there is no possibility to load custom sounds in ROM
Yeah, allowing the emulator to modify the ROM is a legal no-no so I’m not sure how they could work around that. That said, you aren’t the first person to bring this up and, if their Discord is anything to go by, it’s something they’re aware of.
On a semi-related note… looks like they just dropped a public beta of Nodal Red 
the question for would probably be how to program change custom banks, and avoid the question the ROM modification. Any max4live experts here? Could it be possible to make max4live device which could either (1) trig program change from destination other than ROM or (2) somehow record/flash current patch from Ostirus and recall it when needed?
