Відео

many keyboards have some built-in mechanism for adjusting the velocity curve. If not, there’s also a velocity adjustment slider within the “Midi” settings tab in the Sunday Keys App!

That's a great option for practicing at home, one we also use from time to time!

Check out the link in the description for all the details :)

Hi Angela, not a dumb question! As you're already leaning towards confirming, the included iPad power supply doesn't supply enough power to actually power connected hardware devices. That's why we always tell folks to purchase a dedicated power supply that's intended for providing more power.

Hi there, great question. If you'd like to use Sunday Keys sounds for recording we'd recommend that you actually download the MainStage format and then open those Patches as channel strips directly inside the sister DAW, Logic Pro. That way you can take real-time control of the sound, or automate it on the timeline as needed. It gives you maximum flexibility to record multiple midi takes, etc.

Thanks for your comment! We don't have any plans to release for Android, the App is only available for iPad and Mac.

We programmed Worship Beats using the Ultrabeat instrument plugin along with a stack of Midi FX to handle the drum sequencing.

Thanks for your comment. The vast majority of folks run their audio interface output to the soundboard directly, either via a cable, into a stage box, or similar. If you need some monitoring on stage most churches rely on either stage wedges or an in-ear monitoring system. Hope that helps!

Thanks!

Hi there, thanks for your comment and we can definitely help. Crashes of this kind indicate that you need to consider optimizing some of the CPU settings in the App, especially the pre-load setting and the audio buffer size. You can also reduce CPU strain further when you're playing Patches with a lot of sounds (or just playing a lot of notes) by reducing the "Voice Count" setting within individual Sounds in your Patches. We are happy to walk through optimization steps with you in more detail, you'll 100% be able to achieve reliable performance with your device (David's still running an M1 iPad, so you've got him beat!). Please reach out to us via the support page on our site if you'd like us to help you one on one. Thanks and have a great weekend!

Hi Angela, we'd be happy to help you get things connected. The Launchkey is capable of being used as a controller. Please contact us via the support page on our site if you'd like us to help. Thanks!

You’ll need an Apple Lightning to USB3 Camera Adapter. I’m using an older iPad with Sunday keys and it works great. Plug your power cord into the lightning input on the adapter and the USB in the other input. So far my old iPad has been working great with that setup.

^this :) Thanks for the helpful comment!

Glad it was helpful! We appreciate the suppport.

This is the SK Felt Piano from Sunday Keys!

I don’t believe so. On my m1 iPad Air with stage manager turned on it ends up as a little landscape window in the middle of the screen. If you have an external midi controller with faders and stuff and don’t need to actually hit buttons in the app it works fine. The app will keep running and making sound in the background even if it’s not on screen at all. Just remember to close it when you’re done, it often completely drains my iPad battery overnight when I forget it’s running

@@keatonbrier okay thanks. That's what I feared. oh well, on to something else.

Glad to hear! We'll note your feature request for multiple controller support as well :)

Since the top of the controller is metal and the iPad has a magnet embedded in the back, it's able to just lock into place!

THIS!! Waiting for patches for these artists

Yes please! I would love that!

Yeah, if I have a good number of sounds going and hit too many notes with the sustain pedal it crashes on my M1 ipad air

same issue with SK app on Mac. crashes often and isn’t reliable

Really? Mac too. Mmm yeah, definitely something they need to work on. Pause on the new features for a moment and make it as stable as possible

Hey folks, thanks for your comments. Just want to note that we do track overall stability across new versions of iPadOS, MacOS, and across new versions and features of the App. On the overall we are seeing improved stability, with fewer crashes over time and the latest version of the App is proving very stable for the vast majority of users. That being said, we'd love to help you out so you also feel confident. The symptoms you're describing are indicative that some local CPU optimizations can be adjusted to improve performance and reduce CPU strain, especially when you're playing with many sounds and a lot of notes. Just because we make it possible to add up to 15 Sounds, each with 64 voice polyphony per Sound, doesn't mean that all devices are going to be able to handle that. We'd be glad to help offer some specific things you can check to dial in the right balance between performance flexibility and lean CPU usage if you'd like a hand. Reach out to us via the support page on our site if you'd like, or if you'd prefer to DIY you can check out our CPU optimization section in the App's user manual here: support.sundaysounds.com/article/3150-optimizing-app-performance

Thank you!

The higher end Anker hub mentioned in this video features a USB C port, so our recommendation would be to use that with a cable that goes from USB C to type B or whatever type you need on the other end :)

@@SundaySounds we use two MIDI controllers plus a radial USB Pro DI which necessitates a third USB A port along with the USB-C for the host device.

I’ve been having some crashing issues on my M1 iPad air if i have too many of the slots filled and hit a lot of notes. I feel like it’s partly a app problem more than an ipad issue, but can’t be sure for your scenario

@@WesleyanWorshipGuy I have an M1 IPad Pro and have these issues too.

@@WesleyanWorshipGuy so should I didn't buy the up now?

Hi @WesleyanWorshipGuy and @Levinewell2325 thanks for your comments. David himself is using an M1 iPad Pro without issue, so we know there are things you can do too to dial in reliable and smooth performance. The symptoms you're describing are indicative that some local CPU optimizations can be adjusted to improve performance and reduce CPU strain, especially when you're playing with many sounds and a lot of notes. Just because we make it possible to add up to 15 Sounds, each with 64 voice polyphony per Sound, doesn't mean that all devices are going to be able to handle that. We'd be glad to help offer some specific things you can check to dial in the right balance between performance flexibility and lean CPU usage if you'd like a hand. Reach out to us via the support page on our site if you'd like, or if you'd prefer to DIY you can check out our CPU optimization section in the App's user manual here: support.sundaysounds.com/article/3150-optimizing-app-performance

@pianobirdy629 the App runs well for the vast majority of users and you have lots of built-in settings to help dial in a great experience for your device. It powers the keys rig for thousands of churches every Sunday :) If you have any questions or concerns along the way feel free to reach out to us via our website and we're happy to help.

this is all just a single midi channel. When you're building a Patch of this size, it's definitely wise to reduce voice counts based on what you actually need. If you ran all 15 Sounds at 64 voice polyphony, even on a powerful device, you'd be in for some sluggish or unreliable performance, but that's only because you're creating a state the App was never actually intended for! In a real-world performance context, where you use the stock Voice Counts for the included Sound Library, or consider reducing them based on what you actually need, you can control the balance well.

Thanks for the encouraging comment and for taking the time! We appreciate the support.

This is an M1 iPad Pro :)

Yes, you can do that!

It's the Sunday Keys App. It's not available on Android, only for iPad and Mac.

With the lowest buffer time for most audio interfaces you're going to be well below the threshold of human perception. We'd recommend a slightly higher buffer of 128 or 256 for most use cases in Mainstage on an M1 chip, there's no need to run lower than that and it just increases CPU strain unnecessarily.