Skip to main content

On Addictivity And Connectivity

First things first—after a year (at least) of drooling over one, I finally decided to cash in my almost-two-years-of-non-smoking credits, and got myself an EWI.
It sounds a bit like a medical condition, and frankly, it's quite mental, because I can't stop playing with it.
So far it seems to be an amusingly addictive instrument even with a stock soundbank—I plan on making my own patches later, as soon as I figure out how to use that UniQuest joke of a software—worst of all, it can be played in headphones, so I can do it even at 4am if I wanted to. So far, I have more fun then problems playing it, in spite of its little fingering differences (I use SA(x) mode), and totally different breathing technique.
Now comes the connectivity part.
I've used FastTrack USB for a couple of years with a microphone through the XLR input with no problems, but when I tried to connect a line output of EWI's synthesizer to the line input of the FastTrack, the signal level was very low. There was no noise, it was just quiet, even with the track volume all the way up—no match for the rest of the tracks.
I use FastTrack USB for audio input, and built-in audio for output, it's connected through a hub (no problems for two years). In GB microphone is going to the Channel 1 (mono), and still works fine. Synthesizer goes to Channel 2 (mono) and is really quiet. I tried the EWI with two different 1/4" cables with no difference.
After some more research on the Net it appeared to be that all the FastTracks suffer from the same problem, which makes me believe that it's not a bug, but a feature of an unexplainable kind.
Oh, well, back to my old iMic noisemaker (this one works, it's just screened very poorly, so it picks up all the possible interference, and also makes its own little nasty hiss—this is why I switched to the Fast Track a while ago—so I will need to cut it out with an equalizer).
Hopefully, the EQ surgery will not affect the synthesizer's sound consistency and quality as severely as it used to, when I was dealing with a microphone's input.
We'll see. There is also Lightsnake*, which looks very nice...

____
* Ended up getting the Lightsnake eventually. Works fine, in spite of it showing up as "Unknown USB Device" in GarageBand menu.

Popular posts from this blog

WordPress: How to add custom fonts to a twenty seventeen child theme.

Quick help to those who have tried to find some help and failed (as I have so I have to write the code myself). Assuming that you have your virgin child theme configured and activated: here is a function which goes into the functions.php file (of your configured and activated child theme): function childtheme_twentyseventeen_fonts_url() { $replace_original_font = true; // unless you really like Libre Franklin if ($replace_original_font !== true) { $hyph = '-custom-'; } else { $hyph = '-'; }; $font_families = array( //add your Google fonts and weights (400 and 700 are defaults for normal and bold) here: 'Oswald:200,400,700', 'Lato:200,400,700', ); $query_args = array( 'family' => urlencode( implode( '|', $font_families ) ), 'subset' => urlencode( 'latin,latin-ext' ), ); $fonts_url = add_query_arg( $query_args, 'https://fonts.googleapis.com/css' ); wp_enqueue_style( 'twentyseventeen' ....

How to Make a Website Everyone Has

On The Endless Wonders Of Internet Explorer

May be somebody will stumble upon this post and save some time for him/herself. Apparently—it only become apparent after several hours of trial, cursing and error, as it usually goes with IE—, Internet Explorer (up to version 7) throws a runtime error, if you try to modify innerHTML of the dynamically created element under certain conditions. The conditions, as it always go with IE, are significantly lacking consistent logic. For starters, if you assign innerHTML to the element before you insert it into a DOM tree, the error may not come up at all, but will surface later, when you try to modify it. So far it looks like the error mostly comes up, if you change innerHTML of the block element inserted into inline element (which is not kosher in standard-compliant HTML, so it makes sense), and some nested block elements (like DIVs inside Ps—why is that considered wrong, too?—for instance). So, if one really-really need to insert a division into a paragraph, and w...