silverhead

I've wondered that too, but haven't felt the need to swap the JTV piezos. I own a Variax 300 and changed to Graphtec pickups a couple of years ago. The sound improvement was incredible - much better than the original V300 piezos. When I purchased a JTV one of the first things I did was compare sounds with the upgraded V300. At that time the JTV modeling was the same as the V300, so any difference in sound would have been due to the different piezos. I could not tell any difference; to my ears the new JTV piezos sound as good as the Graphtec. Mind you, technology moves ahead - perhaps the latest version of the Graphtec would indeed be better, but I know for me it's not worth it. I am very happy with my JTV as it is, and I'm pretty sure the quality of the piezos is not the limiting factor in my sound or playing. :lol:

arislaf, I agree with you. I want to see another update too and there are several things I would like to see in it, including Workbench HD compatibility. All I'm saying is that nobody should feel entitled to it. Line 6 may provide one, and may not. Doesn't change the fact that we have (or should have) purchased a product based on what it could do at the time, not based on what it might be able to do at some unknown future date. And it does what we knew it could do. Anything else is a bonus, and lack of it is not reasonable cause for disappointment.

Yes, there is. Convert & Modify POD HD Presets | www.jzab.de Kudos to forum member jzab for doing this and sharing it.

Yes - you've identified my fatal flaw, rationality and logic. It plays havoc with my marriage sometimes. :D Q: Does this dress make me look fat? A: No, dear, it's not the dress.

What update? The most illuminating aspect of this thread is its title; in particular the word 'expectations'. No one should have any expectation of any future update. None has been announced and Line 6 is under no obligation to provide it. Having said that, Line 6 typically does provide periodic updates - often not announced in advance. They simply appear - usually for free - and they are a great bonus for users. An almost certain way to ensure that you are disappointed (and we've all seen this play out numerous times) is to: - start to expect an unannounced update, with the basis of that expectation being nothing but a hope - speculate on specific features that you hope (and soon expect) to be in the update. (A favorite one this time is Workbench HD capability via HD500 VDI. I'd love it, and I actually do expect this one soon. But I have no reason to. :o) - project a target date on which you hope (and soon expect, again with no basis) the update to appear - wait, and then wait some more, and then get upset that line 6 is 'late' with the as-yet-unannounced update - finally, eventually, receive a bonus update - and then get disappointed and even angry because it doesn't contain everything you felt had been promised (your unfounded expectations).

I'm pretty sure there are bug fixes that people are expecting and hoping for, and I agree that they should be fixed. But whether or not Line 6 is planning a release soon, or at all, is not something users typically know about in advance. I think we wait and hope, and in the meantime continue to enjoy a great piece of gear despite a few bugs.

Not to be picky, but it's not 'due', really. None has been announced, and Line 6 has no obligation to release any updates. Typically, however, Line 6 does periodically release free firmware updates to its products as a bonus for users. And usually the announcement comes when the release is available. So I expect that if one is in the works we'll only hear about it when it's ready.

That's very good news, for you and for others who might be experiencing symptoms of flaky firmware issues. Let's hope this ends up being a fix!

I agree - more than one phenomenon. In most cases I have seen (like the immediately previous post) these ghost notes end up being the natural acoustic vibration of the string. This is surprisingly easily picked up by the human ear, and the amplified sound has to be very (very!) loud to overwhelm it. However, the pitch of the natural vibration is not transmitted over the analog outputs of the JTV (or the VDI connection). So if this is how you recorded the sound through your Apogee into Garageband then you definitely have a real issue. If, however, you recorded a mic'd amp into Apogee it is still possible that your mic picked up the pitch of the natural string vibration.

I happen to prefer the new models/tones. That means that we have a difference of opinion, and it doesn't make either of us right or wrong. I respect your opinion; please don't belittle mine.

I believe ASIO4ALL would have been installed along with Audacity, but I have never used Audacity so can't confirm that, and I don't know where it would have been installed. My knowledge in this area is based purely on driver/DAW-related problems reported here, and their diagnosis/solution. What I can say is that if Audacity is using the HD400 driver then there should be no ASIO4ALL-related problems, since it is not in use. However, if Audacity is showing different input and output devices then it is in fact using ASIO4ALL (or some other non-ASIO compatible driver). If the HD400 driver is being used there is no possibility of assigning different input/output devices. Also, many users have reported that they are successfully using ASIO4ALL with their Line 6 device. Not everyone has problems with it, but those that do will not get support from Line 6, other than to say 'use the Line 6 driver, not ASIO4ALL'.

This is a property of the audio driver being used rather than the DAW. Audacity uses (by default) a driver called ASIO4ALL, and this driver does, as you say, allow you to specify different input and output devices. Unfortunately this is not compatible with true ASIO driver implementation; true ASIO does not permit this - it requires that the same device is both the input and output device. Hence, using ASIO4ALL with devices that faithfully implement the ASIO protocol (like all Line 6 ASIO devices) can lead to problems. Many DAW-related problems reported in these forums have been traced to the use of ASIO4ALL, and its use is not supported by Line 6. The only ASIO driver that should be used with Line 6 devices is the device driver provided by Line 6.

I regularly use inputs 13/14 and also 15/16 as stereo pairs for a couple of my POD HD devices. I can assign presets to these inputs; specifically, I assign the HD500 preset and connect the Pod HD's audio outputs, with the Pod set to Studio mode. Works fine. Edit: Looking into this a bit more, I see that you can only use presets that are identified as Line inputs with physical inputs 13-16. Not all presets are compatible; only those with the Line Input icon in the top right corner of the preset icon are compatible.

...or, even more simply, just drag/drop a HD500 preset file into any preset slot in HD500x Edit. It will open without difficulty and then you can SEND it to the device.

This bug should be reported to Line 6. To do so, use the product feedback link that you will find under the Contact Us button at the bottom of this page. Provide a 'recipe' for reproducing the problem - a specific series of button-pushing steps that Line 6 can use to recreate the problem for investigation.

I have never found the need to manually SAVE on the device after SENDing from the editor. I think something else must be going on here but I don't know what it is.

I also use two L3t speakers as mains. I keep them at 12:00 and adjust output levels upstream. Don't have any issues with volume. However, the human ear does detect tonal differences in the same sound at different volumes. That may simply be what you are experiencing. It's called the Fletcher-Munson effect, and it's why guitarists often use two sets of patches - one for practice/low volume and one for gigging. Old guys like me remember when a standard home stereo amplifier had a built-in 'Loudness' function, which boosted the low end at low volumes to adjust for loss of tonality.

Check your DAW setup, as well as the HD500 mixer panning. It's possible you are recording only half of the HD500 output signal.

Which signal from the HD500 are you recording: the L channel, R channel, or stereo?

....HANDS UP AGAINST THE WALL BUDDY!! DON"T TURN AROUND!!! :lol:

Usually when people report hearing this it ends up simply being the natural resonance of the standard-tuned string that they are hearing, which creates dissonance with the alternate tuning. The human ear can pick up the natural note/pitch at surprisingly low volumes relative to the amplified sound of the alternate tuning. Note that the natural string vibration is only a couple of feet from your ears, while you amp/speakers are relatively much further away. There are three ways to test for this: - turn your amp/speakers up VERY loud to completely mask the natural vibration. Usually not practical because the volume required bothers the neighbours. - use closed headphones to block out the natural vibration. Again, not conclusive but can be highly indicative. - make a recording of the sound direct to your DAW - not through a mic'd amp. The natural string vibration is not passed to the JTV outputs and hence cannot be recorded. The third method is the most reliable because it is conclusive. If you don't hear the dissonance in the playback of the recording, then what you are hearing, as surprising as it may be, is the natural acoustic pitch of the standard-tuned string(s).

The Workbench upgrade should not affect anything you can do with the JTV in your Vetta, or X3. The Vetta/X3 capabilities apply to the JTV itself, not Workbench. The JTV v2.0 firmware update affects the modeling that the JTV uses but, again, that should not affect anything to do with what is stored re: JTV presets in your Vetta/X3. Anything you could do before you should still be able to do. Remember, the Vetta just stores JTV settings - it has nothing to do with producing the JTV sounds. Note that the Vetta/X3 are limited in what they can do with JTV presets compared to a Pod HD (e.g. can't store JTV alternate tunings in a Vetta/X3 preset, but can in a Pod HD500 preset) but that has always been the case. The JTV/Workbench updates should be transparent to you as far as your Vetta goes. You will, of course, hear the new modeling in your JTV.

To get HD500 tones into your HD500x: - download an HD500 tone file to a folder on your computer - run HD500x Edit with your HD500x device connected via usb - drag/drop the HD500 tone file from your computer folder into any preset slot in the HD500x Edit window - audition your tone (listen to it) - if you like the tone, tweak it further if desired - when no further tweaking is required, SEND the preset to your HD500x device

Sounds like your amp settings may be overdriving the inputs to the post amp fx. Try cleaning up your amp tone as a test.

In general, you should not use the unit at all while using the editor. Using both to make changes while the editor is running leads to oddities such as you describe. When using the editor, use it. When you want to use the unit, close the editor (or suffer the unpredictable anomalies that arise from the devices trying to remain synchronized when both are 'driving'.)