Tablatures 1.5

A new release of Tablatures is available.

The most important addition in this release is a basic and experimental* support for GuitarPro 3-5 files (*.gp3, *.gp4, *.gp5). GP tablatures can be read, but they will be converted to PowerTab when saved, keeping only the first two scores since that is PTB’s limit.

* this means that some files may not work. Feel free to report any problem you find.

A word of advice

When using the contact form to ask a question, please make sure that:

  1. the email you enter is correct
  2. your mailbox can accept new messages

Otherwise it’s quite hard to give you an answer, no matter how hard we try… 😉

Someone from Taiwan is probably waiting for an answer since the past Tuesday because his/her mailbox is full and the reply can’t be delivered (I’ve tried 3 times already): if you’re reading this, please make some room in your mailbox and contact us again.

Tablatures 1.4

Tablatures 1.4 is now available.

This release contains the same fixes applied to TabView 1.18, plus some options that have been requested:

  • Fixed a print problem that happened on Leopard when the print dialog was showing the page thumbnail.
  • MIDI export created unreadable files on several OS X versions due to a bug in a system function. A different way to perform the same operation has been implemented in order to work around the problem.
  • Added an option to choose the initial score (guitar or bass) that will be shown when loading a tab or creating a new document.
  • Added an option to automatically make time and key signatures visible when creating new systems.
  • Added an option to display bar numbers at every bar line.

TabView 1.18

TabView 1.18 has been released.

This version axes a couple of bugs:

  • Fixed a print problem that happened on Leopard when the print dialog was showing the page thumbnail.
  • MIDI export created unreadable files on several OS X versions due to a bug in a system function*. A different way to perform the same operation has been implemented in order to work around the problem.

*namely MusicSequenceSaveSMFData(). I do hope they’ll fix it for good one day…