Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 08/20/2018 in all areas

  1. 7 points
    Embedded programmer and software test engineer here. Since you seem to prefer voicing your opinion in a very direct way, I'll do so too: This crap is becoming tiring. You seem to have zero insight into software development, yet you come here and know exactly what the developers at Line 6 are doing wrong because... Yes, why actually? As an attempt of explanation: Resources are limited. The main resource in this case is the time a team of developers has in total. This time can be spent on concepts, architecture design, implementation design, implementation itself, testing, debugging, maintaining and many other tasks. Developing for a real time embedded system like the Helix isn't like clicking on a few icons in an Android App Maker to build the 16931st whoopee cushion soundboard for the Play Store. These projects eat a ton of time in every stage from concept over implementation to maintenance. Almost everything has to be optimized because any code that is inefficient would result in an audible delay, every bit of wrong code would distort the sound in various ways. This is one aspect. The other is what amsdenj mentioned: Technical debt. It's a term for tasks and unsolved problems that have accumulated over the development of a component or a product, basically a To-Do-List. This list has to be tackled someday if you want to keep your product in the market. If you look at the changelog for the 2.7 update, it's a lot of those minor annoyances that may be major ones in the wrong setting, like polarity/phase issues and amps that become quiet. The third aspect is that we are not talking about a single device here. Helix is a platform with by now a whole set of different hardware devices and a software plug-in. "Platform" doesn't equal "I write a line of code and it works everywhere". It once again may have to be optimized and it has to be tested. And no, testing isn't plugging in a guitar, checking if there's sound and if so, ship it. If that was the case, we wouldn't have to fix bugs at all. Look around in the forum. For over one year there have been complaints about the tuner, including lengthy posts, heated discussions, YouTube side-by-side comparisons with other tuners, people testing it with different instruments and what not. I play bass and have had very few issues with the tuner, but it seems to be a problem for many users. What did Line 6 do here? They addressed a complaint. Isn't that what you wanted? No, you're one of those people that not only buy a product and then somehow feel entitled to get something they want, you also have the impudence of putting yourself above a department full of most likely very experienced software engineers, programmers and projects leads saying "They're all idiots because they can't do more.". I recommend you get yourself a SHARC evaluation board, a matching C++ IDE and start writing your own DSP accelerated real time sound processing pipeline. Then you can use all your insight to add amp models, fix bugs, walk and chew bubble gum every day.
  2. 6 points
    I think Mooer won't get another cent from me (I had some of their small pedals at one point)... Doing what they did with EHX and getting caught only means they're doing it for other things as well. There's too many honest companies making good products to justify supporting a company that's doing that sort of crap.
  3. 6 points
    Allow me to spare you the suspense...Helix will not have an additional 200 amps a year from now, so you might as well break out the credit card and beat the Christmas rush.
  4. 5 points
    Line 6 Helix 2.70 Mega-Setlists · 4 Setlists: IRs LG + IRs HG & Cabs LG + Cabs HG. · 232 Presets, each with 8 Snapshots. · 57 solo amp & 175 dual amp presets. · Cab Sets feature L6 Cabs. IR Sets feature IR blocks, but not IR files are provided. BYOIR. · LG = Low Gain (Supro->Plexi Jump). HG = High Gain (2204->L6 amps). · Each amp features Snapshots for Low, Mid, & High Gain settings. · 2 formats for dual amp presets: “Channels” & “Parallel Amps”. · LED rings color coordinated for Snapshots view. · All FX Blocks are custom named. · All Snapshots output leveled to -28.5 LFKS Integrated, ITU-R BS.1770-4, over 15sec of looped open G strumming. · EXP Pedal 2 has additional Mod, Delay, & Reverb settings. · Amp and FX settings largely derived from the SOAS Project (25%) and personal preferences (75%). · To Import, Drag + Drop directly into Helix. Or hit the top left yellow “Import” button & search for “all files” instead of just .hls. I am not sure why the Setlists are saved as .hlx instead of .hls files. · For more information, including lists of all of the amp and effects settings, along with the OwnHammer IR’s I used, please visit: https://l6helix.wixsite.com/helixsoas · To Download the Setlists, please visit: https://line6.com/customtone/profile/Noobian_Prince https://imgur.com/a/Gic53qq
  5. 5 points
    Why is a guy demo-ing a guitar speaker without having someone actually play a guitar through it? Why SAY this is different than the TS312 without actually running music through both? This has to be one of the stupidest AND most useless YouTube reviews EVER!
  6. 5 points
    Hey - First time poster. I recently got a Helix (love it so far) and while creating patches, I thought it would be nice to have a one page resource for what the blocks are modeling. I tried creating one that kept the theme of the Helix overview cheat sheet available from Line 6. Link: Google Drive PDF I use it all the time now as I'm getting to learn all the Line 6 names and what they are modeling. Thought maybe someone else might benefit from something like this. Cheers.
  7. 5 points
    I've been piping pink noise through the Helix Native mic+cab sims to learn more about them. I don't care at all about what the real units sound like, just about how they shape the sound. This is what I've seen so far: For pretty much any mic, increasing the Distance parameter causes some boosts and cuts in the mids, the frequencies of which which seem to depend on the cab. For instance, on the 4x12 WhoWatt 100, increasing distance significantly cuts 1.2KHz, whatever mic you use. In fact almost all cabs see cuts around the 1-1.5KHz range, with the 4-speaker cabs showing the biggest effects. On top of that, for pretty much any mic+cab, increasing the Distance parameter causes a low roll-off typically of between 6 and 12dB, and a small high-end cut, and a more gentle output decrease across the board. A couple of cabs also see small boosts in the mids, like the 1x12 Celest 12H. I don't think the proximity effect is being modelled because the low end reduction doesn't seem significantly different across the mics. Increasing the Early Reflections parameter causes a broad but small boost in the 300-500Hz range. I didn't measure to see if there was any actual reverberation/delay effect included. By averaging the response across all the mics for a given cab you can get a good feel for its 'signature'. For example, the 4x12 Greenback has a slight boost in the low mids, then a pretty smooth roll-off as the frequency goes up, except for a big boost between 2K and 6K. Good for taming the treble of high-gain, while letting it cut through at the same time. By comparison the 1x12 US Deluxe is almost flat right up to that 2K mark, falls off at 5K, but with a characteristic spike around 12.6K (probably now inaudible to anyone who played through the speaker when it first came out!) And the 2x12 Jazz Rivet is also pretty flat, with a smooth but steep rolloff after 5K, punctuated by a sharp notch at 6.6K. ...and so on. If, like me, you know nothing about the cabs and don't have a specific sound you're going for, it's definitely worth trying some different ones to make sure their particular brand of cuts and boosts fit your material. Arguably the flattest response, with otherwise 'default' settings, is the 2x12 Double C12N, with Distance at 1", and using the 67 Condenser mic. If you want a fairly neutral starting point, I recommend this. For the most low-end, the 4038 Ribbon mic is the one to consider, followed by the other ribbons. For the most high-end, the 421 Dynamic, closely followed by the 112 Dynamic, seem to be the best choices of mic, which seems to tally with the real-life frequency response charts. The 12 Dynamic mic has a significant boost around 700Hz, and which strangely isn't present in the frequency response diagram for the real life equivalent. Might be good for helping leads cut through the mix though.
  8. 5 points
    The pattern is, about 3 - 6 months after any update there is a "when's the next update" rumble on the forums. It kind of comes and goes like the tide for awhile UNTIL the "I heard there's one coming shortly" rumors. Then comes the what they should and shouldn't include along with the "this is what I heard" and "it should be coming come out......" speculation. That whole noise floor keeps rising and rising along with the "what's taking so long" posts until people start to think they can't take all of this waiting anymore. Now a couple of "I'm a beta tester and we're still testing" posts.........THEN!!!!!!..............the update finally comes. At this point the "it's been two hours where's the next update" jokes (often from yours truly) and the "great work Line 6" posts start along with the "this sucks", "why didn't they...", "well you suck if you think this sucks", "well you suck if you don't think this sucks", "are there any new factory patches?" etc. etc. posts. Finally it settles down until about 3-6 months after that. Go back to start. Did I miss anything? Oh....you mean Line 6? No there's no pattern really other than a semi official "we're close" post about a week or two before it finally comes out.
  9. 5 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.
  10. 4 points
    I understand the design motivation for limiting HX Stomp to 6 blocks: Keeping the UI elegant, simple and easy to use Focus on adding a stomp box in an existing pedalboard to compliment an existing setup with HX capabilities Consistency between the number of blocks and DSP capacity Anticipating future blocks that may utilize significantly more DSP resources Limited number of foot switches to control blocks Essentially this means HX Stomp is intended to provide Helix capabilities, with minimum footprint, to existing pedalboard and amp setups, not to be all things Helix in a tiny box. I get that, and these are all good design decisions, although these design decisions also sound appropriate for HX Effects. But let's look at how HX Stomp might be used in a gigging situation by itself to see if 6 blocks is enough. This might be for rehearsal, as a backup to Helix, as a convenient fly rig, or just because something so small is so useful. Consider a typical guitar signal chain that uses front and back of the amp effects (| means or): Input > Wah > Compressor > Drive > Overdrive > UniVibe | Phasor | Flanger | etc. > Amp > Cab | IR > Chorus > Delay > Reverb > Output This it my typical gigging Helix patch. I use 10 Stomp mode and pretty much stick with the same patch all night, using snapshots for open tunings, acoustic, and Leslie. This is 10 blocks, and clearly requires more foot switches than HX Stomp can provide. If you need patches like this or more complicated, you need Helix or Helix LT. Trimming this down to 8 blocks, we get something like: Input > Wah > Compressor > Overdrive > UniVibe | Phasor | Flanger | etc. > Amp+Cab > Chorus > Delay > Reverb > Output If you leave the Drive, Amp+Cab, Delay and Reverb on all the time, and you have a Line6 Mission pedal (if you don't, get one, it makes HX Stomp is a lot more useful), then you need foot switches to control Wah, Overdrive, UniVib, and Chorus. If you configure FS3 in global settings for Stomp, then you have the four foot switches you need. This seems like an ideal setup for HX Stomp by itself and is something I would be happy to gig with. To trim this down to 6 blocks, we get something like: Input > Wah > Drive > Amp+Cab > Chorus > Delay > Reverb > Output This is still pretty good, but looses the front of the amp modulation effect, something I use quite a bit. The work around is to create a patch template that covers the common blocks, then create a different preset for each front of the amp effect you need. That can work since you generally only need one of these at a time. But it means creating and maintaining a lot of patches that differ in only one block, and the potential need to change presets in the middle of a song to get different front of the amp effects. This is probably not practical. So I vote for 8 blocks, full Helix Path 1 capability, and let us users deal with balancing blocks and DSP capacity, just like we do with Helix. Two more blocks is actually a lot of additional flexibility without much additional complexity. This said, I'm pretty happy with HX Stomp just as it is and would highly recommend one as an entry point into the Helix ecosystem, as a Helix backup, or as a stomp box to add Helix blocks to an existing rig.
  11. 4 points
    I am here about 10 years, and as far as i recall, official line 6 persons get more involved there than here. And still yet not figured out why. Lately, line 6 made a survey, and one of the questions was how to improve communication or something like this. I answered, simply speak with us as you do in tgp forum...
  12. 4 points
  13. 4 points
  14. 4 points
    I went through TGP and got all of the info about the Helix models I could find along with some "hints" and put it in a word document for myself. I wish there was some kind of official Line 6 document with this kind of info in it. Here it is if you want to look at it. It's not really organized all that well but, hey, I created it for me. It's 40 pages long. I had to split it into two documents to attach here. It is in the old Word format. Helix Models Info 1.doc Helix Models Info 2.doc
  15. 4 points
    Yes, I see that you agree with yourself... :-)
  16. 4 points
    So, if you think there's a product that has all the amp models and effects you want, why not just use that product instead of expect another manufacturer to essentially copy what they're doing? I can tell one thing for certain, and that's that Line 6 is really not interested in trying to recreate the feature set of the Axe FX in the Helix. They have their own vision for what the Helix is going to become. Certainly that means more amps and effects in the future, but it doesn't mean trying to please everyone...
  17. 4 points
    I've been waiting for this feature, but Line 6 keeps disappointing:
  18. 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.
  19. 4 points
    Is this post for real? Out of curiosity I looked at the OP's custom tone page and the upload date was 1/6/18. Glenn's were put up a couple of years ago. Heck I have 2 organ patches for Helix on CustomTone that I posted back in '16. Maybe the OP and I could start a class action lawsuit against Glenn :) I made cheeseburgers last night and I've been waiting all day for McDonald's to give me a shout out for that concept....
  20. 4 points
    how can an update (and it's free for chrissakes) be disappointing ?
  21. 4 points
    Agreed! Some of the guitar cabs are far better than many bass cabs... for bass use! One important trick for me is to avoid the use of certain mics (57 Dyn cuts lows!). In my experience, a close (1'') 414 Cond or 121 Ribbon give me the best results. If some cab is too dark, then the 47 Cond helps (this is what comes with the SVT by default). Then the 4038 Ribbon boosts lows too much, it is useful sometimes, but I am not sure if there is the need to boost lows when there are so many cabs that work well. Avoiding medium distance "57 Dyn" is what makes MANY guitar cabs usable for me. My favorites bass cabs (Forgive comments in "Spanglish"): Also "No cab" works really well for me. With some EQ to tame and "voice" high frequencies, but totally transparent with lows. It avoids phasing issues. We bass players have enough with our "FRFR" cabs, they are not that "transparent" in the lows, so there is no need to make the problem twice as bad. I have certain theory why some "good" or "professional" or "thoroughly recorded" cab models are not so great with the Helix or any other modeller. Their responses are anything but "tight". 1x18 Woody Blue may sound good with headphones, but I doubt it is good with the full band and using any practical real cab in stage with the full band at high volume. To me it sounds really BAD. I can understand why some bass multi effect users are enthusiastic with their presets tuned with headphones without a band and then in the first rehearsal the band tell them "This is for guitars, your old bass amp sounded way better". ================== About the blend: Some overdrives / distortion have. And this is great because this avoids certain subtle problems that appear when using parallel paths. The problem with parallels paths (besides being very limited in number) has to do with phasing issues, they are different for each amplifier or overdrive. These issues are far worse in bass than in guitar. I know that this topic can be very controversial. Some ODs don't have a blend control, but they work at low / moderate gains "as if" they had a clean parallel path. If you play bass I recommend to try Teemah! for this reason. Teemah! and Obsidian 7000 are my favorite dirts. I have a preset that is simply Teemah! plus an EQ (instead of cab) plus effects, this is one of my favorites with the band. Because it is "rich enough" but "TIGHT". And I need my bass to sound very tight in many songs / band situations. Next in my "OD" list are 3 bass amps (SV Beast and Tuck'n'Go) and then Clawthorn Drive. There are many usable blocks to create OD / Distortion, some are bass amps, some are guitar amps. IME many of them are totally unusable for bass. But there are some surprises, for example the LEGACY heavy distortion (this one requires a parallel path). Or the Tube Screamer emulation is too "treebly", but does not CUT bass, so it admits EQ to restore bass... and does not require a parallel path! (it works better in a band context this way). I really would like to add a blend control in overdrives and distortions. Now I know it is not trivial to add if done properly. Hope it helps.
  22. 4 points
    No, not enough with the high gain. Enough with the Marshalls. We could still use more high gain options.
  23. 4 points
    This is why I'm so supportive of people like Jason Sadites in that a person is FAR more likely to benefit from his video tutorials on YouTube for getting a great sounding preset to meet their needs than they are to expect any preset they purchase or download to be instantly useable for their configuration.
  24. 4 points
    Hello, I would like to have a block “feedback generator” like the Digitech Freq Out pedal or like the Feedbacker of the Boss GT100 to play with feedback at low sound level.
  25. 4 points
    The most glaring deficiency in the Helix... The lack of a Korg Miku model...
This leaderboard is set to Indiana - Indianapolis/GMT-04:00
  • Newsletter

    Want to keep up to date with all our latest news and information?

    Sign Up
×