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

lcphill

Members
  • Posts

    5
  • Joined

  • Last visited

Profile Information

  • Registered Products
    1

lcphill's Achievements

Rookie

Rookie (2/14)

  • First Post Rare
  • Conversation Starter Rare
  • Week One Done
  • One Month Later
  • One Year In

Recent Badges

0

Reputation

  1. In 1987, I became proficient in vi (remember vi?). It got to the point where I just hit keystrokes and jotted down the effect. That's how I feel about the pod go (and probably all things helix). Just hit and/or hold buttons and twist knobs -- like a 2-year old -- and see what they do. (moving to Unix from DEC/VAX/JCL was fun, and I won't even bother to lament about keypunch). On some level, I miss my Pod-XT-Live (remember guitar-port?).
  2. Hi, I've perused some of the posts, but I am making yet another snapshot/wah post, being long past the point of frustration. What I may state below is snapshot as relating to the wah block, so some other block kind may behave differently as the wah block seems "special" in its programmed/factory -- as parlayed to "user" -- behavior. - snapshot bypass (on/off): This appears to factory default to 'on' (and I'm not sure what on versus off even means, since I am playing with this and I can make out what the actual effect of the setting does... at least, when using the wah block). This parameter is ineffective, regardless of setting (on versus off), as I traverse snapshots because the enable/disable state of the wah block supersedes position. Speaking of position... - The position, as on every factory preset (although, I see to only be able to scroll through user presets as 32D goes back to 01A), for the wah block is already in the "white color", which signifies snapshot override. - If I hold the action button and press the position, so as to remove the snapshot specific setting, then the epx1 pedal movement has no effect. To Line6: All this snapshot and wah stuff is a mess. - What is global and what is not global? The manual seems to state that snapshot settings are per block/model. Yet, I have to hold down the left-and-right "page" buttons to get at the snapshot settings. I'm sure there are a bunch of other "oh by the way's" and "gotcha's" that I left out. As for "pod go edit", I try to avoid that (well, at the current moment, pod go edit is not even installed, as my SSD drive failed after only 18 months and I'm starting out on a new laptop once again... deep breath), as I am tired of having to control guitar pedals using a phone or USB (that got old a long time ago). // Vent over...
  3. Hi, Does the Pod-Go have a compressor model that provides the built-in compressor found in the Pod-XT-live? I grew very fond of the compressor built-in to the Pod-XT-live. On the Pod-Go, I've been lightly surveying the numerous compressor models and other boost oriented effects (to include "heir apparent"), but I have not found anything that seemingly approximates what I had on the Pod-XT-Live. I recall some post somewhere that said the compressor that was built-in to the Pod-XT-Live to be some "studio compressor" model, but that statement is rather generic. // Thank you.
  4. Hi, First, I will note that I can have my wahwah effect set on/off on a per snapshot basis (that is, bypass or not-bypass, per snapshot -- in my case / in the default case, via the exp-toe-toggle). That is, I can have the wahwah off for snapshot1 and on for snapshot2. Unfortunately, on a per snapshot basis, that is about all I can do with the wahwah pedal settings (this issue may also apply to other effect units, not just the wahwah). I would like to be able to control, on a per snapshot basis, the (initial) position of the wahwah. Further, it would be nice if I could set the min and max values for the expression pedal on a per snapshot basis as well (it appears that min / max are only settable for the entire patch as a whole -- that is, all snapshots must adhere to the same min/max settings for the entire patch). Final note - I tend to avoid pod-go-edit. That said, on the pod-go unit itself, I cannot find the "snapshot bypass enable" setting. I would think it should be editable on the pod-go unit itself, but I cannot seem to find it (I did find it on the pod-go edit software). // Thank you
  5. Hi, I am paying attention to mono and stereo routing, which includes paying attention to which models are stereo and which models are mono, along with settings (such as the effects loop). The way I am using the effects loop, it is invariably "send mono" and "return stereo". I have purchased the requisite cables for proper breakout. That said, the first question: 1. Can I or how do I "send mono" when the effects loop is set to stereo? The way I am doing it is to use a mono cable for "send mono" and, of course, I am using a "stereo breakout / break-in cable" for "return stereo". In general, I am placing the effects loop behind a mono signal path (not always, see next question). 2. I was surprised to find that the wah and volume models are stereo, yet they are placed -- by default -- up front in the block/signal chain. That phenomenon is, in most cases, negated by a mono sum as going into an amp/cab/ir chain (be it a built in model, or by way of effects loop via x-cable method). I guess that the stereo/mono routing is not entirely applicable to, say, the HX where multiple-signal paths can be configured, but applicable to things like the pod go (not a complaint, per se). Number 2 above is not a question, per se, but an observation. However, there is a question here: What if I have wah/volume routed out the effects loop, in which I have a mono cable for "send" ? Does that mean that the effects loop send is the "left channel" (or right channel, or pick one... sort of -- that's question number 1 above). While here, since instrument-in is mono, it would make more sense -- that is, if you plan on running a full stereo chain to the outputs -- to put the "stereo volume" model block behind the stereo-wah model block (if the volume pedal is directly following instrument-in, it is invariably mono, depending on the model characteristics and settings, of course -- such as "pan" or field-width). The first question (question 1) is probably the most important question for me. Thank you.
×
×
  • Create New...