silverhead

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'.)

I'm surprised that you find an improvement in the amp models. The only real difference in the HD500x is the increased DSP.

The key factor here is the size of the participating audience. Android is a very general app platform, with the potential for many millions of users worldwide and virtually unlimited scope for applications. I don't think anyone buys Android for a single app. Are there really that many guitar players who find the existing capabilities of JTV and Workbench sufficiently limiting that they would invest time and effort in this? Obviously you would. I wonder how many others like you there are?

@sudiptasingh: ... and what's in it for Line 6? .... Remember, they're in business to make a profit. How does this generate revenue for them?

Run Line 6 Monkey with your JTV connected to your computer, either with a VDI connection through a compatible Pod device or using the Workbench hardware interface that came with your JTV. In Monkey, select the device firmware. You should see a button labeled 'Roll Back' or something like that. This will present you with a menu of previous firmware versions to select. Choose 1.83 and proceed.

Check the Outputs pages. Make sure Tone 2 is not muted.

Here's your vote back. :)

Have you tried uninstalling and reinstalling Reaper? Even though Reaper will most likely detect and protect project files during the uninstall/reinstall, I would make a backup copy in advance anyway.

Woah... hang on a second, panaman. This thread is about converting HD500 files to HD500x files - nothing else. In particular, it does not say anything about the general usefulness of the conversion utility. I did not say the conversion utility is a waste of time. In fact it is a very useful tool. I have used it many times in the past, and continue to use it when I need to convert preset files among the Pod HD, 500, and Pro. I have complimented the author of the tool, and have directed many people to the tool for their own use. I have bookmarked the utility web page and I update it every time I need to use it. What I said was 'I wouldn't waste time with the conversion utility for this purpose'. (emphasis added here). There is simply no need to use the utility to load HD500 presets into HD500x Edit. A drag/drop will do, and in your own words '... it is easier to drag+drop a single tone to xEdit of course....'. That's all I am saying. I expect the author updated the tool simply to include the HD500x as a visible target device for conversions from other devices such as the POD HD and the POD HD Pro. That's a useful update. But still, I think there is no need or reason to 'convert' a POD HD500 file to a POD HD500x file, other than the name change. With respect to this specific conversion, that's all the utility needs to do. Of course, if that is incorrect I hope the author will clarify here for us. I think you need to take your blinders off and re-read the posts in this thread, recognizing that it applies only to the conversion of HD500 to HD500x. There is nothing that you should find annoying or belittling.

Sure. Set up a dual tone patch. Use Tone 1 for guitar and Tone 2 for Mic. Each Tone is processed independently - add whatever amp/FX you wish in each Tone. In the Outputs page you can pan them as desired.

That's odd. The description of the Variax power supply in the store says it is compatible with the JTV guitars as well. It doesn't matter for John's purposes, but if there's an error in the published info we should look into it.