codamedia

This is a really old thread.... but I'll help out with your question. Go to this URL: https://line6.com/software/index.html In the search, choose "POD HD500" for the product, "FLASH MEMORY" for the software and "ALL OS" for the operating system. Repeat for "POD HD500x" if you want... That will give you a comprehensive changelog...

Your procedure looks right... not sure why it isn't sticking. Have you tried changing the volume on the HD itself and saving it? Does it stick when you do it that way?

If that is what you took away from my post, then you are completely missing my point. The verbiage LINE 6 uses to edit a Firehawk from the device is "LIVE EDIT MODE"... it doesn't mean editing in front of an audience.

My comment is based on access & editing on the device itself ... sorry I didn't make that clear :) IMO, the HD500(x) is much easier and faster to use if you forced to edit from the device alone which is inevitable at some point. This is important to me, it may not be important to others. For the record, I rarely (almost never) use the computer to edit the HD... I only use it for patch management, backup & restore. Nothing that I couldn't live without if the software support stopped tomorrow. (EDIT: I took the word LIVE out of the first sentence (live access and editing)... wrong word choice)

This is something to really consider. The Firehawk is very dependent on an "APP" and "Bluetooth" to get the most out of it. It is only a matter of time when an APP is no longer updated/supported to work on the latest devices and although Bluetooth has survived the test of time, "what comes next" is always a question in the tech world. There will come a day with the unit will need to be able to work "on it's own"... something the HD is much better equipped for. Just my 2 cents on the subject...

As much as I love the full range aspect of the HD series for flexibility... I full agree on this. The brittle/harsh high end can be difficult to dial out of the amps... which really is the primary use of the unit. The "extended low end" is easily handled in the cabinet parameters with the low cut (HPF). But the high end is not... simply because they didn't include an LPF in the cab parameters. I have found that I need to insert the Vintage Pre or Mid Focus after the amp and dial back the highs to attain the desired results.

I am always skeptical of "free" myself... the general rule is "when you don't pay for the product, you are the product"... They do seem to have an aggressive "donation" campaign on their website. I would like to think that the people that use this software regularly won't take advantage of it and will make a reasonable contribution. I'm not likely to switch from StudioOne... but if I did I would certainly donate the equivalent funds to help keep the project moving.

Just a word of note... this may not work for everyone. Java isn't usually installed on a machine by default... it likely came with a different software installation along the way.

That's a nice little resource... thanks!

When you get a JAVA error... just go to java.com and install the latest version. If JAVA complains that it isn't compatible with your browser just ignore it - that won't matter.

The internal pedal becomes fixed to "exp1" and the external pedal becomes fixed to "exp2" - it doesn't add a third expression. You still only get two pedals, but they can both be active at the same time. There is no limit to what you assign the EXP1, EXP2 and TOE to... but in a traditional VOLUME/WAH setup it could work like this. The external pedal (exp2) can be assigned to the volume block The TOE switch can activate the WAH The internal pedal (exp1) can be assigned to control the WAH

Good catch... thanks for the reminder!

Glad it's working for you... I really don't want to setup an account on the forum you linked to.... any chance you can share that excel spreadsheet here?

The settings will mirror what is stored in the guitar at that moment. If somebody changed the patch, you will only see their changes. Any changes you make in Workbench are auditioned in real time, but need to be sent to the Variax to be retained. Take a search on these forums for a "Factory Default" patch. I know I found one for my 300 when I got it used... I just loaded the patch in Workbench and uploaded it all to the guitar. It's a nice clean slate. If the 500 uses the same patches, I could share my "default" patch... but I would hate to give you something that is incompatible. Maybe someone else will know for certain if I can share my 300 patches with a 500. Workbench warns you... many times. When the guitar is updating (eg: when you are sending patches, or updating the firmware) DO NOT change anything on the guitar! When I am updating I don't move! My biggest concern is that the VDI loses it's connection during mid update... that has the potential of being disastrous. That said - I have NEVER had a problem with any updates... and I've been using/tweaking the 300 regularly (several times per year) since I got it in 2012.

For the 80hz cut I would try an HPF set to 100hz cut by about 3 db. That may seem high, but an HPF is gradual and by starting at 100 it will emcompass the "Q" that is fixed on the graphic EQ. I like the suggestion above as well.... fix that low end in the cabinet parameters. I would still recommend a 3db cut starting at 100hz. With the other frequencies.... as I allude to in my first sentence there is a fixed Q on the graphic and it is pretty wide. The default Q on the global is likely too narrow, you will need to widen it a little (not drastically) to get the same results. Sorry I can't give you any exact numbers.

There are two things that come to mind for me.... If I were using your chain, why bother separating the paths? Just insert SEND 2 right before the IR (don't use a loop, use a send as it doesn't need to be returned). Use the "send" to your amp, and use the output to your DAW/PA. To preserve the Loop for other use... place the IR last and drop it to path B. It should become the only item in path B at the very end. Next, head over to the output Y and hard pan the paths LEFT and RIGHT. Send Path A to your amp and path B to your DAW /PA. You will have to compromise on your output setting. You can set it to LINE and turn down the output going to the amp... or you can set it to Instrument and turn up the signal going to the DAW/PA (both volumes are in the Output Y with the pans). Using the latter would be my preference... as a DAW/PA will have more options to deal with input gain than an amp does (IMO), but this is something to experiment with to get the best results. Good luck....

I am pretty sure it's scheduled to be out during the 2nd quarter 2018... that means any time between March 21st and June 21st. The HELIX is the flagship... I suspect it will always take precedence. However, once EDIT is setup to fully communicate with the HX I think it will be much easier for them to keep all updates together. This is pure speculation on my part :)

Thanks.... the chain looks like it is setup correctly... but I think I see the problem. The entire point of using 4cm is to include your amp in the sound. You didn't do that when setting up your sounds. When you have the HX Effects "effect loop" turned off, all you are getting is the HX Effects direct to your amps "return"....only the master volume and power amp are being used from your amp not the pre-amp. When you have the HX Effects "effect loop" turned on , that will include your amp. This is what you really want. If you setup all of your overdrives with the loop off then you didn't include your amp in the tone! You have to get a good tone from your amp, then build your sounds around that... not the other way around. IMO: 1:) Turn on the loop and leave it on. 2:) Turn off all effects (other than the loop) and dial in a great amp tone. 3:) Setup your effects to that tone! It will sound great!

Can you chart your signal path so we can all understand your setup? I am asking this because in a 4cm setup you need to have a loop on the HX and one on the amp... I'm not sure how you are comparing the sounds to know why you think the loop is at fault.

This is the route I took ... and it's created a very versatile platform that has really extended the life of my HD500. Some ask why I didn't just buy a Helix, simple answer - I don't always want, and often cannot carry a full size board... the HX Effects was a perfect combination of features and size. Yes... all of them are relevant. The only difference between them is the "x" has more dsp power and nicer footswitches. The programming and tones are the same.

That shouldn't happen. I suggest you clean the jacks on both the XPS and the Variax. Do not spray cleaner directly in... spray the jack then plug it in/out several time and repeat. Find quality cleaner (deoxit or similar) and NEVER use WD40. Although I have an XPS mini... I most often power mine through a VDI cable connected to my HD500. The VDI is extremely useful for much more than power, but you do need a VDI compatable (XT, X3, HD) device for it to work.

As far as I know every sound in those 3 pedals you mention are already built into the HD500 so it would be completely redundant. If you want to extend the HD500, I would suggest some analog overdrive pedals either before the unit, or in the loop. Take the time to really learn it... it's a great unit. I recommend starting with an empty preset and build a sound one pedal at a time, and watch the output volume. Every effect you add should be kept at, or near unity gain or the output level will get out of control.

I have found that a used XT LIVE or X3 LIVE is easier to find and about the same cost as the interface when you do find them. I would suggest going that route. Keep in mind the "Beans" do not have a VDI port and will not work... you need the LIVE version, or the X3 Pro. FYI: The older version of Workbench still installs and works fine on a Windows 10 machine... the website just doesn't show it as supported. I have it running on both a Windows 10 laptop and desktop. If you encounter any JAVA errors, you need to install the latest version of JAVA (java.com) to your computer because the installer can't do it automatically anymore. This problem will exist with any Windows operating system.

TRS does not transmit or receive any midi... that jack on the footswitch is likely dedicated for use with the Bugera Tri-Rec amps. This footswitch works as a midi controller only when you use the midi ports... and by the looks of it, it doesn't even have a MIDI OUT (it has a through) so I think it only received messages to control the Bugera Tri-Rec. IMO: I don't think it can send anything to the Helix. If you find a footswitch with MIDI IN & MIDI OUT/THROUGH you should be able to make it work... Helix Out > iPad In iPad Out > Controller In Controller Out/Through > Helix In Then you need to setup appropriate midi channels to make sure the right device talks to the right sections on the Helix.

There are a couple of "spring" reverbs under legacy... they should be the easiest to get setup. As stated already, set the pre-delay higher for more note definition. I find the 35ms is usually enough... but you may want more. Setting it in a parallel path helps, and adjusting the lo & hi cut can also help to keep it out of the way of the guitar.