amsdenj

All those failed updates are likely leaving Helix in a bad state. I don't know how the updates are done, but I would guess that there is no writing to Helix memory until the whole image has been downloaded from USB since that would be the most unreliable link in the update chain. You would think there would also be some checksum at least to verify that the image was downloaded without error. But if something was causing Helix to crash while updating its internal memory, say a faulty unit or turning the power off, then this might cause Helix to be unable to boot. I'd guess Line 6 has a way of restoring such units, but there may be nothing us users can do if a unit gets in this state. So far I've had no problems updating - done it 3 times now.

You could use a iPhone or iPad with the AudioTools app and a Send block in Helix to add metering and wave form analysis anywhere in the Helix signal chain. That wouldn't provide metering for compressors though that would show how many db of compression you're getting.

I bought this amp when I was a Freshman in college, 1968 I think. Earlier this yer I dug it out of the attic and tried to use my POD HD500X to create a digital pedal board into this amp. It sounded awful and I quickly gave up. There were a few problems in the amp - needed new power tubes, the filter capacitors in the power supply needed to be replaced, and the pots needed cleaning. But the worst problem was the Fender CTS 137 speakers in an old 2x12 Bassman cabinet. These speakers just don't sound good, too much bass, flabby sounding, no articulation and an odd color. I got them out of an old Fender Pro that I replace with Celestion Greenbacks. Well, I had the parts ordered to fix this amp a couple of years ago, thinking it would be a labor of love, and bring it back to life. I did the repairs, and replace the CTS 137 speakers with Celestion G12-65s. Now that old amp was sounding pretty good. So I created a traditional front-of-the-amp pedalboard in Helix including: Fassel Wah Deluxe Comp Compressor Low and High Cut EQ to use a high-pass filter to reduce bass into the gain/drive stages Vermin Dist - for Drive: just the edge of distortion as that Showman is super clean. Vermin Dist cleans up well with Drive about 1.9, Filter at 8.0 and Level at 8.3. Turn it on and the amp just starts to get gritty and cleans up nicely by rolling back the guitar volume control Valve Driver - for Overdrive: gives a bit more control on the bass and treble cut for a somewhat more overdrive sound Compulsive Drive - for Distortion: this is a very smooth, musical distortion. I'm really glad Line 6 included this model Script Mod Phase Ubiquitous Vibe Gray Flanger 60s Bias Trem Chorus - sounds great, even in mono Simple Delay - slap-back 125 milliseconds, no repeats Transistor Tape - for 500 millisecond delay '63 Spring 145 Rotary Looper This setup sounds fantastic and has breathed new live into a old amp that means a lot to me. Helix makes a great pedalboard.

Certainly different body images can make a huge difference. See if you can borrow a Fishman Aura, plug it into the Helix effects loop and experiment with different cabinet models. If you find one you really like, I'll capture it for you.

What computer are you using? Maybe that's your problem since is it is common between the two Helix units. Maybe try a different USB port or cable. Updating back to 1.04.2 shouldn't be any different than updating to 1.04.3, so it sounds like there's something unreliable between you computer and Helix.

I use Mac OS X AU Utility to set the Helix output levels of different patches. AU Utility just provides the missing output meters. It's also helpful in gain staging while designing a patch to make sure no block is in danger of clipping. For actual volum levels, I use a DB meter to at least understand what volume level is being output. I try to keep things around 85 DB from my own amp. That provides some consistency in the actual production environment.

Is that the same guitar, amp and speaker model in both versions?

Do you have an amp or speaker model in your signal chain? If so, try bypassing them. A guitar amp generally doesn't work well with acoustic instruments, the tone control voicings for electric guitar aren't really that suitable for acoustic guitar. Electric guitar speakers are even worse since they are very colored, and don't have much high frequency response. If not, then maybe its your guitar pickup. The Fishman Aura body images are created by (more or less) subtracting the impulse response of a under the saddle piece pickup from the body impulse response. Then when you play through the pickup and this modified body, you get the sound of the guitar through just the body. If your guitar doesn't use an under the saddle pickup, then maybe the extracted body image won't fit with your guitar. What are you connecting the Helix output to? It needs to be headphones or a FRFR amp. Finally, different guitars sound better or worse with different body images. The body image created specifically for a guitar might not be the one that sounds best. It takes some experimenting, just like with speaker IRs.

I couldn't find anything like Bodilizer for Mac. I suppose it would be posslble to capture IRs through Bodilizer, even running on Windows from a Mac, but doing it with the Fishman Aura was simpler and possibly has better body images. it might also be possible to extract an IR out of a Bodilizer file if we knew the file format. Perhaps the developers will where.

Creating an Acoustic Guitar Impulse Response for Line6 Helix

See blog post: Creating an Acoustic Guitar Impulse Response for Line6 Helix for how to extract a body image from a Fishman Aura Spectrum into an IR that can be used in Helix acoustic guitar patches. More to come.

Here's a few links: How to make an acoustic guitar impulse response Recording Impulse Responses Making Impulse Responses with Logic's IR Utility Bodilizer How to Make Your Guitar Sound Like a Banjo The IR project: acoustic guitar processing and cabinet simulation

That use to be a problem, but recent Helix and El Capitan updates seem to have solved it.

The Line6 Audio/MIDI drivers just released are not for Helix, but for HD500X and earlier products. Helix is USB Class Compliant and does not require any driver - which is why it sort of works with iOS. There must be some timing issues as setting the I/O buffers to a high number seems to clean up the digital noise, but at the expense of high latency. I use Firewire for my main computer interface and it works fine with El Capitan. But there does some to be some issues with USB audio.

I'd bet its the global settings being reset that's the problem. For example, changing the 1/4" or XLR outputs from Line to Instrument could make a big difference in overall tone.

There are threads on how to create acoustic guitar body impulse responses - Google and you'll find them, including a nice YouTube video. However, you'll need something to process the body and piezo pick response to do anything useful. Bodilizer on Windows might be useful, but it doesn't have any means of exporting an IR that can be loaded into Helix. What I did is get a Fishman Aura Spectrum, then use Logic Pro X's Impulse Response Utility to create impulse responses from the Fishman Aura body images that worked well with my acoustic guitar. I then loaded these IRs into Helix and created some nice acoustic guitar patches (mandolin too). Its a bit of a complicated process and not something that would fit into a forum post. I'll try to create a blog post that walks through the process in a few ways. Ultimately Line6 needs to get into the IR business and provide some acoustic guitar and other body IRs that would really expand the usefulness of Helix. Its great that we have this flexibility.

El Capitan 10.11.2 works fine for me with the Helix app. There's still some clicks and pops from the USB audio, but I don't use Helix for that anyway (Focusrite Saffire Pro 40). What issues are you having?

I'm thinking of developing a Helix Web app in JavaScript using the MEAN stack and deployed to the IBM Bluemix Cloud to upload, download, display, clone and edit Helix patches. I'd use AngularJS and Bootstrap so the app would run in a browser and support mobile devices too. Anyone want to work on this/contribute?

Many PA mixing boards also provide balanced TRS inputs, especially for stereo channels. I use a XLR to TRS cable with my Helix with my Persons 16.0.2 with these cables into one of the stereo channels.

I couldn't reproduce it consistently today. But right after the update it happened every time. Might be a problem with the foots witch, its like pressing the switch and having it send two events instead of one.

I found the HD500X to be a very good audio interface for guitar, even sounded better to me than an Apogee GiO and Apogee makes very good interfaces.

There's no phantom power on the XLR outs, only on the XLR mic input. I think the defect you are referring to is the loss of audio output from the XLR outputs which hopefull is address by the first bullet item above.

I have the same issue. I think the reason is so that pressing Record while recording immediately sets the loop and starts overdub. But that's not really practical because its hard to end one phrase and start another at the same time. Another issue is that the Looper Exit switch is too far away from the other looper switches making it hard to turn the looper mode off and on in order to get to the other block footswitches. One possible solution is to allow the blank footswitches to be mapped to blocks while in Looper mode so that a few key effects could be controlled while in Looper mode without having to switch back and forth.

Delays sound good to me, but I don't use a lot of delay. Re: studio, you might find much better luck with S-Gear from www.scuffhamamps.com than using a real mic'd amp. Helix in the studio might work better than a mic'd amp too unless you have a specific isolation booth for the amp. Digital isn't what it use to be. After all, most of the recording and mixing is digital now, as are most plugins. Why not the guitar amp too? Good convolution models for speaker cabinets make all the difference.

Since updating to 1.04.3, I've noticed exiting from the Looper sometimes (actually quite often) doesn't return to the footswitches but instead displays the two rows of bank patches. I've used the Looper a lot and never noticed this behavior before. This make it require multiple presses of the Exit switch to get back to the normal patch footswitch operation. It doesn't happen all the time, and seems to depend on what other footswitches might have been on when you entered the looper. I'm using 10 footswitch mode, and it seems if footswitch 1 is on, this seems to cause the Looper Exit to fail more often.