I’ve been using Google Chrome browser on Windows 7 x64 these days, and it annoyed me how bad the fonts were being rendered. Too light and somewhat pixelated. After a quick search I found some tips, with most fixes revolving around the LCD antialiasing setting, which didn’t work for me. What did the magic was actually installing and configuring an extension named Font Rendering Enhancer.
This extension has only one setting: “font width”. After adjusting it to “50”, voilà, the fonts started looking good. And, of course, allowing it to work in incognito mode.
Saturday, November 19, 2016
Friday, October 28, 2016
Clean tones of Ibanez JPM100 P2
I recorded an improvisation of my 1997 Ibanez JPM100 P2, which has DiMarzio Crunch Lab + LiquiFire instead of the stock DiMarzio Steve’s Special + Air Norton. The previous owner did the replacement, and I kept it because it sounds crazy good. In fact, these new pickups sound very similar to the original ones, but with more gain.
I used my POD HD500X straight into the computer and a set of .007 Dunlop Rev. Willy's Lottery strings.
I used my POD HD500X straight into the computer and a set of .007 Dunlop Rev. Willy's Lottery strings.
Monday, September 12, 2016
Visual Studio Code slow startup on Linux
Recently I’ve been having a problem with Visual Studio Code, current version 1.5.2, on Linux. The program startup was too slow. I mean, the absurd of waiting over 40 minutes from the doubleclick until I see the window!
I discovered that there are two executables within the VSCode package: one at the root directory, and other inside “bin” subdir. The outer seems to be a wrapper to the inner, since I made a test and ran the inner executable alone... and bang, VSCode started in about 3 seconds – not an example of quick startup, but acceptable.
So I redirected my shortcut to point directly to the executable inside “bin” subdirectory. Whatever the outer executable does, it’s clearly buggy.
I discovered that there are two executables within the VSCode package: one at the root directory, and other inside “bin” subdir. The outer seems to be a wrapper to the inner, since I made a test and ran the inner executable alone... and bang, VSCode started in about 3 seconds – not an example of quick startup, but acceptable.
So I redirected my shortcut to point directly to the executable inside “bin” subdirectory. Whatever the outer executable does, it’s clearly buggy.
Tuesday, August 23, 2016
Visual Studio Code keyboard shortcuts
These days I’ve been using Visual Studio Code at work. It’s a nifty editor written in NodeJS. Being a Visual C++ user, however, I missed some keyboard shortcuts I like to use. To remedy this, I customized the “keybindings.json” file to make it more familiar. To use it, go File → Preferences → Keyboard Shortcuts.
As a meta side node, this is the first time I use GitHub’s Gist to share code of mine.
As a meta side node, this is the first time I use GitHub’s Gist to share code of mine.
Sunday, May 1, 2016
Git .gitignore file to Visual C++ 2015 Update 2
After upgrading my Visual C++ 2015 from Update 1 to Update 2, I noticed that a new file appeared in the root directory of the projects I was opening. The file was always named
The change also demanded an update on my
ProjectName.VC.db
. Indeed according to the release notes, a new SQLite-based database engine is now being used by default, and that’s the file where the database is stored. The old file, named ProjectName.sdf
is now unused and can be safely deleted.The change also demanded an update on my
.gitignore
files to also ignore this new database file, and here it goes:
Debug/ Release/ *.aps *.db *.ffs_db *.ncb *.opensdf *.rar *.sdf *.suo *.user *.VC.opendb TODO.txtIf you import and old
.vssettings
file, however, the option to use the new SQLite-based database can be rolled back to the old .sdf
files. To manually change it, go to: Tools → Options → Text Editor → C/C++ → Advanced → Browsing/Navigation → Enable New Database Engine. Set it to “true”.
Wednesday, March 23, 2016
Disabling C++ exceptions in Visual Studio 2015
When using the STL with Visual Studio 2015 – and older versions, probably –, C++ exceptions are enabled by default. To view the options specified below, first add at least one CPP file to your project.
The first thing to change on the project settings is under C/C++ code generation, enable C++ exceptions: set this to “no”.
Then, on the project settings, C/C++ preprocessor, to each configuration and platform individually, add the following preprocessor definition:
The first thing to change on the project settings is under C/C++ code generation, enable C++ exceptions: set this to “no”.
Then, on the project settings, C/C++ preprocessor, to each configuration and platform individually, add the following preprocessor definition:
_HAS_EXCEPTIONS=0This way you’ll be able to use the STL without the C++ exception handling mechanism.
Saturday, March 5, 2016
Clean tones of PRS Custom 24
This is the most beautiful sounding guitar I’ve ever owned or played, possibly. Being a hardcore superstrat player, I’m having a hard time adapting to the radiused fretboard and the unbalanced body shape – not unbalanced as a Les Paul, but definitely butt-heavy.
So I recorded this improvisation using the POD HD500X looper. I see myself selling this guitar soon: that’s how I want to remember it.
The video was recorded with the great Samsung Galaxy S6, in 1080p and 60 fps.
So I recorded this improvisation using the POD HD500X looper. I see myself selling this guitar soon: that’s how I want to remember it.
The video was recorded with the great Samsung Galaxy S6, in 1080p and 60 fps.
Subscribe to:
Posts (Atom)