• TalkBass has been independent since 1998. Add your voice.
    Create a free account to reply to discussions, view embedded media, and browse with fewer display ads.
    Join freeLog in
    Want zero display ads or expanded classifieds tools? Compare plans.

Source Audio Neuro App improvement thread

More problems with the Atlas: the min/max boundaries appear to do nothing in the app. And again, the attack/release times are completely different to those in Neuro 2; here is me adjusting the attack/release on the same preset (Cubic Zirconia Bass) on Neuro 2 and 3:

Neuro 2:

Neuro 3:

Thank you for sharing. Looks like a decimal place issue.
 
  • Like
Reactions: Killerfridge
With the loss of edit resolution caused by Neuro 3, it is not just dumbing down the app & pedals, but also diluting the adjustability.

Another possible solution would be to just add a secondary display value so when the virtual on-screen knob is rubbed in a rotating manner, it shows values in this sequence:

0% 0, 0% 1, 0% 2, 0% 3,... 25% 64, 25% 65, 25% 66,... 50% 128 ... 75% 192 ... 100% 255.

Specifically, you'd have the exact 8-bit decimal value either smaller or in parenthesis, and the nearest percentage displayed in bold. And the percentage value would change less frequently than the 8-bit value as turned. A preference to show/hide one or the other could be added.

SHOW VALUE AS: PERCENT, 8-BIT VALUE, BOTH

I realize by voicing all this, I too am a "complainer". I assure you this comes from a place of respect.

As a LONG-TIME Kurzweil user, I've always valued professional (not-for-casual-user) products that don't insult my intelligence, or strip away features out of fear that I'm too dumb to know how to use it. Source Audio makes mind-blowing gear that not only hands you the keys, but pops-the-hood and says get in there. I love that about Source Audio gear.
 
With the loss of edit resolution caused by Neuro 3, it is not just dumbing down the app & pedals, but also diluting the adjustability.

Another possible solution would be to just add a secondary display value so when the virtual on-screen knob is rubbed in a rotating manner, it shows values in this sequence:

0% 0, 0% 1, 0% 2, 0% 3,... 25% 64, 25% 65, 25% 66,... 50% 128 ... 75% 192 ... 100% 255.

Specifically, you'd have the exact 8-bit decimal value either smaller or in parenthesis, and the nearest percentage displayed in bold. And the percentage value would change less frequently than the 8-bit value as turned. A preference to show/hide one or the other could be added.

SHOW VALUE AS: PERCENT, 8-BIT VALUE, BOTH
This I would sustain. Alternatively, impletment a configurarion settings we "advanced" users may activate that would provide said functionality.
 
  • Like
Reactions: 5stringedfrenzy
With the loss of edit resolution caused by Neuro 3, it is not just dumbing down the app & pedals, but also diluting the adjustability.

Another possible solution would be to just add a secondary display value so when the virtual on-screen knob is rubbed in a rotating manner, it shows values in this sequence:

0% 0, 0% 1, 0% 2, 0% 3,... 25% 64, 25% 65, 25% 66,... 50% 128 ... 75% 192 ... 100% 255.

Specifically, you'd have the exact 8-bit decimal value either smaller or in parenthesis, and the nearest percentage displayed in bold. And the percentage value would change less frequently than the 8-bit value as turned. A preference to show/hide one or the other could be added.

SHOW VALUE AS: PERCENT, 8-BIT VALUE, BOTH

I realize by voicing all this, I too am a "complainer". I assure you this comes from a place of respect.

As a LONG-TIME Kurzweil user, I've always valued professional (not-for-casual-user) products that don't insult my intelligence, or strip away features out of fear that I'm too dumb to know how to use it. Source Audio makes mind-blowing gear that not only hands you the keys, but pops-the-hood and says get in there. I love that about Source Audio gear.
We just spent 30 minutes discussing this topic and trying to come up with a solution. While this may seem like a really simple thing, it is not. We have created a knob model that is used across all pedals and then gets replicated across all of the platforms when doing a new build. It is very complicated and expensive to make a change such as you suggest. Even moving back to 255 is challenging. With that said, we are going to try in a future release.
 
  • Like
Reactions: LSMFT6
The decision to go all-in, irreversibly, on a percentage display that reduces edit resolution was indeed unfortunate. Alas. Is the existence of negative-zero and zero dB also something that exists across the entire range and is therefore not fixable?

I suppose new users who don't know that the extra adjustability is no longer available, won't miss it. And people who mix with their eyes will probably be cool, as well. I've made enough stink about it, and it seems like I'm alone on this particular hill.

For Android, even if one has updated to the new version, there is at least a path to downgrade to the older version (via apk side-load). I never updated my Android tablet so I still have access to the older version. I don't know what the final version number was for Android. Confusingly, the OLD Neuro is version 3.4.1 (?)

For Mac, I can try to keep using the old version.

For iOS, I'm stuck with the new version and there's no going back.

BTW, check the Ultrawave UI on iOS on an iPhone 13. Lots things are unreadable, abbreviated unrecognizably, or cut-off.
 
  • Like
Reactions: 5stringedfrenzy
The decision to go all-in, irreversibly, on a percentage display that reduces edit resolution was indeed unfortunate. Alas. Is the existence of negative-zero and zero dB also something that exists across the entire range and is therefore not fixable?

I suppose new users who don't know that the extra adjustability is no longer available, won't miss it. And people who mix with their eyes will probably be cool, as well. I've made enough stink about it, and it seems like I'm alone on this particular hill.

For Android, even if one has updated to the new version, there is at least a path to downgrade to the older version (via apk side-load). I never updated my Android tablet so I still have access to the older version. I don't know what the final version number was for Android. Confusingly, the OLD Neuro is version 3.4.1 (?)

For Mac, I can try to keep using the old version.

For iOS, I'm stuck with the new version and there's no going back.

BTW, check the Ultrawave UI on iOS on an iPhone 13. Lots things are unreadable, abbreviated unrecognizably, or cut-off.
Actually, that was the 3.0 dealbreaker for me too. Fortuanately version 2 still works fine on my Windows machine, and hopefully there'll be a fix in the future. It seems odd to drop below the 128 steps we've been using with MIDI for 40+ years. On the bright side, if I never update the pedals they'd still be worth every penny in thier current state.
 
Last edited:
Actually, the native resolution is twice that, at 256 steps (0-255), so MIDI control (hopefully still) is an easy conversion to half-resolution. But some users complained that this range & resolution was not "relatable"
Jesse just shared the following:
" one thing I just checked. If you use the arrow keys to move the knob incrementally which I do a lot, there are only 128 positions covering the full range."

Perhaps we can build on this concept to get what you need for the very particular times when you need it.

We are trying our best to be responsive. We are not lacking technical skills. We are not lazy. We are not deaf to customer input. You are engaging with the leader of the company.
 
Jesse just shared the following:
" one thing I just checked. If you use the arrow keys to move the knob incrementally which I do a lot, there are only 128 positions covering the full range."

Perhaps we can build on this concept to get what you need for the very particular times when you need it.

We are trying our best to be responsive. We are not lacking technical skills. We are not lazy. We are not deaf to customer input. You are engaging with the leader of the company.
If exact 8-bit values could be typed in, and a 10ths place was added to the percentage, that would certainly help. Hopefully, this can be implemented in both the desktop & mobile version.

I understand you are neither lazy or lacking skills. I actually think you're probably some of the nicest people in the biz. My delivery of this criticism has been hard for me, because I do respect and appreciate you all very much.

If I was in your shoes, and people were bitching about 8-bit values, I'd try to educate them-- and write a convincing blurb about why.
 
  • Like
Reactions: rsmith601