![]() ![]() I obviously know that Mainstage comes with a number of patches but, must say, that I haven't been overly impressed with those that I've heard and used so far. I'm stuck as to whether Komplete 11 will be able to accommodate both these wishes. What I'm looking for is a whole host of new sounds to use alongside my current RD-800 keyboard and a DAW. I also have to create my own click tracks for various shows. I work in theatre, where Mainstage is now considered the 'norm' for live performance. At the time I continued to use my old set-up as I had quite a bit of work on and didn't really have the time, or money, to upgrade any further. I started upgrading my set up back in August when I (finally) bought a Mac and purchased Mainstage. I've been a PC/Cubase Studio 4/Dimension Pro user for nearly ten years. So my advice would be to look at how your preset on the MC8 is setup and maybe try to tweak the assignment of the scene change CC and see if that can remove some delay.So, I'm looking to upgrade my entire recording/live playing set-up and am looking for some advice. So depending on what you want to have happen you might want to assign an action to a press vs a release (or conversely a release vs a press because there is an order of operations for how actions get triggered, see a matrix here: Action Type List ) ![]() ![]() What I would ask is - what does the preset look like on the MC8? Are you using multiple actions? (press/release/long-press/double-tap) When you enable things like long-press and double tap that can add additional latency to messages you have attached to press/release actions - this is because the MC8 itself needs to “wait” to see if that initial press is a short one, or a long one, or if a second press is coming (for a double tap) - so there’s a small delay introduced so it can properly determine which action(s) should be triggered. My personal experience tracks with - EXP stuff can still be slow/laggy and seems to have a hard rate limit lower than what it should be (that has varied from release to release and I’ve made Neural aware of it) but scene/preset/whatever “general” messages - simple CC values are near enough to “instant” as to not be noticeable.Įven in a “heavy” preset, scene switching should always be near instant (within the QC) as once the preset is loaded everything stays running 100% of the time which is what allows scene switching to be so quick. I went over the programming on the Morningstar a million times, but it’s perfectly fine, set up exactly as the other scenes and the other scenes do trigger, just a bit delayed. I didn’t have any experience with the previous os, since I updated upon purchase, but it seems the issue for most started with the corOS 2.0? I also cannot get scene B to trigger. I’m really loving the Quad Cortex and don’t want to go back to anything else, but I need it to switch scenes instantly with midi, or else it’s useless to me. I’m also planning to use ableton cc’s for my solo shows, which was my method when I gigged with the Strymon Iridium and worked perfectly, but I read people are also having latency issues with Ableton/Cubase/Logic… Actually just all external midi triggering. I’m using the Morningstar MC8 with sensitivity set to 5 (so zero latency), yet when I switch the scenes on the Quad Cortex itself it goes immediately, however doing the same via the Morningstar it takes 100ms or more. Any updates on the midi latency issue? I’m reading a lot of fellow users with this issue. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |