Jump to content

grdGo33

Members
  • Posts

    361
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by grdGo33

  1. Yeah I think the issue I was mentioning was more specific to the String Synth, the tracking itself (which note) seemed to be working well. Maybe SS related to pickups or usage too; location of the block, etc. I remember seeing a vid about optimizing the synths; basically was all about creating a square wave before it hits the synth. But anyway, totally different from just pitch shift! For tracking, it was pretty good. Not perfect perfect, but very likely 'good enough'. Did you end up trying it @daveaphotopod?
  2. Are you sure it's not an issue with the software side of things? Because it kinda sounds like it is... I would try to plug in just some headphones or output the sound directly to some other device; amp or monitors or something and see if you can reproduce the issue. When you're having the issue, restarting the software and unplugging the Go USB cable would be a good test. Also reminds me of an ultra cheap 15$ USB guitar adapter I once bought, works for 10-20m then it because unusable. Just have it in a box somewhere.. And last also, a DAW is not typically used for live, I think the delay thing is pretty much 'built-in', it can be minimized using different drivers and settings, but from what I recall, it'll never be perfect; it's more for recording than anything else. But I might be wrong as I'm on expert in the field! "A DAW or "Digital Audio Workstation" is any digital software or device that allows you to record, edit and compose your audio tracks." Confident this is your issue. Using audio out of the Go, I'm pretty sure it'll work correctly, so DAW latency = DAW issue... I tried and pretty much gave up the idea when I got the Go myself; when with amp/speakers setup. IMHO, For live, outputting audio from Go would work. Go -> laptop -> house audio / speakers very likely not best route. But laptop/DAW users might chime in and contradict this though!
  3. It's not, but it tracks pretty well 1 note. My extremely limited experience with strings is that it often seems to bug out though; sometimes where it's supposed to go from soft to loud it doesn't go loud, just stays soft. So... I guess could work for recording or to play around, but I wouldn't say it's reliable enough for live or the such.
  4. see here! https://line6.com/support/topic/64437-podgo-140-update-changed-all-my-tones-much-brighter-and-grittier/
  5. I'm cynical, so doubtful it would change anything. I was mostly curious if other users thought it was as much as a PITA to use as I do. Maybe I'll re-check it out, last time I tried posting I couldn't due to account validation. But honestly... I have zero faith, so the only motivation I would would be rather embarrassing and puerile; à la "See? I knew it wouldn't work..." :/
  6. PGO edit is external software though, so it doesn't need to be matched 100% with the Go's Architecture, as long as the end result is. So, you could have global/base 'snapshot' that does not exist in the Go device; simply exists in memory space of the PC. This base settings would then be used to change the base values and reset the 64 variable parameters of each snapshot. Ex; SS1 -> Gain 2.0, SS2 -> Gain 5.0, SS3 -> Gain 1.0, if you set the Gain of the base to 4.0, it would effectively change the 'base' Gain to 4.0, and remove the Gain param of all the snapshots. And yeah, looking at a .pgp file, looks like that seems to be exactly how it works internally; 'base' settings for all blocks, and 4 lists of parameter values for each snapshot. In the GUI, in the base settings, the params which are modified by snapshots could be in red or orange, just to highlight the fact that modifying this value would reset snapshot values to this value. Yeah, using background colours, large titles "BASE SETTINGS" vs "SNAPSHOT 1", it could be very obvious where you were. It's much more practical IMHO to open Snapshot1 and then edit Snapshot1, rather than always being in snapshot X, and changing settings changes settings for all snapshots, unless you manually set the controller to 'Snapshots' for each param you change...! Just explaining the existing logic is painful... There would be no change for the 64 params. You could still display in white under each snapshot the snapshot values. If you run out, you could easily go back to Base and change a value currently set by snapshots. Ex; 64 used, you go to base, change Gain to 4.0, it resets the snapshots, and if I understand correctly you're now using 63 and can choose a different param to control with snapshots. (Could also have a right click, 'reset to base' under each snapshot) Again, under the hood; it would work the exact same way as now. This would really be a PGO Edit only modification, nothing to change on the Go. It's just an intermediary step difference, but end result to the Go is the same. Yeah IMHO, far more intuitive to be in Snapshot #1 and edit Snapshot #1, rather than being in Snapshot #1 and having to set a controller for every param you're changing for Snapshot 1... Maybe it's legacy from earlier L6 products and long time L6 users are used to it, but from a software design point of view, it's really just quirky / dubious design... Just the "explain it to me" makes it pretty obvious! Existing logic is really kinda twisted, and you really have to wrap your brain around the; even if you're editing SS1, you're not really editing SS1 unless you set a 'snapshot controller' because otherwise even if you're in SS1 you're editing the base settings. VS, base you're editing common base values, and under SS1/2/3/4, you're editing value for that particular snapshot. Just so much simpler! There's just so many improvements that could be made to PGO Edit... It really would be great if L6 would release some sort of open source PGO API where users could improve software themselves!
  7. Just curious if people think that editing snapshots on PGO edit is far more trouble than it should be? IMHO, the way snapshot editing should work is that by default, you should be editing a 'base' patch, like 'global' patch settings. When editing this base patch, changes would be applied to ALL snapshots. Alternatively, you could edit a particular snapshot. So, if you switched to patch 1-4, any/all changes should be applied only to the snapshot. None of that assigning 'snapshot' to every single parameter so that it changes the param value only for this particular snapshot... It would be automatic. To edit a value for all snapshots, simply go back to global/base patch, and overwrite all snapshot param value. Would seriously this not be way more practical? I can't count the number of times I forgot to assign a parameter to 'snapshot' and ended up messing up the settings for ALL the other snapshots... The only logic I can see behind this design is that PGO Edit has to be somewhat compatible with editing directly on the Pod, but yeah, this simple change would make editing snapshots so much better...!
  8. Yep, plus supposedly fixed on newer units, and they wouldn't know even if it's an old unit if was fixed or not, not to mention it would mess up the Go's for everyone who has a correct unit or anyone using a buffered pedal. But again, if Root's only hearing an EQ issue, global EQ would fix it.
  9. If it was just that, then fixing it with the global EQ should be pretty easy. Maybe you had set it up and it got reset?
  10. Btw did you open a support ticket with L6 or try to rollback firmware? I'm still unconvinced that they updated some of the amps models (or could be mic, cab, etc.) without putting it into the patch notes... As far as I'm concerned, I have another explanation; I did go through my patches to try to adjust volumes and tweak stuff, but when you equalize settings for guitar A, tends to unequalize for guitar B... So pretty sure that's what happened in my case. Many guitars is problematic in this way... Also, you seem to be the only one to have noticed the issue... Pretty sure again that if L6 tweaked or improved something somewhere, they'd have mentioned it, and you'd have more people noticing...
  11. First time I heard of it was here... I didn't notice any tonal change since the updated (updated 1st day update was available), but a string broke on my HSS, then lots of work, so by the time I switched its strings (D'Addario EXP 110 XL coated strings) and redone the setup because the action was all messed up, I didn't get much single coil strat tone usage lately with the GO; mostly HH, and didn't notice any tonal change. But yesterday, once the HSS was back up, played a bit and yeah I did notice some patches (Fender/clean) yes seemingly sounding brighter, but it did correspond to new coated string and reading your comment the day before soo.... Placebo/strings could very well be 100% of the change I perceived... But yeah before that, I don't recall hearing a tonal change before... Anybody else noticed a change? If there was a change, might have been more audible on cleanish tones, and maybe also make a bigger change with single coils, as as I said, didn't notice much change using humbucker guitars and mostly heavy distortion patches. Oh yeah, could it be also a switch on or settings on the PA speakers? Such as bright switch or someone who messed with the speaker's EQ settings? TLDR 1) maybe EQ on PA speakers 2) maybe some Go amps are affected more than others (likely clean Fenderish amps more affected) 3) maybe even no change, and placebo is just one hell of a drug.
  12. Yep... In your logic, you would need to know the impedance of amp so you would know which power amplifier to buy, and then you would 'need' to find out the the impedance of the cab so you would know which cab to buy. Of course, that's not really how it works, as the difference/gain with 'optimal' impedance of the amp would be largely inaudible and so insignificant. The PGO will work with pretty much any amplifier, and as long as you get an amplifier suited to respond to your speaker's impedance & sensitivity you'll be fine.. Ex; don't buy an amp only rated for 8 ohms if your speakers are 4 ohms.. And don't get a 10 watt amp for speakers with 81dB sensitivity.
  13. Pretty sure it would be nearly impossible to brick a unit with the patch. The patches are very likely one of the last things which are loaded in the Go, so in the worse possible case, as you said, you would have to reset your unit to factory settings, which resets the patches to patches that don't contain the 'hack', and as it's done via buttons while booting the Go, would happen before loading any patch. At worse, still very unlikely, it could cause some unforeseen glitches; maybe affect effects, other patches, visual GUI glitches as you've shown, etc. Bugs are part of the nature of software design, and you're using it in a way which was not foreseen by the devs, and not tested by L6 QA... But yeah, that doesn't seem to be the case; as you'd likely have seen warnings about it. But you never know, maybe one day, when L6 updates its software, it might cause new glitches. FWIW, I'm running out of DSP far more often than blocks, so in my case, haven't bothered yet playing with it. If you want more blocks though, the new 'feature' should over weigh the risks by miles IMHO, as the risks are very minimal IMHO. Risk of bricking the unit is almost null, and any bricked unit after the 'hack' would likely be coincidence rather than the patch, again imho.
  14. Nope. The different channels of amps are in the Go 2 different amps; ex; Revv Gen Purple based on : Gain 1 (purple) channel of the Revv® Generator 120 Revv Gen Red based on: Gain 2 channel of the Revv® Generator 120 Das Benzin Mega Based on: Diezel VH4 Das Benzin Lead Based on: Diezel VH4 https://helixhelp.com/models/ Some of the amps clean up way better than others; more responsive to volume. So play softer and it'll be clean/cleanish, play harder and it'll distort; so you can control gain via guitar volume. The new Ventoux for instance can go from clean to gritty. Might also want to check out The Derailed Ingrid based on Trainwreck Express. It's interesting that some amps you might just glance over have some story and might be more interesting than their original preset might make you think. https://youtu.be/eE14hY8dHSk
  15. Which delay are you using? Simple Delay? If so it's normal, just badly documented or a bad name... The Simple Delay is Stereo.. You could try the Digital delay, I'm not at my Go so not sure which are Stereo delays, but there's quite a few delays, some are bound not to be stereo. Also from what I recall, some delays are stereo and you can adjust the Left vs Right, so setting them to center could be a workaround to get mono sound, but I'm pretty sure some delays should be mono by default, just try other delays!
  16. Are you sure? I mean because it's true bypass, it won't when it's off, but when it's on, it's got the same impedance output as a BOSS (1 k ohm), so it should at least work when it's turned on no?
  17. Yeah, but apparently his pedal isn't buffered, it's a true bypass pedal!
  18. It seems to work just plugged in. I use mostly clean tones, and it's a very noticeable difference on the high ends. Are you sure? Technically, it should not! Is this your pedal? JOYO JF-38 Roll Boost Guitar Effect Pedal - True Bypass https://www.joyoaudio.com/product/76.html So unless your guitar is not true bypass, it should not affect your tone in the Pod Go at all when the effect is turned off. Specs from amazon say "Output Impedance: 1KΩ", so same as buffered pedals, so yeah when the effect is on, it would likely have an affect, but not when off. :) Anyway, interesting conclusions to draw: 1) power of placebo. Never underestimate its power!!! 2) the PGO impedance issue isn't traumatic; if users can't notice if it's on/off, Maybe some think they can hear the issue with their own Go, when in fact their Go doesn't have the issue lol
  19. The issue isn't that it's not possible to build good presets, it's that it could be way faster and easier, less tedious, more practical, etc. with contextual help. It's something that does not exist for Pod Go. https://www.knowledgeowl.com/home/contextual-help But you're asking for something that you can already do. You can already download a patch where you have 8 dynamic blocks. It's super easy, it takes less than 2 minutes. So ironically, you're asking for more 'flexibility' by adding a feature that the Go already has, a one time 2 minutes effort that you can do yourself, while at the same time, rejecting true practicality by saying that you can still build good presets... The irony............. LOL ( not really funny... Morel like; https://www.youtube.com/watch?v=Zg5aKZSF9EM but yeah... reminder of why democracy doesn't work, why the west is falling, etc. lolol)
  20. I for one, know for a fact that when a new product comes out, it makes others sound worse. And I don't mean in an Apple kind of way, where they covertly and deliberately make your phone runs slower when a new Apple phone comes out; or 'optimize battery'. You, my friend, are underestimating the power of placebo...! :D But yeah it's hard to have a clear view of what is what... With for instance YT 'reviews' which are often little more than paid advertisements, over-excited users hyping what they own, poor comparisons (just using presets or having 1 unit louder than the other, or bad/different EQ, etc.), PLACEBO about the newer thing sounding better (disappears in blind testing conditions), different cab/mic/IR, etc., really hard to know what's what. I remember when the Helix Alias fix/improvement came out, I tried to listen to it, and it was really on the insignificant / barely audible/detectable, but still some would say it makes a huge difference..... I watched a few comparison vids, Go vs this and that. Side by side, with its excellent effects and all, it tends to hold its own I think with pretty much anything. I don't think that at the level it is, that it's ever going to be blown away, since I mean already in a blind test vs real amps, it's really hard to tell them apart. I think also that the effects in Go / Helix are excellent, so when comparing vs Axe Fractal or Neuro Quad or whatnot, when ex; testing the shimmer, reverb, delays, etc., it holds its own. Even vs that Big Sky $500 dedicate reverb box I don't know the name, I mean, it's not identical but pretty darn close. Even heard some claim the Dynamic Hall is just as good as anything out there...! But even the reverbs pre recent updates where somewhat comparable. Don't think competitors fare that well there with their budget units. So yeah not perfect; could be simpler imho. But far from being 'old' or obsolete it looks like. Sure, more powerfull stuff for more $, attractive features here and there, but I can see new users go for Go. Still attractive units today despite everything. Every unit has its quirks and shortcomings. PGO Edit for instance, not perfect, but 100x better than having no editing software! Not all units get new fancy effects/amps too, etc. etc.,
  21. I'll disagree a bit with Vox here! The Go really benefits from some effects; for instance, the Dynamic Hall/Plate reverb, the Shimmer reverb, etc., these are extremely nice features to get as freebies, so yeah a big YMMV. For me these were fantastic additions, but that's not something I would say for all effects... But reading a bit the comments and tutorials and stuff, for instance for the Amps, some have said that the new amps just sound better and better, even if the L6 process to create them is the same as the original amps. Amps are kinda crucial, so I don't doubt one sec that most of the users are glad to have new great sounding amps. Again, YMMV. FWI, the Benzin is one of my favs, it's a new amp. The US Princess is another community favourite I think, so kinda nice to have. What I'd really like to see is some sort of contextual help. In PGO Edit, when configuring an amp/effect, being able to put your cursor on a setting and getting the explanation. That would be GREAT help, as often you have no clue what a setting does, so having a hint / mouseover with short explanation would do wonders for improving user experience, as having to do a web search for the info every 10s is a pain. If the mouseover could give tips that would be even better. (like "value ~5 is recommended, but 7 is great for ___ and try value 3 with this other parameter at 7 for _____!" ++ for the rest of Vox's post!
  22. btw do these work ok for any of you? I tried them briefly yesterday, and they seem to track ok for one note, but it goes completely garbled if there are more than one note at a time. Which I'm sure is normal; not polyphonic or whatever the word is. But even with one note, seems to be a bit bugged... For the String Theory for instance, the way it works, as you play a note, plays the string. Each string note has a start, middle and end. The start/end being when the bow starts/stops moving, so very soft, the middle is the note playing; so loud string noise, then the end, bow stops, so goes very soft. As you play many notes, it goes to this iteration quickly, but if you're playing quickly, it just tends sticks to 'middle' where it's loud. Great! BUT, sometimes it bugs out, and it just stays soft all the time... Then you don't hear any string noise anymore, just muffled noises. Maybe it was my settings, was using a clean amp, is there any tips for it to work better? But yeah, for me, it felt a bit uncontrollable and unpredictable. Don't think it was my picking or anything; really like if it was bugging out ...! It almost felt like it was the DSP; like if there was too many things going on and the Go could not keep up and the effect just bugged out.. But yeah maybe it's just me also, maybe I was doing something wrong?!
  23. OH SNAP!! Nice! :D Ha! Ok just a FYI, last step of PGO update; <Update complete. yaddayadda successfully 1.3 to 1.4 yaddayadda, POD GO is rebuilding its preset library and will reconnect to Pod Go edit in a few minutes.> It won't reconnect automatically to Edit, you can click back to Edit, and if it's done it's going to connect, if it's not done I guess it won't... (I was waiting for it to switch back but I don't think it's going to switch back by itself lol) And again just to be sure, when restoring the backup after updating and factory reset, you're also better off restoring the 1.3 presets over the 1.4 presets?
  24. Think your issue might be that if your Blackstar isn't 100% clean (distortion/gain), so your amp will distort multiple simultaneous sounds and that is why you think the looper is bad quality. A little bit like with overdrive, a single note sounds relatively clean, but a power chord gets nasty. So if you're looping multiple samples, you're getting the power chord effect from your amp. Maybe. Basically, your amp should be 100% clean, which sometimes isn't the case even when you set the drive/gain to 0. Being Blackstar, maybe ... [EDIT] But looking at the amp, woa, nice tube amp with a clean channel, so that might not be it either. But tubes, always have some inherent distortion.. What you can also try to confirm if that is your issue, connect headphones to the go and see if you're hearing the same thing when using the Looper. Headphones is really a quick easy test to do. Otherwise, yeah, as phil mentioned, the more layers you add, the less clear everything becomes; trait of loopers I think, any noise also gets compounded, so if you have any noise, adding multiple layers of it every time just degrades the overall looped sample.
×
×
  • Create New...