duncann

The pod's midi output capability does everything you want, except cover the full fixed range of your Rivera. As long as the pod is in pedalboard mode, every time you select a new patch (two presses - bank up/down, then a, b, c, or d), the pod automatically sends out a PC message. The message value is determined by the patch position within the setlist (0-64) The midi channel number can be restricted by the system menu setting. At least ... after thinking about it a bit ... that should do most of what you want. Does the way you use your Rivera require any values above 64? If so, that's the only thing I can see that doesn't work fully how you want. But you could at least control some functions on the Rivera.

Here's the best explanation I've seen for this: http://blog.line6.com/2013/pod-hd-amplifier-extras%E2%80%94using-the-sag-bias-and-bias-excursion-settings/

I agree the manual is not clear on this. There is a system menu option on page 6 (of 12 with 2.62 firmware) that has a midi channel setting. It goes from 1 to 16, and omni. I would assume this is the setting you're looking for when automatic messages are sent.

I'll help you along with firmware problems and attempt to jinx you: If you haven't done the firmware update yet, when you do update it, just watch for the inevitable power failure during the update. Because if a power failure will happen, that's the time for it.

Gotta love the obsessive nature of guitar players, me included. :lol:

I had high hopes for the global EQ, but it looks like I won't be using it at all, especially now that I see it doesn't work over usb. Oh well, no biggie. I don't think turning the EQ on or off makes any difference. The DSP it uses is likely reserved for the EQ. It defaults to on I think.

For the interface you're using, you'll want to go to Roland's website and download the specific drivers for the ua-55 and your operating system. It should include asio drivers that you can select in your daw. I'm pretty sure asio4all is made for soundcards without any official asio capabilities. Probably want to stay away from it if your interface has native drivers.

I didn't install 2.62 yet, but I ran hd edit version 2.26 and it still has the non-valued dep parameters, which the download page claims is fixed.

I wonder if they are going to fix the dep parameters bug now. After all, they seem to think it's fixed. :lol:

I see the new versions of HD Edit, 2.26 for both hd500 and hd500x, still have the bug of no values shown for the DEP parameters when adjusting them. Somewhat disappointing. This bug showed up in version 2.25. I opened a support ticket a few days ago, but no response yet.

I think the closest you'd come to that would be the studio EQ. Try that one, or a multiple of them. To my ears, this one has the least, or zero, amount of effect for just existing in the signal chain.

If you're talking about the exp pedal on the pod, try tightening the allen bolt very slightly before calibration. This will help keep it in place for a longer period of time before it loosens again and starts to fall under its own weight.

You can also extract the Monkey program from the installer and just run it, bypassing the install process (for windows operating system). 7-zip works. The files needed would be: Line 6 Monkey.exe (run this) cpuz.sys (32-bit) cpuz64.sys (64-bit) cpuz.vxd (virtual) The same can be done with hd edit and the license manager.

Might be worth a try. But definitely test it out first before going live with it. One thing, besides the cord being tripped on and ruining the usb port on the pod, would be synchronization errors. When HD Edit is running and being used at the same time of controlling the device with its buttons and pedal, this can cause the pod to crash.

For some reason, the image that conjures doesn't look or sound quite right ... lol. Is that true, or was he joking when he said that? I wonder if lard would work.

Total FX blocks are limited to eight, but you can use those eight blocks any way you want.

What about the lonely, never mentioned, all by itself 88.2KHz? Does anyone even ever consider this one?

I've found for me that any of the wahs sound best when both the mix and position are tied to the expression pedal. The position min and max values may vary depending on the wah: Position: 0 ~ 35 to 75 ~ 100 Mix: 24 to 100 With this setup you don't need to worry about engaging the wah either. If the pedal is in the heel position it's essentially off.

Same here. I used this all the time. I guess the jokes on us. Line 6 says lets use percent on the EQs, even on the software interface. Now they are having fun by saying, "Lets remove all the values, starting with the DEP parameters. What's next? I know, lets make the knobs smaller! Then let's remove the name label HA!" But at least it's confined to HD Edit.

Similar thing happens to me, where a patch will seemingly lose some distortion at times. Although this only started happening since the 2.60 update and the unit doesn't have to be on for a while. Sometimes I turn the pod on and the patch seems suppressed somehow. Other times it seems like how I wanted it to originally be. Could be lots of things, anything from the strings, air pressure, temperature, mood, ears, disease, famine, etc., so I'm not going to automatically assume it's the pod.

The no percentage thing, yes, I get this too. And I have to say, this really needs to be fixed. It used to be that a percentage toottip popped up when adjusting it. Now it doesn't. :angry: The no sound on patches might be something with the input setups global setting? Or a volume pedal somewhere in the chain where if the pedal is in the heel position there will be no sound? I use a lot of dual amp patches and haven't noticed anything like this yet.

Indeed. The cabs and mics are the things that most influence the fundamental tone of any patch. It would be interesting also if the programmers could work their optimizing wizardry on the cabs/mics to add some parameters that are common in IR plugins, like maybe mic distance, better/more mic positioning, and simple EQ controls. Any new parameters like that could be in lieu of the current res/thump/decay controls. In other words, make a multiple choice dep parameter scheme.

I use 48KHz. Tried 96KHz for a while but like you couldn't hear a difference between 96 and 48. Smaller number of samples also means smaller project folders if that's an issue.

I think what rhandy meant to say was holding the down arrow while powering on will bring up the 'Flash Update' message. Then try and flash it again using Monkey.

http://line6.com/support/topic/335-frequency-response-graphs-for-hd500-eqs/?hl=graphs