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

silverhead

Line 6 Expert
  • Posts

    12,113
  • Joined

  • Last visited

  • Days Won

    376

Everything posted by silverhead

  1. I’m not a Spider owner but I don’t see why not. Download it and try. Bad advice. Sorry. I didn’t realize the amp has no USB.
  2. This is a user forum. Line 6 hosts it but it is intended for Line 6 product users, not staff. Participating in this forum is not part of anyone’s job at Line 6.
  3. Seriously, tell us exactly what you did in as much detail as possible. Simply saying that you did something wrong doesn't help us help you.
  4. Just to be clear, I am talking about listening to the demos/videos while your POD Go is connected via USB to your computer with the associated external speakers/amp active. Don't just listen to them using, for instance, only your laptop. But if the patch creators allow you to actually download sample patches then yes, load them into your POD Go.
  5. The POD Go is a single path device. You can’t process two inputs independently. I don’t know about the technical aspects of potential overload or risk by using two inputs simultaneously but I do expect that the resulting sound would probably be awful. I think the input selection of Guitar + Wireless is designed more for the convenience of users who want to switch guitars at various points during their gig. This input setting allows you to put one guitar down and pick up another without having to swap out any cables. All you’d have to do is turn up/down the Vol knobs on the respective guitars when you swap them.
  6. Some good insight above from voxmann55. Someone else’s patches can provide you with some good examples of patch construction and signal routing ideas but you will almost always need to tweak them to make them sound best using your own equipment. And if you’re not familiar with tweaking patches you can be disappointed. And how do you get familiar with tweaking patches? You learn to create your own, at which point purchasing them may be unnecessary. I’ll emphasize point numbers 2 and 6 in voxmann55’s list. The external equipment, specifically any differences in equipment between the patch creator and you, is critical. The most important factor is the speakers. Most patches available for purchase are designed for output to PA systems or FRFR speakers. If you use a typical guitar combo amp and speaker/cab with the POD Go you will likely be very disappointed with any patches you purchase unless you know they are designed for that configuration. Nonetheless I have purchased patches in the past and found some to be very helpful, not only in the tones but sometimes more importantly in patch construction ideas and examples. With reference to the three purchase options you specifically mention I think only you can decide for yourself. Listen to the samples using your POD Go and the connected speakers/amp that you will be using with it. Do not make your choice by listening to these samples using your computer’s soundcard and speakers.
  7. It sounds like you have already contacted Line 6 Support about this. Seems there are two separate issues here: 1. Registration of the Helix device based on its serial number as now belonging to you, and associated with your user account, for ongoing support and warranty purposes. Device ownership is transferable and Line 6 support is usually able to do this for you. They may need to contact the previous owner on your behalf to ensure that the transfer of ownership is valid. 2. Eligibility of the device for a discounted price on the purchase of Helix Native. Only one discounted purchase per device is permitted. Hence the price discount is not transferable to you if the previous owner has already purchased Helix Native at a discount.
  8. What software are you using? Do you have a recent backup of the folder on your computer that this software uses to store its tones?
  9. Also,see manual page 8.2 for USB info. The dry signals from Tone 1 Input and Tone 2 Input are sent over USB channels 7 and 8 to your computer. Make sure Pod Farm is set to receive, as its input, whichever one of these channels/signals you want to use.
  10. See manual page 6.2 Outputs. Set both Tone 1 and Tone 2 to Mute for the outputs your speakers are connected to (XLR or 1/4”).
  11. How are you attempting the backup? Are you talking about the forced backup that is part of the upgrade procedure? Start by downloading and installing HX Edit v3.10. Install all components then run HX Edit.
  12. To understand how this setup will work you may need to understand a bit more about both your X3, the Pod Farm software, and also how your speakers or headphones work with the X3. The X3 processes your guitar signal and sends the output to connected speakers, headphones, and also over USB to your computer if connected. The settings in your X3 allow you to control these output destinations. The X3 is also an audio interface device that communicates with your computer over USB, independent of producing sounds from your guitar. For instance, you can use the X3 as your computer’s audio card and listen to iTunes, YouTube or whatever using the speakers or headphones connected to your X3. You don’t need to have your guitar connected for this. Pod Farm is a program that runs on your computer and produces guitar tones from the signal it receives over USB from a connected audio interface device such as the X3. In this case the guitar signal you want to send the computer over USB is called the ‘dry’ signal. In other words, both your X3 and Pod Farm are intended to take a dry guitar signal as input and process it to produce the ‘tones’. The tone generation aspects of both the X3 and Pod Farm are not meant to be used or listened to simultaneously, as you’ve discovered. To hear the Pod Farm tones without hearing the X3 tones you need to: - connect your X3 to your computer over USB - connect your speakers or headphones to your X3 outputs - configure your X3 to NOT send its processed audio to the outputs you are listening to. You only want to hear the computer’s output (Pod Farm) from the X3 outputs. - configure Pod Farm to take the ‘dry’ tone signal sent by the X3 over USB as its input. The manuals will help you from this point.....
  13. You need to feed Pod Farm the ‘dry’ signal from your X3 over the USB connection. The dry signal is the completely unprocessed guitar signal, not just a clean neutral tone. Consult both the X3 and the Pod Farm manuals in the USB Audio sections to get the details of how to do this.
  14. Again, Pod Farm is not a replacement for Gearbox. They are different types of products. Rather than thinking of Pod Farm supporting your X3, it’s actually the other way around. Pod Farm is supported by an audio interface device to get its sounds/tones into either a recording program running on your computer or into external speakers. The X3 is one such audio interface. But when used on this way the X3 is not producing its own sound/tones; it is acting strictly as an interface device for the Pod Farm and recording software running on your computer. Pod Farm has no ability to interact with the X3 in terms of an editor/librarian.
  15. Pod Farm is not meant to be used along with the POD X3 tones. Pod Farm is software that produces tones using the hardware of your PC; the X3 produces its own tones using its own hardware. Gear Box is an old tone editor/librarian that was used with the X3 back in the day. I’m no longer familiar with what you should/can use today as an editor/librarian with the X3. However, you can do all your tone selection and editing using the X3 itself. You just won’t be able to back up and restore things to/from your computer. Perhaps others are more knowledgeable about what librarian software is still available for the X3, and they can help you with that.
  16. Make sure your version of POD Go Edit and the device firmware are up to date. If so, I would back up everything using POD Go Edit, then perform a factory reset, then restore everything. Sometimes this clears up operational issues.
  17. I do see your point and it’s valid. But again, the way to potentially get this change implemented is via Ideascale. Have you submitted this request there?
  18. The way to draw this feature request to Line 6’s attention is via Ideascale. This discussion won’t change anything.
  19. I presume the Global Settings would be locked up with a Global Setting of some sort? Which, itself, would then be locked? Interesting Catch-22!! Of course in the world of computer security this is usually solved by requiring a password to unlock it. Easily done, I suppose..Because... well .... what if someone else decided to unlock your settings to cause you havoc and chaos?... ;-) (jk)
  20. Yes, all these changes should only be made very intentionally. All of them (except tuner access) require you to specifically press the MENU button and then choose a submenu. You can easily avoid doing this during a gig. Since it’s done so intentionally an extra prompt to make sure you mean it seems superfluous. As far as the tuner goes, you can access it with a HOLD of the Tap Tempo / Tuner switch. Again, a very intentional action. How does one manage to change the tuner calibration by accident? It requires you to not only intentionally access the tuner but then to rotate one of the encoder knobs. Your foot is nowhere near those knobs when you press the switch. You would have to do it by hand methinks. Again, a very intentional act during a gig and easily avoided.
  21. The annoyance factor is exactly why the ‘latest trend’ began many years ago now. Helix does require a 2-step SAVE procedure for presets, and provides an indication that a preset has been changed so that you won’t switch presets without saving unless you want to. Surely you don’t want the confirmation prompt for every change, like changing an amp’s drive value, any more than you’d want to be prompted every time you enter a new character in a text editing program. So what sorts of changes do you want to see specific prompts for? Apparently the tuner offset is one. Others?
  22. That means something went wrong in your environment - that's not what should have happened with HX Edit v3.01. It should have guided you through the installation of HX Edit v3.10 first. Perhaps you should open a support ticket and describe what happened to Line 6 tech support. They may be able to use that info to track down a bug.
  23. No worse than shaving in the bathtub with an electric razor, and dipping the head in the water to clean the blades.....
  24. The situation you describe could happen pre-v3.01 but is now fixed. The ‘line of code’ you ask for is already there. As of HX Edit v3.01, HX Edit recognizes when an update exists and informs the user. Timing of the update the user’s choice - not automatic - as it should be. Sometimes people just don’t want to update right away. The automatic update does install HX Edit first. If this didn’t happen it means you were not updating via HX Edit v3.01 or later, as specified in all the release notes. This should not happen again.
×
×
  • Create New...