I envy those who can pass this… By the way going disabled way was of little help because the audio hint was hardly better recognizible…
// Oprogramowanie Roman Ryltsov
I envy those who can pass this… By the way going disabled way was of little help because the audio hint was hardly better recognizible…
Recently it was the time to sort out an issue with a video DMO, which outputs YV12 video and in the same time is capable of supporting extended video strides in order to efficiently make a direct connection to Video Mixing Renderer Filters. From past experience, I already knew that some bugs are definitely involved…
Once again, there was a need in Nokia software to backup phone contents before sending new phone to service. The new phone, new model, latest firmware has Bluetooth subsystem failing to connect to PC’s bluetooth, to bluetooth headset etc. – it’s worth a separate story itself. So Nokia PC Suite, the latest the greatest version…
In order to obtain a reference audio source and especially useful for debugging purposes, including: audio input device unrelated to physical device, to avoid conditions when device is already in use by someone else non-zero audio signal which is independent of certain speaker or broadcasting service, including one that makes capture, transmission or rendering issues…
While new NTFS Links propery page is looking for contained junction points, it shows an animated picture to indicate opertation in progress. The picture is a stock resource and is taken from shell32.dll resource type “AVI” name 150. It is an Audio Video Interleave (AVI) file embedded into binary resources as is. What is however…
Having installed Visual Studio .NET 2008 Service Pack 1 (installs Windows SDK 6.0a) and Windows SDK 6.1, I would obviously like to have newer Windows SDK used in include path. However after edit of WindowsSdkDir environment variable and checking all include directories to point to new Windows (former Platform) SDK path “C:\Program Files\Microsoft SDKs\Windows\v6.1“, MIDL…
Some time ago I faced an annoying problem with a freeze of Visual Studio opening a solution with a Setup Project. I found that the problem was related to setup projects (.vdproj) that time and it was something with Visual Studio update, but I was of an opinion that Visual Studio .NET 2008 has problems…