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. Yes - I noticed that in your first post. Which told me that you knew very well that you would not get Line 6 support here. Hence there were, I thought, two potential reasons for your post: 1) you actually were seeking community support, or 2) you just wanted to vent. Your first response clarified that it was actually #2. I just hoped you felt better. Apparently not. You can continue venting in good company here: http://line6.com/support/topic/5449-say-something-line-6/ There's usually at least one of these threads at any given time. No need to start your own.
  2. OK - well, this is a community forum so .... no, you won't get official Line 6 support here. But hopefully you feel better now having vented a bit.
  3. Not until you describe the problem you are having..........
  4. Yes - two sets ot patches with/without cab sims is useful.
  5. I found the jumbo frets on the JTV-59 too high for my taste. It appeared the action was very high, but in fact the distance from string to fret was not unusual. It was the added height of the frets that made the strings so high off the fretboard. I couldn't get used to the very light touch required to avoid pressing so hard on the strings that the notes would actually be sharp by the time the string hit the fretboard. My solution was to replace the jumbo frets with normal frets. Lower action (to the fretboard) and no sharp notes.
  6. Yes, firmware updates often affect the tones/sounds. It's usually minor but some tweaking is often required to adjust the sound. There's a notice about this possibility during the firmware installation process. You have the option to cancel the update if you don't want any changes, and you can always roll back to previous firmware afterwards.
  7. The "F-xxxx" models select the factory installed presets in the Variax. The non-F models select the User models in the Variax - the models available using the pickup selector switch. These User models, all 12 banks of them from Custom 1 through the 10 labeled banks and including Custom 2, can all be used to replace the F models with user-created models using Workbench. The R-Billy model bank is one of the 10 labeled banks. Hence selecting F-R-Billy1 will select the original factory installed R-Billy model in position 1. Selecting R-Billy1 (without the F) will select the currently installed User model in the R-Billy bank, position 1. I know the F-model selections are available in the pre-JTV Variax guitars. I have heard conflicting reports about whether they are selectable in the JTV models. Apparently, some see the F-models listed when the JTV is selected as the Variax guitar, and some don't. Personally, I have seen them listed in HD500 Edit when using my JTV-59, but I haven't replaced the factory models with User models so I can't tell whether a selection difference is actually happening.
  8. Nope. If you never use the mixer on the 't' models there's no advantage over the 'm' models.
  9. I should have asked earlier - do you have the Pod xt or the Pod xt Live? Only the xt Live has the VDI (Variax Digital Input) connection. You can't digitally connect the Variax to the bean-shaped Pod xt, so if that's what you have you will have to use the Workbench hardware interface to reset the Variax.
  10. What happens when you click on My Software in the License Manager?
  11. Resetting the Variax requires reinstalling the firmware. In order to do that, Monkey needs to recognize the Variax connection to your computer. There are two ways to connect your Variax to your computer so that Monkey can see it: - use the Workbench hardware interface. Monkey sees the Variax directly - use your Pod xt. Monkey sees the Variax connected through the xt. So the answer is yes and no. Yes, as long as your pod xt is also connected to your computer. No if it is not.
  12. silverhead

    Tuner

    The tuner only works with Input 1. Make sure the instrument you're tuning is selected for Input 1.
  13. At the time I said that, it was true. I almost never change patches while playing; I always change between songs. However, having read more about the popping happening changing patches while playing I tested this on my equipment. I clearly hear it anytime I change patches while the guitar is sounding. I don't hear it if the guitar is silent. I can certainly see why it is annoying to those whose patch setup requires mid-song patch switching. Definitely deserves to be fixed.
  14. Hmmm..... the latency may be due to a delay setting of some sort in the home theater setup. I know in my home theater A/V system I can set an audio delay to synchronize the audio with the video coming from my TV, so that the lip movements of the speaker match the voice. Check your audio settings to see if you have a delay.
  15. Charlie_Watt's advice is good, especially if you plan to use the HD device frequently in different venues for gigs. The footswitches will get a lot of wear and tear, and the better ones are a good investment. The other side of the coin is that if you are primarily a hobbyist (like me), using the device less frequently and moving it less often, the original footswitches are probably plenty sturdy enough. I know they've never been a problem for me. And for the same hobyyist reason I don't need the 20% more DSP. If that description fits you then you could save a few bucks by going with the 500 rather than the 500x without compromising anything.
  16. I see this sentiment expressed frequently, and I understand it. No matter how often we refute it, it remains. I can see how my own behaviour plays into it because I rarely speak negatively here. That's for two reasons: 1) I own quite a bit of Line 6 gear and in my personal experience it works very well for me. In the few cases where I have had problems, Line 6 support has resolved them quickly. I simply haven't had the sort of negative experiences regarding product quality and support that are often reported here. That doesn't mean I don't believe the reports I see, or try to minimize their importance. This is a support forum, exactly the place where such issues should be addressed. I try to help resolve some of the issues. It does no good for me to 'pile on' with the negativity. It's counter-productive in terms of resolving the issue, so I try to avoid it. That can leave people with the impression that I am biased and that somehow my 'Expert' status obligates me to defend Line 6 in all situations, and never say anything negative. Totally wrong. 2) I think there's a lot of merit in what most of our grandmothers told us: If you don't have anything good to say, then don't say anything. I fail at that often but it's something I try to do here. This, too, can lead to the above impression of biased behaviour. I understand that, but I see no point in pointless negativity. I am going to break my habit in this post sepcifically to provide a counter-example to stratman82's comments. I think Line 6's pre-release marketing campaign for the Amplifi product was way over-hyped. I can't and won't try to defend it. As for the product itself, it's simply not one that interests me. I'm sure it has its target demographic; I'm not it. I choose not to buy it, and I also choose to be disinterested in complaining about it or wishing it were something else. I don't want to spend my time even thinking about it any further. I don't expect every product from any company to meet my specific needs or desires. A product is released, I don't like/want it, I move on. As far as my 'Expert' status goes - I am completely free to rant and/or rave here to my heart's content. I could go on and on about how I think the Amplifi marketing sucked, how it's not a product that does anything for me or my Dream rig, how I was expecting much more ..... blah, blah, blah. It doesn't matter. It's a product I don't like. Period. I choose to spend no more time on it. I don't think it's productive for me to do so - there are lots of things I'd rather spend time on. That's my choice - not an obligation imposed by Line 6. I intend to keep a link to this post in my personal files. Every time I hear this sentiment about Line 6 Experts' supposed bias I will refer to it. I am completely free to say what I want when I want here. What I actually do say/do is my own choice. Every Line 6 Expert here has exactly the same freedom of expression. We occasionally disagree publicly with each other, although we do it respectfully. All of us decide for ourselves whether and how we pass judgement on Line 6 products, either positively or negatively. The fact that you may see more positive than negative comments is, at least in my case, both based on my personal experience and a personal preference in terms of expressing my opinions (or not). So I have no more to say about AMPLIFi. Now on to more productive things.......
  17. Sorry - the JTV needs power to be recognized by Monkey or Workbench. There are two ways to get it powered: 1) A VDI connection to a compatible Pod device, or 2) A charged battery with a 1/4" plug connected which acts as a power switch The 1/4" plug doesn't need to be connected to anything. Perhaps there's a pair of headphones with 1/4" connector lying around somewhere at work? Or maybe there's an electronics store near where you work? Perhaps a coffee break purchase of a plug - not even a full guitar cord - would let you check the installed firmware.
  18. Sure - that's done sometimes here. As long as it's Line 6 stuff. Don't want a Craigslist. :D
  19. Yes - that's true. How can there not be a cost/performance decision in processing power? Of course Line 6 could have increased their price point and provided more DSP capacity. That's clearly where other manufacturers are (think Axe/Fractal, Kemper, ...). Line 6 targets a lower price point, provides less DSP capacity, and permits the user to control DSP allocation within the price-driven limitations. The move to the 500x was not driven by a desire to increase DSP, and is not to be interpreted as any kind of indication that the original DSP is insufficient. The X series was driven by unavailability of the original processing hardware. The need to change to new hardware brought with it a minor increase in DSP. A small bonus, but not the reason for the change.
  20. I like to think of the DSP 'Nanny' this way: Every device has its DSP limitation - no exceptions. Almost all devices are engineered to prevent the user from ever reaching that limit. The consequence is that, in all cases and for every preset, there is available DSP in the device that is wasted. Think of the Pod HD300/400. The FX1, FX2, and FX3 architecture guarantees two things. First, you will never exceed the DSP limits of the device and, second, every preset you create leaves some (and sometimes a lot of) DSP available, unused. The dual-path POD HD devices, however, allow the user to decide how to allocate the available DSP, right up to the maximum. An attempt to exceed the limitation causes the DSP Nanny to appear, saying 'Sorry - you can't do that'. I much prefer being able to make those decisions myself, leaving only a minimal amount of unused DSP capacity.
  21. BTW, this conversion utility was generously provided by one of our community members. Solely his work and his donation to all of us. Thanks again, jzab.
  22. 1. I haven't noticed this issue with v2.0. I can't say how prevalent it is, but certainly there are some reports. It would be good to get to the bottom of it. AFAIK it is not an acknowledged problem within Line 6. Does it happen with all patches? if not, Is there a 'recipe' to consistently reproduce it? If so, is there some global setting that can be identified that will make it disappear? Does it only happen with the JTV in combination with a POD HD, or does it also happen with a JTV standalone? Does reinstalling the firmware help?
  23. The .hre file should be in the same folder as the conversion utility .exe file.
  24. I don't experience any popping when changing patches in v2.0. #2 is a behaviour change. There have been reports that the behaviour seems to fluctuate - sometimes switches banks and sometimes doesn't - however I don't believe there has been really systematic and definitive testing and reporting on this. Perhaps one of those who have experienced fluctuating behaviour can clarify?
×
×
  • Create New...