Jump to content


Line 6 Expert
  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by silverhead

  1. I would back up everything and then reinstall the firmware. If the issue persists it is likely a hardware problem.
  2. Depending on the specific IR and guitar I use both different mix settings and different block placement (IR and preamp). I experiment with all arrangements and settings and end up with whatever sounds best to me in any given preset. There’s no right or wrong here - whatever sounds best to you is right for you.
  3. Yes, factory presets are sometimes but not always update in new firmware. The firmware update process does not install the new factory updates; it leaves all presets in the device as they were. Yes you should back up your custom setlists before doing a firmware update. To see any new factory updates you would do as you suggest - perform a factory reset and then import your non-factory custom setlists individually. For reset options see:
  4. Read the thread that @voxman55 referenced at the end of the first paragraph in his response above.
  5. I don’t expect that POD Go presets will ever be compatible with Helix Native presets.
  6. Yes, dynamic DSP management does expose the DSP limitations of a device. But that doesn’t mean that static management devices don’t have DSP issues, or are ‘immune’. Far from it. EVERY audio processing device has its DSP limitation. All that static management does is ensure that you never encounter the limitation by placing handcuffs and constraints on the user. Your previous ZOOM, Valvetronix, and Flextone devices placed certain limitations on preset construction. E.g. only one reverb; no distortion and compression block in the same preset - choose one or the other, no stereo FX, no simultaneous mod and delay blocks, can’t have the Spring reverb at all - it’s simply not part of the product, etc. That way you were prevented from ever seeing the limitation. It also ensured that you could virtually NEVER use all the available DSP; there was always some waste. Of course the POD Go has its own limitations but not as constraining. Dynamic management leaves you in control and provides much more flexibility while also permitting you to use virtually ALL available DSP when you want to. But yes, it takes user awareness and responsibility. Until you understand how it works it can leave the impression that the device is underpowered even though it is more powerful than its static management $$ competitors. Enjoy your POD Go. I know you will.
  7. 1) You will see Line 6’s notes about Catalina compatibility in a link near the top of this page. 2) The POD X3 series is not compatible with iOS afaik. Others may have more info about this and can report here. 3) This is probably your best bet. Note that the POD X3 is not a full midi device; the implementation does not support all midi commands and features. Here’s a snip from the X3 manual: MIDI – connect POD X3 Live to your MIDI equipment to send and receive Program Change Messages for selecting Presets. POD X3 Live’s MIDI Out connects to another device’s MIDI In; its MIDI In goes to another device’s MIDI Out. Chapter 6 has info on setting your MIDI Channel for communication. Visit www.line6.com/manuals for more comprehensive MIDI CC information. .. and here’s the midi reference manual... .
  8. This sometimes happens due to very slight vibrations in the surface where the unit is resting. This can cause the system to interpret the vibrations as movement of one or more of the knobs, causing unexpected changes in parameter values. To see if this is in fact the issue, try rotating all the knobs to their min or max positions; they are less sensitive to detected movement in these positions. Of course as you do that the sound of the preset will change. Just switch presets without saving the changes and then return to the preset, leaving the knobs at the min/max positions. Then continue to use the device as usual and see if the unexpected changes continue. If so there is a different problem.
  9. Thank you for the chart and all the effort that went into it. During my experiments related to this thread I was amazed at the accuracy. The mere 0.8% discrepancy I noted at one point is essentially a rounding error and not indicative of any inaccuracy in your numbers. I strongly agree with you about how to make best use of the chart. Build your presets without any consideration for DSP until and unless you hit the limit. Then use the chart to determine the most DSP-effective adjustments to the preset.
  10. I understand that you are trying to make a product purchase decision and I am impressed with the level of detail and understanding that you have achieved in that effort. I am not trying to sway your decision one way or the other - just trying to help you get the facts and data behind some speculation and calculations. I spent another while on this just to see what I could produce and to assess the accuracy of the DSP allocation chart produced by Ben Vasco based on your listed amp/FX blocks. It is very accurate. I was able to create the following preset: Brit Plexi Normal channel; 4x12 Greenback 25 cab; '63 Spring Reverb; Tape Echo; Script Phaser. According to your calculations and Ben's table that utilizes 98.25% of DSP. That seems to be very accurate because there's only 1 FX block I can now add as the 4th flex block from among all the FX types - the Hard Gate in the Dynamics section. According to the chart it utilizes 2.55% DSP which would exceed the 100% limit by 0.8%. The fact that it and only it can be added indicates that Ben's figures are very accurate. You can be confident using them to do further thought experiments on possible preset creations and limitations. If there's anything specific that you'd like me to test and verify just send me the preset specs and I will attempt to create it. In particular, you are correct that the Tube Screamer cannot be added as the 4th block to hte above preset specification. You would have to make compromises to get it into your POD Go preset. For example, the Spring reverb is a very expensive choice in terms of DSP. Replacing that with either the Ganymede or the Glitz model allows you to add the Tube Screamer in the 4th block. Both the Ganymede and Glitz are very rich models and I am quite confident that you could choose one and set the parameters to achieve a result that you would like every bit as much as the Spring reverb. (Note: I tested but neither of these reverb models + Screamer allows you to restore the Brit Plexi Jump amp model that you would prefer.) The preset with 4 flex blocks is attached. It seems the POD Go comes very close to being able to handle your ideal preset. You are making a small compromise in going with the Normal rather than Jump amp channel, and I expect you could find a satisfying compromise elsewhere to be able to use the Jump channel. I don't think you'll feel like you made a compromise with the reverb at all because I expect you will be quite satisfied with the reverb model replacement; you may even prefer it. A very positive note is that you are virtually fully utilizing the device DSP - which is a big part of the price/value equation. All devices that use a static rather than dynamic DSP allocation virtually guarantee that a significant amount of DSP remains unused and wasted in any preset. Wasted DSP is wasted $$. That's why I prefer dynamic DSP management; leave the user in control. Not to say that every preset you create should fully utilize the DSP but you are wise in making sure your purchase will be able to produce the specific amp and FX models that you want most to use. Another thought.... If you really want to expand the DSP capacity of the device try using an external pedal in the FX Loop of the POD Go. In your case, purchasing a used Spring Reverb pedal would increase your available DSP by 25%. I know it's additional expense and I'm not recommending it, just noting the option. Anyway, good luck with your decision. (The POD Go sounds excellent - just sayin') ;-) DSP Stress2.pgp
  11. I know as much as you do about hubs, namely that Line 6 recommends against using one with their products.
  12. You could just use a USB-C printer cable. This would connect directly from the HX Stomp or POD HD to your computer with no need for a hub.
  13. This topic intrigues me so I spent my Sunday morning coffee time doing some exploration using my POD Go. I set out to bring the POD Go to its knees in terms of DSP utilization using as few blocks as possible. I designed a preset that begins with the most DSP-intensive amp and Reverb models based on the above observations by voxman55. Having done that I then modified the preset by reducing DSP utilization in some model selections in order to permit the addition of certain model types to the preset until all 4 flex blocks are assignable. The details of the experiment are described in the attached document for interested readers. For those who may only be interested in a summary.... The 'minimal' POD Go preset seems to be an amp with its default cab, the fixed FX blocks, plus 2 flex FX blocks (1 reverb and 1 delay). At this point, if you've selected the most DSP-intensive models of each of these types, you are unable to add a 3rd flex FX block to the preset. However, with some compromises you can readily edit the preset to achieve the allocation of all 4 flex FX blocks. Also attached is my resulting preset. Note that I never even listened to this preset - I never had my guitar connected - so it likely sounds like cr@p. This was purely a preset design exercise using Pod Go Edit and the default parameters of all blocks. Listen at your own risk!! EDIT: I just listened to this preset. I have 2 pieces of advice to you. 1) DON'T listen to this preset!!! If you choose to do so, turn DOWN your volume! 2) DON'T design presets by trying to max out the DSP! And remember... this is an experiment designed to max out the POD Go's DSP. Under normal circumstances, without such nefarious intent, a user who did their research before purchasing the POD Go will rarely (imho) encounter meaningful DSP limitations. Having said that, you might just be the user whose basic 'go to' preset is the Brit Plexi Jump amp with the'63 Spring reverb and 6-head muli-tap delay. If that's the combination you can't live without - the POD Go is not for you unless you offload one of your reverb or delay FX to an external pedal in the FX Loop. Otherwise you should be OK. POD Go DSP.txt DSP Stress.pgp
  14. Your Marketplae assets should be available for download immediately. To download them go to your Line 6 account page. Under Support tab above, select Account Services - My Account. Then select Helix Marketplace in the left column.
  15. Several years ago I had repeated problems with Logitech devices (a USB mouse and a webcam) interfering with my Line 6 devices. I came to the conclusion that Logitech and Line 6 just don’t play well together in Windows. I ditched my Logitech stuff and haven’t routinely had USB connectivity issues since.
  16. The tempo issues are fixed in v2.92 Is it ‘safe’ to update? Probably, but I’d still wear a mask, wash my hands, and keep a fire extinguisher handy. Oh - and don’t do it after curfew.
  17. It's the opposite. Update HX Edit first and then use that to update the firmware.
  18. I've checked on my POD Go and I don't see this behaviour. The VOL pedal works on the later factory presets unless you manually turn it off. I do notice that these presets are very heavily effected, as you say. This causes the change in VOL pedal position to be less noticeable and somewhat delayed, but it's working for me. Press the pedal to full heel position and wait a few seconds; the sound disappears. A VOL pedal consumes very little DSP - that's not an issue.
  19. The different shading reflects different modeling technology. The darker colours indicate models based on the latest Helix technology and the lighter colours indicate older technology. So the 70's Chorus uses Helix modeling on the BOSS CE-1 while the Analog Chorus uses older technology to model the same BOSS pedal..
  20. No, Helix Native and POD Go are not compatible. You can’t swap presets between them like you can Helix Native and a Helix device. Of course you can use the POD Go as your audio interface device while running Helix Native in your DAW, which is what spaceatl is doing.
  21. silverhead

    Helix LT IR's

    Just want to start from basics...... The POD Go ships from the factory with all IR slots empty. IRs are third party entities that must be manually added to the IR library by the user. Adding an IR to the library is a necessary first step before you can select an IR from the library to add to a preset. If you have never added any IRs then what you are describing is normal. You should expect to see all IR slots empty when you attempt to include an IR in a preset until you have added some iRs to the library.
  22. silverhead

    Helix LT IR's

    Are you still getting the error when trying to load an IR? If so I suggest you open a support ticket.
  23. Yes. It all depends on how DSP-intensive your selected 3 blocks are. As already described, 3 Reverb blocks probably precludes adding a 4th. Similarly, 3 other DSP-intensive blocks of any type may do the same. I know there is a listing for Helix, submitted by a user, that identifies the relative DSP intensity of each amp, cab, and FX block. I don’t have an exact reference for you. I don’t believe such a listing has been created for the POD Go but it would be similar. In my experience with the POD Go I have never encountered the DSP limitation (I.e. I’ve not seen any greyed out boxes) unless I am trying to double or triple up on some model types. I do not think this is a regular event with reasonable selections. You can count on being able to select all 4 of the assignable FX blocks in most cases.
  24. silverhead

    Helix LT IR's

    As suggested earlier, try reinstalling the firmware. After firmware installation your Helix will automatically restart to rebuild the presets and create the newly designed IR library. Allow this process to complete.
  • Create New...