VividTracker v1.1 is live on App Store

Version 1.1 is now live on App Store. It comes with two new features: Audiobus 2 support and rudiment Bluetooth keyboard support. There’s no support for keyboard shortcuts like in Protracker yet, just very simple support for playing notes on the keyboard, but I’m working on implementing shortcuts to get as close as possible to Protracker. This is a good start anyway, and I’m looking forward to hear your comments about it. I will now get started on v1.2, which will contain more keyboard support.

read more

VividTracker and iOS 8

VividTracker v1.1 is still waiting for review to be released on App Store. It will hopefully be released within the next couple of days. However, iOS 8 will be released today so if you update to iOS 8 you will notice that Audiobus no longer works with VividTracker v1.0. This is because VividTracker v1.0 was built with Audiobus 1.x, and this version of Audiobus is not compatible with iOS 8. You will still be able to use VividTracker, but Audiobus will be disabled. This problem has been fixed with v1.1, so the problem will go away as soon as Apple has approved the new version.

read more

VividTracker v1.1 submitted to App Store

I have finally submitted v1.1 to App Store. It includes two things: – Audiobus 2 support. This version of Audiobus is required for iOS 8, so I had to hurry up with submitting a new version of VividTracker to Apple. – Rudiment Bluetooth keyboard support. You can now connect a Bluetooth keyboard and use it to play notes in the same way as you would do in Protracker. It does not yet include all the nice features that you have in Protracker, but this is a good start and I will continue to work on this. For now, you can use they qwerty-keys to play notes and the cursor keys to move around with the cursor, just like in Protracker. The return key works as the STEP button in the user interface, i.e. you can play one row at a time by pressing the return button. One limitation is that you have to press e.g. the down arrow key multiple times to move more than one row, i.e. you cannot just hold it down and let the cursor move automatically. I have an idea how to get around this problem for the next version, but it takes a little bit of time to implement and I want this version out now. Another limitation is that VividTracker only supports English layout, but you can easily switch between different layouts in iOS so I don’t see this as a major issue. In Protracker, you cannot play higher notes than B-3, which corresponds to key u. However, the keys i  9 0 o etc maps to C-4 and onwards, which in VividTracker allows you to play and change to another sample. This means the key i will be the same as “play sample #1”, 9 will be “play sample #2”, etc. This is a really neat feature for creating a drum pattern. Protracker has many nice shortcuts that I want to implement, but I don’t know if I will be able to implement everything exactly the same way. For instance, I have not yet seen that it’s possible to read the F-keys on the keyboard in iOS. Protracker uses the F-keys for things like cut/copy/paste and to move to different pattern positions. For instance, F8 in Protracker allows you to jump directly to position 32. But I will have some sort of workaround, for instance that you instead of pressing F1-F10 will have to press SHIFT-1 to SHIFT-0 or something similar. However, that would then exclude features like storing pattern positions on selected F-keys, because that is done with shift+F6-F10 in Protracker. Anyway, this is a good start, and a BT keyboard does indeed make the workflow a lot simpler. The next version will follow this version soon after it has been...

read more

Bluetooth keyboard again

I got quite far with integrating bluetooth keyboard support today. Now I can press the keys qwerty to play the notes C-3 to A-4. The only problem is that it will be really difficult to support different keyboard layouts for different countries. Take for instance the difference between an English keyboard and a German keyboard. If you press z on an English keyboard, you are suppose to get the note C-2. However, on a German keyboard, you expect to get the note A-4, because z and y are swapped on a German keyboard. There are also differences between Nordic keyboards and an English keyboard. Unfortunately, I have not found a way to actually read the location of a key, just its character. The only workaround I have found so far is to have two keyboards in your settings (e.g. German and English), then switch to English keyboard when using VividTracker. Fortunately, this is easily done by holding down command and space to get up a menu where you can shift between the two languages by pressing space while you still hold the command button. However, it has to be done somewhere where you can type. In VividTracker, you will be able to do it when you are for instance renaming a mod. You can also do it in e.g. the Notes app. I hope you find these limitations to be OK. Now I will carry on with implementing all...

read more