Jump to content

DolurumMafikala

Members
  • Content Count

    22
  • Joined

  • Last visited

Community Reputation

2 Neutral

About DolurumMafikala

  • Rank
    Just Startin'
  1. Hi, Have you changed the Windows Playback Device to the Pod? If you click the speaker icon in the bottom-right of the screen in Win10 you can select the Pod there.
  2. Good luck with the gig! Let us know how it goes... I'd been idly wondering what that bit of plastic was for, so thanks for the thread :) DM
  3. You could try now in your home or rehearsal space and see if it still happens.
  4. Oh, interesting, so it is reliable if you are just recording into Reaper or listening/playing without third-party plugins? If so, it makes me think your setup might have a bottleneck somewhere. Looking at the Toontrack website, they seem to be quite full-featured plugins. My experience with the Pod USB connection is that the driver stack doesn't seem to handle interruptions/stuttering very well when the PC / USB subsystem is busy. Ideally it should gracefully buffer, or discard if it can't, but there seem to be unhandled error conditions. This is all a bit speculative, but I wonder if, with the Toontrack stuff being heavyish, that it ties your machine up a bit too much, which means it can't service the USB audio stream from the Pod quickly enough, leading to the BSODs from the Pod drivers. Googling "Toontrack CPU", I did find this thread https://www.toontrack.com/forums/topic/insane-cpu-usage/ , which talks about restricting Superior Drummer 3 to using 1 CPU core when used in a DAW. Some people had found that help them avoid clicks and pops. Might be worth looking into? What actual Toontrack plugins are you using? I see some comments on their forums about SD3 maxing CPU on some machines while the older versions are ok. Unrelated, but when using the Pod I am listening/monitoring with headphones connected to the Pod, rather than the phones connected to my PC sound card or my other audio interface. This means my Windows "Speakers" are set to the Pod. I felt it was better to keep things simple and be using one audio system at a time, and I suppose I also get the minimal-latency monitoring of my guitar playing. I don't disable those other audio interfaces, just don't use them at the same time. DM
  5. @MotherGo0se, so would you say you get the BSODs mostly when you are streaming Youtube and playing? I'm wondering what you have already tried to isolate the problem. I've seen some of your older posts where you seemed to be using an oldish machine. Are you still using the same one? Some thoughts: Have you tried setting the buffers very high? I know you won't want to do that permanently, because of the latency, but it might be worth trying to see if you can find a stable setup. I'm thinking if you try to minimize the load on your machine (and remove unneeded things, even temporarily) you may be able to isolate some of the key reasons for the BSODs and then remove them. Does you get bluescreens if you just listen to Youtube but don't record your playing back to the DAW? Do you get bluescreens if you are just running HD Edit and not streaming audio from the Pod to the PC via USB? i.e. you are listening using speakers or headphones connected to the Pod? For that matter, how do you usually use the Pod? Do you monitor on speakers connected to the Pod or via your PC? Just generating ideas. What have you already tried? DM
  6. @MotherGo0se I guess it is up to Line 6 if they want to put any maintenance work into the drivers, but I do tend to agree with you that the drivers could be more robust. While Line 6 still sell the HD series as a current product, rather than a discontinued item in legacy support, it would seem reasonable to harden the drivers against the conditions that cause the errors that result in blue screens on Windows. I've had a bit of recent success with getting mine from unusably-frequent-BSODs to a stable setup. I posted about it a few days ago. That post contained a link to the Line 6 USB audio trouble shooting guide that might be useful if you haven't seen it. We can't control whether or not Line 6 can or will make any updates, but if we want to use our Pod HDs we can see what we can do to lessen the chance of BSODs with the current drivers. If you want to DM me what you've tried already we can swap notes. My approach was to remove potential sources of stutter so that the driver stack has less to deal with and therefore the error conditions occur less. DM 5 BSOD-free sessions and counting...
  7. Summary Check the Pod HD ASIO driver is not performing Sample Rate Conversion without you being aware of it. Remove easy potential sources for stutter. Background I had been plagued by the commonly-reported Pod HD-related blue screens (BSOD) on my Win 10 desktop, particularly when working with my DAW, Reaper. I have reached a point where my setup is now stable. Over recent weeks I've had four recording sessions without bluescreens whilst maintaining a USB connection. In this post I'm intending to document what I did, what was effective and what was ineffective. I see many frustrated posts about this issue. Sometimes people seem to be replacing or returning their Pod HD, which is a shame. I have not seen Sample Rate Conversion problems being talked about in the trouble shooting posts I read, so I hope this helps someone. Workarounds or ineffective configurations I tried - Ignoring USB and going direct to my other interface (as I have one). Obviously this works, but the sound quality did not seem as good as the USB connection to me. I'm not saying I can hear the extra DAC/ADC step, but it's another spot where you have to get the levels right, and you need two cables if you want stereo. My other interface only has two channels and I wanted to keep a mic in the other one. So, if you are really stuck this works fine, but was not great for me. - Disabled Selective USB Power Down. You will see other references to this step. It did not reduce BSODs for me on its own. I did leave this setting disabled in my final configuration, though, so it may be a factor. - Using the rear USB vs the front USB. This does have some logic to it as the front USB ports on a desktop tend to be a hub, so if the rears are not then things have been simplified. Using a Rear USB did not make a difference for me. - USB2 vs USB3. Simply swapping to USB2 was not enough for me, but I have continued to use a USB2 port in the stable configuration, so could be a factor. If you have USB2 ports available I think it make sense to use them, as the Pod HD was, I think, designed before the USB3 standard was introduced. - Different combinations of allowing the Pod to be or not to be the audio device used by Windows as default made no difference for me. - Disabling Windows System Sounds on its own made no difference for me, but I have continued to leave them off in the stable configuration, so could be a factor. After trying those solutions I found the official Line 6 advice on USB troubleshooting here: https://line6.com/support/page/kb/recording/computer-audio-set-up-and-troubleshooting/usb-audio-troubleshooting-r443/ and set about eliminating sources of stutter which seem to be less-well handled by the Pod HD driver stack when compared with the driver for my Focusrite Saffire 6 USB audio interface. I noticed that Reaper was reporting that the Pod driver was operating at a 44.1 kHz sample rate, despite the Windows Sound Control Panel settings being set to 48kHz sample rate and Reaper being set to use whatever the hardware was using. Checking the Line 6 Audio-Midi Devices App confirmed the same thing, and the Sample Rate Converter light in that app was on. I went through all the parts of the end to end system where I could set the sample rate and made sure all were aligned to the same settings (48kHz, 24 bit). There are four places I checked and aligned: 1) Windows Sound Control Panel/Playback tab/Line 6 POD HD Device Properties/Advanced/Default Format -> Set to 24bit, 48000 Hz (Studio Quality) 2) Windows Sound Control Panel/Recording tab/Line 6 POD HD Device Properties/Advanced/Default Format -> Set to 24bit, 48000 Hz (Studio Quality) 3) Reaper/Audio Device Settings -> Request Sample Rate to 48000 4) On the Pod itself, under the IO settings there is a setting for the sample rate of the S/PDIF interface. This name suggests it has nothing to do with the USB output, but I made sure it was set to 48Khz too. Annoyingly, I can't remember what the default was, so I can't remember if I changed this. After step 3 Line 6 Audio-Midi Devices App now reports no Sample Rate Conversion happening and Reaper also reports 48kHz operation. I also shut down some unnecessary audio-using apps (Skype, Google Music Manager and Steam) and removed the Windows System Sounds. I felt these were easy and prudent steps to take. I felt from the Line 6 article the general advice was to remove sources of noise and stuttering, so where I could remove potential sources easily for me I did so. I did not at any time remove my existing Focusrite Saffire 6 USB interface and its driver, so in my case at least the Pod is able to co-exist with other ASIO drivers. Note that the Focusrite wasn't being used as Reaper doesn't provide the option to use two ASIO devices at the same time, but was plugged in and powered on. I have not taken the time to isolate the single factor that has made a difference for me, however the BSODs did seem to clear up once I had got the Pod ASIO driver operating in 48 kHz sample rate instead of doing Sample Rate Conversion. I don't yet know why it was stuck operating at 44.1 kHz, as nothing before or after it was asking for that and I had not changed defaults. Furthermore, when I was trying to force it back to 44.1 to isolate the fix for this post it stubbornly refused to return to that rate. At this point I have arrived at a stable setup for me so I am unlikely to spend more time characterizing the cause, but will report back if I find something. I'd say it is likely others have this problem as I don't change defaults for this sort of thing. Effective Configuration - Disabled Selective USB Power Down - Disabled Windows System Sounds - Shut down unnecessary apps that use audio - Ensured Windows Sound Control Panel properties for Playback and - Recording on the Pod are set to 24bit, 48000 Hz - Reaper/Audio Device Settings -> Request Sample Rate to 48000 (key step for me) - Using front panel USB2 port I am sure not all of these steps are quite necessary for me, but wanted to share as completely as I could. General guidance, summary observations and speculations Clearly, reading the official advice at https://line6.com/support/page/kb/recording/computer-audio-set-up-and-troubleshooting/usb-audio-troubleshooting-r443/ is good practice. I've internalized that article as "you have to be as kind to the drivers for the Pod HD as you can". For me that meant getting over a Sample Rate Conversion that was happening, which I speculate takes extra cycles in the driver stack, introduces more potential error conditions and makes it more susceptible to stutter conditions. I am not sure why the driver was choosing to operate at 44.1 Khz instead of 48 Khz, but I have been able to force it to 48 Khz operation with Reaper. Removing unnecessary Sample Rate Conversion feels like good practice in any case. Getting the USB connection stable has been a big plus for me. The clarity of my recordings is better, I have stereo, so things sound fuller, it is easier to set levels and hear changes. It makes me feel like I need Helix Native less. Happy days :-) DM
  8. Super - thanks for clarifying! I still don't sound quite like Dan Auerbach. I blame Line 6 :-)
  9. Really appreciate all the thoughts. One tone to concentrate on (then tweak in different situations only if needed) feels like a weight off my mind! Thanks again for the responses, DM.
  10. Hi, I'm trying to get the most out of my Pod HD 500X by using it for both live use and for recording. I may move to a software amp sim package for recording, but for now I am trying to use the Pod as a singular rig I see posts and articles that say: - You will typically need different versions of a particular tone for live use and for direct recording. - When recording, the guitar sound that will sound good in the mix is not likely to be a guitar sound that sounds good on its own. Would anyone be prepared so share some examples of tones where they have a live and a direct recording version or a tone they set up specifically for recording to sound good in a mix? If you can't share the tone examples, I'd be grateful for some comments on the typical changes you make between a live version and direct recording version of a tone. If it helps, I am thinking about blues rock styles, and for the amp in the live situation, assume a PA or similar, rather than a guitar amp. For guitars, single coil or basic humbuckers, nothing active. DM
  11. Glad it helped. Hurghanico's points are all still valid, and offer you more control. If you hear unwanted clipping again you can reduce gain on the individual models in your chain. DM
  12. As well as Hurghanico's points, the Pod HD default input settings can cause your input signal to be hotter than you might intend. There is a thread about it here: https://uk.line6.com/supportarchivenew/thread/74045/ and the MeAmBobbo Guide talks about it here: http://foobazaar.com/podhd/toneGuide/setup#input If you want to try that quickly, take one of your patches with your LP and set Input 2 Source to Variax (or mic - something you are not using) and see if that cools your input. DM
  13. Hi, In what way is it different? Also, if you listen to your recording through the same headphones but via your on-board sound card, does it the sound the same as when you play back through the Pod? Do you have Record Monitoring on in Cubase? I am wondering if that makes you hear the sound twice when playing: once through the monitoring on the Pod, and again, slightly delayed, through the monitoring in Cubase. DM
  14. Some thoughts after digging into the Pod HD 500x for a year tl/dr: stick with it, you can get good results but you will have to dig for them, especially if you are new to modellers. What I was looking for First off, bedroom player. Low talent. Don't gig. Do jam and record with a friend. Low experience of actual amps and stompboxes. Been recording terrible songs on-and-off since teenage-hood, but getting back into guitar over the last couple of years after a long absence. That said, good aptitude with things digital and I do read manuals. Currently approaching the mid-century. Influences: delta blues, classic rock, dirty blues rock and goth/indie. I bought the Pod HD 500x after buying a reissue Big Muff. I wanted to get a Black Keys kind of tone. After using the Big Muff once I starting watching Rig Rundowns and realising that there is a lot to finding your tone(s). I realised that I might be on the start of some epic quest to find what worked for me. I started looking at pedal boards and pedals and power supplies and interconnects and then realised that I didn't want an expensive, buzzing mess of unreliable, unsightly and expensive pedals and interconnects when I didn't even know what sorts of tones I liked. I also wanted to be able to try different effects without having to go through the whole "which is the best Univibe, then buy it" loop. The idea of being able to just drop in a modelled effect with a few clicks really appealed. So, at that point I decided to go sim/multifx. I accepted there would be a compromise on "real tone" and on mojo. My thinking was that multifx would be neater and give me more experimental options. I did look into setting up a purely-VST- based rig. I worked out that the cost of the attendant midi foot switches and an expression pedal was not massively different to the various modeller floorboards that are available. Add in the cost of the software itself and it would be even more expensive. The idea of a dedicated unit that did everything in one box was really appealing. I looked into the various options. I should comment at this point that one of my guiding principles in life is not to be the guy with "all the gear, no idea". I don't want to have higher-end gear than I have knowledge and talent to use. I want to be able to fully exploit what I have, then move on if I outgrow. Because of that I discounted the Kemper and Helix-level products. I settled on the Pod HD 500x as it gave me lots of effects, a software interface, a physically-robust floorboard, an expression pedal, a looper AND the ability to send midi from the stomps to control VSTs if I wanted. It seemed reasonably priced for all the flexibility. At the time the Pod Go was not available so don't take this post as a comparison with the Pod Go. Starting with the Pod HD 500x Initial impressions were ok when I flicked through the presets. I'd been warned that they were all over the top so wasn't expecting to use them. I was left with the impression of flexibility and a wide range of tones available. As I dug in and started to try my own tones I did find it hard to get things right. There are many options. Not all sound good. They probably don't sound like the real thing in a lot of cases. My ear was uneducated. There is a lot of discussion on the internet but the nuggets are buried in a lot of subjectivity. I found that downloads from Custom Tone were helpful as a way of seeing how other people had got their tones. Some worked straight away for me, others provided a base. Many sounded very off so I suppose they didn't match my equipment or taste. Another possibility is that the person had uploaded a tone that just wasn't very good. Issue using HD500 tones, or uploaded tones that may have been re-labelled as 500x Don't try HD500 tones on your 500X. You can drag and drop them into HDEdit, but it doesn't mean they are quite compatible. The format of the files is different and it can make your floorboard decide to lose all patches. I had this problem very early on. It was not a big deal for me as I simply performed a factory reset, but it worried me at the time. To deal with this, firstly, regularly back up your whole bundle in HD Edit. Secondly, if you really want to try a tone from a different model, then load it into HD Edit, examine it without sending to the hardware, then create your own duplicate from scratch. It doesn't take long and then you know you have a compatible patch. Absence of Pod Farm HD and inability to reamp with Pod HD series After some time I realised that you can't really re-amp with the Pod HD series. There are ways to do it, but they are awkward. This made me long for what is present in the earlier Pod series and the in HX series: a software version. The earlier Pods seemed to come with Pod Farm for free. The Helix hardware offers a heavy discount on the matching software, called Helix Native. I really like the ability to just plug into my audio interface and record something, then tweak the tone later, with full recall. For some reason Line 6 didn't make a software companion for the HD series. Epic search through almost every amp-sim software available Realising this made me start to consider buying a third-party amp-sim/fx package. Sticking with Line 6 would make sense from a model-similarity point of view as I wanted to have some comparability between my recording and live tones. I was quite miffed at having to buy the models twice when this would not have happened with the previous Pod generation or the HX generation. I tried most every ampsim/fx package and singular plugin available. I read many threads debating the merits and how to set them up. Some basic findings and conclusions I came to: - All the ampsim/fx packages can sound fine in the mix, even the really old ones. - The newer and more paid-for sims do sound a bit better than the older ones and the free ones, but there is not a huge amount in it when listening solo and less when in a mix. - Some of the newer free sims are really excellent. You really can just go free if you need to. It would not be quite as satisfying as the paid packages, but you will be able to record stuff at a hobby level. The honestampsimreviews website was useful for finding free sims. I'd mention Amplitube 4 (the free starter), Mercuriall/Roxolder, Flextron and PSA from AXP, Ignite, Blue Cat and Kuassa as the ones I liked. - The newish, cheaper modular packages end up costing you about $200 by the time you have bought a couple of amp sims and the usual pedals you would use - overdrive/distortion, compressor, reverb, delay. I loved Kuassa for Caliburn, Matchlock and their overdrive. - The older all-in amp-sim packages like Pod Farm and Guitar Rig offer a lot of options but are somewhat overpriced given that they don't offer current technology. I would likely have bought Pod Farm (Platinum as I want the range of models) if it was discounted more. Both of these seem around $200 by the time you have carefully bought the right package on sale. - It is not particularly well-published, but Helix (including Native) incorporates legacy models which seem to cover the HD series models. So the elusive, non-existent Pod Farm HD could be achieved at some expense with Helix Native and the use of the Legacy models. - TIP: Getting the right level for your audio interface is not necessarily the same as getting the right level for your VST amp-sim (or any plugin I supposed). On your audio interface you want to set the gain as high as you can whilst leaving headroom to prevent your audio interface digitally clipping your input (so leave plenty of head room). Once you are in your DAW, your plugin will often offer an input level knob (often with a meter). Sometimes the documentation even tells you what range it is expecting. Set this appropriately as it makes a big difference to how the plugin reacts. Line 6 plugins give a good indications. In the end, all of this messing around and A/Bing different sims taught me a lot about modellers and how to optimise them. It caused me to read up a lot more about real-life mics, mic placement, speakers, cabinets and room sounds. Lol, I even read up on the history of the Celestion factory. This kind of thing is useful to be able to understand what the modellers mean when they talk about Greenbacks and Blackbacks. This knowledge and ear-education translated directly back to the Pod HD 500x, so I now get much better results with the Pod and am more confident using it. I don't slavishly choose "Greenback" because that is what someone's Rig Rundown says. I'm ok to choose Blackback, or a more modern cabinet as I know what it means. USB-recording issues The Pod HD audio drivers will blue-screen some modern Windows PCs. You see many posts about this. I have a couple of Win 10 desktop PCs I have tried the POD HD 500X on. One is older and never bluescreens. My newer one - which is the one I want to use - does bluescreen. It does it less if I use one of the USB 2 ports. Easiest workaround seems to be to just run from the 1/4inch outs into an audio interface if you have one (I do), but the quality does seem noticeably better on the USB interface. I wish Line 6 would create a solution for this issue. Although the Pod HD series is old, it is still a current product. So where have I ended up after a year of use? I like the Pod HD500x. It does what I bought it for - gives me lots of effects models and amp models, together with stomp-box-style foot switches and an expression pedal. I'm miffed that it does not have a software companion as the older and newer generations do. I will likely buy Helix Native when it is on sale sometime, but it pains me that I'm buying the models twice. The USB connectivity issue irks me. I will tinker a little more with some of the "downgrade your USB connection" options, but I do wish Line 6 would characterise this issue and issue a fix or workarounds so I don't have to spend the time. All the learning I did with other plugin options translated directly back to the Pod HD 500x and I can go straight to the models and effects I like to get the tone I am after, or something workable enough. As such, the need for reamping and the software companion is actually reducing. I've moved away from the concept of "Clapton used a JTM-45 on Bluesbreakers, therefore I have to use a JTM-45 model in the Pod" to trying different amp models and fx models to get a sound I like. For example, I'm enjoying the Soldano models in the Pod. I've never heard a Soldano in real life and the tones I like tend to be on the Marshall / HiWatt /Orange side. For whatever reason the Soldano models are sounding good to me. When I create a new tone now I do what the guides suggest. I start with a blank tone and add an amp. I adjust it so I like it, including adjusting the cab and mic options. You can sometimes get where you want to be with just an amp/cab model. Then I add distortion pedal(s) up front if I want/need and delays and reverbs after the amp model. You can double up if you want more subtlety / richness. I'm happy with what I am getting. I'm feeling enabled by, not limited by, the Pod. I love the integrated looper. Yes, it is basic, but it is good for getting ideas, noodling/practice and testing tones. TIP: move the looper to the front of the chain while tweaking tones. That way you don't have to keep replaying. TIP: Put the looper in half-speed mode before you record and you get twice the recording length. I presume there is a reduction in quality. Oh, the Line 6 model gallery is a joy as it shows you the original equipment that the model is based on. Then you can go and read about the history and use of that particular amp/pedal. You can see videos demonstrations of the real thing and listen to records on which it was used. Fun and educational. The knowledge translates really well into your use of the models in the Pod. Falling in love with my real amp I have a little practice amp that I bought 20 years ago. It's a Peavey Rage 158. We are not talking about a monster or classic amp here. I used to think it was awful, but it isn't. I was that I didn't know how to adjust the controls for a good sound as my ear was so poor. I suppose my playing has improved a bit too. Now I really like the clean and mildly-overdriven sounds from that little (loud!) amp. When I put the Pod in front if it I now have a ton of effects I can use. I like it! In Summary POD HD 500x is very flexible for the money. It does take time to get the most out of it, and there are some limitations. The journey will be a rewarding experience if you have the patience. Oh yes... trust your ears. It really is true. actually, let me add an edit: Develop your ears a bit by listening to lots of different things and then trust them. DM Appendix: Random nuggets All the Pod HD series sound the same. They have different form-factors and the newer ones will run more effects and have more in-built models, but sound is essentially the same. Fuzz pedals like to go first. The Output Modes on the Pod are a bit crude but they do the job. I really wish there was a clipping indicator as you can clip things internally in the chain and not always realise. Headphones don't sound like speakers. I need to work on that.
×
×
  • Create New...