Thark

I use my Variax JTV59 to test IRs. I have a preset that links the tone control to the IR number and I can whiz through all of the loaded IRs in no time. Of course, you would need a Variax instrument to do this ...

I reamp using Helix Native ... less hardware involved and no conversions back and forth from digital to analog. Guitars go into the mixing board via a Radial powered DI and are digitized in the board and sent to Cubase. Then I use Native to select an amp, which I can change any time. Very simple.

Driver?? I’ve never had to install a driver on my Mac. My understanding is that, unlike Windows, the Mac is “core compliant” which means ... no driver needed.

I used a Pod 2 for many years, right up until I got my Helix a couple of years ago. Didn’t pay any attention to new products from Line 6 until then. The Pod was perfectly satisfactory for me for all that time. As an aside, because of my long-time Pod use, I am completely ignorant of the developments in modellers between the Pod and the Helix. Doesn’t bother me though. :)

I know that when I first installed Mojave I had much the same experience ... no input from any source into Cubase. It turned out that the first time I ran Cubase it asked me whether or not I wanted to use the “microphone”. I said no ... no use for the built-in Mac mic. Wrong answer! Microphone in Applespeak means audio input. The fix was to tick the box beside Cubase in the security section of the system preferences. Go to System Preferences/Security & Privicy/Privacy/Microphone and make sure that Logic is checked. BTW, I’m not going for Catalina until all of my critical apps have been released in 64-bit versions. Edit: There's an app called Go64 that will check your system and list all 32-bit (and 64-bit) apps. Useful for knowing what needs updating.

Try looking at Midi Guitar 2. Excellent polyphonic tracking.

Funny. I use a Mac as well and have had zero problems with either my Helix floor or LT. My impression here is that most problems seem to occur on PCs. BTW, the next OSX version will be 64-bit ONLY. Any 32-bit apps will no longer function.

Does this mean that a JTV and flash v2.00 *will* update via the Helix?

I use a piece of cloth cut to size as a dust cover for my LT in the studio. Works fine. Not so good.probably for gigs.

That seems a bit excessive. They’re $59 CAD where I am, which translates to about $44 USD. I have one in my studio for my EastWest instruments.

No problems here as well so it can’t be a bug. Just really picky about sample rate etc.

I’ve used my Helix’s on-the-fly editing while playing with my band without any problems. It’s great for tweaking a sound during a tune and also having a funky back myself I really appreciate it. You can change a parameter rapidly with the expression pedal (which, as you say, is a bit tricky to use for precise settings) or incrementally via the footswitches (which allows very precise setting). Wouldn’t using a tablet mean not playing while tweaking? Surely you could only use it between tunes. Perhaps this is what the OP meant?

Either I'm missing something here or everyone else is. You want to tweak settings as you're playing, right? Why go to the trouble of using a midi device? Why not just use the Helix's on-th-fly edit facility? On my LT I just push the MODE button and hold to edit the preset. It will enter the edit mode and then you edit each of the blocks in your preset by simply tapping on a footswitch and perhaps using the expression pedal to adjust a setting. Easy-peasy and great when playing live.

The Powercab 212 is way too heavy for me to lift on a regular basis. I use two Powercab 112s linked together via L6 Link. Sounds really good to my ears. I don’t know the Firehawk but if, as gunpointmetal says, it is purely FRFFR then you won’t have all of the sound options that come with the Powercab such as FRFR, LFRAW etc. ... not to mention the built-in speaker emulations and ir capabilities that can reduce the processing load in your Helix.

I’ve updated to 2.81 for my Helixes and 2.00.1 for my Powercabs. Sounds fine ... better than fine actually. This is an odd problem that I’ve not heard of before. You could try going back to 2.71 (which I assume you came from) and see if that fixes it.