Customizable delay / latency
Search the forum before posting your idea.
No explicit, hateful, or hurtful language. Nothing illegal.
No explicit, hateful, or hurtful language. Nothing illegal.
My keyboard doesn.t have a proper MIDI input, rather it.s usb...
And there seems to be a few 100's of milisconds latency. (I.ve got to hit the notes slightly before they are lined up perfectly).
A manual latency variable would be nice; but an automatic delay adujstment (a bit like a popular music video game...) would be awesomer.
Thanks!
And there seems to be a few 100's of milisconds latency. (I.ve got to hit the notes slightly before they are lined up perfectly).
A manual latency variable would be nice; but an automatic delay adujstment (a bit like a popular music video game...) would be awesomer.
Thanks!
1) Hadn.t tought of proprietary drivers
2) It happens more when I.m at slower speeds than 100%. So maybe there.s something in the 'slowing down' method at playhere...
Oh and, I.m extremely picky here; the 'delay' I.m talking is probably no more than 150-200ms... so .. yeah, not that critical
2) It happens more when I.m at slower speeds than 100%. So maybe there.s something in the 'slowing down' method at playhere...
Oh and, I.m extremely picky here; the 'delay' I.m talking is probably no more than 150-200ms... so .. yeah, not that critical
Which kind of device are you playing Synthesia on? PC, Mac, Android, or iPad? Usually keyboards are very fast (say, less than 5ms latency) so it might be something else. Android is super terrible most of the time for audio (and input and video output and every other kind of) latency, so it might not be your keyboard's fault.djbono wrote:And there seems to be a few 100's of milisconds latency.
Thanks for the reply,
I'm using the PC version on a fairly recent Dell (quadcore, 16gb or RAM, win7.)
Again, I can.t press enough the fact that I,m being very picky here. It.s not a 'big deal' though it does cause the song to stop sometimes before I hit the note when I feel like it's right to press.
Most of the time I can manage to press a tad earlier
I'm using the PC version on a fairly recent Dell (quadcore, 16gb or RAM, win7.)
Again, I can.t press enough the fact that I,m being very picky here. It.s not a 'big deal' though it does cause the song to stop sometimes before I hit the note when I feel like it's right to press.
Most of the time I can manage to press a tad earlier
Well, as an output device I use my Keyboard, but for the mapper, yes I guess then it's windows's.
I"ll try to switch
Thanks for the info
(but just so we're 100% clear - It's not really slow nor buggy at all, just it feels like there.s a 100-150ms delay on the input).
Then again the delay must be also there since I use the same keyboard as the output... weird.
Maybe its just in my head
I"ll try to switch
Thanks for the info
(but just so we're 100% clear - It's not really slow nor buggy at all, just it feels like there.s a 100-150ms delay on the input).
Then again the delay must be also there since I use the same keyboard as the output... weird.
Maybe its just in my head
Ok so yeah, 100ms is probably way too much , in reality its closer to 20-30ms I guess.
I did update the yam driver from 3.1.3 to 3.1.4; didn't notice any difference.
The green dot still has the time to appear (well, flash) before I press each note; and it's not because I,m slow, I'm simply following rythm of the track being played back by my piano.
I did update the yam driver from 3.1.3 to 3.1.4; didn't notice any difference.
The green dot still has the time to appear (well, flash) before I press each note; and it's not because I,m slow, I'm simply following rythm of the track being played back by my piano.
I've got Synthesia connected to my Steinway Spirio | r, which is an acoustic grand piano with an official player system that supports MIDI in/out. I've spoken with Steinway, and their rep confirmed that there's a 500ms delay built into the MIDI in -> actuator pipeline, since it's a physical device and it requires a lot more work to make a physical key get depressed.
Given this, it would be AMAZING to have the ability to manually set a delay within Synthesia (I use the iPad app) that counterbalances the delay in the MIDI processing on the piano. I'd simply want the visuals to be 500ms delayed (while the MIDI data goes out without a delay), so that both the visuals and the piano's playback would be synchronized.
I get that this may be a super niche feature, but I'm willing to pay extra for it if that helps! This is really going to blow open the world of learning piano for me, and it's a dream I've had for decades. Thank you!
Given this, it would be AMAZING to have the ability to manually set a delay within Synthesia (I use the iPad app) that counterbalances the delay in the MIDI processing on the piano. I'd simply want the visuals to be 500ms delayed (while the MIDI data goes out without a delay), so that both the visuals and the piano's playback would be synchronized.
I get that this may be a super niche feature, but I'm willing to pay extra for it if that helps! This is really going to blow open the world of learning piano for me, and it's a dream I've had for decades. Thank you!
That is an interesting use case (and definitely niche, like you mentioned). Hmm.
Decoupling the audio playback position from the on-screen drawn position would take... a lot of effort. That we're drawing and playing the same thing at the same time is one of those universal assumptions the code makes. It would break Melody Practice mode outright: you can't play the background parts 500ms ahead of time if you don't know whether the song will still be playing or be stopped in 500ms.
For strictly "Watch and Listen" mode, it might at least be a tractable problem... but it'd still be a big job.
I'm afraid for how narrowly this would help the majority of users, it is tricky to justify spending the effort on it. The (not great) workaround in the meantime would be to have Synthesia output the background tracks through its own built-in synth (which completely defeats the purpose of having such a high-end instrument in the first place), but at least then your playing would be closer to in sync with Synthesia's.
Decoupling the audio playback position from the on-screen drawn position would take... a lot of effort. That we're drawing and playing the same thing at the same time is one of those universal assumptions the code makes. It would break Melody Practice mode outright: you can't play the background parts 500ms ahead of time if you don't know whether the song will still be playing or be stopped in 500ms.
For strictly "Watch and Listen" mode, it might at least be a tractable problem... but it'd still be a big job.
I'm afraid for how narrowly this would help the majority of users, it is tricky to justify spending the effort on it. The (not great) workaround in the meantime would be to have Synthesia output the background tracks through its own built-in synth (which completely defeats the purpose of having such a high-end instrument in the first place), but at least then your playing would be closer to in sync with Synthesia's.
Which port did you use to connect your Spirio to Synthesia? Are you using the USB port on the piano or the MIDI ports? I've been unsuccessful in having Synthesia recognize the Spirio as a MIDI device.