silverhead

I can't see anything in the documentation or the app that sheds any light on this. I suggest you open a support ticket to get clarification directly from Line 6 tech support. Please let us know what they say.

Is this the first time you have tried to engage the models manually using the Model Select knob? In other words, have you previously used the HD500 presets to turn modeling on/off as specified in the preset? It may not be an issue of 1/4" vs. VDI. It may be a physical flaw with the guitar itself that is noticed only when using the knob manually rather than using the HD500 presets for model selection. The physical flaw is that the Model Select knob may not be depressing far enough to activate the switch beneath the shaft. There is a known issue where the edge of the knob can contact the body of the guitar and be prevented from depressing far enough to engage the switch. Inspect the knob/body. If this is happening you can fix it easily be prying the knob gently up off the shaft, insert a small wad of paper into the knob, and replace the knob. The paper raises the knob enough so that the shaft will depress fully and engage the switch. This would explain why you need to 'boost' modeling mode using VDI. As soon as you select an HD500 preset that specifies a Variax model, Model Mode is engaged on the Variax (electronically, not manually) and the light on the knob will come on. From then on you can select models manually on the Variax but you won't be able to manually exit Model Mode and activate the mag pickups. You would need to recall an HD500 preset that selects Variax Mags as the input. But of course if you have often manually used the Model Select knob to turn modeling mode on/off in the past then the problem is something else that has recently happened. Let us know.

I don't recall that issue but since it was a long time ago I suggest you check the firmware version in your V300 and update if there's a newer version available. If the problem was fixed the latest firmware will have the fix.

Hmmm..... I will investigate further. I don't think any features were removed from this version, but like you I don't see any Customtone search capability. I did not notice it was missing - really haven't used it with Mobile Pod before.

Sorry - I missed the word 'mobile' in your post. I thought you were referring to the Pod 2.0 product. Customtone does not apply to the Mobile Pod 2 software. You can't load new tones into the app; it comes pre-loaded. You can save new tones that you create in the app but there is no import feature. The tone search feature in Mobile Pod 2 applies to the internal pre-loaded tone library, as well as any saved user tones.

Didn't know about the length constraint. Thanks Peter.

Sounds great. Thanks. I think the Helix editor requires that the Helix device be on and connected to the computer. Is that always the case for you, or would you have to go to your studio anyway to turn the Helix device on?

I agree that editing on the device itself is very efficient (except for the back-breaking part). There are several specific things that I find faster and a little more comprehensive on the editor: - block selection. I find it a lot easier, faster and less error prone to click on an FX block in the editor than repeatedly move the joystick L,R, Up, Down with each movement potentially involving an unintentional rotation which changes the model selection. - multiple-page parameter views. Easier for me to scroll a mouse wheel to see all parameters of a block rather than multiple biutton presses to view different pages on the device - naming anything. An actual keyboard is nice. But I agree that once you're actually to the point of editing the parameter numeric values there's essentially no difference

Since each path has a stereo output the output blocks are only assignable in a stereo pair, e.g. USB 3/4. Your DAW however can select and record each side of the stereo pair as a mono track. So you may have to mix your paths so that each output carries a mono signal of the path using one side of the stereo pair. In other words, assign the outputs of both path 1A and 1B to USB 3/4. In the processing blocks of each path pan 1A fully L and 1B fully R. In your DAW select USB 3 for 1A and USB 4 for 1B. I'm basing this on theory rather then experimentation so it may not work like this, but worth a try.

The controller is powered by Helix. I believe the power input on the controller is there for potential but unspecified future use.

In the app you can export all IRs in one operation. This creates individual wav files in a folder on your computer. However I am not sure that this operation retains the critical association between filenames and IR slot number in Helix so the operation may not be reversible. I suggest changing the filenames of your IRs before exporting to include the slot number as a prefix to the filename. That way you can manually import the individual IRs to the correct slot.

Try the link at the top of this page.

I know the GSP has dual DSP that permits spillover, but that's only part of the problem. The spillover hides the audio gap while the next preset is loading, but it does nothing about the time taken to load the next preset. NO device can make that loading time zero ms. If you tap the preset switch exactly on the first beat of the bar where you want it to take effect, simultaneously with hitting the first chord on the beat, you won't ever hear the first chord because the preset is not yet loaded. So you HAVE to pre-select if you want that first chord on the beat, don't you? Even with dual DSP you need to 'skip some beats' at that tempo, don't you, either at the end of one bar or the beginning of the next? I know this has been beaten to death now, but it seems to me that you have to pre-select your preset switch timing if you want to hit the first beat, and that dualDSP spillover will hide the gap. So will your band. With a bit of practice and creativity in band backup and preset switch timing your audience will never care, and probably not even notice.

It is not supported but it partially works with my old Variax 300. The power is fine and communication between Helix and the V300 seems OK. I can store V300 model settings in the Helix preset and they are recalled correctly, resetting the V300 model as prescribed. However the settings must be made using Helix. V300 to Helix communication does not work for me. If I manually select a V300 model the change is not properly captured or stored in Helix. Since Helix <-> Pre-JTV communication is not supported it is possible that your experience might be different. Give it a try to see whether you can find an acceptable way to work things.

Depending on how DSP-intensive your bass processing is you might be able to get away with using only Path 2B for that, allowing you to effectively use 3/4 of overall HELIX DSP for your guitar and 1/4 for the bass. The reality is that amps and IRs are the most DSP-intensive blocks. The more of those you use the less DSP remains for other purposes. Every device has its DSP limit. Line 6 is somewhat unique in allowing you to control the DSP allocation rather than placing arbitrary design constraints and restrictions that limit your options. (e.g. only permitting one amp/IR pair per path)

Depending on the type of UX-1 and its purchase/registration date you may be entitled to a license for the original Pod Farm software. Run Line 6 Monkey with the UX-1 connected. It will let you know what you're entitled to and help you download and install Pod Farm if entitled.

Then I'm not sure what the point is. You're asking if you should be able to do more with only half the device's power? Why not start using the other half?

I would try saving and reloading my setlists now, before reloading the previous bundle. That should work successfully (the backup bundle recommendation was only a precaution). If there's no problem I would forget about the backup bundle. Note: while doing this create a new folder; do not overwrite any previously saved setlists. If there is a problem then: - reload previous bundle - backup individual non-factory setlsits - restart/reset Helix to restore factory setlists - reload individual setlists

The new (beta) versions of Helix firmware and application, including the editor, are now available. Although public beta versions they are very stable and I would advise updating. In preparation for updating Line 6 advises that you should back up existing presets using Helix app v1.04. That may be what you are trying to do. Perhaps you could try exporting individual setlists rather than the entire bundle. No need to export the factory setlists since you can replace those in the new update. Export your custom setlists one at a time. That may help you isolate the problematic preset(s). If a setlist export fails, consider all presets in the setlist and individually back up the ones that you really want to keep. If an important one is corrupt and fails to export then you can take note of its settings and recreate it manually after updating. Yes, this will take a bit of extra time but I think it's worth it if you don't want to lose your custom setlists and presets. After updating be sure to reset the device to the factory presets. This will get rid of any corruption that might otherwise linger.

I noticed this item in the release notes: - Keyboard shortcuts won't work if an item in the Librarian pane was clicked I don't know what keyboard shortcuts this refers to but perhaps you can chase this down.

I do that now by filling up a template preset with a bunch of these blocks and settings. I would never use the template preset as an actual preset - it's just a repository from which to cut and paste.

I suggest you upgrade to the latest beta editor and firmware. They are now publicly available in the Downloads area of this website. Check the 'beta' box to make them appear in the list. Let us know if the problem persists.

That's what I do. My patches are not complicated and I try to use FX as required to stay within the same patch for each song. New song, new patch (at least when playing cover tunes for a set). Patch switching between songs causes no 'annoying interruption', even if you choose to change the order of your songs on the fly because there's generally at least a few seconds pause between songs. Plenty of time to decide on the next song and switch to the appropriate patch. And the odd time that it is necessary to switch patches within songs the few milliseconds delay is not an issue for me. I pause playing, the rest of the band makes that unnoticeable, and I resume a half second later. The whole thing is a non-issue for me. However, I understand and respect that it is an issue for some. Personally, I think there will be improvements in this area in a future firmware release.

I don't think there's any relationship between the two in terms of new product releases. Variax Standard is still quite new; I wouldn't expect anything new at this point.

Try increasing the output volume level of your computer.