Ridgewalk by Aqeel Aadam Sound (Released)

sigma79

@osc101 said:

@aqeelaadam said:

@osc101 said:

@aqeelaadam said:

@osc101 said:
Looks interesting.

Can the “play head” be controlled via host automation?

If you mean playback being controlled generally - you can play/pause Ridgewalk via a param called "PLAY". If you want to control where the loopers are playing back from, yep, you can use the "External" Movement option and use the param "EXTERNAL MOTION" to control where loopers are positioned.

I’ve loaded Ridgewalk as an insert fx in Cubasis 3 on an audio track playing a wav file. Ridgewalk seems to work, however, under automation, there are no Ridgewalk parameters shown at all. First time I tried this, Ridgewalk crashed. Second time and thereafter, no parameters shown under automation. Setting “External Movement” made no difference.

Perhaps I am doing something wrong?

Hey @osc101, sorry, just sitting down to look into this. Firstly, the latest update should really help with crashes and stability, so I'd make sure you're on that version.

Secondly, I'm not super familiar with Cubasis so please correct me if I'm wrong, but Ridgewalk seems to be behaving as I'd expect in Cubasis. It seems that no AUv3s have their controls available in the Automation list at first, but if you manually record automation to an AUv3 control, it then shows up in the Automation section for further editing and manipulation. Here's a Jakob Haq video describing that behavior (he's demoing Cubasis 2 but this seems consistent on my Cubasis 3 as well). Can you confirm that same or is it still different for you?

The update does seem to have lessened the amount of crashes…good work!

As for my automation question, no luck. I understand how Cubasis works with automating parameters, the problem I’m having is that there is nothing to automate. Once movement is set to external, what parameter should I be tweaking for the automation setting to instantiate? Nothing in the UI controls the “play head” (other than the play, pause, reverse) and there are no other parameters selectable in the host automation channel.

I think what I’m looking for is more like a source module via AU that allows for a file to be loaded, then granulated with a manually articulated playhead.

Forgive the lameness ( although its cool for a first tweak )

Of Drambo wavescanner module.

Its a spectral processer I think.

You can scan the file, with a knob or add lfo to slices. So the slices scan back and forth before next random slice and lfo'd slice.

You could probably add silo after.

Its actually just this key patch as the sample

osc101

@aqeelaadam said:

@osc101 said:

@aqeelaadam said:

@osc101 said:

@aqeelaadam said:

@osc101 said:
Looks interesting.

Can the “play head” be controlled via host automation?

If you mean playback being controlled generally - you can play/pause Ridgewalk via a param called "PLAY". If you want to control where the loopers are playing back from, yep, you can use the "External" Movement option and use the param "EXTERNAL MOTION" to control where loopers are positioned.

I’ve loaded Ridgewalk as an insert fx in Cubasis 3 on an audio track playing a wav file. Ridgewalk seems to work, however, under automation, there are no Ridgewalk parameters shown at all. First time I tried this, Ridgewalk crashed. Second time and thereafter, no parameters shown under automation. Setting “External Movement” made no difference.

Perhaps I am doing something wrong?

Hey @osc101, sorry, just sitting down to look into this. Firstly, the latest update should really help with crashes and stability, so I'd make sure you're on that version.

Secondly, I'm not super familiar with Cubasis so please correct me if I'm wrong, but Ridgewalk seems to be behaving as I'd expect in Cubasis. It seems that no AUv3s have their controls available in the Automation list at first, but if you manually record automation to an AUv3 control, it then shows up in the Automation section for further editing and manipulation. Here's a Jakob Haq video describing that behavior (he's demoing Cubasis 2 but this seems consistent on my Cubasis 3 as well). Can you confirm that same or is it still different for you?

The update does seem to have lessened the amount of crashes…good work!

As for my automation question, no luck. I understand how Cubasis works with automating parameters, the problem I’m having is that there is nothing to automate. Once movement is set to external, what parameter should I be tweaking for the automation setting to instantiate? Nothing in the UI controls the “play head” (other than the play, pause, reverse) and there are no other parameters selectable in the host automation channel.

I think what I’m looking for is more like a source module via AU that allows for a file to be loaded, then granulated with a manually articulated playhead.

Ahhh, I see what you're saying. I didn't realize you were trying to access the EXTERNAL MOTION parameter specifically - which is "headless" (no direct UI control).

One thing I had been thinking about doing under the hood was tying the "Tap" position to the "External Motion" parameter, so that the Tap mode position would actually be reloaded when restarting a session. I think that would solve your problem as well, as you could use Tap mode to record some automation and then edit from there? But then it's getting fairly convoluted and I'm not sure where I'd even start with explaining that in the manual haha

To be honest, IMO this is kind of strange behavior on the part of Cubasis; every other DAW I know of just gives you a list of params and lets you start editing or automating them. But I would like to support this use case of course

I like your “controlled tap” idea. I take a lot of well known pieces of audio, and try to creatively rearrange them in ways that bring them new life. Thus my request for control of the play head. Your idea has merit in this regard.

I do agree about Cubasis, their automation mode leaves a lot to be desired, but it does work. It’s just quirky.

osc101

@sigma79 said:

@osc101 said:

@aqeelaadam said:

@osc101 said:

@aqeelaadam said:

@osc101 said:
Looks interesting.

Can the “play head” be controlled via host automation?

If you mean playback being controlled generally - you can play/pause Ridgewalk via a param called "PLAY". If you want to control where the loopers are playing back from, yep, you can use the "External" Movement option and use the param "EXTERNAL MOTION" to control where loopers are positioned.

I’ve loaded Ridgewalk as an insert fx in Cubasis 3 on an audio track playing a wav file. Ridgewalk seems to work, however, under automation, there are no Ridgewalk parameters shown at all. First time I tried this, Ridgewalk crashed. Second time and thereafter, no parameters shown under automation. Setting “External Movement” made no difference.

Perhaps I am doing something wrong?

Hey @osc101, sorry, just sitting down to look into this. Firstly, the latest update should really help with crashes and stability, so I'd make sure you're on that version.

Secondly, I'm not super familiar with Cubasis so please correct me if I'm wrong, but Ridgewalk seems to be behaving as I'd expect in Cubasis. It seems that no AUv3s have their controls available in the Automation list at first, but if you manually record automation to an AUv3 control, it then shows up in the Automation section for further editing and manipulation. Here's a Jakob Haq video describing that behavior (he's demoing Cubasis 2 but this seems consistent on my Cubasis 3 as well). Can you confirm that same or is it still different for you?

The update does seem to have lessened the amount of crashes…good work!

As for my automation question, no luck. I understand how Cubasis works with automating parameters, the problem I’m having is that there is nothing to automate. Once movement is set to external, what parameter should I be tweaking for the automation setting to instantiate? Nothing in the UI controls the “play head” (other than the play, pause, reverse) and there are no other parameters selectable in the host automation channel.

I think what I’m looking for is more like a source module via AU that allows for a file to be loaded, then granulated with a manually articulated playhead.

Forgive the lameness ( although its cool for a first tweak )

Of Drambo wavescanner module.

Its a spectral processer I think.

You can scan the file, with a knob or add lfo to slices. So the slices scan back and forth before next random slice and lfo'd slice.

You could probably add silo after.

Its actually just this key patch as the sample

Interesting! But I don’t see where the control of a knob scans the file. I’ve never used Drambo, so forgive my ignorance.

Those demos remind me of the old Korg Wavestation. Loved that thing…

NeuM

I like this trend of super simple UI's for plugins.

sigma79

@osc101 said:

@sigma79 said:

@osc101 said:

@aqeelaadam said:

@osc101 said:

@aqeelaadam said:

@osc101 said:
Looks interesting.

Can the “play head” be controlled via host automation?

If you mean playback being controlled generally - you can play/pause Ridgewalk via a param called "PLAY". If you want to control where the loopers are playing back from, yep, you can use the "External" Movement option and use the param "EXTERNAL MOTION" to control where loopers are positioned.

I’ve loaded Ridgewalk as an insert fx in Cubasis 3 on an audio track playing a wav file. Ridgewalk seems to work, however, under automation, there are no Ridgewalk parameters shown at all. First time I tried this, Ridgewalk crashed. Second time and thereafter, no parameters shown under automation. Setting “External Movement” made no difference.

Perhaps I am doing something wrong?

Hey @osc101, sorry, just sitting down to look into this. Firstly, the latest update should really help with crashes and stability, so I'd make sure you're on that version.

Secondly, I'm not super familiar with Cubasis so please correct me if I'm wrong, but Ridgewalk seems to be behaving as I'd expect in Cubasis. It seems that no AUv3s have their controls available in the Automation list at first, but if you manually record automation to an AUv3 control, it then shows up in the Automation section for further editing and manipulation. Here's a Jakob Haq video describing that behavior (he's demoing Cubasis 2 but this seems consistent on my Cubasis 3 as well). Can you confirm that same or is it still different for you?

The update does seem to have lessened the amount of crashes…good work!

As for my automation question, no luck. I understand how Cubasis works with automating parameters, the problem I’m having is that there is nothing to automate. Once movement is set to external, what parameter should I be tweaking for the automation setting to instantiate? Nothing in the UI controls the “play head” (other than the play, pause, reverse) and there are no other parameters selectable in the host automation channel.

I think what I’m looking for is more like a source module via AU that allows for a file to be loaded, then granulated with a manually articulated playhead.

Forgive the lameness ( although its cool for a first tweak )

Of Drambo wavescanner module.

Its a spectral processer I think.

You can scan the file, with a knob or add lfo to slices. So the slices scan back and forth before next random slice and lfo'd slice.

You could probably add silo after.

Its actually just this key patch as the sample

Interesting! But I don’t see where the control of a knob scans the file. I’ve never used Drambo, so forgive my ignorance.

Those demos remind me of the old Korg Wavestation. Loved that thing…

No worries.

Just read you need a manual playhead and thought of this.

The offset knob 0-127 cc scans the file. Its whats automated here to go back and forth.

The file can be sliced. The slices set to random slice, each time the sequencer actually triggers a slice. When slice is triggered. Lfos I think are p-locked to the step sequencer notes. Where the lfos scroll the offest before getting triggered by next step/random slice.

You can actually use this Drambo module and do the same in any host, using Drambo as an fx because all the automation will work.

Because its a Drambo module and not an AU. Which need to be hosted only in Drambo. To gain automation.

Gavinski

@NeuM said:
I like this trend of super simple UI's for plugins.

Just checking you know that when you tap on the 3 main labels on the main UI it opens up other knobs and controls?

aqeelaadam

@osc101 said:
I like your “controlled tap” idea. I take a lot of well known pieces of audio, and try to creatively rearrange them in ways that bring them new life. Thus my request for control of the play head. Your idea has merit in this regard.

I do agree about Cubasis, their automation mode leaves a lot to be desired, but it does work. It’s just quirky.

Cool! Glad that idea makes sense to you. I think it makes some technical sense too because, like I said before, it would be kind of nice to reload the last tapped position when reopening a project, and tying the taps to the parameter would provide this for free.

I'm uploading a new version to the App Store right now but I'll table that for the next version.

@Gavinski said:

@NeuM said:
I like this trend of super simple UI's for plugins.

Just checking you know that when you tap on the 3 main labels on the main UI it opens up other knobs and controls?

Good question to ask, though the basic set of controls is also intended to provide a "I don't care, let's make sound!" experience

NeuM

@Gavinski said:

@NeuM said:
I like this trend of super simple UI's for plugins.

Just checking you know that when you tap on the 3 main labels on the main UI it opens up other knobs and controls?

The front facing UI is clean and easy to comprehend. Having the option to dig deeper is completely OK.

aqeelaadam

@SilentObserver said:

@aqeelaadam said:

@SilentObserver said:
@aqeelaadam I'm getting weird performance with Logic iPad. When a midi region, routed through Ridgewalk, finishes, the app stops playing the last loops, even though the track is still playing (and the hold time is quite long).

The odd thing, is that this behaviour is not consistent - sometimes it will continue playing the last loops until the hold time runs out, other times it won't.

Oh interesting. I think I know (roughly) what this issue might be - I'll take a look into it today and release a patch if it's simple enough.

In testing on desktop, Logic seems to be the one DAW that really cares whether or not your "audio effect" is actually producing sound on its own. From Logic's perspective, an audio effect should only produce sound if it's receiving sound, and it'll shut down your plug-in's audio processing if nothing is actually being input to the plug-in. On desktop, loading Ridgewalk onto a software instrument's track at all seems to do the trick, but maybe Logic for iPad is further optimized and will shut down your plug-in's audio processing if input stops being sent. I think there's a way to declare your plug-in as having an infinite "tail" (e.g. like an infinite frozen reverb or self-oscillating delay).

@waka_x said:
thanks @aqeelaadam
much better now on my iPad 3.

still- do you support iOS 12.5.7? (iPad air 1)!?
there is a weird bug - the plug mostly works
but Traversal "directions" popup doesnt respond. (forward, wander, etc)
it's dead- non-interactive. Would be cool if you can fix this... I still use that old iPad:)
no problems if you don't...

I'll try to investigate this - I think I have a similar device laying around. It's possible that the software framework that I'm using doesn't support such older devices anymore But I would love to support them if I can. If not, I'll update documentation.

Thanks @aqeelaadam - I guess it could be due to Logic shutting the processing. I can restart the internal play engine within the app to keep the remaining loops going, once Logic stops it, but I'd prefer to keep that processing running if possible. If you know that work-around for Logic, I'll give that a go! Strange that it's inconsistent though...

Just posted another update for iOS which should further improve stability, as well as hopefully helping this issue too. @SilentObserver could you confirm if it's fixed on the latest version whenever you get the chance?

McD

@aqeelaadam said:

@SilentObserver said:

@aqeelaadam said:

@SilentObserver said:
@aqeelaadam I'm getting weird performance with Logic iPad. When a midi region, routed through Ridgewalk, finishes, the app stops playing the last loops, even though the track is still playing (and the hold time is quite long).

The odd thing, is that this behaviour is not consistent - sometimes it will continue playing the last loops until the hold time runs out, other times it won't.

Oh interesting. I think I know (roughly) what this issue might be - I'll take a look into it today and release a patch if it's simple enough.

In testing on desktop, Logic seems to be the one DAW that really cares whether or not your "audio effect" is actually producing sound on its own. From Logic's perspective, an audio effect should only produce sound if it's receiving sound, and it'll shut down your plug-in's audio processing if nothing is actually being input to the plug-in. On desktop, loading Ridgewalk onto a software instrument's track at all seems to do the trick, but maybe Logic for iPad is further optimized and will shut down your plug-in's audio processing if input stops being sent. I think there's a way to declare your plug-in as having an infinite "tail" (e.g. like an infinite frozen reverb or self-oscillating delay).

@waka_x said:
thanks @aqeelaadam
much better now on my iPad 3.

still- do you support iOS 12.5.7? (iPad air 1)!?
there is a weird bug - the plug mostly works
but Traversal "directions" popup doesnt respond. (forward, wander, etc)
it's dead- non-interactive. Would be cool if you can fix this... I still use that old iPad:)
no problems if you don't...

I'll try to investigate this - I think I have a similar device laying around. It's possible that the software framework that I'm using doesn't support such older devices anymore But I would love to support them if I can. If not, I'll update documentation.

Thanks @aqeelaadam - I guess it could be due to Logic shutting the processing. I can restart the internal play engine within the app to keep the remaining loops going, once Logic stops it, but I'd prefer to keep that processing running if possible. If you know that work-around for Logic, I'll give that a go! Strange that it's inconsistent though...

Just posted another update for iOS which should further improve stability, as well as hopefully helping this issue too. @SilentObserver could you confirm if it's fixed on the latest version whenever you get the chance?

I noticed there was a bundle option to get both Ridgewalk and Weeping Wall at a nice discount so I use some credits I have left from a Gift Card that I’ve been itchy to spend. I like the user interface and the soundscapes that are produced with very little effort. They don’t manipulate the loops beyond recognition and you get an interesting swirling texture of realistic sounds. I went with the ping-pong
effect.

Nice work @aqeelaadam.

SilentObserver

@aqeelaadam said:

@SilentObserver said:

@aqeelaadam said:

@SilentObserver said:
@aqeelaadam I'm getting weird performance with Logic iPad. When a midi region, routed through Ridgewalk, finishes, the app stops playing the last loops, even though the track is still playing (and the hold time is quite long).

The odd thing, is that this behaviour is not consistent - sometimes it will continue playing the last loops until the hold time runs out, other times it won't.

Oh interesting. I think I know (roughly) what this issue might be - I'll take a look into it today and release a patch if it's simple enough.

In testing on desktop, Logic seems to be the one DAW that really cares whether or not your "audio effect" is actually producing sound on its own. From Logic's perspective, an audio effect should only produce sound if it's receiving sound, and it'll shut down your plug-in's audio processing if nothing is actually being input to the plug-in. On desktop, loading Ridgewalk onto a software instrument's track at all seems to do the trick, but maybe Logic for iPad is further optimized and will shut down your plug-in's audio processing if input stops being sent. I think there's a way to declare your plug-in as having an infinite "tail" (e.g. like an infinite frozen reverb or self-oscillating delay).

@waka_x said:
thanks @aqeelaadam
much better now on my iPad 3.

still- do you support iOS 12.5.7? (iPad air 1)!?
there is a weird bug - the plug mostly works
but Traversal "directions" popup doesnt respond. (forward, wander, etc)
it's dead- non-interactive. Would be cool if you can fix this... I still use that old iPad:)
no problems if you don't...

I'll try to investigate this - I think I have a similar device laying around. It's possible that the software framework that I'm using doesn't support such older devices anymore But I would love to support them if I can. If not, I'll update documentation.

Thanks @aqeelaadam - I guess it could be due to Logic shutting the processing. I can restart the internal play engine within the app to keep the remaining loops going, once Logic stops it, but I'd prefer to keep that processing running if possible. If you know that work-around for Logic, I'll give that a go! Strange that it's inconsistent though...

Just posted another update for iOS which should further improve stability, as well as hopefully helping this issue too. @SilentObserver could you confirm if it's fixed on the latest version whenever you get the chance?

Thanks for this @aqeelaadam! While the app is much more stable, sadly it still stops playing when the channel input stops regardless of the status of Logic playback engine. The only way I can 'fool' the app is by inserting a reverb like Crystalline ahead of Ridgeway. Then the app will continue to play the remaining loops until the Hold Time finishes.

_ki

@aqeelaadam I‘m also wondering a bit about the fade-to-silence behavior when stopping the playhead of the host.

In my AUM jams, i often start with stopped playhead and play some sounds to stack up an ambience, then start the playhead which starts rhytm-machines and sequences. At the end i stop the playhead to stop these rhytms and sequences, but continue playing outros or ambiences.

This doesn‘t work well with the current RidgeWalk, here a simple setup to show the problem:

After loading RW with default patch into an Fx slot of an instrument assigned to AUMs keyboard with stopped AUM playhead, i can play the instrument and RW is wandering around.
This wandering continues, when i‘m starting AUMs playhead. But if i stop the playhead, RW fades to silence in about 2sec even with its default ‚infinite hold time‘ setting.
But any new instrument sound i‘m playing after stopping, receives the RW treatment of wandering echoes…

So if i kind of ‚filled‘ up an intersting soundscape (ie buffer RW is traversing) while playhead is running this soundscape seems lost upon stopping because of the automatic fade-to-silence.

As a work-around i just noticed that if i trigger an RW buffer update by playing a new just loud enough note immediately after stopping AUM, the rest of the buffer is still there. So the buffer doesn‘t seem to be cleared, its output is just faded upon playhead stop.

I would prefer if the audio would keep playing in ‚infinite hold time‘, but at least i now have a work-around

All in all, i really enjoy RidgeWalk ❤️
I already stored several AUM sessions using it with various settings (for instance to create unintelligible vocal snippets by feeding an accepella into a backward playing RW with short size)

aqeelaadam

@SilentObserver said:

@aqeelaadam said:

@SilentObserver said:

@aqeelaadam said:

@SilentObserver said:
@aqeelaadam I'm getting weird performance with Logic iPad. When a midi region, routed through Ridgewalk, finishes, the app stops playing the last loops, even though the track is still playing (and the hold time is quite long).

The odd thing, is that this behaviour is not consistent - sometimes it will continue playing the last loops until the hold time runs out, other times it won't.

Oh interesting. I think I know (roughly) what this issue might be - I'll take a look into it today and release a patch if it's simple enough.

In testing on desktop, Logic seems to be the one DAW that really cares whether or not your "audio effect" is actually producing sound on its own. From Logic's perspective, an audio effect should only produce sound if it's receiving sound, and it'll shut down your plug-in's audio processing if nothing is actually being input to the plug-in. On desktop, loading Ridgewalk onto a software instrument's track at all seems to do the trick, but maybe Logic for iPad is further optimized and will shut down your plug-in's audio processing if input stops being sent. I think there's a way to declare your plug-in as having an infinite "tail" (e.g. like an infinite frozen reverb or self-oscillating delay).

@waka_x said:
thanks @aqeelaadam
much better now on my iPad 3.

still- do you support iOS 12.5.7? (iPad air 1)!?
there is a weird bug - the plug mostly works
but Traversal "directions" popup doesnt respond. (forward, wander, etc)
it's dead- non-interactive. Would be cool if you can fix this... I still use that old iPad:)
no problems if you don't...

I'll try to investigate this - I think I have a similar device laying around. It's possible that the software framework that I'm using doesn't support such older devices anymore But I would love to support them if I can. If not, I'll update documentation.

Thanks @aqeelaadam - I guess it could be due to Logic shutting the processing. I can restart the internal play engine within the app to keep the remaining loops going, once Logic stops it, but I'd prefer to keep that processing running if possible. If you know that work-around for Logic, I'll give that a go! Strange that it's inconsistent though...

Just posted another update for iOS which should further improve stability, as well as hopefully helping this issue too. @SilentObserver could you confirm if it's fixed on the latest version whenever you get the chance?

Thanks for this @aqeelaadam! While the app is much more stable, sadly it still stops playing when the channel input stops regardless of the status of Logic playback engine. The only way I can 'fool' the app is by inserting a reverb like Crystalline ahead of Ridgeway. Then the app will continue to play the remaining loops until the Hold Time finishes.

Ahhh darn. Seems I have more work to do. Thanks for the update @SilentObserver. Just to double check, the potential fix would be v1.0.3 which just went out late yesterday.

@_ki said:
@aqeelaadam I‘m also wondering a bit about the fade-to-silence behavior when stopping the playhead of the host.

In my AUM jams, i often start with stopped playhead and play some sounds to stack up an ambience, then start the playhead which starts rhytm-machines and sequences. At the end i stop the playhead to stop these rhytms and sequences, but continue playing outros or ambiences.

This doesn‘t work well with the current RidgeWalk, here a simple setup to show the problem:

After loading RW with default patch into an Fx slot of an instrument assigned to AUMs keyboard with stopped AUM playhead, i can play the instrument and RW is wandering around.
This wandering continues, when i‘m starting AUMs playhead. But if i stop the playhead, RW fades to silence in about 2sec even with its default ‚infinite hold time‘ setting.
But any new instrument sound i‘m playing after stopping, receives the RW treatment of wandering echoes…

So if i kind of ‚filled‘ up an intersting soundscape (ie buffer RW is traversing) while playhead is running this soundscape seems lost upon stopping because of the automatic fade-to-silence.

As a work-around i just noticed that if i trigger an RW buffer update by playing a new just loud enough note immediately after stopping AUM, the rest of the buffer is still there. So the buffer doesn‘t seem to be cleared, its output is just faded upon playhead stop.

I would prefer if the audio would keep playing in ‚infinite hold time‘, but at least i now have a work-around

All in all, i really enjoy RidgeWalk ❤️
I already stored several AUM sessions using it with various settings (for instance to create unintelligible vocal snippets by feeding an accepella into a backward playing RW with short size)

Hey @_ki - thanks for trying and enjoy! Just to double check, have you tried disabling the playback syncing in the settings menu (top right corner)? By default it's enabled, but you can turn it off and Ridgewalk will ignore AUM's transport.

In the future I'd like to have a preset system and/or "save the current settings as default" option which should like it would useful in your case as well.

_ki

@aqeelaadam 👍🏼 Thanks a lot, disabling host playback sync fixed my problem!
Now that i know, its no problem to change this setting in my saved AUM sessions.

aqeelaadam

@SilentObserver said:

@aqeelaadam said:

@SilentObserver said:

@aqeelaadam said:

@SilentObserver said:
@aqeelaadam I'm getting weird performance with Logic iPad. When a midi region, routed through Ridgewalk, finishes, the app stops playing the last loops, even though the track is still playing (and the hold time is quite long).

The odd thing, is that this behaviour is not consistent - sometimes it will continue playing the last loops until the hold time runs out, other times it won't.

Oh interesting. I think I know (roughly) what this issue might be - I'll take a look into it today and release a patch if it's simple enough.

In testing on desktop, Logic seems to be the one DAW that really cares whether or not your "audio effect" is actually producing sound on its own. From Logic's perspective, an audio effect should only produce sound if it's receiving sound, and it'll shut down your plug-in's audio processing if nothing is actually being input to the plug-in. On desktop, loading Ridgewalk onto a software instrument's track at all seems to do the trick, but maybe Logic for iPad is further optimized and will shut down your plug-in's audio processing if input stops being sent. I think there's a way to declare your plug-in as having an infinite "tail" (e.g. like an infinite frozen reverb or self-oscillating delay).

@waka_x said:
thanks @aqeelaadam
much better now on my iPad 3.

still- do you support iOS 12.5.7? (iPad air 1)!?
there is a weird bug - the plug mostly works
but Traversal "directions" popup doesnt respond. (forward, wander, etc)
it's dead- non-interactive. Would be cool if you can fix this... I still use that old iPad:)
no problems if you don't...

I'll try to investigate this - I think I have a similar device laying around. It's possible that the software framework that I'm using doesn't support such older devices anymore But I would love to support them if I can. If not, I'll update documentation.

Thanks @aqeelaadam - I guess it could be due to Logic shutting the processing. I can restart the internal play engine within the app to keep the remaining loops going, once Logic stops it, but I'd prefer to keep that processing running if possible. If you know that work-around for Logic, I'll give that a go! Strange that it's inconsistent though...

Just posted another update for iOS which should further improve stability, as well as hopefully helping this issue too. @SilentObserver could you confirm if it's fixed on the latest version whenever you get the chance?

Thanks for this @aqeelaadam! While the app is much more stable, sadly it still stops playing when the channel input stops regardless of the status of Logic playback engine. The only way I can 'fool' the app is by inserting a reverb like Crystalline ahead of Ridgeway. Then the app will continue to play the remaining loops until the Hold Time finishes.

@SilentObserver - taking a second pass through the info you provided. Just to clarify, are you saying the Ridgewalk's play/pause setting automatically toggles to pausing when exiting a MIDI region? Or that the audio just stops entirely? Per "I can restart the internal play engine within the app to keep the remaining loops going" it sounds like it's the former - Ridgewalk basically automatically pauses when a MIDI region is complete?

If that's the case, just as a proof of concept, toggling off "playback syncing" the menu would stop that from occurring. That would give me some good data as to whether or not Logic is doing some funky with the transport (I'm reading some stuff claiming that Logic might say the transport is stopped if you're outside of a MIDI region, even though the global transport is still running).

SilentObserver

@aqeelaadam - I think I know what is happening now! The Hold time was somehow set to the length of the midi region, so it stopped playback as no further info audio was occurring. Changing the Hold time to a smaller value or Infinite seems to fix this. I completely overlooked this as it always appeared to stop at the time the midi region did which was totally confusing me!

aqeelaadam

@SilentObserver said:
@aqeelaadam - I think I know what is happening now! The Hold time was somehow set to the length of the midi region, so it stopped playback as no further info audio was occurring. Changing the Hold time to a smaller value or Infinite seems to fix this. I completely overlooked this as it always appeared to stop at the time the midi region did which was totally confusing me!

A-ha! Glad to know it's all good. You bringing up the issue helped me realize/notice some other issues though, so glad you brought it up

aqeelaadam

Not iOS related, but I just posted a desktop update as well. I'm doing desktop updates ~weekly since they're a bit more painful for me to issue and for people to install (compared to iOS). This basically gets all of the critical stability updates to desktop users as well.

abf

@aqeelaadam Thank you for the desktop update! I will check it out tomorrow. I'm looking forward to it!