Quantcast
Channel: tladb » Nodal
Viewing all articles
Browse latest Browse all 4

Mapping Eve Online to music with Nodal

$
0
0

The Kor-Azor sector

The Lonetrek sector

The maps from Eve Strategic Maps where used as a basis for mapping the systems to Nodal nodes. The pitch was set be security level;. In the case of Kor-Azor the installations modified the basic pitch. In the Lonetrek project each installation added a note upwards in the scale. Velocity was set roughly from the amount of asteroids and moons. There is not as much movement in the music and that would entail different pitch choices and even using the paths to modify CC values.

This was the second method thought of  to create music from Eve Online maps. The first idea was to convert Eve system data to Nodal files. Eve system data can be downloaded as SQLite files. These files can be viewed in the Base application and exported as XML.

An Nodal node in pList is :

 <key>35</key>
            <dict>
                <key>ContainerType</key>
                <string>StrDict</string>
                <key>DurationList</key>
                <string>100%</string>
                <key>TickPos</key>
                <string>{-2372832, -776160}</string>
                <key>Type</key>
                <string>Node</string>
                <key>ArcIdentifiers</key>
                <dict>
                    <key>ContainerType</key>
                    <string>IntDict</string>
                    <key>41</key>
                    <integer>0</integer>
                    <key>44</key>
                    <integer>1</integer>
                </dict>
                <key>VelocityList</key>
                <string>24</string>
                <key>PitchList</key>
                <string>C4</string>
                <key>SignallingMethod</key>
                <string>Random</string>
                <key>ArcUsageList</key>
                <string>41=1,44=1</string>
            </dict>

and from an XML export of the Eve systems table:

<mapsolarsystems>
	<regionID>10000001</regionID>
	<constellationID>20000001</constellationID>
	<solarSystemID>30000001</solarSystemID>
	<solarSystemName>Tanoo</solarSystemName>
	<x>-8.85107925999806e+16</x>
	<y>4.23694439668789e+16</y>
	<z>4.45135253464797e+16</z>
	<xMin>-8.85119031484906e+16</xMin>
	<xMax>-8.85092564717606e+16</xMax>
	<yMin>4.23692979274891e+16</yMin>
	<yMax>4.23696457492639e+16</yMax>
	<zMin>4.45130363558928e+16</zMin>
	<zMax>4.45141116897829e+16</zMax>
	<luminosity>0.01575</luminosity>
	<border>1</border>
	<fringe>0</fringe>
	<corridor>0</corridor>
	<hub>1</hub>
	<international>1</international>
	<regional>1</regional>
	<constellation>1</constellation>
	<security>0.858324068848468</security>
	<factionID>NULL</factionID>
	<radius>1323338364984.0</radius>
	<sunTypeID>3802</sunTypeID>
	<securityClass>B</securityClass>
</mapsolarsystems>

But there are a lot of programming issues which are beyond me such as mapping the 7000+ 3D Eve system co-ordinates to Nodal 2D.

This is using Nodal 1.7. Nodal 1.8 has been released and this may present some new ideas.

 



Filed under: Music


Viewing all articles
Browse latest Browse all 4

Latest Images

Trending Articles





Latest Images