Jump to content

MusicLaw

Members
  • Posts

    1,521
  • Joined

  • Last visited

  • Days Won

    6

Posts posted by MusicLaw

  1. The Yamaha DXR10 are truly outstanding! Not too heavy. Not too big. Not too small. They sound phenomenal at any volume, horizontal and vertical, and they can get plenty loud! Fed 1/4" stereo from Helix's Amp outs, the DXR10s' 1/4" (Input 2) Level controls were set at 12 o'clock (0 db) for Line level. With Helix's Main Volume at 12 o'clock they sounded absolutely thunderous! I'm loving these FRFR PA speakers. :) They're really well constructed and covered by a reassuring 7 year warranty. I've yet to try them with XLRs. More fun with DXRs tomorrow....

    • Upvote 1
  2. Quarter inch outputs will be louder

    I discovered this with a set of JBL LSR305. Fed by Helix's Line Outs (set to Line Level) they would not reach the SPL as when fed by Helix's 1/4" Amp outs.

     

    Has Line 6 published Helix's Output specs? If so, where are they available? I have not seen them.

  3. This sounds like the it should be a Global Settings, User Preference Item. Sort of like the fsw configuration layout options.

     

    Why couldn't Global Settings allow users to designate their default preference EXP1/EXP2 options, such as: Vol/Wah, Wah/Vol, Off (until otherwise Model/Block Controller assigned), etc?

  4. For Download and lnstallation Instructions, See: http://line6.com/software/index.html

    (Choose "Helix" in first Product dropdown and your Operating System in last dropdown)

    =========================================================

     

    Helix Firmware 2.10 Release Notes (Nov 22, 2016)

     

    New Amp Models

     

    Archetype Clean, based on* the clean channel of the Paul Reed Smith® Archon®

    Archetype Lead, based on* the lead channel of the Paul Reed Smith® Archon®

    Line 6 Litigator, new Line 6 Original inspired by boutique mid-gain amps

     

    New Effects Models

     

    - Distortion > Stupor OD (Mono, Stereo), based on* the BOSS® SD-1 Overdrive

    - Delay > Pitch Echo (Mono, Stereo), Line 6 Original

    * Paul Reed Smith and Archon are registered trademarks of Paul Reed Smith Guitars, LP.

    * BOSS is a registered trademark of Roland Corporation U.S.

     

    New Features

     

    Auto Enable/Bypass blocks from EXP 1/2/3 and Variax Volume/Tone Knobs—Processing blocks (such as Wah, Pitch Wham, etc.) can now be enabled/bypassed by simply moving EXP 1, EXP 2, EXP 3, or Variax’s Volume or Tone knob. Press MENU and then Knob 1 (Bypass Assign). Turn Knob 1 (Switch) to select the desired switch. When selecting a continuous controller as a switch, Knob 2 (Position) and Knob 3 (Wait) appear.

    Bypass Assign > Position—Position determines the location in the Exp Pedal or Variax knob’s travel where the block is engaged. For example, if set to 1%, the block will turn off as soon as the pedal is moved to the heel position. If set to 99%, the block will only turn on when the pedal is moved to the toe position. To swap the on/off state regardless of position, press the BYPASS button.

    Bypass Assign > Wait—Wait determines how long it takes after the Exp Pedal or

    Variax Knob is moved below the Position location before the block turns off. For example, you may not want the Wah to turn off instantly every time you hit the heel position during your big funk solo. Also, does your song really need a big funk solo?

    Block Bypass via MIDI—Individual processing blocks can now be enabled/bypassed via incoming MIDI CC messages. Press MENU and then Knob 1 (Bypass Assign). Turn Knob 4 (MIDI In) to choose the desired MIDI CC. Incoming CC values 0-63 will turn the block off; values 64-127 will turn the block on. Note that some MIDI CCs are reserved for global functions and cannot be selected.

    Learn Bypass Assign—As with Controller Assign, you can also now quickly learn a source for bypassing the selected block instead of assigning it manually. On the Bypass Assign screen, press Knob 6 (Learn) and then engage the desired footswitch, expression pedal, Variax knob, or MIDI CC. Helix will show the switch above Knob 1 (Switch) or if it’s a MIDI CC message, above Knob 4 (MIDI In).

    Clear All Bypass Assignments—You can now clear all bypass assignments at once. From the Bypass Assign screen, press ACTION and then Knob 1 (Clear All Assignments). Press Knob 6 (OK) to confirm.

    Snapshot footswitch LED color—You can now choose a color for each snapshot footswitch. Press the PRESETS knob and then Knob 6 (Rename Snapshot). Turn knob 5 (LED Color) to select the desired color. â€œAuto Color†is the default red. NOTE: There is currently no way to set snapshot footswitch color from the Helix application.

    Split > Y Balance parameters—The old Split > Y block sends both left and right signals to Paths A and B equally. 2.10 adds individual balance (pan) control of the signals sent to Path A and B. By default, they’re set to “Centerâ€, which behaves exactly like the old Split > Y block.

    Support for MIDIpants

     

    Improvements/Changes

     

    - Added a Headroom parameter to Delay > Vintage Digital

    - Snapshots now recall the currently active expression controller (EXP 1 or EXP 2) for the built-in treadle

    - Split > Y can now be bypassed; when bypassed, the block sends both left and right signals to both paths equally (like the old Split Y block)

    - Looper Mode switch LEDs now display a dim/lit state to better reflect their current states

    - Non-selected Pedal Edit Mode parameter switch LEDs now display a dim state

    - Added forward slash [/] to list of characters for naming presets, setlists, snapshots, and Stomp mode custom labels

    - Bypass Assign > Knob 1 (Footswitch) has been relabeled “Switch†to better reflect all values

    - Tap Tempo no longer affects a preset’s dirty state (“E†icon)

    - Minor updates to the Factory Preset bundle

    - If a user fails to read and follow the update instructions, Helix will cause their car radio to only play polka death metal every Thursday from 1-3pm PST

     

    Bug Fixes

     

    - Errant graphics could appear when selecting an IR block from the Controller Assign page - FIXED

    - When assigning a command to EXP 3 on the Command Center page, the turquoise indicator could occasional fail to appear - FIXED

    - When sending/receiving Looper MIDI CC messages through external devices, MIDI feedback could occur - FIXED

    - General stability improvements

    - Other minor bug fixes and optimizations

     

    Known Issues

     

    - In very rare cases, corrupted presets containing a Volume/Pan > Volume Pedal block can cause volume to drop to 0%. In such cases, completely clear the Volume Pedal block and add again. If the same preset exhibits this behavior again, please contact Line 6 Customer Service and be ready to email us the raw preset so we can analyze it

    - Bypass Assign > Wait defaults to 300ms from the hardware and 100ms when selected within the Helix edit application

    - Copying and pasting a block assigned to auto enable/bypass from the Helix editor may result in a “Cannot paste block†error message while the Helix hardware confirms the block was indeed pasted correctly. Workaround: Save the preset to re-sync the application.

     

     

    Helix Firmware 2.11 Release Notes (Dec 15, 2016)

     

    Bug Fixes

     

    - After importing a pre-2.10 preset that contains snapshots, EXP 2 could disappear from the expression pedal’s scribble strip LCD - FIXED

    - After importing a pre-2.10 preset with IR 127 or 128 loaded, corruption could occur - FIXED

    - Bypass Assign > Wait defaults to 300ms from the hardware and 100ms when selected within the Helix edit application - FIXED

    - General stability improvements

    - Other minor bug fixes and optimizations

     

    Known Issues

     

    - In very rare cases, corrupted presets containing a Volume/Pan > Volume Pedal block can cause volume to drop to 0%. In such cases, completely clear the Volume Pedal block and add again. If the same preset exhibits this behavior again, please contact Line 6 Customer Service and be ready to email us the raw preset so we can analyze it

    - Copying and pasting a block assigned to auto enable/bypass from the Helix editor may result in a “Cannot paste block†error message while the Helix hardware confirms the block was indeed pasted correctly. Workaround: Save the preset to re-sync the application.

    - EXP TOE cannot be bypass assigned using the LEARN option in Bypass Assign menu

     

     

    Helix Editor v2.10 Release Notes (Nov 22, 2016)

     

    New Features

     

    Auto Enable/Bypass blocks from EXP 1/2/3 and Variax Volume/Tone Knobs—Processing blocks (such as Wah, Pitch Wham, etc.) can now be enabled/bypassed by simply moving EXP 1, EXP 2, EXP 3, or Variax’s Volume or Tone knob. Click the Bypass Assign tab. From the source pulldown menu (normally reads “Noneâ€), select the desired switch. When selecting a continuous controller as a switch, Position and Wait sliders appear.

    - Bypass Assign > Position—Position determines the location in the Exp Pedal or Variax knob’s travel where the block is engaged. For example, if set to 1%, the block will turn off as soon as the pedal is moved to the heel position. If set to 99%, the block will only turn on when the pedal is moved to the toe position. To swap the on/off state regardless of position, click the small bypass icon above the selected block.

    Bypass Assign > Wait—Wait determines how long it takes after the Exp Pedal or Variax Knob is moved below the Position location before the block turns off. For example, you may not want the Wah to turn off instantly every time you hit the heel position during your big funk solo. Also, does your song really need a big funk solo?

    Block Bypass via MIDI—Individual processing blocks can now be enabled/bypassed via incoming MIDI CC messages. Click the Bypass Assign tab. Move the MIDI In slider to choose the desired MIDI CC. Incoming CC values 0-63 will turn the block off; values 64-127 will turn the block on. Note that some MIDI CCs are reserved for global functions and cannot be selected.

    Split > Y Balance parameters—The old Split > Y block sends both left and right signals to Paths A and B equally. 2.10 adds individual balance (pan) control of the signals sent to Path A and B.

    Snapshot Assign Shortcut—OPTION-click (Mac) or ALT-click (PC) any Home screen parameter to quickly assign its value to the Snapshots controller

    Unassign Controller Shortcut—SHIFT-OPTION-click (Mac) or SHIFT-ALT-click (PC) any Home screen parameter to instantly remove any controller assignment

    Exit Fullscreen Mode Shortcut—Press ESC to exit fullscreen mode

     

    Improvements/Changes

     

    - Added a Headroom parameter to Delay > Vintage Digital

    - Split > Y can now be bypassed; when bypassed, the block sends both left and right signals to both paths equally (like the old Split Y block)

    - Added forward slash [/] to list of characters for naming presets, setlists, snapshots, and Stomp mode custom labels

    - Bypass Assign tab has been relabeled “Switch†to better reflect all values

    - Tap Tempo no longer affects a preset’s dirty state

    - If a user fails to read and follow the update instructions, Helix will cause their car radio to only play polka death metal every Thursday from 1-3pm PST

     

    Bug Fixes

     

    - If many MIDI program change messages are received while the editor is importing or exporting data, the editor can freeze and Helix can crash - FIXED

    - Copying and pasting blocks on top of one another while in Pedal Edit mode can sometimes result in a blank scribble strip - FIXED

    - General stability improvements

    - Other minor bug fixes and optimizations

     

    Known Issues

     

    - When changing snapshots from the Helix application, block redraws may appear slower than normal. This does not affect actual snapshot selection

    - Bypass Assign > Wait defaults to 300ms from the hardware and 100ms when selected within the Helix edit application

    - Copying and pasting a block assigned to auto enable/bypass from the Helix editor may result in a “Cannot paste block†error message while the Helix hardware confirms the block was indeed pasted correctly. Workaround: Save the preset to re-sync the application.

     

     

    Helix Editor v2.11 Release Notes (Dec 15, 2016)

     

    Bug Fixes

     

    - After importing a pre-2.10 preset that contains snapshots, EXP 2 could disappear from the expression pedal’s scribble strip LCD - FIXED

    - After importing a pre-2.10 preset with IR 127 or 128 loaded, corruption could occur - FIXED

    - Bypass Assign > Wait defaults to 300ms from the hardware and 100ms when selected within the Helix edit application - FIXED

    - Bypass Assign > Custom Label And Switch LED parameters do not apply to EXP 1/2/3 and Variax Vol/Tone, yet were visible - FIXED

    - In rare cases when selecting a snapshot, the Input block could revert to None and become unresponsive - FIXED

    - If continuous bypass assignments exist in a preset containing multiple snapshot states, in rare cases, some parameters could not recall correctly - FIXED

    - General stability improvements

    - Other minor bug fixes and optimizations

     

    Known Issues

     

    - When changing snapshots from the Helix application, block redraws may appear slower than normal. This does not affect actual snapshot selection

    - Copying and pasting a block assigned to auto enable/bypass from the Helix editor may result in a “Cannot paste block†error message while the Helix hardware confirms the block was indeed pasted correctly. Workaround: Save the preset to re-sync the application

  5. Line 6 Forum Mods:

     

    Please create pinned threads at the top of the Helix Forums to prominently accumulate all newly added features and descriptions until a new User Guide PDF is released! Ideally, there should be one thread for newly added Firmware features, and another for newly added Editor features. These could be combined into one thread if clearly organized. Perhaps entitled something like: "Helix Features User Guide Addendum". The same language from the original 2.10 Release Notes posts could be copied and pasted. This should be added to on an ongoing basis.

     

    Note: This is not regarding the Editor and Firmware Installation Instructions!

     

    The features introduced in fw 2.10 that had been briefly described in the 2.10 firmware installation thread and editor installation thread are now gone (or very difficult to find)! The 2.11 fw inatallation instructions have replaced the prior feture descriptions.

     

    As no updated User Guide is being released until the next major update, the details of newly introduced features subsequent to 2.0 (i.e. not in the Rev D User Guide), should remain prominently posted in a thread atop these forums!

     

    A search of the Line 6 Knowledgebase for 2.10 features did not produce any obvious information!?

     

    I know various threads since 2.10 was introduced Nov 22 do contain discussions of these features, however, these are not evident (to new users) and are also not easy to find.

  6. As this is a wish list thread....

     

    Any one (or all) of Todd Sharp's JOAT Amps heads! With at least one of his dual voiced 2x12 cabs.

     

    The 20RT, sounds incredible. It has outstanding response and feel. Really easy to dial in spectacular sounds with the 5 position Attitude selector, Bite switch, and 6 position Hi Cut and Low Cut selectors.

  7. Probably best to, both, submit a Bug Report Support Ticket, and, to let this thread accumulate user responses.

     

    Line 6's likely and typical response will be to encourage all users to update to the current firmware (now 2.11).

     

    AFAIK, Line 6 does not publish a comprehensive listing of release notes detailing all of the general stabiliy improvements and miscellaneous bug fixes with each fw release. This creates a scenario where multiple users may be encountering odd fw behavior that Line 6 may or may not have already identified as a known issue or may have fixed without expressly publishing that it has been fixed.

     

    Additionally, as many users have posted reluctancies to embrace every fw update release due to various frustrations from legacy Preset conversion errors, IR pointer issues and stability concerns, Line 6 really needs to improve their software efforts to improve and stabilize the process. Let's hope we see this stride soon in early 2017.

  8. I have no prexisting Helix custom presets, 3rd party patches, nor IR headaches to be concerned with, so unless the problem has been remedied and is included amongst yesterday's: "General stability improvements" and "Other minor bug fixes and optimizations" I'm content to await the next significant update, learn more about using the Helix, hunt for more bugs and continue to submit use suggestions.

     

    Once another 2.11 user replies that the issue is no longer present, or, that it persists (alternatively, when Line 6 explicitly replies to the Support Ticket) I'll know, if I need to install 2.11.

     

    Until Line 6 releases an Android Updater for the Helix, installing an update is inconvenient. Particularly a one one-hundredth (2.10 -> 2.11) update, such as yesterday's, absent any new substantial features.

  9. Selecting Amp Models using the Rotary feature of the Helix Floor's Joystick, often involves a noticable hesitation and does not display the next or previous model item. Although the next detent is clearly felt, the rotary encoder's command to the Helix's OS seems to get lost (or ignored).

    This causes the displayed Model not to advance to the next or go back to the previous Model. Essentially, Helix seems to skip a beat during this rotary selection, clockwise or counter-clockwise.

    This happens regardless if the display is Model List display or Home Screen Amp Block selected (where the Model name appears on the lower portion of screen view). And, regardless if an Amp+Cab, Amp, or PreAmp Block type.

    I did notice that while in Amp Model List display, this often (but not only) occurs when the last item in each list screen's worth of models is reached.

    I posted this to one of the Support Forum threads recently and another user concurred that they had similar findings. (I have been unable to find that thread using the Forum's limited Search tools.)

    Although this is an intermittent symptom, it does occur frequently enough to be encountered at least once if not several times every Helix session. This happens on more than one preset. Each preset is only path 1 with looper block, amp+cab block, amp block, cab block, a stereo FX Rtn block, stereo Gain Block, and stereo FX Send.

    Helix not connected to a computer.

    Fw 2.10 installed.

    No pre 2.10 presets exist.

    HELIX is 3 wks new.

     

    Support Ticket Submitted.

  10. Confirmed I was using Templates 06A New Preset.

     

    This time, I created a new Preset using Templates New Preset 06B.

    Results are identical.

     

    All in Path 1

    Default Input Block (multi)

    Looper (mono) in Block pos 1 (bypassed)

    US Double Nrm Amp+Cab in Block pos 2 (enabled)

    US Double Nrm Amp in Block pos 3 (bypassed)

    2X12 Double C12N in Block pos 4 (bypassed)

     

    Save Preset using a custom name

     

    Select Input Block

    Press Amp Button

    Rotate Joystick one click (either direction).

    Originally depicted symptom presents.

  11. It might be fair to classify this as a bug as most effect parameters revert to their default when pressed. I can verify that this is the same behavior I see. The mic always reverts back to the first one in the list (57 dynamic) when the parameter knob is pressed.

    Along those lines I would love to see blocks keep their parameters in memory until you shifted focus to another block. In other words, if you are trying to select a distortion block, you modify its settings and then want to compare different models, each time you switch to a different distortion model the parameters change back to their defaults if you return to the one you just modified. For comparison I would prefer that the different distortions retain the settings I choose until I switch away from the block. This would be handy for most of the block categories. Right now the only way to do comparisons that have your own custom settings within a category is to set up multiple blocks and switch between them. Not always convenient or even possible if you are running low on DSP. This particularly applies to amplifier blocks where just a couple of them with a few effect blocks consume all the DSP. It would be great if at least the editor had this capability.

     I concur that, while auditioning different models of a block within a Preset, it would be advantageous to have a user's interim values persist as different block models are tried. This would be a nice enhancement! For my Fender Mustang amp's Fender's FUSE software lacks this feature. However, the exceptional 3rd party REMUDA Android App does remember a user's preferred FX settings parameters and amp settings in two ways. Both, when retrieving them from the menu and between amp profiles. This makes comparison auditiong between model much better. Helix should have the equivalent functionality on board, w/o requiring any Editior software.

    Agree w both the above. The Mesa EQ also doesn't reset correctly.

     Have not tried those knobs yet. Nonetheless, they should be consistent to reset to factory default. 

    Some parameters do not necessarily have a default, just reverts back to what is first on the list of choices.

    They should all act consistently unless another operational status or mode is active and blatantly obvious.
  12. Is the Cab Block's Mic selection knob 1's press to reset to default value function not behaving correctly? See symptom post here: http://line6.com/support/topic/24493-cab-blocks-knob-1-press-to-reset-behavoir/

     

    Update: The linked thread is active with other users also finding the same results, and also similar behavior with some another model's parameters (Mesa EQ)!

     

    If posting in this Bug thread is sufficient for Tech Support, then I won't open a Support Ticket. Otherwise, I certainly can open a Ticket.

     

    Does Tech Support harvest bugs from this thread?

     

    [Addendum: Support Ticket submitted: Thr, Dec 15]

×
×
  • Create New...