HonestOpinion

Btw, for newer users of snapshots and in the interest of beating the details on this setting into the ground(Global Settings --> 'Preferences' --> 'Snapshot Edits'), it not only impacts how the snapshots behave while performing but also while editing a preset. If you have it set to "Discard" it is not a bad idea to save each snapshot before moving on to design the next one. Otherwise it is pretty easy to inadvertently lose the snapshots settings when you start switching around to edit other snapshots. With it is set to "Recall" you can save just once when you have completed editing the entire preset.

21 hours ago, jeffreyke said:

Oh sorry - new to this.  Thanks.  Here you do (I hope).  Thanks again.

Morgan + D&R.hlx 14.7 kB · 1 download

Maybe I am unsure of exactly what behavior you are looking for, if so please let me know. Loaded up and examined your preset. The instructions from my prior post should work for you, e.g. Set Global Settings --> 'Preferences' --> 'Snapshot Edits' = "Recall".   When I test your preset it works as it is, unmodified by me, to retain the last selected state of both the parameter settings and the bypass state(in the case of FS2 with its two assigned delay blocks)across snapshot changes as long as I have the global setting set to "Recall" as described. When I click through the other snapshots and return to the one I made a change in, it is exactly as I left it. Disclaimer: I have the Helix not the Stomp.

Btw, that is a fairly slick use of the Stomp for a new user. If I could make one suggestion. Rather than having your multiple footswitch assignments read "Multiple(*) which is rather nebulous, take advantage of the 'Customize' button under either the 'Bypass Assign' or 'Command Center' menus on the device or click the 'Bypass/Controller Assign' tab in HX Edit and use the 'Customize' field there to rename them to something more meaningful.  Maybe you just didn't get around to it yet.

If the suggestion in the first paragraph does not work for you I will assume much like the case of the OP that I have yet to identify some other global setting that is set on my Helix that is required for the proper behavior, or that the Stomp is working differently than the Helix on this feature. Makes me wonder which HX device the OP is using as well? The only other global setting I know of that can disrupt the behavior described above is if you set Global Settings --> Preferences --> 'Snapshot Reselect' = "Toggle Previous" (don't do that). Another possibility is that because I am using the Helix's footswitches to switch snapshots rather than an external MIDI controller as you are that the Helix is changing snapshots somehow differently. Seems unlikely but I suppose it is possible. I would need to maybe have both a Helix and a Stomp and sniff the MIDI commands on the PC with something like MIDI-OX to be sure that they are operating identically; assuming all the internal messages pass through.

Let me know if just changing the setting above works for you.

25 minutes ago, jeffreyke said:

Hello,  here is my preset that I'm having issues with.  You will see that if you engage FS1 on the stomp it will turn on the Dual Pitch and if you switch between snapshots it will stay on, and if you turn off on any of the snapshots it will turn off on all of them.  If you then look at FS2 and FS3 these do not behave in the same way.  Only logic I can come up with is that its because FS2 and FS3 are parameter changes rather than on/off.  Any help would be great, thank you for helping and looking into this.

HX Stomp Snapshot issue.hls 50.97 kB · 0 downloads

Looks like you exported your entire setlist. Can you upload just the preset. You can right click on the preset in HX Edit and click 'Export'.

On 1/22/2021 at 7:28 PM, Hey_Joe said:

In my opinion it would be a good thing to have the Powercab Level indicator show up in PowerCab Edit.

This would be very helpful (at least to me) when dialing in a preset to see the  GREEN  and  YELLOW  colored LED and see if and when it clips into  RED  from my listening distance (computer to amp placement in the room).

Another good thing about this would be, to be able to see the difference between the  GREEN  to  YELLOW  signal LEDs. I don't know about you, but on the amp, I have trouble discerning the difference between the GREEN and YELLOW LED (BTW - I am not color blind).

Is this doable or is it like the reason L6 can't get a read out code for the tuner written for HX Edit? As I recall the old POD EDIT program (not Gearbox) had a tuner in the GUI - it was doable then.

 

I put it on Ideascale

https://line6.ideascale.com/a/dtd/Powercab-Signal-LED-Level-indicator-to-show-up-in-PowerCab-Edit/1009166-23508

 

 

I would actually find it even more helpful for this indicator to show up in HX Edit and best of all would be on the Helix itself although that might chew up some valuable DSP or memory.  PowerCab Edit would be helpful though if that is the only place feasible to make it happen.  Voted btw!

On 3/2/2021 at 2:13 PM, The_HairyDangler said:

Hi,

just wondering, when building a preset with both powercab and helix, what is the better approach with using high and low cut.  Use the high/low eq in the helix or use the same parameters in the powercab? I’m assuming using both would be redundant?

The Helix global EQ doesn't work across the L6 Link connection as stated above but the other Helix EQ blocks within a preset do as well as the Powercab specific high/low cuts that you can select from the Helix or HX Edit under the Powercab tab. Ultimately use your ears and decide where you prefer the cuts do be done. The various EQ blocks available within the Helix as well as the cuts available on the Powercab can have different curves so you may find you prefer one method over another.

On 2/26/2021 at 12:37 PM, PaulTBaker said:

ok, that explains things.  I have the same (sort of) problem.  On some presets, I have amp vol and drive parameters tied to a stomp button(not snapshot).  The amp has the snapshot bypass = off.  When I change snapshots, the amp drive/vol change back to whatever they were the last time I was in the snapshot.

 

That does explain things, however, I don't like it :)

 

On 2/26/2021 at 1:54 PM, HonestOpinion said:

 

Another approach is to leverage the 'Snapshot Edit' parameter in global settings. Since your preferred behavior is to always have the delay enabled do the following. Do NOT set FS3 to always have Bypass=Off. Instead assign the Delay block's 'Time' parameter to FS3 as you have been with the Min/Max set to your preferred values(200ms & 600ms). Now go set Global Settings --> 'Preferences' --> 'Snapshot Edits' = "Recall".  Make sure you save the preset with the delay block active in all snapshots.

 

Now when you switch snapshots whatever 'Time' value you last selected for your delay with FS3 for that snapshot will be remembered; even if you switch snapshots, change the 'Time' value in the new snapshot, and then switch back to your last one. I have attached a simple sample preset below that should be behaving the way you would like it to if I understood your post correctly.

 

You can check out the assignments once you have loaded the attached sample preset. Select the delay block and 'Bypass/Controller Assign' tab in HX Edit and look at the left hand column to see the assignments for the delay. There should only be the one assignment for the delay 'Time' parameter on FS3 with your Min value set to 200 and your Max value set to 600.  If for some reason your 'Bypass' parameter gets assigned to FS3 as well just use the 'Bypass/Controller Assign' tab to clear it.  You can also do this by right clicking on the Delay block and selecting "None" for the 'Bypass Assign' entry in the pulldown menu. Make sure you have all your snapshots saved with the delay block active.

Delay Example.hlx 8.83 kB · 2 downloads

Have you tried setting things up the way I suggest above? The key is that if you want the snapshot to always have the block in the state you last left it in, no matter how many snapshots you roll through, set Global Settings --> 'Preferences' --> 'Snapshot Edits' = "Recall".  One note, maybe obvious but worth mentioning, once you change presets(not snapshots), all snapshots values in that preset will revert to the state they were saved in.

If you want the snapshot to always revert to a specific state when you go back to it, set Global Settings --> 'Preferences' --> 'Snapshot Edits' = "Discard".  If you use this global setting because you prefer this behavior make sure you save each snapshot in the state you want when you are creating the preset.

15 hours ago, DewyGoodwood said:

Thanks for responses folks. Sounds like this behavior is by design. Unfortunate but I guess it makes sense.

 

Thanks for the suggestion HonestOpinion but no joy. I still get the same results.

 

I found a workaround by adding a second delay block. I have one with time set at 70 and the other with time set at 200. I assign both to the same footswitch so pressing turns one on and the other off. That way I can have the snapshots ignore the bypass and get the results I want. Takes a little more DSP but it works.

 

Cheers.

14 hours ago, HonestOpinion said:

 

Glad you found a workaround that works for you but that should not be necessary. If this did not work with the preset I uploaded it must be related to some Global Setting we have not hit upon. It works perfectly on my end. Did you check the assignments tab as I suggested to make sure your bypass state was not also assigned to that footswitch? What did my preset do specifically when you uploaded it? Might also help if you upload one of your presets that was not working as expected. Would love to get to the bottom of this.

 

Btw, are you on the 3.0.1 firmware?

I should also ask, what HX device are you using?

8 hours ago, jeffreyke said:

Sorry it I’m piggybacking on someone else’s questions. Seems like we have same issue. Yes I’m using 3.0.1. I will download your patch and let u know how it works for me. Happy to share my preset with you if I can’t get it sorted. Thanks for your support. Will be back in touch later on. 

Would be happy to look at it although with the added element of you using MIDI for switching your issue may be different than the OPs.

1 hour ago, DewyGoodwood said:

Thanks for responses folks. Sounds like this behavior is by design. Unfortunate but I guess it makes sense.

 

Thanks for the suggestion HonestOpinion but no joy. I still get the same results.

 

I found a workaround by adding a second delay block. I have one with time set at 70 and the other with time set at 200. I assign both to the same footswitch so pressing turns one on and the other off. That way I can have the snapshots ignore the bypass and get the results I want. Takes a little more DSP but it works.

 

Cheers.

Glad you found a workaround that works for you but that should not be necessary. If this did not work with the preset I uploaded it must be related to some Global Setting we have not hit upon. It works perfectly on my end. Did you check the assignments tab as I suggested to make sure your bypass state was not also assigned to that footswitch? What did my preset do specifically when you uploaded it? Might also help if you upload one of your presets that was not working as expected. Would love to get to the bottom of this.

Btw, are you on the 3.0.1 firmware?

16 hours ago, rd2rk said:

HF Trim - Page 18 of the PC Manual, third item down. It controls the Output Level of the HF Driver.

In PC Edit you'll find it on the SYSTEM Tab, right below the Input 1/2 Gain controls.

It doesn't SEEM to affect the Clip light (doesn't add enough gain?), which is part of the reason I wonder why the FRFR and Speaker levels DO affect the Clip light.

I think it's a bug, and the PC's internal level settings should NOT affect the clip light.

But, again, it could be an engineering thing, and until somebody technical at L6 checks in, we're all just guessing.

 

As for Jason's video, since the Input 1/2 Gain controls only affect the analog inputs (as far as I can tell), and he says at the beginning that he's using L6 Link, I don't know why he would even mention those. I don't have time to re-watch the whole thing to find that spot, but if he says then that he's using XLR, he's contradicting himself. Maybe he used different methods in different parts of the video? Anyhow, the XLRs are how I bring in a VST, and using a VST or an HXS or anything that doesn't have L6 Link, the Input 1/2 Gain controls are the ONLY way (EDIT: except for the FRFR/Speaker Level) to set the clip indicator (isn't Input Gain what an Input Clip indicator monitors?), so I have no clue what he's talking about.

Yep, was aware of the HF Trim but as noted that does not control input level, just HF Driver gain.

I think what Jason was saying was that when he tested adjusting the "Input 1/2 Gain" levels on the PC+ he was connected by 1/4" and/or XLR, and that it introduced higher S/N levels. That testing was not done during the video. At some point he states that the video was made using L6 Link. So essentially his "Input 1/2 Gain" level adjustment testing was done prior to the video with a different connection type(1/4" or XLR).  He does not actually use "Input 1/2 Gain" for his recommended adjustments to gain stage settings in the video.  Just shows them when he describes his testing prior to the video.

So, still an open question on where or if there is an Input adjustment on the PowerCab+ that can change the levels showing in the level/clip indicator when connected via L6 Link?  As far as I know there isn't one. If someone knows better please educate me.

2 hours ago, rd2rk said:

Well, there is an Input Trim Control, it's on the System Tab in PC Edit, and in the System settings on the Powercab itself (press and hold the HOME button). It can be controlled via MIDI PC#5, and the settings go from OFF (PC#5 Value 0) to +12db (Value 127) with 113 being 0db - not 100 per the PC Manual.

 

My problem with the implementation is that it's about the only Global PC setting you can't access on Helix itself from the GLOBAL Tab on the Powercab dialog.

If you are referring to the "Input 1/2 Gain" controls they may modify the input sensitivity with an XLR connection but they don't impact the PC+ input level/clip indicator light at all with an L6 Link connection. At least as far as I can tell. Is there some other input level/trim control setting I am unaware of?  Maybe I am misremembering but isn't this why, for example, Jason Sadites has that video on Powercab gain staging which has you boosting your signal at the Output block on the Helix or some other block rather than just turning up an input level on the Powcab?  Either way I would still love to have a simple level/trim knob to get my signal peaking in yellow with perhaps an infrequent red.

Btw, I agree that including those level controls on the Powercab tab in HX Edit would be most useful; but only useful for L6 Link connections if they applied to a Powercab input level control that worked with L6 Link.

Edit: Just watched a bit of Jason's video again and he mentioned the primary reason he doesn't like using the "Input 1/2 Gain" for increasing levels is that they also increase the S/N ratio.  But... he also mentions in passing that at least for that part of his testing he was using an XLR or 1/4"  connection although later on in the video his HX Edit screen is showing the Powercab tab and he is making changes on it. He also describes his connection for the duration of the video as being via L6 Link.  So I am still left wondering if there is a control on the Powercab+ for changing its input level when using the L6 Link such that it affects the level/clip indicator?

2 hours ago, rd2rk said:

 

Yes. It makes NO sense to me that there would be any other way to affect an INPUT clip indicator other than the OUTPUT level of the device that's feeding it. The SPEAKER level and IR level in the Powercab are OUTPUT levels within the Powercab. Makes no sense at all, and I think it's a bug. But, as you say, that's a L6 engineering problem, and

they're not talking about the Powercab AT ALL - not here, not over on TGP - no feedback from L6 at all where Powercab is concerned. Scary.

 

 

 

I agree, it has always seemed like a grave omission to not include an input trim control on the Powercab, particularly on the Powercab+. As has been stated here though I suspect that this is a deliberate design choice to mandate that whatever the optimal signal is for the PC+ be provided by whatever source is feeding the PC+. Simplifies things theoretically but actually complicates them in the real world.

The L6 Link adds and simplifies remote control of the PC+. Using the L6 Link connection is the preferred and most powerful way to use a Powercab+ when you own an HX device. L6''s no input trim design decision then proceeds to precipitate a whole lot of unnecessary and major hassle adjusting output levels on multiple presets on HX devices.  Even if you are using equipment without an L6 Link connection you still have to adjust your source signal to get the right level arriving at the Powercab+.

An input trim knob would have made life so much simpler.  Seems like the perfect(optimal source output signal) may have been the enemy of the better(adjust input sensitivity with trim knob on the Powercab+) in this case although there may have been some other reason that drove this decision. 

On 2/28/2021 at 5:24 PM, ichasedx said:

Using a Helix floor and PC+...are there any indicators available on the Helix that show then clipping is occurring? Something that mimics the LED on top of the PC+?

Thanks,

Mike

 

On 2/28/2021 at 6:48 PM, waymda said:

 

...

 

Finding a way of monitoring this without sitting on top of the PC+ was somethign I played with this weekend. In the end I took the analog send from the PC+ and calibrated the meters on my desk so I know when they hit the red so is the PC+. Took a bit of time to adjust the input trim to and understand the bits that impacted but should be worth it.

 

...

I have a couple of amps/cabs with the controls on top, most notably a Vox and Powercab.  While marginally "novel", top mounted controls have always seemed like a poor idea to me on any amp/cab. The only way they are useful is if you are standing directly over the amp and the amp is flat on the floor(perpendicular). The problem being that if you are performing this is probably the worst position for an amp which you want either leaned/kicked back if on the floor or hoisted up on a stand.  Either one of those more ideal positions makes it difficult to view and use top mounted controls.  If you are at home practicing there may be a good chance you are seated and again the top mounted controls and indicators are in a less than ideal viewing position unless you practice with your amp next to and pointing at your knees.  #KeepEmOnTheFront. Rant over.

Connecting via Wi-Fi is a great solution and I hope it is included in the next generation. Just as long as they include Ethernet and USB connectivity as well. Not exactly analogous but I can attest that having run sound on mixing boards with Wi-Fi you want at least the option to have a hard wired connection available for when the Wi-Fi decides to drop or your tablet starts misbehaving right before a mic starts feeding back.

Getting past OS and USB issues would be a big win although Wi-Fi doesn't guarantee side-stepping problems with new versions of operating systems. Soundcraft mixing boards like the "Ui24r" found an interesting way to circumvent OS issues by having their remote app run within a browser using Wi-Fi. Don't know whether or not that approach would transfer data quickly enough to serve as an editor/interface for HX devices.

On 1/30/2021 at 12:31 PM, rd2rk said:

 

 

"Amp In The Room" (AITR)

Most people who get hung up on this are actually saying that they prefer the sound of their tube amps over modelers.

Powercab is an AMP. If you play it in a room, that's AITR.

As codamedia said, it's just a different sounding amp.

 

 

...

 

The whole Helix is like a studio recording(true to some extent) vs. AITR sound is truly the discussion that keeps on giving. The AITR sound may be tube amps as you point out or can also be the old familiar and limited frequency range and response of the typical guitar cab. Most guitarists are aware that guitar cabs do not traditionally have high frequency drivers as do PowerCabs or many other FRFR offerings.

If you are used to listening to your sound live with a PA, unless you use IEMs, then you really get used to a PA+Amp in the room sound(PAITR). A combination of a guitar cab behind you and the reflected sound of the PA off the venue's walls, floor and ceiling as well as peripheral projection from the PA's speakers with the possible addition of a wedge monitor in front of you as well.  Never hear anyone around here calling for PAITR though. Really just wanted an acronym I could call my own :-) 

When you think about it a Helix used with a guitar cab(without a high frequency driver) behind you with a separate modeled cab/mic feed to the PA can be pretty indistinguishable when set up properly from the old traditional tube amp setups miked to the PA.  Conversely the benefit of using an FRFR as your backline monitor is that you get a better sense of what the audience is hearing but lose more of the traditional AITR sound.  You can really go down the rabbit hole with this stuff. Ultimately it is a matter of taste and what "feels" right to you.

If it were me I would probably return the Katana. Hard to beat the small footprint and amazing capability of the HX Stomp and a pair of headphones for living room playing. You could always pick up a Headrush FRFR-108 later if you miss having a cab. Those things are also really small, inexpensive, and create a fairly big sound.

If it were not for the fact that you were not happy with your Katana I would also say you might enjoy the Positive Grid Spark amp. However, if you are not satisfied with the Katana's sound I doubt the Spark will cut it for you. It is a very capable practice amp though, sounds good, lots of features to explore, and small.

On 3/3/2021 at 6:00 PM, raww said:

I tried several settings. But every time I click on an element in HX Edit it jumps to process view

I have the Helix Floor not the LT. Maybe there is a setting for LT users that I am unaware of. This does not happen on the Helix when I use HX Edit. All of the stomp assignments stay visible. In my case on the bottom row of scribble strips as I reserve the top row for snapshots. Perhaps there is another setting available for LT users as the LT utilizes the screen to display the stomps. Little help from a LT user? You can always restore just your global settings from a prior backup using HX Edit's 'Restore From Backup' option on the 'File' menu.  Just uncheck everything else.

Btw, just in the spirit of being thorough when you click 'Help' --> 'About HX Edit' on the editor's menu do you see version 3.0.1 at the top & bottom of the splash screen?

18 hours ago, raww said:

After some update I had this issue. When using HX Edit the helix jumps from stomp effects on/off to edit mode (viewing the two process lanes). Somehow I did solve this last time

 

Now I have this again.

 

What setting do I have to change to keep just my assigned effect buttons visible on my Helix LT?

One thing it could be is your Global Settings --> Footswitches --> 'Preset Mode Switches' or 'Snapshot Mode Switches' setting.

On 3/2/2021 at 2:08 PM, tragomago said:

Yes.. i think it is solved.

Now it freezes recalling a deluxe phaser favorite preset.

Try deleting the phaser favorite and that preset and recreating.

When it comes to possible extinction level events this one comes in towards the bottom of my list of concerns, whether it is imminent or not, which I doubt.

1 hour ago, PierM said:

For us non-native, wha the hell is EOL?

54 minutes ago, scotterp said:

End Of Life. :)

Or alternately a nocturnal predatory bird with a "facial disk" known for a call that sounds like "Who" (or reportedly "Dr. Who" or even Roger Daltrey if you live in Britain)  :-)

20 hours ago, cziebold said:

... However what about us Variax users? What---no Variax input on the XL?!! The 'hit' on the regular stomp on Variax was that it was too small and not powerful enough for a Variax input. ...

Agree, including a Variax and maybe even an L6 Link port would have been a great use of the extra back panel real estate and possibly allowed some people to see this as an admittedly different but much less expensive and similarly compact alternative to the Quad Cortex that allowed them to leverage their PowerCab or Variax. Have to say though, this is a very cool addition to the HX line.

On 3/3/2021 at 8:38 AM, brue58ski said:

 

Ooooo. Thank you for that shortcut tip. Is there a list of shortcuts somewhere? I couldn't find one in the manual. One thing I do not like about things these days is more and more products will have functions that aren't well documented at all. It seems like it takes someone to accidentally discover something.

HX Edit has a large number of keyboard shortcuts available and all listed together. If you go to HX Edit's menu and select 'Help' --> 'HX Edit Application Pilot's Guide' you will find a list of shortcuts starting on page 65. It is extensive!

For shortcuts on the device they are not gathered together in one place. In the Helix manual for example, they appear instead within gray boxes scattered throughout the doc.  I find the easiest way to scan them all quickly is to use the find function(Ctrl-F in Windows) and search on the keyword "Shortcut". Maybe someone will cut & paste them all into a condensed single document at some point.

The helixhelp site has some useful tips:

https://helixhelp.com/tips

Old but a few tips in here  - https://media.americanmusical.com/ItemFiles/Manual/LIN_HELIXFB_2shortcuts.pdf

5 hours ago, tjbassoon said:

Well, that's helpful, but more helpful for me is finding out from a comment there that press and turn a parameter sets that parameter to snapshots! That's mostly all I really want to do anyway: when I'm in a snapshot, change the parameter and have it stick. I just need to press it down while I turn! Awesome!

The press and turn the knob thing has been part of snapshots pretty much since they first appeared. Definitely a great method if you are working directly on your device. Discovered this one too for HX Edit. Shortcut: In HX Edit, highlight any parameter by clicking on its value or title and hit the letter "S" once and it will be assigned to snapshots. Hit "S" a second time and it will unassign that parameter from snapshots.  Handy shortcut and I find it faster than right-clicking the parameter and selecting 'Snapshot' from the bottom of the pulldown(should be at the first or second position in the pulldown IMHO).

Occurs to me that if they added a Shift-Select and Ctrl-Select ability to HX Edit such that you could select multiple parameters on a block at one time, assigning them to snapshots could be done in a single keystroke.

3 hours ago, brue58ski said:

 

Here's an ideascale I added awhile ago which addresses this I think. Vote it up!!

 

https://line6.ideascale.com/a/dtd/Snapshots-one-click-multi-parameter-assignment/869909-23508

Voted!