purusha

I meant top, as in highest frequency. The string next to the B. :)

I don't think it's necessarily the Piezo dying. The guitar tech/Luthier who set my guitar up, had to set the top E (as in next to the B) with minimal bridge height, since the neck has a natural curve/radius. We strongly suspect that raising / lowering the heights of the saddles affects the Piezo pick-up. I've seen others comment and mention the same thing. Hence the need to adjust relative gains of the individual strings.

Thanks all! Good info! For my purposes, I have one particularly quiet string (top E) I've like to adjust, so global levels are fine. I think there may generally be some confusion over the terms - like I thought "global" on some of the other threads, meant across all 6 strings. So - now I have the problem of finding a USB interface... :) It's a real shame that Helix and HD500X don't support the old Workbench.

Thanks for the response, but I just found this which says that string levels can be controlled individually: Link below says: "There are also controls for adjusting the individual string levels." https://www.soundonsound.com/reviews/line-6-variax-workbench That has a screen-shot, which shows "mix" per string at the bottom left. Does that sound right?

Hi all, My POD XT Live died some time ago, so I've been without the old Java based Workbench. Can anyone tell me if the old pre-HD system allowed individual string gains to be set? If so, I might invest in a Variax interface. Actually, that raises another question. My HD500X and Helix don't support the original Variax system, so which Variax interface I could buy now, will work? Thanks for any help with the above!

Anyone else getting this? Is it expected? At 48KHz, on any of my DAWs, Helix Native sounds fine. ...but at 44.1KHz, I'm getting some really nasty tones / frequencies super-imposed. Thanks!

Thanks. My Internet connection is fine. Helix Native seems to be OK through multiple reboots on my MacBook (limited to 10.13), so it could be a Mojave related issue. In which case, Line6 will have to sort that out before I buy. Studio full of hardware and software here, all of which I tested on a Mojave partition before making the jump. There is an error on this Mac Pro system though, in syslog: Oct 28 10:48:16 MacPro Live[536]: objc[536]: Class L6HttpRequestHandler is implemented in both /Library/Audio/Plug-Ins/Components/Helix Native.component/Contents/MacOS/Helix Native (0x1377a9a60) and /Library/Audio/Plug-Ins/Components/Helix Native.component/Contents/Resources/HelixCocoaView.bundle/Contents/MacOS/HelixCocoaView (0x144abe140). One of the two will be used. Which one is undefined. Might check that on the MacBook and send over to Line6 for further thoughts. I'm afraid I'm wary of Line6 software, due to lack of support for 64 bit VST on Pod Farm, which means I can no longer use it on Cubase 9.5. Edit: spoke too soon. My MacBook is now doing the same thing as the Mac Pro. It's not a Mojave thing.

Any thoughts? The demo worked, just after install, on my system, but now both the AU and VST versions (Ableton and Cubase) won't start. All I get, is a permanent spinner and a locked-up app. This is MacOS 10.14, Cubase 9.5, Ableton 10.0.0.4. I think the Helix plug-in is 1.7, as of a couple of days ago.

I'm struggling with this too. I'd very much like to see a general update to Pod Farm, with proper 64 bit VST support on OSX, plus new models etc.

This really is a big shame. ...but, if I have to use Cubase's 32 bit wrapper, does anyone know of a way to disable the firewall messages which pop up every time a Pod Farm plug-in instance loads?