Who's Who - Professional Pianists on Piano World Member Recordings - Non Classical Pianist CornerĮVENTS! Piano Concerts, Recitals, Competitions.įun Stuff! - Parties, Tours, Projects & More.įorum Members Parties, Tours, Cruises, & M. MY NEW PIANO or KEYBOARD! - Share Your Story! Thanks for the help everyone! As well as the welcomes :-)ĭigital Pianos - Electronic Pianos - Synths &a. Question is, how much more latency should there be on a SL88 compared to a cheaper NI launchkey?
TL DR: I run SSD and the difference in latency is very noticable from the SL88 to my other keyboards/pads. That being said if it is then I am either really sensitive on latency (I don't think I am), or the product is simply poorly/unfortunately design (which I would not expect based on reviews). Although it is like you're saying, for all I know this may be the way the piano is designed. I have the feeling that there is something wrong, and to the best of my knowledge through testing I believe it to be the piano. I do run 3 SSDs and 2 HDDs on the system, whereas the DAW and the VSTs are running on SSDs as well as the operating system (windows). It is playable when not recording, although playing anything other than chords and easy pieces is far from enjoyable almost to the point of more stressing. I have been playing on several real instruments ranging from old pump organs to pianoes (of various sorts), and I've never experienced anything like playing on this one.
And it did as expected have an effect, although it's still far away from how fluent playing on the other controllers is. Honestly that is a very good question, I did play with the velocity curves. Where are you seeing buffer of 32? That is an uber-low latency and I don't think anyone here got their piano VIs to run so rapidly. What size buffers and sample rate are you using with the Focusrite? Have you tried this option?Īre you running latest Focusrite Clarett drivers? I would guess the last option (MIDI DIN to Focusrite) "could" be the most efficient (not running both USB & Thunderbolt computer). SL88>MIDI DIN>Focusrite> Computer (Studio One 4 & VI)>TB>Focusrite >Monitors? SL88>USB>Computer (Studio One 4 & VI)>TB>Focusrite>Monitors NEW- Now are you running StudioLogic SL88 with USB & DIN MIDI: LaunchKey>USB>Computer (Studio One 4 & VI)>TB>Focusrite>Monitors? OLD -You had a Novation Launchkey with USB MIDI only and were running: Are you only using that only as DA converter and preamp to your monitors/headphones? INTERFACE - The Focusrite Clarett 2 Pre Thunderbolt interface seems to only have DIN MIDI in (No USB MIDI in). Sorry, I don't fully understand your post. īoth the USB and the MIDI performs about the same (1 ms difference) UPDATE: I've tested both the midi and the usb and they seem to have similar timings, so that if there is something wrong, atleast both are damaged.
TL DR: Anyone else having latency issues with SL88? Running a short buffer (anywhere from 32-128), 3.2 GHz 4 core i5 3570, 32 GB of ram on Studio One 4 with a thunderbolt Clarette 2 Pre. There should be no problems with the system, as the latency on launchkey and launchpad (tested on the same usb) is next to zero.
Is this common as a transition from keyboard to hybrid piano (keybed) solution? I would think not, but I'm no expert. I can't help but notice that there is a problematic latency, especially apparent when trying to play with a metronome or on a beat. It has a great feel to it, and the 3 censor arrangement is very welcome for piano Virtual Instruments. Enable the 'Do not allow any sites to use system exclusive messages to access MIDI devices' option.I recently upgraded to a SL88 from my Launchkey (much needed). Enable the 'Do not allow any sites to use system exclusive messages to access MIDI devices' option.I have re-created your issue here, but under some very specific circumstances which I would like to check with you: are you running Google Chrome?ģ.
Locate the 'MIDI devices full control' section.ģ. In chrome navigate to 'Settings > Advanced Settings > Content Settings'.Ģ. If this is the case, please do the following:ġ. Turns out that the default setting in Chrome is to access whichever MIDI port is available! Here is solution from Softube: "I have re-created your issue here, but under some very specific circumstances which I would like to check with you: are you running Google Chrome? Okay there is one configuration that can cause this issue unfortunately it's not mine.