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

PierM

Members
  • Posts

    1,660
  • Joined

  • Last visited

  • Days Won

    81

Everything posted by PierM

  1. Line 6 isn't reading your posts over here. If you want to ping them about that aspect, contact support. As for the drivers, I don't care anymore, I moved my DAW to MacOS and only use core audio. Bye Bye Micros**t. :)
  2. You can send commands to multiple devices just using the MIDI THRU on every next device, like Helix--->SY1000 (ACTIVE MIDI THRU)--->Vocal Processor Then assign a dedicated MIDI channel to each device to prevent wrong assignments, like Helix on CH1, SY1000 on CH2 and Vocal Processor on CH3. At this point all you have to do is to specify the Midi channel on the command so that only that specific channel will execute. You can send a command per footswitch, one per pedal and six instant commands.
  3. Dont know if it's being used in the Helix, but a direct substitute for the VOF6512 is the ECS65US12. Id contact support for a confirmation, even if they share exactly the same specs. https://www.xppower.com/portals/0/pdfs/SF_ECS65-130.pdf https://www.newark.com/xp-power/ecs65us12/power-supply-ac-dc-medical-12v/dp/67R9479
  4. PierM

    Future of Helix

    I wouldnt hold my breath. In more than 20 years I follow this brand, I dont remember a single core product copying something already existent in the market. In fact, it's pretty much the opposite. So, if any Helix 2.0 is in the plans, I believe will be something completely different than what you see around these days, and as the origianal Helix, will be probably looking to the future, not really to what people can already buy now from another brand. Honestly, if they'd release a Helix/HX Mark II, with same core but better construction, top quality parts and less chinese low budget components, Id buy it again and I would be happy. :)
  5. Be sure you are not hearing the picthed tone above the acoustic sound of the strings. :) Also, post a preset so we can check.
  6. I'd try to shape the attack through compressors and a bit of eq and see what you can get, not an easy task. Also depends on the nature of the attack. An heavy and thick pick produce a huge transient at the attack which may be really hard to hide to the Pitch Block. You could also try experimenting with a split dynamic block, placing the pitch only to path A and see if you can manage to send the attack noise transient to path B, without the pitch block. The hard task here is to isolate only the noise transient, without getting any harmonic mix between the two paths, otherwise you'd always get some harmonized transient...:) Split > Dynamic Settings Threshold; Any signal below the Threshold volume level is routed to Path A; any signal above the Threshold is routed to Path B. Attack; Determines how fast the signal is routed to Path B once reaching the Threshold. Decay; Determines how fast the signal returns to Path A once falling below the Threshold. Reverse; When on, reverses the path assignments (any signal above the Threshold value is sent to Path B, any signal below the Threshold value is sent to Path A).
  7. Unfortunately the HX and Helix won't listen for redundant PCs, so once a preset it's loaded into memory, it won't respond to that same PC, which means what's being selected and active (snapshots, FS, params, whatever editing), will stay there until you change preset (or reload from the onboard). Only trick I could think of, is to create an empty preset somewhere (like at the end of your setlist), and send a double PC for each preset (command, wait, command), first is the last empty preset, second is the preset you want to reload. This will send a quick double command, that it will force Helix to unload and reload the memory. That's some extra time gap I know...
  8. This sounds like you were plugging your helix and modeling in front of a guitar amp...which would explain the shrill and the entire tone chase. Anyway, whatever it works for you. :)
  9. Yes, guitar amp (5Khz range vs FF), the guitar (pickup, wiring scheme, pots values, caps, strings, nut, saddles, frets etc...) and - last - but not least - your playing and touch (style, skills, pick material and thickness etc), can make the difference. Especially between what you hear on youtube and your own room.
  10. Post some audio. All this talk without listening it's just a waste of time. It's like talking about the smell of clouds. Sorry didn't want to be harsh, but you use a lot of words, without going into details (that matters!)... On paper, a modeler will always be brighter than a guitar amp, even just because they are two completely different things, and one it's capped to ~5Khz, the other is capable of a full freq response, with mic response and room response involved. Plus there is the guitar, the pickups, your playing, the system you use to monitor and compare etc etc... That's a lot of variables that can't be analyzed through words...so yeah, I'd post some audio just to understand if what you are getting is in the normal and expected range, or you are getting something weird that needs further "investigation".. :) All I hear from that video is that his guitar is out of tune, and he's also adding a lot of extra dBs on the high side because he's saying base tone is too dark. :)
  11. IME the Helix/HX ASIO drivers never been good enough for live/low latency use. Even on high performance computers, I never managed to get a solid and reliable low latency performance. Something I could easily achieve with my Scarlett, or MOTU, or the little Jogg. Same story in MacOS. Core Audio works much better than L6 drivers. Again, this is just my own experience, in 8 years I do mess with these devices (I had the Floor, then Rack, now I only own the Stomp). On the other side, these drivers are perfectly good for standard DAW operations, where a super fast round trip isnt a requirement. The drivers are good and reliable, but not fast enough for live VST, that's it. If you really need to use VSTs for live, my suggestion is to find a product with better drivers for this use (like RME).
  12. There is no any possible chance to a things like that to happen; a +2 semitones polyphonic pitch shifting, ONLY HAPPENING after 9th fret. I wouldnt feed it, as the guy is probably laughing while lurking these answers. ;)
  13. Can you provide more info about those DI statements? :)
  14. Offline editing it's just a recipe for disasters, like preset overriding, setlist mismatches, broken database etc... Also what's the point to edit a tone that you can't listen? I don't really get it lol! Tuner needs an audio engine, and this isn't available in the editor (because it doesn't need one). It will never happen just because it's a technical nonsense. :)
  15. Block Level and Volume Block aren't really doing the same thing. Block Level is for gain staging, and it's linear. Also, since this is scaled as gain/boost, it has a huge range in dB, which force you setting proper min and max unless you don't want to make a hole on your ceiling when hits the +12dB. :) Also, since this is a gain, its variation it will change the behaviour of blocks after this one. Volume block is acting like a real PASSIVE volume pedal, with a 0/100 range, and can be set to work as a linear or log potentiometer. When assigned to a exp pedal (with correct specs) will act and feel as a real passive volume pedal. That's why they did this way, a that's why you can even choose between a Volume Pedal block and a Gain Pedal block. :)
  16. Try different USB ports. Dont plug the Helix into a USB hub. Use the shortest USB cable you have there. Dont run any audio/music software in background while updating.
  17. Use Snapshots instead jumping presets. You wont have a seamless preset change, even if you do a volume leveling between all of them. The pop and noise is mostly due the DSP memory unload and reload happening every time you change presets.
  18. And the Strymon guru, Pete Celi, was Senior DSP engineer at Line 6 back in the days. Small indeed! ; "When I started there (Line 6), Variax was really a blank paper project. They told me they wanted me to start researching how they could take what they did with [emulating] amps and do it with guitars, and two or three years later: “Hey, this actually works!” I wrote all the DSP sound generating code for the original Variax. Getting involved with that, writing DSP code for a product and being instrumental in shaping the sounds of that product really felt a lot more true to what I really wanted to be doing." Pete Celi.
  19. PierM

    Faulty Helix?

    Open a ticket and see what are your options at this stage. Could be just a joint failure or a bad connection, who knows without a proper diagnose. Good luck.
  20. I still believe the first variable here, before any further overthinking and overcomplicated paths, are the headphones you are wearing. I don't know the freq response curve of your focusrite bundle model, but I wouldn't be surprised to see a very "coloured" HiFi curve. I have two headphones that I trust even to do presets; BD 770 Pro 250 Ohm (if you need more juice, 80 Ohm is probably better), and Shure SRH840A 40 Omhs. The 770 is probably the most "flattish" of the two, but the Shure starts earlier to move on the bass range, and has a little notch on the bright side, which I love for cleans. When I do presets with these two headphones, I do mostly need small adjustments on the fly when using cabs or FOH, or just when changing location and volumes (that's pretty normal and expected). Of course depends on the base tone you use, but never had a "fizziness" issue with these headphones. If your base tone is some compressed modern HiGain, things are gonna be a bit more tricky to tame when using headphones for obvious reasons. o/
  21. There is not a simple answer to this question. Many factors are playing here, so first thing to address is; what headphones are you using?
  22. PierM

    Faulty Helix?

    This is enough to suspect a faulty unit. The randomness could just be related to broken semiconductors conductance at the joints and in the body, that make them working when cold and dying when hot.
  23. Yeah I believe he did that. There is no specific W7 driver for what I can see. It's just the same driver for W7, 8, 10 and 11. My bet on this is that new drivers aren't really tested or fully certified for the dusty Windows 7 (as they aren't for Windows 11)...
×
×
  • Create New...