This was a tough one but good news is that the bad microphone quality issue in combination with an USB microphone has been resolved for me.
This is the story….
I’ve recently upgraded to a brand new powerhouse of a PC and was thrilled to play my favorite games together with my friends. The joy of this new machine came to a halt when I was told I sound really bad – like on a telephone. I’m using an Auna CM 900 USB Microphone so sound drivers can’t be the reason or can they? Since I’ve only changed the PC and not the Microphone, I did a short investigation on several locations. The things I’ve checked were:
Are all the sound drivers up to date?
Is the CPU load too high?
Is something wrong with the settings inside Teamspeak?
Is the quality also bad when using different recording tools?
…and so on…
Then, after doing the aforementioned standard procedures, I checked the internet and stumbled across several threads about bad microphone quality inside Teamspeak. They were telling that the quality in other applications was great but only Teamspeak would do the strange sound. Of course this would make perfect sense if the Teamspeak client would manipulate the input sound somehow but it doesn’t. It just takes the „raw“ signal and pumps it into the server. This is also true for playback – more or less. After an hour or so of reading I came to the conclusion that none of the threads were any help at all since everybody seems to focus on the sound card or drivers. So I went on a search inside the well obfuscated UI of Windows 10….
First of all the Issue could be much obvious if the UI of Windows was more clear about were to click to achieve something. It’s mindboggling how Microsoft decided in the last years that it’s wise to lock away the in-depth technical guts of hardware properties behind unmeaningfull text.
After tinkering fighting with the UI for a moment, I was able to have a look inside the controller settings.
But this post would be over right here if Windows was nice but it isn’t. As soon as you apply the setting it may happen that some app is locking on your microphone. As soon as you switch to another microphone you wouldn’t reach the magical link to the device settings. Bummer.
The last step is just selecting the microphone back to be selected as default:
As a more or less seasoned computer professional this one drove me almost crazy… either I’m getting old or this stuff is getting weirder 🙂
This post is intended to help others achieve great results with their camera.
When I began using the Osmo+ I was baffled at first what this thing can do but soon the euphoria came to a halt because the material just didn’t look as natural as I’d like. Especially shots of cars felt weird as if something is wrong or missing. I even went through the process of viewing the resulting videos on different screens…This is where the story begins. Right now I’m testing different styles and settings and -prior- I’ve read a lot of opinions to investigate on the subject LUT development for the X3 Zoom without spending money on prefabs. Almost no profile provided satisfied my needs and if so the thing is just too pricey. Most of the supplied LUTs are even developed for aerial photography on the Mavic or the-like. Getting nowhere with the color correction stuff I headed out to try it on my own. How hard can it be to develop a self-made LUT anyway? We’re talking about color correction after all!
After several tries I came to the conclusion that simply the base correction is key, while also taking care of the camera settings in the first place in order to receive natural looking, vivid colors with the camera. You can then go ahead and safely add color corrections to give the image a certain visual style as you prefer and not as the seller of the LUT wants it. Just getting the whole color spectrum right without applying any effects. So the ultimate goal is to achieve a safe foundation, a starting point for getting the most out of it. This means having your camera set up correctly. It is absolutely vital to produce footage that’s close to what you expect. No software can effectively turn bad source material to perfect cinema-quality videos and if it could, the rendering times are just terrible…
So once more I’ve jumped into the car and recorded some footage to test out what works best. After this trip I was confident to have something to share with the community!
Alright – first things first, here’s a comparison video where three different styles have been applied on top of the LUT correction and in the LUT applied without any effects. The first two clips are recorded out of the window while it was down, the other two are recorded straight through the windscreen:
This LUT is optimized for best performance of the sensor which means shooting at ISO 100, 1/60 for 30fps and 1/120 for 60fps. In order to achieve that it might be necessary to have a set of ND filters handy. In this video for example it was necessary to put on the ND16 even though the Sun was just two hours away from setting. Keep in mind that the source material must be free of artifacts of any sort in order to achieve clean output. That’s something I forgot to take into account way back when I just started to use the Osmo+ Profile: D-Cinelike Saturation: +2 Contrast: 0 Sharpness: -1
Why Cinelike? Most of the information on the web states that D-LOG is the way to go but this profile produces weird artifacts like moireé and grain that can’t be removed easily. It’s just not right for the X3 in my opinion. You’ll get a 100% better results with D-Cinelike right from the start. Usually you would want to have the source material as flat as possible to have more leeway in post production. Unfortunately the sensor of the X3 doesn’t cut it with the D-LOG profile and what you’ll end up with it is just muddy material.