It was mentioned in the mega thread that SA is (or will be) working on a new version of the Neuro App. A consolidated thread of wantsies might be useful. Many or all of these issues may already be on the road map for the new software. For the record, I’m a lightweight Neuro user, with only one pedal (an Aftershock).
1) Edit patches in the cloud directly. Currently, when editing a patch from the user library, it has to be selected and loaded into temporary memory, then edited, then before it can be saved to the cloud, it has to be burned to a slot on the pedal, and then saved to the cloud from there. There is also no intelligence for overwriting existing patches with the same name, it just always creates a new patch, which requires going back and manually deleting the old one from the user library.
2) Library organization. User patches are currently just a long list that at some point spills over to another page. Folders would be an improvement. And the ability to re-order patches in the user library, preferably by drag and drop. And when selecting the cloud tab, the user’s own library should be the default view, not the community patches, because bless their hearts, but really, most them aren’t, um, “optimal for my use case”.
3) More efficient screen layout. See the attached screenshot for the Aftershock. There’s a lot of unused space, which requires unnecessary scrolling to access controls. The control groups (left channel, right channel, parametric EQ, etc…) could arrange dynamically into smarter columns, based on available screen size. This is easy to see with the Aftershock because it has limited controls. Other pedals with more extensive controls wouldn’t be as flexible. This may also be a real headache in terms of programming resources.
4) Double click to reset default value. Or some other shortcut to reset a control to it’s default value instead of dragging the control or manually entering a number.
5) Onboard documentation. Some explanation of the function of the controls, even an abbreviated one, should be readily accessible in the program itself. An “i in a circle” info button, or something. Definitely not a post in a blog somewhere.
6) Landscape mode. That the iPad app doesn’t support landscape mode is a gross abomination against God.
That’s it for me, and thanks to the people at Source Audio for being accessible and open to customer feedback.
1) Edit patches in the cloud directly. Currently, when editing a patch from the user library, it has to be selected and loaded into temporary memory, then edited, then before it can be saved to the cloud, it has to be burned to a slot on the pedal, and then saved to the cloud from there. There is also no intelligence for overwriting existing patches with the same name, it just always creates a new patch, which requires going back and manually deleting the old one from the user library.
2) Library organization. User patches are currently just a long list that at some point spills over to another page. Folders would be an improvement. And the ability to re-order patches in the user library, preferably by drag and drop. And when selecting the cloud tab, the user’s own library should be the default view, not the community patches, because bless their hearts, but really, most them aren’t, um, “optimal for my use case”.
3) More efficient screen layout. See the attached screenshot for the Aftershock. There’s a lot of unused space, which requires unnecessary scrolling to access controls. The control groups (left channel, right channel, parametric EQ, etc…) could arrange dynamically into smarter columns, based on available screen size. This is easy to see with the Aftershock because it has limited controls. Other pedals with more extensive controls wouldn’t be as flexible. This may also be a real headache in terms of programming resources.
4) Double click to reset default value. Or some other shortcut to reset a control to it’s default value instead of dragging the control or manually entering a number.
5) Onboard documentation. Some explanation of the function of the controls, even an abbreviated one, should be readily accessible in the program itself. An “i in a circle” info button, or something. Definitely not a post in a blog somewhere.
6) Landscape mode. That the iPad app doesn’t support landscape mode is a gross abomination against God.
That’s it for me, and thanks to the people at Source Audio for being accessible and open to customer feedback.
