Jump to content

Klaim

Members
  • Posts

    72
  • Joined

  • Last visited

  • Days Won

    1

Klaim last won the day on August 23 2020

Klaim had the most liked content!

Profile Information

  • Registered Products
    1

Klaim's Achievements

Enthusiast

Enthusiast (6/14)

  • Week One Done
  • One Month Later
  • One Year In
  • First Post Rare
  • Collaborator Rare

Recent Badges

11

Reputation

  1. To add to these valid solutions: I got a lot of random Windows crashes (as in blue screen of death) coming from Asio4All when I was using it all the time, I think it's best to first see if switching between the constructor-provided Asio drivers isn't working well enough for you. That being said it was more than 2 years ago and there have been updates so I don't know. It's just good to know that there might be stability issues with it. An alternative to Asio4All for Asio driver working as an aggregator: VoiceMeter Banana - it works well but in my experience it was slow (as expected for this kind of feature I guess) to the poitn I couldnt use it for recording guitar, and it was super hard to understand all the parameters (I feel like it have more than Asio4All.
  2. Klaim

    Unexpected Crackles?

    Thanks everybody and in particular @datacommando for the clarifications and historical quote! I'll add that I remembered today that I have the Big Book Of Helix Tips And Tricks which also have a section explaining the Headroom setting, and with the background given by Ben Adrian it makes a lot of sense. I'm also noting that I didn't think it would be related to distorsion because the noise felt like lattency issues instead of distorsion to me, so I learned now that actually it can be distorsion. Thanks again everyone!
  3. Klaim

    Unexpected Crackles?

    Yes, I tried to explain this happens without any DAW and the recording is only the SPDIF digital output, there is no audio processing happening here. Without a DAW I can hear the crackling directly on the speaker which is plugged directly on the Helix. Maybe I was not clear: this is a FACTORY preset, it's located at position 96 in the FACTORY 1 bank, "RABEA AMBI LEAD" to be very precise. So can you try it and tell me if you observe the same thing? The solution given by DuneinDragon works but I don't understand why yet. Or maybe the reverb's "Headroom" should be considered as a buffer size? Though I did reset it completely after upgrading the 3.15 version. I can try again, will report.
  4. Klaim

    Unexpected Crackles?

    Only the delay on the right channel (the one which is crackling in this preset) have a headroom parametter set to +2.7dB I pushed it to +6dB and now it doesnt crackle anymore indeed! Thanks! It is not clear to me how the crackling and the headroom are related technically so if you have an explaination I'm interested (I'm a software engeneer and knows a little bit about audio processing but not enough for understanding that particular case) Sidenote: Helix did something weird when I first bootup to try this: the signal went through the first processor but not the second, so I wened up with no sound on this particular preset. I think it's again a bug of when you change preset quickly (using the rotation button) and I just rebooted the Helix and it worked. Hopefully it will not happen in live ....
  5. For some time now I have been noticing sometime when working with my own presets on my Helix (Floor), almost randomly, crackle noises, similar to what would happen if your processing chain couldnt match the given latency goal (like if you didn't set enough buffer in an audio interface, you know what I mean I guess). It happens randomly and rarely enough in my own presets that I didn't mind, but I have been noticing it for several months to a year now, not sure exactly. Today while trying random presets (I'm on v3.15, everything reset to factory, then I added my own presets in one of the empty library) and I noticed that I can hear it systematically with the RabeAfro Lead Ambiant preset, but only on the right side, and only when trying to play chords loudly (my guitar is a TAM10 so it's 8 string with lower strings, but the mic is not loud). I started analyzing whats going on: - this is a preset where the left and right side have different chain of blocs and different amps etc, with just a gain pedal and a compression pedal in common at the beginning - even the reverb and delays are different on each side; - on this specific preset I can only hear the crackles (when trying chords) on the right side; I changed the output node to go to the left side and of course I heard it on the left side, to be sure it was very specific to that chain; - the preset itself don't have a loud output, actually the output level of both sides are reduced, and the guitar's mics are not super hot either (I usually use compressors to bump the guitar signal a bit actually, but here it's not a preset I made); - suspecting my new pair of speakers (Headrush 108, getting the jack output from the Helix) I recorded (see below) through Reaper the signal coming from the RCA output which goes into my audio interface (Focusrite Clarett 4Pre Usb), so it is the digital signal but not going through usb but through the S/PDIF channel in. I can hear the exact same crackles and you can hear it in the recording. - we can hear that the crackles feels coming from before the reverb and delay and I managed to remove the crackles by disabling the amp block on the right side, but it kind of kills the whole thing doesnt it? XD So right now I feel like the issue is coming from the preset itself, the block being maybe overloaded in some way, but that feels also wrong from my understanding of how it works, it should not do this kind of thing? Questions: 1. Am I alone observing this? I wonder if my unit have an hardware issue, so if I'm alone it might mean it is. 2. If not, what would be the cause? Specific to some blocks? 3. Should I consider this a software bug? My (limited but a bit educated) knowledge of the subject suggests that for this crackle to happen the block in question or the chain of block must spend more time than the specified processing deadline, which should not be the case here I think? So...bug? I didn't find this issue when searching for known issues, the closer I found was issues when using the Helix as audio interface, that I basically never do. Recording: Rabeafro Ambiant Lead preset, playing chords, with a TAM10 set to position 2 full gain knob, and the recorded through the SPDIF output -> cable -> Focusrite Clarett 4Pre USB -> Reaper (ASIO/Windows10). I hear the same thing (different of course) with speakers (both monitors blugged through the XLR output of the Helix and Headrush 108 speakers plugged to the jack output of the Helix). https://drive.google.com/file/d/1Nrh5QJ2dkLmr18NYezK5K9H_CLz5DgAz/view?usp=sharing
  6. I just got my SY-200 but didn't try yet the midi stuffs, so this is very interesting. I still need to buy a midi cable. I just checked and apparently most cables I see online do not explicitly state if it's type B or type A - this is annoying...
  7. I am also considering getting a Boss SY-200 too. However, did you try it? In conjonction with an Helix? My experience in the past with synth pedals (mostly from Electro Harmonics) have been mitigated.
  8. Oh thank you silverhead, I didn't realize that! Ok good to know about rebooting, that would also explain a lot of random behavior I saw in the past too that was fixed with a reboot.
  9. I just booted my Helix (floor) and noticed it was taking time and actually it was rebuilding the presets. I am surprised because: I did not upgrade anything since the release of 3.11.0 I did not request the rebuild and there was nothing over the buttons to accidentally request that The only thing I did before turning the Helix off yesterday is adding all the presets (about 200?) from the Helix Tips book mentioned in another thread. This means I used the banks 3 and 4 (I used the 3rd in the past but deleted its content in the beginning of the year). As far as I know, this should not trigger a preset rebuild either? Or am I missing something? Basically it looks random so I'm a bit scared that it might be a sign something is wrong. (I just made a backup in doubt)
  10. That's weird, the difference in volume between on and off should be drastic... did you check in an empty preset?
  11. In process of becoming an habit (until I get some automatic thing someday). I am now convinced it is not but the fact that it was only happening with the Helix and only with XLR in/out was disturbing enough for me to be sure, because if need to repair the Helix it will probably not be cheap (I think I passed the 2y guarantee). So far I've been lucky but I guess I'm a bit anxious. Yes it's line level. Also I don't think it's related to sounds produced by the Helix anyway as it appears when the screens get powered, before the firmware screens even appears. Though I might be wrong. A power related thing is probably the source. I tried before with an empty preset, no change in behavior (it's one of the clues that it's not related to generated sound). As a variation of all my other attempts, I also tried this just now: Global EQ activated with level -60dB Result: still the pop at both startup and shutdown. Yeah it appeared weird to me mainly because - I started music+guitar late so most hardware I used so far is very modern (and definitely not old school in any way - and I avoid real amps because they are too expensive, big and fragile XD) so I probably dodged this kind of issues involuntarily; - Since I got my Helix I never experienced this until I decided to plug the XLR output of the Helix directly in the speakers instead of passing through the input of the audio interface. I guess I was just not exposed to this kind of issue until now. Lesson learned.
  12. I know, I already said (multiple times) I change setup to do that easilly (I couldnt before). But that doesnt clarify if the issue is with the Helix, it's just a general good practice/workaround. BTW I did a few more tests and can reproduce the issue (but far less loud) with a Zoom G3X, so I suppose the issue is with the speaker or interraction between speaker and Helix. The message from usedbyanr also goes in that direction. What I didn't try is to do the same with different speakers. Anyway ok.
  13. I totally missed your post, thanks for the info.
  14. I did a last test: plugging the XLR cable into the monitors while both are powered, both powered minutes before. I was expecting a noise at plug, but nope, no noise. So for now the only source plausible is "signal coming from the XLR output of the Helix". Meh. Yeah @datacommando I think I will stop here for the weird search and just use the new (less simple) setup I have to avoid doing the noise.
×
×
  • Create New...