Thanks for the feedback! I am happy someone is taking advantage of the IAA effect possibilities. It took a number of iterations to get the sync working with respect to different apps. It seems it was worth the effort after all. :)
I agree that, in practice, many of the other effect apps kind of take over the sounds coming from the loops. Originally, I wanted the effect app to be either inline or as a send. I wasn't sure if anyone would even use it, so I just went with the simplest option: inline. This was especially effective since most effect apps seem to be designed to be run on their own as independent music applications (to some degree).
That said, I think it is possible to have the effect app on its own bus and then a fader to route each individual loop to that bus OR the main stereo bus. This would be like a sub-mixer, where the effect output and Everest's first two channels are summed into the final (1,2) stereo output bus. I think this design is close to what you are suggesting. I need to investigate how to code it, of course, but given what I know about Apple's AUGraph, it is feasible.
As a temporary work around, you can route any loops you do NOT want applied to the effect app to the second stereo output bus (3,4). This is because I only route the first two channels (1,2) to a connected effect app (most only support stereo anyway).
This can be done using the (quadraphonic) panning controls in the settings menu. However, this does require more than two output channels on your audio hardware OR a device connected to the dock/lightning connector AND the headphone jack. I have tested this on devices with 4-6 output channels and it works really well. It will not work with just a stereo output, as the second stereo output bus (3,4) does not get summed to the first stereo output bus (1,2).
Yeah, I have been a little busy with other development work recently. I have coded up a few of the message board/email suggestions/feedback/bugs, but I need to consolidate them and add them to the roadmap, so people know what is coming and when. I also worked on a desktop version of Everest, but that is going to take some time. I also saw that Apple are adding plug-in support to iOS for their new AudioUnit version 3.0 API. It isn't clear to me yet how Everest would work in this new world, as it is both a host and a plug-in, with respect to Inter-App Audio.
Anyway, feel free to remind me what you want to see or what the priority order should be.
Yes, interesting to see how iOS 9 pans out. At the moment midi learn would be useful as my foot controller isn't assignable.. And the way everest is set up you get different workflows if you use cc's or notes.
Hey everyone, I just updated the roadmap spreadsheet. I consolidated all the feedback and suggestions I received, along with a few things I want to see. They are in rough priority order, but it would be helpful to have some voting on what I should focus on first.
Thanks @thinds. I signed up for the group to see any questions or comments, but my membership is still pending. So, I can't even see the post. Can you relay any important feedback?
Can do @christianrober. Nothing interesting to report but glad you applied for membership. It's a great friendly group where you can get excellent feedback.
Hi Christian. It would be amazing to see if your looper could be able to record long asynchronous loops for ambient looping. This is a feature that loopists can't find almost in any looper manufactured so far, either hardware or software. The multyplying option is ok when you want to play traditional rhythmic loops but for experimental soundscapes and ambient music, a total asynchronus option for the loops it's the way to go. Do you think you can develop that feature for your looper? No clocks, no synchronization between loops, no time signatures. Just free looping independently for each loop track.. Thanks for your time. Pepe
I think Everest already does what you want. Here are some options:
1. You can disable all quantization in the settings menu. Just turn off the three quantization switches, and the loops won't synchronize with each other. Nor should loop functions like insert and multiply quantize their start or end points.
2. You can disable quantization on a per loop track basis, leaving some, or none, quantized. The overdub button becomes a quantization toggle when the loop is empty/initialized. If you press it for all four loops, even over MIDI, quantization will be disabled for those four loops till they are erased, without having to mess with the settings menu.
3. Currently the max loop time per loop is around 4 minutes. As loops get longer, subsequent edits (like overdub) do clobber the old loop state, so the undo history gets kind of ruined, but that is just a limitation of the way I designed the memory allocation. In other words, I tried to consume a modest amount of memory by default so that Everest could co-exist with other apps. I have vague long term plans of making this configurable for advanced users, somewhere in the settings menu.
4. Be mindful of the loop edges. I added a feature last release that adds automatic fades to loop edges and loop window edges. This will create a discontinuity in long, continuous drone-type loops. When I want perfectly smooth loops I turn off the automatic fades and use overdub and the volume on my instrument to get smooth continuous waveforms across loop boundaries.
Let me know if that helps; I may have misinterpreted your request.
@crifytosp I just wanted to let you know that Undo now undoes recordings. I think you requested this feature. @thinds you may have requested this as well. I hope it works to your satisfaction!
Comments
Thanks for the feedback! I am happy someone is taking advantage of the IAA effect possibilities. It took a number of iterations to get the sync working with respect to different apps. It seems it was worth the effort after all. :)
I agree that, in practice, many of the other effect apps kind of take over the sounds coming from the loops. Originally, I wanted the effect app to be either inline or as a send. I wasn't sure if anyone would even use it, so I just went with the simplest option: inline. This was especially effective since most effect apps seem to be designed to be run on their own as independent music applications (to some degree).
That said, I think it is possible to have the effect app on its own bus and then a fader to route each individual loop to that bus OR the main stereo bus. This would be like a sub-mixer, where the effect output and Everest's first two channels are summed into the final (1,2) stereo output bus. I think this design is close to what you are suggesting. I need to investigate how to code it, of course, but given what I know about Apple's AUGraph, it is feasible.
As a temporary work around, you can route any loops you do NOT want applied to the effect app to the second stereo output bus (3,4). This is because I only route the first two channels (1,2) to a connected effect app (most only support stereo anyway).
This can be done using the (quadraphonic) panning controls in the settings menu. However, this does require more than two output channels on your audio hardware OR a device connected to the dock/lightning connector AND the headphone jack. I have tested this on devices with 4-6 output channels and it works really well. It will not work with just a stereo output, as the second stereo output bus (3,4) does not get summed to the first stereo output bus (1,2).
Yeah, I have been a little busy with other development work recently. I have coded up a few of the message board/email suggestions/feedback/bugs, but I need to consolidate them and add them to the roadmap, so people know what is coming and when. I also worked on a desktop version of Everest, but that is going to take some time. I also saw that Apple are adding plug-in support to iOS for their new AudioUnit version 3.0 API. It isn't clear to me yet how Everest would work in this new world, as it is both a host and a plug-in, with respect to Inter-App Audio.
Anyway, feel free to remind me what you want to see or what the priority order should be.
https://www.facebook.com/groups/Ipadmusician
I think Everest already does what you want. Here are some options:
1. You can disable all quantization in the settings menu. Just turn off the three quantization switches, and the loops won't synchronize with each other. Nor should loop functions like insert and multiply quantize their start or end points.
2. You can disable quantization on a per loop track basis, leaving some, or none, quantized. The overdub button becomes a quantization toggle when the loop is empty/initialized. If you press it for all four loops, even over MIDI, quantization will be disabled for those four loops till they are erased, without having to mess with the settings menu.
3. Currently the max loop time per loop is around 4 minutes. As loops get longer, subsequent edits (like overdub) do clobber the old loop state, so the undo history gets kind of ruined, but that is just a limitation of the way I designed the memory allocation. In other words, I tried to consume a modest amount of memory by default so that Everest could co-exist with other apps. I have vague long term plans of making this configurable for advanced users, somewhere in the settings menu.
4. Be mindful of the loop edges. I added a feature last release that adds automatic fades to loop edges and loop window edges. This will create a discontinuity in long, continuous drone-type loops. When I want perfectly smooth loops I turn off the automatic fades and use overdub and the volume on my instrument to get smooth continuous waveforms across loop boundaries.
Let me know if that helps; I may have misinterpreted your request.