Community: Message List

Re: Why presets are saved in the wrong setlist or sometimes even saved when I didn't "send"?

support@line6.com — Sun, 17 Feb 2013 04:03:10 GMT

It's not something that happens all the time, so I can't specify an exact way to reproduce it. It seems to happen more often when I open POD HD500 Edit and I start working without changing setlist. At the time of saving a patch, it simply saves in another setlist, not the one that is selected at that moment. As I explained above, I change setlists everytime I open POD HD500 Edit in case the program doesn't receive accurate information. Last time I didn't work on nor create any patch; just went through some setlists, played, and that's it. I closed POD HD500 Edit, then unplugged the USB cable. As usual, the last patch selected had the * character showing, so I switched to the next patch and came back to the previous one, but this time was showing a patch which is originally in another setlist, but was saved in the setlist that doesn't belong to and not showing the *, that is a saved patch in that position, just as I explained above. That's as accurate as I can be as this doesn't happen all the time, but when it does, it ruins my setlists and I have to recover them from the saved setlists in my computer, afraid of this problem happening again when sending those patches.

By the way, the USB cable is plugged to the front of my CPU and as I recall, those ports go direct to the motherboard, so they don't go through any hub nor share the connection.

Why presets are saved in the wrong setlist or sometimes even saved when I didn't "send"?

support@line6.com — Sat, 16 Feb 2013 23:54:45 GMT

Ok, this problem is getting annoying. I've started a ticket about this but they don't seem to pay attention to this. When using POD HD500 Edit I had this problem sometimes. I opened POD HD 500 Edit, tweaked or created a preset, clicked the send button with the proper setlist selected, then I found that preset was saved in a different setlist, thus erasing the previous preset in that setlist. I guessed it's some kind of problem in the Firmware or POD HD 500 Edit which didn't inform the setlist properly, so I started changing setlists from POD HD 500 Edit so the program knows well which setlist is selected. So far, doing that seemed the solution for that problem.

Now, yesterday I plugged the POD HD 500 to the pc to go around presets, not to create a new one or make any changes. I know it's foolish since I can use the pedalboard for that, but I'm used to plugging it and using it via POD HD 500 Edit. After I finished using it, I closed POD HD 500 Edit and unplugged the POD from the USB cable. As usual, the preset selected keeps an * character. I don't like seeing that so I don't think afterwards I modified that preset. So I changed to another preset with the pedalboard and went back to the previous one. What I found is that I had a preset from another setlist recorded in that place...and I didn't even had modified ANYTHING with POD HD 500 Edit when it was plugged...Either the program or the Firmware did that by itself.

I wanted to ask how many of you have this problem and if there's any solution to that in the user's hands. This is turning annoying and so far I've been lucky to have those presets (and latest versions of them) saved in my computer. I work with music so the POD HD 500 is one of my working tools. It's getting annoying having to deal with these simple but serious problems. I really hope Line 6 fix this in their next update.

Re: "Tone suck" when pedals are off

support@line6.com — Thu, 03 Jan 2013 04:15:04 GMT

Just sent a message to Line 6 about this matter. I'll inform you if I get an answer.

Re: "Tone suck" when pedals are off

support@line6.com — Thu, 03 Jan 2013 01:17:15 GMT

I'll write them, posting this thread too for them to see I'm not the only one who realized about this heh.

Re: "Tone suck" when pedals are off

support@line6.com — Thu, 03 Jan 2013 01:16:24 GMT

That's why I emphasized I don't use the 'automatic' setting of impedance; I have it in 1 M as a global preset, that is active in every situation, whether there are 2 or 3 bypassed pedals or no pedals in the chain.

Re: "Tone suck" when pedals are off

support@line6.com — Wed, 02 Jan 2013 17:18:00 GMT

hurghanico escribió:

lachinelli ha scritto:

..You can do an A/B comparison, one with a bypassed Wah/Chorus pedals and another one without any pedals in the slots..
I did the A/B comparison you were talking about, and... yes, I confirm that there are some differences between the no-fx-version and the bypassed-fx-one..
the no-fx v. is somehow richer in harmonics, and sounds more natural..
the differences are subtle and not so big but are there, it isn't so easy to describe it, but in the byp.-fx v. it seems almost like the signal was down-sampled and with a limiter-like-fx applied to it

Exactly, this is what I meant, but maybe because I'm not a native english speaker, I couldn't explain myself well. The difference is subtle, meaning it doesn't destroy the signal, but to my standards it does make a difference enough for me to make different patches to avoid this problem when I'm going to record.

Re: "Tone suck" when pedals are off

support@line6.com — Wed, 02 Jan 2013 17:20:59 GMT

I'd like Line 6 to take this matter into account for next update and they add in System Options the choice whether we want "tone suck" or not when pedals are bypassed.

Re: "Tone suck" when pedals are off

support@line6.com — Wed, 02 Jan 2013 17:13:54 GMT

spaceatl escribió:

This is just my opinion...by all means use what works for you...

Using the Same setting on input 2 will certainly give more signal in the chain...convienient for driving an amp model a bit harder with a lower drive settings...however, the FX will react to this also...and not in a very nice way...It's neat for some amp models, not so neat for some of the FX...The tape echo is a good example of this as the modelled clipping is a lot more apparent and happens quickly...Anyway, I do use the same setting for a couple of tones that use the Park Pre as it doesn't saturate very much...and a few dual tone patches, but mostly I have input 2 shut down as internal gain in the signal chain is too high for my tastes when input 2 is set to same...

After I tested that method I came to the conclusion that people that don't need high gain and want a cleaner sound can use it. In my case, I use high gain and proper settings that don't make the signal to clip get me where I want. To avoid clipping I compare the raw sigal output with the processed signal and both should have the same levels. Of course, I neither abuse the output of any pedal/amp I use.

Re: "Tone suck" when pedals are off

support@line6.com — Wed, 02 Jan 2013 16:09:06 GMT

Yeah, I bypass wah and other pedals from POD HD500 Edit.

Re: "Tone suck" when pedals are off

support@line6.com — Wed, 02 Jan 2013 14:35:07 GMT

You have a good point there. My settings are Guitar in input 1 and Same in input 2. I tried the suggested setting in the forum using Variax in input 2, but the loss of gain was substantial. Still, what you said could be the reason that the sound is modified in the chain. I guess I'll just have to make different patches in which the wah or pedals are in the chain only when they need to be active.