Jump to content

Klaim

Members
  • Content Count

    46
  • Joined

  • Last visited

  • Days Won

    1

Klaim last won the day on August 23 2020

Klaim had the most liked content!

Community Reputation

5 Neutral

About Klaim

  • Rank
    Just Startin'

Profile Information

  • Registered Products
    1
  1. @mprater76 Oh wow that's interesting, thanks for reporting that! So far I didn't get any feedback from Line6, I tried to ping them in the ticket but still no feedback. I don't know if they are working on it.
  2. Yes I get the sound through XLR and it doesn't change a thing, though it's easier for me as I can have everyuting plugged to my interface. Anyway I can't reproduce that issue. I was wondering if it might be something like your guitar's pickup? Are they active? Or anything between the guitar and the helix?
  3. This is recorded direct from the helix? Through usb?
  4. I yes I missed that, got it. Indeed, something is weird. Can't reproduce this without either some noise gate or something similar.
  5. Could you send here an audio extract where there is the sound you find bad, and a preset that generates it? So that we can check if we observe the same thing with different outputs.
  6. If I understand correctly, I think the only way to make it work is to make the OS use the Helix as it's audio interface (same as DAW but for the OS by default) via the usb cable, in which case: - you would need to have the speakers plugged to the output of the Helix to be able to hear OS+Helix directly; - all the sounds of the OS would go out fo the Helix to the speakers (because Helix is an audio interface); - all the sounds of the Helix would go out to the speakers too (because directly out of it); - the performance of the audio interface would be the one of the Helix (it's good, though not as good as some other audio interfaces); I do it in a different way, which might not help you if you only want to use the usb cable: I have a Focusrite Clareette 4Pre (so recent Focusrite audio interface) and they provide an audio routing software which helps me set it up this way: - the OS (Windows in my case) uses the Focusrite always; - the Helix outputs ==XLR==> inputs of Focusrite; - output of Focusrite ==> Speakers (actually I have several speaker sets and I also use headphones but let's focus on a case similar then yours) - Helix ==USB==> Windows (because I still want to use HXEdit) and sometime I use the Helix as an audio interface too; The routing software allows me to output anything coming from the Helix to any other output (speakers by default, but sometime I shut them up and only have the headphones). I can also route the audio from Windows through the same output when I want to play with the Helix over a track. That's all without a DAW. When I use a DAW, I can either hear the Helix directly and deactivate monitoring, OR activate monitoring and route the output of Windows+DAW to the speakers/headphones, after shutting the Helix output from the speakers). Basically, I find far more flexible to plug everything I have in my audio interface, and then route inputs to outputs as I need, because I can do that without the DAW.
  7. Klaim

    128 IRs

    I suspect most Helix users (like me) have it plugged in a computer when they are not going live and just have their library of presets and IRs backuped there, and probably tons of IRs on the computer that they only move in the Helix for their tons. (actually since a few months I stopped using IRs to focus on the models provided by default, as in my case it's far enough and I'm learning a lot about sound engineering)
  8. I would not qualify pressing switches designed for that as "hard enough" ... As pointed before, that's also a test they have to do to be able to sell units anyway. It would be different if I had put some coffea on it, or made it fall in some way, but here it's just pressing switches which are designed for... being pressed. (and the related software) Again (sorry, don't take it negatively, I'm just summarizing what I pointed before): - I'm not looking for alternate solution, I already know them, but thanks anyway :) ; - I had the guitar in my hands to be able to strum between each preset when I discovered the issue (so I was not specially fast as I was strumming between each preset), you can't go efficiently with the dials when doing this. When I'm tweaking presets I already use HX Edit a lot, that's probably why I didn't find this issue earlier. Indeed, that's why I wonder if anyone around can reproduce this? Even slowly? Also I'm not considering this as a too big issue, so, as I pointed before, that's fine if they put it as low priority. Though I suspect it's still a problem they will have to fix as it's still blocking the unit from working beyond the preset it's stuck with. I'll need to investigate more for more details.
  9. That's mainly why I pointed that nobody would do that "in a live show". But okay, no problem. Indeed it makes sense that - it takes time to do ... anything really through software; - here there is concurrency involved so it's not necessarily trivial, but they do need to make the system as responsive as possible, so I agree with your points; But the issue here, is totally besides the point you are making: a system being slown down by some usage is one thing; making the system unusable (basically broken) is definitely a bug, however you reach that point (assuming just pressing buttons). For example I've worked with humanoid robots, which are naturally highly concurrent. It can happen that some programming or some human usage will slow them down (or just some specific reactions) which can be an experience problem, maybe to be solved, maybe not, depends. But anything that render the whole robot stuck in no-reaction, in some ways, have to be a showstopper. Though, the less probable the issue trigger happen, the less priority is given to the issue.
  10. I had the Helix for almost 2 years, so no your assumption is incorrect, but I can see how you would have guessed this; I'm not a power user but I've used it regularly, like almost daily, for production and live (well, more like preparing for live this year :P); I also use it a lot to explore (guitar) sound. So far I couldn't confirm if speed plays a role in this. If my memory is correct, I wasnt doing it fast the first time (because I was strumming between each preset change) but this would have to be confirmed, I'll try when I have a minute; About if it appeared before the patch: I did the same thing several time since I had the Helix and didn't hit that issue (also note that pressing quickly switches is a basic hardware test that's usually done in factory, it's not special and should never "brick" the unit - so I assume it's due to a software change). However that doesnt mean that it wasn't there before the patch(es) to 3.0(1), I can't completely confirm that because it might be due to other factors - for example it took me less than 30 seconds to brick the thing the 2 first times I reproduced this bug, so maybe I was "lucky" before the update. Though the update was probably a condition to get this, I suppose. I'm not looking for an "answer" though, just reporting a problem that can occur. It's fine if the devs says it's low priority or something because it's not a big issue and its easy to not hit (I think). Though note that in my "short" xp with it, that's not the first bug I found, I reported some because they could have happened live too, which is a bigger problem (for when we'll be able to do live shows again lol).
  11. To be clear: I'm not looking for a workaround or anything like that, it's not a big issue in live, it's an issue mainly at home trying stuffs. I know there are other ways to switch between presets (I didn't check yet if they block the unit too). I'm not looking for "help" (or whatever twisted viewpoint you might have on broken software). I posted to report the issue because that's clearly a software failure and it's easy to reproduce. For a programmer that's maybe half the problem solved (though here it involves concurrency so it's probably not that easy). That's a bug, devs should be aware if they are not already. I'm happy with my unit, I'm not complaining. edit> I put the info in an issue ticket, I suppose it will be more useful to the devs there than here.
  12. You do realize I reached that point in normal daily use, simply looking for a sound? Of course I'm surprised, it should never break for such simple thing. Of course it's not abuse, switching presets is a basic operation. Seriously people, what's wrong with you all? You see your hardware brick after basic usage and that's necessarily your fault? O__o
  13. Yeah thanks, I do know about the alternatives. Though I got there by simply trying presets quickly with my foot, it's not a big problem, but it means I can "quickly try presets", which is surprising. It's necessarily a bug. If it was "DSP not being able to keep up" there would be glitchs or something, not "switches not working anymore".
  14. That's quite a bad analogy. Changing a preset is a basic operation, like turning the wheel. Turning the wheel left and right very quickly should not make the wheel block suddenly, right? Also, I a programmer, it's obvious that the issue is a software bug. I don't see the point in trying to make "me" the issue.
  15. Well, it's certain that I wont do that in a live show XD (assuming it's not a random bug when switching presets) And it's easy to avoid. However I found this when I was trying to find a preset that had the right sound (I had background music and was improvising). Also I think I did that a lot in the past without problem (and I was doing that a lot with a Zoom G3X before, as I am still quite a beginner in sounds). Looks like this issue is easy to reproduce?
×
×
  • Create New...