Source Audio Sorcerers Society (S.A.S.S) Part 3

[Nic.]

http://www.mipuc.com

Wow damn that looks useful. I've been having problems finding a good iPad audio interface that also supports MIDI. Pity I don't use the iPad anymore, the audio apps kept crashing.

You need some sort of adapter to give you a female USB-A connection on your device. So, for my tablet I use this:
http://www.amazon.com/gp/product/B00HHJ04MQ/ref=oh_aui_detailpage_o01_s00?ie=UTF8&psc=1
And for my phone I use something like this:
http://www.amazon.com/gp/product/B00C2HIJDO/ref=oh_aui_detailpage_o02_s00?ie=UTF8&psc=1

Then to convert from USB to MIDI I use this:
http://www.amazon.com/M-Audio-Midisport-Uno-MIDI-Interface/dp/B00007JRBM

Wow that's inexpensive too. I ought to get one to keep in my pedalboard case. Thanks!

 

[nshuman]

Wow damn that looks useful. I've been having problems finding a good iPad audio interface that also supports MIDI. Pity I don't use the iPad anymore, the audio apps kept crashing.


Wow that's inexpensive too. I ought to get one to keep in my pedalboard case. Thanks!

I have an iRig2 Midi incoming, it is taking forever to get here because the vendor made a mistake. But, I am seriously thinking of a PUC as well. I could just attach it under my board and be done with it.

Now that I have tasted wireless bliss for iOS with my H9 Max, I really want that for the SourceAudio pedals as well. It looks like the PUC is the easiest/cheapest way to accomplish this.

 

[Nic.]

I have an iRig2 Midi incoming, it is taking forever to get here because the vendor made a mistake. But, I am seriously thinking of a PUC as well. I could just attach it under my board and be done with it.

Now that I have tasted wireless bliss for iOS with my H9 Max, I really want that for the SourceAudio pedals as well. It looks like the PUC is the easiest/cheapest way to accomplish this.

But the MIDI can't do audio at the same time. I mean like high quality audio out through USB rather than audio out through the jack... I tried the alesis iOdock, which worked but wasn't very stable. The PUC looks a lot more practical, yeah.

 

[FretNoMore]

The PUC needs a newer iPad than mine though if I read the specs right. (I'm still using an iPad 2)

 

[Adamixoye]

Wow that's inexpensive too. I ought to get one to keep in my pedalboard case. Thanks!

The only thing I would add is I haven't found the connection to be 100% stable. I'm not sure whether that's a function of the app or any of the three points in the hardware (device, OTG USB adapter, USB-MIDI adapter). You want to make sure you connect/disconnect properly and not leave idle for a very long time. However, if you do those things it's pretty reliable (so far, IME).

 

[FretNoMore]

But the MIDI can't do audio at the same time. I mean like high quality audio out through USB rather than audio out through the jack... I tried the alesis iOdock, which worked but wasn't very stable. The PUC looks a lot more practical, yeah.

The first version of the iO Dock is not that great, I had problems with noise as well as instability. Against better judgement I bought the new version (iO Dock II) and so far it works and sounds much better.

 

[nshuman]

But the MIDI can't do audio at the same time. I mean like high quality audio out through USB rather than audio out through the jack... I tried the alesis iOdock, which worked but wasn't very stable. The PUC looks a lot more practical, yeah.

Yeah, the newer Focusrite interfaces are supposed to be nice though. I think it's hard to get greta results with the lower end stuff.

 

[Nic.]

The only thing I would add is I haven't found the connection to be 100% stable. I'm not sure whether that's a function of the app or any of the three points in the hardware (device, OTG USB adapter, USB-MIDI adapter). You want to make sure you connect/disconnect properly and not leave idle for a very long time. However, if you do those things it's pretty reliable (so far, IME).

I don't need it to be 100% reliable, it's more like a backup if my MIDI controller dies. I'm seeing my home-made MIDI controller as a temporary thing until the Source Audio MIDI controller is released.

The first version of the iO Dock is not that great, I had problems with noise as well as instability. Against better judgement I bought the new version (iO Dock II) and so far it works and sounds much better.

Interesting. I didn't know there was an iO Dock II, I assume it must have come out within the past year. I probably won't jump on it at the moment, though, since I've just gotten a really useful setup. TBH my iPad problems weren't just with the hardware; the apps kept crashing on me too.

Yeah, the newer Focusrite interfaces are supposed to be nice though. I think it's hard to get greta results with the lower end stuff.

Agreed.

--------

Anyway, earlier today I set up my pedalboard with the controller and migrated all the presets from the various pedals into the Hub Manager. Here's a video showing what I've done with it:


0:00 Clean with delay from the Zoom MS60B
0:07 Scene 1: Classic crunch: OFD clean/dist morph via expression pedal
0:28 Scene 1 with low pass hothand engaged
0:36 Scene 2: Multiband distortion: MWBD2 clean/dist morph via expression pedal
1:08 Scene 3: Multiband octave synth distortion: MWBD2 clean/dist morph via expression pedal
1:17 Scene 3 with low pass hothand engaged
1:49 Scene 4: High-grit using single band octave on MWBD2 and octave distortion on Manta, moveable filter via expression pedal to drastically alter EQ
2:10 Scene 5: Synthy envelope follower, envelope mix controlled via expression pedal
2:58 Scene 6: Phaser on distortion, phaser follows tap-tempo-controlled sine wave, filter mix controlled via expression pedal
3:37 Scene 7: Step filter on distortion, step rate controlled by tap-tempo, filter mix controlled via expression pedal
4:20 Scene 8: Huge wooly fuzz, amount of treble controlled by expression pedal
4:48 Scene 8 with low pass hothand engaged
If any if you guys want any of these patches, I can send them to you. You'd probably have to do a lot of tweaking though, because I've set up my bass for very low action for more percussive attack, so the output is a lot lower than normal. I'm kinda using the OFD to expand this narrow range of output volumes into a good range for the MWBD2.

I'm particularly proud of these aspects of the setup:
1) The expression pedal morphing trick
2) I've set up my Manta such that footswitch 1 is always hothand low pass filter so I can add that to any of the distortion scenes ad hoc
3) All LFO-based scenes are automatically tap tempo, so I can free up the expression pedal for other things (e.g. wet/dry). How this is done is that I've set footswitch 2 to tap tempo on the pedal itself. Once you do that, any scene that uses footswitch 2 will have that scene's manta patch will become tap tempo! i.e. tap tempo is not something you can set within the scene, but is instead something within the pedal that's linked permanently to either the left or right footswitch.
4) Less relevant to the Source Audio thread, but anyway, no matter what patch the Zoom MS60B is on, pressing the Zoom's footswitch will ALWAYS cycle between the patches marked A, B, C, etc.; for example, I set patch 10 and 11 as A and B respectively. To set the Zoom MS60B into the right mode for MIDI control, I have to press the footswitch once, e.g. to patch A. Then say I press my MIDI controller, so it goes to scene 2 (which I've set as patch 3 on the Zoom). Pressing the Zoom's footswitch will instantly send it to patch B (i.e. patch 11). So I'm using the Zoom's footswitch as a solo boost + delay. No matter what scene I'm on, I can always press the Zoom's footswitch to get the exact same sound, just louder and more solo-ish. Then to change back, I just need to press the MIDI pedal again.

Some other points to note:
- The Guitar OFD gives a surprisingly nice nearly-clean tube tone. It's become the foundation of most of the scenes here. The fuzz settings also sound surprisingly good on bass even without a blend. If you listen to scene 8, you'll hear really really defined attacks. I honestly don't know how I did it, I found this patch by accident. I'll dissect it another day.
- Disappointingly, I can't simultaneously control one pedal with both Hothand and expression at the same time. I wanted to be able to use the expression pedal to change the resonance of the manta filter, or maybe change wet/dry mix, and hothand to do the actual modulation. The only way I can think of to get around it at the moment is to either use a MIDI expression pedal and set the MIDI to whatever number is needed to change that parameter, or change the MIDI channel of the hub's expression out. But then that means I can only use that expression pedal for one particular function in all the scenes (I think!). I don't think the expression pedal can currently be assigned to different MIDI channels for different scenes, although that could be a nice future update. But anyway, this isn't a big problem, it's just something that would be nice to have.

Has anyone seen this? It just popped up on my recommended list.

Wow I'd love to visit one day. It looks awesome.

By the way, that Jet Flanger keeps reminding me of the larger Line6 enclosures, like on the DL4

 

[FretNoMore]

I have to ask a couple of questions about tap tempo;

- The Manta has tap tempo but the Orbital hasn't?
EDIT: OK, it works, it's just not in the manual.
EDIT2: Not in the old version of the manual I had.

- I can't get external tap tempo via MIDI to work, is that not possible?

 

[Adamixoye]

@Adamixoye if I'm not wrong it's Midi Designer for iPad, I used it before. There's a few versions though, not sure which one he's using. There's the free version with ads, the free version without ads but can only put 12 buttons/switches/etc. on it, and the paid version without ads and with unlimited placement.

----

Anyway, another important update! I think this wasn't made explicitly clear in the manuals and I haven't seen it turn up in the discussion so far, but you CAN set both presets using the hub manager! I guess you could say I found a loophole around it.

The reason for doing so is so that you can set two presets on your OFD or MWBD2, and then morph between them.

Okay, it's done this way: When you're in the hub manager, for the pedal you want to set two presets, include it TWICE in Scene Viewer (the bottom panel). Make sure both are set to engaged, and under additional controls, scroll down to Current Preset, and set one of them to 1 and the other to 2.

When you load the scene from your midi footswitch or whatever, it will load the engaged pedals in the Scene Viewer from left to right. So the first preset you set in the scene viewer will be loaded into either preset 1 or 2 in that pedal, and then a split second later, the second preset will be loaded into the other slot. Now that both are loaded, morphing from one to the other works with the footswitch!

Some other things I discovered while figuring this out:

1) It only works if both are set as "engaged". I think if it is set to "bypass", the hub doesn't bother to send all the other functions, it just sends a "bypass this pedal" message.

2) If you don't set two presets in your scene, instead, you just set one scene (e.g. Preset slot 1) and set it to morph, it won't morph to the preset that you saved in your pedal's slot 2 beforehand. Instead, it morphs to your last used preset in the pedal's slot 2.

For example, say you used a scene with a multiband foldback 08 in slot 1 and a single band octave 20 in slot 2. Then you load a scene that only sets a clean boost in slot 1 with expression set to blend. If you blend, it will morph from the clean boost to the single band octave (at least if my ears don't deceive me and my memory is absolutely clear).

With regard to the earlier point about bypass, using the same example, if the second preset has clean boost with expression pedal morph in slot 1, and some bypassed preset in slot 2, it will NOT morph to the bypassed preset in slot 2. Instead, it will morph to the single band octave.

3) If you load a scene where one pedal is bypassed, e.g. slot 1 is a clean boost and slot 2 is some bypassed multiband octave 13, stepping on the slot 2 footswitch won't turn on a multiband octave. Instead, it will load the preset in slot 2 saved into the pedal itself. Likewise, say the scene loads a preset into slot 1. If you turn it off and on again with the footswitch, it will not load the scene's preset, instead of will load the preset in slot 1 saved into the pedal directly.

4) Finally, a confusing thing - earlier I said the scene loads the engaged pedals in the Scene Viewer from left to right. But if there's a bypassed scene, it seems to be the other way round. For example, if you just have two of the same pedal in the scene viewer, the left one is set to bypass while the right one is set to engaged, the pedal will be bypassed when the scene is loaded. But if the left one is set to engaged while the right one is set to bypassed, the pedal will be engaged. No, I don't understand why this happens. But it doesn't matter, since it doesn't affect morphing anyway.

So TL;DR: If you want to load two presets to morph between, load two of the same pedal in Scene Viewer, set both to engaged, and put the preset for heel-down position on the right.

Do let me know if this method is successful for you guys!

I tried to read this two or three times and didn't understand it. Maybe I'm just having a super-dense moment. So by "loading" the presets into both slots, can you click them on and off, essentially having two settings within a scene? Or do you only have the option to "morph"?

I don't think the expression pedal can currently be assigned to different MIDI channels for different scenes, although that could be a nice future update.

+10000000 I don't want to be the only one banging the drum for this!

 

[Nic.]

Merry christmas everyone! It's Christmas morning over here, and I'm typing this out over a breakfast of leftover turkey sandwich

I have to ask a couple of questions about tap tempo;

- The Manta has tap tempo but the Orbital hasn't?
EDIT: OK, it works, it's just not in the manual.
EDIT2: Not in the old version of the manual I had.

- I can't get external tap tempo via MIDI to work, is that not possible?

Last time I saw this topic brought up, iirc it was said that external tap tempo via MIDI doesn't work. I'd like it to work though.

I tried to read this two or three times and didn't understand it. Maybe I'm just having a super-dense moment. So by "loading" the presets into both slots, can you click them on and off, essentially having two settings within a scene? Or do you only have the option to "morph"?

Nope, you cannot click them on and off. The pedal's footswitches are ALWAYS assigned to the presets within the pedal. I believe far there hasn't been a Hub command to -overwrite- the saved presets within the pedal.

However, I believe that in addition to the internally saved preset, there's also some kind of buffer space in the pedal where the current patches are saved. I don't know how the guys at Source Audio actually programmed these things, but to my experience it behaves like some sort of buffer, so you have a "preset" bank where the pedal saves data on "what settings to select when the user presses the footswitch", and a "buffer" bank where the pedal saves data on "what are the current settings now"?

Actually, I think I'll go with this terminology to make things clearer, I'll use "preset" to refer to the patches saved within the pedal and activated with the pedal's footswitch, and use "patch" to refer to just some state of the pedal. Then a Scene refers to a collection of patches sent to all the pedals, but these patches do not overwrite any presets. So even though the Hub sends patches to all the pedals, it does not change the internal presets of the pedals, it just saves these scenes to a temporary buffer.

Now, this is the important part. It seems that when you morph, it morphs between the two patches (not presets) currently in the 'buffer'. So I believe these are the following possibilities (in my experience so far; I might be wrong on some points since I wasn't taking notes scientifically and just trying to get a certain final result, the only thing I'm definitely sure about is that sending two patches lets you morph between them)

1) Normal pedal usage (without Hub): When you start up the pedal, the two presets go into the buffer. Whenever you turn on one of them, and use morph, it morphs between the two.

2) Send one engaged patch via Hub: When you start up the pedal, the two presets go into the buffer. Now, you send a patch. There are three options: send to 1 or 2, or send to neither (i.e. changes current settings but does not light up either LED*). Say your scene sends the patch to slot 1. So the current status of the pedal's 'buffer' is that slot 1 has the new patch from the hub, but slot 2 has the original preset from the pedal. So morphing will morph between the Hub patch (in heel down position) and the pedal's preset 2. Vice versa if your scene sends the patch to slot 2. As for the other option, where neither LED lights up, I accidentally selected that option for one of my scenes, and the result is that no morphing happens.

3) Send two scenes in succession, one with an engaged patch to slot 1 and the other with an engaged patch to slot 2: When you first start up the pedal, the two presets go into the buffer. Then the first scene overwrites slot 1's buffer, so now morphing goes between the slot 1 patch (heel down) and the original slot 2 preset (heel up). When you send the second scene, it leaves slot 1 alone, but overwrites slot 2's buffer, so now morphing goes between the slot 2 patch from the second scene (heel down) and the slot 1 patch from the first scene (heel up). However, keep in mind that throughout, the presets stay the same, so if you change patches using the pedal's footswitch, it goes back to the presets. What I have NOT tried, is, from the scenario above, now slot 2 is engaged, if I turn off slot 2 and turn it on again, it should go to the pedal's slot 2 preset but the slot 1 buffer should still contain the patch from the scene, so it should morph between those two.

4) Send a single scene with a patch to slot 1 and another patch to slot 2. This gives the final result of #3. However, I have realized that the Hub doesn't always send the patches from left to right. I don't understand how it works. At some point I had to swap the order of the scenes to get my desired "heel down" default position.

5) And finally, if you send a bypassed patch, it doesn't seem to save anything to the buffer, so I think the only message it sends is "turn this pedal off". Perhaps to save MIDI data and reduce latency, since there really is no point to sending data for a bypassed pedal. For example, say you send a patch to slot 1 but it's bypassed. If you click the footswitch, it doesn't go to that patch, but it instead goes to the pedal's original preset.

*Regarding the "neither" option in #2, I don't really understand how this works, but it seems that engaged/not engaged is independent of the LED in this case. So neither LED lights up, but the effect happens. From here, you can click either footswitch to go to preset 1 or 2.

In addition to that, I believe this scene thing works like when you tweak pedal settings. For example, say you have preset 1 engaged. You make some changes to the knobs. Then this is no longer preset 1; let's call it patch 1. If you morph from here, you go from patch 1 to preset 2 and back - at no point does the expression pedal send you back to preset 1 instead of patch 1. But if you bypass and then engage the pedal again, it goes to preset 1 and patch 1 is lost. Actually that's why I had hope of this method working, I tried this with my MWBD Pro before my hub arrived and it gave me some hint to how the morph processing works. One thing I haven't tried, but I -expect- to work, is this scenario: Start with preset 2, twiddle knobs and make a patch 2. Then click the footswitch for preset 1, and twiddle knobs to make patch 1. Now, morph should go between patch 1 and patch 2 rather than patch 1 and preset 2.

I think that should just about sum up everything I've experienced so far with this!

While I used to want a Hub command to overwrite preset, that was because I assumed morph worked between presets. But now I don't want to overwrite anymore because this gives me both the option to morph between two desired patches, as well as to have certain universally useful presets on hand at all times via the pedal's footswitch.

+10000000 I don't want to be the only one banging the drum for this!

I believe at the moment the Hub already sends expression and hothand messages using MIDI format anyway, so hopefully it's possible!

 

[NoxNoctus]

Santa was good to me.

Merry Christmas, fellow Sorcerers!

 

[rsmith601]

Add me too please Manta, Orbital, Dimension, hub.

And midi moose too. Can someone tell me. The moose causes the hub to light and presumably the pedals to change but it causes no changes in the hub software. It should right? If I hit the moose's #2 pedal it should cause the hub software on my laptop to change. Any guesses why it isn't?

You are number #203! Welcome to SASS where the Hub users are getting very clever these days!!

 

[Adamixoye]

Last time I saw this topic brought up, iirc it was said that external tap tempo via MIDI doesn't work. I'd like it to work though.

By "external tap tempo" are we talking about any incoming MIDI clock? Because if so, that is both surprising and disappointing.

Nope, you cannot click them on and off. The pedal's footswitches are ALWAYS assigned to the presets within the pedal. I believe far there hasn't been a Hub command to -overwrite- the saved presets within the pedal.

However, I believe that in addition to the internally saved preset, there's also some kind of buffer space in the pedal where the current patches are saved. I don't know how the guys at Source Audio actually programmed these things, but to my experience it behaves like some sort of buffer, so you have a "preset" bank where the pedal saves data on "what settings to select when the user presses the footswitch", and a "buffer" bank where the pedal saves data on "what are the current settings now"?

Actually, I think I'll go with this terminology to make things clearer, I'll use "preset" to refer to the patches saved within the pedal and activated with the pedal's footswitch, and use "patch" to refer to just some state of the pedal. Then a Scene refers to a collection of patches sent to all the pedals, but these patches do not overwrite any presets. So even though the Hub sends patches to all the pedals, it does not change the internal presets of the pedals, it just saves these scenes to a temporary buffer.

Now, this is the important part. It seems that when you morph, it morphs between the two patches (not presets) currently in the 'buffer'. So I believe these are the following possibilities (in my experience so far; I might be wrong on some points since I wasn't taking notes scientifically and just trying to get a certain final result, the only thing I'm definitely sure about is that sending two patches lets you morph between them)

1) Normal pedal usage (without Hub): When you start up the pedal, the two presets go into the buffer. Whenever you turn on one of them, and use morph, it morphs between the two.

2) Send one engaged patch via Hub: When you start up the pedal, the two presets go into the buffer. Now, you send a patch. There are three options: send to 1 or 2, or send to neither (i.e. changes current settings but does not light up either LED*). Say your scene sends the patch to slot 1. So the current status of the pedal's 'buffer' is that slot 1 has the new patch from the hub, but slot 2 has the original preset from the pedal. So morphing will morph between the Hub patch (in heel down position) and the pedal's preset 2. Vice versa if your scene sends the patch to slot 2. As for the other option, where neither LED lights up, I accidentally selected that option for one of my scenes, and the result is that no morphing happens.

3) Send two scenes in succession, one with an engaged patch to slot 1 and the other with an engaged patch to slot 2: When you first start up the pedal, the two presets go into the buffer. Then the first scene overwrites slot 1's buffer, so now morphing goes between the slot 1 patch (heel down) and the original slot 2 preset (heel up). When you send the second scene, it leaves slot 1 alone, but overwrites slot 2's buffer, so now morphing goes between the slot 2 patch from the second scene (heel down) and the slot 1 patch from the first scene (heel up). However, keep in mind that throughout, the presets stay the same, so if you change patches using the pedal's footswitch, it goes back to the presets. What I have NOT tried, is, from the scenario above, now slot 2 is engaged, if I turn off slot 2 and turn it on again, it should go to the pedal's slot 2 preset but the slot 1 buffer should still contain the patch from the scene, so it should morph between those two.

4) Send a single scene with a patch to slot 1 and another patch to slot 2. This gives the final result of #3. However, I have realized that the Hub doesn't always send the patches from left to right. I don't understand how it works. At some point I had to swap the order of the scenes to get my desired "heel down" default position.

5) And finally, if you send a bypassed patch, it doesn't seem to save anything to the buffer, so I think the only message it sends is "turn this pedal off". Perhaps to save MIDI data and reduce latency, since there really is no point to sending data for a bypassed pedal. For example, say you send a patch to slot 1 but it's bypassed. If you click the footswitch, it doesn't go to that patch, but it instead goes to the pedal's original preset.

*Regarding the "neither" option in #2, I don't really understand how this works, but it seems that engaged/not engaged is independent of the LED in this case. So neither LED lights up, but the effect happens. From here, you can click either footswitch to go to preset 1 or 2.

In addition to that, I believe this scene thing works like when you tweak pedal settings. For example, say you have preset 1 engaged. You make some changes to the knobs. Then this is no longer preset 1; let's call it patch 1. If you morph from here, you go from patch 1 to preset 2 and back - at no point does the expression pedal send you back to preset 1 instead of patch 1. But if you bypass and then engage the pedal again, it goes to preset 1 and patch 1 is lost. Actually that's why I had hope of this method working, I tried this with my MWBD Pro before my hub arrived and it gave me some hint to how the morph processing works. One thing I haven't tried, but I -expect- to work, is this scenario: Start with preset 2, twiddle knobs and make a patch 2. Then click the footswitch for preset 1, and twiddle knobs to make patch 1. Now, morph should go between patch 1 and patch 2 rather than patch 1 and preset 2.

I think that should just about sum up everything I've experienced so far with this!

Okay, I'm going to have to read this a few more times (and, ideally, actually try it out, perhaps today) but you answered my question at a basic level. Thanks!

While I used to want a Hub command to overwrite preset, that was because I assumed morph worked between presets. But now I don't want to overwrite anymore because this gives me both the option to morph between two desired patches, as well as to have certain universally useful presets on hand at all times via the pedal's footswitch.

I am still very much in favor of a mode where the scene loads into preset (as you've defined it), so that it can be switched on and off, while preset two is still accessible.

I believe at the moment the Hub already sends expression and hothand messages using MIDI format anyway, so hopefully it's possible!

Yes, I believe it does. The problem is if you want it to send that MIDI CC to a 3rd party pedal(s), you have to have it/them on the same MIDI channel as the Hub, which you might not want for preset/scene saving purposes.

 

[FretNoMore]

By "external tap tempo" are we talking about any incoming MIDI clock? Because if so, that is both surprising and disappointing.
.

According to the manuals (Manta, Orbital) the pedals can sync to MIDI clock, provided the preset in the pedal has tap tempo activated. I don't know enough about MIDI to know what the difference is between MIDI clock and tap tempo, but from my tests I can not get an external tap tempo switch connected to a MIDI footswitch to change the tempo in the pedals.

 

[Adamixoye]

According to the manuals (Manta, Orbital) the pedals can sync to MIDI clock, provided the preset in the pedal has tap tempo activated. I don't know enough about MIDI to know what the difference is between MIDI clock and tap tempo, but from my tests I can not get an external tap tempo switch connected to a MIDI footswitch to change the tempo in the pedals.

Okay. I don't need "tap tempo" as long as it accepts incoming MIDI clock. I imagine the source of your troubles are in how "tap tempo" is converted to MIDI clock, or perhaps you need your Manta/Orbital to be set to a certain mode to accept MIDI clock?

 

[FretNoMore]

I'll have to go back and read the manuals again, but I suspect this is not supported.

 

[Nic.]

Okay, I'm going to have to read this a few more times (and, ideally, actually try it out, perhaps today) but you answered my question at a basic level. Thanks!

You're welcome! Do post if you manage to get the same results as me, and if you've any interesting discoveries on this topic please share!

I am still very much in favor of a mode where the scene loads into preset (as you've defined it), so that it can be switched on and off, while preset two is still accessible.

Yeah, it really depends on what you need out of it! So it would be good if both possibilities are available. That said, I think that if you want to switch the particular preset on/off, couldn't you do it from the MIDI pedal...?

Yes, I believe it does. The problem is if you want it to send that MIDI CC to a 3rd party pedal(s), you have to have it/them on the same MIDI channel as the Hub, which you might not want for preset/scene saving purposes.

I see... I know hardly anything on this topic since I'm not using any other pedals that need CC.

--

Oh yes, one more thing... @rsmith601, sorry to bother you on Christmas, but if you've time could you update my membership status to read Guitar OFD, MWBD2, Manta and Hub? Thank you!

 

[Adamixoye]

Oh yes, one more thing... @rsmith601, sorry to bother you on Christmas, but if you've time could you update my membership status to read Guitar OFD, MWBD2, Manta and Hub? Thank you!

Well I can officially say my membership needs to be updated. IN: Bass OFD & Hub. OUT: Dual Expression Pedal. TOTAL: Manta, Bass OFD, HH3, Hub.

 

[FretNoMore]

...
Yeah, it really depends on what you need out of it! So it would be good if both possibilities are available. That said, I think that if you want to switch the particular preset on/off, couldn't you do it from the MIDI pedal...?
...

This has been discussed a few times and SA has indicated that having the scene store to a preset might become possible in some future version of the firm/software. I like the idea of being able to see the SA pedals as regular stompboxes (only that changes functionality when you load a scene) so you can use the foot switches to turn the effect on and off without reverting to the preset as happens now. (Actually it still would, but the preset would have been replaced by the scene change).

It is possible of course to solve this by using dual scenes (and patches/presets on your MIDI controller) and scroll up and down to switch the pedal on and off but I don't want to work that way. It becomes even more cumbersome if you want to turn more than one pedal on and off individually during a song.

I'm hoping this will be implemented; what I do in the meantime is use the expression pedal to simulate turning a pedal on and off, which works if you don't need it for something else.