silverhead

It’s not a ‘problem’ that can be fixed. It’s actually a very common and normal occurrence. It just reflects the reality that headphones and FRFR speakers are very different. Most players who want to have a preset sound similar when listening to headphones and to FRFR speakers find that they need to maintain two different versions of the preset, with different EQ (at least) settings. You will also find a noticeable difference in sound if you use different headphones, or even different FRFR speakers. Maybe not as dramatic, but still different.

Didn't he also say 'Guitar players can be very picky and sometimes get strung out.'? That's clearly a clue that the next update will include modeling for different pick thickness and strength, as well as string gauge. I'd love to be able to switch immediately, between strums, from a 7mm on light stings to a 15mm on heavy strings!! ;-)

You can test hardware compatibility of presets by using Helix Native and it’s Hardware Compatibility mode. You can download Helix Native for a free trial period.

Thanks for this. Good follow through!

Hmmm... -;)

I’m not familiar with the Iridium but from what you say I assume it is another type of ampFX modeler. Also, I don’t know what Apollo interface you’re using but it seems you’re not using the Pod Go as your audio interface for recording. Based on those assumptions I have two suggestions: 1) Try using your Pod Go as your audio interface and take both the Iriidium and the Apollo out of your setup. No harm in at least trying this. 2) You can go out either the Main Out or Amp Out from the Pod Go to your Iridium. You may have to configure your Iridium to accept the corresponding Line or Instrument input level.You’re right about not using the Pod Go amp/cab in any preset, again assuming your Iridium does that. Doesn’t matter whether or not you use a modified Factory preset or start anew. Note that by connecting the Pod Go output to your Iridium input you are limiting the POD Go FX to being in a pre-amp position in the signal chain. Not an optimal use of the Pod Go modeler. Does your Iridium provide FX like Reverb or time-based FX like Modulation or Delay? If not, and you have to use your Pod Go for these FX, you may notice a difference in how they sound before the amp.

2) That would be great. Bear in mind that the factory presets often change with each firmware update so perhaps you could update the list each time? 3) I saw that thread earlier today and concluded that I don’t have anything quick to offer on that so I moved on. I’ll take another look and decide if I have the time or knowledge to respond. If I don’t answer you know why….

Well, in this case the reason for no informative answer is….. there is no such list, at least not that I’m aware of. No one has yet bothered to say that because it doesn’t seem helpful. You know what would be helpful? If you two got together, or one of you took it upon himself, to create such a list and then post it here so that the next time this question is asked I can point to your list. Yes, it would take some time and effort, which is why it hasn’t been done. Care to take it on?

You're not an idiot. The Direct, or Private, Message (DM or PM) feature was removed from this forum some time ago. Don't know why or exactly when but afaik it's no longer possible to reach out to another forum member for private communications. I don't know of any way to contact castlevania directly. Hopefully he is still around here and will see this eventually.

Yes. First you must download and install the Firehawk FX driver from the Downloads section of this website. Then connect Firehawk to your PC via USB and then start up your Ableton program. If Ableton doesn’t automatically detect the Firehawk FX as its audio device you may have to configure it to do so.

You say you restored from ‘a’ backup. Was it the most recent one, created during your most recent firmware update?

Not a separate restore. The Restore feature allows you to select the components you want restored (IRS, Globals, Setlists, etc) but by default all of them are selected. Unless you specifically chose NOT to restore the Globals they should have been restored.

Are you recording using a mic or direct from the Taylor’s 1/4” output? Have you followed the guidance in the thread above your post? Does your Taylor have an on-board preamp?

Two things: - make sure you assign the desired parameter (in this case the Drive level) to the Snapshot controller. To do this, push and rotate the parameter knob. The value will then appear in white brackets indicating that the assignment has been made. - In Global settings you will find a parameter that controls whether or not Snapshot changes are saved or discarded when you switch snapshots before saving the preset. Make sure you understand how this works and set it to your preference.

Just curious… After updating the firmware (which resets the Globals to default values) did you restore the Globals to your pre-update settings using the backup file created during the update? I ask because if you didn’t you may soon find other issues related to a change in the Globals. It’s always good practice to restore your custom Global settings after an update.

Yes. The number of blocks was increased from 6 to 8 as of Firmware v 3.01 released 12/4/20. (See Release Notes in Downloads section)

Who are 'they'? If not an authorized Line 6 service center I suggest you open a support ticket to deal directly with Line 6 Support.

Not sure that's true. Do you have any specific information supporting that opinion or are you just speculating?

The Canadian supplier for Line 6 is Long & McQuade. You may be able to order the part through them.

Did you purchase the Helix Native plugin? It’s completely separate from your Helix LT, though the presets are compatible and you will receive a discount as a Helix LT owner. You may need to configure Ableton’s audio properties to have it recognize your Helix LT device.

Try setting the knobs to either the min or max position rather than 12 o’clock. This makes them less susceptible to jitter, which is the likely cause of your problem. When dirty the knobs can interpret minor vibrations from the floor (jitters) as knob movement. This is, indeed, a common circumstance as the equipment ages. The combination of cleaning the knobs (by rapid rotation and/or with appropriate cleaning fluid) and parking them at min or max generally resolves the problem.

If you haven’t previously saved the factory setlist (folder) you will need to reinstall the firmware to restore it. This will restore all Factory setlists and will also delete all User setlists, so make sure you backup anything you want to keep before reinstalling the firmware. Or, you could ask someone who does have a backup of that factory setlist if they would be kind enough to send it to you. You could then Import it using the editor.

Thanks.

@codamedia: I’ve tried that before but got hung up on levels. For instance, if the Vol is active and the pedal position is at some mid-point value less than 100% you have to increase the Vol level to 100% in order to engage the toe switch to activate the Wah. The same is true when going from Wah back to Vol. How do you handle this, or do you not find it problematic?

If you already have a Variax guitar you can also use the Vol and Tone knobs as additional expression controllers.