Please ensure Javascript is enabled for purposes of website accessibility Jump to content

All Activity

This stream auto-updates

  1. Past hour
  2. Yeah, that should just work if you are using just it as a box of extra FX in a regular pedal board setup. Then just assign a block for whatever effect you want to use in the HXS, for example, pitch shift, chorus, glitch delay, shimmer verb, looper, whatever. You can use the FX Loop option for your other external time based hardware units. Have fun!
  3. Yesterday
  4. Yes, I had something like that a few times since one of the recent firmware updates. As @Schmalle said, turning the device off and on fixed it.
  5. I think I had this issue once or so, too, but it was just a matter of power cycling to get it fixed. Is it like this every time you turn it on? Is it dependent on the duration it was on? Can you connect with HX Edit and perform a backup?
  6. Hello! I've got the HX Stomp running firmware 3.71.0. I've got it plugged directly into a tube amp using mono channels. I haven't updated the firmware or changed anything recently. The last time I turned it on, it was fine. But now it seems like the unit is just bypassed. It turns on, I see the display, I'm able to manipulate the pedals and effects and use every feature. But it's not affecting the sound that's coming out of the amp at all. Has anyone had this happen to them in the past? I know that doing a factory reset is the likely the next step. I'm just worried about losing all my configurations, as well as the overall dependability of the unit in a gig setting at this point. Thanks for any insight!
  7. You just need the FX Loop block in the preset for all external stomps. You don't need a block for the external expression pedal;' it just needs to be connected and defined in the POD's Global Settings.
  8. Maybe I'm not understanding how the blocks work... So as far as other pedals go, I have a standalone compressor, tuner, 3 drives, a delay and reverb. Will I still need to use the blocks to accommodate them as well or just for the effects loop and expression pedal? And I probably wont need the amp and cab. I primarily will be using the Stomp as a pedal for some effects I don't have, its effects loop, and hopefully looper.
  9. never messed with Z on the Helix. Just let it do it's default thing... based on the first pedal in my chain, which is always a wah-wah.
  10. It is useful for POD Go devices that have not yet had a manufacturing hardware fault fixed. Line 6 has a lifetime warranty for this issue so if you get it fixed (no cost to you) you will no longer need the buffer. Contact support to get it fixed.
  11. Hi all, I've read that putting an analog boost pedal in front of digital multi-effects processers like the POD Go, Helix, etc. can do wonders for improving the overall tone. Additionally, the person that sold me my POD Go suggested putting a simple buffer--even just a tuner--in front of it for a similar reason. Does anyone have any experience with this? If so, are there certain pedals (or types of pedals) that you'd recommend? Thanks for any suggestions!
  12. Hi, Best place for help on how to wire it up is to see the HX Stomp3.0 Owner's Manual > Pages 9-11, Quick Start "Hooking it all up". https://line6.com/data/6/0a00050b058066312873a50cf/application/pdf/HX Stomp 3.0 Owner's Manual - English .pdf O.K. even as a newbie, at the very least you should have checked out the basic spec of the HX Stomp, which would reveal that you are limited to signal path that can contain a maximum of 8 blocks available to play around with. Looking at your example above, if you are considering using an external expression pedal that's one block gone, Compressor is another block, SEND/RETURN FX loop is one, or possibly two more blocks depending on the use. Then after the return, a Delay, Reverb and Looper block. Now you have used at least six blocks, without even mentioning an Amp and Cab, block which would only leave space for one, not several, Drives. Hmm... that's the down side to having limited block options, but a few folks have come up with a few workarounds for using a n expression pedal to switch between a Vol and Wah effect, or even save a Volume block by mapping an Exp to the Amps channel volume. One other thing to remember is, the HX Looper was not really designed to be a full on performance looper, but if you can work with the limitations of a 60 second Mono, one switch looper fine. Personally i have a whole bunch of separate, external looper options. This guy has a couple of tricks for using a Dunlop X Mini Volume and Expression Pedal with the HX Stomp. Hope this helps/makes sense.
  13. Thanks for the warning! I've been reading through all the specs. Too bad it's limited to 8 switches for pedals in stomp mode (unless they've done a firmware update I don't know about?). However, it has FULL HELIX DSP like you said! No worries, I'm not going to be pushing against the resources either.
  14. Thanks! I've already ordered new XLR cables!
  15. Follow up.... Headrush tweeter is not working. On a hunch, I opened the grill of my Headrush 108 and played and listened to the speakers. The tweeter is not working. It must have been intermittent at one point because I remember one day the rig sounded amazing and the next day it was trash. One day I tested the Headrush against the Powercab to see if the Headrush was broken. They sounded the same until i accidentally put switched the powercab from FR to a speaker model. It sounded great. Mulling this over, I realized the Powercab speaker model included the tweeter. Looked into tweeter issues with the Headrush and found that mine is broken. Answering the obvious, why am I using the Headrush when I have a Powercab? I have a small office and apiece of furniture that perfectly fits the Headrush and the HX Stomp. I spend most of my time in here and wanted a compact solution. The Powercab was too big for the room.
  16. The 1/4" outputs are "unbalanced" on the LT. They can be set to line level output... but that is just level, it has nothing to do with "balanced or unbalanced". From page 9 of the v3 manual.
  17. There are still limits you'll need to work within. Compared to a stomp it may have 4 times the number of block allocations, but it only has twice the DSP. It's never been an issue for me... I can always work within the limits. However, I am reminded of the limits when I want to try something and it's "grayed out".
  18. Same here. It seems that the AU version of Helix Native does not receive PC messages smoothly. When changing the preset with a PC message, the process of the CPU jumping and focusing on the changed preset is also slightly strange. I've tried various DAWs and AU Hosts, but they are all the same.
  19. Yes, your right! I did miss the elephant in the room. That's why I'm selling my PodGo, I totally bypassed a Stomp XL, and purchased a HELIX LT instead this evening! :-) My HX Effects already uses the same editor as a HELIX LT, so now I probably have all the resources I'll ever need, for direct recording or for LIVE!
  20. It makes total sense! Thanks for responding. No matter, I just purchased a Helix LT tonight, which will arrive next week. No more worries about running out of DSP, or blocks, or pretty much anything else. Dual chips, all the blocks I want to play with, and probably more resources than I'll ever use, or need.
  21. I just purchased a HELIX LT to replace my PodGo, which I've been using to record with. I've been feeding balanced 1/4" Mogami cables from the PodGo (which has balanced 1/4" stereo outs) into the XLRs on my mixer and multi-track. I see the Helix LT has both balanced XLR outs, AND 1/4" outs (but the manual "hints" they ARE NOT balanced?). My Helix is arriving in about a week. Do I need to order new cables ASAP with all XLRs, or will I be able to keep using my balanced 1/4" cables with the Helix LT?
  22. Last week
  23. Hello everyone, I'm encountering an issue with the AU versions of Helix Native (version 3.71) when using MIDI to trigger preset changes within Logic Pro and Ableton Live during a song. Whenever a preset is switched via MIDI, there’s a noticeable hiccup or lag in the DAW's tempo and a significant spike in CPU usage. This problem does not occur when changing presets manually directly in the plugin's interface, nor when changing snapshots. Interestingly, the issue is doesn’t happen in the AAX version of Helix Native in Pro Tools, which operates smoothly. Unfortunately, I cannot test this in the VST3 version in Ableton since it does not support MIDI. After reaching out to Helix Native support, I received a generic troubleshooting guide that did not address the specifics of the problem, and they did not even attempt to reproduce the issue. The support person was able to mark the ticket as "replied" which is all that matters. Can anyone else confirm whether they have or do not have the same issue? Can someone please try to reproduce? I can't be the only person in the world who tries to switch presets (not snapshots) during a song with MIDI. Thank you all in advance for any help or guidance you can provide!
  24. When attempting to update the TBP516G transmitter using Windows, some users have reported that the device either does not establish a connection via USB, or loses the connection during the update. It is worth noting that Windows supplies the driver for this Relay device. There are two scenarios where the Relay device is not recognized by the updater app after connecting via USB: the updater is launched before the Relay device drivers have finished installing. This may occur more often on slower computers, computers that already have several open windows or processes, or with machines that have a slower internet connection. the "Driver not successfully installed" message appears. In this case, click "Change settings" then choose "Yes, do this automatically (recommended)" in the Device Installation Settings dialogue box, then select "Save Changes". In the event the "Driver not installed" message box is not present, you can navigate to Device Installation Settings using the following steps: Click Start, type "devices and printers" in the search box, and then click Devices and Printers. Under Devices, right-click the icon for the computer, and then click Device installation settings. Choose "Yes, do this automatically (recommended)" and select "Save Changes" button. After changing this setting, remove the USB cable, then insert it again so that Windows can detect the Relay device and install the driver for it. It is possible to see the Relay device update fail shortly after it starts. This can occur if one of the Relay device drivers has not finished installing before you initiate an update. In this case, the updater will typically display that the firmware version is unknown. The workaround here is to wait until the driver completes installation, or disconnect the USB cable, reconnect it, then start the update again. Lastly, it is worth noting that some USB cables are charge-only, so a change in cables may help. Also, trying all ports and even a different computer may resolve the issue, based on various USB port configurations.
  25. Please review this link as a further explanation on topics that are covered in the document below: http://www.churchproduction.com/story/main/a-small-churchs-guide-to-working-with-wireless/3 As the environment is the biggest factor in wireless audio performance, there is a chance that certain environments and circumstances will not allow for satisfactory performance. This can be verified by successful performance in a different environment. This is an extremely informative video on how all wireless gear works in a WiFi rich environment Note: If you have multiple members in your band with Line 6 wireless, everyone needs to be on the same RF mode. Pre-Qualification: First Things To Rule Out: Use the factory power supply Try on more than one channel! Try in more than one place/venue Check the transmitter LEDs during drops/interference. RF dropouts result in the green LEDs going completely off. Even one green LED means the signal is present and something other than the wireless system is causing the problem. If you see full red LEDs followed by quickly shifting back to green, it means that the system has re-synced (normal if the dropout is too long). The red LEDs come on only if the intended signal from a Line 6 transmitter is not present. In this case, they are showing RF competing for the same space. Interference: Symptoms Reduction of RF LEDs on the front panel that indicate usable RF signal strength Audio signal muting Possible causes Trying to function at too great a distance Having unintentional transmitters, such as walkie talkies or in-ear monitors, too close to a receiver Significant amount of close-by RF signals within the same 2.4GHz range (Wi-Fi, microwave ovens, etc.) Suggestion "Walk test" your system in advance of an event over the entire desired range to verify that sufficient RF signal is available to avoid mutes from occurring With transmitter off and receiver turned on, scroll through the channels. Red LEDs indicate stray RF on that channel. Choose channels that exhibit the least red LEDs. Note: Line 6 wireless WILL still operate but at reduced range. Decreased Range Symptoms Reduction in range in general Reduced range indoors vs. outdoors Possible causes Blocked "Line of Sight" between the receiver and the transmitter Barriers such as walls or air-curtains can impede the path of radio waves Transmitter strength reduced if it must pass through walls Transmitting through earth (receiver in basement) Human bodies absorbing RF energy Receiver is very close to other intentional radiators in the same frequency band such as Wi-Fi wireless access points Suggestions Improve "Line of Sight" Elevate the receiver Weak Audio (thin audio output compared to other wireless systems) Symptom Weak and/or noisy audio output Possible causes Gain/trim settings on mixer need adjustment Plugging into a "line level" input Plugging into a channel with pads engaged Using a TRS plug in the 1/4" unbalanced output Suggestions Adjust gain/trim as if using a wired microphone Connect the XLR output on the receiver to an XLR input on the mixer Use a mono plug in the 1/4" unbalanced output, never a TRS plug Dropouts ("Audio" vs "RF" dropout: different paths to correct) Symptoms Audio signal interrupted Possible causes Local conditions in one or more venues, e.g. a large Wi-Fi installation in close proximity, metal walls/roof Instruments or amps being used are faulty Signal chain issue Blocked "Line of Sight" between the receiver's antennas and the transmitter's antennas Other XD-Vs/Relays operating on the same channel Receiver near any transmitters such as walkie-talkies, In-Ear Monitors, etc Using a substitute power supply Suggestions Try a different venue to reproduce problem Try multiple instruments/amps to reproduce problem Trace signal through chain one component at a time. "Audio" LED lights when signal is received. Improve "Line of Sight" by moving receiver to 6-8 feet high while avoiding obstacles such as metal posts, walls, etc. Ensure each system has its own unique channel to operate on Move intended transmitter closer to receiver than unintended transmitter to eliminate "near/far" issue. Provide ample distance between the receiver and other transmitters. The distance will depend on the strength of the transmitter and the gain of the transmitting antenna. Use the factory power supply or one that can supply the required 9v DC current. If you are using a pedalboard supply, it must be able to supply this amount of power to the receiver in addition to whatever else you have plugged into it. Q: Does USB 3.0 create interference in the 2.4GHz frequency range? A: USB 3.0 computer cables and peripherals, including hard drives, are known to emit radio frequency interference throughout the 2.4GHz band, which results in reduced range and/or performance for any 2.4GHz device in its proximity (including wireless keyboard or mouse, WiFi, etc.). We recommend placing any digital wireless receivers at least two meters away from the USB 3.0 device and its cabling. Below is a link to a study by Intel regarding this interference. http://www.intel.com/content/www/us/en/io/universal-serial-bus/usb3-frequency-interference-paper.html References for working with wireless systems http://en.wikipedia.org/wiki/Non-line-of-sight_propagation http://www.djsociety.org/Wireless.htm
  26. Hello all. I recently purchased an HX Stomp and, I'm sure its been asked many times, but I was hoping for some help in how to wire it? I'm wanting to use it for some wah and pitch-shift stuff up front but also the looper and time based effects in the back. But I want to use my other pedals for the time based stuff. Can the HX Stomp be wired in that way? I.e. Volume>(HX Stomp?)>Comp>Several Drives>(Maybe HX effects loop here along with some other built in effects? Not sure if possible)>Delay (Possibly in the HX effects loop)>Reverb (Possibly in the HX effects loop>HX Looper. Probably not necessary info, but I also have the JET Pedals midi controller for the Stomp. I know this sounds like a stretch, but if I can get remotely close to it, that would be great. Any feedback would be appreciated! Thanks!
  27. If you really want to know about DSP per block in the Helix/POD Go family of products, I would suggest you have look at the DSP chart created by sometime forum user Ben Vesco "Malhavok". https://benvesco.com/store/helix-dsp-allocations/ Hope this helps/makes sense.
  28. Q: Are XD-V Wireless Products still manufactured? A: No, XD-V Wireless Products are no longer manufactured as of January 2024. Despite this, retailers may still have units in inventory over time. Q: Why are they no longer manufactured? A Typically, as with many companies, the decision to end the manufacture of any YGG product is based on one or more of these factors: a lack of market demand, a planned successor product, or because the parts to manufacture it are no longer available. Q: What product will replace XD-V Wireless Products? For a number of reasons vital to our business, we can't comment on future product releases, but follow us on social media or sign up for our email list to receive new product announcements (We can change this message once the replacement product launches/is announced). Q: Why is XD-V Wireless Products at a lower price? You may find XD-V Wireless Products at a lower price at retailers to allow them to clear their inventory of this discontinued product. Q: If I buy XD-V Wireless Products, will you honor the warranty? Yes. The full warranty applies if bought as new from an authorized Line 6 retailer and a receipt copy is furnished. See our Warranty page for details. Q: In what ways will the discontinued product be supported? You can find manuals on our Legacy Products page, additional information at our Knowledge Base, tutorial videos on our YouTube Support channel, and our Customer Support team can be reached from our Contact Us page.
  1. Load more activity
×
×
  • Create New...