Let’s finish off 2016 in generative fashion … An interview with Tim from Intermorphic

I have known Intermorphic and what they do for a very long time now. In fact, almost as long as I’ve been running PalmSounds. I’ve known them in a variety of iterations, there’s more about that later, but what’s really interesting is the journey they’ve come through and where they’re going.

Tim and I actually started this interview quite a long time ago, so it’s good to finally get it out. Especially as I think we’re going to be seeing a lot more about generative music in the coming weeks.

With that, let’s get going …

PalmSounds: Tim, you’ve been involved in Generative music for just over 25 years now and that’s an amazing achievement in itself. Can we start off by talking about what it was that started you off on that journey? Can you tell us what made you want to be involved in generative, what sparked your imagination?

TC: On my 14th birthday my parents gave me a classical guitar and I’ve played and created music ever since – that guitar was what kick started my love affair with music making that has lasted to this day.  My personal site (http://colartz.com) is now home to some of my musical creations.

Looking back, I guess the original inspiration for our approach to generative music engines came from the classic Foundation series by Isaac Asimov, which I probably started to read some time in the 70s. In it, Asimov introduced the Visi-Sonor, a device which could be manipulated by a skilled operator to create amazing multimedia entertainments combining both music and visuals. Today I imagine it might be called a kind of hyper-instrument. I thought no more of it until 1986 when, for some reason, I started deliberating about a sphere-like composition and performance instrument and madly figured it would be fun to try to create one. The slight problem was that I had no idea where to start and I certainly knew I could not do it on my own!

In 1989 I found the courage to take myself off to business school where I hoped I would learn how to start and grow a business and maybe meet some like minded people, too. It turned out it was exactly the right thing to do and SSEYO (https://intermorphic.com/sseyo) was born soon after. Lot’s of ideas were swirling around at that time and it is a bit tricky to unpick what happened when and how we ended up where we have.

One of the ideas came from noticing that a ticking clock seemed to provide a focus for the mind, somehow helping it to filter out extraneous sound and foster the establishment of calm and stillness. In this situation the brain is obviously doing an incredible amount of real-time audio processing work, totally automatically. This led me to start thinking of a listener’s brain as the ultimate creative instrument. The brain is, after all, what takes music input and interprets it in the context of a unique set of historical and emotional occurrences to create an experience that is unique for every person.

Another idea came through wondering if a chance-based engine with sufficient boundaries and rules might be able to assemble something music-like and interesting enough to engage the brain and stimulate it to fill in the gaps and make interesting and serendipitous connections. I imagined a set of ball-bearings traveling down a chute, in a way akin to a Bagatelle or Pachinko game. Each time the ball bearings would make their journey, they would combine to travel a different set of paths, bouncing off each other as they would go, but the available paths would be constrained by the internal physical design and boundaries of the game – an envelope of musical possibilities as it were.

At some point we did consider algorithmic composition, and even tried neural nets , etc., but we slowly realised that style-based music systems were not what we wanted to build – we would leave that to others to explore. The path that just felt right for us was in designing engines that used stochastic/aleatoric techniques to compose within some overall boundaries and then letting the listeners brain do the rest. We did not yet understand the pivotal role that the sounds themselves would have to play, but that would come later.

We had to start somewhere, so we kicked off with a concept we called an “Environmental Management System”. It was meant to be a device that would act as a kind of sonic buffer to a world of external sensory “overload”, working along the lines of what was discussed above. However, to get anything working we needed a suitable music engine! After a few initial explorations it did not take long to realise the real key to any musical device or instrument would be in the software smarts that powered it, so we started in earnest developing what was to become the SSEYO Koan Music Engine, releasing the first beta in 1992. And, of course, that was the start of the journey we have been on since.

PalmSounds: What was the reaction like to the SSEYO Koan music engine, and how did you deal with what users wanted?

TC: Over the years we have been very lucky to have worked with many really helpful beta testers, early adopters and musicians, including the genius Brian Eno whose “Generative Music 1” with SSEYO Koan software (https://intermorphic.com/sseyo/koan/generativemusic1) definitely upped our profile and helped popularise the SSEYO Koan system. We love communicating with our users, and, as there are only two of us again, we reserve an especial place in our hearts for those that can also be constructively critical :).

The reaction back in 1992, when we got out the first betas of SSEYO Koan (https://intermorpihc.com/sseyo/koan), was very encouraging so I guess we decided it was worth continuing. I seem to recall that people felt that the output could be interesting and felt organic; this was promising and indicated we might be doing something right.

We then just got on and did the things we wanted to do, listening to feedback along the way. Early development of a system like Koan was quite open ended in scope so we were always short of time (still so very true today). We experimented with all sorts of ideas, including music rules which changed or became active according to the time of day. Our approach just meant we tended to hone in on feedback concerning bugs and features that just didn’t work quite right or that could work better. Of course, over time we picked up a number of helpful suggestions concerning potential improvements to what we were doing, but as it is now so long ago I just cannot recall specifics.

We have always had a long, long list of related things *we* want/plan to do (time willing) and a pretty clear idea of where we want to go, so we don’t tend to look around much at what others are doing. This is no doubt a failing of ours, but, as people are now finding with Facebook, it is easy to get envious of what others are doing – we would rather just get on with what we want to do. That doesn’t mean we do not read, listen to and sometimes take on board feedback or keep a loose eye on the market and market developments; it just means that reported “crashers” and “bugs” tend to get the most attention.

By way of analogy, we tend to feel like we are in a small boat on a big sea. For us to have any chance at all of surviving the storms and the swell until reaching the next port we have to make sure we are taking account of prevailing conditions or those we can see coming. That means we are always re-checking the horizon and adjusting our jib. This in turn affects the order of things on the long list of things to do. You can imagine, therefore, that getting new stuff on to that list can be quite tricky, which is why we often find it easier to deal with feedback that matches up with something already on it!

PalmSounds: After SSEYO was acquired by the Tao Group things didn’t go too well, what happened and how did that impact your work and how you felt about it.

TC: I tend to believe that there are always 2 sides to every story, that if you are trying to make the future then time is too short to dwell unduly on the past, and that no thing worth doing is ever going to be easy. It is the nature of life that it exists only now, so rather than looking back I prefer instead to try to find the good in any situation and then move forward from there. It is a positive approach because to build anything you need to stay positive.

In many ways things did actually go well for us at Tao Group and we got to work with many really nice, very clever people.

We were able to keep a smart audio team together and undertake the challenge of developing the Tao intent Sound System (iSS). The iSS was a collection of audio technologies that was deployed as required in the Tao intent software platform, a true multi-threaded operating system and virtual machine primarily for mobile devices. Tao Group had a stellar set of investors and Tao intent was licenced to a number of big name manufacturers.

It was through what we did on the iSS and our employment at Tao Group that we got to experience the mobile and device world from the inside out. This was to our long term benefit as we got to understand more about the mobile ecosystem, its workings and relationships. Plus, we made some good friends and connections, too!

Whilst at Tao we also worked on two “products” that were released. The first was the Advanced Polyphonic Ringtone Engine, and the second was SSEYO miniMIXA. Launched in 2004, SSEYO miniMIXA was, for its time, a very advanced mobile music mixer app that ran on Symbian, Windows Mobile and intent (and wherever that could be deployed).

Although for financial reasons it was a dreadful day for all involved when Tao Group folded in 2007, it also finally set us free to start over with Intermorphic: a door was opened that let us set out once again on our generative journey, but from a new vantage point.

In 2008 Intermorphic managed to secure the rights to the iSS, SSEYO miniMIXA and all past SSEYO IP. Much of what we did at Tao is now in the Intermorphic Sound System. The ISS has been put to good use and underpins all our current apps, including Mixtikl (https://intermorphic.com/mixtikl) which we evolved from SSEYO miniMIXA.

So, just as without the SSEYO years there would not have been the Tao years, without the Tao years there would not have been the Intermorphic years – that is, in terms of how they have turned out, of course. There would still have been Intermorphic years, but just different years with different generative apps.

Of course, running a small, niche software business is always going to be hard work and require heaps of passion and bags of luck. We are truly grateful to and for the amazing people we have worked with along the way and appreciate how fortunate we are to still be standing. Onwards!

PalmSounds: So, that brings us up to the present day, or rather, up to the Intermorphic years. How have things been different for you now that you make the decisions on direction and new products? Has it been a creative release, or, do you think that being part of a commercial environment with all its pressures actually helps the creative choices you make?

TC: When we first started SSEYO we were like a young new band; we had total creative control over what we did and bags of energy and time. We were in a niche area and as SSEYO developed we had to find a way to feed it – which at the time meant Venture Capital. So, when we raised Venture Capital (VC) there rightly came with it some big, new and important VC-related factors to address. Then, after SSEYO was acquired by another VC-backed company there were yet more VC-related factors and we were then of course working for someone else with their own requirements and direction.

When we took the decision to start Intermorphic it was to regain creative control over “something” and we knew we would, as before, have to live on our wits and organic growth. It was different with Intermorphic, though, as we were older, with families, and had less time and more pressures. As well as that there were some tight resource constraints. All of these continue to this day to bring their own challenges.

Creative endeavour, if it is to be sustained, doesn’t exist in a vacuum: it has to be fed and supported. A lot of our creative effort at Intermorphic, as it did at SSEYO, goes into trying to figure out how to survive. There is always a lot of tyre kicking and iterative thinking around what we could and even should do in the context of our audience and our resources, which have always been very constrained. In the light of that and in the early days of Intermorphic, the first app we built was a cut-up text generator desktop app called “Liptikl” (https://intermorphic.com/liptikl), a useful non-music tool which was spurred by me having trouble coming up with new word associations/lyrics for my songs. Once that was out of the way we decided we were ready to start work on a clean room build of a generative music engine we called the Noatikl Music Engine (NME) (https://intermorphic.com/nme/3/guide), together with a generative music composer desktop app and interface to it that we called “Noatikl” (https://intermorphic.com/noatikl).

Those early days for Intermorphic feel like a long time ago; today there is way more competition and ever more user expectation as the app market is now global and there are also many more business models to consider and factors to deal with – all generally set against diminishing returns. It is a perfect storm in many ways, and whilst things are whirling around us it can often seem if we are moving very slowly. But, strangely, this situation is also a stimulus, in that it forces us to focus on what we do best, what our USPs are and what it is we can do that can bring real value to our customers and fans.

So, it is bit of a dichotomy really. On one hand we have more creative freedom (no one now tells us what to do) but on the other we have less creative freedom (surviving in the current app marketplace). It requires a good deal of effort to counter inertia and to keep innovating, but we know that nothing stands still and it is in our DNA have to innovate, whether that is through new features for existing apps or new apps altogether. In many ways, the biggest creative challenge of all is to discover and agree on interesting green pastures to farm and explore and that fit our current resource profile. In our new developments we try to keep a sense of our history, identity, domain, audience and competitive environment and look to find creative ways to combine our existing code base with new ideas, novel approaches and simple interfaces. We are excited therefore about the potential for our Wotja Reflective Music System (https://intermorphic.com/wotja), first released in 2014, which ticks all the boxes for us, and it is an app that we want to do much more with. More on that in a bit.

PalmSounds: People find generative music difficult to get to grips with, why do you think that is, and where do you see tool makers like yourselves going in the future to help this, and what is it about generative that you think people struggle with?

TC: I think to get some perspective on this it helps to consider Computer Generated Music (CGM) in general. By this I mean music that a computer generates, composes or mixes itself, whether by rules, chance, algorithms, AI or whatever. It could be assembled from any size of building block, from a sample to a loop to a recording whether made by human, animal, nature or computer. Unless a human has a clear hand in controlling, directing  and imbuing meaning to it, to my way of thinking any of the foregoing is Computer Generated Music. I am sure it is not a perfect description, but it will suffice for now and in the context of my thinking outlined here.

Over the years I have enjoyed hearing CGM, principally the Generative Music that our systems have generated, and I have often pondered on the nature of it. My thoughts change and have kept changing, and I am not sure there are any hard and fast answers as it depends on the person and a number of factors. I think some of the (by no means exclusive) factors to consider relate to how a creator’s or listener’s tastes or needs vary for the following:  1) Compositional control (e.g. what control do I need to have over what happens?); 2) Intrinsic meaning (e.g. do I need it to have any emotional, personal meaning?); 3) Context (e.g. do I need the music somehow fit the context of where/when/how it is experienced?); 4) Musical style & structure (e.g. do I need it to have a feeling of style or for it to have a directional vector?); 5) Foreground/Background music (e.g. do I want to actively listen to it); 6) Interactivity (e.g. do I need to be created live, in the moment; as in “inmo” (https://intermorphic.com/inmo) ?); 7) Sounds used (e.g. do I want natural or synthetic sounds, created live or sampled?); 8) Ideas (e.g. am I wanting to use it to create ideas for me to later use?); 9) Ease of creation (e.g. how much time do I need to set aside to make it; how hard is it to do well?); 10) Sharing (e.g. as a creator, do I want to share what I have made?); 11) Turing test (e.g. can you be certain it was/was not created by computer?) etc.

Every creator/listener will have different needs and taste profiles for all of the above, and these are likely to change according to mood, context, day, season , etc. So, as you can imagine, asking why “people” find generative music difficult to get to grips with is a difficult one to answer; the answer is a very personal.

As I said in a previous answer, we are primarily concerned with music that is created stochastically/aleatorically. It might be easy to think that that this kind of music can have little emotional impact on a listener. However, I am reminded of a time back I think in 1996 when I was in the zone listening to Timothy Didymus’ “Float” (https://www.intermorphic.com/sseyo/koan/float  – Timothy is an amazing generative musician who we still have the honour of working with). I think I was listening to “Midheaven” at the time (https://www.intermorphic.com/sseyo/koan/float/#float-audio) and I distinctly recall entering some kind of quasi state where I felt I could “taste” the music; it was a remarkable and moving experience I think related to the subtle changes in the music. As far as I know it was something peculiar to me and only happened the once, and I have not experienced it with other non-generative music either, but it emphasised to me the personal impact that CGM could have in the right context.

In the context of the music our engines make I have been pondering quite a bit about “Intrinsic meaning”. It seems to me that everyone has a “music player“ in their head. However, experiences and appreciation can be different as each person’s “music player” has associations specially keyed with their age, culture, demographic, personal/shared memories (e.g. concert) etc. And, even then, to really appreciate music, repeated listenings are often required. I love playing my guitar and writing music and, at least to me being a creator and songwriter, there is a fair amount of meaning in what I make – my music is distilled from my thoughts and emotions and is played with passion. However, if I share a recording of my music for someone to listen to, then what meaning can they, as a listener, extract from my recording (listening to it at a distance as it were)? They do not have my memories or context to unlock or quickly interpret it, to hear it as I hear it. I find it interesting to then consider CGM in this kind of sharing context, and it raises all kinds of questions related to meaning.

One other factor that plays a part in all this deliberation is that over the years we came to understand that generative music played against an image seemed to elicit a deeper reflection on the image, unlocking thoughts and memories. As a result, way back in 2010 we had decided to run with the term “Reflective Music” as a descriptor for the effect that the output of our generative music system could engender, and secured the reflectivemusic.com domain. In hindsight it was a good move, as the descriptor was to become even more apt…

So, trying to make sense of it all, I stood right back and got to thinking about text. Everyone has both a text player and writer in their head (language aside) so people can both easily and quickly create it and assimilate/understand it, it. Text has meaning and a reader’s imagination puts flesh on the bones; in a musical analogy it is a bit like a visual MIDI score played through different MIDI synths. Unlike music, though, text it is not particularly temporal and you can also quickly change it or respond to it. We figured it might be fun to play around with a kind of music messaging where a creator’s text could be used convey any meaning required and the text itself could be used by our engines, as a seed, to generate melodies / music as an accompaniment to it. This is the general idea we are currently exploring with the Wotja Reflective Music System (https://wotja.com).It quickly became clear that “Reflective Music” was the perfect descriptor because the meaning of the text can be reflected upon and the generated melody is, in turn, a reflection of the text.

PalmSounds: Can you talk about how your products have evolved in the time you’ve worked with generative music?

TC: We started out by building content-open and content-extendable creativity tools that let others make and record things of their own, to use however or wherever they wish. Even after all this time we see no reason to change our direction and, besides, we really enjoy seeing and hearing what other people can create with our tools and apps!

In the intervening years many, many external factors have changed, none more important than the emerging importance and capability of mobile devices. We first started work in mobile in 1998, in “Mobile Music Making” as it were, so mobile thinking has been in our DNA for many, many years.

However, we really started thinking in earnest about “mobile first” back in the noughties, sometime before I started claiming in 2004 (with good reason, and prior to the release of SSEYO miniMIXA), that “the mobile phone is the next electric guitar”.

There have been lots of stops, starts and dead ends along the way for us, and it took us a long time to get there, but we now think mobile first for everything and have done so for some time now – be that apps, business models, websites or anything else. They all have to work and work well on mobile; everything then scales up from there.

Part of the issue with mobile is that it is mobile – screen size, performance, input mechanisms, app inter-operatibility, UIs, usability, complexity, operating system, sharing, social, marketplace, business models etc. all brings constraints and opportunities. All these have to feed into our app planning, design and thinking as we evolve our apps.

One of the big things we learnt very early on, and alluded to earlier, was that it was all very well having a powerful generative music engine, such as our Noatikl Music Engine (NME), but if you want someone else to hear and in the same way experience the generative music you have made, then the music has to be *portable*, i.e. there has to be a player for any desired listening device. That means you generally either need to A) restrict your compositions to rely on the use of audio samples (these are big and have issues if you want to share them so are generally inbuilt), maybe with some pitch shifting or post-FX; or B) you need to build or licence and include some kind of good quality, flexible, MIDI-like modular synth sound engine that allows real-time polyphonic sound generation with sound shaping; or C) some combination of both of those. We chose the latter route, C), so over the years we have spent a good deal of time evolving our integral Partikl Sound Engine (PSE) (https://intermorphic.com/pse/3/guide). This is now a powerful and customisable modular/SF2 MIDI synth with live FX that is included in all our music apps and we recently updated it to allow stereo synth sound design. Other than trying as best we can to keep up with advances in sound generation, in so far as it is relevant to portable generative music of course, the main problem with something this flexible relates to the interfaces you choose to provide to it to allow complex sound design, especially on mobile, and how they can be accessible. This is an area we have made some progress in, but we still have a long way to go and are still mulling over exactly what to do next.

Aside from the ongoing development of our essential core technologies such as the NME and PSE, we have found it is the mobile factors that have shaped our thinking the most with respect to our products over the last few years. So, although we started out in 2007 with desktop versions of Noatikl and Liptikl we now have mobile versions of both of those. Mixtikl is the evolution of SSEYO miniMIXA and at the time of Mixtikl’s first release (2008) we built it with a scalable XML front end so the same UI would work on mobile (Pocket PC) and desktop (Windows and Mac), meaning it started out as a hybrid. Apps that came after that, such as Tiklbox Ambient Generative Music Player (https://intermorphic/tiklbox) and have been totally mobile-centric designs, using native controls where we can, and that we are looking to develop Desktop versions for as we’re adopting Swift where we can.

Business models really do have a major impact on what developers can do and how it is done, so we experimented with many different approaches trying to find the right balance for our offerings. After much trial and error over a few years we have now pretty well settled on a model the best allows us to move forwardsWe have built Wotja to be not only a creativity tool, but also a generative music publishing system in its own right in that totally custom Noatikl pieces can be imported into Wotja and saved or exported as wotjas and then played, for free, in Wotja.

It is not easy these days surviving as a niche app developer, what with VC money continuing to pump into apps resulting in market consolidations, a global app market with ever more noise, shifting customer expectations and everyone suffering increasing pressures on their time. However, we love doing what we do, we love our customers, fans and friends and, for those interested in the areas we work in, we expect to continue trying to innovate in our own niches and even to find a few new ones!

That’s the end of the interview that Tim and I worked through earlier in the year. To finish off this post Tim has added a few words about what’s happening now at Intermorphic.

A lot has happened at Intermorphic since we started this interview. We have some exciting new developments in the works and which are not far off now, hence this “end of year” addendum.

In the last year we focused hard on stability and released a number of related updates for Noatikl 3 and Mixtikl 7. We wanted to be in a good position for the long journey to our next major milestone in Reflective Music, namely Wotja 4. This has been a major undertaking for us as we are gradually consolidating the best of Noatikl 3, Mixtikl 7, Tiklbox 1 and Wotja 3 into one app, Wotja 4. We expect to release the first iOS version and macOS Safari App Extension in January 2017 followed by desktop versions sometime later in the year.

Wotja 4.0 is actually the start of a whole new journey for us, a new stage of evolution if you like, and there is a lot to be excited about. Being able to focus on just one reflective AND generative music app with full editing means we will be able to move it forward faster with improvements and extensions and it also means we are better able to evolve our music and sound engines. To that end the Noatikl Music Engine is evolving into the Intermorphic Music Engine (IME) and the Partikl Sound Engine is evolving into the Intermorphic Sound Engine (ISE). Both of these engines are at the heart of the new Wotja Reflective & Generative Music System. Of course we will also be extending the Intermorphic Text Engine, too, in due course.

Although we don’t feel it appropriate this close to release to pre-announce the details of Wotja 4 :), one thing we can say is that the IME in it will itself support multiple Text To Music (TTM) Pattern voices to allow the creation of richer reflective music tapestries that can sit on a gorgeous bed of generative music – with everything being deeply and totally customisable. TTM has been in Wotja since its first release, but prior to Wotja 4 it was not in the engine itself so only one was allowed in a wotja – no longer!

If you have read this far then many thanks for your interest in what we are doing and we hope that you might decide to get and try out Wotja 4.

Especial thanks to Ashley at Palmsounds who does more than anyone else we know – and we have no idea how he does it unless there are 10 of him.

Our season’s wishes to all! Intermorphic.

So that’s all for 2016! Have a lovely New Year and we’ll be back again in a day or so.

Wotja Pro 2017 – Generative Music & Cut-up Text 4.2 arrived

As a long time fan of Intermorphic’s work it’s nice to see the development of their apps into Wotja (pro and subscription). With version 4.2 they’ve brought in the functionality from Liptikl (an app I had a lot of fun with) directly into Wotja. This is pretty cool. Everything is now in one place and…

Brian Eno’s Bloom gets its 9th update since 2008

Which is not a lot of updates. When Bloom arrived back in 2008 it was a pretty amazing event. It was a little bit of a toy, but it was an app from Brian Eno, and that was pretty amazing on a mobile phone. Now of course he has a lot of different apps including,…

Wotja 4.0 brings the best of Mixtikl, Noatikl into one place

As a long time fan of Intermorphic’s work I’ve been waiting for this for a very long time. I didn’t get it initially, but when the guys at Intermorphic explained it to me I got there, and now it’s here. Here are all the details: Wotja is our chilled-out music app for creative relaxation &…


Something went wrong. Please refresh the page and/or try again.

From the beginning … PalmSounds on video, back in 2007: Two OS’s together?

“I had thought about doing this a while ago. This is a short video showing AxisPad (using sounds from SoundPad) being played through Pocket StompBox (a multi-effects processor) into a pair of portable speakers. Made me think of Dr Who soundtracks from the 70’s!”

Now I’m getting into the whole Windows Mobile thing and running StompBox on the Dell Axim.


From the beginning … PalmSounds on video, back in 2007: Emulation

Back then I was experimenting with emulation on mobile platforms. You couldn’t really do it on the Palm OS but Windows Mobile did the job quite well. I never really got anything finished with it though, it was never really robust enough, but fun to experiment with.

Moments in Mobile Music: 2 – Griff and Windows Mobile

Griff was (is) an app (not that we called them apps in those days) that was a complete revelation to me. Up to that point I’d only used Palm OS stuff (see previous post on miniMusic) and hadn’t ventured into the world of Windows Mobile (as it was called in those days). But Griff was a big enough excuse to go there. When I found out about Griff and what it could do I decided to get myself a Windows Mobile device second hand and try Griff out. I got an old Jornada 568 which was up to the task and I bought Griff.

Compared to now Griff was an expensive buy. To get the base app and all of the then available plug ins was going to cost you over $100 so I did it in bits, but it was worth every penny. Griff worked as a host to a series of plug ins not dissimilar to how AU is starting to work for iOS. The people behind Griff made a bunch of their own but some were 3rd party as well. It had an excellent range of synths and effects but it’s real strength was the huge amount of automation that was possible for every parameter. Griff was an incredible feat of software engineering in its day and I think it is still very impressive now.

Here’s a taste of it from the tutorial video:

Back in 2007 I wrote this review of Griff, and I think it’s still a good introduction to the app. For me it was a turning point in my own journey in mobile music, and, very occasionally I still go back to it. Of course, writing this now makes me think I should do the same again and revisit Griff and some of the work I never finished with it. I still think it’s amazing.

If you’re interested in finding out more about Griff and reading a little more of my ramblings on the subject then you might want to first read the review mentioned above. I also wrote about the mda filter and leslie, PocketKick, a drum synth, the pSyn synth, PocketHat, which probably needs no explanation, Goldfish, which was a great bass synth and PocketSnare, which again needs little explaining. There’s also a taster post from 2014 where I featured Griff in my 24 apps for Christmas and that has links that’ll be useful if you wanted to get going with Griff for yourself.

If you’re interested in everything to do with Griff then click here which will take you to a full search of the site for everything Griff based.

The more I think about it the more I feel I should dust off my old Dell Axim and get Griff going once more. If you were a Griff user and decide to do the same then I’d love to hear from you!

The History of Sunvox in screen shots

I’m sure most of you will know SunVox and be aware of just how awesome it is and has become. But I expect that few people will be aware of how long it has been around and how it evolved. I actually remember using SunVox on an old Palm OS Treo 650. It was awesome even then. Just look at how far it has come since it started.

But this begs a few questions. Just how is it that such a complex piece of software has been made so widely cross-platform and grown so much with the vision of just one person. Ok, one really amazing person, but there is only one NightRadio,

Well here you can find all of the screen shots of SunVox, the complete history, and long may it continue to get better and better.

My 24 apps of Christmas: 18 – Griff (for Windows Mobile)

So it’s time to go a little retro with my 24 apps of Christmas this year. I know that lots of people might think it a little strange, but actually I think it makes perfect sense. When you look at Griff and what it can do you’ll start to wonder how it was ever created for Windows Mobile. It was, and still is an amazing piece of software, complete with it’s own plug in architecture with full automation.

And of course now, Griff, the mobile music studio for Windows mobile, is free, as in beer.

So, if you have an old Windows Mobile device knocking around you should really go and grab Griff as it and all it’s plug ins are now free. Well, to be fair, the ones that the Griff people made are, but the third party ones are pretty much vanished now. It’s a shame, but these things happen.

Of course, if you don’t have an Windows Mobile device then the whole thing is a bit academic really. However, they can be picked up very cheaply these days, and I can recommend a Dell Axim X51 which has always done really well for me. Dell Axim at eBay

If you want to know more about Griff you should check out the other posts I’ve written about it over time. You can find them all here. There’s plenty of stuff there, from reviews to video etc.

So Griff is my number 18. One of those apps I’ll keep coming back to and experimenting with. One of the apps that helped me on this journey into the world of mobile music, and a little bit of history that’s worth knowing about.

Phoenix Studio for Windows Mobile and for Android

I haven’t actually tried out the Android version of Phoenix Studio as yet, but I can still find my way around the Windows Mobile version, and in theory they shouldn’t be too different.

I had thought it was coming to iOS as well though.

Phoenix Studio comes to Android

Well I didn’t see that coming! Phoenix Studio returns from the long lost land of Windows Mobile and is now with us once again on Android, and apparently coming to iOS too. What next I wonder? Griff coming back? Bhajis Loops even! No probably not.

Even so, it’s great to see an app that’s been around so long come back again, and a huge thank you to Musical Android for posting this.

Retro VU meters is where it’s at

And more roots returning …