Jump to content

malhavok

Members
  • Content Count

    220
  • Joined

  • Last visited

  • Days Won

    5

malhavok last won the day on January 4

malhavok had the most liked content!

Community Reputation

138 Good

About malhavok

  • Rank
    Iknowathingortwo

Profile Information

  • Gender
    Male
  • Location
    Oregon, USA
  • Registered Products
    7

Recent Profile Visitors

887 profile views
  1. There's nothing wrong with using POD through a hub except that there's tons of super-cheap and crappy hubs. If you have one of those then you're just asking for trouble. If you've got a great and reliable hub then no problem.
  2. That most important rule is to make sure your DAW is feeding your dry signal back to POD at exactly the same level it was originally recorded at. Try re-amp though an empty preset with no active blocks. The dry re-amp'd signal should be exactly the same volume as your original dry track. If it isn't, then your gain staging is messed up somewhere and that's the first thing you need to fix.
  3. @billjolly the "jumper trick" can work on POD Go. Just be sure to set FX return type to "Return" and not "Aux In" in the global settings. Also, be sure the loop is set at 100% mix and placed before the amp.
  4. Spillover is a neat feature that only the original read bean POD and the POD XT had and no other Line 6 unit had until Helix got the 3.00.0 update. It's less to do with requiring two DSP chips, per se, and more to do with requiring two things: Both presets (the one you're coming from and the one you're going to) must "fit" simultaneously in your overall DSP "horsepower" available. In simple terms, the only way to guarantee it is to limit any preset to use no more than 50% of available power. On Helix, this is easily achieved by limiting each preset to a single DSP chip. Then, you must also be able to process all available channels of both presets simultaneously. This is the stickier point. A POD Go preset has two channels (left and right) so to support spillover, you'd need to not only limit 50% of the processor per preset but you also now need to be able to process four channels (L+R of both presets) simultaneously. On Helix, a preset on a single DSP has four discreet audio paths (L+R for both A and B paths) so spillover is again easily solved by "per DSP" processing of each preset which subverts the need to process eight channels of audio on the chip. It is not known to me if POD Go's DSP could process four channels of audio simultaneously. Even if we assume it could process two L/R pairs of audio, we'd still be limited to 50% of power. That means you'd sometimes not even even be able to fit a delay or reverb as the amp+cab together can often take the full 50% of power. How did they achieve it on the old PODs then? Well, those did not have dynamic DSP. The original red bean did not even have delay "models" and just had what you might think of as a global digital delay that could be on or off on any preset. Its position was not assignable. It was in a fixed position in the signal chain just before the reverb which was also across all presets and fixed last in the chain. On the XT, my recollection is also that spillover really only worked correctly with delay in the "post" position and that when some other "global" type of feature was introduced introduced (in an update) you could either have that feature or delay spillover, but not both. No Line 6 unit after that ever supported spillover until Helix 3.00.0 release. The trade-offs to support spillover are large. You can trivially support spillover if you sacrifice either a great amount of power or a great amount of flexibility. I think it's great we have the option to choose behavior on Helix but I'm skeptical we'd ever see it on POD Go. Though, I can think of a way it could be done if it required the delay to always be very last in the chain and always be a fixed delay model... My personal vote would be for other features instead of spending time on that.
  5. They're definitely trying to position POD Go in this range of products. Notice the similarity to these Gearbox-era (and older) devices where the primary difference is they've allowed the stomp/mod/delay/verb to be fully assignable rather than fixed to those types of blocks. I'd love to see a "POD Go Pro" or something that gave us a whole blank slate to work with but also "get" the market segment they're trying to address with this product. They've got HX-era modeling split into at least seven different segments already. Would their bottom line benefit or be cannibalized by adding an eighth segment or significantly expanding the overlap of a few of those segments? I have no idea the answer to that question but will always vote in favor of more freedom and more free updates to any of those products.
  6. malhavok

    Helix Looper

    Just tried it and can confirm if you put the same looper block in the exact same location that it absolutely does carry over into the next preset. This is on Helix 3.01.0
  7. After watching that vid, seems totally whack. Honestly, I'd try re-flashing and factory reset if it happened to me.
  8. Totally understand what you are saying. It just isn't what "dynamic DSP" means as a vocabulary term. Fixed DSP means something like all amp models use the same DSP regardless which amp you choose. POD Go just does not work that way. Every amp model chosen will dynamically allocate the amount of DSP needed. That's what dynamic DSP means. Dynamic DSP absolutely does not mean "freedom of choice" in all things. Helix allows for 32 blocks with full freedom of choice. It's easy to make a preset that uses all 32 blocks and still has not used up 100% of DSP power. Does that mean Helix doesn't have "full" dynamic DSP? Of course not. HX Stomp also had dynamic DSP just as much when it had six blocks as when it had eight. Similarly, you can still add all eight blocks and have not used 100% available DSP power. Dynamic DSP refers to the way DSP is allocated and apportioned and has nothing to do with how much of total processing you might be able to use on any given preset. If you're going to argue that all patches having DSP reserved for an EQ block means it doesn't have "full" dynamic DSP then you must concede that there are no products with full dynamic DSP. Helix, HX Stomp, HX Effects, they all have fixed blocks that cannot be removed and take up DSP whether you use them or not. For example, on the internal architecture (and this is reflected in patch building) the input and output blocks are truly "blocks" in every sense of the word. They take up space in the patch. They take up DSP power by reserving a fixed allocation percentage that can never be re-claimed or used for any other purpose. So either none of the Line 6 modelers have full dynamic DSP (and it's a fictitious term that doesn't actually exist) or they all do. Helix has eight blocks that can't be removed and take up DSP whether they are on or off. HX Stomp has four blocks that can never be removed and take up DSP whether they are on or off. POD has eight blocks that can't be removed and take up DSP whether they are on or off (and some of those take a variable amount of DSP unlike Helix/HX where they are all a fixed amount). I agree it would be awesome if POD let us delete every block in a preset and start from scratch.
  9. malhavok

    Helix Looper

    AFAIK, if you place the looper in the same place in each preset then it will carry over.
  10. malhavok

    LedRing colours

    Yeah, the three levels of "yellow/orange" from yellow, light orange, dark orange, can be challenging. I get it. It can be hard to come up with "that many" distinct colors that don't have some amount of overlap on the spectrum. I tend to always use my POD Go with the snap/stomp display and focus on that to remember what the switches are assigned to.
  11. My money is on us seeing acoustic sim included in the next firmware update along with all the new amp models. I'm also betting we'll see many of the new effects blocks but zero of the poly pitch blocks. It's all speculation. We'll have to wait and see.
  12. To be clear, neither Helix nor the HX Edit software displays the percentage. The term "dynamic DSP" just means a contrast with older PODs where you literally had one amp, one dirt box, one delay, one mod, one reverb, vol, wah, and cab. The DSP for delay was reserved for delay. If you didn't use delay it's not like you could use that power for a second reverb or drive pedal. It was perma-slotted for delay. Period. Dynamic DSP refers to the fact that if you don't use that slot for delay then you can use it for something else. POD Go has this (as do all the Helix/HX series and the POD HD series). Don't read too much into it.
  13. No sir. I was only offering an answer to the OP. No correction on you was offered or intended.
  14. So far, the Legacy section is ONLY for blocks that were ported from older-than-HX units. Any new delay models added would not be likely to cause other HX-class delays to move into Legacy. The one remaining exception are the wah blocks which are HD-class but remain in the non-Legacy section.
  15. @JamieCrain, agree wrt drop tuning on variax but I personally don’t use poly on helix for drop tuning either and for the exact same reasons. I’m not knocking it. It just isn’t my cup of tea. I wouldn’t hesitate to use either in a pinch but I tend to avoid those pinches. Another benefit of Variax drop tuning is saving 50% Dsp. YMMV and only you can say if your variax is no longer needed. Mine gathers dust (and is, in fact, listed for sale on Reverb as of last week but has nothing to do with Helix 3.0 as I haven’t really played that guitar in about 15 years). As for the useless and completely subjective semantics discussion, I wonder why articles like https://www.sweetwater.com/insync/easy-alternate-tunings-for-guitar/ never mention things like “Van Helen Tuning - down 1/2 step” as surely it’s the easiest “alternate” tuning that ever existed.
×
×
  • Create New...