|
The whole point behind distortion pedals is that they boost frequencies to create a controlled distortion sound - there's a lot of boost going on in there. What would be interesting is running the distortion through a compressor to see what effect that has.
This space for rent
|
|
|
|
|
True, but I have found Boss & Roland pedal which do the 'same' thing have some oddities at certain frequency's...(I had a load of FX pedal belonging to a guitarist friend of mine and a 'scope)
|
|
|
|
|
|
my friend has a mixing panel, I might try his and see if that solves the issue, good idea!
|
|
|
|
|
Can you mic up the amp and record off the mic?
|
|
|
|
|
Thought of that, but I have a rubbish mic and many cars pass by (making noise that's also recorded)
|
|
|
|
|
I have a TBone MB85, got it off Thoman.de, they are cheap and very good, almost as good as the Sure. Close to the amps speaker it should be selective enough, after all, its what many bands do on stage.
|
|
|
|
|
|
I had a quick google for guitar effect-pedal attenuators[^], to find that they do actually exist, and they're pretty cheap.
I'm not absolutely sure it's what you need, but it sounds like it.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Sheesh, software people. Hook up an oscilloscope and find out what your sound card is seeing. Some of that distortion could be up in the ultrasonic frequencies or something and causing sample aliasing errors.
We can program with only 1's, but if all you've got are zeros, you've got nothing.
|
|
|
|
|
Best answer here today,
Just one problem, how many software people own an oscilloscope?
I do, but I haven't used it in many years.
|
|
|
|
|
Jörgen Andersson wrote: How many software people own an oscilloscope?
Easy answer, any software person that needs to look at low bandwidth analog signals like audio should have one.
Here's a $20 (US) one[^] that uses a computer with a USB port for it's display & power, it even includes some digital inputs. It would probably be good enough to see what's going on with the OP's issue. There's others too. It's great for what it is, and was perfect for debugging my car, just don't expect it to be a high end oscilloscope.
We can program with only 1's, but if all you've got are zeros, you've got nothing.
|
|
|
|
|
I was actually looking up the proper procedure to swear in the new knights when I found this.[^]
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
I solved the issue below by completely re-installing VS 2017 version 26127.3
==================================================================================
Today there was a new update to VS 2017 RC that I found to be another Microsoft bomb - Yuck!
The version before this "improvement" was 26127.0
This "improvement" reports version 26127.3
It totally messes up VS 2017. After the update it refused to load all projects. Eventually I got a message I needed to install some or another package. After this install it loaded projects, but it lost the ability to format the styles of all XAML files. The settings for these files in Tools -> Options -> Environment -> Fonts and Colors is non-existent. All text in the XAML files is plain black and white.
I tried to restore the previous version of VS 2017 via a restore point, but after the restore there were other errors and all my custom folder settings were returned to MS defaults. 
I had to re-image my systems drive to a recent image to get VS 2017 to work the way it did yesterday. Yuck and double Yuck!
It seems that MS is doing minimal testing on new releases and depends on their customers to do the testing for them. So what else is new? 
Get me coffee and no one gets hurt!
modified 2-Feb-17 12:23pm.
|
|
|
|
|
At the risk of being the devil's advocate here, it's a release candidate. In a large product like visual studio, I suspect that not every possible bug shows up readily no matter what kind of testing gets done.
While I empathize with you, and while I thank you  for posting this information here, I do hope that you've logged an appropriate defect with the visual studio team as it's the only way they may know of this defect.
|
|
|
|
|
Yes, I did file the issue with Microsoft, but as you can see above, I did solve the issue.
Get me coffee and no one gets hurt!
modified 2-Feb-17 13:12pm.
|
|
|
|
|
It'd be nice if the OS had a "snapshot" facility like that of VMWARE or Hyper-V. Then rolling back would be simple...
#SupportHeForShe
Government can give you nothing but what it takes from somebody else. A government big enough to give you everything you want is big enough to take everything you've got, including your freedom.-Ezra Taft Benson
You must accept 1 of 2 basic premises: Either we are alone in the universe or we are not alone. Either way, the implications are staggering!-Wernher von Braun
|
|
|
|
|
TheGreatAndPowerfulOzIt'd be nice if the OS had a "snapshot" facility like that of VMWARE or Hyper-V. Then rolling back would be simple...
This is precisely why I (and I suppose many others) install non-stable versions of software on a VM. 
|
|
|
|
|
Including Windows from a VM running under Linux?
#SupportHeForShe
Government can give you nothing but what it takes from somebody else. A government big enough to give you everything you want is big enough to take everything you've got, including your freedom.-Ezra Taft Benson
You must accept 1 of 2 basic premises: Either we are alone in the universe or we are not alone. Either way, the implications are staggering!-Wernher von Braun
|
|
|
|
|
TheGreatAndPowerfulOz< wrote: Including Windows from a VM running under Linux?
If you mean RC releases of Windows OS, then yes, unless required, I always run RC software on a VM.
Given your hypothetical situation, I don't see why should the host OS necessarily be Linux. I use another OS than Windows only when required.
|
|
|
|
|
Why stop there? Everything I run these days is inside a VM. My host machine has nothing but motherboard drivers and the like.
|
|
|
|
|
dandy72 wrote: Why stop there? Everything I run these days is inside a VM. My host machine has nothing but motherboard drivers and the like.
Visual studio is a large and and complex piece of software. From experience, usually when something goes wrong with the unstable version of VS, it won't just go down but will take the other (stable) versions of VS down with it. If your development is mainly VS based (like mine), it leads to a completely stuffed-up development environment and a lot of frustration, followed by a clean wipe and install of the OS and the rest of the software.
If you install and run the RC version of something crazy big like visual studio on your main development machine, you hopefully know the risks that accompany it. It's all joy and fun when it works, but when it doesn't, it leads to threads like this and someone will eventually come along to say "told ya so".
modified 1-Feb-17 22:39pm.
|
|
|
|
|
I'm not sure if you understood what I meant. I haven't simply switched to running everything inside a single VM - I run everything in separate VMs. I have one for VS2015 (my daily driver), another for 2008 (for projects that for one reason or another, can't be upgraded), another for my domain controller, another for WSUS (to update all the VMs), etc. And obviously, any RC will have its own VM.
When something goes down hard, the damage is limited to that VM only.
|
|
|
|
|
Sorry, I thought you were being sarcastic.
While your approach offers great reliability and peace of mind, it does require a lot of discipline and therefore extremely unsuitable for me.
|
|
|
|
|
Rajesh R Subramanian wrote: Sorry, I thought you were being sarcastic.
I'm sarcastic by nature, but this was definitely not one of those instances. I seriously don't have anything installed on the host OS other than Windows Server, Hyper-V, motherboard drivers, and updates for all of those. As such, I never bother backing up the host - it's just as quick to reinstall. Backing up the VMs is trivial, and snapshots, as you know, are extremely useful.
Rajesh R Subramanian wrote: While your approach offers great reliability and peace of mind, it does require a lot of discipline and therefore extremely unsuitable for me
Well, I can't help you there. But I've been using practically nothing but VMs here at home since Hyper-V became standard in Server 2008...and once I understood the flexibility, portability and convenience, there was no going back.
Of course now I want my next machine to have 128GB of RAM instead of my current 64...
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
