joel_brown

What do you plan to connect the PODHD to ? Otherwise your question is like asking "Can anyone suggest what guitar I should play live onstage ?".

You replied to a 2 year old thread.

Not that this fixes the problem but you should be able to disconnect and reconnect your mouse and keyboard and have them work again. At least you wouldn't have to restart the computer.

Yet another amp that chugs. We have enough options to choose from inside the Helix and PODHD to make that tone already.

Send it back before it gets worse.

Sounds to me like you got ripped off with a defective unit that someone was trying to unload.

macOS 10.13 and 10.14 has implemented an additional security layer for kernel extension drivers, such as the Line 6 audio drivers. After the Line 6 device is connected, the customer must open the Security Control Pane and accept the Line 6 driver in order for the device to be recognized. Typically, but not always you'll see this message when your driver gets blocked, or is not available for use with your DAW: However, sometimes the driver gets blocked and the message won't appear. Your driver and hardware simply won't work. In either case, you'd need to approve the driver in System Preferences > Security & Privacy: Additional information about this change can be found at https://developer.apple.com/library/content/technotes/tn2459/_index.html#//apple_ref/doc/uid/DTS40017658 For some cases if the "Allow" button does not change anything, or the "Allow" button does NOT disappear after clicking. Please try these steps: Go into: System Preferences > Keyboard > Shortcuts > Select 'All Controls'. Then: Go back to System Preferences > Privacy & Security > Press 'Tab' until 'Allow' is selected > Press 'Spacebar'. Note: the Privacy & Security page may need to be unlocked before 'Tab' will work.

Seems like every couple months it's the same post about MacOS. This has been answered so many times I almost remember the the answer off the top of my head and I've never owned anything Mac. A couple of searches for past posts about this and you'll find the answer.

Maybe it's the amp or a cable and not the PODHD. I would keep a set of headphones around and plug them into the PODHD next time it goes out to make sure it's the PODHD and not something else. I know you're in the middle of a gig but you have to diagnosis exactly where the problem is before trying to fix it.

It's the same. The rack unit has a few more routing options and jacks but sound wise they're identical.

The OP wrote this in April. Doubtful if you'll hear from him. But a lot of other people will help you. I use a 50watt Marshall into a 2x12 cab with my PODHD. I just use the Marshall as a power amp and plug the PODHD using the Studio Direct setting into the FX return of it. Then I use the PODHD for all my FX and PreAmp modeling. One cable into the PODHD, one cable from the PODHD to the amp, and one cable from the PODHD to my floorboard. Seems like most people use a P.A. speaker or some form of FRFR powered speaker for the PODHD. Then the tones you create are more likely to sound good going direct into a board. I personally like the added coloring a tube amp and guitar speaker give me, but that's just personal preference.

This thread is from 2014. Please look at the dates of the last post before replying.

Turn the Sag down.

Big deal, a few bucks extra for a cable... I'd be thrilled if that was the only thing I could find to complain about.

Do you have the ASIO4ALL.sys driver installed on your PC ? If you do then get rid of it. That's typically the problem.