Tag Archives: bugfix

MusicTrans price drop and Windows bug fix

Yes, MusicTrans price has been dropped, both Android and Desktop versions!!

As a musician I’ve enjoyed MusicTrans a lot, and I’m sure that is an amazing tool for anyone interested in playing music, so a few weeks ago I dropped the price for the Android version. I did it quietly to see what would happen, and the response has been great!

Considering that enthusiasm, from today the price for the Desktop version has been dropped too. Now you can get MusicTrans Android or Desktop for just USD$4.99

UPDATE: This offer ended in 2015

And there is more news! The installers for Mac OS X and Windows have been improved, and you don’t need to install Java, the installer includes everything you need to run MusicTrans.

(The Ubuntu/Debian installer don’t need that, the package system will install everything for you, only the generic Linux version will need a manual installation of Java.)

Last but not least, some people running MusicTrans for Windows had a strange bug that made it freeze when trying to open a song.  That bug has been fixed in this new version (1.0.7).

Remember that you always can contact me at fcatrin gmail dot com if you need help or want to give some feedback to improve MusicTrans.

MusicTrans 1.0.5 adds “recent files” and and small fixes

Recent Files on MusicTrans

MusicTrans now has an easy way to open your most used songs. When you press the “open” icon you will see a list of recent songs, where you can choose any of them with just one click. No more need to remember where and what were your songs, even if you have deleted the original file. This feature is available ONLY for registered users.

This new version also includes a fix for some Windows users that reported a bit of flickering when using the slider controls like the tempo control or the equalizer bands.


MusicTrans 1.0.4 adds Preamp and bug fixes for Windows

MusicTrans 1.0.4A new version of MusicTrans for Desktop has been released.

Most notably in this version is a Preamp control.  Sometimes when you filter out some frequencies with the equalizer, the overall signal level goes down. Of course you can move up all the sliders to recover some power but now you only have to move the Preamp level up.  There is also a level indicator to give you a hint of how much you can push up before getting distortion.

This version also includes some fixes for the Windows platform.  Some users reported that the note analyzer was flickering, and sometimes the wave view too.  Now the flicker should have gone on those views. There is still some issues on the sliders but they will be fixed in the next version.




Crash bug fix on devices with low memory

If you tried the MusicTrans demo and it crashed at launch this is important news for you.

With the help from some users, we found that the memory allocated by MusicTrans at launch was too much for many devices (1GB of RAM). A new version that fixes this problem has been released a few minutes ago, so if MusicTrans just crashed on your device this new version may fix that.

We also fixed a problem with the license checking routine.  At first launch the license was handled as expected, but once the license data was saved to avoid excessive network traffic, the license check failed.  So some valid users were restricted to 2 minutes of use, like if they were using the demo version. This is also been fixed now.

Now some technical details for those interested…

The processors found on most Android devices are very limited in power in comparison with the processors found in desktop machines.  The digital signal processing code in MusicTrans is very intensive, and it has been heavily optimized to run on this small processors.  One of the techniques used to run this code faster is to pre-calculate as much data as possible, but this technique has the drawback of requiring more memory to store the results of this calculation.

In the previous version (the one that most people have tried), the size of the pre-calculated data was “a little” relaxed, and unexpectedly they added up to 1GB of RAM.  This situation was undetected on my test devices but some users reported the crash, and looking at the code traces I found that Android couldn’t load the digital signal processing code because of the amount of RAM required.

I dropped some pre-calculated data on any code path where it didn’t made a major change, and then I ran some test to see exactly how much data where required to hold some parts where the real limits weren’t clear enough.

After those changes, MusicTrans memory use dropped from 1GB to about 40MB of RAM with just a minor performance impact, so it shouldn’t crash on any devices because of memory use now.

BTW: Did you notice that the APK is only 700KB?  Think that there are simple apps like “flashlights” with APK of 6MB or more!!