silverhead

The silence speaks volumes. I don’t know of anything current using that model of song building for audio. It reminded me of MIDI sequences commonly used in keyboards but applied to audio mostly for guitarists. I used to find it useful for sketching out song ideas, or for practicing solos over a background loop. I think it has been superseded by DAW technology and simple plugins today. Even the most basic DAW supports loops, usually with recording punch-in and punch-out including multiple layered takes, and there are plenty of simple, free drum plugins to provide the same features of RiffWorks and much more. The only other thing that Riffworks offered was the sequencing aspect allowing a building block approach. Copy and Paste in a DAW using multiple audio tracks simultaneously accomplishes the same thing within seconds. I don’t see a business model for a standalone product like RiffWorks today.

Don’t care to fight…..

Have you tried a factory reset or reinstalling the firmware? See manual for details. Since you’ve already backed up your custom presets you won’t lose anything.

Not that I’m aware of.

Umm… what about it?

Your computer may need an upgrade but since it’s running Win10 it’s not too old and may suffice. You’ll know after you get things set up. You will need an audio interface. They vary in price according to many things, an important one being the number of inputs and usb channels. If you want to record only one guitar at a time you need a 1-input interface. If you want to record guitar and vocals simultaneously you need a 2-input interface, preferably one of them being XLR and also including onboard phantom power if using a condenser mic. Do your research. I don’t know if there are audio interfaces that support expression pedals. Again, research. You mention HX Control so I assume you have the Helix Rack. HX control is not a generic foot controller; it works only with Helix Rack. So, no - you can’t use it directly into the audio interface or your computer. Since you own Helix Rack you are entitled to a discounted price on Helix Native, unless you are not the original owner of the Rack and a previous owner has used the discount.

A minor conceptual correction: the presets are not ‘automatically restored’; they were simply not deleted during the firmware update. They do, however, need to be rebuilt to ensure compatibility with the new firmware and they will be rebuilt automatically at the next system startup. So you can’t really skip what you call the auto update; it’s actually preset rebuilding and it’s necessary. You can interrupt and defer it (here’s where your prompt might be useful, but you don’t need it) by powering off the Helix at the point when the preset rebuilding starts. I do this because I know I will perform the factory reset and restore the backup file (except for the factory setlists). After that is complete I power down and restart the device to allow the preset rebuilding to happen only once, at a time of my choosing.

That’s correct. I added that part for clarification.

From the manual: … the Wah block is automatically controlled by EXP 1 and the Volume Pedal block is automatically controlled by EXP 2, and both the Wah and Volume Pedal blocks have their Bypass assigned to the on-board pedal’s Toe Switch. Doesn’t this default setup accomplish what you want? The toe switch toggles the one physical pedal between acting as EXP1 or EXP2 (as long as there is no external pedal connected). Pressing the toe switch alternately controls and activates/bypasses either the Wah or Vol block so that one or the other is always active and controlled by the pedal. Note: be careful with your Vol pedal setting. When the Vol is active and you sweep it to the toe position to activate the switch for Wah the Vol level will go to max. This means that whenever your Wah is active the Vol setting will be max, and it will begin at max again when you deactivate Wah and activate Vol. In my experience it’s best to configure your preset levels so that Vol is normally at max and use the pedal to temporarily lower the level if desired. If it’s not working for you please elaborate.

A firmware update does not overwrite any setlists/presets on the device. A factory reset does. If you’ve been in the habit (as many are) of ignoring the factory reset in past updates, or restoring the old factory presets after the Factory Reset as part of the Backup Restore process, you may well have factory setlists that are very old, including the Factory 1 and Factory 2 setlists. Check the bottom of this thread for the v3.8 factory stuff if you want them. Read my initial post in the thread for details.

Here ya go... FACTORY 1.TEMPLATES.hlshlsFACTORY 2.hlsUSER 4.hls ... maybe a glitch in attaching files? Ignore the no-name hls file if you see it...

Typically any greyed-out items mean there is insufficient DSP to add the selection. Helix Native has a Hardware Compatibility Mode parameter. Check to make sure it is set to OFF, meaning your DSP capacity is limited only by your computer’s power, not by the specified Helix device. Of course doing this would render your preset incompatible with the Helix device.

I suggest you open a support ticket to get these questions answered by Line 6 directly. Most users here won't have the ability, or perhaps the inclination, to do all the testing required to answer. And even if they do the answer might not be applicable to your specific PC environment. If you act on the recommendation of Line 6 support they will take responsibility for anything that might go wrong. If you act on the advice of a user here, however well intentioned, well, ....

In a former life I managed a team of software developers in a large telecommunications company. There was a rigorous software development process including software library management tools ensuring development integrity and regression testing. I had to fire employees who considered software they developed as their own personal property and refused to follow the development process. My favourite refrain? “I developed and tested this myself. I can assure you it’s bug-free and doesn’t need further testing!” The last person you want testing software is the person who developed it. They’ve already thought of and handled everything they think could be problematic. It’s the things they haven’t thought of that will catch them, but someone else will think of those things and test for them.

You are assuming that the same level of development resources were applied in both cases. That’s not true. Line 6 has reallocated development resources to the next generation flagship product. Otherwise they’re planning to be out of business soon, which I highly doubt.

That indicates there is insufficient DSP remaining in the preset to load those amps. Try starting with a New Preset (empty). Are those amps still greyed out?

Mark your calendar ... in pencil.

I believe those are the preset names used in the demo. When you click on those names you see a description of the preset, including the underlying amp and relevant FX blocks.

It’s up to you. You can just place it in-line with your other pedals as you’ve shown or you can use the 4CM assuming your amp has an FX loop. The advantage of the 4CM is that you can place HX FX blocks and your physical pedals (e.g. reverb, delay) after your preamp in the signal chain. Some people prefer to place time based FX after the preamp and before the cab/speaker; 4CM lets you do that.

I assume that by ‘aggregate’ you mean the ability to use both devices simultaneously as the audio input and/or output devices. If so I’m pretty sure (less than 100% confidence) the answer is HX Stomp, as an audio interface for recording purposes, uses the ASIO protocol which requires that the same audio device, and only that device, be used as both input and output device. Hence it won’t work with the Scarlett. This limitation is imposed by the ASIO protocol and the HX Stomp is fully compliant with it. You mention that Asio4All doesn’t work. I’m not surprised. It seems to work for some people in some PC configurations but generally it is known to cause problems with Line 6 devices. That’s because Asio4All is not fully compliant with the ASIO protocol, part.y because it attempts to contravene the protocol by supporting more than one device. Whether or not you consider this ‘firm information’ is up to you I guess. As I said, not 100% certain because I’ve heard reports of asio4all working for some. If it’s not working for you now I don’t think you will get it working.

In the forums it’s included in the Helix area. I’ve moved your thread there.

Are you speaking about a difference in the intervals of value changes when rotating the knobs slowly vs. rapidly? If so, that’s a designed feature, not an issue. By design (and in response to user feature requests) parameter values change in bigger jumps when you rotate the knob quickly. You need to rotate it more slowly to make the intervals smaller. If that’s not what you’re talking about please elaborate.

Typically you would adjust this in your computer. Lower the volume there. You could also reduce the USB 1/2 Trim setting in Global Settings -> Ins/Outs.

Aah, yes…. but the gap between your initial post to start this thread and your most recent post hours ago is 100 days. So, well, there ya go. All sorted now. Start holding your breath!