Thanks for that. I think need a duet on there (aren't there a lot?) and can probably now curve your rows for you. See below
The gnomes of Wirral have been busy over the past week and I think I've cracked the concertina layout issue and have a unified token system that covers all
squeezeboxes. It's seen me abandon 'Good Ol' ASCII' and embrace UTF-8 character encoding. However www has been using this for well over 10 years and it is the de facto standard for web pages.
My testbed version uses UTF arrow character 'ꜛ,↑,ꜜ,' prefixes to specify 'nudges' of ¼-position, ½-position up and ¼-position down allowing the sort of 'curved' layouts common here (but of course, unknown to the melodeonista community)!
There's also progress on the knotty sound issue. Turned out that you can't simply use musical notes as they have to be voiced into octaves. Melodeon Explorer (apologies) doesn't know whether octaves lie left to right (anglo) or down to up (EC) and I think very few of us know how a bandoneón is played! Rather than make dubious assumptions, I've again used UTF prefixes: 'º,¹,²,³' to 'voice' the notes individually. Sounds hard work, but you only do it once and it is then 'right' Actually it's pretty quick - the octaves always lie in patterns
This technical change transferred the character encoding issue into its editor (UTF characters aren't keyboard typeable) But having crossed the Rubicon - all was well
ME's edit box converts eg ^2Ab to ꜛ²A♭ in a jiffy.
The final Good News is that I've allowed eg a simple A♭♭ and G♯♯ token to overrule the underlying 'music' model's view that these notes are the same thing. They still 'sound' the same, but display as A♭ and G♯ without any conversion. This avoids the need for any 'processor directives' - always a pain.
Sorted! We seem to have a common encoding for all squeezebox layouts as per 'mission'. I've laid it out on http://squeezebox.ch...l.net/notes.htm
There is also progress on sound, as per actually 'hearing it'
with sampled .ogg snippets plumbed in over 6 octaves. MSIA (as ever
) uses its own format, but sound 'sounds' on up to date
Firefox, and should also work on Chrome and Opera. You can try it on the notes page, but the main 'Explorer' presets are not yet 'voiced'. Sound has to remain 'experimental' as it needs HTML5 (which officially deploys in 2016)!
Thanks for your continuing input, I've learned a lot. Please don't rely on the main Explorer page for edit/builds for the next few days.
The sound changes and edit will most certainly have introduced bugs.
Is anyone going to Whittlesea?
Edited by chris ryall, 09 January 2013 - 04:41 AM.