Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation on 08/23/2020 in all areas

  1. 3 points
    It's not clear what you mean. If you mean "why isn't there a looper in all the patches?" then it's just a patch so you can modify it by adding a looper. If you mean that you see patches where you cannot add a looper, it's probably that there are already too many blocks in the same line, or to many super consuming blocks. Basically think about the top and bottom lines are 2 processors, they need to be able to process the audio of what you make them work with. Helix will prevent you from adding more work than that processor can work with. You can fix this either by removing another block, or by serializing both processors: make the output block of the top line go to the input block of the second line. Then you need to move the blocks to balacne the work on both processors.
  2. 1 point
    SY-1 takes only taps. Micro or smart clock handles taps and midi to integrate.
  3. 1 point
    Lower your expectations and you’ll never be disappointed. :)
  4. 1 point
    Global Settings -> Footswitches -> Knob 1
  5. 1 point
    Modern MFX devices like the Line 6 Helix, Pod Go, Mooer GE300, Zoom G11 etc all use 'dynamic' DSP rather than 'static' DSP. If you are used to 'Static' DSP units eg Vox Tonelabs, Boss GT3/GT5, Digitech RP6 etc etc then it does require a 'mind shift'. The aim is to give you much more choice and control, and way higher quality amp, cabs, effects etc rather than a more limited selection, so you choose what models to select. Heavy DSP users are eg spring reverbs and certain amp models eg Jumped Plexi. Once you get your head around it, it's actually rarely a problem because by changing eg a spring reverb to a room or chamber reverb, or choosing a different amp eg a non-jumped version, you free up DSP. to use elsewhere. Think of it as having a container that can hold up to a litre, but no more. If you choose a room reverb, that will take up more than a third of your container. If you went for a room , hall, plate or chamber reverb, it would only use up 13.6% of your container. A multi-head delay would use 25% of your container, but a simple delay would only use 7.6%. A Brit Plexi Jump amp would use up nearly 41% of your container whilst a non-jumped Plexi, JCM800 or Marshall Super Lead 100 are around 34-35%. But a Supro amp uses up less than 18%. And so on. There is a really good chart that Ben Vesco put together (see link below - look at the Pod Go column) & he has a youtube video explaining all this. When I first discovered this, I also thought 'WTF' and there's a post of mine here on this very subject. But in practice, when creating patches, I rarely have any issues. But if you choose the heaviest usage amps, reverbs & delays/FX you could find that you run out of DSP quite quickly and rather than having (up to) 4 user blocks you might be down to 3 and in extreme cases 2. The thing is to go by what you hear and like rather than assuming a spring reverb is 'best' (trust me, there are other great alternatives!). But there are lots of forum and you-tube 'tricks' to help you get the most out of your DSP allowance - eg using an EQ as a distortion boost, and instead of adding a distortion boost for that lead solo, kicking in amp gain (even with different EQ settings if you want), and instead of loading 2 delays (one long, one short) you can use the same delay for both by changing the delay time, mix settings etc all via a single footswitch. You can use snapshots to bring these changes in and/or use stomp footswitches - and In this regard I have two extra footswitches connected to give me even more flexibility here. As you get to learn how Pod Go works (and do watch tutorials/vids - there's a ton of info out there!) you'll realise how flexible it is, and the DSP really won't be a problem. Pod Go's a brilliant, very flexible & high quality unit that gives you (except for 3 very heavy DSP models) exactly the same models as Helix. But it's been designed for a particular market sector at a more budget cost and because it only has a single DSP chip, there are some compromises - so if you want the extra processing power, plus the ability to run more than one amp/cab, and more than 4 user blocks, you'll need Helix or Helix LT. but these are more expensive, and are a lot bigger and heavier! Most users agree that the display on Pod Go is actually better, and there have been more than a few Helix/Helix LT users who are selling and buying a Pod Go because many users are simply not using all the extra things these units can do, and want something smaller, lighter & simpler to use. https://benvesco.com/store/helix-dsp-allocations/
  6. 1 point
    Thank you datacommando, Line 6 says "use DC3 power supply only" so they just miss in the manual " for French users if it's broken put pour you HX in trash" Thank you Line 6 !
  7. 1 point
    I think the idea of this isn't necessarily (if at all) to get a true FRFR sound but rather being able to make use of patches created under FRFR conditions (through studio monitors, headphones, standard FRFR monitors) but at the same time sort of "inject" a certain guitar cab alike behaviour to them, whatever that might be (directivity, the way the cab resonates, the way it creates reflections, etc.). Gotta say that I find this to be an interesting or valid idea/approach (probably not for me, though, I'm absolutely happy with standard FRFR monitors).
  8. 1 point
    I have a powered FRFR. Headrush. I have some nice custom cabs basically. This is what I am talking about doing...
  9. 1 point
    I finally figured it out. As usual Operator Error. Operator unable to fully comprehend incomplete/vague manual. What the manual doesn't properly explain is the concept of DISCRETE OVERDUBS and LAYERED OVERDUBS. Yes, I made up those terms, to describe the way the Looper actually works. Once the initial loop is recorded, if you press RECORD/OVERDUB it SAVES the initial loop and goes straight into OVERDUB mode. You can record as many overdubs as you want, but if you press UNDO it deletes them ALL, leaving just the initial loop. If you press PLAY/STOP, the initial loop and the LAYERED OVERDUB is SAVED as a DISCREET OVERDUB. That overdub can be deleted by pressing UNDO. If you record further overdubs and press PLAY/STOP, THOSE overdubs, simple or layered, are saved as DISCREET OVERDUBS, become the most recent, and will be deleted by pressing UNDO, leaving the initial loop and any previously saved overdubs. As long as you press PLAY/STOP between overdubs, a DISCRETE OVERDUB is created, and UNDO will delete only the last SAVED (DISCRETE) overdub. I hope that makes sense. I know, all the smart cats figured this out themselves long ago. Maybe because it's how standalone loopers work? Dunno, never used one. However, I do not think that this is intuitive. The manual could have gone a bit more in depth about the process. If it did, and I missed that part, point me to that part of the manual, I don't see it. As for me, I'll continue to use Reaper for loops. Much easier for me to deal with. Besides, I can never time the button presses right! :-)
  10. 1 point
    I can get it to work with the just the double-tap on the 1Switch looper but I have to get the timing just right. It's like having the double-click interval on your mouse set too fast so it often fails to double-click. Its timing should almost be a settable parameter. Of course if they do that then people, particularly those who set a slow/long double-tap interval will complain that the end of their loop isn't restarting in the right place at the right time(modified Dr. John). Maybe a double tap is not the best way to do the stop command but not sure how else you would do it if you truly want to keep all the functions on one switch. In other words, for a one switch approach, without quantizing the loop's end-point, or perhaps some very clever switch logic, if you grant the user more latitude on the double click it will also impact where the stop is detected and potentially make for a loop end-point that is slightly off.
  11. 1 point
    1 Footswitch looper bug: If I set up the 1 swtich looper, I can punch in fine and then punch out. I think the problem is with the double tap to stop the loop. It seems to have trouble reading that and just goes into record for an overdub. then if you do get it stopped after a few attempts. If you long press to erase the loop the led stays lit. So in general there are some things going on in there. This acutally got me thinking. It would be nice if Line 6 could offer long press and double tap as an option for programming footswitches. Especially for command centre which I use to control my voice live rack for vocal harmonies etc. It would be really nice to have the harmonies set to momentary... but double tap would turn them on and off all on the same footswitch.
This leaderboard is set to Indiana - Indianapolis/GMT-04:00
  • Newsletter

    Want to keep up to date with all our latest news and information?
    Sign Up
×
×
  • Create New...