Yahoo Tuning Groups Ultimate Backup tuning .tun file format

I know OPENMPT AKA modplug tracker uses it. Otherwise, I have not seen it anywhere else.

--- On Mon, 12/15/08, Aaron Andrew Hunt <aaronhunt@h-pi.com> wrote:
From: Aaron Andrew Hunt <aaronhunt@...>
Subject: [tuning] .tun file format
To: "TL" <tuning@yahoogroups.com>
Date: Monday, December 15, 2008, 2:35 PM

I am currently adding .tun file format exporting support to my

software. I have looked around for any information about the origin

or authorship of this file format, but have found nothing. Can anyone

tell me where this format came from, who came up with it, what other

software uses it, etc.?

Thanks!

Aaron

=====

Aaron Hunt

H-Pi Instruments

Please note that I choose not to be involved in discussions of things

H-Pi related outside of the H-Pi forums,

<http://launch. groups.yahoo. com/group/ tuning/message/ 74905>

and I cordially invite everyone who is interested to please join and

participate.

Forum: <http://www.h- pi.com/phpBB2/>

Blog: <http://www.h- pi.com/wordpress />

🔗Aaron Andrew Hunt <aaronhunt@...>

OK, thanks Michael. Anyone else have any info on .tun?

Thanks,
Aaron

--- In tuning@yahoogroups.com, Michael Sheiman <djtrancendance@...> wrote:
>
> I know OPENMPT AKA modplug tracker uses it. Otherwise, I have not seen it anywhere
else.
>
> --- On Mon, 12/15/08, Aaron Andrew Hunt <aaronhunt@...> wrote:
> From: Aaron Andrew Hunt <aaronhunt@...>
> Subject: [tuning] .tun file format
> To: "TL" <tuning@yahoogroups.com>
> Date: Monday, December 15, 2008, 2:35 PM
>
>
>
>
>
>
>
>
>
>
>
> I am currently adding .tun file format exporting support to my
>
> software. I have looked around for any information about the origin
>
> or authorship of this file format, but have found nothing. Can anyone
>
> tell me where this format came from, who came up with it, what other
>
> software uses it, etc.?
>
>
>
> Thanks!
>
> Aaron
>
> =====
>
> Aaron Hunt
>
> H-Pi Instruments
>
>
>
> Please note that I choose not to be involved in discussions of things
>
> H-Pi related outside of the H-Pi forums,
>
> <http://launch. groups.yahoo. com/group/ tuning/message/ 74905>
>
> and I cordially invite everyone who is interested to please join and
>
> participate.
>
> Forum: <http://www.h- pi.com/phpBB2/>
>
> Blog: <http://www.h- pi.com/wordpress />
>

🔗Carl Lumma <carl@...>

🔗Aaron Andrew Hunt <aaronhunt@...>

🔗Cameron Bobro <misterbobro@...>

AKAIK the .tun format originated with the Korg Oasys system (DSP card
and software, now a hardware workstation).

--- In tuning@yahoogroups.com, Aaron Andrew Hunt <aaronhunt@...>
wrote:
>
> I am currently adding .tun file format exporting support to my
> software. I have looked around for any information about the
origin
> or authorship of this file format, but have found nothing. Can
anyone
> tell me where this format came from, who came up with it, what
other
> software uses it, etc.?
>
> Thanks!
> Aaron
> =====
> Aaron Hunt
> H-Pi Instruments
>
> Please note that I choose not to be involved in discussions of
things
> H-Pi related outside of the H-Pi forums,
> </tuning/topicId_unknown.html#74905>
> and I cordially invite everyone who is interested to please join
and
> participate.
> Forum: <http://www.h-pi.com/phpBB2/>
> Blog: <http://www.h-pi.com/wordpress/>
>

🔗Carl Lumma <carl@...>

--- In tuning@yahoogroups.com, "Cameron Bobro" <misterbobro@...> wrote:
>
> AKAIK the .tun format originated with the Korg Oasys
> system (DSP card and software, now a hardware workstation).

I'm pretty sure it outdates the OASYS (great PCI card... the
new workstation hardly lives up to its legacy :). I think
the TX802 used .tun.

Again, the author of Scala would probably be very helpful.
Not all synths implement .tun exactly the same way (surprise
surprise!) and Scala has to deal with many of them.
I gather he has not been following the list as closely of
late. I'd recommend contacting him offlist, coul at computer
dot org.

-Carl

🔗Carl Lumma <carl@...>

Let us know what you discover. It is a bit surprising I don't
see any information on its origin on the web.

-Carl

--- In tuning@yahoogroups.com, "Aaron Andrew Hunt" <aaronhunt@...> wrote:
>
> I've contacted Manuel as you suggested, to find out more,
> and I also sent a note to Mark Henning at AnaMark.
> <http://www.mark-henning.de/main_e.php>
>
> .tun is an excellent candidate for use with anything
> implementing MTS, since is just a list of MIDI note
> numbers with corresponding frequencies in Hz. It
> would work well for the Bulk Tuning Dump, for
> example. (For anyone not knowing what that is:
> <http://www.midi.org/techspecs/midituning.php>)
>
> Carl, I'm guessing that this easy compatibility with
> MTS may be what you are citing for some Yamaha
> units that support MTS, but it looks like maybe the
> format originated with Mark Henning(?) I hope to find
> out the facts soon!
>
> Cheers,
> Aaron

🔗Daniel Forro <dan.for@...>

Oasys and TX802 have nothing to do with .tun extension.

All synths including Yamaha have tuning tables in their internal
proprietary format, not published (part of machine code of their OS).
But they can be controlled by SysEx commands, and sent thru MIDI as
SysEx data dumps. When saved, file extension depends how and where it
was saved - .mid, .syx, .b00 - .b99, .x00 - .x99, just to name some...

Concerning Korg Oasys PCI, its tuning tables have .txt extension. I
quote from Owner's Manual (being a happy owner):

------------------------------
Scales
The OASYS PCI’s Scales allow any incoming MIDI note to create any
pitch, with a
resolution of a single cent (1/100 of a semitone). Using Scales, you
can create stretch
tunings, historic European tunings, scales with greater or fewer than
12 tones per
octave, and more.
Each Patch in a Program may have its own Scale, as assigned on the
Program Edit
page (see page 86).
Each Scale is stored as an individual file in the “Scales” folder,
within the Korg
section of the OASYS PCI folder.

Editing Scales
Scales are text files, and can be edited using any standard text
editing program,
such as SimpleText. Each file contains a single Scale.

Syntax
Tuning can be specified separately for each of the 128 MIDI notes.
Each note must
be on a separate line; blank lines are OK.
Each re-tuned note needs to have at least three entries: the incoming
MIDI note, the
resulting pitch (a note name), and fine tuning (+/- 100 cents).
Entries must be
separated by either spaces or tabs. Anything after the fine tuning is
ignored, so you
can put comments at the ends of the lines.
For instance, below is a valid entry, including a comment, which causes a MIDI
note of D2 to be remapped to F3 (E3 plus 100 cents, a full half-step):

d2 E3 +100 D2 becomes F3

There doesn’t need to be a line for every MIDI input note. If no re-
tuning is
specified, that note will simply be sent straight through to its
normal pitch, A1 to
A1, C#3 to C#3, etc. If you want to have an entry for every note, you
can also just
map input straight to output, as shown below:

F4 F4 0 Also could simply not use an “F4” entry.

Symbols
Notes must always include both letter and octave number.
Note letters can be lower or upper-case, so both “d2” and “D2” have
the same
result.
The # sign is used for sharp. Flat notes should be expressed as sharp
notes; for
instance, use A# instead of Bb.

Note and tuning range
The valid range of notes is C-1 to G9.
Cent values for fine tuning must be integers in the range of -100 to
+100. For
positive values, the + sign is optional.
C-1 cannot be fine-tuned down. G9 can be tuned up, however.
-------------------------

Have a nice day!

Daniel Forro

On 17 Dec 2008, at 3:05 AM, Carl Lumma wrote:

> --- In tuning@yahoogroups.com, "Cameron Bobro" <misterbobro@...>
> wrote:
> >
> > AKAIK the .tun format originated with the Korg Oasys
> > system (DSP card and software, now a hardware workstation).
>
> I'm pretty sure it outdates the OASYS (great PCI card... the
> new workstation hardly lives up to its legacy :). I think
> the TX802 used .tun.
>
> Again, the author of Scala would probably be very helpful.
> Not all synths implement .tun exactly the same way (surprise
> surprise!) and Scala has to deal with many of them.
> I gather he has not been following the list as closely of
> late. I'd recommend contacting him offlist, coul at computer
> dot org.
>
> -Carl

🔗Manuel Op de Coul <manuel.op.de.coul@...>

Aaron,

It was invented by the makers of the VAZ Plus softsynth. Soon after
Mark Henning added support for it to his AnaMark softsynth, but didn't
want the arbitrary restriction to integer cents. So he specified a
backwards compatible change to the format by adding a second optional
section with cents values with arbitrary precision.

It's supported in:
Alphakanal Automat;
Big Tick Angelina, Rainbow, Rhino;
Camel Audio Alchemy, Cameleon5000;
DashSignature EVE one;
Fruityloops by Image Line;
HERCs series; Abakos Pro;
LinPlug Albino 2, Alpha 2, CronoX, Octopus, Organ 3, Sophistry;
Manytone ManyStation, ManyGuitar, ManyOne;
Mark Henning AnaMark;
Modartt Pianoteq 2;
Mutagene Mukoco, Macomate 88;
Omringen Oblivion;
Smart Electronix Foorius;
Tobybear Helios;
VAZ Plus, 2001, Modular;
VirSyn Cube, Poseidon and TERA 2;
Wusik Wusikstation v2;
Zebra 2.1

It's the most popular text based format for softsynths, and quite a
straightforward one.

Manuel

🔗Ozan Yarman <ozanyarman@...>

Manuel, is it possible to convert a .scl format to a .tun format using SCALA? I couldn't do it when I was using oblivion.

Oz.

On Dec 17, 2008, at 5:13 PM, Manuel Op de Coul wrote:

> Aaron,
>
> It was invented by the makers of the VAZ Plus softsynth. Soon after
> Mark Henning added support for it to his AnaMark softsynth, but didn't
> want the arbitrary restriction to integer cents. So he specified a
> backwards compatible change to the format by adding a second optional
> section with cents values with arbitrary precision.
>
> It's supported in:
> Alphakanal Automat;
> Big Tick Angelina, Rainbow, Rhino;
> Camel Audio Alchemy, Cameleon5000;
> DashSignature EVE one;
> Fruityloops by Image Line;
> HERCs series; Abakos Pro;
> LinPlug Albino 2, Alpha 2, CronoX, Octopus, Organ 3, Sophistry;
> Manytone ManyStation, ManyGuitar, ManyOne;
> Mark Henning AnaMark;
> Modartt Pianoteq 2;
> Mutagene Mukoco, Macomate 88;
> Omringen Oblivion;
> Smart Electronix Foorius;
> Tobybear Helios;
> VAZ Plus, 2001, Modular;
> VirSyn Cube, Poseidon and TERA 2;
> Wusik Wusikstation v2;
> Zebra 2.1
>
> It's the most popular text based format for softsynths, and quite a
> straightforward one.
>
> Manuel
>

🔗Manuel Op de Coul <manuel.op.de.coul@...>

🔗Carl Lumma <carl@...>

Thanks for clearing that up, Manuel! -Carl

--- In tuning@yahoogroups.com, "Manuel Op de Coul"
<manuel.op.de.coul@...> wrote:
>
> Aaron,
>
> It was invented by the makers of the VAZ Plus softsynth. Soon after
> Mark Henning added support for it to his AnaMark softsynth, but
> didn't want the arbitrary restriction to integer cents. So he
> specified a backwards compatible change to the format by adding a
> second optional section with cents values with arbitrary precision.
>
> It's supported in:
> Alphakanal Automat;
> Big Tick Angelina, Rainbow, Rhino;
> Camel Audio Alchemy, Cameleon5000;
> DashSignature EVE one;
> Fruityloops by Image Line;
> HERCs series; Abakos Pro;
> LinPlug Albino 2, Alpha 2, CronoX, Octopus, Organ 3, Sophistry;
> Manytone ManyStation, ManyGuitar, ManyOne;
> Mark Henning AnaMark;
> Modartt Pianoteq 2;
> Mutagene Mukoco, Macomate 88;
> Omringen Oblivion;
> Smart Electronix Foorius;
> Tobybear Helios;
> VAZ Plus, 2001, Modular;
> VirSyn Cube, Poseidon and TERA 2;
> Wusik Wusikstation v2;
> Zebra 2.1
>
> It's the most popular text based format for softsynths, and quite a
> straightforward one.
>
> Manuel
>

🔗Aaron Andrew Hunt <aaronhunt@...>

Perfect! Thank you so much, Manuel!

Yours,
Aaron
=====

--- In tuning@yahoogroups.com, "Manuel Op de Coul" <manuel.op.de.coul@...> wrote:
>
> Aaron,
>
> It was invented by the makers of the VAZ Plus softsynth. Soon after
> Mark Henning added support for it to his AnaMark softsynth, but didn't
> want the arbitrary restriction to integer cents. So he specified a
> backwards compatible change to the format by adding a second optional
> section with cents values with arbitrary precision.
>
> It's supported in:
> Alphakanal Automat;
> Big Tick Angelina, Rainbow, Rhino;
> Camel Audio Alchemy, Cameleon5000;
> DashSignature EVE one;
> Fruityloops by Image Line;
> HERCs series; Abakos Pro;
> LinPlug Albino 2, Alpha 2, CronoX, Octopus, Organ 3, Sophistry;
> Manytone ManyStation, ManyGuitar, ManyOne;
> Mark Henning AnaMark;
> Modartt Pianoteq 2;
> Mutagene Mukoco, Macomate 88;
> Omringen Oblivion;
> Smart Electronix Foorius;
> Tobybear Helios;
> VAZ Plus, 2001, Modular;
> VirSyn Cube, Poseidon and TERA 2;
> Wusik Wusikstation v2;
> Zebra 2.1
>
> It's the most popular text based format for softsynths, and quite a
> straightforward one.
>
> Manuel
>

🔗Cameron Bobro <misterbobro@...>

The .tun format is also supported by Robin Schmidt Straightliner, one
of the best-sounding softsynths I've heard.

--- In tuning@yahoogroups.com, "Manuel Op de
Coul" <manuel.op.de.coul@...> wrote:
>
> Aaron,
>
> It was invented by the makers of the VAZ Plus softsynth. Soon after
> Mark Henning added support for it to his AnaMark softsynth, but
didn't
> want the arbitrary restriction to integer cents. So he specified a
> backwards compatible change to the format by adding a second
optional
> section with cents values with arbitrary precision.
>
> It's supported in:
> Alphakanal Automat;
> Big Tick Angelina, Rainbow, Rhino;
> Camel Audio Alchemy, Cameleon5000;
> DashSignature EVE one;
> Fruityloops by Image Line;
> HERCs series; Abakos Pro;
> LinPlug Albino 2, Alpha 2, CronoX, Octopus, Organ 3, Sophistry;
> Manytone ManyStation, ManyGuitar, ManyOne;
> Mark Henning AnaMark;
> Modartt Pianoteq 2;
> Mutagene Mukoco, Macomate 88;
> Omringen Oblivion;
> Smart Electronix Foorius;
> Tobybear Helios;
> VAZ Plus, 2001, Modular;
> VirSyn Cube, Poseidon and TERA 2;
> Wusik Wusikstation v2;
> Zebra 2.1
>
> It's the most popular text based format for softsynths, and quite a
> straightforward one.
>
> Manuel
>

🔗Aaron Andrew Hunt <aaronhunt@...>

TL, I received this response from Mark Henning about .tun
The specs Mark refers to in his message are here:
<http://www.mark-henning.de/files/tuning.zip>
(link supplied by Carl Lumma in a previous post; thanks)

I am in the process of adding .tun importing and exporting
to CSE and TPXE, and importing to Scordatura.

Thanks,
Aaron
=====
Aaron Hunt
H-Pi Instruments

---On Dec 17, 2008, at 6:16 PM, Mark Henning wrote:
A basic variant of the format was used before in VAZ 1.5
Plus, but for me, it had some limitations:
- Missing base frequency
- Values were integer cents
- You had to enter a value for *each* MIDI note.
Reading/writing/editing such a file manually is hard work.
Understanding/interpreting (e.g. is there a periodicity) is
almost impossible.

So I added a few features:
- Base frequency specified (-> easy shifting of a scale)
- Values can be floating point
- There is an automatic "scale expansion" ability which
makes it easier to handle periodic scales (e.g. to detune
each note 'E' by +12.5 cents takes only a few lines, see
the example in the specs).

By the way: The base frequency is not necessarily limited
to MIDI note 0 as there is no need to set MIDI note 0 to 0
cents (and negative values are allowed too). You could
set the base frequency to e.g. 440Hz. In this case you
just need to shift the cent values accordingly, so that
the middle key note has 0 cents. :-)

Maybe you're interested in some history:

In 2002, VSTi land suddenly looked like dessert when
you asked for micro tuning support, and it was even
worse with VST-Hosts.

If in such a situation everyone tries to implement his
own file format, this would lead to confusion on the user
side and prevent this feature from spreading around:
For the user it is much easier to load *one* tuning file
into his synths than keep a bundle of different tuning file
formats - one for each synth - up-to-date. (Of course,
the best way would be a straight-forward implementation
in each VST-Host making implementations in plug-ins
unnecessary. But this was far from reality.)

I was looking for a simple format with some capabilities.
I knew about scala. But to me, the file format seemed too
complicated, I didn't expect a wide spread, and the format
specs were not obvious. The VAZ format was simple but too
limited.

That's why I decided to encapsulate the new features in
a separate section of the TUN-file to give it some
downwards-compatibility. So the AnaMark tuning file
format is also compatible to VAZ 1.5 Plus, thus I called it
"AnaMark / VAZ 1.5 Plus-compatible tuning file format".

For the same reason, some weeks later, I put the format
specs and some basic C++-source code online to encourage
other developers to implement it as well.

Sorry for prosing. ;-) But you asked. ;->

Any clearness left to confuse? ;-)

🔗Aaron Andrew Hunt <aaronhunt@...>

OK, I just received clarification from Mark Henning, and
he also requested that I post the message here. Both
VAZ and AnaMark are using CENTS values, not Hertz. The only
value which is Hz is the AnaMark 'basefrequency' as given
in the C header file - this is what was confusing me! I am
therefore deleting 2 previous posts about my 'correction'
which was completely my error! Here is Mark's note:

---On Thu, 18 Dec 2008 14:55:27 -0600, you wrote:
>I have a question about this part:
>
>A basic variant of the format was used before in VAZ 1.5
>Plus, but for me, it had some limitations:
>- Missing base frequency
>- Values were integer cents
>
>Looking at the C code you supplied, I verified that the
>original VAZ is supposed to use cents values, while
>AnaMark uses Hz values?

Both - the [Tuning] as well as the [Exact Tuning] section use cent
values.

>I ask because actual .tun files I have seen which
>have the [Tuning] header show something like:
>
>note60=256
>
>where this is giving a *frequency* in Hz rather than a
>cents value, so it appears that VAZ was using Hz and
>not cents?

No, VAZ uses cents. From the help file of the current VAZ Plus 2.02
Demo which can be downloaded from http://www.software-technology.com
you can find under the topic "Synth preferences":

|Enable Microtuning File enables the use of a tuning map file selected
|just below. These are text files using the Windows ini file syntax which
|allow a tuning, accurate to 1 cent to be entered for every MIDI note.

There it is said definitely: Values are given in cents, accuracy is
one cent.

There might be other synths using tuning files with .tun extension and
values given in Hz. But then it's not an AnaMark / VAZ tuning file.
(And for me, Hz-values are not reasonable, as it's no longer obvious
to see the differences to the standard scale nor to find the pattern
in a scale; and shifting the scale will also be a nasty task. Just
shift a scale given in Hz and it will look completely different
compared with the original one.)

BTW2: There is no need to give each note a higher pitch than the
previous one. So

note 1=100
note 2=200
note 3=300
...
note 59 = 5900
note 60=110
note 61=210
note 62=310
...

would be O.K.. It depends on how you want to use a scale (playing
live, special way to separate notes belonging to different scales in
one sequencer view etc.).

This seems to be a discussion on the tuning list. As I have no direct
access to it, I would be glad if you could forward this email too.

Greets,

- Mark

--
AnaMark V2.21 - The VST-Synthesizer
http://www.mark-henning.de/

🔗Aaron Andrew Hunt <aaronhunt@...>

I deleted previous posts where I said .tun uses Hz, to
try and clear up any confusion someone following this
might have. Sorry!

I considered adding pages to the H-Pi glossary about
these file formats, but I think the proper location for
such information online is probably wikipedia? Unless
someone else has a better suggestion?

If not, I suggest that wikipedia pages be made for the
file formats commonly used in microtuning, at least .scl
and .tun, as these appear to be the most important for
developers - the most widely supported. Scala already
has a page clearly defining its structure,
<http://www.xs4all.nl/~huygensf/scala/scl_format.html>
When I search for something like this for .tun, I
find .tun is an extension from microsoft or other
some such concerning file trees or something. There
are also 'file extensions' websites that give incomplete
or wrong information for the .scl file format.
What we need is a situation where someone
types .tun or .scl into Google and comes up with a
webpage having totally definitive information needed
to implement the standard. Right now a search for
.scl from Google brings up a wikipedia page on
Summa Cum Laude.
<http://en.wikipedia.org/wiki/SCL>
With a wiki .scl page, even if this is still the first
Google page to come up, there can be placed on
that page a clear link to the wiki page on .scl

Searching Google for .scl + Scala does not even bring
up the correct xs4all page on the first Google listing.
I had to go to a page and scroll down and click another
link. And I already know knew where to find that other
link.

I feel the correct and complete information should
be right there for anyone, not requiring wading through
links and wrong information.

Is wikipedia the right way to go with this?

Thanks,
Aaron Hunt
=====

🔗Aaron Andrew Hunt <aaronhunt@...>

🔗Carl Lumma <carl@...>

Aaron wrote:

> What we need is a situation where someone
> types .tun or .scl into Google and comes up with a
> webpage having totally definitive information needed
> to implement the standard.

That would be nice! I think part of the problem is that
google doesn't respect the dot. At the beginning of this
thread, I tried searches like "".scl"" and "+.scl" but
these didn't help.

This page
http://www.xs4all.nl/~huygensf/scala/scl_format.html
does come up for "scala file format" (1st/2nd result).

".scl file format" produces the above page as the
3rd/4th result.

There's also a link to the above page from
http://en.wikipedia.org/wiki/Scala_(program)

I do not see pages for the .seq and .kbm formats. The
above page refers to the help for .kbm, but I don't see
any format description of it there. Manuel, do you have
pages describing these?

> Is wikipedia the right way to go with this?

Certainly they could be added to this page:
http://en.wikipedia.org/wiki/List_of_file_formats_(alphabetical)

I'll try to do that when I get the time...

-Carl

🔗Carl Lumma <carl@...>

🔗Mark Henning <maillists8377@...>

--- In tuning@yahoogroups.com, "Aaron Andrew Hunt" <aaronhunt@...> wrote:
> I've contacted Manuel as you suggested, to find out more,
> and I also sent a note to Mark Henning at AnaMark.
> <http://www.mark-henning.de/main_e.php>

A basic variant of the format was used before in VAZ 1.5 Plus, but for
me, it had some limitations:
- Missing base frequency
- Values were integer cents
- You had to enter a value for *each* MIDI note.
Reading/writing/editing such a file manually is hard work.
Understanding/interpreting (e.g. is there a periodicity) is almost
impossible.

So I added a few features:
- Base frequency specified (-> easy shifting of a scale)
- Values can be floating point
- There is an automatic "scale expansion" ability which makes it
easier to handle periodic scales (e.g. to detune each note 'E' by
+12.5 cents takes only a few lines, see the example in the specs).

By the way: The base frequency is not necessarily limited to MIDI note
0 as there is no need to set MIDI note 0 to 0 cents (and negative
values are allowed too). You could set the base frequency to e.g.
440Hz. In this case you just need to shift the cent values
accordingly, so that the middle key note has 0 cents. :-)

Maybe you're interested in some history:

In 2002, VSTi land suddenly looked like dessert when you asked for
micro tuning support, and it was even worse with VST-Hosts.

If in such a situation everyone tries to implement his own file
format, this would lead to confusion on the user side and prevent this
feature from spreading around: For the user it is much easier to load
*one* tuning file into his synths than keep a bundle of different
tuning file formats - one for each synth - up-to-date. (Of course, the
best way would be a straight-forward implementation in each VST-Host
making implementations in plug-ins unnecessary. But this was far from
reality.)

I was looking for a simple format with some capabilities. I knew about
scala. But to me, the file format seemed too complicated, I didn't
expect a wide spread, and the format specs were not obvious. The VAZ
format was simple but too limited.

That's why I decided to encapsulate the new features in a separate
section of the TUN-file to give it some downwards-compatibility. So
the AnaMark tuning file format is also compatible to VAZ 1.5 Plus,
thus I called it "AnaMark / VAZ 1.5 Plus-compatible tuning file format".

For the same reason, some weeks later, I put the format specs and some
basic C++-source code online to encourage other developers to
implement it as well.

Sorry for prosing. ;-) But you asked. ;->

Any clearness left to confuse? ;-)

🔗Marcel de Velde <m.develde@...>

🔗David Ryle <dryle@...>

🔗Mark Henning <maillists8377@...>

--- In tuning@yahoogroups.com, "Aaron Andrew Hunt" <aaronhunt@...> wrote:
> Any other formats to wiki?

Wouldn't it be better to write a wiki site about micro tuning and to
put links about the file formats there? (I wonder that a search for
micro tuning in wikipedia gives no result...)

I think, when people begin working with micro tuning, they will first
look for this than for certain file formats or file extensions. And I
doubt that wikipedia is the right place for technical specifications.
There are better places in the www like wotsit.org or something like that.

At least for the AnaMark/VAZ .tun format I'll keep hosting the specs
on my website. And directing the people to the original source eases
keeping them up-to-date.

BTW: I'll revise the C++ sources and the specs in the next weeks a
little bit to improve english language (make things clearer) and to
update the source to more current header files.

- Mark

🔗Aaron Andrew Hunt <aaronhunt@...>

Jacob Barton's microtonal wiki comes to mind:
<http://xenharmonic.wikispaces.com/>

But my idea is to make the file format info accessible
to developers, not to microtonal enthusiasts, per se.
In my opinion things should get to the point where
people who want to make microtonal music do not need
to worry about learning anything about file formats...
which prompts my next post.

Yours,
Aaron H

--- In tuning@yahoogroups.com, "Mark Henning" <maillists8377@...> wrote:
>
> --- In tuning@yahoogroups.com, "Aaron Andrew Hunt" <aaronhunt@> wrote:
> > Any other formats to wiki?
>
> Wouldn't it be better to write a wiki site about micro tuning and to
> put links about the file formats there? (I wonder that a search for
> micro tuning in wikipedia gives no result...)
>
> I think, when people begin working with micro tuning, they will first
> look for this than for certain file formats or file extensions. And I
> doubt that wikipedia is the right place for technical specifications.
> There are better places in the www like wotsit.org or something like that.
>
> At least for the AnaMark/VAZ .tun format I'll keep hosting the specs
> on my website. And directing the people to the original source eases
> keeping them up-to-date.
>
> BTW: I'll revise the C++ sources and the specs in the next weeks a
> little bit to improve english language (make things clearer) and to
> update the source to more current header files.
>
> - Mark
>

.tun file format

🔗Aaron Andrew Hunt <aaronhunt@...>

🔗Michael Sheiman <djtrancendance@...>

🔗Aaron Andrew Hunt <aaronhunt@...>

🔗Carl Lumma <carl@...>

🔗Aaron Andrew Hunt <aaronhunt@...>

🔗Cameron Bobro <misterbobro@...>

🔗Carl Lumma <carl@...>

🔗Carl Lumma <carl@...>

🔗Daniel Forro <dan.for@...>

🔗Manuel Op de Coul <manuel.op.de.coul@...>

🔗Ozan Yarman <ozanyarman@...>

🔗Manuel Op de Coul <manuel.op.de.coul@...>

🔗Carl Lumma <carl@...>

🔗Aaron Andrew Hunt <aaronhunt@...>

🔗Cameron Bobro <misterbobro@...>

🔗Aaron Andrew Hunt <aaronhunt@...>

🔗Aaron Andrew Hunt <aaronhunt@...>

🔗Aaron Andrew Hunt <aaronhunt@...>

🔗Aaron Andrew Hunt <aaronhunt@...>

🔗Carl Lumma <carl@...>

🔗Carl Lumma <carl@...>

🔗Mark Henning <maillists8377@...>

🔗Marcel de Velde <m.develde@...>

🔗David Ryle <dryle@...>

🔗Mark Henning <maillists8377@...>

🔗Aaron Andrew Hunt <aaronhunt@...>

🔗Aaron Andrew Hunt <aaronhunt@...>