Thank you! I use this every Sunday with Third Party plug-ins and very rarely have any issues. Love the versatility and smoothness of transitions, takes a lot of pressure off live sets. I always learn something new that makes using the SK app easier.
I Love Love Love the flexibility and the ease of use along with the power of sounds the this app offers. If you haven’t tried it, don’t wait! Our worship keys went to a whole new level.
I really love this app, and have been using it both on an iPad Air (M2) and a 2018 Macbook Pro. I believe the claims of reliability are probably valid as long as you stick to the SK library, but the 3rd party AU/AUv3 implementation really needs work. Reliability is NOT solid once you add plugins. Sometimes they simply disappear (on iPad) requiring a restart of the app. This happened to me during a service recently and was not exactly fun Lol. More common is bad delays loading patches with plugins (iPad and Mac) even with preload set. which makes transitions not very smooth. I've been on a support ticket about this - the support team is really responsive and knowledgeable, but so far no solution in sight. I really hope they can get this sorted out because I love using the app, but not sure it's quite ready for prime time yet, at least with 3rd party plugins.
I concur with this comment. I’ve been using the app since day 1, and the AUv3 integration needs work, it crashed several times on live performance or it doesn’t even load when changing between patches.
@@shemaradams561 Honestly don't know if one is inherently better than the other but the decision comes down to a few things for me: What instruments do you want to use? For instance, if you must use Kontakt, then your only choice is Mac. If you're using Pianoteq, you could go either way since there is an iOS version of that instrument. There are also many other great iOS instruments out there as well. One big advantage with iOS is that instruments (except for Pianoteq) tend to cost a fraction of the price of their VST counterparts. USD $30 is on the expensive side in the iOS world, for instance. Another consideration, if you own both a mac and an iPad, is that you'll want to use whichever has the better specs. I believe SK will run better on an M2 iPad than on an Intel MBP, for example. A 3rd consideration, which I had initially underestimated the importance of (if you want to use snapshots), is that Macs don't have touch screens. This makes a huge difference in the heat of live performance, as I've found it really tricky to quickly select snapshots using the trackpad on the MBP. Much easier to do this smoothly on iPad. So after all is said and done and having used both extensively, my preference is the iPad. Hope that helps!
@@shemaradams561 Having used both quite a bit, I prefer the iPad, because the touch screen makes it a lot easier use snapshots than the trackpad on the MBP. I don't know if one is inherently better than the other, though. If you already own both, you'll want to use the one with better specs (e.g. M chip over Intel or A series). Instrument availability is a consideration, but since my main instrument is Pianoteq (available for both MacOs and iOS) I can go either way. I do like the fact that iOS plugins (aside from Pianoteq) tend to be a fraction of the cost of MacOS plugins.
That kind of limit happens in logic as well…. I would always use the least amount of 3rd party plug ins possible for the best possible reliability with any program. I am researching this for myself and haven’t used it before, but that’s how most digital audio workstations work. This can often be the limit of computing on the device rather than the application, but then causes the application to fail.
SundaySounds Hello! Thank you for all the amazing content! Just a quick question, will you guys ever make more content for SundayGuitar? I bought your software and love it, just wish there was more support for it like you guys do for the keys🙏🏽 I joined the Facebook but there’s not much of responses from anyone there, and I love the keys tutorials for songs you guys post and would love it on the guitar! Again, thank you for everything and may the Lord bless you guys abundantly in Jesus’ name!
I really like some of the features of this app. I have the main stage version of Sunday keys, I.m wondering if any update is coming in the near future for Main Stage. I really like the one knob per sound for more options and the snapchat tabs.
I just downloaded the app onto my new MacBook Air with m 3 chip.. I am about 98% satisfied with everything. The one feature that I noticed that doesn't work as seamlessly as described in these videos, is the smooth transition between patch changes.. if I sustain a note in one patch and then click the next patch button, it does not hold the note until I begin playing the new patch, rather it abruptly cuts off.. according to your description, even in this video, that's not how it is supposed to happen. If anybody reads all the way through this comment, do you have any suggestions on what I should do? Thanks!
Hey there, head to the settings Menu and in the Audio tab you’ll find a setting called “Time to Silence previous Patch”. You can increase that up to 10s and that should give you more time to get into that next Patch :)
@@SundaySounds Would be better if it would sustain as long as you hold the notes down like in MS and Gig Performer, but if that's not feasible, at least a smooth fadeout, rather than just cutting off. I'm guessing increasing the time demands more CPU?
Is this beginner friendly? We really need our sound to fill up the space. Also are some of these built in or would someone have to build these for each song, each week?
Yes! The Sunday Keys App is the most user-friendly software for live worship keys, it's a huge part of why we developed the App. The Sunday Keys library comes with hundreds of ready to play Patches and we even have a cool feature discussed in this video called "Patch Builder" that let's you describe the Sounds you need in natural language and we create a great Patch for you in seconds!
PS - the patch loading delay I alluded to is even a worse problem than it seems at first glance. You have no idea how long it will take for the module with the AU/AUv3 sound to load, and for me it's usually the main piano sound. It can take several seconds, and here's the worst part - if you play any keys before the sound is loaded (because you have no way of knowing it hasn't loaded yet), those previous notes you played will suddenly be triggered all at once and OUT OF TIME whenever the sound does finally load, which is obviously super embarrassing and makes you sound like a really bad musician. I seriously hope this is fixed soon because this alone is causing me to consider killing the SK app experiment for our team, which would be sad because it really is a good concept.
UPDATE: Setting Preload Patches to MORE THAN 1 in both directions seems to help with this issue, even if you only plan to advance one patch at a time through your set. This seems a bit counterintuitive, and you might get a warning that performance may be degraded (which might be true) but that's the only workaround that's helped me. Also, I'm not sure but I think there was an SK core update (can't confirm - would be nice if one could easily find a changelog on their site). That, and updating to iOS 18 seems to have improved reliability and smoother patch changes on the iPad...keeping🤞🤞 There was a lot of frustration expressed in my last post, but I hope that doesn't take away from the fact that I really love this concept, and that it could potentially be great someday, if these kind of performance issues are given high priority.
I've installed this app on my iPad Pro 11 M1. But my device heats up and would crash. I have followed the optimized settings it still heats up. Can someone please help me with this setup. Thank you!
Love this app, however, I’m having issues midi mapping to faders on my Motif XF. The App recognizes both the XF and my other midi controller, but only allows mapping and playing on the other controller. Am i doing something wrong?
Looks like you may need to do some programming either in the keyboard or via the Yamaha editor software to setup those faders. You'll want to program them to send MIDI CC data then it will be recognized by the App. From Yamaha on the editor: usa.yamaha.com/files/download/other_assets/3/329713/faders_xy_pad_om_en_b0.pdf You can also check what data the App is receiving in Settings > MIDI, move the faders and you will see the data show up in the MIDI Monitor. support.sundaysounds.com/article/3183-midi-monitor
You can use a MIDI controller like the Korg nanoPad2, or if your keyboard has drum pads that you can program to send MIDI CC those will work. We think an even easier option is to use the Patch Lock feature for the Tonic Pad Player, this will save your Tonic settings to the Patch, so once you set up Patch Lock for each Patch in your setlist, Tonic will smoothly change to each setting you program as you change patches. support.sundaysounds.com/article/3136-tonic
2 หลายเดือนก่อน +1
In my case, I am using the Steam Deck from Elgato. I programmed a MIDI plugin on the Stream Deck on my Mac and configured my buttons to send MIDI messages to activate the tonic, the tonic key, and the snapshots per patch as mapped in the SK app. I use a Macbook instead of an iPad since I also use Kontakt along with this app.
This. Is. AMAZING!!! I have wanted something like this for YEARS on iPad 😩
Thank you so much for making this 🙏🏾🙏🏾🙏🏾
Thank you! I use this every Sunday with Third Party plug-ins and very rarely have any issues. Love the versatility and smoothness of transitions, takes a lot of pressure off live sets. I always learn something new that makes using the SK app easier.
I Love Love Love the flexibility and the ease of use along with the power of sounds the this app offers. If you haven’t tried it, don’t wait! Our worship keys went to a whole new level.
Please make a standalone app for Windows 🙏🙏🙏🙏🙏
I really love this app, and have been using it both on an iPad Air (M2) and a 2018 Macbook Pro. I believe the claims of reliability are probably valid as long as you stick to the SK library, but the 3rd party AU/AUv3 implementation really needs work. Reliability is NOT solid once you add plugins. Sometimes they simply disappear (on iPad) requiring a restart of the app. This happened to me during a service recently and was not exactly fun Lol. More common is bad delays loading patches with plugins (iPad and Mac) even with preload set. which makes transitions not very smooth. I've been on a support ticket about this - the support team is really responsive and knowledgeable, but so far no solution in sight. I really hope they can get this sorted out because I love using the app, but not sure it's quite ready for prime time yet, at least with 3rd party plugins.
I concur with this comment. I’ve been using the app since day 1, and the AUv3 integration needs work, it crashed several times on live performance or it doesn’t even load when changing between patches.
Would you say which is better, Mac or iPad for Sunday keys?
@@shemaradams561 Honestly don't know if one is inherently better than the other but the decision comes down to a few things for me: What instruments do you want to use? For instance, if you must use Kontakt, then your only choice is Mac. If you're using Pianoteq, you could go either way since there is an iOS version of that instrument. There are also many other great iOS instruments out there as well. One big advantage with iOS is that instruments (except for Pianoteq) tend to cost a fraction of the price of their VST counterparts. USD $30 is on the expensive side in the iOS world, for instance.
Another consideration, if you own both a mac and an iPad, is that you'll want to use whichever has the better specs. I believe SK will run better on an M2 iPad than on an Intel MBP, for example. A 3rd consideration, which I had initially underestimated the importance of (if you want to use snapshots), is that Macs don't have touch screens. This makes a huge difference in the heat of live performance, as I've found it really tricky to quickly select snapshots using the trackpad on the MBP. Much easier to do this smoothly on iPad. So after all is said and done and having used both extensively, my preference is the iPad. Hope that helps!
@@shemaradams561 Having used both quite a bit, I prefer the iPad, because the touch screen makes it a lot easier use snapshots than the trackpad on the MBP. I don't know if one is inherently better than the other, though. If you already own both, you'll want to use the one with better specs (e.g. M chip over Intel or A series). Instrument availability is a consideration, but since my main instrument is Pianoteq (available for both MacOs and iOS) I can go either way. I do like the fact that iOS plugins (aside from Pianoteq) tend to be a fraction of the cost of MacOS plugins.
That kind of limit happens in logic as well…. I would always use the least amount of 3rd party plug ins possible for the best possible reliability with any program. I am researching this for myself and haven’t used it before, but that’s how most digital audio workstations work. This can often be the limit of computing on the device rather than the application, but then causes the application to fail.
I love this app, I've been using it on my ipad pro M1 and it worked great. Looking forward to being able to use the pitch wheel !
I'm using this as well with my ipad pro 11 M1. My device heats up and would crash at a certain point. Does yours heat up? Care to share your set-up?
@@deanreese1702what is the storage capacity for your M1?
How many memory needed when download all sounds pack?
SundaySounds Hello! Thank you for all the amazing content!
Just a quick question, will you guys ever make more content for SundayGuitar? I bought your software and love it, just wish there was more support for it like you guys do for the keys🙏🏽
I joined the Facebook but there’s not much of responses from anyone there, and I love the keys tutorials for songs you guys post and would love it on the guitar!
Again, thank you for everything and may the Lord bless you guys abundantly in Jesus’ name!
I really like some of the features of this app. I have the main stage version of Sunday keys, I.m wondering if any update is coming in the near future for Main Stage. I really like the one knob per sound for more options and the snapchat tabs.
I just downloaded the app onto my new MacBook Air with m 3 chip.. I am about 98% satisfied with everything. The one feature that I noticed that doesn't work as seamlessly as described in these videos, is the smooth transition between patch changes.. if I sustain a note in one patch and then click the next patch button, it does not hold the note until I begin playing the new patch, rather it abruptly cuts off.. according to your description, even in this video, that's not how it is supposed to happen. If anybody reads all the way through this comment, do you have any suggestions on what I should do? Thanks!
Hey there, head to the settings Menu and in the Audio tab you’ll find a setting called “Time to Silence previous Patch”. You can increase that up to 10s and that should give you more time to get into that next Patch :)
@@SundaySounds Would be better if it would sustain as long as you hold the notes down like in MS and Gig Performer, but if that's not feasible, at least a smooth fadeout, rather than just cutting off. I'm guessing increasing the time demands more CPU?
Do you plan to integrate AUv3 effects on the Main audio outputs? It will be great to have that flexibility on the app.
Is this beginner friendly? We really need our sound to fill up the space. Also are some of these built in or would someone have to build these for each song, each week?
Yes! The Sunday Keys App is the most user-friendly software for live worship keys, it's a huge part of why we developed the App. The Sunday Keys library comes with hundreds of ready to play Patches and we even have a cool feature discussed in this video called "Patch Builder" that let's you describe the Sounds you need in natural language and we create a great Patch for you in seconds!
Tenho um iPad 8gen e nao é compativel com o MainsTage!!
Can you increase the tempo of the tonic pad?
If yes is it possible also in Ableton live?
Can you use a presonus atom as the midi controller?
PS - the patch loading delay I alluded to is even a worse problem than it seems at first glance. You have no idea how long it will take for the module with the AU/AUv3 sound to load, and for me it's usually the main piano sound. It can take several seconds, and here's the worst part - if you play any keys before the sound is loaded (because you have no way of knowing it hasn't loaded yet), those previous notes you played will suddenly be triggered all at once and OUT OF TIME whenever the sound does finally load, which is obviously super embarrassing and makes you sound like a really bad musician. I seriously hope this is fixed soon because this alone is causing me to consider killing the SK app experiment for our team, which would be sad because it really is a good concept.
UPDATE: Setting Preload Patches to MORE THAN 1 in both directions seems to help with this issue, even if you only plan to advance one patch at a time through your set. This seems a bit counterintuitive, and you might get a warning that performance may be degraded (which might be true) but that's the only workaround that's helped me. Also, I'm not sure but I think there was an SK core update (can't confirm - would be nice if one could easily find a changelog on their site). That, and updating to iOS 18 seems to have improved reliability and smoother patch changes on the iPad...keeping🤞🤞 There was a lot of frustration expressed in my last post, but I hope that doesn't take away from the fact that I really love this concept, and that it could potentially be great someday, if these kind of performance issues are given high priority.
I've installed this app on my iPad Pro 11 M1. But my device heats up and would crash. I have followed the optimized settings it still heats up. Can someone please help me with this setup. Thank you!
⭐⭐⭐⭐⭐ Satisfied (Please add Drums loop or Rythm I know you can do that) 🤩🤩🤩
How about in android and windows?
Love this app, however, I’m having issues midi mapping to faders on my Motif XF.
The App recognizes both the XF and my other midi controller, but only allows mapping and playing on the other controller. Am i doing something wrong?
Looks like you may need to do some programming either in the keyboard or via the Yamaha editor software to setup those faders. You'll want to program them to send MIDI CC data then it will be recognized by the App. From Yamaha on the editor: usa.yamaha.com/files/download/other_assets/3/329713/faders_xy_pad_om_en_b0.pdf
You can also check what data the App is receiving in Settings > MIDI, move the faders and you will see the data show up in the MIDI Monitor. support.sundaysounds.com/article/3183-midi-monitor
Can i buy a ipad 10th generation for Sunday sounds....or it will lag
@@HYPERGAMING-wx8le you can and it will work fine until you add auv3 instruments. The rest works fine
What's the best MIDI controller for the tonic pad
You can use a MIDI controller like the Korg nanoPad2, or if your keyboard has drum pads that you can program to send MIDI CC those will work. We think an even easier option is to use the Patch Lock feature for the Tonic Pad Player, this will save your Tonic settings to the Patch, so once you set up Patch Lock for each Patch in your setlist, Tonic will smoothly change to each setting you program as you change patches. support.sundaysounds.com/article/3136-tonic
In my case, I am using the Steam Deck from Elgato. I programmed a MIDI plugin on the Stream Deck on my Mac and configured my buttons to send MIDI messages to activate the tonic, the tonic key, and the snapshots per patch as mapped in the SK app. I use a Macbook instead of an iPad since I also use Kontakt along with this app.
Can you use a presonus atom ??? @sundaysounds