Leaderboard

Sorry. Snapshots don’t affect DSP usage. The preset’s DSP requirements take account of all blocks in the preset, whether or not they are used in any particular snapshot. Unfortunately the answer to the last sentence/question in your post is Yes.

Posted this a while back so it is getting a little long in the tooth but you might find an idea in it and it has a link for an unofficial Helix MIDI guide. If you come up with any cool loopback ideas feel free to post them over there. Was attempting to gather them up in one place for easier reference.

To the user group as a whole. (A small rant) The intent of this group is to help each other. Sarcastic, inflated, offhanded comment do not help anyone. I've been a member of the line 6 forum for 13 years. I stopped using it for years because of this problem and because of just a few people. Now that I've purchased the Helix floor, I've been using the forum again. The Helix, to my admission it is very powerful and can be confusing and I needed guidance. We all have question and get confused by the equipment, processes, and programs. Some of us have more experience with PC, some with other skills. So if someone asks a question that has already been asked (or we think is stupid) then politely point them to the correct thread. I teach Mainframe Security for a living and the only stupid question is the one that isn't asked. If they are confused about something help them in a nice way. Trashing and trashing is not helping anyone. Some people learn by reading, some by seeing and doing. Some lucky few can do both. As much as I like Line 6, we paid for the hardware and software. We should expect Line 6 to fix problems when we discovered and reported by proper means. We also have to understand Line 6 has to collect, research, test, prioritized, correct, and build a new modification release. If the software release for the Helix was crashing, Line 6 would be freaking out to create a fix. So we have to have a little patients. Also Line 6 does use these sites to their benefit. This reduces the need for Line 6 to staff their help desk. Software can and does have problem. The number of defects after a software release reflects on the degree of testing done before being released. Also a very important point, there are so many ways to use and stress the Helix as per hardware / operating software. Due to this versatility, we can and do create new creative ways to create bugs. In some ways we're spoiled. In the old days we had had 5 stop boxes if you were lucky and rich. Vol, Compress/Distortion, Flanger, Chorus, Delay/Reverb. We spent more time playing the instrument. Now our processors are so powerful and many of us are geeks we seem to be spending more time playing our processors. (one thing to remember is "everyone has an A$$, but you don't have to be one" Have fun, Playing, tweaking, do both, be nice and help each other out. Happy holidays and stay safe.

Firmware/Editor: Firmware 3.00; HX Edit 3.00 OS: Windows 10 Global Settings: Prefereces: Preset Numbering set to 01A-32D, Footswitches: set to “Preset/Snap” with “8 Switches”. Bug: Bank Down skips Bank 1. It goes straight to Bank 32. Also, sometimes if higher up (IE bank 16, it will skip bank 15 and go to 14). To duplicate: Install HX Edit 3.00 Run HX Edit and perform firmware update 3.00 from HX Edit All of my patches are in USER01. Select that and hit bank up to bank 5. Hit bank down to try and get back to 1. It goes to 32. I reinstalled 2.92 and it doesn’t do this. Bank up and Bank down is perfect. Workaround is to go back up from Bank 32, so not so bad, just a pita.

I have always used the Helix and Pod Go through a power amp (Orange Pedal Baby) and real cab. Using the preamps and no cabs as that always sounded best to me. Still a great solution for these units but the other day I decided to pick up a JBL 305p mkii just to see what an FRFR can do. Well it opened up a whole new world for these units. Every stock amp sounded great in default settings, and being able to use all Amp and Cab options really makes a huge difference. I ordered the Line 6 1x12 power amp. Probably still keep the JBL as it sounds great for just messing around in a different location.

Thanks, software developer by day, gigging musician by night. More information the better for this type of thing.

I didn't go the PC+ route, just the basic version. I plan on using the cabs within the Helix/Pod only and maybe some IRs in the future.

Glad to hear that! One note, maybe you already did this already, but if you are on firmware 3.0 now you should also download and install HX Edit 3.0.

Thank you. I was actually watching some of these videos before posting this question. Very helpful, thank you.

You already got an answer to your question(s).... I'll just provide a few tips.... Amps use a lot of resources.... that is probably the vast majority of your resources. Since you separate the amps and cab.... check the "pre-amp version" of one (or both) to see if you can it is suitable enough instead of the full model. For your effects, make sure you are NOT using any stereo versions unless you absolutely need it! eg: Once you go Stereo you have to stay Stereo... before that, keep it Mono! Here is a link to a helpful chart showing DSP usage of each amp/effect. Sometimes an acceptable substitution for an effect is all you need :) https://benvesco.com/store/helix-dsp-allocations/

I agree, RME and Zoom interfaces on USB3 have below 5ms latency while DAW monitoring (reamping with live plugins) and that's truly unnoticable. So those last 2-4 ms of recorded track misalignment while direct monitoring are nothing. Getting recorded tracks perfectly aligned in a DAW is a nice thing, though. But it turns out that something was off with my Line 6 driver (4.2.7.7). It was "frozen" (no ability to change settings). I thought that simply reinstalling it won't make a difference (for buffer settings and this latency misalignment)... but it did. I just clicked "reinstall" in Line 6 Monkey and everything works properly now. Thank you for the tip about line level FX Loop, I haven't though about it! I will do this "loopback" test out of curiosity anyway ;) You are really a life saver hurghanico! I think you have more practical knowledge about HD than Line 6 ;)

... and you shouldn’t feel dumb at all. If you think everyone understands it just fine you’re wrong. They just don’t ask, perhaps because they might feel kind of dumb..... But because you have asked the question hopefully you understand a little better. And you have helped some silent readers who may also benefit from this.

AUX and MIC are instrument level and there is no setting setting to change their behavior. However one the rear panel there is the RETURN input which depending on the dedicated physical switch setting can work at LINE or INSTRUMENT (STOMP) level, but to use it you need to put the FX LOOP block somewhere in the chain. I must say that I find it hard to believe that a human listener is able to clearly perceive a misalignment of +/- 2-4 ms. Luckily the listeners get the audio, but if instead they were to see the waveforms in millisecond detail along the time grid what would they think of who recorded those tracks? .. I think it would be fun _______________________________________________________________________________________________________________________________________________________________________ All about POD HD500/X help and useful tips

1. The amp pack is a set of actual Helix presets that use the Helix Cali Rectifier amp model. Hence the .hlx format. 2. Yes. You can usually replace the Helix preset Cab model with any purchased IR. 3. A1) IRs are usually used to replace a stock Cab but sometimes they are used to augment a stock cab, meaning both should be used toghether. Perhaps ML Sound Labs has used this approach in their MO Cab Pack. Or, the Rectifier Amp Pack presets are designed so that you can choose to use either the stock cab or the IR in the same preset, selecting between them with, for instance, a footswitch. You'd have to inspect the preset structure to answer this question. 3. A2) Don't know exactly how this purchase is structured, but if you can purchase the Amp Pack without the IR pack then the preset files have to be able to stand alone, using a stock cab without an IR.

I opened a ticket about this and submitted a video. I use banks 32, 1, 2, and 3 almost exclusively, so this is really messing me up.

Huh? Now I’m really confused. No USB? If you don’t have USB you will not be able to make backup safety copies of your presets, or use HX Edit to load IR files. It’s a real “must have” thing on a computer communicating with Line 6 HX devices. The clue is in the name Universal Serial Bus, its an industry standard. To me this doesn’t make sense.

Yep & Yep. Thanks

I would invert the colors when the snapshot is selected as well.

Only way to know is to try it and see. If it sounds good at home, no reason it shouldn't sound good live. Certainly, an acoustic amp is a lot nearer FRFR than a valve amp. My lightweight solution is to use Pod Go straight through the PA. If it's a smaller gig with no PA, I have a Headrush FRFR108 which is superb and I can use as a monitor even if there is a PA.

Actually no testing is needed if the settings are in a certain way. Any decent DAW should automatically compensate for the amount of latency in the system in use, and if you only use the hardware direct monitoring (POD) you should not have any problem of synchronization between the recorded tracks and the one in recording. The synchronization problems/tracks misalignments occur only when instead of the direct hardware monitoring (POD) you use/enable the monitoring of the recording track in the DAW as auditory reference for recording, for example if you need/want to monitor live a plugin loader of impulse responses. So in conclusion I recommend enabling only the direct hardware monitoring (POD), and applying any plugins if necessary only later on the track already recorded. To enable the direct hardware monitoring (POD) you should use the Line6 ASIO control panel, to disable/enable the DAW track monitoring you should use your DAW dedicated commands/buttons. _______________________________________________________________________________________________________________________________________________________________________ All about POD HD500/X help and useful tips

hey all. I have a hx stomp. Updated to 3.0. When I go into a patch now- if i move a block it completely forgets and wipes out all the blocks. still remembers the name but no sound comes out and I have to go in and out of a patch.. really annoying if i have spent 20 minutes tweaking to loose all my tweaks! Anyone else seeing that bug?

I'm sure here's made a script that does it for him. If not, he's a charitable, kind and patient soul. On that topic, I also updated before updating Edit, felt that something was wrong "with me", got anxious etc.... Came to the forum and saw the 300 threads panicking about the same problem. Now I see people who help and people who chastise over posts just will dissappear over a few weeks. So I really appreciate when people are patient enough with those who MAY NOT be forum regulars and arrive here understandably nervous. Yes there is a search function but, by the same token the UX for the update process could be improved. Likes, as this is such a recurring problem and given the numner of 3.0 updates these weeks, why isn't Line 6 putting that black retangle WARNING of theirs to clarify about the Edit 1st, Helix 2nd order of biz? TL;DR thanks @phil_m

I found a way to come close. There is a sweep echo in Helix that works really well. I had a GT-100. I liked it but it didn't compare to the Helix. The biggest thing about the Tera was how your pick attack could drive the effect. I have come really close with a dynamic split ( basically a gate to the effect), the sweep echo and the chamber echo.

So, you believe that Microsoft and Apple are lining up all the many, many producers of software when there's a new beta OS update and one by one, in some kind of order of importance, "fixing" the problems that their software is having with their OS? And that Line6 is waiting for their turn to get fixed? I'm just trying to understand.

Here's a specific example of a company who had an incompatibility with Big Sur early in the beta... Dropbox. Dropbox would simply crash when you opened it. Instead of telling their customers not to upgrade their OS, they fixed the incompatibility, released an app update and everything was resolved. That is how it works. OS updates break app compatibility all the time... the companies update their software. Line6 and other audio companies that make software simply as an afterthought so that they can sell their hardware as "works with Windows and Mac" don't put much resources into keeping things up to date. Also... I haven't insulted you at all.

Sure... you are right. Probably the Adobe stuff (or something like that) and a very limited number of high profile things, but an unmeasurable percent of the software out there.

Ok... so, neither Microsoft or Apple or any operating system developer is testing the many thousands of individual pieces of software that are out there on their OS updates. To think that they could or would do that is absurd. The way it works, in general, is they release betas to the developers before it hits the public, and software developers, like Line6 have an opportunity to get their software ready to be compatible with the new OS. Some developers take advantage of this, and some, like Line6 do not. There are certainly and frequently problems with all sorts of new OS versions, but that is not what we are talking about when we have a discussion about third party software compatibility. You are not talking about the same thing.

So, you think that Microsoft and Apple, etc... are going through all the many thousands and thousands of pieces of third party software to test them and make sure they are compatible each time they issue updates to their operating systems? I just want to make sure I understand what you are suggesting.

Yes, I have solved the problem in Windows 8.1 via the compatible mode for License Manager. I set this one on Win 7 up and additionally the admin mode too. And then - works! It detects the UX2 now.

The message you are getting is correct. The device presets are not compatible. You can’t load a Helix preset into the POD Go. The POD Go uses Helix models and DSP algorithms and the sounds are virtually identical. That doesn’t mean the presets are compatible. It does mean that if you manually recreate a simple Helix preset in the POD Go the sound of the two presets will be very close if not identical. I say a ‘simple’ Helix preset because the POD Go preset structure is much more limited than Helix. That’s why the presets are incompatible. ... and no, there is no preset converter.

The fact that YOUR mac is working fine isn't any indicator at all that the Big Sur release isn't without some significant problems. In the world of operating systems it's up to the manufacturer to thoroughly test their OS to determine if it works with third party software or what it's limitations are as well as what the base requirements are for the Mac to be able to run it correctly and efficiently. This is done during the different phases of bench testing, unit testing, performance testing, integration testing, capacity testing and so forth...LONG before it's released as a BETA to the public. It's very clear from all the press and responses on the internet there are significant issues with this release. If manufacturers are alerted about things that will no longer be supported on the OS, they can fix it. If they don't do thorough enough testing to even determine such things that falls into Apples domain to fix. Product testing, especially when it comes to core software such as operating systems, is not something that doesn't have multiple decades of history and procedures about how to do it right, so there's really no excuse for not doing it correctly if you care about your installed base of users.

I personally know for a fact the Microsoft does, as did IBM in it's mainframe heydays as well as Digital Equipment Corporation (DEC) in it's releases of new PDP-11 updates. It's all a part of being in the operating systems business, and your business is dependent on not breaking the things that depend on your operating system. For the most part this is done through partnership agreements and early BETA testing (long before there are "open" Beta releases). I can't speak to how Apple does it. But I can speak to how Microsoft does it and there are far more employees in testing and QA than there are in development on any given product (roughly about 3 to 1). As far as IBM and DEC I was working on products that ran on those systems and was tasked specifically with BETA testing their operating system updates with our products. Those products sometimes were off-the-shelf commercial products and some were in-house specialized company programs. In spite of all of this, anyone can have a bad release. But because you have a bad release doesn't relieve you from your responsibility to fix it if you're in the operating systems business. To be honest given the general responses of people to the Mac OS releases I often wonder if Apple still sees itself as a small specialty operating system since they really don't play in the bigger business market where Fortune 500 companies are betting their business operations on an operating system. And that causes them to be less diligent in their approach to testing.

Only because most people are morons and want to cry bricked at the first sign of trouble....im sure about .01% of those threads were actually "bricked"