silverhead

There may be some dust or dirt in the knob shaft. Try rotating the knob from min to max rapidly many times; this may clear out the accumulated grit. If that doesn't work try some electronics contact cleaner.

I doubt it but I'm not 100% sure. The USB port on the Mobile Keys would interface internally with hardware/firmware that expects a standard PC/Mac USB connection and driver on the other end. I don't think it will communicate with an iOS system. That's why there is a separate mobile port on hte MobileKeys.

OK. All clear.

I don't think the offering is for mobile devices. The info says the requirements are PC or Mac. I don't think Cubase LE runs on iOS devices.

Yes - agreed. But there is no global setting re: switching presets. Or rather, the fixed global setting is No Trails when switching presets. You can't change that so I wouldn't call it a setting. The only changeable setting is per preset, not global. It is in the System Utilities menu area but as the doc says it is not a global setting. And in our discussion we were talking about within a preset - not between presets.

Where is the global setting vs. the per-preset setting? And how are they different?

I think the problem is with your Bluetooth connection. Try 'Forgetting' the Firehawk in your mobile Bluetooth settings, then re-establish the connection. Also try temporarily disconnecting any other Bluetooth devices so that you only have the Firehawk connected.

Yeah I think it always has been like this. I only noticed after checking the Guide after StephenSLR's comment. I always have Trails On and never change it so I assumed it was global. Wrong.

I think this should work. No harm in trying - shouldn't take long to find out.

Yes, you need another identical preset with no delay. Yes, trails are assigned per preset. Thanks for noting this. I've corrected my misinformation in my previous post.

Select the Looper in the signal chain. The display will show several looper parameters that can be adjusted, including Playback Volume. Experiment with these parameters.

Try using two instances of the Delay FX in your signal chain and assign them both to the same footswitch. Save the preset with one of the FX On and the other Off. Set the global Trails parameter in the Setup menu to OFF. Make the settings on the two FX blocks identical so that you have the repeats happening virtually infinitely at the volume you want. Then, as you switch chords, hit the assigned footswitch. The current delay (chord) will stop with no further repeats as the new delay kicks in, providing the desired repeats again for the new chord. This will happen every time you hit the footswitch when changing chords. You'll just have to remember to change the global parameter when you want your FX trails back again. EDIT: Disregard the last sentence. The Trails parameter is saved on a preset basis; it's not global.

No problems for me with iPad 4 (Retina) running iOS 9 and Safari.

Have you tried searching Customtone? It will be tedious but at least you'll no longer be hoping for someone else to do something.

There's more than 4 hrs to go before 'tomorrow morning' is over in California. Fingers crossed.

Input 1 and Input 2 have nothing to do with stereo. They are used primarily for dual-path presets so that you can have two input signals processed differently using the different signal paths. The input signals can be from the same source (Input1=Guitar, Input2=Guitar) or different sources (Input1=Guitar, Input2=Mic).

Check that your signal 'chains' are completely independent. If you have any FX block positioned before the path split this will cause the signal paths to merge. Make sure there is no FX block before the path split.

Experience says that even announcing the next release date, excluding any content info, is problematic. Any unforeseen delay in the release schedule/date - and that happens for good reasons often enough - triggers a deluge of dissatisfied customer complaints. Line 6 has been there, done that, and no longer does it. Can't blame them, IMHO.

I am not wanting to 'bash' you, but I find your stance on this quite interesting. Seems that as long as you don't experience a problem yourself, anyone else who experiences the problem is doing something wrong. But if you started to experience the problem yourself, you wouldn't be doing something wrong - it would be a problem with the device. Interestingly self-righteous!

Select No Amp in the Firehawk preset. Set the Firehawk Output Mode to Amp. The simplest connection method is to connect your guitar to the Firehawk and connect the Firehawk output (mono) to your amp's guitar input. This will position all Firehawk FX in front of (pre-) your amp. If you want the flexibility of having some FX pre-amp and some post-amp you will need an amp with an FX loop (send/return) and you will need to use the 4-cable connection method. You can search this forum for details about that.

I don't believe there is any change in the USB ports between the HD500 and HD500X. There may have been an improvement in the manufacturing process in this area but no one would know about that - it's just an inference from the fact that there haven't been many recent reports about it with the HD500X, and it was quite common with the HD500. But the design and the part itself seems to be the same.

.... or you could bypass the Saffire and use the HD500X as your audio interface. Connect your monitors to the HD500X outputs, connect the HD500X via usb to your computer/Ableton. Configure Ableton to use the HD500X and its ASIO driver as the audio input/output device.

To change the FX type, select the desired FX block. In the top left corner of the FX display window hit the FX type icon. You will see all models of the given FX type, as well as the word Type in the same top left position. Hit the button that says Type. The display will change to a show the different FX type options (distortion, delay, chorus, reverb....). Select the type you want. The display will change again to let you select the FX model of the given type. Then you can assign it to a footswitch as described above.

You're welcome!

Yes. After making changes, hold down the footswitch of the active preset for a couple of seconds. The display will start blinking. Release the switch, then hold it down again for a couple of seconds. When the display stops blinking the preset has been saved in its original location.