silverhead

Just for fun (?) I did the math. The new cab engine in firmware v3.5 introduced 20 guitar cabs and 4 bass cabs, and v3.6 introduced 9 new cabs. That's 33 cabs now running on the new engine based on individual IRs. The Release notes say: "Thousands of impulses were captured with Sound Design's all new IR capture system" Thousands? What an understatement if we take Line 6 at its word (and I do). I couldn't find detailed information on Sound Design's IR Capture system but unless there's some aggregation magic involved I presume each IR is captured separately and individually from the cab and mic sources. So how many is that? In addition to the cab selection there are 4 mic-related parameters that I imagine are baked into an IR: Mic, Position, Distance, and Angle . I believe the other parameters Lo/Hi Cut, etc) would be applied to the IR rather than baked into it. By my understanding a unique IR is specified by the specific combination of values of all these parameters. What are the available discrete values? There are 12 mics; 101 Position values ranging from 0 to 10 in decimal point values; 45 Distance values ranging from 1.00 to 12.00 in 1/4" increments; and 2 angles, 0 deg and 45 deg. So for each cab there are 12*101*45*2 individual IRs. That's 109,080. With 33 cabs that's 3,599,640 individual IR files. I think it would be ludicrous to attempt that without automation, not only for the human effort involved but also because no humans could do that without introducing a large number of errors due to boredom and exhaustion. So I bet there's an automated ratchet set of railroad-like tracks in Line 6 labs that moves a mic stand through 101*45 positions, with a 45 degree angling of the mic at each position. Am I anal? Is it my CDO? (i prefer it in alphabetical order.) Whatever. Back to real life now....

Yes, I do too. I wasn’t questioning you; just commenting on the size and scope of the undertaking.

Yes, true! Can you imagine the tediousness of the development? “Here’s your job for the foreseeable future, mister/miss Line 6 developer. See that collection of cabs and mics over there? Use this IR creation tool to create an IR for every specific combination of cab, mic, and mic position (to a specific granularity) in two directions. And follow this IR file naming convention so that the Helix firmware can properly index and locate/load the IR file on demand. Oh, and here’s your isolation pay bonus. Pack a lunch.” It would almost be worth building a robot that moves the mic position in the specified increments and issues the Create/Save IR FIle” command. Then manual intervention would only be required to periodically change the physical mic and cab. Makes me wonder if they actually did that.

In Windows there is no aggregate device capability as described by rd2rk. The ASIO a protocol requires that a single audio interface device be used for both input and output. Hence you should configure your DAW to use the HX stomp XL and its ASIO driver as the audio input/output device. Don’t use any other ASIO device connected to your computer while using your DAW. Connecting your speakers/monitors to the Stomp XL audio outputs provides latency free monitoring. You can connect the keyboard audio outputs to the stereo Return/Aux inputs of the Stomp XL. You can record this dry (no processing) using the Record Source USB 7/8 for the DAW track. Connect your guitar to the Input L(mono) Input and record the guitar’s processed output using USB 1/2 in your DAW track, and record the dry guitar using USB 5. You can record all three tracks simultaneously and then playback all recorded tracks independently, and reamp the dry guitar track as desired. For recording the outputs of other (non-guitar) audio devices you can use both the stereo Inputs and Return/Aux In inputs simultaneously. Using the Input jacks allows you to select the inputs for processing in the Stomp preset. For instance, you could record a second keyboard, or a drum machine, etc. For full details read the manual chapter titled USB Audio.

Try this setup: #1 to FOH. Use the Amp Out jack. In Global Settings set this to Line level and set the Amp Out Src to Main Out. This is an unbalanced output so depending on the venue you may need to use an external DI box to feed FOH. #2 to HR. Use the Main Out jack. In Global Settings set this to Line level.

It should be on the bottom of the device. The manual shows pictures of every surface except the bottom and it isn’t on any of those surfaces, so…..

Models are greyed out when the path’s DSP limit is approached, as described in the manual. Read it more carefully for a more complete understanding of the device’s capabilities and limitations. Path 1 output is stereo, and routing it to Path 2 does provide a stereo input to Path B. Unless, of course, you have a mono FX block at the end of Path A. Then Path B will receive the mono signal from Path A. Paths A and B are independent processing paths, each of which can be split into parallel paths for mixing/merging within the Path. The Output block in each of Path A and B provides a Pan parameter which allows you to mix the output signals from each Path. Please provide other specific examples of what you would like to be able to do. There may be a way.

No idea how you would determine the serial number. But it likely means you own a stolen or knock-off guitar (not made in Indonesia by Line 6). Or, some manufacturing flaw allowed it to pass through the process without a serial number ever being stamped. The picture looks like that area is very clean. Is there any evidence that the number was removed or erased?

I would look into a pair of studio monitors or PA speakers, at least 5”. These are not home stereo speakers; they are called FRFR (full range, flat response) monitors. There are many options, and many threads in this forum on this topic. KRK seem to be favourites around here but talk to your local audio store.

I suggest you both open a support ticket if you haven’t already done so.

Since it’s not working now your next update will need to be manual. The release notes for the next release will tell us whether or not this has been fixed. But there’s no timeline for the next release. However I do know that Line 6 is aware, and it’s a very visible bug so I think there’s a good chance it will be fixed soon.

Analysis suggests each marker is 10 cents. Five markers on each side represent 50 cents flat/sharp, after which the tuning display changes to the adjacent semi-tone, where what would have been 51 cents flat becomes 49 cents sharp and vice-versa.

I notice your Mac OS is the one that has an issue with HX Edit’s ability to detect that updates are available. Is it possible that you updated HX Edit to v3.60 and then did not update the HX stomp firmware to v3.60 because you are aware that an update is available? If so you may be running incompatible versions of the driver and firmware. Just a thought - not likely, but possibly, the problem.

There is no Footswitch block. Do you mean the Vol or Wah (pedal) block? Or maybe the FX Loop block?

Which Line 6 amp do you have? Is the mixer channel that you’re using expecting a Line level signal? Does the amp work standalone with your guitar (no mixer involved)?

Perhaps I misunderstand. Seems to me your cabling would be Guitar -> physical amp Guitar In -> amp FX Send -> POD Go Guitar In -> POD Go FX Send -> amp FX Return -> ???? That feeds your amp’s power amp and cab section. What goes back to the POD Go FX Return? If the above is not what you’re thinking, then please describe it. At the very least what you are losing by connecting your guitar directly to the amp is the ability to place any of the POD Go’s FX blocks in front of your physical amp.

Can you disable the ASIO4ALL driver so that Cakewalk does not recognize/list it? Restart your PC and the POD HD afterward.

Do you have the Line 6 driver installed?

Connect your speakers/headphones to the POD HD outputs. Also, configure your DAW (recording program) to use the POD HD400 and its ASIO driver, not ASIO4ALL.

I don’t have any experience with that sort of setup, but I know this: Rule #1 with Line 6 USB - avoid using usb hubs. Can you test, temporarily, what you want to do without using the hub? Let’s simplify things to see if you can get that working first, then add complexity.

I believe that’s the preset tempo.

The POD Go midi uses the usb connection. How is your midi footswitch connected to the POD Go?

That’s very odd. Perhaps a factory reset will fix it. Make backups of anything you want to save before you perform the reset.

Yes there's an update. You may be on a specific version of Mac OS where a bug in HX Edit is preventing notification of an available update. Download and install the v3.60 firmware file to your computer then run Line 6 Updater and choose 'Install from File'. The bug will be fixed soon.