Jump to content


Popular Content

Showing content with the highest reputation since 05/01/2017 in all areas

  1. 10 points
    Dear folks at Line 6, please update the Firehawk FX in 2019! suggestions: - improve switching, it’s lagging quite a bit sometimes... - add new effects and amps like you do with the Helix products; I’d like to see POG and HOG effects and some new boutique pedals and amps - improvements for the looper, increase of recording time would be nice to make it useful and also being able to eliminate a recording without starting playback for 2 seconds, this makes the looper useless in live situation. - overall bug fixes to add more stability to the system. I love this product and I know it can do so much more if Line 6 puts some effort in updates.... not everyone wants to buy a Helix..... i know im not alone here, just hope someone at Line 6 takes proper action! thank you for your time and I’ll be waiting for feedback!
  2. 9 points
    2.9 Model Updates: -Revv Purple (Ch3) -1x12 Fullerton and Grammatico Cabs -Red Llama Drive -Steve Vai Legendary Drive -Harmonic Antagonizer Fuzz -Rochester Comp (Billy Sheehan Compressor) -Small Stone Phaser -Split Dynamics (Path A/B Routing) Feature Updates: -Output Meters -Gain Reduction Meters -Clip Indicators -IR Attachment by Name -New Switch/Snap/Looper Layout Options -New Model Subcategory Shortcuts -Update from HX Edit -A/B Compare for HX Native Available “soon.”
  3. 8 points
    Hi Made an update of my Cheat Sheet, Line6 Helix Model Summary, if anyone are intereted. All up to date with 2.50 update and all amps, cabs, mics and effects are in order of appearance on the unite. Some corrections are also made, if someone down loaded the previus version. Unfortunately, there will be one more page as there are just too many amps and effects in the unit :-) Or, there is now room for more... I still want to keep the sheet readable, so have kept the font size the same. Download from my dropbox - https://www.dropbox.com/s/e2jsnnqwscr6iml/Line6 Helix-Model Summary%2C 2%2C50-P1.0-01.pdf?dl=0 Have fun //Per
  4. 7 points
    Can't say I do. Walking through the south Bronx after dark without an armed escort is a "messy and dangerous experience". Updating firmware, even if it results in a toy that's temporarily unusable, ranks somewhere between "the car I want isn't offered in 'burnt sienna' ", and "I'm sorry, but we're out of the cheesecake".
  5. 7 points
    Pete Thorn can play, and I'm sure he's an all around swell guy. However, I think... strike that...I know that reality is VERY unlikely to live up to your expectations. Trying to use patches created by somebody else, no matter who (or how wonderful) they are, is mostly an exercise in futility. You will always always end up having to tweak them to the rest of your rig, guitar(s), needs, playing style, etc. etc. Even if they were free (which they wouldn't be if L6 is cutting the guy a check), you're still chasing your tail. And yes, to confirm my suspicions I've tried (repeatedly) a bunch of downloaded patches...some free, some not... including some of the most talked about ones around here. The free ones were a waste of time, and the paid ones were a waste of money.... so I don't bother anymore. Mine work because I made them with my guitars, monitors, headphones, PA, etc... and all at the volumes at which I intend to use them. When all of those other factors are a complete mystery, and Helix the only common denominator, you're pi$$ing in the wind.
  6. 6 points
  7. 6 points
    A disaster? I think that’s quite a bit hyperbolic... There are some bugs, and 2.82 will be out shortly to clean up some of the remaining things. I mean, personally, I’ve done a bunch of gigs using the 2.80 and 2.8 firmware and really haven’t run into any showstopper bigs. I suppose with a complex system with so many different possible use scenarios, everyone is going to be different.
  8. 6 points
    Okay, cool. I've played as an armchair quarterback too. It's a wonderful thing to do because it makes you feel really proud of yourself and smart, but there's no system of accountability if you're completely full of lollipop so it's a relative safe zone. I did that with my wife's casserole dish the other day. I just forgot not to do it when she's there. I'm hoping the front door is finally unlocked tonight.
  9. 5 points
    It appears that there is an issue with the LA Comp. You likely won’t notice it if you use it before the amp block as it doesn’t do much to the over all volume in that position. However if you put it after the amp block it will affect the volume of the patch and as a result depending on how it’s feeling when you load the preset you may get full volume and you might get less than full volume (as I said it’s random). I started using the compressor at the end of the chain after watching and following along building a patch from a Jason Sadites youtube video. And it 2.71 it worked great. In 2.8 LA comp seems to have an issue loading. If I take it out of the signal path the preset will consistently load at the same volume if I put it back in and keep re-loading the patch after less than 10 re-loads (most often less than 5) the patch will load at a lower or higher volume. I also tested with leaving it in the signal path and just disabling it which has the same effect (as expected). When Line 6 answers my support ticket, I’ll just point them to this thread as I know there are others who have put in a support ticket for this issue.
  10. 5 points
    Here's one back at ya Phil, and Happy Labor Day Ya'll!
  11. 5 points
    I'd like this statement to be required reading for everybody who comes in here whining that Helix (or modeling in general) sucks after playing with it for all of 12 minutes. All in favor?
  12. 5 points
    I'm in the exact same situation... but for me it was an easy decision and solution. As soon as I realized that this was a complete re-write of the CORE I made the conscious decision (right then and there) to be patient and wait until 2.8.1 was released. I do the same thing when my DAW releases a major update. I wait for the dot release while everyone else finds the bugs. I do the same thing when Microsoft does a major update on Windows 10 (every March and November).... I wait until the first round of "fixes" are completed before I do the update. (eg: Windows update 1903 broke a lot of audio systems.... I waiting until the April fix was released before I updated) It's all software... and if I need to rely on it I am not going to be an early adopter of any major release! Coming from an IT background I do have one complaint... an update as major as this one should have been given the 3.0 designation making it obvious that a major change has taken place. Just my perspective :)
  13. 5 points
    You seem like such a reasonable and level headed person. Are you SURE you're on the right forum? ;-)
  14. 5 points
    Great work from line6 here! I like lots of the new features and pedal models. I hope they will implement a db meter for the compressors with the next version. Thank you Line6 for another great update free of charge.
  15. 5 points
    A At this point, where doesn't it come from? The participation trophy generation was raised with the steadfast belief that merely existing is in itself, praise-worthy. The universe owes them for breathing...and unless every need, want, and desire is delivered yesterday, exceeding their wildest expectations, and on somebody else's dime, it's an "injustice"... and someone must pay. They're all professional victims.
  16. 5 points
    I'm heading out of town for a couple of weeks and sent an e-mail to Line 6 asking that they hold off on the 2.8 release until I get back. I hope you guys don't mind.
  17. 5 points
    They do... well, the cabinets do, because that is really where the cuts are happening in real life Remember, the Helix is not "amp in the room" tone, it is "miced up amp" tone... which is very different. You cannot compare a Helix through an FRFR to an Amp sitting in the room. You need to compare it to that same amp, with a mic on it, pumped back through that same FRFR. When you do that, you will find the Helix to be remarkably accurate.
  18. 5 points
    Sorry ,but can't help but be other than hugely impressed by the fact that you did a 5 hour gig in the hot sunshine , i'd have given up way before the Helix.:-)
  19. 5 points
  20. 4 points
    While there are definitely a few people here saying they shouldn't have meters, I think most people are saying that, since they're not available and people are still using the Helix to great effect, they're not necessary and there's no point in complaining about the lack of them or using that a justification for your displeasure with the tones you're getting. The discussion I thought was going was that adding meters won't make your tones better, they'll just make them metered. And I'll say again, I would use them if they were there, but there's nothing missing without them.
  21. 4 points
    Just want to add... you can leave the LA Studio Comp where it is if you want to tame the peaks, just be sure to set the LA Studio to "Limiter" rather than "Compressor". That "should" tame the peaks, while leaving all the quieter parts (swells, reverbs, etc...) untouched. The LA Studio Comp is an LA2A model.... not a stomp box model. It shines at the end of the chain, but only if you don't try to use it like a guitar compressor.
  22. 4 points
    Nobody has ever brought this subject up before. After this many years, I don't think we should start now.
  23. 4 points
    ^^^ This, plus the fact that not all that many bridges are intonated well enough for fractions of a cent to be a rational concern during tuning :-) Just my .2 cents... :-)
  24. 4 points
    Guys, there were plenty of people who's update froze for a long time at the Warning Stage (can't remember what the exact error message was, but you know what I am talking about). Most of these people followed the instructions correctly. Mine was FUBAR and froze up for about an hour. Someone on this here forum had the same problem, offered a solution that worked for him, and it worked quickly for most everyone who tried it after that. Just want to be the voice from the other side. Not all issues were user error.
  25. 4 points
    I wouldn't say I'm being defensive... I don't work fro Line 6. I have nothing to do with the programming side of things. All I'm saying is that some of the ideas being put forth don't really make sense to me because that's not really how the product works. It's very hard to design a system that has some of fail-safe protection at every step along the way simply because people are really good at coming up with unexpected ways to find new problems. My day job is a lighting designer/engineer. The most complex things I do in my normal work are designing lighting control systems. And I'll just say that if you think the Line 6 software isn't user friendly enough, then never try doing anything with a lighting control system. But from the customer side of things, it's just hard to predict what people will do. This isn't meant to blame anyone, but if I have one word of practical advice for people, it would be this. Please don't update Helix during the middle of a thunderstorm... I've been slightly surprised/amused by a few reports from people who lost power when updating their Helix because they were doing during an electrical storm... :-)
  26. 4 points
    Good to know, thanks. If prior releases are any indication downloading the HX Edit package will include matched versions of the editor, drivers, and the updater, even if they are numbered differently. It still appears that users downloading components separately leads to the lion's share of upgrade problems every time there is a new release. Making backups, downloading these three components as a package(usually named "HX Edit") and then matching up your firmware is probably still the best way for most people to ensure everything is in synch. That way you don't wind up with mismatched versions of for example the editor and the firmware. As always follow release and upgrade instructions and make backups before you change anything.
  27. 4 points
    Lovely one with the retsina!!! Now absolutely seriously, one time that i was sailing, (i am seaman) i brought ouzo with me. I shared it with the crew (filipinos) and they put fanta orange juice. I was shocked, but they insist on me to try it, and honestly it is really a great combination. Now greeks want to kill me though !!
  28. 4 points
    hi guys first of all I'd like to let you know that I read all the threads I found about this same subject and didn't find the complete answers, so I decided to run some tests myself (like I did on the POD HD years ago) and to create a new thread with my results (I'm on FW 2.60 by the way) ok, I'll start from the end results, so that those who just need to have a quick answer can read it immediatly, then I'll give some deeper explanations the main point of this post is: the moment you create a split/merge routing configuration by dragging down a block you get a level change: after the merge block, with all bypassed fx: with split A/B and Y you get +3dB at the output sum with split crossover you get -3dB at the output sum BUT each path by itself gets attenuated by -3dB so if you use the split A/B to switch between sounds, each of those sounds is -3dB qiueter than the same fx/amp with the same settings in a non-splitted path the good news are that the level changes do not actually occur at the split, so the two paths are both an exact copy of the signal before the split, instead the change occurs at the merge block so the right solution is to act on the merge mixer faders --- why? and why those values? • well to answer, I need to clarify two things that I've read someone get wrong and mixed up in other threads 1) when you sum two identical signals in a circuit either analog or digital you get +6dB boost (voltage sum) 2) when you send a signal to a physical speaker and then send the same identical signal also to another identical speaker you get +3dB (acoustic power sum) this is math and physics, not an opinion now, this second point is one of the reasons why something called "pan law" exists: as we said, when you have a mono signal going to two speakers (so the pan knob on a mixer is at the center position) you get +3dB of sound pressure so mixer designers in some cases decided to pad the center position of the pan knob by -3dB, gradually returning to unity gain at the extremes (in some other cases they may use -2.5, -4.5 or -6dB: the actual effect of the pan law depends on the coherence/incoherence of the signals, on speaker placement, on listening conditions, and also on mixing taste I would say, so the designers have to make an assumption and take a plunge, I don't have time to enter into this now, sorry). • now back to the Helix: you have an empty "new preset" patch you have a signal going through path 1 (I used various sine waves and pink noise) you add a gain block at 0dB (if you want you can even bypass it) => nothing changes you drag the block down creating a double path => you get +3dB at the output sum so, what's going on? - the A/B or Y split duplicates the signal to two paths, so each of them carries the same identical signal which goes to a merge block mixer channel, then the two get summed together... so you should get +6dB, but... ... since the pans in the mixer have a -3dB pan law you only get +3dB - the crossover does not duplicate the signal but splits it in two frequency bands, if you sum those two filtered signals you get the exact same signal you had before, so no +6dB boost here, but there is still the pan law, so you get the -3dB - but, as I wrote before, each path by itself gets attenuated by -3dB because of the pan law, so if you use the split A/B to switch between sounds, each of those sounds is -3dB qiueter than the same fx/amp with the same settings in a non-splitted path • please note that these are not theories or speculations, I've tested and measured thoroughly every configuration and I'm sure the Helix routing works like that • all this behaviours occur identically to mono or stereo signals, remember that all the lines representing signal flow in the Helix display are always "double conductor cables" so either stereo or dual-mono (stereo = they carry two different signals; dual-mono = they carry two identical signals) this point could be deepened a lot but I don't have time for this now --- some other considerations: • if for example you open the pan pots of the merge mixer to the extreme L and R, the pan law attenuation does not apply and the level goes back to unity BUT this is not a solution, because if you run in stereo you only get the left from path 1A and the right from path 1B • I'd like to warn you of potential problems I found with the parameters inside the split blocks I) the split A/B "route to" parameter is a balance control, not a crossfader, so moving it to the left attenuates the signal going into B while not touching the signal going into A and viceversa; so it is appropriate to use that parameter to switch from A to B but not too much to find a mix of A with B for 3 reasons: 1- as I said you only have control over the attenuation of one of the two signals you are mixing 2- at center (even position) you have more level than any other position because the two signals are at full level, so the judgement on which is the best mix is compromised for psychoacoustic reasons 3- worst of all: if the blocks in the paths are amps or distortion boxes or compressors, as long as you are not in A100, "even" or B100 positions, you are sending an attenuated signal to one of them, changing its sound and not only its level II) the split Y "Balance A" and "Balance B" parameters (added in fw 2.10 so not covered in the manual) work like this: the stereo or dual mono signal goes into the split, it is duplicated to path A and B and on each of those you can control the balance between left and right, those balance control also have a pan law but different from the merge mixer block pans ! in this case it's unity at center and +3dB at sides ! (I think the reason for this is to avoid an attenuation to the splitted signals at default settings) so if for example you use 2 amps in the paths do not use these parameters or the two amps will receive a different level than if the balance is at center. --- • to finish I'll add two other Helix Routing measurements I found during my tests: - the pan block is actually a balance control with a pan law equal to that applied in the split Y block: at center it's at unity gain, going to the left attenuates the right up to minus infinite and adds +3dB to the left (and viceversa) - unlike the POD HD500 the fx sends / returns on the Helix are all at unity gain levels (+/-0.3dB), thanks Line 6 ! --- thanks for reading, I hope to have been helpful bye Lorenzo
  29. 4 points
    I know how you feel, brother. When I was but a lad on the precipice of adolescence, I came up with the idea that male and female organs might actually fit together somehow. Now all kinds of people are doing that and not one. single. person. has thanked me for the original concept. On a less ludicrous note, I've chased after these a-holes selling paid for presets for quite a while now. They site-rip Custom Tone, buy producers' monetized tones, and then sell them on eBay. Every time I see one of them advertise in threads I ask the direct questions (never answered). With respect to people all butt-hurt because their uploads are used as templates for other tones, that is what they are there for. It's crowd-sourced content. Get over yourself or start charging for your stuff. Frikkin' cry babies.
  30. 4 points
    Lol...well that is quite the list. Given it's extensiveness, if I were you I'd prepare for what will very likely be an epic, personality-shattering disappointment. ;)
  31. 4 points
    They could call that the cork sniffer tone variation switch!!!!!
  32. 4 points
    The point of an ICON is that it's an OBVIOUS representation of something. A new user would NOT recognize that icon as representing the function SAVE. That particular icon usually means DOWNLOAD, not SAVE. Best practices in GUI design (at least as I learned it) has always been to use pop-up Tool Tips with icons. EDIT - NBD, just pointing out a possible reason for OP's confusion.
  33. 4 points
    https://en.wikipedia.org/wiki/DWIM Sorry, I couldn't read all of your message on my phone.
  34. 3 points
  35. 3 points
    Normally at this point I'd crack wise about little maple candies and weird round bacon... but truth be told, these days I'm genuinely envious. It's a $hit-show down here. ;)
  36. 3 points
    And when just the wireless part craps out, now the brains of my rig has to get hospitalized along with it till it's fixed? No thanks. Want a wireless? Buy one... having absolutely everything in one self-contained unit is never a good idea.
  37. 3 points
    What worked for me (only a couple of my Presets seemed to be affected) was to use HX Edit to change to another Snapshot. Click on the error message that resulted (this makes the message disappear) and SAVE the Preset. Do this for each Snapshot in turn. Tedious, but much quicker than recreating the Preset from scratch.
  38. 3 points
    THIS is proper thinking. I updated because I don't have a critical need for Helix to be 100%, so I'm willing to play with new features at some risk of issues and maybe help find glitches. Any major software change is like this, from firmware, to apps, to computer OS. Companies try to beta test thoroughly, but until it gets into "the wild" with the entire user base, things will likely be missed. This is simply the reality of software development. To expect different is just not reasonable, IMO. The greater difficulty of this update was PLAINLY spelled out, as were the step by step instructions. There are those having problems despite following instructions, but most that I've seen have gone back, said "oops", done it correctly, and are working. Anyone seeing "major code rewrite" and still opting to update a "critical production system" instead of waiting a bit for the x.1 update is playing with fire. With any brand or software type. Agreed on the 3.0 designation. My guess is the new feature set wasn't enough to name it that way, but as another IT guy, the code rewrite warranted it.
  39. 3 points
    Check in the Global Settings———>Preferences Check that Joystick Encoder it’s set to Model. This is the original behavior. If it’s set to Selection, it is moving Left/Right while rotating, but you can still select Models if you rotate while pushing.
  40. 3 points
    The feature I would like to see is «converting» of Amp+Cab/Amp/Preamp blocks I use the Helix with two DT50 but also direct out or with headphones for practice at home at night. I dial my tones mostly connected to the DT50, where I use preamp-blocks. When I'm satisfied with a preset, I make a copy for direct out/headphones. There I have to replace the preamp-block with an Amp or an Amp+Cab block. Switching the block resets all settings to default. That means, I have to manually write down the settings, change block and apply them again. I like so see the possibility to either a) change the block type between Amp/Preamp with all settings kept, or b) copy only the amp-settings and apply them to preamp-block and vice versa
  41. 3 points
    The words "corporate" and "soul" don't really belong in the same sentence... On the other hand, I bet I could order a soul from Amazon, and have it here by this time tomorrow...;)
  42. 3 points
    Oh, I bet they do. With a projected release date of Spring 2027.
  43. 3 points
    Colors? No problem! I've added them in my list. I used a seperate column - otherwise you couldn't read anything...and it could seriously damage your eyes. ;-) Maybe it's helpful. The comments I had saved in my list are from the Line 6 homepage...but I don't know, where I had found them... Only the gear of the Firmware 2.50 had any kind of descriptions. Line 6 gear 2019-06-04.xlsx
  44. 3 points
    Geez, do I have to do everything around here?
  45. 3 points
    The thing is that expectations play a huge part in these sorts of things. If you play something and expect it to sound a certain way, that is often what you'll hear. It's called confirmation bias. Really, the only proper way to do this sort of comparison is a true blind test, and that's darn near impossible to do on your own. I've heard clips comparing real amp to the Line 6 modeled ones, and they get very, very close. When Line 6 had the "Helix Challenge" up on their site, 50% of the people guessed which was the real amp and which wasn't... That's basically what you're looking for in a modeling scenario - the guess rate is the same as chance.
  46. 3 points
    UPDATE: Instructions for installation further down the page Not sure if any of you folks out there are in Linux-land, but after an SSD failure yesterday I took the opportunity to rebuild my machine with a clean version of Ubuntu 17.10 and WINE (I record using Reaper). Instead of using the Windows version of Reaper, I installed the Linux native version, and then spent the evening futzing about in a last attempt to get Helix Native working. The result... That's Helix Native running under WINE inside Reaper running natively (with lin-vst as the wrapper). It works fantastically well; even patches which would max out a hardware Helix are using just 3% of the available CPU capacity (it's an i7 6700), with no additional latency compared to other amp sims. I is a happy camper :) I couldn't find any info about the process other than the maintainer of lin-vst dropping some hints (and he missed out some major gotchas). Is there any appetite for a guide on how to install it, or is it just me who wants this and nobody else cares?
  47. 3 points
    Just wanted top let you all know that this patch (and IR) should be in the Line 6 Marketplace section tomorrow for all Helix and HX Stomp users. Thank you so much for your continued support.
  48. 3 points
  49. 3 points
    you are just gonna get different opinions.This is how i decided if it was something that i can work with and use.
  50. 3 points
    I'm just curious, with all of this screen real estate, I thought it would be nice to have an area to put some notes about the patch. Like what kind of guitar, what distortion did you use, stereo mono, etc. whatever. Just to remind me/us about what some of the specifics are in specific patches. Just curious your thoughts. Have no idea how easy or hard it would be to implement. And I know it would use the same method patch naming directly on the Helix does. But I would assume it would be available in HX Edit also if it were implemented. Just curious about peoples thoughts on this. Worth it? Or a waste of the developers time?
This leaderboard is set to Indiana - Indianapolis/GMT-05:00
  • Newsletter

    Want to keep up to date with all our latest news and information?
    Sign Up
  • Create New...