Please ensure Javascript is enabled for purposes of website accessibility Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Posts posted by zolko60

  1. Cab (not Amp) - corrected.
    So I am wating for bridged impedance value and "knowledge from L6 that this is 100% safe without damaging the unit" while playing my favorite speakers ;)
    Maximum headphone amp power at some load impedances was the casual thing stated in specs. But I can haven't found specs for Helix LT nowhere. :(

  2. Maybe this tip can be helpful for some midnight home players.
    I have noticed that Helix headphone amp has plenty of power, took a look at manual and found out that it has 12ohms impedance. So I connected 8ohm guitar cab to headphones output and disabled  Cab/IR blocks. It works and sounds as it should! Like 1-2(?)W amp. Even too loud when you don't want to disturb your neigbours. I like it even more than when connected line to fx return of my tube amps set so low. There is no coloration and EQ curve already emulated in amps models but definately the speaker is as real as could be and the feeling of monitoring through real guitar cab is "that feeling".
    Now i have to solder TRS to TS jack cord to bridge L/R power and lower impedance to 6ohms.
    Try this at your own risk of course ;)

  3. So what is Volume Control?
    Digital attenuator/booster before DA converter which I can assign to Multi Output as a master fader for XLR/1/4/AES/USB1/2out or as master fader for individual outputs (after their faders in Output Blocks)? Where is its unity gain setting? What is it's maximal boost? Why have I to find it out by experimenting? I know how few people read manuals, but I would appeciate adding couple of sentences more.
    BTW. When can I find specs like Input/Output impedancies, Full-Scale Input Level for Helix LT?

  4. Yeah, indeed! Ben Adian is the Cartographer amp designer and capturer!
    Ben took a lot of effort in showing us how different cliping diodes work in his circut. This is great for me!.

  5. Have you ever heard your amp through mic/IR and your monitor/headphones only?
    If not, get the reactive load box and connect your amp to Helix and monitor. Use path 1 for your amp and path 2 for Hx emulation. Check if you can find IR that suits you, compare and tweak emulation to get the sound you like.
    If you can not find IR that make you feel comfortable - make your own. Take your amp to the studio or to the basement and capture IR using flat response power amp.
    If you can not bare the sound of miced and monitored amp/cab (I know guitarist who can't) so the future of your relation with any amp modeller (as replacement) is hopeless :(

  6. 1 hour ago, DunedinDragon said:


    Well you hear wrong.  Helix cabs are not a mixture of mic placements relative to the speaker cap.  They are dynamic, programmatic model implementations that simulate the behavior of IRs and that's why they take up less DSP usage than does a typical IR.

    How can I check Cabs use less DSP? When the DSP usage is almost full I can add either one Cab or one 1024 IR. When full I can not add neither Cab nor IR.
    EDIT: I got it! It's opposite to what you claim. When I exchange Cab with 1024 IR in heavy loaded Path, my choice of Dynamic DSP block count is 4 instead of 3 and 8 instead of 7 in case of Modulation block.
    Checking "dynamic, programmatic model implementations that simulate the behavior of IRs" shoud be simple . When I have some more time I will capture Helix Cab to IR and compare them side by side to find out what it means.

    Edited: Speaker "cap" instead of "cab" axis. Sorry for misleading.

  7. What I hear Helix cabs are mixture of the different mics placements relative to the speaker cap axis. This is why when I need more "on my face" sound free from phase interference I look elswere. Hx Native install weights 20MB while single Redwirez cab collection @24/48 IR is 6-10MB. Divide it by the number of "saved axis mics placement's". Let's assume 2/3 of mic distances" are on the fly DSP interpolations. It's still 2-3MB per cab. There are 30 cab's - 60-90MB. When squashed with 10:1 lossy compression it could fit the installer.

  8. Oh, really? They indicate?
    So why when I load eg "2x12 Double C12N" Cab with R121 mic, 3.0 distance I can make almost the same sound mixing Redwirez TwinJensenC12N-R121-CapEdge-3in.wav, TwinJensenC12N-R121-Cone-3in.wav and a little bit of TwinJensenC12N-R121-Cap-3in.wav?
    Did you ever use impulse responses of the same cab type made by different people in different studios? I did. It is always totally different story.

  9. Thank you. Looking at two photos one can feel it is the same picture, doesn't he? IRs like a digitized photos or other soundfiles - you can alter them, process them but to some degree there is a feeling this is this and not something else.  So I am asking people who did compare them and can share their experience. I am not conspiracy detective. Just curious and always willing to check if I can trust my ears.

  10. Like thousands od other Helix users I had a feeling that Cab DSP blocks are not good enough. So I used to search better sounding IRs. While searching through Redwirez Big Box I discovered that Helix Cabs are in fact Redwirez cab IRs. They does not sound exactly the same - maybe mixes of different mic position, maybe compressed with some loose algorithm but having experience in using IR's and studio cab micing, I am almost sure I can hear the same cab captured. I mean the same cab the same method, path and postprocessing - this what IR capturing is all about. Eg. Helix 4x12 Greenback 20 is Redwirez BasketweaveG12M20s and so on.
    Anybody with the same feeling?

  11. What I am experimenting with right now is using USB 3/4 out as output for Path 1A, insert whatever plugins on DAW/Host Stripe having USB 3/4 as input and USB 3/4 as output. Then I use USB 3/4 in as Path 2A input. This is workaround for lack of adressing USB busses to FX Loop DSP blocks in current (2.7) firmware.
    Second "FX Loop"  I do just using of built in summing USB 1/2 input on Multi Output. Making a Y split at the end of Path 2 and setting 2B out to USB5/6 and setting DAW channel stripe with USB 5/6 in and USB 1/2 out enables me to use reverbs and delays set to 100% wet.
    I can not imagine any use of USB 5/6 and 7/8 inputs in current firmware for what I try to do and when 1B is used for internal routing. There is simply no path left to assign it to. Please correct me if I am wrong.
    The drawback is latency. While Helix is great interface concerning AD/DA quality, it is not very fast.
    Round Trip Latencies are:
    21ms on "Small" 128 samples buffer@48kHz
    17ms on "Extra Small" 64 samples buffer@48kHz
    15ms on "Small" 128 samples buffer@96kHz
    10ms on "Extra Small" 64 samples buffer@96kHz - but this setting is unusable because of artifacts


    I always think of latency as a distance from cab/monitor. 15ms is 4,5m - not very far but in case of delay/reverbs on "FX Loop 2" their predelay is doubled to 30ms.

    Speaking of Amplitube: Some of its amps, cabs and stomps are really good. Their emulation od EHX Electric Mistress is so much better then that in Helix. Small Stone is even better than my EHX nano version. That is what I would use Amplitube for, but there are tons of great plugins to widen Hx plugins/blocks offer and add DSP power to your rig.

  12. For existing Helix Floor/LT:
    - More looping SubPaths (1C, 1D, 1E)

    - Feedback routing for loop paths
    - Routing of Send, Return, FxLoop blocks to USB busses
    - Some new decent XXI century quality sounding reverbs (or New Old Stock refubished Modern Vintage emulations ;)

    For future version:
    - Lowering weight to 1kg while preserving footprint
    - Self containg folding roadcase with handle
    - touch display covering >50% of the unit surface
    - 6 hours built in battery operation
    - Ten/twenty times more processing power
    - Additional heel switch for EXP pedal
    - Touch activated EXP pedal switch
    - Wireless communication for MIDI/OSC controll
    - Additional wireless receiver for guitar input (while transmitter should still be optional for 200$ ;)
    -  Audio network interface (like AES67)
    -  Routing of Send, Return, FxLoop blocks to audio network busses
    - Loading of VST, AU, AAX, UAD, Strymon plugins as DSP Blocks (virtual instruments too of course)
    - (Let's hope Kemper like impulse technology will be finally common as software)
    - Lowering Round Trip Latency to microseconds range
    - Infrared "theremin like" foot or hand controller (or two of them ;)

    - "Find my Helix" feature
    - "Find me The Preset that make me famous and rich"  feature
    - "Teach me how to play" feature :D


  13. "IMPORTANT! You may change presets while looping, but loop playback will
    stop unless the preset you select includes the same type of looper block (mono
    or stereo) on the same path (1 or 2) and is assigned to a footswitch"
    Manual, page 13
    Hard to say what you are missing. Try on first two factory presets (loop works there after the preset change) and check what is different.

  14. My two cents: I have been using Helix Native for more than year with small USB interfaces at home with DT770 which I like and use both home and in studio. Now on Helix LT - what a difference! This thing has great AD and DA converters and/or (?) headphone amp. I feel it like it is comparable to hi class studio audio interfaces.

  15. Really? I have not upgraded from 1.6 to 1.7 yet but maual states: "Mac Computers: • Mac OS X 10.10 and 10.11, and macOS 10.12 and 10.13 • 64-bit AAX Native, Audio Units (AU), VST® (VST2 or VST3) host DAW software • Supported sample rates: 44.1kHz, 48kHz, 88.2kHz, and 96kHz Windows Computers: • Windows 7 SP1, Windows 8.1, and Windows 10 (64-bit versions only) • 64-bit AAX Native, VST (VST2 or VST3) host DAW software • Supported sample rates: 44.1kHz, 48kHz, 88.2kHz, and 96kHz"
    I could not make Ableton see 1.5 version (no trick worked for me) but 1.6 contains both VST2 and VST3 and works good.

  • Create New...