Have to pay for my web hosting for the next year next Sunday but I am seriously poor.
Like after bills I have a around 50€ for food and everything else!
As you can tell I have not figured out how to  make the website rentable at all...
(These two years I have made a whooping 110 euros through the website and spent 180)
And my other activities as an artist just keeps me afloat...
Not complaining at all as I rather be dirt poor and free to make art than  working with something that does not make any sense to me...
In either case it would be in your interest if you want to continue to see the website in this format for a longer time. The webhosting is one of those where it can be a free version with less options and have the option to pay for some extras... so it would continue in either case but it would be a less flexible site.
So if there is an interest in supporting Musical Android please use the Paypal button Buy Now on the right side. 

This music made with the funky app Kosm!
It is one of my favorite apps and it just got a update making it even greater.
For free and without publicity...

The latest update:

changes for version 2.0.2:
- added reset mode for clearing all orbs
- added support for small screens
changes for version 2.0.1:
- implemented low latency audio engine
- implemented high resolution graphics
- optimized UI
- removed the previous two minute limit on recordings
- greatly improved the writing speed of saving the recording

Play Store info:
Ready to rock your next party? Introducing djay 2 - the next generation of the world's best-selling DJ app is now available on Android.djay transforms your Android device into a full–featured DJ system. Seamlessly integrated with Spotify and all the music on your device, djay gives you direct access to mix your favorite songs and playlists instantly. You can perform live, record mixes on–the–go, or enable Automix mode to let djay create a seamless mix for you automatically. Whether you are a professional DJ or a beginner who just loves to play with music, djay offers you the most intuitive yet powerful DJ experience on an Android device.

FEATURE HIGHLIGHTS

• Spotify integration 
• Music library integration (all files on your device, no access to Google Play Music)
• Automix 
• Match: intelligent song recommendation engine powered by The Echo Nest
• Audio FX: Flanger, Phaser, Echo, Gate, Bit Crusher 
• Mixer, Tempo, Pitch-Bend, Filter and EQ controls 
• Looping & Cue Points 
• Colored HD Waveforms™ 
• Live Recording (local music only)
• Sampler with included sound FX, drums, and an exclusive pack by Snoop Dogg
• Single Deck portrait mode 
• Pre-Cueing with headphones (using Griffin DJ Cable) 
• Advanced time-stretching (requires quad-core Nexus device) 
• Automatic beat & tempo detection 
• Auto-Gain 
• Support for all major audio formats 
• Support for Bluetooth devices
• Support for DJ MIDI Controller (Reloop Beatpad)

Watch DMC Champion DJ Rasp perform on djay for Android: 
http://youtu.be/OhBJnDUxMEU

Spotify integration requires Spotify Premium and an internet connection, a FREE trial is available.

This is the first article in a series where developers talk about different issues regarding making applications for Android. To start with andreas the developer of G-Stomper Studio, VA-Beast and G-Stomper Rhythm will talk about latency as this is something that concerns many music makers that use Android.
If you are not a programmer do not be scared to read it as it is also understandable for non-programmers!

So thank you so much Andreas for taking the time to write and share with us all!
_______________________________________________________________________________________________________
Latency in audio applications is probably one of the most discussed and also one of the most annoying issues on the Android platform. Understanding and handling latency the right way can be a mighty jungle, especially if you’re a “normal” developer, and not a scientist.

This article is focused on output latency on Android devices, not input or round-trip latency. Hopefully someday I’ll be able to write about input latency as well, but so far input and round-trip was no issue in my applications. So the term latency in this article is always meant as output latency. Also please forgive me when I forget some scientific details. It is neither my goal nor am I able to write a scientific paper about latency on Android. What you read is my personal experience with the different aspects of output latency on the Android platform.

Output Latency, what is it?

In short, output latency is the time from the moment you press a button or a piano key until you hear the sound from the speakers. And, output latency in audio applications is something we all want to get rid of.

The complete output latency in a musical application, which includes live playing, is a combination of the following 3 main factors:

1. Control Input Latency (e.g. display reaction time)
2. Application Latency (everything that happens in the app layer)
3. Audio System Latency (everything that happens in the system layer)

Control Input Latency (e.g. display reaction time)

The Control Input latency is the time from the moment you touch the screen (or an external MIDI Keyboard) until the audio system gets notified by the Android OS to do something. It is influenced by various factors, which strongly depend on your device and Android version. It can vary from a few milliseconds up to 300ms or even more. The Control Input Latency is under full control of the Android OS and the underlying hardware. There’s no way to optimize or measure it from inside an app. But can get rid of a good part of it by using a MIDI controller/keyboard. The reaction time of an external MIDI keyboard is usually around 30-40ms faster than the on screen controls. This may surprise you, but the undisputed king regarding display reaction time is still the Google/Samsung Galaxy Nexus (2011).

Audio Output Latency (everything after the Control Input Latency)

The Audio Output Latency is the time from the moment when an application starts to play a sound until you hear it from the speakers. The Audio Output Latency is hardware, operating system and app dependent. A good part of it can be optimized from inside the app (as long as the hardware and operating system allows it). The Audio Output Latency can vary from ~35ms up to over 250ms. Sure, there are apps that report latencies down to 10ms, but this is not the complete thing (more about this later).

Application Latency (everything that happens in the app layer)

“Application Latency” is not an official term. I call it that way that way because it happens in the main application, the audio app. Meant is the time from the moment when an application starts to play a sound (technically when it starts to fill an audio buffer) until it is passed (enqueued) to the underlying audio system (AudioTrack or OpenSLES). This part is under direct control of the audio application. It depends on the defined audio system main buffer size and the app internal buffering.

AudioTrack is the out of the box system, which guarantees to run stable on every Android device.
It is not thought to be used in real time audio applications, but since it’s the one and only ready-to-use system, it is used in most audio apps. AudioTrack has a device dependent minBufferSize which can be obtained by invoking AudioTrack.getMinBufferSize(). In short, AudioTrack has the full control over the minBufferSize as well as over the way the buffers are handled (once a buffer is passed to the AudioTrack system). The lowest ever reported minBufferSize by AudioTrack comes from the Google/Samsung Galaxy Nexus (2011) and corresponds to an application latency of 39ms at a sample rate of 44100Hz. More likely on modern non-Nexus devices are minBufferSizes around 80ms. Using smaller buffers with AudioTrack than the reported minBufferSize usually results in an initialization error.

The native OpenSLES system on the other hand allows more control. The buffer size as well as the way the buffers are handled is under responsibility of the app developer. OpenSLES allows smaller buffers than AudioTrack, of course only as long as a device can handle it. The smallest well working OpenSLES buffer size in the G-Stomper environment corresponds to an application latency of 10ms on Android 5.x and 20ms on Android 4.4 (both with a Nexus 9).

The application latency can be calculated with a simple formula:

AUDIO_SYSTEM_MAINBUFFER_LATENCY_MS
 = audioTrackByteBufferSize * 1000 / sampleRateHz / bytesPerSample / numChannels

APP_INTERNAL_BUFFER_LATENCY_MS
= internalFloatBufferSize * 1000 / sampleRateHz

Now take the max of these two values and have the Application Latency.
On the Android platform, this value can vary from ~10ms up to ~200ms.

Audio System Latency (everything that happens in the system layer)

One of the biggest mistakes regarding output latency is the fact that most apps on report only the Application Latency. This looks of course nice (e.g. Nexus 7 2013/AudioTrack: 40ms), but it is only half the truth.

The moment a buffer is passed to AudioTrack for example does actually only mean that the buffer was enqueued to the AudioTrack internal buffer queue. But you never know exactly how much time will pass before the buffer will actually come out as a sound from the speakers. The time from the moment when a buffer is passed to the audio system until you actually hear it from the speakers, is what I call the “Audio System Latency”.

The Audio System Latency comes in addition to the Application Latency and strongly depends on the audio system internal buffer pipeline (buffer queue, resampling, D/A conversion, etc.). Regarding low latency, this is the most significant part of the latency chain, which reveals the obvious problem of AudioTrack. With AudioTrack, you don’t have any control over its internal buffer pipeline, and there’s no way to force a buffer to pass it more quickly. What you can do is to prepare the buffers as final as possible, e.g. do the resampling in the audio application and pass the buffers always at the systems native sample rate. Unfortunately this does not change the latency, but it avoids glitches due to Android internal resampling.

I’ve measured Audio System Latencies of over two times more than the Application Latency. In other words, if the Application Latency is 80ms, it can easily be that the full output latency is more than 240ms, which is ridiculous for a real time application.

What did Samsung in their Professional Audio SDK to achieve such low latencies?

I’m no scientist, but it’s quite obvious that they reduced the audio pipeline (application to speaker) to a minimum, and they did a very good job with impressive results. Unfortunately the SDK is for Samsung devices only, but it’s for sure a great pioneer work, and maybe it’ll motivate others to catch up. There’s a nice video presentation of the Samsung Professional Audio SDK on YouTube: https://www.youtube.com/watch?v=7r455edqQFM

For (supported) Samsung devices, it’s definitely a good thing to consider the integration of their SDK.

What can you do as an app developer to get a faster audio pipeline?

Go native! Using the native OpenSLES reduces the Audio System Latency significantly. Even if you work with the same buffer size as with AudioTrack, you’ll notice a big difference, especially on newer Android versions.

Using OpenSLES does not implicitly mean “low latency”, but it definitely allows lower latencies than AudioTrack, because all audio buffers are written directly to the audio hardware, without the AudioTrack API and Dalvik/ART runtime overhead. This means the audio pipeline is shorter and therefore faster.

“The Audio Programming Blog” provides good tutorials regarding the OpenSLES integration:
https://audioprograming.wordpress.com/2012/03/03/android-audio-streaming-with-opensl-es-and-the-ndk/
https://audioprograming.wordpress.com/2012/10/29/lock-free-audio-io-with-opensl-es-on-android/

Also helpful is this article on GitHub:
https://github.com/igorski/MWEngine/wiki/Understanding-Android-audio-towards-achieving-low-latency-response

The “Google I/O 2013 - High Performance Audio” presentation gives a good overview about low latency audio on Android in general.
https://www.youtube.com/watch?v=d3kfEeMZ65c

Will the G-Stomper apps get OpenSLES support?

Yes, definitely. Actually, OpenSLES is already integrated as an experimental additional audio system. In the current version 4.0.4, it is exclusively available for Nexus devices. The upcoming version 4.0.5 will introduce the OpenSLES to all 1ghz Quad-Core (or faster) devices running on Android 4.2 (or higher). The default will still be AudioTrack, but users with supported devices will get a notification and will be able to manually switch to OpenSLES in the G-Stomper setup (Setup dialog / Audio / Audio System / OpenSL).

How can the full output latency get measured?

Unfortunately there’s no proper way to automatically calculate the full output latency (Control Input Latency + Application Latency + Audio System Latency) from inside an app. The only way to get real numbers is to measure it.

There’s an article on android.com, which shows a way to measure the full audio output latency (Application Latency + Audio System Latency) in use of an oscilloscope and the device’s LED indicator:
https://source.android.com/devices/audio/testing_circuit.html.
But honestly, by far not everyone has that equipment.

Here’s a simple way to measure full output latency:

The only things you need are a microphone, a PC with a graphical audio editor installed, and an Android device. While recording on the PC, hold the microphone close to the screen, and tap some button or piano key on the Android screen, which is supposed to play in a sound. Be sure to tap the screen hard enough, so that the tap is audible. The microphone will record both, the physical finger tap and the audio output. Then, in the audio editor on the PC, measure the gap between the two peaks (finger tap and audio output).

Be sure to make more than one recording and take the average of the measured times. Especially the display reaction time may vary over multiple taps.

There might also be a quite significant difference between the head phone jack (with an external speaker connected) and the device internal speakers. Using the device internal speakers may result in higher latencies because of the post processing, which is usually done for internal (low quality) speakers.

This is definitely not the most scientific and also not the most precise approach, but it’s precise enough to give you an idea of the real output latency. You’ll be surprised by the results.

Have used and played with Pixivisor and think that it is genius to use in different ways to create interesting videoclips. One thing that did not get tried though is to use as in this video just simpler shapes and colour combinations. As you can see it can be pretty effective.
For the ones thta have not heard about this application it is for making videos and is not a soudn application. Why there is the white(?) noise is because you transmit images through sound from one device to another. There is also a free desktop version.

Hey this is great if you need high quality recordings and have some cash laying around as it is not cheap but that is relative as these types of microphones easily can get up over the hundreds!
The good news is that you can use it with the desktop as well so if you are looking for a condenser microphone for the desktop this could be something to look  into as it would be for your USB OTG devices as well...

Here is the official publicity:

Make professional studio-quality recordings on the go

Introducing iRig Mic Studio, IK Multimedia’s ultra-portable large-diaphragm digital condenser microphone for iPhone, iPad, iPod touch, Mac, PC and Android. It packs a 1” diameter condenser capsule into an ultra-compact enclosure that can be used to make professional-quality recordings anywhere. Great for musicians, vocalists, home producers, podcasters, broadcasters, voice-over artists and more, it puts the superior power of a large-diaphragm microphone into the palm of your hand.

Features

• Professional studio microphone with large-diaphragm capsule
• Ultra-compact size that’s easy to carry around
• High-quality 1” back electret condenser capsule
• 24-bit converter with 44.1/48Khz sampling rate
• Low-noise, high-definition preamp
• Integrated headphone output
• Multicolor LED status and level indicator
• Onboard gain control and headphone level control
• Comes with a full suite of IK apps
• Includes portable tripod tabletop stand
• Includes Lightning, Micro-USB OTG and USB cables
• 30-pin cable available separately
• Available in black or silver version

Big sound, small size

What’s remarkable about iRig Mic Studio is that it offers its truly amazing recording quality in an enclosure that’s smaller than an iPhone. It features a large 1” diameter back electret condenser capsule, a 24-bit audiophile-grade A/D converter (with 44.1/48 kHz sample rate) and a built-in low-noise high-definition preamp. These, combined with its 133dB SPL rating, allow for optimal recording at any sound pressure level — it can capture everything from the subtle and nuanced dynamics of the human voice to the full-on bombast of an amplified electric guitar, and everything in between.


A full suite of controls

To ensure you'll always record at your best, iRig Mic Studio comes with a full set of flexible controls: It has a gain control knob and a multi color LED level indicator. It also includes a headphone output with its own level control for onboard monitoring directly from iRig Mic Studio itself. And, for better positioning while recording, iRig Mic Studio comes with a sturdy and portable tabletop tripod stand.

All this is to say that iRig Mic Studio is equipped with everything you need to capture the highest quality sound no matter whether you're at home in the studio or recording while on the go.


It’s all about the connections

iRig Mic Studio is compatible with all your favorite mobile and desktop platforms. It comes with a female micro-USB port and an assortment of cables: Micro-USB to Lightning for iPhone, iPad and iPod touch; micro-USB to micro-USB OTG for Android (requires either an Android 5 or Samsung Professional Audio device); and micro-USB to USB for Mac and PC. A micro-USB to 30-pin cable is available separately for older iPhone, iPad and iPod touch models.



Record with the power of apps

For immediate recording, iRig Mic Studio comes equipped with a powerful suite of vocal apps that match its cross-platform compatibility. iPhone, iPad and iPod touch users will be able to enjoy VocaLive, a powerful effects processor and multi-track recording app that features a selection of 12 professional real-time vocal effects. EZ Voice for iPhone, iPad and iPod touch and EZ Voice for Android are streamlined and easy-to-use sing-along apps that make it easy for vocalists to practice with any song in their music library. iRig Recorder for iPhone, iPad and iPod touch and iRig Recorder for Android are straightforward apps for field recording, podcasting, note taking and more.

This does sound and look intersting but for some reason it is not accepting any of my devices...
This could have to do with restrictions on country as some developers prefer to limit Beta testing so if you can not download it maybe wait until it released officially?

Play Store info:

Monophonic synthesizer application that delivers a wide variety of sounds, MIDI support, and a high quality synthesis engine.2 Alias-Free(Low noise), Stereo, Dynamic Waveform Generators (multiple synthesis techniques)
10 32-bit Wavetables
Custom designed, unique, waveforms.
FM & RM Synthesis via the modulation matrix.
Standard VA-Style Waveforms Saw, Pulse/Square(with PWM), Triangle, Sine
1 Low Pass Filter with 3 different modes.
Completely stereo signal path.
Tape-delay inspired stereo delay (can function as a flanger or chorus effect!)
Flexible Modulation Matrix
2 LFOs (Low Frequency Oscillators) 6 different waveforms with 2 built-in destination routes each. Tempo sync + retrigger along with an error control to add chaos.
4 Envelope Generators ~ ADSR
High quality sound engine. 32-bit floating point internal processing. Adjusts to individual device's optimal settings.
4 Slot Modulation Matrix
Basic MIDI support - Plug-and-play with an OTG cable. Supports pitch bend, mod wheel, velocity, after touch.
Improved latency that takes advantage of the latest Android improvements. Optimized for Kit Kat 4.4.2. See release note 1 below.
Page Based User Interface - Swipe left or right to navigate through the different parts of the synthesizer.
Keyboard designed to be easy to play and to be appropriately sized for most people's fingers.
Monophonic


Minimum System Requirements:
Android Version 4.4.2 "Kit-Kat" or later.
1 Ghz processor or better (multi-core recommended)
1 GB RAM
External speakers or headphones are recommended.


Demo Version Limitations:
Presets cannot be saved.

Release Notes:
Latency is ultimately dependent upon your hardware and version of Android. The demo version is provided so you can try it out on your particular device.
Android MIDI device support only works for MIDI controllers that require no additional or proprietary drivers. i.e. Generic MIDI Devices. Consult the Android documentation for more information.

Binaura made three cool applications since some time then they got into some other projects but I do hope that they develop some more cool stuff for Android again!
Ahh and they use Pure Data for making their apps and for a lot of their other projects which are very interesting.

Have mentioned this app before but here is another video and having not used it do not know how useful it would be but it looks like for some people it could be interesting...

Play Store description:

FEATURES:
Click on any video to play it.
Combine the sounds of all the videos to create amazing music videos.
Loop the video clips in a number of different ways.
Replace any videos with your recordings.
Choose the maximum length of your recordings.
Choose the amount of videos to show at once - between 1 and 25 videos can be played together.
Edit the playing time and volume of video clips.
Import existing videos from the library.
Add special effects to your recordings.


Check out CamJam Video's - Behance Project: http://on.be.net/14ldJHw

* Support for 24-bit WAV files
* New loop editing features
* Auto quantize during Jam
* Convert Jam session to a loop (for editing and reuse)

So anyone that works a lot with samples should definitively check this app out and specially now when it has added automation and effects into the mix.

Play Store info:
- Effects: Master Reverb, Delay, Highpass, Lowpass Filters
- Automation: Volume, Balance for each Slot Sample
- Shuffle Mode
- Improved Pattern Editors with Toolbars
- New Demo
- New SlotMix overlay while playing
- Better Tunable Percussion Notes
- Pads are now enlighted when playing
- sustained notes, sequenced slots
- and a lot of usability improvements

Here is a new demo song using the new effects and automation...

So just to mention that Audio Evolution Mobile is now one step closer to a full blown DAW with the possibility to automate effects plus that it also have the possibility to buy in-app a Autotune and harmonizer plug-in...
It is growing fast these last months!

Have not used it myself but here is what is said on the Play Store:
_______________________________________________________________________________________________________
Launch Buttons is a handy tool that gives you an additional interface to compose and perform your music with. Setting it up takes no longer than 3 minutes and off you go!
Works with Mac OS X and Windows XP/Vista/7/8/8.1.
Optimized for Ableton.To learn how to connect, visit http://bassapps.de/connect.html
If you run into any trouble connecting, please message me!

If you are teaching music, you could save loads of money providing a whole classroom with a functional MIDI controller running on Android devices instead of spending an extra thousands of dollars for hardware equipment.