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

silverhead

Line 6 Expert
  • Posts

    12,445
  • Joined

  • Last visited

  • Days Won

    415

Everything posted by silverhead

  1. Sounds like you actually don’t want an amp/cab modeler at all. Have you considered using an FX-only modeler, such as the HX FX? That is designed for exactly what you say you want - plug it into an amp and be done with it. With the HX FX you can have up to 6 FX.blocks in a preset rather than the POD Go’s 4. And all 6 blocks are ‘Flex’ (to use POD Go terminology). No restrictions on block type or placement and no imposed blocks.
  2. Yes, that could indicate a bad cable. Have you tried using a different one? Any RJ-45/Ethernet cable can be used temporarily as a test.
  3. This likely related to gain staging. Are you switching 'on' other FX blocks for the boosted solo? If so it's likely that those blocks need to be inspected for levels. While in you non-solo snapshot, try activating any additional blocks used in your boost snapshot one at a time. You may find that one or more of them is contributing to the problem. Try adjusting levels/settings within those blocks.
  4. Updating or reinstalling firmware was the third most likely problem. Did you rule out the first two? Specifically, are you sure the cable and the VDI ports are OK?
  5. I expect the problem, in decreasing sing order of likelihood, is one of: - bad cable. Try temporarily using the cable that came with your JTV for connecting to Workbench HD, or any other RJ-45 cable; - damaged VDI ports at either the guitar end or the HD500X end. Inspect the ports visually and carefully straighten any crooked wires. In most cases a J-hook constructed from a wire twist tie works well; - corrupt firmware in either the JTV or the HD500X. Reinstall both; - VDI port hardware failure in either the JTV or the HD500X. Open a support ticket.
  6. There is a section in the Metallurgy Collection Pilot’s Guide describing automated parameter control within a DAW for the plug-in version. I suggest you start there and come back with specific questions after gaining an understanding of the basics and how that relates to your DAW and foot controller hardware.
  7. A firmware update takes the same amount of time regardless of the number of bug fixes. It does not overwrite a small amount of code; it overwrites the entire memory space. It takes the same amount of time even if you simply reinstall the current firmware version, involving no new features or bug fixes. Perceived sonic improvements might simply be a placebo effect or it could be very real. It depends partly on the firmware version you are updating from. For instance, if your device was previously running a pre-v2.0 firmware version you are hearing the dramatic improvement due to the new Cab engine. Also, a firmware update resets the Global Settings to their default values. It’s possible that you pre-update settings were not optimized for your equipment, and now they are.
  8. Please open a support ticket if you haven’t done so already. That’s the best way to bring a bug like this to the attention of Line 6 Support so they can log it and get it fixed.
  9. I’m always intrigued by discussions like this. A very specific question is asked, with a clear binary correct answer, in this case No. A one word answer is requested and provided. The person who posed the question disappears, having received the requested answer….. Then the thread takes on a whole different life involving other people providing their own interpretations of what else the OP might have been asking, or providing their own speculative reasons for why they think the answer is what it is - expecting that the OP must be interested in that. But the OP is gone, maybe to return and maybe not. Meantime….. carry on. I find it a curious phenomenon but perhaps someone will learn something.
  10. I’ve never tried using Helix Native for real time processing. Seems like that’s what you’re talking about. What do you mean by ‘standalone’ mode? HN is a plug-in so there must be a VST host (s.g. DAW) running on the MINI PC? What’s the latency like for playing live?
  11. Try connecting a MIDI cable from the Helix MIDI Out to its MIDI In. YOU WOULD need to turn OFF the MIDI Thru function in Global Settings. Chaos and infinity would otherwise collide.
  12. It would really be confusing if that’s the case. Two distinct notes can’t t really be said to be in harmony unless a key/scale is involved. If you use the so-called Pitch Harmony with an interval of a 3rd and then play in a minor key - it’s not in harmony unless the 3rd is flatted, and the Pitch Shift FX doesn’t do that. Calling it a Harmony FX without the ability to harmonize is misleading at best.
  13. In your account, go to Order History. Select the book and View Invoice. Embedded in there is the activation code. Click on it, or copy/paste it into a browser.
  14. A modified solution is to use two mono inputs from your keyboards. Then you can use both L and R of either the Main or the Return inputs. If you need stereo inputs from the keyboards I don’t have a suggestion other than additional outboard equipment such as a small mixer to take the two stereo input pairs and merge them before hitting the Stomp inputs.
  15. The confirmation email from Sweetwater for your original purchase contains an activation code. Click on that.
  16. Many thanks for the update Craig. I look forward to each of your updates after a new firmware release. Always exceptional. Full disclosure…. I am not in any way affiliated with Craig or compensated for the following in any manner. This is purely at my own initiative in the spirit of helping Line 6 users…… I purchased this book shortly after it was first released. It has become an invaluable resource for me and certainly a great purchase at a very reasonable price, especially considering the updates. It contains detailed and comprehensive information, as well as many presets, that benefit Helix users at all levels of experience. It would be valuable for POD Go users also since many of the amp, cab, and FX of Helix are also in the POD Go. There’s also plenty of transferable information regarding preset construction and methods. Do yourself a favour and get this book. I truly believe you will learn a great deal from it regardless of your current knowledge and skill with Helix.
  17. Did you also update HX Edit to v3.70?
  18. An afterthought….. If you did indeed originally record both the DI and processed tracks first, as described in the manual, make sure you use the DI track for reamping and Mute the processed track.
  19. It seems to me that your ‘base’ POD Go preset includes POD Go amp, cab/IR, and FX blocks. Then you want to reamp that recorded track to fine tune it. That’s a bit different from the ‘normal’ reamping procedure. Normally one records the dry (DI, no processing) track first and then reamps it to apply full processing. You quote from the manual, and that quote is a follow on from the previous section that describes how to record a Dry DI track. Note that the dry rack uses the mono USB channel 3 as its record input; not the processed stereo channel 1/2. If the track you are reamping is a partially processed track as described in my first paragraph, then you need to consider that your pod Go ‘base’ preset processing is already baked into that track. When you reamp you need to account for that fact and use a preset that applies only the additional processing you want. For instance, if you used an amp and Cab/IR in the original recording you need to remove those blocks from your reamping preset. You can’t just start tweaking, say, the Drive parameter on the amp when reamping. If the amp remains in the preset you are effectively double-amping your original guitar signal; once with the Drive setting in your ‘DI’ recording (it’s not DI) and again in the reamping with a different Drive setting. Long story short, make sure your original recording is in fact a DI recording as described in the manual.
  20. Yes, considering product support expectations before you purchase is important. and there are at least two considerations. One type of support is what we’re talking about here: how long can the manufacturer be expected to keep the product alive in the sense that it will still work as the supporting technology progresses (e.g. computer OS upgrades). Line 6 and other manufacturers of audio equipment have established a history of providing another type of product support. They regularly release product updates that do far more than just keep the product alive. They keep adding functions and features that can dramatically improve product capabilities. And the updates are free!! That gives users a whole other dimension of support to consider. Expectations in this dimension are more difficult to assess, but of course we do it anyway. And personal opinions on this matter vary much more widely, in my experience, than the end-of-life (EOL) decisions. We often see astonished cries here of ‘What?? No more feature additions and improvements? It’s only been X years since I bought this!’ The Helix product line is a great example of this. The Helix Floor hardware platform hasn’t changed since it was introduced in early 2016, and there have been nearly 30 firmware updates since that time. A few were no more than bug fixes but most were enhancements. It’s now way more powerful and capable than it was nearly 8 years ago, and there’s no reason (yet) to believe that it’s EOL is approaching. But certainly it will someday reach that point. I can’t imagine that anyone then will complain that they’ve been shortchanged (he says, with tongue firmly in cheek). But Helix has remained an improving product for far longer than any of its predecessors, most recently the POD HD series. So what sort of support expectations should a buyer have when deciding whether or not to purchase the successor to Helix whenever it is eventually introduced? I have always said (and still do) that anyone should purchase a product based on the value/cost equation at the time of purchase. In other words don’t buy a product based on personal expectations of what one thinks it might be able to do in the future. Buy it because you think it’s worth the price today, and consider yourself fortunate if there are ever any free upgrades. But Line 6 has certainly raised the bar with Helix and it will be hard for me to imagine that its successor will be ‘one and done’. Time to stop rambling…..
  21. I've bolded what I think are the key words in your post. All electronic product manufacturers make these decisions based on factors other than user's opinions. I, too, would like to see updated drivers for many of my old products, from printers to Roland/Boss audio/midi interfaces. The hardware is still fine but the products no longer work. Of course, how you want to respond to that reality (e.g. no future purchases of Line 6 products that require drivers) is up to you. But your opinion won't change anything, and the 'problem' is not specific to Line 6. Be careful you're not jumping from the frying pan into the fire, as they say.
  22. Check the manual section n Global Settings -> Footswitches. There are numerous options regarding how footswitch functions and displays work. You can choose the option that works best for you. It may or may not give you exactly what you want as described by your question but you will find a good fit - perhaps better than what you currently think you want.
  23. The Helix Floor unit has Send/Return pairs that will accommodate external pedals in an FX Loop. So even if you’re not satisfied with whatever similar FX Helix offers you can just continue to use your current pedals. And, as you note, this will conserve Helix DSP.
  24. I notice a tuning fork icon on the bottom row of the controls. What’s the display for each under that panel?
×
×
  • Create New...