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

rd2rk

Members
  • Posts

    7,490
  • Joined

  • Last visited

  • Days Won

    366

Everything posted by rd2rk

  1. Is it that way in EVERY preset? If not, maybe that preset is corrupt and you need to recreate it. If it's the same in ALL presets, then it sounds like you've done all that you can do. Open a support ticket.
  2. IME putting an OD/DISTORTION pedal in the FX Loop tends to boost the small bit of noise that exists in the FX Loop. These pedals are meant to be placed between the guitar and amp and work best with Helix when placed between the guitar and Helix. YMMV.
  3. I must be misunderstanding your workflow, because you cannot, nor have you ever been able to, save a single snapshot. Snapshots are saved by saving the preset, which saves ALL of the snapshots in whatever state they're in. Snapshot Edits=RECALL prevents the loss of your changes between snapshot tweaks, WITHOUT saving the preset, unless you change presets WITHOUT saving, in which case all changes are lost, so maybe that's what you mean? I must be misunderstanding because I know that you're no rookie at this, you've been at it a long time and you're a performing PRO. Whatever, the important thing is that your workflow works for YOU, so ROCK ON!
  4. Helix doesn't SAVE a Snapshot until you SAVE the preset. I don't recall how it worked in 3.15. I seem to remember that the FUNCTION of a FS was always set the same in all Snapshots. Didn't it used to set all Snapshot BEHAVIORS for a switch the same until you SAVED the preset? IOW - set a FS to HX Snapshots FUNCTION and the BEHAVIOR to go to a different Snapshot and it set that FS to THAT behavior in all Snapshots? I like the way it works now, as I would rather set the FS FUNCTION's BEHAVIOR in each snapshot per my needs. I could be mis-remembering how it worked previously, I'm not sure what I had for dinner last night... :-P Only ONE save is necessary if you have Snapshot Edits set to RECALL.
  5. SÌ. Imposta il comando istantaneo (fulmine) su Bank/Program. Imposta MIDI CHANNEL sullo stesso canale del ToneX. Impostare CC00 su 0 (PC# 0-127 nel Banco 1) o 1 (PC# 0-21 corrispondono ai preset 128-149 nel Banco 2). Tieni presente che mentre il ToneX SW numera i BANCHI come 0-49 A-B-C, sto usando i MIDI BANK n. 0 e 1. Usa lo stesso Instant Command in ogni istantanea, impostato sulla destinazione ToneX desiderata. Yes. Set the Instant Command (lightning bolt) to Bank/Program. Set MIDI CHANNEL to the same channel as ToneX. Set CC00 to 0 (PC#s 0-127 in Bank 1) or 1 (PC#s 0-21 correspond to presets 128-149 in Bank 2). Note that while ToneX SW numbers BANKS as 0-49 A-B-C, I'm using the MIDI BANK #s 0 and 1. Use the same Instant Command in each Snapshot, set to the desired ToneX destination.
  6. To expand on what @theElevatorssaid - When you assign a FS to a function, HX Snapshot in this case, that FS retains that function in ALL snapshots. If you the assign that FS to go to a specific snapshot all of the other snapshots retain the DEFAULT - in this case, NEXT, which is the same as Snapshot UP. So, when you get to the destination snapshot from Snapshot 1, the FS assignment in that snapshot is NEXT by default. You have to assign a behavior for that FS in EVERY snapshot. IOW - if FS1 in SS1 calls SS5, FS1 in SS5 will be NEXT unless you assign it to do something else, say, go to SS3. When a function in a SS is assigned to a FS, that FS must be assigned to a specific behavior in EVERY SS else those Snapshots default to NEXT.
  7. Maybe it's time to contact support?
  8. In Global Settings>Ins/Outs you can set the Sends/Returns to either INSTRUMENT (1M) or LINE. What you lose is the AUTO INPUT-Z - if the device you're using has that. When asking for help on this forum, it's helpful to specify which device you're using.
  9. Hard to say, since you didn't specify which device you're using...
  10. I'm not sure what you're trying to accomplish. The following assumes that the Catalyst is the only audio output device. For recording into a DAW (using the Catalyst as interface), I leave the MS Sound Panel settings to the internal sound card on both recording and playback. This allows me to stream backing tracks from the computer to the Catalyst AUX input and still use the computer's internal mic for whatever. In my DAW I set the ASIO Driver (DL from Line6) to the Catalyst. I set one track to USB 1 or 1/2 for processed signal, and another track to 3 or 3/4 for DI signal. Track/Record Monitor Switch set to AUTO. This prevents the DAW signal from mixing a delayed signal with the LIVE signal when recording. Unless I'm misunderstanding your goal, this should fix it.
  11. I have no noises with my setup, simple RCA SPDIF as described. I don't even really know what "word clock" is for. I just looked it up: Word clock and MIDI interfaces. - InSync (sweetwater.com) Seems like more stable, less strain on CPU. Like, if you're depending on controlling Helix from DAW for live performance it would be useful? It does seem like it's an either/or thing - BNC vs RCA, so maybe using both is causing your noise problem? Just spitballing here while we wait for someone who knows what they're talking about to chime in!
  12. If FOOTSWITCHES>STOMP SELECT is set to TOUCH or BOTH, then you should be able to select a Block, touch a FS and the screen should show the option to assign the FS to Bypass that Block. In HX Edit, RIGHT CLICK any Block and use BYPASS ASSIGN from the dropdown to select how to control it.
  13. Helix Floor and Scarlett 18i20 - SPDIF works fine. Simple RCA SPDIF cable connections. Internal, 48k. Helix can be set to send or receive MIDI Clock. Not something I normally use, but with RECEIVE MIDI CLOCK set to AUTO I have synced it to follow tempo from Reaper. I also used it to control DAW Tempo with EZDrummer. Both of these were just experiments to see if it worked and TBH, I only did it once, long ago. Only noises I ever got with this rig was when I tried to use a really low buffer setting (<64) when using Helix with plugins. Need a better computer to go <64, but 7.6ms latency works fine for me (Scarlett as AI, Helix as AI 12.6ms). That's about all I know, like I said, not something I really use.
  14. If the affected block's parameters are being controlled by the replaced block, its parameters could be reverting to defaults. IDK for sure, but something to consider. If that is what's happening, you should express your opinion on Ideascale. If you still can't track it down, that's weird, contact support.
  15. If the copy/paste is replacing an existing block which has SS/FS settings that affect parameters in other blocks, that might be the issue. Otherwise, if it's just adding a block, that should not cause an issue.
  16. The BSOD in Windows indicates a computer issue. Start there. Make sure you've got the PC fully updated and running properly under the latest version of Windows. I haven't suffered a BSOD since Win10. Do a thorough memory integrity check, as the BSOD is often caused by bad physical memory. If you get it fixed, remember computers 101 - back up early, back up often!
  17. If you're in the US, call support. If not, open a support ticket. It sounds to me like maybe a cable has come loose inside.
  18. I'd need to see the actual preset. Export it and attach it to your reply.
  19. No. You could make a preset template with a FS that went to your "Talk" preset, but there's no way to store the current preset # for the return trip. PREV and NEXT only move to the previous or next preset in the setlist. There are MIDI controllers that can do that, just not Helix.
  20. It's actually labelled that way on the HXS, but not on the HXFX. Does it say that somewhere in the manual? Just wondering, hate to spread misinformation...
  21. Turn the attenuator full counter-clockwise to the MUTE position. Keep in mind that XLR output volume is controlled by the CHANNEL Level, not the MASTER. If you want to use a custom IR Loader in your DAW you should load the Catalyst Edit program and in the speaker section, turn the speaker emulation OFF. This (or using other FX in your DAW) is really the only time you'd want to monitor through your DAW, as doing that adds latency to the signal.
  22. From the HXFX Manual: 15. OUTPUT L/MONO, RIGHT Use unbalanced 1/4" TS cables to connect to your guitar amp or other pedals. When connecting to a mono pedal or single amp, connect only the L/MONO 1/4" jack. In your situation you might go with the HXFX for the extra switches and get a DI Box for FOH. OTOH, IDK what price/availabilty is like in your country. A quality DI Box can add quite a bit to the total cost. A good alternative might be the HXSXL. It has balanced outs for FOH and one more switch. Two more could be added for much less than a DI Box. The Helix amps will provide you backup in case the ToneX fails. Also consider, and this is just my opinion - I have both the full size ToneX and the Helix Floor. I have tried tone matching (I use Amalgam captures exclusively) and find nothing outstandingly superior about the ToneX sound OR feel vs Helix amps, and much prefer being able to use the amps' modeled tone stacks vs the ToneX EQ and hunting for "the perfect capture". The IR rabbit hole is bad enough. My main reason for keeping the ToneX remains what it was when I bought it - being able to try amps I'll never get to try (or even SEE) ITRW.
  23. Agreed, good catch!. Setting the SEND to LINE level could overdrive the amp's Input, and if the amp's SEND is Instrument level and the Helix RETURN is set to LINE, it might be returning a lower signal. The Variax is a separate Input, so that could be where the problem lies. I don't have either a Variax or a DeVille to test but setting the FX Loop to Instrument level would be a good thing to try if you haven't already. Also, while it requires an extra block, you can always use a SEND set to Instrument and a RETURN set to Line. Just something else to try.
  24. Not necessarily. Unfortunately, there's no standard for FX Loops. I assume that they've tried both settings.
×
×
  • Create New...