• 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

Well, that's all pretty reasonable and it's my next step (I didn't have a chance to troubleshoot last night, I will tonight).

However, there are a few problems with it. One is that I don't have a "simple" MIDI controller, by which I take it you mean something like a MIDI Mouse or One Control Gecko. So I can't change scenes without connecting a device (laptop, iPad, or Android device---I could do any of the above). This limits how well I can isolate the variables you are talking about, although I can still isolate things up to a point.

A lesser problem, and not so much a problem per se, is that in theory I should know when my iPad/MIDI Designer/M-Audio UNO setup is sending MIDI data. Lights blink when data is being sent---on both the app and the interface. Even though there seems to be a correlation between what is hooked up and the problems, there doesn't seem to be a correlation between what MIDI data I've tried to send (or when I'm sending it---there is not continuous data being sent from the iPad) and the problems. Furthermore, I've had pretty much perfect success with this setup and all of my other pedals. So while I agree it's something I should test---it wouldn't be scientific if I didn't---that explanation doesn't seem as likely to me as it seems it might be to the rest of you.
Your M5 can serve as a simple midi device, for future trouble shooting/programming.

Sometimes I feel like a creep for knowing forum members boards as well as I know my own. But then I remember I own most of my pedals because of rave reviews from those same forum members.
 
Your M5 can serve as a simple midi device, for future trouble shooting/programming.

Sometimes I feel like a creep for knowing forum members boards as well as I know my own. But then I remember I own most of my pedals because of rave reviews from those same forum members.

*Self-face-palm* to your first paragraph (why didn't I think of that?), and a hearty chuckle to the second.
 
  • Like
Reactions: ncabral
You just have to be aware the M5 will send additional MIDI CC depending on what FX are utilized in the M5 scene. There's no way in the M5 settings to defeat that "feature".

For the Hub my workflow is to power on my board. Wait a few seconds for everything to get running. Then click the SCAN button on the Hub to get it to reach out and connect to all of the pedals. Sometimes when everything initially powers on at the same time the Hub doesn't always connect to the pedals. It's a good habit to get into pressing SCAN after a full power cycle.
 
For the Hub my workflow is to power on my board. Wait a few seconds for everything to get running. Then click the SCAN button on the Hub to get it to reach out and connect to all of the pedals. Sometimes when everything initially powers on at the same time the Hub doesn't always connect to the pedals. It's a good habit to get into pressing SCAN after a full power cycle.
Great tip. Mine doesn't start up properly once in a while and I usually just power cycle again. I'll try this next time. Thanks!
 
You just have to be aware the M5 will send additional MIDI CC depending on what FX are utilized in the M5 scene. There's no way in the M5 settings to defeat that "feature".

For the Hub my workflow is to power on my board. Wait a few seconds for everything to get running. Then click the SCAN button on the Hub to get it to reach out and connect to all of the pedals. Sometimes when everything initially powers on at the same time the Hub doesn't always connect to the pedals. It's a good habit to get into pressing SCAN after a full power cycle.

Do you know what MIDI CC the M5 is sending out? This is correlated to the parameters?

I have learned to hit "scan" after every power up. Because everything is combined into my PSU, it all powers up at the same time so I frequently have this problem. It's good advice, though.
 
No, each FX in the Line6 products output a particular MIDI CC. I cannot quickly find the chart that details which FX outputs what. My recollection is you want to set the M5 to a Volume Pedal FX on each patch to ensure it's not sending CC that will affect the SA pedals. But don't quote me on that.
 
No, each FX in the Line6 products output a particular MIDI CC. I cannot quickly find the chart that details which FX outputs what. My recollection is you want to set the M5 to a Volume Pedal FX on each patch to ensure it's not sending CC that will affect the SA pedals. But don't quote me on that.

Aaaaaaaaand we're back full circle because it's stuff like this that made me never really seriously consider using the M5 as my MIDI controller in the first place. :D
 
I'm familiar with all of that, but I thought it was all input, not output.
From what I've read I think it both sends and receives the same messages; if you change programs on the M5 it sends the PC, if you stomp the bypass switch it sends CC11 etc.

CC01 (Expression pedal) collides with Sustain in the guitar Multiwave
CC64 (tap tempo) collides with LFO Rate in the Dimension
CC69 (tuner on/off) with Effect type in the Dimension

But this is just what I've read, I haven't tried it myself.

For the most part it looks like it could be used for program changes at least.
 
Lobby for an option / feature in the Hub to exclude inbound MIDI CC (but continue to accept and act upon PC and Clock) and it solves the problem when using the M5 (and any other Line6 product as they all do the same thing) as a controller.

Well that would hurt what I'm doing with my iPad, so I don't want to do that. If they're going to update something along these lines, I would much rather it be that they have separate input and output MIDI Channels (so I can do HH3 via MIDI to a 3rd party pedal not on the same channel as the Hub).

From what I've read I think it both sends and receives the same messages; if you change programs on the M5 it sends the PC, if you stomp the bypass switch it sends CC11 etc.

CC01 (Expression pedal) collides with Sustain in the guitar Multiwave
CC64 (tap tempo) collides with LFO Rate in the Dimension
CC69 (tuner on/off) with Effect type in the Dimension

But this is just what I've read, I haven't tried it myself.

For the most part it looks like it could be used for program changes at least.

And yet it won't do MIDI Thru in general, specifically clock-thru. SMH. :D
 
For the Hub my workflow is to power on my board. Wait a few seconds for everything to get running. Then click the SCAN button on the Hub to get it to reach out and connect to all of the pedals. Sometimes when everything initially powers on at the same time the Hub doesn't always connect to the pedals. It's a good habit to get into pressing SCAN after a full power cycle.
Mine actually never connects to the pedals so I developed the same workflow.
 
  • Like
Reactions: Nic.
I didn't expect to ever actually sit down and watch through a 12 minute review of an **EQ **pedal. That was a very good review, and the trick at the end was really cool. Can you control those tricks by MIDI and/or Hub? e.g. change Autoscroll speed by MIDI?
As far as I know, the MIDI only functions to turn ON/OFF, select presets and regulate Volume. But it is possible that something is implemented that is not on the manual. It might be also possible to have a firmware update that enables some more features, only the guys at SA can clear that.
 
  • Like
Reactions: Nic.
Check out my first pedal Demo with the Programmable EQ (Subtitles in english)

Está m
I didn't expect to ever actually sit down and watch through a 12 minute review of an **EQ **pedal. That was a very good review, and the trick at the end was really cool. Can you control those tricks by MIDI and/or Hub? e.g. change Autoscroll speed by MIDI?
Go to the Backpage, turn it on and off with 'AS' and adjust the speed with 'SW'
 
Last edited:
Adamixoye, I watched your videos from about a week ago showing difficulty saving presets on Manta and OFD when using the Hub. I spent about 20 minutes at my desk today playing around with the Hub / Hub Manager, saving/loading scenes and storing/recalling presets on the Manta and OFD, and I couldn't duplicate the behavior you were seeing. So, quick question for you... is this still a problem, or have you resolved it? If it's still a problem, can you give me a more detailed description (ideally, step-by-step instructions) of how to get into the state where preset saving no longer works? That would be very helpful for debugging. Thanks!