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

silverhead

Line 6 Expert
  • Posts

    11,649
  • Joined

  • Last visited

  • Days Won

    323

Everything posted by silverhead

  1. I think the HX One will get you exactly nothing more than you already have with the HX FX. Theoretically it would give you one more FX Block but in fact you have to sacrifice a block in the HX FX to fit in the FX Loop block you need to enable the HX One. So, yeah… no advantage.
  2. I would open a support ticket. Perhaps Line 6 can intervene on your behalf to expedite things.
  3. I understand that Variax users are a small minority among guitar players, it for those who, like me, do use a Variax this issue disappears. You store the desired Variax model in the Helix preset. I’m often not sure what guitar model I’m playing but I know I have previously tailored the preset for that model.
  4. I am on EST also. How about 11 am or 4pm today? I haven’t used Zoom in a long time. I am reluctant to provide any personal info here in public. Please advise how you suggest we make the Zoom connection. For instance, if you want to provide your email address here I will email you and we can go from there.
  5. Hi Rob. I'd be happy to spend some time with you on Zoom. Let me know how and when you'd like to proceed.
  6. You’ve received a reply to the identical question you asked in the Helix subforum.
  7. I would open a support ticket. See …. In the above, the driver version you mention lists Guitarport as a compatible product on Windows 11. POD Farm 2 (not the original version) is also listed as compatible. I believe your GuitarPort product came with a license for the original POD Farm product. You may need to purchase a license for PF2. However, you should open a support ticket before doing so.
  8. Forgive my ignorance but why does this matter? Can you not have both your camera and your Stomp connected via USB?
  9. This looks like an example of a recent trend I'm seeing to get past the spam nanny here - namely the requirement for new users to have their first post approved. A sophisticated approach for a new spammer is to copy an already approved post by someone else so it will also be approved as their first post, then begin spamming under an approved userid. I am following this user.
  10. Check out the POD HD section here:
  11. Just to tie up a loose end here…. I opened a support ticket and received the following reply: The Don't Force option is by design, but there's a bug with it that is being worked on. I have talked with my colleagues in development and they were aware of this issue. I can't give an ETA as to when it'll be fixed, but rest assured that they are aware and that it'll get fixed.
  12. There is no perceivable difference in my experience. You can test it by simultaneously recording a dry and wet signal. Export the Helix preset using Helix Edit, and then import it into Helix Native. Apply the Helix Native preset to the dry signal and compare the audio of the two recorded tracks.
  13. No Rack model has been announced. Never say never but I doubt it. Yes, some sort of Helix Stadium Edit will be available.
  14. There is also the option to Clear All Blocks as described on pg19 of the manual.
  15. Not sure this will help, but make sure you are logged into your Line 6 account within Monkey. See the Login button?
  16. Either 3 and 4 or 5 and 6 will do for your purposes. Here’s the relevant doc: The Helix drivers are installed along with HX Edit. The HX Edit download is an installation package, not just the Edit program. Install all components.
  17. Yes, correct. Yes, instructions are complete and detailed, including restoring your device from the mandatory backup created during the update procedure. Updating the factory presets is optional. I always do it. I find the easiest method is to restore them using knobs 3 and 4 immediately after the update, and before restoring your backup file. Then when restoring the backup file choose not to install/overwrite the just-installed new factory Setlists (1, 2, and 8). You do this clicking on the arrow beside the word Presets and then deselecting/unchecking 1, 2, and 8.
  18. No you don’t need to update, however you may find some useful features depending on your current firmware. Check the release notes for firmware releases since the version you currently have installed and decide whether you want to. I don’t know why you wouldn’t though. The update procedure is pretty robust and well documented. There’s lots of help here if something unexpected happens. The likelihood that you will end up being unsuccessful is small.
  19. The fact that the Expand D10 exists strongly suggests that the answer to this is almost certainly yes. That connection would do nothing. I’m sure you already know that but simply want to voice your displeasure, and that’s fine. I too use a Variax JTV59 as my main guitar and wish Yamaha hadn’t halted its development when they acquired Line 6.
  20. For vocals and guitar simultaneously, for one reason. There are many others.
  21. Here's a test I just did and the result: Systems: Win 11; Helix Rack v3.80; HX Edit v3.82; JTV59 v2.10 (later versions don't apply to JTV59) Settings: Helix Variax Per Preset; JTV59 model Chime 2 (12-string), Standard tuning. Preset #1: anything in standard tuning that's not an Acoustic 1 model Preset#2: Helix model Acoustic 1, Custom Tuning Drop D Preset #3: Helix Model Don't Force; Tuning Don't Force Steps: 1) Select Preset #1 2) Select Preset 2. Confirm that model and tuning are as prescribed by preset 3) Select Preset 3 Expected behaviour: Don't Force settings should allow physical JTV guitar settings to be applied; Model Chime 2 (12 string) in Standard tuning Actual behaviour: Acoustic 1 model in Drop D is retained. My understanding of the term ‘Don’t Force’ is that Helix makes no changes to its current Variax settings. Specifically it does not seem to query the Variax guitar and apply its physical settings. Conclusion: The observed behaviour may be a bug. It may also be design intent. I noticed this years ago but didn’t report it because I assumed it was design intent and there is no documentation refuting that. The manual states: When set to “Don’t Force,” Helix respects the Variax current setting. This is ambiguous to me. Does it mean it respects the currentI Variax setting within Helix, or the physical setting on the guitar? It actually does the former, not the latter, so I presumed it was intentional. @psarkissian Is it worth reporting this since Helix Stadium has been announced? Won't likely be addressed in Helix even if it is a bug.
  22. That's what I initially thought and it makes sense. However, during my testing I recall that the actual behaviour is that the Variax retains its current settings even when Don't Force is specified. It does not seem to revert to the actual physical guitar settings. Perhaps my memory is faulty or it was a bug that has since been fixed. I will do more testing and report back when I have time. Sorry if this causes confusion.
  23. This subject has been confusing for me. Keep in mind that I’m describing my understanding based on my experience in trying to figure it all out in the past. I’m not aware of any official detailed documentation about this.
  24. The Don’t Force setting applied to a Helix preset means that the Helix will make no changes to the existing tuning when the preset is loaded. So yes, it will prevent different tunings from being applied. However it says and does nothing about the existing tuning.
×
×
  • Create New...