[Harp-L] Tabs & Software
- To: Harp-L@xxxxxxxxxx
- Subject: [Harp-L] Tabs & Software
- From: Tino Heth <bluenotes@xxxxxxx>
- Date: Sun, 17 Jan 2010 10:46:26 +0100
- Cc:
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; t=1263721587; l=1456; s=domk; d=t-no.de; h=Mime-Version:To:Date:Subject:Content-Transfer-Encoding:Content-Type: From:X-RZG-CLASS-ID:X-RZG-AUTH; bh=S1N9RoW2MXe3jcqkdSiT0wRrp38=; b=MDUu35bKeBUk/FObt4h6Ktwhn2mkNeGKvXRFZtxLsQyN/Xx+K5+1Lcw2B3c94h0lAbt dbC2x7FRC21fGb6E5vNrG1fEKgo+nVLDNa8BsVg/qAYURea1b9qEgh7daI9MrvlvM/nmk Bh9R1rkcohddkIcVTN1mcwA1S4tnFxzT/Q4=
Hello everybody!
I'm currently working on a little tab database for the iPhone.
I don't want to do much advertising here, so if someone wants to know more,
take a look at http://bluenotes.t-no.de/index.html.en
The reason for this post is that I want to get some feedback about useful features
and the preferences of other players.
One important question for me is how to display tabs, as there seems to be no real
standard:
I know a system using arrows (which is hard to read, and even harder to typeset),
and then there are many variants looking like "4 4 -4 4" or "+4 +4 4 +4".
The problem with the second system is that there is no natural way of denoting
bends or overblows, so I'd like to hear about established ways to indicate the use
of such techniques.
I guess textual representation of notes ("C C C# C") are not very attractive for most
of you - but, of course, there is still the graphical, staff-based approach... just tell
what you prefer.
There are plenty of other things I'm thinking of - but most topics might be to special for
a discusion on the whole list, so feel free to contact me directly if you have some comments:
- lyrics (line-based vs. note-based)
- build-in synthesizer
- links to audio files in iTunes
- rating of existing file formats (MIDI, ABC, MusicXML)
- importance of editing/creation-capabilities and ways how to handle those
- ...
Greetings,
Tino
This archive was generated by a fusion of
Pipermail 0.09 (Mailman edition) and
MHonArc 2.6.8.