Continua by Audiodamage (iOS)

DCJ

@dendy said:

• no noticeable "stepping" even during very slow tweaks (tested on filter cutoff with high resonance)

I am absolutely getting stepping on fast manual filter movement. Strange that you’re not getting the same.

palms

I grabbed Continua against my better judgement. I saw that it supported TUN microtuning. I will support ANY developer who adds microtonal support to their instruments.

But just like Quanta, the microtuning is broken right out the gate. (Try loading a different tuning and see what happens...) I thought that surely they wouldn't pull the exact same thing they did last time. Quanta microtuning still does not work.

First time I've ever requested a refund. I contacted him directly regarding microtuning with quanta when it first came out and at first he said he would absolutely fix it "in the next few days". months passed. I contacted him again and he basically said that since nobody uses microtuning, that it was low priority.
Well, then maybe don't advertise that it is microtunable?? I fell for it again and now I'm done with Audio Damage. I get that apps are often buggy when they first get released. But their track record is pretty good with a bunch of cool "looking" apps, that are full of bugs that never really get resolved.

Yes, the gui looks slick, but with Continua I was very underwhelmed by the synth engine itself. I like everything about this synth in theory, but it just doesn't perform as well as it looks. The envelopes are fidgety, and I agree with others: the mod matrix in Quanta is awesome, not sure why they went this route.

bcrichards

@palms said:

@hibjshop said:
The Sugarbytes blessings continue!
Im still learning Factory, discovering new sounds, enjoying its MASSIVE depth and they drop yet another synth.
Total Gratitude🤙🏼

? I can't tell if this is a joke..

this synth is by Audio Damage

#wakeup #sugarbytesdidcontinua

bcrichards

Deleted

eross

Anybody else notice dead notes when playing the keyboard. If I play with external midi it work fine. But in app keys only register finger presses about 50% of the time. Also I turned of MPe in settings and it still does it.

palms

@bcrichards said:

@palms said:

@hibjshop said:
The Sugarbytes blessings continue!
Im still learning Factory, discovering new sounds, enjoying its MASSIVE depth and they drop yet another synth.
Total Gratitude🤙🏼

? I can't tell if this is a joke..

this synth is by Audio Damage

#wakeup #sugarbytesdidcontinua

🤣

ohwell

Anyone managing to get Continua to behave on an air 2? On mine it feels plain unusable...

EDIT (thanks to comments further down in thread): Turns out the AUv3 works well on Air 2 (at least within AUM, and in non-mpe mode). It still misses half of the notes from the lightpad (seems like an MPE issue as described by other users.) Standalone mode remains unusable for me: I get intermitent, inconsistent response—including with the internal keyboard.

skiphunt

Ugh 😩 I was looking forward to picking this up tonight. Sounds like there’s a lot of issues and disappointment?

Anyone with an iPad Pro 10.5 or better... running 13.3 and having no problems with Continua? And loving it?

I can take the rare crackle, but it sounds like some are having a lot of functionality issues. Can’t tell if that’s due more to older hardware and older iOS versions.

craftycurate

Continua patch Browser tips, to help circumvent some of its frustrations in its current implementation:

1. If you do not add a folder name, patches are saved in the root folder. This is quite unexpected (why not default to the User folder??) but it’s how it works at the time of writing. You will need to add the folder name EVERY TIME you save a patch. Gaaah!

2. To Save current patch to same name (i.e. Save not Save As) e.g. when you’re working on a patch and want to save regularly, an easy way is:

• Create the file name (including folder - see point #1) in some note taking app
• Copy to clipboard.
• Click Save in file browse
• Delete “Default” (it will always be Default when you click Save)
• Paste in your file name, and then hit Save

So your file name string might be e.g.

User/PAD Bladerunner

This way you don’t have to remember what you called the patch or where you saved it, or type it all in every time. It’s faster and less error prone.

3. You can scroll the browser patch list by swiping on it, but be aware that this will select the patch where your finger touches the screen to begin swiping. I hope this will be fixed in an update.

4. The only way to move a patch is to load it, and save it to the new location using steps 1 & 2 above.

5. Be really careful if you are editing a patch and go to save it. If you accidentally click on a patch name in the browser (very easy to do by mistake as the scroll bar is so thin) you will instantly load that patch and lose all your work without recall. Best to save it right away.

[Deleted User]

@hibjshop said:
The Sugarbytes blessings continue!
Im still learning Factory, discovering new sounds, enjoying its MASSIVE depth and they drop yet another synth.
Total Gratitude🤙🏼

I think I’ll still be learning Factory and Aparillo when Drum Computer drops!

But, this one belongs to Audio Damage, not Sugar Bytes.

[Deleted User]

@palms said:

@hibjshop said:
The Sugarbytes blessings continue!
Im still learning Factory, discovering new sounds, enjoying its MASSIVE depth and they drop yet another synth.
Total Gratitude🤙🏼

? I can't tell if this is a joke..

this synth is by Audio Damage

Maybe it is a joke. Albeit an abstract, cryptic one that goes above my head.

[Deleted User]

The user and all related content has been deleted.

RedSkyLullaby

@JohnnyGoodyear said:

@reasOne said:
@RedSkyLullaby , really digging your sounds!!

I'm buyer anyway, but anything with the application of Red Sky Sauce gets an autopurchase just to see what he's up to.

Thanks gents

RedSkyLullaby

@skiphunt said:
Ugh 😩 I was looking forward to picking this up tonight. Sounds like there’s a lot of issues and disappointment?

Anyone with an iPad Pro 10.5 or better... running 13.3 and having no problems with Continua? And loving it?

I can take the rare crackle, but it sounds like some are having a lot of functionality issues. Can’t tell if that’s due more to older hardware and older iOS versions.

Its fine on 13.3. Im on 2017 10.5 pro and had no issues and i dug pretty deep while designing presets. The effects are really good especially the reverb

skiphunt

@RedSkyLullaby said:

@skiphunt said:
Ugh 😩 I was looking forward to picking this up tonight. Sounds like there’s a lot of issues and disappointment?

Anyone with an iPad Pro 10.5 or better... running 13.3 and having no problems with Continua? And loving it?

I can take the rare crackle, but it sounds like some are having a lot of functionality issues. Can’t tell if that’s due more to older hardware and older iOS versions.

Its fine on 13.3. Im on 2017 10.5 pro and had no issues and i dug pretty deep while designing presets. The effects are really good especially the reverb

That’s good enough for me. Thanks 😊

RedSkyLullaby

@JohnnyGoodyear said:
anything with the application of Red Sky Sauce gets an autopurchase just to see what he's up to.

Been spending alot of time down Endlesss beta rabbit hole

sclurbs

@eross said:
Anybody else notice dead notes when playing the keyboard. If I play with external midi it work fine. But in app keys only register finger presses about 50% of the time. Also I turned of MPe in settings and it still does it.

Using a linnstrument. What I'm dealing with is that only channels 1-7 are producing noise. 8-16 do nothing.

DCJ

It also sucks that you can’t easily reset parameters to default (e.g., fine tune). Desktop is double click. On iOS double tapping will only get you the matrix. Would have been a great use of the long press, no? Maybe I’m missing something.

rs2000

@DCJ said:
It also sucks that you can’t easily reset parameters to default (e.g., fine tune). Desktop is double click. On iOS double tapping will only get you the matrix. Would have been a great use of the long press, no? Maybe I’m missing something.

Agreed. I'd do a double tap for reset, tap-hold for modulation. It doesn't make much sense to do UI gestures different from de-facto standards, and tap-hold for opening the mod editor seems intuitive to me.

ohwell

@sclurbs said:

@eross said:
Anybody else notice dead notes when playing the keyboard. If I play with external midi it work fine. But in app keys only register finger presses about 50% of the time. Also I turned of MPe in settings and it still does it.

Using a linnstrument. What I'm dealing with is that only channels 1-7 are producing noise. 8-16 do nothing.

I seem to be getting this kind of behavior with the lightpad. But also ..... with the in app keyboard?!?!

I don't know how much of my experience is due to the air 2, but this feels like a promising, beautifully designed product that was rushed through testing and sloppily optimized.

Is there a way to turn off the animations for the modulators? (Would likely help performance on older devices...)

Also, is there a way to just reset the FEG? (Deleting each loop point can get awkward on touch screen.)

skiphunt

Bought it. Been playing with it for a little over an hour. iPad Pro 10.5 iOS 13.3

Mostly in standalone mode but som as AU in apeMatrix.

Occasional sticky interface, but otherwise problem-free so far. Love the sound. Easy to get going and the interface is fairly intuitive. The modulation routing works similar to Shockwave. Still plenty to explore but thrilled with it thus far.

[Deleted User]

@palms said:
I grabbed Continua against my better judgement. I saw that it supported TUN microtuning. I will support ANY developer who adds microtonal support to their instruments.

But just like Quanta, the microtuning is broken right out the gate. (Try loading a different tuning and see what happens...) I thought that surely they wouldn't pull the exact same thing they did last time. Quanta microtuning still does not work.

First time I've ever requested a refund. I contacted him directly regarding microtuning with quanta when it first came out and at first he said he would absolutely fix it "in the next few days". months passed. I contacted him again and he basically said that since nobody uses microtuning, that it was low priority.
Well, then maybe don't advertise that it is microtunable?? I fell for it again and now I'm done with Audio Damage. I get that apps are often buggy when they first get released. But their track record is pretty good with a bunch of cool "looking" apps, that are full of bugs that never really get resolved.

Yes, the gui looks slick, but with Continua I was very underwhelmed by the synth engine itself. I like everything about this synth in theory, but it just doesn't perform as well as it looks. The envelopes are fidgety, and I agree with others: the mod matrix in Quanta is awesome, not sure why they went this route.

Yep i had the same experience, something broken in quanta, chris says he will absolutely fix it and never did because for some reason correct pitch is not an issue to him if the majority of users dont notice it. Will never buy his apps again.

dendy

@DCJ said:

@dendy said:

• no noticeable "stepping" even during very slow tweaks (tested on filter cutoff with high resonance)

I am absolutely getting stepping on fast manual filter movement. Strange that you’re not getting the same.

Ah i was trying very slow tweak - usually synths with no smooting have stepping when you do slow tweaks, as a result of low resolution of knob. Confirming that with fast tweak, there is stepping

zeropoint

@craftycurate said:
Continua patch Browser tips, to help circumvent some of its frustrations in its current implementation:

1. If you do not add a folder name, patches are saved in the root folder. This is quite unexpected (why not default to the User folder??) but it’s how it works at the time of writing. You will need to add the folder name EVERY TIME you save a patch. Gaaah!

2. To Save current patch to same name (i.e. Save not Save As) e.g. when you’re working on a patch and want to save regularly, an easy way is:

• Create the file name (including folder - see point #1) in some note taking app
• Copy to clipboard.
• Click Save in file browse
• Delete “Default” (it will always be Default when you click Save)
• Paste in your file name, and then hit Save

So your file name string might be e.g.

User/PAD Bladerunner

This way you don’t have to remember what you called the patch or where you saved it, or type it all in every time. It’s faster and less error prone.

3. You can scroll the browser patch list by swiping on it, but be aware that this will select the patch where your finger touches the screen to begin swiping. I hope this will be fixed in an update.

4. The only way to move a patch is to load it, and save it to the new location using steps 1 & 2 above.

5. Be really careful if you are editing a patch and go to save it. If you accidentally click on a patch name in the browser (very easy to do by mistake as the scroll bar is so thin) you will instantly load that patch and lose all your work without recall. Best to save it right away.

Admit it’s a poor/confusing implementation. But you don’t need all the above. To save the same patch to the same location, select the current patch name in the browser first, then press Save. Now you can save to the original location without specifying folders and sub folders . To save a copy just rename in the dialog.

[Deleted User]

@ohwell said:

@sclurbs said:

@eross said:
Anybody else notice dead notes when playing the keyboard. If I play with external midi it work fine. But in app keys only register finger presses about 50% of the time. Also I turned of MPe in settings and it still does it.

Using a linnstrument. What I'm dealing with is that only channels 1-7 are producing noise. 8-16 do nothing.

I seem to be getting this kind of behavior with the lightpad. But also ..... with the in app keyboard?!?!

I don't know how much of my experience is due to the air 2, but this feels like a promising, beautifully designed product that was rushed through testing and sloppily optimized.

Is there a way to turn off the animations for the modulators? (Would likely help performance on older devices...)

Also, is there a way to just reset the FEG? (Deleting each loop point can get awkward on touch screen.)

Not working well on Air 2? I’ll stay on the fence a bit longer.

cuscolima

I am always surprised that after years of iOS apps delivery, people are still complaining that a new app doesn't work perfectly. I think that it is part of the deal. You have a good product for a very small amount of money but you have to be a little bit patient and proactive. Initial bugs will be solved soon. Cracks and pops aren't normal and will be solved because it has an impact on a lot of people (don't forget to send a notification to the dev). I understand the frustration with the micro tuning bug. However, if the dev has received only a few complaints about this issue, then it won't be prioritised. People with commun troubles have to discuss and agreed that all of them have to send a notification.

palms

@bcrichards said:

@palms said:

@hibjshop said:
The Sugarbytes blessings continue!
Im still learning Factory, discovering new sounds, enjoying its MASSIVE depth and they drop yet another synth.
Total Gratitude🤙🏼

? I can't tell if this is a joke..

this synth is by Audio Damage

#wakeup #sugarbytesdidcontinua> @cuscolima said:
I am always surprised that after years of iOS apps delivery, people are still complaining that a new app doesn't work perfectly. I think that it is part of the deal. You have a good product for a very small amount of money but you have to be a little bit patient and proactive. Initial bugs will be solved soon. Cracks and pops aren't normal and will be solved because it has an impact on a lot of people (don't forget to send a notification to the dev). I understand the frustration with the micro tuning bug. However, if the dev has received only a few complaints about this issue, then it won't be prioritised. People with commun troubles have to discuss and agreed that all of them have to send a notification.

When there's a pattern, people will take notice. The pattern with AD seems to be: fix a few initial bugs and then call it a day.

I understand low priority. in this case it is no priority (in that it's unlikely to ever get fixed).. and to do it again with a new app.. it's insult to injury. you can only burn your customers so many times.

[Deleted User]

@palms said:

@bcrichards said:

@palms said:

@hibjshop said:
The Sugarbytes blessings continue!
Im still learning Factory, discovering new sounds, enjoying its MASSIVE depth and they drop yet another synth.
Total Gratitude🤙🏼

? I can't tell if this is a joke..

this synth is by Audio Damage

#wakeup #sugarbytesdidcontinua> @cuscolima said:
I am always surprised that after years of iOS apps delivery, people are still complaining that a new app doesn't work perfectly. I think that it is part of the deal. You have a good product for a very small amount of money but you have to be a little bit patient and proactive. Initial bugs will be solved soon. Cracks and pops aren't normal and will be solved because it has an impact on a lot of people (don't forget to send a notification to the dev). I understand the frustration with the micro tuning bug. However, if the dev has received only a few complaints about this issue, then it won't be prioritised. People with commun troubles have to discuss and agreed that all of them have to send a notification.

When there's a pattern, people will take notice. The pattern with AD seems to be: fix a few initial bugs and then call it a day.

I understand low priority. in this case it is no priority (in that it's unlikely to ever get fixed).. and to do it again with a new app.. it's insult to injury. you can only burn your customers so many times.

yep, summed up perfectly, it a business strategy to get the app out and move on to the next app quick as possible. Price is low so who cares.

Also the pitch issue on Quanta is a big mistake even if people don't notice it, stills makes the app unusable for a project. That particular issue has been known by dev for over a year.

[Deleted User]

@cuscolima said:
I am always surprised that after years of iOS apps delivery, people are still complaining that a new app doesn't work perfectly.

You call it complaining, I call it useful information. Knowing that an app isn't going to work as I expect it to saves me from disappointment - and as someone with an older device, performance of newer apps can sometimes be an issue.

Unjustified dev bashing is obviously a bad thing, but constructive feedback that covers the pros and cons is helpful to all of us. Otherwise we'd all buy a new app totally unaware of any issues, and the dev instead would be hit by bad store reviews and refunds. Better to iron them out on here and get feedback from trusted members.

Philandering_Bastard

@ohwell said:
Anyone managing to get Continua to behave on an air 2? On mine it feels plain unusable...

Working fine here on 13.3

Under ‚Settings‘ you could try to set the ‚Modulation Downsampling‘ parameter to 32. That might help although I do not seem to have issues at 8.