mettelus

Yeah, and most times is not relevant at all anymore (as it is in this case). I wasn't familiar with the computer model so looked it up to see how old it was and the specs on it. You have to go back over 15 years to find a computer not SATA 3 capable, but I wanted to make sure. Back in the day, folks were "upgrading" SATA 2 machines with SATA 3 SSDs and wondering why they saw no improvement afterwards.

+1 to the above. Also for reference, there is a slight difference between SATA 2 and SATA 3 cables themselves, which is that small tab in the upper right of the first picture you posted. Those are SATA 3 (6Gb/sec drive) cables when they have that tab, so those cables match as well.

Just run MOHO 14 (whichever version) to auto-update. Quite a few new features, with the biggest one being able to export into gITF format for direct import into 3D applications. Full feature list is in the manual here. Original thread on MOHO 14 is here if interested. Excellent free tutorial series for MOHO 14 is on YouTube here if you have MOHO 14 and didn't realize it was out there.

Holy crap... I saw this article "New Jersey man believed to be 1st known death from red meat allergy linked to tick bites" (of course, the click-bait doesn't say what state, so I had to click it). The guy didn't realize he had alpha-gal, and basically went into anaphylaxis from it! What's worse... they say "Researchers said that in the eastern U.S., what are sometimes referred to as "chiggers" are often larvae of lone star ticks." LOL, I got bit by about 400 chiggers about 10 years ago now unwittingly tearing up things all around their nest (mentioned that above), but those were definitely chiggers. I never even considered that baby ticks could be confused with them... but then just learned that tick larvae do not attach when they bite, so that is definitely something to keep in mind if you are in areas where lone star ticks live (red counties are worst than yellow, but they are pretty much all over the east half of the US now ).

^^^^ This is definitely worth repeating. I got the Complete Bundle over 8 years ago now and the things that keep getting thrown in just add to the value of that decision. Over time, unless something is truly unique I don't even read about it anymore... Melda covers a lot more bases than other vendors in most cases. Even as a vendor, Melda has always stood out with the focus of getting more users, not allowing folks to duplicate purchase things, and rewarding loyal customers by throwing more free stuff at them. This is a far cry from those that milk their user base for everything they can and charging them for upgrades every year.... never paying for an update on something you own has immense value unto itself.

I can understand the OPs frustration. If you step back and think about it, the Undo history defaults to triple-digits (or used to, but forget the actual number) and that updates interactively. It isn't much of a stretch to ask that the MRU is updated interactively as well, especially since it has far less load to handle.

Another note, it is good practice to put a limiter on your output buss(es) to protect both your ears and hardware. I leave that engaged even when mixing (set high with a steep slope), but disable it for mixdowns/exports. I have seen a couple VSTis glitch over the years that output ~90 dB in the red.

Do you happen to have Z3TA+2? Muz3um had made two patch banks for it years ago, and Minimoog was several of the presets from them. I seem to recall other synths that have Minimoog patches (although the synth itself is not focused on the Minimoog), but Z3TA+2 was the first one that came to mind. NI's Monark is supposedly one of the better ones. I picked that up with Komplete a few years back, but not used it enough to speak to it.

Quick update for you from my downloaded preset "issue" I mentioned above (or for anyone here that may see this issue). This thread from the Line 6 forums has good info and the issue is almost always (probably 90% of the time) that the input is set to something specific (like Variax), so shifting it to "Multi" or "Guitar" will make things good. What I did not think about till I saw that post was that some presets have hardware loop blocks in them (which will interrupt the chain if not connected), but the more obvious one (and my issue with the "Dan Huff, Kinda" preset) is there is a Volume block (straight up volume) that was assigned to zero volume as its default. These are often assigned to an expression pedal, and because the unit has more than one, I didn't think to switch the expression pedal over. The solution for that is to either remove the Volume block entirely (I have gotten used to the volume knob, so don't use a pedal for that) or set the volume default to 100. In either case, once you resolve the issue, re-save the downloaded preset. I hadn't downloaded any presets in a long while, so grabbed 8 that came to mind last weekend but only had issues with that one. Unfortunately, even with that issue resolved, none of the snapshots are very close to what I was seeking, so I am going to have to make one from scratch anyway

Excellent. Thank you for posting the solution. Best of luck with everything!

I think I dodged the bullet on this one. I never set up junctions for Melda, and always had samples go to my F drive since day 1. I didn't realize you cannot change those locations after the fact

Nice testament of what can be done with things when you get creative and keep things organic. Younger people have gotten used to DAWs and sound isolation (nothing but the instrument... we will add the space later); but back in the day the recording space, stuffing mics into pillows, throwing jackets over amps lying on their backs, and being creative with the tone chasing was where the fun was (and still is IMO). [Stupid side note, but this made me laugh so much I had to share it] OMG, I was literally laughing when I read Slash's quote about Rocks from Wikipedia! "I was in seventh grade and just going through the whole 1978 music thing that was happening for kids – which was like Cheap Trick and the Cars. Anyway, there was this chick that I was going after that was considerably older than me ... I'd been trying to be cool enough to take her out and have my way with her ... Finally, I sort of weaseled my way into her apartment. So we're hanging out and she put Rocks by Aerosmith on, and I was mesmerized by it. It was like the be-all-and-end-all, best-attitude, *****in' hard rock record ... I'd grown up with music, but this was like my record. I must have listened to it about half a dozen times, completely ignored her, and then got on my bike and rode. I was totally in there. I was at least gonna get a decent French kiss out of it, and I completely dropped the ball for Aerosmith, and that was that. It's probably one of the records that sums up my taste in hard rock bands to this day. Meanwhile, she's out there somewhere and I missed it. But it was worth it" Totally blew her off to listen to Rocks, then "got on his bike and rode"... he was in 7th grade!!!

Maybe one of the reasons I am confused is the OP picture. Sonar is recording a "stereo" track, so that leads me to believe that is what is coming out of the HELIX and is what SONAR is seeing (2 channels, identical or not). The interleave button as @Base 57 mentioned above is also something to check (especially if a track will not pan). If Sonar is truly seeing only one channel, another quick check is to "Bounce to Track(s)" that track in the OP and choose "Split Mono." This will create two mono tracks with the left and right channels separated. If you then phase invert one of those channels (on the track view) and solo those two tracks, they will sum to nothing when played back if truly identical.... when you said "slight differences" between channels, they should sum to "something." My concern is that some effects convert to "stereo" by simply duplicating a mono track left and right with a very minute delay between them. Again, the same test with a factory preset with obvious left/right differences will immediately point out if there is a handshake issue between the HELIX and Sonar (if that sums to zero, the bakers on both sides of the fence may need to get involved). Lastly, is this a factory preset you are using or one you created or downloaded? I can check it out this weekend on mine if I know which preset/snapshot it is or can load it. If it is one you modified or downloaded, they are small, so you can attach them to a post here. I just need the preset/snapshot from it where you are seeing this problem to test it on my end. I downloaded a Dan Huff preset with >1000 5-star ratings a couple weeks ago and literally cannot get it to output anything unless the input to path 2A is the guitar (bypassing half the FX chain and making it useless)... an obvious bug with porting it forward, so I was planning to dissect/rebuild/tweak that this weekend anyway. Checking out another preset along the way won't be a big deal if you want me to test it on my end.

This always comes to mind for me when AmpleSound updates are needed... first you have to download the correct installer Mac or PC (which includes 2 variants in the zip), unpack those, install them all manually and separately (and choose the proper VST2 folder), then check to see if new libraries are needed, then clean up all the downloads. Updating typically takes an hour I wish they had an installer! Then you just log in, see what things you own that need updating and it can all just happen while you go grab more coffee and be done with it.

For the ASIO part, here is something else to try. Windows has been terrible with letting the first app that needs audio to take control of a device and this wreaks havoc on audio interfaces. Start with the HELIX on and plugged into the computer with HX Edit open. Then open "Sound Settings" in the Windows search bar, and click "Sound Control Panel" in the upper right. In that popup, set the Realtek as the default device for playback, that way the audio interface can only be used by an app that you choose to let see it (not Windows). Then highlight the HELIX and click on Properties. On the "Enhancements" tab at the top, make sure "Disable all sound effects" is checked, then on the "Advanced" tab be sure the default format matches your project and that both items in the "Exclusive Mode" box are unchecked. Just for good measure, in the "Spatial sound" tab, make sure that is off. Apply those changes and open Sonar and see if you can shift modes to ASIO then. I always start the HELIX, open HX Edit, then start the DAW. HX Edit is far simpler for me when sitting at a computer (no need to bend over to tweak knobs/buttons when you can do it with a mouse), but now I am sort of wondering if that should be open anyway to force the HELIX to be talking to the computer properly. Even in WASAPI mode as long as the drivers are loaded it should work fine. A quick check would be another patch that has an obvious ping pong delay or rotary in it so the channels coming from the HELIX are clearly different. Some patches carried forward from other firmware versions (or downloaded from LINE6's site) do not always port to the newer firmware 100%, so slapping a ping pong delay on a factory patch would be best. As long as you have Firmware and HX Edit versions > 3.0, I think they all talk properly, but the newest version of both is always best. Also, have you tried the LINE 6 forums? Although some of us here have the HELIX, I have never seen your issue before (and it is really confusing me as to why). The LINE 6 community might have insight as well.