aleclee

I have both.  It's kind of an apples to pineapples comparison IMO.

• VG99 does guitar modeling.  HX does not.
• VG99 does polyphonic synth sounds.  HX does not.

If you're looking at amp/cab/FX modeling, I'd say that HX wins across the board.  For my purposes, HX is the bomb.  I don't do much with the VG99, particularly since my GP10 does the bulk of what I want out of the VG.

Have you tried V-Guitar Forum?  Lots of FC-300 expertise there and a fair number of Helix owners as well.

Aren't you describing snapshots?

i think the difference is that his suggestion involves substituting blocks, it just turning them on and off.

 

It's not so much snapshots as gapless preset switching with spillover. Unfortunately, those were the issues that snapshots were created to address.

Stopped using tube amps when I turned to the digital side back in 2009.  Sold off my last tube amp well before acquiring my Helix.

I think the approach here is to work with him.

Depends on the details of the situation. The bass player is a knucklehead and a lousy communicator. If the band is a major source of my livelihood, I'd suck it up and try to make lemons into lemonade. If I'm a weekend warrior who's mainly interested in blowing off steam, there's no way I'd deal with that bassist any longer than I had to. Life's too short.

It would be full range but likely nowhere near flat response

You might try this.  I think the bar sockets are pretty standard.

http://www.fu-tone.com/catalog/index.php?main_page=product_info&cPath=73&products_id=278

First of all, your bass player sent you an email. That right there is telling you there's trouble. My bass player can't touch his phone without breaking it let alone look at a computer long enough to figure out what it is and why it isn't exploding.

 

Does your bass player have a second band because this sounds exactly like my bass player?   :D

 

This is considered a power user hack, tho'.

 

How about implementing that hack in firmware?  https://line6.ideascale.com/a/idea-v2/903037

 

It might make it more accessible and less error prone.

MIDI "loopback" for those applications that currently call for hooking a MIDI cable between Helix' MIDI out and in.

 

https://line6.ideascale.com/a/idea-v2/903037

I'm new to the forum and did not know about the idea website to state an idea.  Instead of directing me there, I've gotten many responses that I feel aren't justified or conducive to anything but letting me know my idea is off based and not warranted. 

 

 

I'm continually surprised at people joining a forum who start spouting without getting a read on the vibe of the joint.  When I join a new online community, I'll read a buttload of threads before making my first post. Keeps me from asking stupid questions or pissing in anyone's Cheerios.

I have owned a Helix. Got the floor unit. Liked it. Want the rack but the controller is same layout. Everyone gets so butt store over nothing. Seriously.

 

 

 

Yup. And you're definitely part of "everyone".

Post your suggestions there and vote up those that are similar.

 

 

Or threaten to hold your breath until you get your way.

For practice and recording, I use the Equator Q8's in my recording setup (see below).  

 

For jamming, I'll run direct if the PA is up to it.  If I'm bringing my backline, my Atomic CLR is my first choice.  If I want to run stereo or smaller mono, I have a couple of QSC K8's.

 

You lost me at "neuter". If you'd rather have those buttons for IAs & presets, that's fine but "neuter" and starting a "can't purchase" thread is a bit over the top IMO.

Spring came and went can we please get an updated ETA which is more informative than "it's in beta" ? When will the rest of us be allowed to try/purchase this? Thanks.

I don't think they can. Once it's in Beta, you work off bugs until the known showstopper bugs are all fixed. While there are some statistical models to help estimate how long it'll take to identify & remediate those showstoppers, it's still a matter of actually finding and fixing them and it takes as long as it takes. The only alternative is lowering the quality benchmark to hit a date and that can't happen with a new product like Native where you need to make a great first impression.

 

There's a maxim in the tech industry: customers will remember a release sucks a lot longer than they will remember it's late. Kemper was late by nearly a year but they got it right. That touchscreen modeling doodad from InMusic wasn't ready for prime time and it seems to be struggling. I don't expect Native to be nearly as tardy as KPA but I do expect it to be very good.

Funny.  I had the exact opposite experience going from AxeFx to HX.  AxeFx levels were weak with HX levels right where I want them.  I suspect it all boils down to the levels in the presets.

Color me impressed!

What MIDI channels are the HX & GR using?

I have crackling on USB audio in or out. I've re-downloaded the driver/editor (windows 10), reset to factory specs; still same. Not sure what else to do but I'm hoping it's not a hardware issue. Now I can change the sample rate; do I have to match these manually for it to work?

Crackling is often a buffer overflow issue.  What are your system specs and input buffer settings?

There is a split and a merge block but I am not sure exactly what this has to do with high and low cuts.

I thought there was a split that acted as a crossover

 

Edit: Just confirmed on page 31 of the HX manual.

Does anyone know which block Ben Adrian was referring to in his quote referencing "Crossover filters" as 4 pole and 24db? Where is there a "Crossover filter" on the Helix? I feel like I missed some piece of information earlier in this topic or perhaps in TGP where this quote was extracted.

Isn't there a crossover block for splitting signal between paths? That's what I assumed he was talking about.

Back in my AxeFx days, I used a tone match block to get a single coil sound from a humbucker. For those not familiar, it uses match eq to create an appropriate IR. While the tone was in the ballpark, it wasn't as convincing to me as an acoustic IR but where I really found it lacking was in feel. YMMV, of course.

Analog piano on average takes 8ms for the sound to reach your ear after hitting the key. Not all that perceivable.

This is a phenomenon that's often cited in latency discussions but some details are missing.

 

While it's absolutely true that audio time of flight can cause delays greater than the 7-10ms that can cause perceivable latency, there's a reason why one is not irritating while the other one is. In the case of audio time of flight through the air, your brain gets cues (e,g, reflections) that help it place the source and compensate for the delay. With "wire latency" there are no such cues. That's why you can use a wireless pack and roam far from your amp 30-50ft and have time of flight far beyond what would be tolerable latency in a recording environment.

I don't use the expression pedal much with my HX Floor but hope that DAW automation might be an effective substitute