It's probably because this old man "grew up" in the one function per "brick" era. If An uncluttered solution is avialable I always go for that. Nobody seems to have an opinion about my processor load reduction question so I gues I'll have to find out the hard way (sigh)! :-) VCV Rack also has some physical modelling modules. It's a brilliant tool but sounds nothing at all like Kaivo.ĪAS Chromaphone is a physical modelling percussive synth that works in stand alone mode, again nothing at all like Kaivo. UVI Falcon works standalone, is multi channel audio & midi. A lot can be done with those basic building blocks. It also sounds like you might want to have multiple instances running, so a mixer will be useful.īitwig's grid is very, very capable. Having the ability to freeze tracks can help with performance. A large portion of my workflow is also only using synths, and I don't see it as overkill at all, but a necessary prerequisite of using VST's. I do however still only use the DAW for synthesis purposes so that seems overkill and a waste of valuable processor power to me"ĭAW's are optimized to host VST's. "So run Kaivo in Bitwig Studio then, you will say. It sounds to me like sticking with Bitwig will be the most straightforward solution for you, especially as you already own it. I don't think Mainstage is officially supported on Windows(?). The laptop's audio output will then be “dumped” on a stand alone audio workstation so no extra number crunching is needed for that. Otherwise running 8 mono instances or so and driving them via individual MIDI channels will do the trick. An 8 voice Kaivo instance would however already suit me VERY well, especially if poly AT can be used to control / scrub the sample position per note in real time. It's a 64 bits, Windows 10, 8MB with an Intel 8th gen i-3 core. My laptop is a reasonable machine but not high spec. Which at last brings me to my question: Do you have any idea how Kaivo will run within Main Stage 3 on a Windows laptop? For me such a program was after all the missing link at the time. I do however still only use the DAW for synthesis purposes so that seems overkill and a waste of valuable processor power to me. So run Kaivo in Bitwig Studio then, you will say. In that respect Kaivo still comes closer to my ideal. It works really well but it only provides regular building blocks like delays, comb filters and such. Then I bought Bitwig Studio 3 because one can build his own instruments in its Grid modular synth. In the mean time I tried Tasty Chip's GR1 which at least seemed to tick all the granular boxes within a hardware solution but it's software tuned out to be a bit of pile up (to put it mildly!). I have also been able to reproduce the same issue using a switch type sustain pedal in my Yamaha S80 controller and also using my Analog Factory MIDI contoller.Īny comments or assistance would be greatly appreciated.Remember me? I bought Kaivo some years ago but never got it to run because I did not yet use a DAW at the time. I have tried deleting and adding the sustain pedal in my Mainstage layout. I am using the latest version of Mainstage from the app store and the latest version of OSX Lion. I have tried uninstalling and reinstalling Mainstage. Note that I have no problem with full continuous control of the sustain pedal in standalone mode and in Logic - only in Mainstage. If I switch pianos in Pianoteq, the problem disappears only to reappear when I switch Mainstage patches and then return to the Pianoteq patch. Every time I switch a patch in Mainstage and then switch back to my Pianoteq patch, the notes are cutoff and will only sustain with the pedal depressed. Recently, I have developed a problem using my sustain pedal (Roland RPU-3) controlling Pianoteq in Mainstage. I have used Mainstage on my 2009 MacBook Pro for several years driving Pianoteq as my main piano instrument.
0 Comments
Leave a Reply. |