grdGo33

Yeah it's surprisingly not bad! It doesn't sound 100% like a real acoustic, but, it can kinda sound like a piezzo PU, anyway, sounds closer to an acoustic than just a regular single coil PU. Hmmm.. Slightly bugged in PGO edit though, when you try to select the amp sim, it just resets back to the 1st node with the noise gate and guitar selection... It's like it selects the correct block for 1/10th of a second, then goes back to input/noisegate ... ! But now it stopped... Hmmmm... Strange...! Anyway, cool feature! :D

You're in luck! New update just released, install and check if it fixes your issue!

Update went flawlessly this time, love the new glitch delay, thanks! :D

Anyone knows how it works? Never mind... I finally stumbled on this site. So until the manual gets updated, this site will likely have the info for the new effects! https://dshowmusic.com/line-6-helix-effect-models/ Or yeah would also be in the Helix manual... Should have thought about that lol Glitch Delay Mono, Stereo Line 6 Original Performance delay that lets you freely manipulate the repeats’ behavior in real time Time—Sets the delay time; press the knob to toggle between ms/sec and note values Delay Div—Divides the delay time into smaller increments Mix—Controls the wet/dry mix of the delay. When set to 0%, no delay is heard; when set to 100%, no dry signal is heard Feedback—Controls the overall number of repeats heard for the entire sequence SliceFdbk—Controls the number of repeats heard for individual slices. At higher values, you could call this “Super Chaotic Feedback” Shuffle—Determines the likelihood of repeats shuffling/reordering Octaves—Determines the likelihood of repeats playing back an octave higher or lower Reverse—Determines the likelihood of repeats playing backwards Seq Drift—Determines the likelihood of the entire sequence changing every time it loops around. When set to 0%, the same sequence loops forever. TIP: Assign this parameter to a footswitch set to toggle between a higher number and 0%. If you hear a random sequence you want to maintain, press the switch to set Seq Drift to 0%, and it’ll repeat that way indefinitely Smoothing—Higher values apply smoothing between slices and can give a synth-pad type quality, lower values maintain transients. Or set it just high enough to avoid pops and clicks Trails—When on, delay repeats continue to ring out after the block is bypassed Btw, for having tried it a bit, the Delay Div does seem to 'often' introduce a bit of 'clipping' sounds; when they're reversed or whatever, but maybe it could be smoothing... Or, maybe I was just using too many delay divs given the time, anyway, will experiment more, as I probably experimented with some bad settings. Very fun delay! :D

Yeah, maybe because I`m not as ancient here as others, but we'll have a better idea of the typical time frames. Helix 3.0 was released last November, so it took about 4 months for new features from Helix to trickle down to the Pod Go. So next time, we'll have a better idea. :) (Communication by L6 about future release firmware/patch ETAs with expected features would be nice to have!) Plus I think we`ve gotten pretty much everything as expected! :D (https://line6.com/support/topic/59695-pod-go/?do=findComment&comment=372131) all except Still with the Glitch delay, you can sort of reproduce the shuffling looper; they're at least somewhat similar in terms of effect I think...

The issue with that is that your risk inadvertently activating it when you don't expect and blow your speakers or ears... I've got all my patches also relatively low volume to go around issues with too high level making my looper distort. When DAW'ing, I reduce the speaker's volume, and crank the channel volume. Sure, bit tedious, but less chance of playing, pressing the wrong button and the sound going from 3 to 10...

nope

are you using the latest firmware? There was no sound issues that were fixed, so if not up to date, update!

Seems like I'm always posting the same preset video lol imho they're really not terrible, hell, listen to the above, they mostly sound pretty good; not something you'd be shocked at hearing on a record or radio. It's really a combination using a fitting guitar and style for the preset, using it for what it does, etc. They can sound a bit 'bland' or generic, anyway, they're just presets. IMHO, they're not even really intended to be actively used. Don't think anyone at L6 believes anyone will buy PGO and will try to use the unit with its presets... PGO is really made for you to configure your own sounds. Easy way to 'fix': Try each preset. Just save the dozen of so presets you like or find decent to your user patch list, customize for your taste/guitar/style or for starting point of new patches, then never visit the presets ever again. Oh snap! The gauntlet has been thrown!!! :p

Yeah the presets are ... lackluster. It would have been nice if they were categorized; jazz, metal, rock, lead, ambient, etc., but yeah it's all mixed up. It's worth it going through each preset though, noting what you like and dislike, check what effects they're using, etc. Also, you can download patches from the L6 free share thing, so maybe you'll have better luck finding the type of sound you like. But anyway, even if you had the perfect patch, you'll likely need to adjust it for your own guitar, amp, etc.

Yeah fast startup didn't fix it... To describe the issue; it gets to the login screen, but once you login, then the screen becomes black and/or starts flashing for a bit, then the CPU apparently sky rockets because the fans of the laptop are running at max speed, then a few minutes later BSOD. I just unplugged the Go from the hub and it booted without issue, so it is 100% caused by the Go and its drivers...

Maybe! Although I did use a hub with my PC and it worked without issue... But I do also have the fast startup disabled on my PC... But yeah I'll try it! If the fast boot does not work, I'll try going without the hub see if it fixes the issue! Thanks!

Recently changed the computer I'm using with the Pod Go, went from a PC to a Dell XPS 9570 laptop. And ever since, the laptop has been having booting issues. But if I remove the USB hub with the Go and keyboard+mouse, does not seem to have any booting issue. Something about driver power on state or something like that... Looking online different errors from the event viewer, it might be caused by the fast startup options in the power settings... So maybe that'll fix it... Anyhow, maybe this could help someone someone else, or has anyone else had such issues and found a fix?

There might be some streaming software that does it, which is pretty much what you seem to be trying to achieve. https://www.thetechlounge.com/best-streaming-software/ Anyway, with distinct tools; 1) download and play your YT video 2) record your guitar using a DAW 3) record your webcam video / sound using some other software 4) merge everything using video editor Of course this wouldn't be 'live'. If you output the sound via Go, there will be no delay, probably need a decent pc to pull it off!

Wow... Crazy! Btw, for exporting/importing single, the format for exporting all the presets vs single is very likely the same, so by opening the file in a text editor, you'd be able to find the preset you're interested and simply copy the block to a single file. Yeah, a patch (.pgp) is in JSON format, so 99% sure the full export also is, so if you take a single patch export, replace its content with the patch you're interested in, you could likely import a single patch from the complete setlist. **To Be Confirmed!** If it's the 1% and they chose to use a different format for the 'setlist', then it would not work; but highly unlikely as it would have doubled the programming work by creating 2 import types.. JSON format is simple, plus there are guides & json validators online.

hopefully..

The sound (sound waves) is exactly the same whether someone is there to hear it. And that is exactly the premise of the entire music and recording industry; an event occurs which causes sound vibrations, those vibration are captured and stored on a device (ex; mic & CD), then, the data is read, and converted back to sound waves (tranducers; speakers). That's how you can hear someone playing example violin in your room via speakers even if there is nobody in your room playing violin. What is artificial in my original comment is that you can ONLY hear a cab via a microphone, and the actual sound you would hear from say a 4x12 Marshall in a living room does not exist in Helix/Go. Nobody listens to a 4x12 two or five inches away ... And I'm pretty sure that a well recorded 4x12 in a room (using mic blends or whatever; just recording the cab so that it sounds as close as possible as to what you would hear in room) would not sound like with the Helix/Go set at 12 feet or whatever... But yeah, maybe it's just a bad idea... I mean; setting up a pair of speakers to get optimal sound in a room is a PITA, and then you need to be seated at a precise location in the room; as if you move around, the sound goes to hell. But yeah, if you had a room and a cab, and walked around in the room to the best spot to listen to the cab, that could well be a good capture point for an in-room IR. But maybe also the sound you get via the current cab+mic Go/Helix system is just way better than my 'in room' concept... It might very well end up sounding poorly vs any other 'standard' Helix mic+cab setting, as there is no 'accurate' in room 'sound', it would be the sound at one spot in a particular room; and given the FR effects of the room, reverberation, etc., might just sound 'poor' vs a cleanly recorded cab... Still, my old Digitech RP5 had reverbs like stadium, hall, church, bathroom, garage, etc., which made it sound like you were playing in one of those environments, it was pretty cool. But yeah the entire microphone thing seems to be a big can of worms also... Although the maybe the 'new' laser microphones could do the job! :D https://germanmasterworks.com/publish/articles/Advice/The-Myth-of-the-Accurate-Microphone.html https://www.engadget.com/2009-09-21-laser-accurate-microphone-proves-once-and-for-all-that-everythin.html

Absolutely zero metaphysical! Just meaning; captures the sound waves perfectly. IF we had a perfect transducer and a perfect mic, we could simply compare the original signal and the recorded signal; what is commonly called a null test. So; it would be 'what comes closest'. Now there's no perfect transducer (which is what we want to capture with 'cabs' emulation; distortion of the signal). With microphones, there are correction curves to alleviate the mic's FR aberrations, so already that ?should? give us fairly close representation of the sound of the cab? Quick search results in results such as these, but I'm not entirely sure how it would end up sounding say if we put a cab in a room or anechoic chamber and recorded them using one of these, then using as IR or emulation reference... https://www.bksv.com/en/transducers/acoustic/microphones https://earthworksaudio.com/measurement-microphones/ http://www.josephson.com/pdf/srs5.pdf http://www.josephson.com/pdf/c617setds05.pdf Going on a tangent; for headphone use, it would be, I think, fairly simple to generate a binaural IR, and that would put us in the room with the cab. That would be cool. But that wouldn't work for speakers; for speakers, you'd be better off with a pair of the most accurate mics & creating an IR... And yeah... IR... Actually, that entire topic could in fact be summed up as an in-room IR; taken with a very accurate (realistic sounding) microphone...

It would be fairly simple; 'perfect mic'. Well maybe it's not that simple...! lol But yeah, you do need a mic at one point I'm guessing, maybe there is a multi-million dollar experimental/scientific near-perfect mic that could be used, if you want to go kind of the IR way? Maybe using mic blends & source signal to get from the original signal to what you would hear in a room? https://moneyinc.com/most-expensive-microphones-in-the-world/ https://mynewmicrophone.com/top-20-most-expensive-microphones-on-the-market-today/ But we have a source signal before going in cab. The cab (with an IR or other) will have an effect on the signal; that likely already built in Helix; the helix does appear to have 'cab' emulation, and 'mic' emulation... Unless the Helix basically uses an IR of every possible cab + mic + distance? (I don't think so, think it's mic emulation + cab emulation?) But anyway, likely, it could be similar to what Helix uses; just using the 'cab' algorithm, plus some room reverb, and yeah 'distance' probably isn't even really relevant, just having cab + room without variable distance parameter would be great!

I was just thinking, a great feature to have in the cab section would be a head or human instead of a mic. Let me explain; in the cab block; you mainly select a cab, a mic and a distance. But why not also have the ability to select a person? Meaning; say you had a 4x12 in a room, and you were 8 meters away from the cab; how would it sound if you were in the room? (aka; if it was recorded with a perfect mic?) I think that actually this should have been the default setting for all cabs. How would the amp sound if you were in the room? When you have to select a mic, you're basically removing cab simulation from unit; and you're basically saying, this is how it would sound if it was recorded. I mean it's fine/great to have as a feature, getting the recorded mic+cab tone from albums is great. But, the Go lacks the most basic ability to emulate a guitar cab. It cannot emulate the sound of a cab; of how a plain cab would sound to a human in a room. It can only emulate the sound of a cab if it were recorded with a microphone... And that is to me quite an artificial way to treat cabs. The most basic way to use an amp and a cab is playing them directly, and hearing the sound. The Go lacks this most basic feature. This would simplify tremendously the cab block, and I think might help get some great tones also... Of course room becomes a parameter; are you playing in a garage, bedroom, church, etc., (reverb characteristics) but many reverbs aren't super expensive DSP wise, and if my my old 1994 Digitech RP5 could do such reverbs; don't think the PGO couldn't... Thoughts? Any idea why there isn't such implementation?

Nice! Yeah most of your tone is going to come from your cab, and it's not the simplest thing to wrap your head around. Reading a few threads on other forums about them, here's a few notes, mostly collection of user quotes, could help out at least as a starting point! Going IRs can also simplify this quite a bit.

Ah yeah many class D amps, if they don't have large enough heatsinks to dissipate heat caused by using more watts, can overheat if they are played at max/high power for too long, so likely that's what you're experiencing... Built-in amps in the monitors are probably overheating... I was also thinking of mentioning FRFR, but they're just different beasts; anyway, some of his points might be argued (ex; can elevate FRFR), but, design-wise, a FRFR with a 2000 watt amp (made to play loud, live; like a PA speakers) vs studio monitors; which are designed more to be tonally accurate, maximize sound quality over quantity, etc., it's more about what you want/need. Not saying studio monitors are better, many here seem to absolutely love the headrush FRFR 108 and say they sound absolutely fantastic. (haven't heard the FRFR 108 myself) https://forum.fractalaudio.com/threads/headrush-frfr-108-vs-studio-monitors-please-help-me-choose.152476/ So just depends what you're after. I remember a long time ago while researching music & HT speakers, many were recommending studio monitors as opposed to audiophile speakers for music: Save $ on 'overpriced' amps & get 'pro' gear which suffers less from audiofoolery & snakeoil BS like audiophile gear tends to have; no audiophile 'pricing'. So go the pro route by going studio monitors for sound quality imho good idea. Anyway, imho, for a more music or sound quality investment; studio monitors likely the way to go. For a guitar only with possible gigging, playing with band, etc., then yeah definitely go FRFR.

While you can control the unit via the unit itself, you can connect it to USB to a computer and use Pod Go Edit; which makes it much less 'painful' than using the knobs and the small screen of the Go. It's way more practical to use that way. Some also use it on a table and use their hands to control it, well then you can't get to use the PGO as a floor unit; so lose the usage of the volume/expression pedal, and can't really use the looper very well... Stomp can have more effects on at the same time, dual paths (ex; 2 amps at the same time), but it costs more than double I think, less buttons, smaller, smaller/worse screen, etc. I think the Stomp is yeah more for gigging musicians with already pedal rigs, vs Go probably better unit just to jam at home; or maybe even gigging, if you'd want everything included in 1 unit, and don't really need/want the dual path or https://www.thegearpage.net/board/index.php?threads/pod-go-vs-the-stomp-is-the-pod-go-a-stomp-killer.2113675/ https://www.youtube.com/watch?v=t8GX3TeTvts

The size of the mid driver in a 2 channel speaker mostly depends on SPL; to play louder you need to move more air, and moving more air means means either having a larger driver (moving the same amount as a smaller driver will move more air with bigger driver) or, the woofer will move further back and forth. Also; bass is what what requires the woofer to move most air; while treble (high frequencies) require very little movement. So the deeper the bass, the larger the woofer you generally require. So at one point; it gets easier to move more air with a bigger woofer, so you're never going to see 4 inch driver playing incredibly loud and having amazing low end response. BUT, the bigger the woofer, the more mass it has, and it becomes more and more difficult to move it back and forth. And the higher the frequency, the faster it needs to move back and forth. So that is why you have a extremely small and light tweeter, and a mid woofer (plays mid frequencies) in 2ch speakers and, you have 3 channel speakers (or more, MTM, etc.) with tweeter, mid woofer and bass woofer; each getting larger. So for 2 channel speakers; the typical size is 5 to 6.5 inch. These can typically play VERY loud in a small to medium room. Larger drivers become more relevant if you want to play very loud or if you have a larger room... Sounds get less loud the further you are, so the bigger the room, generally the further you are, so generally need to compensate with either much higher quality drivers or just get larger drivers... ANYHOW. LOL. I was also looking to maybe get a set of studio monitors to upgrade my computer speakers, and use with the Go. KRK seemed to pop up a lot; but sadly; with speakers; it can be really subjective. Someone can love the sound of a speaker, while another might totally hate it... We all hear differently, have different tastes, expectations, etc., lots of recommendations for 'best'; https://www.musictech.net/guides/buyers-guide/best-budget-studio-monitors/ https://www.musicradar.com/news/best-budget-studio-monitors https://musiccritic.com/equipment/speakers/best-budget-studio-monitors/ https://www.4soundengineers.com/budget-studio-monitors/ So your best bet might be try to identify a few which fits the budget and seem interesting to you, and try to go listen to them somewhere. None of them should 'crackle' at 'normal' listening levels; (often can be caused by the amp not being able to drive the speakers correctly) plus guitar doesn't have massive bass so it shouldn't be super taxing for speakers... So yeah, might not be super hard to want more volume than the 25w/side + smaller drivers can handle...

Thanks! Yeah I just bought the Pod Go, I didn't go through the entire Line6 employee list to find out who exactly worked on it! Is this something people typically do? Like you purchase a freezer, and you have to do the research to find out who designed it, and what their forum nickname(s) is/are? LOL ;) :D Good enough for you? See the link: https://blog.line6.com/2020/11/27/eric-klein-talks-helix-3-0-with-joe-gore/ I breezed through the article But didn't see the Pod Go announcement for the firmware updates and features...