silverhead

DarrelM5 and duncann, that's been my experience too. That's why I believe loss of sync problems have more to do with the user's computer environment than buggy Edit software. Certainly makes it difficult for Line 6 to reproduce and resolve any software issues that might exist.

Exactly. I made a point of saying that during this test you should avoid touching the device itself. That's because there is known to be a general problem with keeping the Edit program and the device in sync when both are being used to operate the device simultaneously. This manifests itself in many and random situations, not only in the SEND/SAVE presets case that is the subject of this thread. And I suspect that a lot of this has to do with the user's PC environment so different users experience this a great deal and others not at all. What I was trying to do was investigate whether there is a particular bug in the Edit software that might have existed independent of the general loss of synchronicity bug. It's no surprise, nor a new bug, to find another situation like this one where problems are manifest when using both the Edit program and the device together. By removing this factor from the test we seem to have eliminated the existence of a new, specific bug. That was the goal. Again,as a general rule, avoid touching the device when using the Edit program. If you want/need to use both together then you need to develop a workaround, as you have done, to minimize any impact of the loss of synchronicity that you may experience.

Tboneus - I haven't tried the comparisons you asked me to make, and I don't think the results would be objective. I have a JTV-59 and a 1970's vintage Les Paul Deluxe. At various times in the past few years I have routinely played the JTV using mag pickups as well as the Lester model and the Les Paul, all using the same patches on a Pod HD500 and HD Pro. While they are all slightly different in tone they are also all remarkably similar. I never noticed anything with the Lester models that was microphonic or hollow as you describe it. I do recall that at one time (before the JTV was released) I used Workbench with a Variax 300 to try to reproduce the sound of my LP Deluxe because that's not one of the Variax models. I used the mini-humbucker pickups available in Workbench, which is what my LP has. With some tweaking I was able to produce a model that sounded so close that I was unable to distinguish the Variax from the LP. I could fool myself into thinking each one was the other. That's what I'm afraid I would do here if I actually did the comparison you ask for. The fact that I haven't noticed what you describe in the last several years suggests to me that I would be fooling myself if I now reported that I heard something new and different. Or maybe my old ears just aren't that good anymore.......

I don't have a DT amp so can't comment on that. I go Studio out direct to PA/monitors. I tend to go for classic rock tones, and I generally match my models to the equipment most often used by the classic artists. For instance, I will generally match a Fender guitar (T-model and Spank banks) with a Fender amp model (Blackface, Deluxe, Tweed). I'll use a Gibson guitar (Lester, Special, Semi banks) with a Marshall-like amp model (there are many), and I'll go for the early-British invasion of the 60's with the R-Billy or Chime models and the VOX amps (early Beatles sound). Can't wait to try the Jazzbox JTV models with the pending JC120 HD amp model.

That makes it really difficult to characterize this as a software bug. It does not seem to be a straightforward situation of the code failing to properly SEND and store a modified preset in all cases. duncann's experience provides the counter-example. Other complicating factors may be: - complexity and/or nature of the modifications (e.g. there's only a problem with certain amps? FX? Parameters?). Awfully hard to diagnose. - stability of usb connection during the SEND operation (intermittent device conflicts? maxed-out CPU doing other things like virus checking?) - intermittent hardware failure (RAM issues?) If we're lucky, Line 6 had prior knowledge of this from an earlier bug report and may have been able to track it down and fix it. If so, that fix might appear in the next release of the Edit program(s) that are likely to accompany the firmware v2.6 release. Failing that I think the best anyone experiencing this issue can do is identify a specific workaround that works for you, and use that procedure consistently. (e.g. Brazzy's approach which, as I understand it, is not bothering with the SEND operation at all and using the SAVE command on the device exclusively).

So, based on the same steps, Brazzy experiences a problem in the second test and duncann does not. Is that correct?

You're right - there's no L6 Link on Firehawk and hence no control over DT-25 amp. The connection between the Firehawk and the DT-25 would be exactly like the analog connection between any guitar processor and any amp.

Your UX2 becomes your PC's soundcard. You need to connect your monitors/speakers to the UX2 outputs.

Try using this preset structure rather than New Tone: http://line6.com/customtone/tone/217206/

Does it actually matter? Any 'deception' in your ears is likely based on an expectation that what you observe should occur at 50% rather than 60%. But so what? As long as you hear only the dry signal when mix is 0%, and only the wet signal when mix is 100%, and as long as there is a gradual blending of the two as you adjust the mix level, does it really matter if what you hear as 'equal' occurs at something other than 50%? Most importantly, are you able to get the mix you want?

I'm aware of the other currently active thread on this topic and I'm curious about the behaviour but am not near my POD to test today. I know the expected and intended behaviour is that the SEND from the Edit program should be sufficient; you should not also have to SAVE on the POD directly. Can a few of you please try the following and report back? - SEND the modified preset from the Edit program to the POD - before doing anything else, shut down the Edit program and disconnect the usb cable - now recall the Sent preset using the POD footswitches. What happens? - repeat the above, but this time after disconnecting, switch to a different preset on the POD before recalling the Sent preset. What happens? During all of this, make sure you do not touch ANYTHING on the POD while the Edit program is running. My hope here is twofold: - obtain a reliable recipe for a workaround to unexpected behaviour - collect information to reliably reproduce a potential bug, and then report it to Line 6.

That makes sense if you have not sent the changes made in Edit to the POD device, using the Edit program's SEND command. If you recall an edited preset using the device before sending the changes made in Edit, the device will recall its previously stored preset (not the edited one) because it has no knowledge yet of the edits. They are only stored in the Edit program's working memory until sent to the device for permanent storage. There are other anomalies that will occur when you use the device to make changes while the Edit program is running. A general rule of thumb is: whenEdit is running, don't touch the device.

@raston: I would return it and get a replacement.

Have you tried using different usb ports on the computer(s)? You need to use usb2.0 and avoid using any hubs.

Make sure you are also using a guitar cord in the 1/4" jack of the JTV. That acts as the power switch.

Is there something more behind your question? I ask because the situation is quite standard and simple. As the previous posters have said, there will likely be an update to Hd Edit. But that's quite normal and it's a simple matter of downloading and installing the update, a one-time thing that should be no problem. Are you anticipating a problem if there is an update? What prompts you to ask the question?

I wouldn't expect the app to be available until the product ships, but I'm just guessing.

Yes, the Firehawk can do that. Here's a link to info I provided earlier: http://line6.com/support/topic/12081-best-for-jtv-variax-hd500x-or-the-new-firehawk/

No - there is no change to the DSP capacity of the device.

I would guess that the difference is based on local supply/demand factors rather than technical or manufacturing considerations.

In fairness you also need to consider what Firehawk offers that the Pod HD does not. - Most, if not all, of the Pod Farm series amps - Bluetooth connectivity to mobile devices running an editor app - Tone search/match capability of AMPLIFi - your own personal and unlimited cloud-based tone library Not arguing for or against either product; just completing the comparison.

It is still supported. There's a difference between a product being discontinued and unsupported. Discontinued means it is no longer being produced, and no further updates are expected. The product is still supported, meaning existing problems will continue to be addressed. The HD300/400 are discontinued but currently supported.

Never. There will not be an update for the Hd300/400.

There are a couple of differences: - the HD500X allows you to fully control the Variax using the device itself as well as with the editor. The Firehawk device supports much less onboard editing; it relies on the iOS app for detailed editing, including the Variax controls. So the controls are available, but only if the app is running alongside the Firehawk. - Firehawk and its app do not support Vol and Tone knob locking, or their assignment as parameter controllers. But you can use the Firehawk to save/store Variax model selection, Tone knob position, and alternate tunings on a per preset basis.

Still seems you were faster than me!