• 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 Sorcerers Society (S.A.S.S) Part 3

Am I being stupid

I’m in the desktop app… I fiddle with settings and now want to save them and burn them to the c4 …. Am I missing something obvious?

I can easy find someone else’s patch and burn it, I can download into my library - but I don’t know how the edit - save - burn function is supposed to work!! I equalised the volume on my patches a few months back so I obviously worked it out then - but think I used the mobile app
Make sure you have :"device" selected in the upper right corner and not "cloud". This will show all of the preset locations. 000 to 006 are the toggle switch presets.
 
  • Like
Reactions: Luke the Fluke
@Gibs210

Perhaps the issue is that Mobile Neuro has some unfinished business.

The Mobile Neuro for Ventris shows knob assigns: Control 1...5, and Soft Control with no explanation. The Engine Specific parameters aren't even labeled as Engine-Specific, much less numbered in any way, much less referring to "control 1", etc. Yes, a person could do some guess work and randomly assign a knob to Control 5 and see what happens (which might be nothing). That's not self-explanatory.

A while back, on the Neuro app thread, I was suggesting that SA take steps to make sure the terminology amongst the Desktop App, Mobile App, and the manual was consistent, try to use terms that avoid ambiguity, and when not possible, offer a proper explanation in the manual. Beta testers with fresh eyes might spot things.
 
Last edited:
I think we’re getting into dead horse territory a little bit, on “how not to do it going forward”. The new app is a re-write from the ground up. Roger has said they put more R&D into it than the previous versions combined. A lot of the issues we’re talking about are artifacts of the “just one more thing” nature of SA’s development cycle. The current products are well established and feature-mature, and I expect Neuro 3.0 will show that in its completeness and consistency.
 
You're right, and I'm admittedly very late to this party.

The only thing I wish they would change in the pedal firmware would be to add the ability to assign parameters to knobs on the "mod squad" (Gemini, Lunar, and Mercury) so that they truly are "all the same pedal with different paint-job."

Clarifying what is missing, conflicting and/or confusing within the Mobile & Desktop Neuro and documentation would no doubt be a big project. Hoping Neuro 3.0 will clarify as much as possible.
 
Last edited:
Make sure you have :"device" selected in the upper right corner and not "cloud". This will show all of the preset locations. 000 to 006 are the toggle switch presets.
Just tested it and got you!

Find patch on cloud > burn into preset > Switch to device tab > edit > save (Asterix showing if not saved)


I was trying to do it without burning into preset :)
 
  • Like
Reactions: zardeefonder
I think we’re getting into dead horse territory a little bit, on “how not to do it going forward”. The new app is a re-write from the ground up. Roger has said they put more R&D into it than the previous versions combined. A lot of the issues we’re talking about are artifacts of the “just one more thing” nature of SA’s development cycle. The current products are well established and feature-mature, and I expect Neuro 3.0 will show that in its completeness and consistency.
If that was in response to my question, I genuinely had spent an hour or two learning the pedal and couldn't work out how to save!
 
I spent a little chunk of time getting acquainted with the Ventris.

Some engine type have "tap patterns" that you can smear using diffusion. For example, the Hall-L has a specific tap rhythm (x x x x - x x x x - ....), and as you increase diffusion, you can blur the distinct taps and fill in the gaps between them. The E-Dome, has a baked in pre-dly.

With the other reverb units/plugins I've used, Early Reflections are a series of irregularly spaced delay taps that simulate the first several reflections off the walls. From what I could tell, Ventris's "early reflections" is just one delay tap. The feedback can be increased with "pre-delay feedback" but it just reads like a simple delay line, and not random reflections. Adjusting the diffusion does smear that tap a little, but at high diffusion, the result is a unpleasantly ringy. Unless I'm missing something, I'll probably leave Early Reflections down or off.

Choosing engines and sizes is fairly straight-forward-- even though the inclusion of "engines" in the sizes list is a little unclear, and because changing engines moves the controls around, it's not easy to compare them. There's a nice variety of flavors there.

It's an insanely versatile pedal, more quirky than I expected. Like other reverbs, it has its personality. It's a good personality. At some point, I may do more of a head-to-head against the Fractal's reverbs.
 
Find patch on cloud > burn into preset > Switch to device tab > edit > save (Asterix showing if not saved)
I was trying to do it without burning into preset :)

For the desktop Neuro, when you're in Cloud mode, you find a patch, then clicking on (selecting) any cloud preset loads it to the pedal (but does not save it to any pedal slot). If instead, you click on the Burn (flame) icon on the Cloud preset will save it to your chosen slot on the pedal. You don't have to switch to the device tab and save again-- but it's harmless to do so.

As you say, if you are in Cloud mode, and you select a preset (loading it to the pedal), then you return to the Device tab, you can either save (to the currently selected pedal slot) or you can Save As... to choose a different pedal slot. This method will also save it to the pedal, but it also allows you to make some adjustments before saving.
 
  • Like
Reactions: rsmith601
Hey there I may be wicked late to the party. But I’m having a little bit of an issue setting up the lunar phaser in terms of turning it on and off. Unlike the spectrum which uses CC number 102 to turn it on and off (I just use the value of 0 and 127), the phaser doesn’t seem to respond to that and I can’t find anything in the manual or elsewhere to let me no which CC number to send those values to. Otherwise I can get it to go up and down the presets and all that good stuff.
 
Hey there I may be wicked late to the party. But I’m having a little bit of an issue setting up the lunar phaser in terms of turning it on and off. Unlike the spectrum which uses CC number 102 to turn it on and off (I just use the value of 0 and 127), the phaser doesn’t seem to respond to that and I can’t find anything in the manual or elsewhere to let me no which CC number to send those values to. Otherwise I can get it to go up and down the presets and all that good stuff.
Look in your Lunar’s MIDI map via the Neuro Desktop and configure whatever CC you want to that function.
 
Ventris/Nemesis:

When an expression pedal is connected and you switch to a preset with expression enabled parameters, the preset reads the position of the expression pedal immediately and changes the value of the preset parameters. Is it possible for the effect pedal to ignore the expression pedal when a preset is first loaded, until the expression pedal is moved?

Expression pedal is a Dunlop DVP3. I've connected directly to the Ventris for testing, but also into the omniport of an MC8. The goal is to use the MC8 to switch the expression pedal between controlling the Ventris and the Nemesis by toggling which MIDI channels the CC#100 messages are sent to. This is working well, but having the effects read the expression pedal position when switching presets is still a problem. From what I've read, the MC8 cannot be configured to "hide" the expression pedal from the effect until the pedal is moved.

Toggling off the expression pedal before switching presets prevents it from being read, but that's awkward, and if the patch you switch back to was changed with the expression pedal, then even if the expression pedal is now toggled off by the MC8, the preset will still load it's settings as previously altered by the expression pedal, instead of it's saved settings.
 
Ventris/Nemesis:

When an expression pedal is connected and you switch to a preset with expression enabled parameters, the preset reads the position of the expression pedal immediately and changes the value of the preset parameters. Is it possible for the effect pedal to ignore the expression pedal when a preset is first loaded, until the expression pedal is moved?

Expression pedal is a Dunlop DVP3. I've connected directly to the Ventris for testing, but also into the omniport of an MC8. The goal is to use the MC8 to switch the expression pedal between controlling the Ventris and the Nemesis by toggling which MIDI channels the CC#100 messages are sent to. This is working well, but having the effects read the expression pedal position when switching presets is still a problem. From what I've read, the MC8 cannot be configured to "hide" the expression pedal from the effect until the pedal is moved.

Toggling off the expression pedal before switching presets prevents it from being read, but that's awkward, and if the patch you switch back to was changed with the expression pedal, then even if the expression pedal is now toggled off by the MC8, the preset will still load it's settings as previously altered by the expression pedal, instead of it's saved settings.
This is something we addressed in the Mortrix controller; I specifically asked for jump, pass-through and relative modes to be implemented for expression on a per-preset basis.
 
  • Like
Reactions: boing
While I don’t specifically know what any of that means, I understand the translation is “yer screwed”. :atoz:
“Jump” is where the parameter value immediately jumps to the position of the expression pedal as soon as it is touched. (The Source Audio pedal knobs behave like this and I wish there were an option to change it to one of the other two behaviours below.)

“Pass-through” is where the value only changes once the moved pedal reaches the position matching the parameter value.

“Relative” is where moving the pedal will cause an immediate but gradual scaled change to the value, but it won’t suddenly jump. Once the pedal position catches up with the actual value, behaviour becomes “normal”.
 
Perfect example of how we get ourselves in trouble. The Room and E-Dome programs were taken from the Dimension Reverb, which is perhaps the best reverb value in the used market. Its mono, in an odd-looking housing and as a consequence it was largely overlooked when it came out. At some point I mentioned to Jesse that we ought to allow users to find the sounds from the Dimension Reverb. Metal Box is cool. It occurred to him that it would be early to do this in the "size" menu. So he added it in and for some reason it never made it into any updates to the User Manual. A company with more restraint would never have thrown that into the mix. I thought, why not? Better to have it in there unexplained than not in there at all? I take full ownership on that one. I dont see that knob assigns in the Desktop. Where is that?
Still a big fan of the Dimension. The E-dome on that can be tricked out to an insane depth that isn't reachable on the Collider. Great little pedal. If a "simple" reverb is in the works, that in a more traditional housing might finally find the right market.