loonsailor

Sure, I can't stop them from doing that. But if I test early and notify them of any issues I find, I increase the odds of the release being clean. Isn't that the whole point of a beta release? As to where Line6 is, I have no idea, but I choose to assume the best until proven otherwise.

It's more iterative and cooperative than that. They (Apple) send me (developer) a beta. I can choose to ignore it, but at some point in the beta cycle I decide to try my application on it. I do this for two reasons. (1) It helps me to know if I'm going to need to do work on my app to remain compatible when the OS is released, and to do some of that work before the OS reaches release stage so my users will be happy with me. And (2) it helps them because I'm stressing the beta in ways that they might not be able to do without me. By the way, (2) is good for me, too, because I don't want them to release an OS that might have a bug they haven't found, but that is a show stopper for me. That cycle iterates a few times through the beta cycle. After that iteration, when the OS is released I still need to test on that final release, but hopefully most or all of my development work is done, and I just need to drop it into my own release cycle and get it to my happy users. Hopefully, that's where Line6 is now, and I'm perfectly fine with them doing a thorough job of the final test before offering it to the user base.

Have you done a full hard reset, by holding down switches 9&10 during boot up, as per the bold face instructions at the top of this page?

So, I decided to try again. In order to be 100% "clean", I rebooted. logged in as a different user, re-downloaded the installer, and ran it. This time, it works fine, and HN 1.9 is now installed. I guess something in my account insisted on opening the old installer, somehow. Anyway, problem solved, and I guess the problem was on my side, and not with Line6 or the installer.

I keep looking for operator error, but I think I'm doing everything right. I deleted the Helix Native plugin (I use the vst3 version) and the installer that I had downloaded, then re-downloaded the new installer and ran it. That got me to here. You can see that the installer file is called HelixNative1.90.dmg, When I open that file and run the installer package (right-clicked, to get past mac security) it takes me to a flag page that says it's gonna install 1.82. Figuring that maybe it was just an oversight in editing the flag page, I hit continue anyway, and was successful. Looking in Library/audio/plug-ins/vst3/line6, I see that it has installed Helix Native.vst3, which I had deleted prior to the install just in case it had a problem overwriting the old one. When I inspect that file, I see the following, which shows that the file was created 7 months ago, and is version 1.82. Fwiw, the other plugin in Components has the same September date. So, if I'm doing something wrong, what is it?

I've downloaded Helix Native 1.9, which gets me file HelixNative1.90.dmg. When I open it (need to do that by right-clicking and choosing open, doesn't work with a double-click), then double click on Helix Native.pkg, it takes me to a dialog where it tells me it will install Helix® Native 1.82. Thinking it may just be an error in the dialog, I agree, but it seems to reinstall 1.82, or maybe to do nothing. The files in Library/Audio/Plug-Ins/{vst, vst3, components}/line6/Helix... are created Sept 19, 2019. Looks like the package was put together with the old version, instead of the new.

There are a bunch of non-DAW vst hosts for this very purpose. I've got no real experience with them, but google "vst host" and you'll find a bunch, including free ones, for mac, windows and linux. If you don't want to google, check out https://hiphopmakers.com/best-free-vst-host-applications, or https://www.kvraudio.com/plugins/windows/macosx/linux/vst-plugins/vst3-plugins/audio-units/aax-plugins/rack-extensions/hosts/free/most-popular.

You can open it by right-clicking and selecting open, instead of double click. BUT, it seems to be screwed up at the moment. Although the filename is HelixNative1.90.dmg, it tries to install 1.82 instead. Looks like the dmg was prepared with the old software.

Thanks, Phil. I succeeded doing it the second way - importing from my .hlx file backups that I had created from the HxFx with Hx Edit. But, I don't see what you mean by "Hx Edit in Helix Native". How do I open Hx Edit in HX Native?

I've got a bunch of presets on my HX Effect unit (not full Helix), and would like to copy some of them to Helix Native, for use in Cubase. Can I do that? How?

I don't use an FRFR, 'cause I have an HX Effects that goes to an amp, so I have no direct experience. But, I have listened to a couple of FRFR shootouts on YouTube, and have been surprised at how different the various cabinets sound. To my ear (via unknown mic'ing, digitization, ...) the Powercab sounds better than most. Check out https://www.youtube.com/watch?v=WteWgQ1lV8A and https://www.youtube.com/watch?v=WjMsdts5F70 If you do want to use an amp, rather than an FRFR, you might check out the BluesCube line. I really like mine. It's solid state, so light and easy to carry, but it's voiced like a tube amp, not "modeled". The cool thing for practice is that the output power is switchable, 0.5W, 15W, 45W or max. In my basement, it sounds great on 0.5 W, and even some band practices I leave it there. It's loud enough that it almost never goes above 15W.

I'm using several different pedals successfully with the HX Effects (not sure about the Helix, HX stomp, ...), and I think I've cracked the code. Some of the pedals I'm using need a TRS cable. e.g. Both my Valeton EP2 and my Donner Viper work as an volume pedal if you plug a TS cord into them, and as an expression pedal with a TRS (stereo) cord. The HXFX needs them to work as an expression pedal. The complication is that the Expression Pedal inputs** for the HXFX need a TS cord. The problem can be solved in one of two ways. You can use a stereo TRS cord from pedal to HXFX and cut the R (middle) wire on one end. Or, you can use one of these adapters https://www.amazon.com/gp/product/B000068O5D/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1, plug a TRS cord from pedal to the Hosa adapter, and the red Tip output from the adapter into the HXFX pedal input. The other (ring) output from the adapter just hangs free, or you can cut it off. I also use a line6 expression pedal with an ordinary TS patch cord. Of course, it works perfectly. It's a very nice pedal. ** Actually, there is an odd thing about the pedal inputs on my HXFX. Pedal input #1 works as I described above. But, my pedal input #2 doesn't seem to care whether it has a TS or TRS cord plugged into it. So my volume/expression pedals work fine with a TRS cord from them to Pedal #2, but don't work in Pedal #1 without the fix I just described. If you have a pedal that isn't working, try using a TRS cord into the pedal #2 input. You might get lucky.

I've already set it to off/brt, and still can't see it. It's just not bright enough to be seen in any sunlight.

I've just played a couple of outside gigs and it's really tough to use my hx-effects in the sun. It's hard to read the labels, but I can live with that. The really bad part is that I can't tell if the led rings around the buttons are on or off, so I don't know which effects blocks are on. The ceba sunshade that the OP mentioned (https://www.gearbyceba.com/music-products/helix-sun-shield-splash-guard) looks slick, but looks like way overkill, too big for my hx-effects, and costs $125. Has anybody come up with any other solutions for this?

I use the built-in wah with an expression pedal, and I haven't noticed anything like that. Might you have the pedal inadvertantly mapped to "level" on the wah, as well as "position", or even on some other effect? You could tell whether you've done it on another effect by turning the wah off with your switch and see if the pedal affects volume. If not, check all the other parameters on the wah.

Thanks, Phil. Kind of a bummer. For live use, I might very well wanna tweak depth, mix, frequency, but I'm unlikely to care about stuff like pre-delay, which is what some blocks give me.

Is it possible to reorder the front panel knobs on the HXE so that the 3 most useful parameters show when a block is selected? I’ve tried both in HXEdit and on the unit itself, but I don’t see how.

I had the same problem. After a couple of go-rounds with Line6 tech support, the conclusion was that I had corrupt presets (specifically, all of the existing factory presets) and needed a reset. I fixed it by resetting only the presets, and didn't lose any of my own presets or anything else. Save the presets that you've made by exporting them individually using the HxEdit. (optionally) copy them to a high bank in the HX effects. I think, though I'm not certain (somebody please confirm) that resetting the presets doesn't mess with effects in higher banks than are occupied by the factory resets. I don't remember for sure, but I think that after the reset banks 1-10 (11? 12?) were occupied with factory presets. So, if you put your own presets in banks >= 15, they should survive the preset. Either this or step 1 should be sufficient, you shouldn't need both, but why take a chance? Do a Preset Only reset, by holding down FS5+FS6 while powering on the unit. (Documented in https://line6.com/support/page/kb/effects-controllers/helix/helixltfx-reset-procedures-and-troubleshooting-tricks-r768/). This will not affect your global settings, nor IRs. I'm think, though I'm not certain, that it won't affect upper preset banks. That's it. If your presets are still there in the upper banks, you're done. If not, you've exported them so you can simply reimport them. After I did this I had more and better factory presets, and the backup function in HxEdit works fine.

Thanks for clarifying. I had misunderstood. The amps and effects listed for the ampliFi (http://line6.com/support/page/kb/_/amplifiers/ampl/amplififulllistofampsandeffects) are indeed somewhat different than those on the HD500, though there's a lot of overlap, at least by name. I guess at this point I just need to go mess with it a bit, and see if it's a better box for me. Thanks.

I don't understand this. There's no real meaning for "high definition" audio. It's just a marketing term. I can't find any specs anywhere that provide sampling rate or bit depth (the measures that might matter for audio quality) for either of these devices. When I look at the M13 models for mods, reverbs, etc. they seem to be identical to the HD ones. So, what is the difference? Is it documented anywhere? (BTW, there's no info on the line6 web site about what models are actually in the fx100. I'm taking your word for it that it's the M13 set.) If they really are different, why would Line6 come out with their cool new device, using an old set of models? I have an HD500. I love the sound, but I definitely don't love how big and heavy it is, and I don't love that it's really tough to make a tweak on-stage ("lets try a different distortion box on this solo, please") unless I've pre-programmed that parameter to a knob or button. The fx100 should be a big improvement in both of those areas. As for the other stuff - variax, usb audio interface, ... - I don't care much, at least in a live situation. I haven't tried the fx100 yet, but I will!