Please ensure Javascript is enabled for purposes of website accessibility Jump to content

pomor

Members
  • Posts

    22
  • Joined

  • Last visited

Profile Information

  • Registered Products
    5

pomor's Achievements

  1. Check this out: https://line6.com/support/topic/49342-hx-edit-281-and-helix-native-starting-with-with-a-blank-screen-and-crash/page/3/
  2. It looks like the 3.5 factory setlist TEMPLATES is broken - the actual presets are shifted one preset back with relation to their titles in the preset list, as illustrated below: the first preset called "Quick Start" is not the actual "Quick Start" preset as it was in 3.15, but in fact it is the "Parallel Spans" preset. The actual "Quick Start" preset is missing. Next preset called "Parallel Spans" is in turn the actual "SNP:4-Amp Spill" preset, an so on. Not a terribly huge deal since you can always just restore 3.15 TEMPLATES from backup, but still looks like a bug.
  3. Thanks, this makes sense. If I may suggest, it would be great if you guys put this exact information into the top post in this forum that currently reads “This topic is not intended for bad-mouthing the Helix but for providing Line6 with maximum feedback to assist them in fixing issues as early as possible.”, which creates an impression that this forum is indeed targeted directly at L6, and maybe change the title to something like “Helix Bug Discussion” (unless existing contributors would get too confused by such a change) - somehow I think I’m not the first (and probably will not be the last) person who got slightly confused here… 25 years in the software industry makes you interpret the phrase “bug reports” in a very specific way. Cheers!
  4. Thank you for your reply. So, this forum is called “Helix bug reports” and L6 don’t read it? What is the point in submitting bug reports here then, since no-one except L6 can fix bugs? Also, few posts prior you responded to someone’s bug report: “Reported and verified. They're working on it.” Was that bug reported to L6 via ideascale or some other, actual L6 bug tracking system? Appreciate if you clarify.
  5. I have an enhancement request - please increase the timeout of the Tempo configuration page or make it persistent until next UI action is performed outside the page - there’s not enough time to adjust the tempo and listen to the results when setting global tempo with the knob by ear, the page closes too soon. Thank you. This is Helix Floor 3.5.
  6. No problem, I was just as confused :) seems like the UI could use some improvement.
  7. There are two distinct tabs with “restore factory settings” buttons, probably you are on the wrong tab. Not at my computer right now and I don’t remember the tabs’ exact captions, but one is for settings and the other is for presets IIRC..
  8. Helix Native 3.5 does not provide the rate “Note Sync” option for these two effects either.
  9. Thanks, I did the factory reset (so I'm seeing the new presets indeed), and I deliberately did not restore FACTORY 1 setlist from the backup in order to keep all the new presets. Take for example 12A "Justice Fo Y'all". The cab on the path A is the new dual 4x12 Cali V30 / 4x12 Uber V30. But the cab on the path B is the legacy single 4x12 1960 T75. Can you (or someone else) please check yours to see if your preset shows the same? Thanks! Update: Helix Native 3.50 behaves the same way. Update 2: It is understood that not all legacy cab models were reimplemented for the new cab engine, so presets using those remaining legacy cabs can be expected to continue using the legacy models. But it looks like in some presets (12A for example, again) there are still legacy cabs that do have new, reimplemented counterparts, like 4x12 1960 T75. What might be the reason?
  10. My first attempt to update failed at the very beginning the same way. I had Line 6 FBV Shortboard connected to the computer as well. Disconnected that, power-cycled Helix, restarted the update and it went through all the way.
  11. I'm seeing that some FACTORY 1 presets were completely converted to the new cabs, some use a mix of legacy and new cabs and some still use only legacy cabs. Is this what everyone else is seeing and is this supposed to be this way? Thanks!
  12. Thanks everyone for your comments. I do have the latest FW 3.15 and I did see the mention of improved knobs ballistic in the release notes, however it is still far from ideal. For me, the current algorithm based on the speed of rotating the knobs is rather erratic - a few times it works ok, next time it doesn't and sometimes a param jumps straight to its min or max value. It seems to work somewhat better for wide range parameters like delay times, but seems worse for the plain old 1-10 knobs. @PierM - very good point regarding limited encoders' resolution - this morning I realized it too that a simple straight min to max adjustment per single turn alone will be too coarse for, actually, most of the params. I have a couple of thoughts on possible further improvements though, I'll try and post something on ideascale.
  13. Dear Helix developers, it would be great to have, possibly as a configurable option, a “realistic ballistic” mode for parameter knobs, meaning, any parameter knob being able to change the corresponding parameter from its min to max value just in a 3/4 of a physical turn, just like a real potentiometer. In this mode, fine adjustments could be implemented via a simultaneously pressed modifier button. Currently, it is, unfortunately, a PITA to quickly adjust params, compared to a real amp or an effect device. Thank you.
  14. Thanks, I saw this too - I waited until it finished and went to the home screen, I even played it a little and then I turned it off and then back on later - that's when it hung.
×
×
  • Create New...