ochikubo

Thanks, for doing it. With both Trillian and Keyscape having the sounds in the patch browser is super helpful - the name is exactly descriptive of the sound. Omnisphere doesn't seem like it would make as much sense since there are so many sounds with very creative names.

Thanks! Working good - looks like for the ones I loaded they are all working. Also, some fun music on your website!

looks like it was on his drop box account and it has moved ...

Great job! Thanx for sharing! Replying to an old thread, is this preset database for Keyscape still available. The link is not working when I try it (links to an old dropbox location).

You might need to load a midi driver for the midi interface. I have two m-audio midi interfaces and one requires a driver and the other does not for some reason. But they look the same.

I have been using this setup and it has been stable for me. So far I have only been operating it in a rehearsal and haven't done any gigging out with it. In order for me to have a stable setup, I have pretty much moved all of the bread and butter sounds (pianos, etc) to my Kronos X and then am just using MainStage to provide secondary sounds and lead sounds.

Just completed the backup and install. Still getting the smaller CPU spikes when not playing anything, where CPU usage goes from about 3% and jumps to 25%. But I haven't seen the really big 1000% CPU spikes so far. Going to let it run for a while and see if they come up. Not too clear from the release notes what the other stability issues they fixed might be.

The macbook pro that I am using has 16 gig of memory in it, so memory is not tight. Looking at both the MainStage memory monitor or the activity monitor utility it sits around 5.5 gig of memory used (stays constant). But I do notice that the spikes occur after some time, and so that might point to a memory leak or something else going on. Read a lot online the Samsung SSD's and TRIM. Main issue I read is regarding benefit of TRIM on the write side performance on drives at a high level of utilization. The drive sits at about 75% utilization so their is still a fair bit of space available. And looking at activity monitor, for the concert I have had running (with all the patches in it), it is 20 Mbytes of writes versus about 4 Gbytes of reads. Did go ahead and do a backup and then enabled TRIM since it is supported natively on El Capitan, waiting to see if the problem comes up. Also, read some online regarding kernel_task spiking for El Capitan CPU requirements, but I am not seeing any of that here. On a side note, did take a listen to the Ravenscroft and Pianoteq pianos online demos. They sound good, First time checking out Ravenscroft and it has been quite a while since I last took a look at Pianoteq, and that sounds a lot better than what I remember.

The nice thing with mainstage is the CPU Load history gives you visibility on the processing taken by each individual plug in. So I can see Ivory relative to other instruments and effects. And that is where I see Ivory spiking up and other instruments not. I have made a very simple concert with only Ivory in it and it doesn't have the problem - so definitely interaction. I am starting to go through and exporting different combinations of sets/patches and see if it possible to isolate the offending interaction. One thing I do notice is that the native instruments are very stable and efficient in the latest version 3.2.3 of mainstage. The latency issue also seems to have gone. Just nothing in the native instruments has the quality of Ivory.

I have tried it, but didn't attempt to record as my computer ran out of CPU cycles, just cause MainStage takes a lot of CPU and glitches every now and then. What I ended up doing was just moving the few patches that I needed over to logic and then recorded MIDI in logic while playing the patches live.

I have spent some time trying to isolate where some of the peak loading is happening in my setup when using MainStage. The one AU plugin that I have seem to consistently have issues is with Ivory (AU 2.1.3b138 x64 Coa). With a program that has Arturia MiniV, Silververb, EXS24, Channel EQ, Chorus, and Ivory. Watching the CPU Load History (while running in performance mode), it will idle around 4 to 6 percent, with an occasional spike around 15%. Every couple of minutes it will have a VERY big CPU spike over 1000%. The CPU spike can be attributed fully to Ivory. Not clear on how to eliminate this. I have tried reinstalling Ivory, but it continues to happen. Mainstage 3.2.3 Using some modest audio settings (512 I/O buffer size and 44.1 kHz sampling) MacBook Pro (13-inch, mid-2012) 2.9 GHz Intel Core i7 16 GB RAM OSX 10.1..13 WiFi is OFF Samsung 250 Gbyte SSD (with about 50 Gbytes free) MOTU Ultralite Mk3 Hybrid (using FW) MOTU Microlite (for MIDI) Using built in Logic AU plug-ins, u-he Diva (very heavy CPU load), Synthogy Ivory (very "spiky" CPU load), Arturia MiniMoog (medium heavy CPU load).

An alternative approach would be to make a copy of the entire Patch ( with all the desired mappings) then replace everything you "don't need" in the new patch. CCT That is a good approach, but you still end up where you can mix and match tracks. The channel strips work great for saving the sounds and then combining them in different combinations. But just haven't found a way other than manually to copy over the controller mappings.

I have multiple patches in my set that use different mappings of external controllers (MIDI Fighter Twister or keyboard foot controller) to control specific parameters in the patch. A good example, is having some physical knob on the Fighter Twister controlling a pedalboard pedal parameter (like the distortion pedal knobs). I would like to copy that pedalboard to another patch, including the external controller mappings. I can currently setup a present and just take the pedalboard and put it on another patch, but I then need to go through one knob at a time and recreate the mappings (including the behavior when the patch changes, stored value, etc.). A very tedious process. The mappings are not universal to the entire concert, so I don't want to set it up at that level, it would just be for a particular set of patches.

I recently tried using MidiPipe (http://www.subtlesoft.square7.net/MidiPipe.html) a small utility that "highjacks" your MIDI port so you can grab the data and so some processing on it. In my case I have been using it to remap an old DX7 velocity curve to one that has the full 127 levels of velocity, and also to filter the output of a DJTechTools Midi Fighter Twister. For working in Logic, I have the ability to create something in the environment that will do everything I need to do (and more). For performing live with MainStage, it is not so easy (DX velocity remapping is easy), but the filtering on the Midi Fighter Twister is not so easy (at least not at a global level). I have seen MidiPipe mentioned a few times on various threads, but are people finding that this is reliable for live performance and touring around where I don't want to be messing with debugging a configuration in between gigs? It definitely has the feeling of hacking into things, when it is running the midi screen in Audio MIDI Setup doesn't reflect things correctly. I am running the latest versions of Logic and MainStage, on Yosemite, on a Mac Pro (mid 2012) and Mac Book Pro (2012), with a MOTU ultralite interface. Craig

Has anyone done the presets for the arturia minimoog v2?