On the other hand if it is still the same software then better keep the same generation number. 4 would mean something new, not just an improvement.
Enjoy the benefits of a premium membership!
Upgrade Account
-
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 free Log in
Want zero display ads or expanded classifieds tools? Compare plans.
We (Source Audio) released Neuro 3 too early. We're sorry!
- Thread starter rsmith601
- Start date
- Status
It might be a way to say “no more betas, this is production, and what will be supported going forward”.
It still smells like beta, at best, though.
It still smells like beta, at best, though.
Looking at the version history for the old Neuro Mobile app, it shows as version 3, even four years ago.
I wouldn't get too hung up on the numerics of what the app versions are/were called.
We are referring to Neuro 3 as Neuro 3 because it's the third generation of Neuro. Neuro 1 is what you see in older One Series manual screenshots like the Gemini manual for instance. The dark gray, primitive-looking mobile format. Neuro 2 is the first generation that introduced a desktop editor. Neuro 2 can be found in something like the Atlas Compressor manual for instance (not for much longer, I'll be updating all the One Series manuals to reference Neuro 3 in the coming weeks).
Neuro 3 is what we have now; the blacked-out UI and parity between mobile and desktop versions.
We are referring to Neuro 3 as Neuro 3 because it's the third generation of Neuro. Neuro 1 is what you see in older One Series manual screenshots like the Gemini manual for instance. The dark gray, primitive-looking mobile format. Neuro 2 is the first generation that introduced a desktop editor. Neuro 2 can be found in something like the Atlas Compressor manual for instance (not for much longer, I'll be updating all the One Series manuals to reference Neuro 3 in the coming weeks).
Neuro 3 is what we have now; the blacked-out UI and parity between mobile and desktop versions.
I must not be describing this right.
The OLD version of Neuro Mobile was version 3. The NEW version of Neuro Mobile is also version 3. Probably won't cause any issues; but I imagine someone saying, "no need for me to update. I'm already on 3"
The OLD version of Neuro Mobile was version 3. The NEW version of Neuro Mobile is also version 3. Probably won't cause any issues; but I imagine someone saying, "no need for me to update. I'm already on 3"
Now you are mixing two things. 3 means generation of software, but inside of it there is different versions like 3.5.5 and older 3.4.x. etc.
Windows 11 had multiple updates and still maintaining the 11.
All this is basic software structure. You need to go to correct setting in menu ("about" in many software) to get the exact version number.
I understand. We have many ways of helping users find out if they are on the right version. If they are lost at the mobile version number starting with 3, we will help them identify the numbers after the decimal and make sure they line up.
What I am saying is that we are boldly referring to the new generation of Neuro as Neuro 3 which is a top-level distinction that hasn't been done by us before.
Probably mobile and desktop app versions are not directly comparable, because they are two different applications even they are under the same Neuro naming, and version numbers have separate paths. I would say both have equal features released at the same time, no matter what are the version numbers.Um. Ok, I think I get it.
So 3.2.xx is the old mobile version, from 4 years ago. And mobile is 3.55 and above is the bold new Neuro 3.
And desktop 3.0.20 is newer than mobile 3.2.xx.
That makes perfect sense.
Last edited:
If the number is called is the biggest bug you've found the guys at SA have done their product revisions well!Um. Ok, I think I get it.
So 3.2.xx is the old mobile version, from 4 years ago. And mobile is 3.55 and above is the bold new Neuro 3.
And desktop 3.0.20 is newer than mobile 3.2.xx.
That makes perfect sense.
- Apr 14, 2009
- 4,461
- 8,356
- Disclosures
- CEO and Co-Founder, Source Audio
The version numbers were never intended to communicate marketing information. They are technical in nature. As it happens, I am on version 128.0.2739.67 of my browser, which is meaningless to me. I note that the Android and iOS current versions of this browser do not start with 128 either. To say we are out of step with the industry on version nomenclature is not correct.Um. Ok, I think I get it.
So 3.2.xx is the old mobile version, from 4 years ago. And mobile is 3.55 and above is the bold new Neuro 3.
And desktop 3.0.20 is newer than mobile 3.2.xx.
That makes perfect sense.
You are right, we should have called Neuro 3 something more meaningful such as "Neuro 3G", because that is what it is: the 3rd generation of Neuro. I was the one who started calling it Neuro 3.0 way back when we started talking about it. This was a mistake, but it's too late to change it at this point and I am not sure its where we should focus our resources.
I am also not inclined to force the engineering team to change their nomenclature to satisfy the needs of the marketing department. We are an engineering company, and I intend to keep it that way.
Let's not get ahead of ourselves.
The previous incarnation of Neuro Mobile was at version 3.2.72, and the previous version of the desktop Neuro was 0.8.86. In this latest update, the desktop version moved up to 3.x, and the mobile version stayed at 3, but moved up to 3.55. That's not a big deal. Just was confused because I hadn't needed to pay attention to it before. Most users who update the mobile app via the App Store won't have to pay attention either. Because I side-load the apk on my android device, I had to double check the version numbering.
Let's not get ahead of ourselves.
The previous incarnation of Neuro Mobile was at version 3.2.72, and the previous version of the desktop Neuro was 0.8.86. In this latest update, the desktop version moved up to 3.x, and the mobile version stayed at 3, but moved up to 3.55. That's not a big deal. Just was confused because I hadn't needed to pay attention to it before. Most users who update the mobile app via the App Store won't have to pay attention either. Because I side-load the apk on my android device, I had to double check the version numbering.
At least they kept the numbers increasing.
I recall dealing with software that reset their numbers when they did the next versions:
Software - 1.0 -> 3.0
Software2 - 1.0 ....
IIRC, Izotope released their last version of an 12 year old (?) plugin, Trash 2, in late 2022. Then, in 2023, released a major upgrade "Trash" (not "Trash 3") a completely new version of that plugin. And re-started the versioning at 1.0
I gave up on understanding version numbers 15 years ago. Once they got past two decimal points, I gave up.
Yes-this! I thought it was me doing something wrong or using the wrong connector. UW Bass newbie
Seems like everyday something on the App doesn’t work right, or is different. Seriously considering ditching my C4 and going back to analog. What a clusterF.
I'll be honest and say that I'm considering ditching my Ultrawave, but not because I don't thing SA can't fix the app issues because that I think they can.
It's the documentation. There is a *lot* of configuration options going on in this pedal and while the documentation give a very brief overview, it's not enough for my relatively new mind to the platform (and bass). Add that I'm highly analytical, and I want more to understand interactions. Even a SA supplied tutorial - in print - would help as reference to understand how things are interacting.
As simple example of this is the drive knob - there is two of them active by default on the Ultrawave (one under master, and one under distortion in the blue box). Which one matters? How do they interact? And then the multiband is a percentage of that or it's own thing on top of those?
If I was younger, I'd have more time and more inclined to play with stuff and learn it. At this point, I just want to read and understand the controls so I can plan and then play.
It's the documentation. There is a *lot* of configuration options going on in this pedal and while the documentation give a very brief overview, it's not enough for my relatively new mind to the platform (and bass). Add that I'm highly analytical, and I want more to understand interactions. Even a SA supplied tutorial - in print - would help as reference to understand how things are interacting.
As simple example of this is the drive knob - there is two of them active by default on the Ultrawave (one under master, and one under distortion in the blue box). Which one matters? How do they interact? And then the multiband is a percentage of that or it's own thing on top of those?
If I was younger, I'd have more time and more inclined to play with stuff and learn it. At this point, I just want to read and understand the controls so I can plan and then play.
We were a bit too "public" with our beta app testing. We should have waited for a 100% polished version before releasing the update. I'm very sorry for the inconveniences this update process has led to. A big part of it was budding frustration of not being able to release new products for a couple years straight due to parts shortages.
Hey there, I wrote the user guide and the blog post that Luke replied to you with, as well as the paper about Distortion Types (linked below) talking about the distortion types. I'm not out to defend the work here, I just want to learn what else you need in terms of documentation for this pedal.
User Guide: [Invalid or Expired Link Removed]
Distortion Type Lexicon: [Invalid or Expired Link Removed]
Editor Deep Dive: [Invalid or Expired Link Removed]
- Status
