Skip to main content

...iKaossilator!

I have the original yellow Kaossilator, and I am a big fan. This app, although visually similar in many ways, is fundamentally different in the way it handles the phrases you create; it's not better or worse, it's just different, and if you are to use it, you just have to learn.
First of all, it does not record and loop sound, like the original Kaossilator does, it records sequences. The downside of it is that one can't endlessly overdub the track, using the same voice, it will start erasing previous loop eventually (but they do give you five layers to play with, so there is plenty of space to build your riffs). The upside is that you can save, undo, redo the sequense, return to it, re-record, reassign instruments, change the key, tempo, scale, everything, all in real-time, and then save it again.That is big. And the mix play is a very nice feature.

WHAT IT NEEDS:
Ability to export MIDI
Ability to import MIDI (there is no way the tracks in app's library were made with the app, no one can play a touch pad the way the keyboard is played, it's even smaller the the pad on the hardware Kaossilator)
Dynamic GRID on the pad, reflecting th actual scale being played.
Ability to be MIDI controlled with an external controller (I'd pay extra just for that, the syn sounds are awesome, well... KORG it is...)
I want the Drone sound back (#60), and the rest of the effect sound missing from the original Kaossilator set!!!

iPad version with a bigger pad would be nice, too...

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' ....

{position:fixed} in iOS 6

I stumbled upon this oddity when upgrading to iOS 6 while working on a mobile advertising project, and it took me a better part of the day to figure out what is going on: all of a sudden an element {position:fixed} stopped working in a correct manner (which is staying put, while the page is scrolling), and started "sticking" to the scrolling page, moving out of the viewport, and then just "jumping" back to the correct location after the scrolling was finished.If you scroll this page , you will see it—hint: that's the one labeled "broken"—assuming that you have a correct device/browser combination. Mine was iPhone4 and iOS 6.0 (6.0.1-6.1.3 behaves just the same). On the original page, where I first encountered the problem, all of my elements were created dynamically using JavaScript, but at the end of the day (literally) it become clear, that the glitch is in the iOS 6 CSS implementation.Here is what happens: if you have an element {position:fixed} whic...

How to Make a Website Everyone Has