JiveTurkey
Goatlord
- Messages
- 19,536
Gross legacy amps take less resources

Gross legacy amps take less resources
I know. I just wanted bag on BossBut their X models don't seem to use much more, either. At least not so much as to harm latency or overall performance.
Just confirmed with Brandon—Helix Floor, Rack, and LT are ~1.83ms from analog in to analog out. HX Stomp and Stomp XL are even shorter (1.17ms) because they don't need to hop between two DSPs. (Hopping between cores is similar, so remember: more cores = more latency.)Hi, @Digital Igloo! A tough one. How did Boss manage to get their latency well under 1ms which most other are above 2ms and usually 3+ with some configurations, including Helix?
I just wanted bag on Boss
I should probably clarify that I like Roland/BOSS quite a bit. I'd probably still be at Roland US if Japan hadn't completely ignored all my proposals—not even a "Sorry, Eric. We're not interested." They have way more wheelhouses in which to play than YGG does. My MV-7000 and MV-9000 (2007, so yeah, they're mighty ugly today) might've done well, but alas, they were never meant to be:I know (obviously).
On a serious note, there's really a whole lot of things Boss is doing right. Sometimes *vastly* better than any of the competitors.
- Mobile OS editor. Excellent. No need for any fancy on-device touchscreens. I know, the BTS app itself is quite debatable, but still.
- Lowest latency in its class. Pretty much the only unit allowing you to nest multiple loops serially, maybe even when running some other digital devices, without running into latency trouble all the time. This is a big one for me as I could possibly replace my loop switcher and still integrate my analog pedals the way I like it.
- Global blocks. No need to elaborate, IMO each and every somewhat more complexed modeler should offer such a functionality.
- Sort of gapless switching with delay/verb spillover. Yes, I know about the limitations - but for most situations, they should not limit you all that much. Especially along with global blocks this is a huge one (as you could, say, split a huge kitchen sink preset into one bank without losing gapless switching and global access to some parameters).
- Freely assignable parameter knobs. That's just sooo much what Mr. Franck's doctor ordered, really. Loved it with the GT-10 already (and it's been just 4 knobs with rather limited assignment options).
There's probably more and I'm explicitely not talking about the sounds (whether they'll be working for me is the very thing I plan to find out more thoroughly in 2024, my rather brief encounters yielded mixed results).
Sorry that this is getting so much OT in your part of the forum, Eric, but uhm... couldn't help it. And well, seriously, if the Helix had some/all of the above (ok, at least global blocks) and better visibility, I'd rebuy it tomorrow.
I can't imagine BOSS building their entire engine around 96kHz to save less than a few hundred microseconds in latency, which even Steve Vai wouldn't notice.
Then consider that if you're also recording at a sample rate other than 96kHz, you lose any latency advantage because you need to sample rate convert back to 44.1 or 48.
I can't imagine BOSS building their entire engine around 96kHz to save less than a few hundred microseconds in latency
Just confirmed with Brandon—Helix Floor, Rack, and LT are ~1.83ms from analog in to analog out. HX Stomp and Stomp XL are even shorter (1.17ms)
Analog in > Analog Out won't be affected, correct, but if you're recording via USB (or S/PDIF or AES/EBU if the modeler has it) and monitoring the output of your DAW, SRC negates any latency advantage of 96kHz—unless you're also recording at 96kHz, of course, which almost no one does.Nah, that's irrelevant. In-to-Out device latency will stay the same, regardless of the sample rate you record at (assuming that you draw an analog connection to another interface, which is at least what many people are still doing very often).
Very few blocks in Helix add any appreciable latency. The poly pitch ones do though, yeah.But that's only true for empty paths. From all I know, some blocks are adding their own amounts of latency (very obviously the pitch blocks do, but I think some more commonly used ones do as well). Pretty decent figures, though.
This isn't what DI's talking about, he's talking about the conversion latency which is typically 24 samples in+out. 24/48k - 24/96k = 250 microseconds.With the Zoom UAD-2 I'm currently using, at 32 samples buffersize I'm getting 4.2ms RTL @ 48kHz vs. 2.7ms @ 96kHz. With some additional I/O routings factored in, that's already within the "could become noticeable for mere mortals as well" realm. And within a dedicated OS, things should possibly scale a bit more evenly, too (as in getting half the latency at double the sample rate).
This isn't what DI's talking about, he's talking about the conversion latency which is typically 24 samples in+out. 24/48k - 24/96k = 250 microseconds.
I can't imagine BOSS building their entire engine around 96kHz to save less than a few hundred microseconds in latency
Analog in > Analog Out won't be affected, correct, but if you're recording via USB (or S/PDIF or AES/EBU if the modeler has it) and monitoring the output of your DAW, SRC negates any latency advantage of 96kHz
My point was that if you're recording and you're concerned with latency, 96kHz impacts latency (and sound quality) way less than unnecessary D/A and A/D conversions, and you should be running digital if possible. If you're not recording—that is, not dealing with additional A/D/As, DAW buffers, interfaces, control panels, and the like—anything under 4-5ms is a nothingburger.While true, rather little folks are doing so. I have been recording at some places using whatever modeler setups I was using at the time, and I never connected things digitally, not even with the Helix, which would've been easier to connect than other things I was using before.
If you're not recording—that is, not dealing with additional A/D/As, DAW buffers, interfaces, control panels, and the like—anything under 4-5ms is a nothingburger.
About helix paths/cores synchronization - if I play with powercab AND real cab I have two paths - one with IR for powercab and second without for real one. Are they in phase? Generally speaking if two paths have different effects sets will they be synchronized at the output?
Please add poweramp simulator
I can't RTFM my way through this but how to make helix auto assign bypass to footswitch as soon as I add new block?
Please give us global blocks
In headrush it assigns to the first free one. Very handy for quick experiments. And as all UI/UX shortcuts takes only that little time manually yeah. I'm very proficient at hitting Save twice for example. All my presets are New.While I'm all for UI improvements, how would the Helix know which footswitch you'd like to use? Besides, if anything, assigning bypass to a footswitch takes around a second (in case the unit is in reach).
I'm far from DSP field but I guess IR length dictates segment size and n in O( n ). That's why it can limit number of 2048-point IR - knowing length gives estimation of loadI guess this would be difficult as the Helix can't guess what the IR is doing.
I'm far from DSP field but I guess IR length dictates segment size and n in O( n ). That's why it can limit number of 2048-point IR - knowing length gives estimation of load