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

grdGo33

Members
  • Posts

    439
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by grdGo33

  1. After some research, you can easily find true bypass pedals for 20-30 bucks but buffered pedals mostly start around 60, even a simple buffer pedal seems to start at 60.  Compressor pedals are more expensive and start around 110 for a BOSS, so if you want budget, distortion is likely your best bet as getting a buffer without a distortion is kinda silly if you can get a distortion pedal for the same price. 

     

    So if you want to go budget route, your best bet might be a Boss SD-1 distortion pedal.  Classic tones, versatile, and from quick research, it's more transparent sounding than a screamer, and so stacks better with other pedals.  (still mid boost sound though)  All reviews I've seen have been quite positive.  It's a classic design and they're all over the place used.  It's the Stupor OD in Go, so you can play with it without having it...  There's one nearby on my used local market, 1/2 off, I might pick one up myself.

     

    For more more expensive...  Honestly, I wouldn't bother.  You're buying the pedal as a buffer, and the Go has tons of distortion pedals and even amps, so getting a fancy pedal would be a waste imho.  What would you even be getting?  It would have to be something not in the Go's effects...  Horizon Devices Precision Drive is 220, so unless you're ALWAYS using the one in the Go, are you going to buy one to save DSP?  Friedman BD-OD is 200, but again you've got the real Friedman amp in the Go....   Maybe something like a BOSS OD-3, but that's twice the cost of the SD-1, but maybe the extra 60 might be warranted depending on how often you use it, though unlike SD-1, you'd be gaining a new effect.   (https://www.youtube.com/watch?v=w__tl6Wqt9M) 

     

    It's annoying that sites don't let you filter true bypass vs buffer...  Anyway, BOSS I think is your best bet from what I could gather, really haven't found anything else.  Really seem the king of affordable buffered pedals; nothing buffered near the price point. 

     

    And reading some comments on the above yt video, some do comment that the SD-1 is effectively a boost...  So yeah, $30-60 whether you buy used or new, getting a boost and PGO fix.  Probably a no-brainer for all PGO users without a current PGO impedance fix.

     

     

  2. So what would be some of recommendations to use as a workaround for the impedance issue?   Would you rather go for a compressor?  Boost or overdrive/distortion?  And what would be some recommendations in the budget, normal and fancy ranges?

     

    Short thoughts; DSP wise boost/distortion/compressor seem to have similar costs, so not much gain to have there, and compressors can be used after your amp, so maybe boost/distortion makes more sense.  But, you'd have to find a boost/distortion that you really like, and that will either replace a Go block, or might work well with stacked Go blocks...

     

    Or do you think it's not worth bothering since you don't feel it affects you much or you have found some workaround?
     

    Spoiler

    So basically; plugging a guitar directly in a Pod Go is not optimal.  Impedance issues;  see

     

    https://line6.com/support/topic/57670-pod-go-tonesuck-through-my-tweed-amp/

    https://line6.com/support/topic/63825-any-official-response-on-pod-go-impedance-issue/

    https://line6.com/support/topic/63488-problemas-de-impedancia-en-pod-go/

     

    https://www.youtube.com/watch?v=Ykezs1A7PBE

     

    Short version, from my understanding, anything with 'true bypass' will not work as to resolve the issue, but pedals with a buffer, aka buffered pedals, will work as a workaround.   (Turning on a true bypass wouldn't work either correct?)

     

     

     

     

     

  3. On 5/18/2022 at 10:40 AM, poodad said:

    Someone on the facebook Pod Go group posted a snippet of the Go's schematic clearly showing a 1nF capacitor shunting the input to ground, and a picture showing the location of the offending cap (C126 if memory serves). The post was removed within hours - Line 6 probably threatened legal action.

     

    Wow........  How dare they post a schematic..............   Must threaten legal action!

  4. Also, with the multi function described above, more realistically; you could have ex;

     

    S1 = overdrive/clean

    S2 = chorus on /off + low settings

    S3 = reverb on/off  + low settings

    S4 = delay on/off  + low settings

    S5 = high settings for chorus + reverb + delay settings (doesn't on/off, just changes parameters)

    S6 = wah or boost or whatever

     

    That way, you could say hit S1, heavy drive, press S4 to engage delay, then hit S5 to boost it.  Then hit S3 to engage reverb with low settings and hit S4 to disable delay, then later S5 to boost the reverb, etc.   Then hit S3 twice to reset the reverb to low reverb settings.

     

    You could probably do some neat stuff using similar techniques.  But then again, KISS is very likely the way to go.  You should question the necessity of going with a more complex setup like this...   But yeah, doesn't seem that bad, seems like it would be usable and useful!

     

  5. Hard to understand your post.  Would have been easier with notation

     

    Switch 1 =  xyz

    Switch 2 = xyz2

    etc.

     

    The way I see it, sure, the Go is limited, but what you're trying to do seems unreasonable.  You can setup 4 snapshots, so you can theoretically setup 4 'sounds';  a sound for the verse, chorus, solo and maybe bridge or intro or whatever.  That seems pretty reasonable...

     

    If you want more,  you could probably bind the expression pedal to ex; delay length, % of chorus, drive, etc., which could likely give you an extra way to configure your sound per snapshot.  Think that should work.

     

    But also, you can assign multiple functions to 1 switch

     

    1st switch:   6/10 drive + reverb 50%

    2nd switch:  7/10 drive + reverb 30% + chorus on with 50%

    3rd switch:  3/10 drive + reverb off + chorus on with 70%

    4th switch:  reverb on +  reverb 60% + chorus 50%

     

    So you can press 2nd then 4th and it just applies the binded values, giving you multiple ways of managing effects; like turning on/off and adjusting values without resetting everything 'per view' as per snapshots.   Pressing 1 then 3 would give very different results than pressing 1 then 2 then 4 then 3.     But then ........  I guess if you workout a system where that works better than snapshots.......  But yeah seems like it would just be confusing and just things much more complicated than they should be, for maybe not a whole lot of practical gains. 

     

    KISS = Keep It Simple Stupid.

  6. On 4/16/2022 at 2:41 PM, droonster said:

    Did it right away. Just wondering if this has happened to anyone else and maybe there is an easier fix then sending off.

    Don't have the link, but you can try to reset the unit to factor settings, but if it's 'bricked'; not visible by USB because it crashed at startup, there's also a key shortcut to start the unit in debug mode by pressing some buttons during startup, you could give that a try, it if boots up, maybe you'll have some luck restoring factory settings or something.

     

    Been reading the forums for a while, and I think you're the 1st case of white screen I've seen here yet.

    • Like 1
  7. Wow good job so far!  Sadly, well beyond my competence!

     

    Quote
    compressed zlib size in bytes (size)

     

    Quote

    Archive Section Data

    The data part of each archive section seems to be obfuscated, compressed and/or encrypted.

     

    As it's firmware, I have absolutely no clue what anything would do; without even knowing the language, how it's used to interact with likely proprietary hardware/controllers/whatever, I would be absolutely zero help, really not my cup of tea.   When you're dealing with proprietary software/data, the formatting & bytes can be absolutely anything.  Some as you said delimited by indexes, set lengths, maybe pointers, honestly, I would have no idea how to go about reverse engineering everything ...!

     

    Hell, it's firmware, so as far as we know, it's compiled code formatted for Line6 chips, so there's no way to unzip or make any sense out of it other than de-compiling as I said earlier and recompiling...   Just not human readable/manageable data format.

     

    Quote

    I'm still trying to be able to rename the amps and stompboxes.

     

    Honestly,  you get used to the amp names very quickly.  LOL   Making your own custom/hacked firmware just do that.....................     Playing with JSON patches, sure......  But Firmware is on an entirely different plane of existence for difficulty!

    • Like 1
  8. On 4/7/2022 at 7:21 AM, BarkingSpiders said:

    I'm currently also trying to reverse engineer the firmware (.hxf file), as I'm still trying to be able to rename the amps and stompboxes. I managed to identify various chunks and archive sections, but I don't seem to recognize the used encoding for the various archive sections. If anyone here is interested in helping out, let me know and I'll post my findings on GitHib.

     

    How did you manage that?  What language is it even using?  Not sure what you mean for 'archive sections'.   The hxf is the firmware from what I remember right?  Likely is compiled, I know next to nothing about reverse engineering / decompiling / recompiling firmware, but normally, you'd need to decompile, modify the code and then recompile.  Just attempting to make changes to compiled code would likely not work, well, depending on what kind of software/firmware it is...  (pure guess here)

     

    The issue also is that every change you make might have repercussions; but yeah if you just change the label of the amp, that should not break anything... in the patches; references by ID seems like;  ex;

    @model
    :
    HD2_AmpPlacaterDirty

    but yeah anything else might cause compatibility issues between patches/updates...  Say you hack your firmware, something changes in patches or anything, next L6 firmware versions, will you be stuck and have to apply similar fixes/changes to make your patches compatible with the new firmware?

     

    Also, when comes time to pushing to the Go...  Again, far from being an expert, but there's been mentions of bricked units.  Modifying json patches is one thing, but firmware......  Even the patches, there's no guarantee that edited json patches will be compatible/work with next firmware...  It works now, sure, but if L6 makes some changes, who knows if such patches could cause issues ...

     

    Even for your 'hacked' firmware, depending on changes/compilation/whatnot, who knows what issues it could cause...  If you know what you're doing, ok fine, but if you're new at this, well, you have to start somewhere I guess lol

  9. What are you comparing?  Same amp vs same amp?  Different amps behave differently, so unless you're comparing the same amps...  

     

    Also, don't forget that with Go you're not emulating a guitar cab,  you're emulating a recorded guitar cab, so you're not going to get the same results as the same amp + cab in a room.  You'd be getting the same results as the same amp + cab as if you were recording it given a particular microphone.

     

    Also you may be experiencing placebo.  Lots of blind tests (ex; https://www.youtube.com/results?search_query=helix+blind+test+) illustrate that the sounds are typically very very close.  Very experienced guitar players can usually still tell the differences, but I'm not sure most guitar players could.  Sure, most would likely claim that they could.  But under blind conditions, I'm pretty sure many would be surprised that what they thought they perceived turned out to be placebo.

  10. So yeah, maybe a fun project, but...  As a programmer, lol, I think it would be more just a fun project rather than a useful tool.  Maybe switching LED color automatically might be useful, but then you'd have to export and re-import the patches, so unless you can do so automatically, might not be super useful, as that would be a PITA to do constantly; ex; after creating a patch.  Proably less trouble to manually set the LED color rather than export, run tool, import.

     

    I think practically, you could change the default color values of effects, what is called 'favorites'.  Maybe you can even do it in a Go setting, can't recall if it's possible or not.

     

    But again, your best bet would probably just be getting used to Go's colour scheme.  Don't try to fix the world; try to fix yourself.  ;)

     

    But yeah, for learning programming project, could be fun!   :D   And later on, once you've learned the basics, then you could apply it to more useful features, not exactly sure what it could be for Go, but you never know, could lead to something!

     

    What I'd be interested in doing, if I had not already an overload of programming, would be to 'attack' PGO Edit, and add in features such as add empty blocks, maybe have a tuner, but yeah that would involve some decompiling and that's a far greater PITA than just modifying JSON...  There's likely an API for the Go also, so building up on that could work; likely something like using wireshark to see how Go/Edit communicate together might lead to 'easily' decoding the communication between the 2 devices, but then you'd need to re-implement a GUI from scratch, BUT, yeah, if you could say use the tuner from Go, etc., turn on/off effects, maybe something like having a 'virtual' Go controller; not so much to edit, but maybe just bind some keyboard keys to footswitches, controlling snapshots, etc., could be very cool.  But yeah, that's a lot of hours of work.

  11. On 4/1/2022 at 7:41 AM, BarkingSpiders said:

     quickly checks all volume settings,

     

    Problem is that there's no 'normalized' volume settings.   With a certain amp and distortion pedal, with ch. volume and master volume at 5 you might get ear bleeding volume, whereas another amp with the same 5 would be barely audible.  So normalizing volume by programming would be a very complex problem to solve.

     

    Quote

    or is able to force identical colors for certain stompboxes.

    That should be pretty easy.  Modern programming languages all have libraries to load and save json files, so you'd basically define the structure of a patch (ex; patch contains blocks which can be of type X which contain X value), then changing a value and saving.  So you'd just loop through patches and change the value depending on type. 

     

    Or, you can just code in particular values to loop through and if the name/type or contains said property, change X value inside this object

     

    For the pgp format, it's json.  So nothing particular to do with that, you just save the json string in a file with .pgp extension and you're done.

     

    Quote

    force all reverbs to be green and always in the 4th switch position.

     

    Yeah decoding the format to work with snapshots and all might not be as simple as I recall, just loaded a random downloaded patch and the snapshot...    Data contains a tone object, and this tone object contains a controller, footswitch, dsps and snapshots...   https://www.jsonvisual.com/  displays everything in easily readable format.

     

    I think for Go you'll always only have a dsp0 with values, as the Helix has 2 paths, but Go only has one, the dsp1 will always be empty.   So dsp0 contains your patch settings.  Snapshots obviously contains snapshot info.  Footswitch contains footswitch info.  Not sure what's the purpose of 'controller', probably more related to Helix.

     

    Actually no, I think 'controller' defines how the effect is controlled via the GUI of the Go; so if you select a particular reverb, that reverb will have have say 6 settings, 1st called x, 2nd y, etc., with values min 0 max 10, etc., so basically; defines how once loaded how everything is controlled.

     

    So if you modify block order (ex; put reverb last),  you'll very likely have to modify this section, otherwise you're likely to encounter errors or very strange behaviour as ex; you'd be trying to assign reverb settings to a distortion pedal, which could result in random settings or make the Go crash ...  Ex; controller 2nd element contains Block 3 contains HBE, dsp0's 2nd element contains block3 contains HBE related values

     

    But yeah to alter the footswitch position, that would be footswitch section, but not sure of the logic, they contain a @fs_index but many have the same index, (ex; 1, 2, 3, 5, 9, 9) so my guess would be that 9 means no switch, and you likely have fs_index 1-6 for the Go's foot switches.  yep, that would make sense.  the fs_label is even there, obviously from Helix, but again not useful for Go.

     

    So yeah, you'd likely just have to modify the index.  Again, programatically, you'll have some issues, as you might have to switch or change to 9 an existing block at the footswitch 4 position you're trying to switch an effect to, otherwise, 2 blocks for 1 switch.  What if you have 2 reverbs?  Etc..  Just some 'edges' cases to fix.

  12. Yeah normally the IR needs to be in a particular slot to work, as described in the patch description.

     

    I don't recall if the Go validates just the slot # or if there is also the IR name saved in the patch, and if both don't concord, error message.  Either way, if the correct IR is on the right IR slot, and when you open the patch you can see that the correct IR is selected, just saving the patch should fix the issue, and if it isn't the correct IR, just select the right one and save.  If you don't have dozens of patches to fix, just fixing them manually would be faster than wasting more time looking to fix/troubleshoot the issue!

  13. Normally you'd want a guitar amplifier with FX in/out and connect with 4 cable method, but yours doesn't seem to have FX loop...  With 4 CM you use your amp's Amp section using the Go's FX out/in, so your amp is in the right spot of your chain)  Or, you could connect to a sound system, something like stereo sound system, studio monitors, FRFR speaker, etc.!

     

    But yeah, you're getting double amp and double cab with the Go blocks on, and if your amp has any distortion then all Go effects will also get distorted...

     

    But it should still work, if you're getting 'buzzy' sounds, it could be indicative of an issue, but no idea really what 'buzzy sounds' is exactly so couldn't really tell you!  Make sure to run your amp as clean and neutral as possible, and you could try also just using the Go's Amp section and bypass the cab section, since you're using your real cab.

  14. On 3/21/2022 at 11:57 AM, pianoguyy said:
    On 3/21/2022 at 5:46 AM, Numbat said:

    I can run the POD Go into my JC40 via the 4 cable method with the amp and sim disabled in the signal chain.

    Then for those times when I'm direct, I can activate my amp and cab sim of choice. 

    It doesn't really work that way. 

     

    Create patches for use with an amp. 

    Create patches for use without an amp. 

     

     

     

    Why would it not work that way?  4 cable method = amp passes through FX loop no?  So you can run with that and disable the IR/cab and the amp, since you're getting your 'amp' sound from the amp, and the 'cab' sound from the cab, you'd be fine.

     

    Then when you want you can turn off your FX Loop block; bypassing the amp, and activate the Go's amp and cab.

     

    So yeah it should work that way, I don't see why it shouldn't!

  15. On 3/18/2022 at 10:09 AM, Dazzer40 said:

    I have connected a boss rc 500 looper pedal to the pod go and it records the loop i make but then i want to change the patch from the pod go  it also changes it on the looper pedal ,  just wondering if there is a way it can record the sounds without them changing ? 

     

    you can set your FX Loop block at the end of the chain, and connect

     

    guitar -> Go -> Go FX out ->   Looper pedal -> Go FX in -> Go -> amp or whatever

     

    or you can connect your looper at the end of your physical chain;

     

    guitar -> Go -> Looper ->  Amp.

    • Upvote 1
  16. On 3/17/2022 at 12:17 PM, tribal123 said:

    Same issue here.. muddy tones.. i'm totally newbie in pedal effects and in analogic settings... can someone advise me a low budget pedal tha can act as buffer to buy?

    Only external pedal owned is a Wha VOX v847 but i don't think that can act as a buffer...

     

     

    Quote

    Vox V847 Wha Wha

    Based on the specifications of the original pedal developed by VOX in the ’60s, the new Wah-Wah offers guitarists the same legendary tone with the addition of AC power capability and a buffered input jack for preserving the unprocessed guitar tone when the pedal is not engaged.

     

    Plus, if you're sitting down, you'll be able to use both the Go's wah plus your Vox wah at the same time using both feet, giving you double wah, the wahssibilites will then be endless!!

    • Haha 1
  17. Have you read the manual?  Hum, ripple, etc., are very briefly covered there.  For some of the new effects L6 has some description with what the various settings do.

     

    Otherwise, this site has some details about a few effects;  https://helixhelp.com/models?categoryId=6   but often the settings are a bit generic and no info...  For instance, for compressors, the settings are somewhat standards so reading guides on compressors can give you the info you're seeking.

     

    You can also look at youtube for tutorials, I've linked a couple of useful channels in a thread a few weeks ago, but it got zero interest and is probably on page 2 by now.

  18. On 3/10/2022 at 11:59 PM, Eric2002 said:

     don't sound very clear and thaey dont have that "guitar punch you in the face sound" despite all the raving being sad online about this pedal. Honestly disappointed.

     

    Also, what are you outputting the sound with?   The speakers you use are critical for that.   If you're using quality speakers, studio monitors or FRFR you should be OK, but I've seen reviewers acknowledge the fact that it doesn't sound exactly like a guitar amp + cabinet in a room.

     

    And that's what you have to realize also.  The Helix/Go (and likely other FX units) don't try to sound like a guitar cabinet in a room.  They're trying to sound like a recorded guitar which you'd hear on an album track.  So by default, you're not getting that cabinet in a room sound.  So if that's what you're expecting, I'd think you can kinda get it, but that's not what you're getting out of the box.

  19. Also see the tone suck thread.  There's an issue wit the Go where if you plug in your guitar straight into the Go, it will 'suck' out the tone of your guitar, so you need some sort of pedal with a buffer between your guitar and the Go to get expected tone.

     

    The effect really depends on your guitar and playing style.  I didn't realize it at first, since when you add the Go's Amp, Cab or IR, the effects, your tone is changed by a lot, so the Go's 'tone suck' isn't that obvious.  Plus again, the more effects/distortions, the less noticeable it is.

     

    But if you just plug in a strat with clean tone and few effects that you're familiar with, that's when it gets really noticeable.  Pretty sure it's a defect/design of the Go, so you can't really fix it.  But yeah, it's like turning down the Tone knob of your guitar.

  20. 3 hours ago, voxman55 said:

    Do you have a router near your PGW that might be interrupting the signal? 

     

    Good point.  I assumed he was plugged in using a cable.  Does the issue only occur when using wireless or also with a cable?  When it's 'bugged', if you unplug the wireless controller, or plug in a cable, does it work?   Try to identify if it's just the wireless and Go works when plugged in via cable...

     

    You could also try  changing the settings for the cable + wireless, think there's a setting in Go to go from one to the other, so when it's bugged, if you switch the settings to cable, then switch back to wireless, does the sound come back?

  21. If you just want clean/transparent amps, you can just select preamp instead of amp, that will sound 'clearer' than going through the amps, so as you're not emulating the power section of the amp, gives a cleaner (more transparent) tone.

     

    Quote

    2. re straight into the front of an amp - would a 'blank canvas ' amp like an aer  (compact 60 ( it does have an effects loop as well))  give good results using the amp and cab simulators? 

     

    But if you're asking for amp 'amp' like plugging in a Marshall amp or AER amp or watnot, then you'd be better off using the 4 cable method and not using an amp in Go, since if you're emulating an amp and then running that through an amp, well, you've got double amps, which likely isn't what you want.

     

    And if you're asking if you should plug in front of an amp, well ... IMHO, no.  The amp emulation of the Go is one of its main features, so unless you really love your amp and just want to use the Go for the effects (which is fine), then you should be looking at Studio Monitors or FRFR speaker(s) as silverhead mentioned.  That will give you much more flexibility as you'll be able to use the ridiculous amounts of amps in the Go instead of your 1 expensive guitar amp!

  22. On 2/3/2022 at 3:52 PM, voxman55 said:

    Line 6 increased the blocks in HX Stomp from 6 to 8 but this coincided with polypitcg effects being added and folk complained about the DSP drain. Hence they are very reluctant to add blocks to Pod Go. But recent posts on The Gear Page suggest that if sufficient votes are evidenced on Ideascale, the door might not be completely closed here.

     

    Digital Igloo said "Feel free to keep pushing the expanded block thing, too (stranger things have happened), and IdeaScale is the place to get the most eyes on it."

     

    (quote from another thread, but bumping this one instead)

     

    That's pretty sad...   Just sounds like excuses, it's very easy to say that people didn't demand this feature because it didn't get enough votes...  But how many PGO users are on ideascales, and how many know about this feature, or that they can vote for it on ideascale?!    Just to know about any of this, you have to visit this support forums or 'the gear page' forum's pod go thread or whatnot, learn of existence of the feature by reading a bunch of posts, and then you have to REGISTER to ideascale, wait for approval, then go to the bother of finding the exact place to vote.  No wonder there's few votes, takes a bunch of very unlikely events to occur to make it possible to vote.

     

    If Line6 was really interested in knowing if Pod Go users are interested, there could have been a simple poll somewhere; which features would you like most; a, b, c or d.  Or, would you like to have this? Yes/no.  Then people would vote, and you'd get an idea of what people want.  But this voting "if we get enough votes" thing is designed for user requests to be ignored. 

     

    Anyway, maybe it's not as bad as I assume. Maybe ideascale works better than I'd wager.  But I've never bothered to check it out in the past.  Like most people, the bystander effect is real; why do I need to vote, I'm just 1 person, doesn't really matter, others will do it.   And yeah, certainly Line6 is aware of all of that.  I guess the idealists views ideascale as a good faith effort, and the realists view it for what it is.   (The previous L6 answers confirm this, see my 1st comment in this thread)

     

    Quote

     

    Idealism is what precedes experience; cynicism is what follows.

    David T. Wolf

     

     

    And yeah, to answer to the original quoted comment.  It's a very silly answer.  Minorities always complain.  There will ALWAYS be people complaining.  And it's not like you couldn't run out of DSP previously...   Anyway, it just sounds to me like another excuse not to do it.  

    • Like 1
×
×
  • Create New...