Well someone did a not so ignorant argumentation over here.
https://gainstaginggeekery.com/2018...g-google-headaches-excedrin-rinse-and-repeat/
There are so many flaws in this I don't even know where to begin...
Well someone did a not so ignorant argumentation over here.
https://gainstaginggeekery.com/2018...g-google-headaches-excedrin-rinse-and-repeat/
What? This dude struggles to get one measurement right because of his lack of basic knowledge in the subject. Summary of his verbose, badly communicated article: He chronicles how he keeps getting the measurement wrong because of his equipment and technique, until the very last graph.
The only graph worth a salt is the very last one which goes to prove Cliff's finding, high-ish aliasing noise in the Helix across its amp models.
Correct. I struggled with this till i upgraded my audio interface. If you read the entire post you will see that the only real relevant data is the last graph where it confirms your findings. I did my best to draw no conclusions, and I think you will also admit that this is a difficult test. 60 db is a high bar. That said. Helix failed I am a helix owner, and wasnt particularly happy to post this but it failed plain and simple. I wasn't going to hide my results. As to the story and drama... Its just a blog post, i try and make it amusing. I'll give you the signal to aliasing ratio of any amp in helix if you ask.He's doing something very wrong because his very first graph comparing to the Fuchs has aliasing on the real amp and real amps don't alias. Those spikes at 4 and 6 kHz are aliases as are the two around 14 kHz.
Actually, now that I think about it, I know exactly what he did wrong. There's a little quirk (one of several) in TrueRTA in that it will alias (a LOT) if you don't set it's sample rate to equal the sample rate of your interface. IIRC the default sample rate is 44.1. If you leave it at 44.1 and your interface is running at 48 it will alias and vice-versa.
As I said, Its just as blog, I do it for my own amusement. I document my successes as well as my failures. I followed this process because it intrigued me. No other reason, no agenda, or i wouldn't have posted it at all.This article is a nice example of internet knowledge in blogs I'm not saying that all blogs are as wrong as he is, but there's a lot of bullshit information out there.
But at least he's honest telling the readers that he has no idea
As I said, Its just as blog, I do it for my own amusement. I document my successes as well as my failures. I followed this process because it intrigued me. No other reason, no agenda, or i wouldn't have posted it at all.
Correct. I struggled with this till i upgraded my audio interface. If you read the entire post you will see that the only real relevant data is the last graph where it confirms your findings. I did my best to draw no conclusions, and I think you will also admit that this is a difficult test. 60 db is a high bar. That said. Helix failed I am a helix owner, and wasnt particularly happy to post this but it failed plain and simple. I wasn't going to hide my results. As to the story and drama... Its just a blog post, i try and make it amusing. I'll give you the signal to aliasing ratio of any amp in helix if you ask.
I imagine that one of the consequences of higher levels of aliasing noise in a signal is a cumulative listener fatigue. Are there any studies on this subject that establish thresholds and durations of what most people will tolerate?
Perhaps. I believe it's also a contributor to the "fizz" that people say they hear.
I would ask you to write more clearly so that it's well understandable from the beginning that the other graphs are meaningless. Your readers will have less of an understanding than you do, and not be able to sift through the junk from real data unless you're very clear about it. You make several conclusions along the way, and aren't clear about communicating that they're the wrong conclusions.If you read the entire post you will see that the only real relevant data is the last graph where it confirms your findings.
And if I may, "it's just a blog" seems a little unforthcoming. You're an admin in the huge Helix facebook group, and seems to me distributing your blog and graphs out for many to see. So again, I would ask for clear communication.As I said, Its just as blog, I do it for my own amusement. I document my successes as well as my failures. I followed this process because it intrigued me. No other reason, no agenda, or i wouldn't have posted it at all.
And if I may, "it's just a blog" seems a little unforthcoming. You're an admin in the Helix facebook group, and seems to me distributing your blog and graphs out for many to see. So again, I would ask for clear communication.
I'd encourage everyone to go back to the post where the grand entrance was made
But that's from a different person though.
You are more than welcome. One small thing tho... Ya see there's this small complication.... when I reproduce the test and alter the gain settings on my Helix the same way you said that you did on your AxFxIII i come up with this. Which shows 78dB "peak signal to aliasing" To be 100% clear your unit as you tested it only came up at 68dB.Thank you for you honesty and candor.
You are more than welcome. One small thing tho... Ya see there's this small complication.... when I reproduce the test and alter the gain settings on my Helix the same way you said that you did on your AxFxIII i come up with this. Which shows 78dB "peak signal to aliasing" To be 100% clear your unit as you tested it only came up at 68dB. View attachment 45174
LOL I couldn't help myself glad you have a sense of humor.I'm assuming the green trace is the DUT in which case it's only 30 dB. At 5 kHz there's a small spike that touches -30 dB.
Oh, and nice title on your project...