mfell

hi... has anyone used artnet (dmx over ethernet) or developed an 

hi... has anyone used artnet (dmx over ethernet) or developed an  
artnet object or patch???
thanks
mark
-----------------------
www.markfell.com
-----------------------


artnet

Can't find anything on google or maxobjects.com. I'm interested in this aswell.

Quote: mfell wrote on Wed, 06 June 2007 13:05

----------------------------------------------------

> hi... has anyone used artnet (dmx over ethernet) or developed an 

Quote: mfell wrote on Wed, 06 June 2007 13:05
----------------------------------------------------
> hi... has anyone used artnet (dmx over ethernet) or developed an  
> artnet object or patch???
> thanks
> mark
> -----------------------
> www.markfell.com
> -----------------------
>
>
>
>
----------------------------------------------------


i think vvvv has an artnet 'node' (object) which im going to look into

On 6 Jun 2007, at 14:12, Mattijs Kneppers wrote:

> Can't find anything on google or maxobjects.com. I'm interested in 

> Quote: mfell wrote on Wed, 06 June 2007 13:05

> ----------------------------------------------------

>> hi... has anyone used artnet (dmx over ethernet) or developed an

> Hard- and software for interactive audiovisual sampling

i think vvvv has an artnet 'node' (object) which im going to look into
m

>
> Can't find anything on google or maxobjects.com. I'm interested in  
> this aswell.
>
> Mattijs
>
> Quote: mfell wrote on Wed, 06 June 2007 13:05
> ----------------------------------------------------
>> hi... has anyone used artnet (dmx over ethernet) or developed an
>> artnet object or patch???
>> thanks
>> mark
>> -----------------------
>> www.markfell.com
>> -----------------------
>>
>>
>>
>>
> ----------------------------------------------------
>
>
> --
> SmadSteck - http://www.smadsteck.nl
> Hard- and software for interactive audiovisual sampling

-----------------------
www.markfell.com
-----------------------

Quote: mfell wrote on Wed, 06 June 2007 15:32

> i think vvvv has an artnet 'node' (object) which im going to look into

As in trying to make it into a max object?

Quote: mfell wrote on Wed, 06 June 2007 15:32
----------------------------------------------------
> i think vvvv has an artnet 'node' (object) which im going to look into
> m
>

no, as in buying a pc to run vvvv so i can use artnet :(

On 6 Jun 2007, at 16:00, Mattijs Kneppers wrote:

> Quote: mfell wrote on Wed, 06 June 2007 15:32

>> i think vvvv has an artnet 'node' (object) which im going to look 

> As in trying to make it into a max object?

no, as in buying a pc to run vvvv so i can use artnet :(
m

>
> Quote: mfell wrote on Wed, 06 June 2007 15:32
> ----------------------------------------------------
>> i think vvvv has an artnet 'node' (object) which im going to look  
>> into
>> m
>>
>
> As in trying to make it into a max object?
>
> Mattijs
> --
> SmadSteck - http://www.smadsteck.nl
> Hard- and software for interactive audiovisual sampling

Quote: mfell wrote on Wed, 06 June 2007 17:34

> no, as in buying a pc to run vvvv so i can use artnet :(

Aw. I don't think artnet is a very hard protocol to implement in C, so someone that has experience with usb devices should be able to code a max object.

How much will the pc + vvvv learning time cost you? Perhaps for this amount of money somone is willing to give it a try?

&q=+artnet+dmx+show:zI3zU48Wzos:8m1xQWRedxQ:ngMffP0CVcc&sa=N&cd=2&ct=rc

http://www.nomis52.net/data/artnet/qlc/artnetout.tar.gz

Quote: mfell wrote on Wed, 06 June 2007 17:34
----------------------------------------------------
> no, as in buying a pc to run vvvv so i can use artnet :(
> m
>

Just look at http://www.google.com/codesearch?hl=en
&q=+artnet+dmx+show:zI3zU48Wzos:8m1xQWRedxQ:ngMffP0CVcc&sa=N&cd=2&ct=rc
&cs_p=http://www.nomis52.net/data/artnet/qlc/artnetout.tar.gz
&cs_f=artnetout/artnetthread.cpp#a0

Quote: Mattijs wrote on Wed, 06 June 2007 17:55

> &q=+artnet+dmx+show:zI3zU48Wzos:8m1xQWRedxQ:ngMffP0CVcc&sa=N&cd=2&ct=rc

No, seriously, after some more checks I think this guy could be willing to help..

http://www.nomis52.net/?section=projects§2=artnet&page=intro

Quote: Mattijs wrote on Wed, 06 June 2007 17:55
----------------------------------------------------

> Just look at http://www.google.com/codesearch?hl=en
> &q=+artnet+dmx+show:zI3zU48Wzos:8m1xQWRedxQ:ngMffP0CVcc&sa=N&cd=2&ct=rc
> &cs_p=http://www.nomis52.net/data/artnet/qlc/artnetout.tar.gz
> &cs_f=artnetout/artnetthread.cpp#a0
>
> We're almost done! ;)
>
> Mattijs
----------------------------------------------------

yeh i guess you are right. but i wanted to learn vvvv anyway..

but i would like to know if anyone would write an artnet object.. i 

dont think it would need any experience of usb as its ethernet...

On 6 Jun 2007, at 16:55, Mattijs Kneppers wrote:

> Quote: mfell wrote on Wed, 06 June 2007 17:34

>> no, as in buying a pc to run vvvv so i can use artnet :(

> Aw. I don't think artnet is a very hard protocol to implement in C, 

> so someone that has experience with usb devices should be able to 

> How much will the pc + vvvv learning time cost you? Perhaps for 

> this amount of money somone is willing to give it a try?

http://www.google.com/codesearch?hl=en&q=+artnet+dmx

> 8m1xQWRedxQ:ngMffP0CVcc&sa=N&cd=2&ct=rc&cs_p=

> data/artnet/qlc/artnetout.tar.gz&cs_f=artnetout/artnetthread.cpp#a0

yeh i guess you are right. but i wanted to learn vvvv anyway..
but i would like to know if anyone would write an artnet object.. i  
dont think it would need any experience of usb as its ethernet...
m

>
> Quote: mfell wrote on Wed, 06 June 2007 17:34
> ----------------------------------------------------
>> no, as in buying a pc to run vvvv so i can use artnet :(
>> m
>>
>
> Aw. I don't think artnet is a very hard protocol to implement in C,  
> so someone that has experience with usb devices should be able to  
> code a max object.
>
> How much will the pc + vvvv learning time cost you? Perhaps for  
> this amount of money somone is willing to give it a try?
>
> Just look at http://www.google.com/codesearch?hl=en&q=+artnet+dmx 
> +show:zI3zU48Wzos: 
> 8m1xQWRedxQ:ngMffP0CVcc&sa=N&cd=2&ct=rc&cs_p=http://www.nomis52.net/ 
> data/artnet/qlc/artnetout.tar.gz&cs_f=artnetout/artnetthread.cpp#a0
>
> We're almost done! ;)
>
> Mattijs
> --
> SmadSteck - http://www.smadsteck.nl
> Hard- and software for interactive audiovisual sampling

Forgive me if I am being obscenely slow, but what is the benefit of 

I mean both run over ethernet, and both require conversion to become 

DMX, right? The choice of protocol shouldn't matter all that much, 

should it? The upside with OSC is that udpsend and udpreceive are both 

in Max already, you can quickly compile a client app to sit on any 

> yeh i guess you are right. but i wanted to learn vvvv anyway..

> but i would like to know if anyone would write an artnet object.. i 

> dont think it would need any experience of usb as its ethernet...

> On 6 Jun 2007, at 16:55, Mattijs Kneppers wrote:

Forgive me if I am being obscenely slow, but what is the benefit of 
"artnet" over something like OSC?

I mean both run over ethernet, and both require conversion to become 
DMX, right? The choice of protocol shouldn't matter all that much, 
should it? The upside with OSC is that udpsend and udpreceive are both 
in Max already, you can quickly compile a client app to sit on any 
machine, anywhere in the world...

mark@markfell.com skrev:
> yeh i guess you are right. but i wanted to learn vvvv anyway..
> but i would like to know if anyone would write an artnet object.. i 
> dont think it would need any experience of usb as its ethernet...
> m
>
> On 6 Jun 2007, at 16:55, Mattijs Kneppers wrote:
>
>>

Since artnet is used by most light technicians I assume there are much more readymade convertors and control desks designed specifically for this protocol.

Quote: Wetterberg wrote on Wed, 06 June 2007 20:13

> Forgive me if I am being obscenely slow, but what is the benefit of 

> I mean both run over ethernet, and both require conversion to become 

> DMX, right? The choice of protocol shouldn't matter all that much, 

> should it? The upside with OSC is that udpsend and udpreceive are both 

> in Max already, you can quickly compile a client app to sit on any 

> > yeh i guess you are right. but i wanted to learn vvvv anyway..

> > but i would like to know if anyone would write an artnet object.. i 

> > dont think it would need any experience of usb as its ethernet...

> > On 6 Jun 2007, at 16:55, Mattijs Kneppers wrote:

Quote: Wetterberg wrote on Wed, 06 June 2007 20:13
----------------------------------------------------
> Forgive me if I am being obscenely slow, but what is the benefit of 
> "artnet" over something like OSC?
>
> I mean both run over ethernet, and both require conversion to become 
> DMX, right? The choice of protocol shouldn't matter all that much, 
> should it? The upside with OSC is that udpsend and udpreceive are both 
> in Max already, you can quickly compile a client app to sit on any 
> machine, anywhere in the world...
>
> Andreas.
>
>
> mark@markfell.com skrev:
> > yeh i guess you are right. but i wanted to learn vvvv anyway..
> > but i would like to know if anyone would write an artnet object.. i 
> > dont think it would need any experience of usb as its ethernet...
> > m
> >
> > On 6 Jun 2007, at 16:55, Mattijs Kneppers wrote:
> >
> >>
>
>
>
----------------------------------------------------


Well, even the guys that invented the protocol, Artistic License, seem 

to have a fairly bland selection going on:

http://www.artisticlicence.com/cat3_1.htm

I see nothing revolutionary there, and since both the dmxusbpro unit and 

the Art Net converters end up as a DMX universe I don't see much of a 

By the way, when you say "most light technicians", you must mean "most 

light technicians who need to network several universes of DMX" - which 

can't be a great number of people, right?

> Since artnet is used by most light technicians I assume there are much more readymade convertors and control desks designed specifically for this protocol.

> Quote: Wetterberg wrote on Wed, 06 June 2007 20:13

>> Forgive me if I am being obscenely slow, but what is the benefit of 

Well, even the guys that invented the protocol, Artistic License, seem 
to have a fairly bland selection going on:
http://www.artisticlicence.com/cat3_1.htm

I see nothing revolutionary there, and since both the dmxusbpro unit and 
the Art Net converters end up as a DMX universe I don't see much of a 
real-world difference.

By the way, when you say "most light technicians", you must mean "most 
light technicians who need to network several universes of DMX" - which 
can't be a great number of people, right?

Mattijs Kneppers skrev:
> Since artnet is used by most light technicians I assume there are much more readymade convertors and control desks designed specifically for this protocol.
>
> Mattijs
>
> Quote: Wetterberg wrote on Wed, 06 June 2007 20:13
> ----------------------------------------------------
>
>> Forgive me if I am being obscenely slow, but what is the benefit of 
>> "artnet" over something like OSC?
>>
>>


my understanding is that the advantage of artnet over OSC is that 

there are hardware units that can convert from artnet to dmx and also 

increasingly many fixtures now come with artnet onboard. if i was 

using OSC i would have to have a computer receiving it, and then some 

from of dmx unit attached to the computer. but im not an expert in 

lighting systems so if you know otherwise please let me know.

On 6 Jun 2007, at 19:37, Mattijs Kneppers wrote:

> Since artnet is used by most light technicians I assume there are 

> much more readymade convertors and control desks designed 

>> Forgive me if I am being obscenely slow, but what is the benefit of

>> I mean both run over ethernet, and both require conversion to become

>> DMX, right? The choice of protocol shouldn't matter all that much,

>> should it? The upside with OSC is that udpsend and udpreceive are 

>> in Max already, you can quickly compile a client app to sit on any

>>> yeh i guess you are right. but i wanted to learn vvvv anyway..

>>> but i would like to know if anyone would write an artnet object.. i

>>> dont think it would need any experience of usb as its ethernet...

>>> On 6 Jun 2007, at 16:55, Mattijs Kneppers wrote:

my understanding is that the advantage of artnet over OSC is that  
there are hardware units that can convert from artnet to dmx and also  
increasingly many fixtures now come with artnet onboard. if i was  
using OSC i would have to have a computer receiving it, and then some  
from of dmx unit attached to the computer. but im not an expert in  
lighting systems so if you know otherwise please let me know.
m

>
> Since artnet is used by most light technicians I assume there are  
> much more readymade convertors and control desks designed  
> specifically for this protocol.
>
> Mattijs
>
> Quote: Wetterberg wrote on Wed, 06 June 2007 20:13
> ----------------------------------------------------
>> Forgive me if I am being obscenely slow, but what is the benefit of
>> "artnet" over something like OSC?
>>
>> I mean both run over ethernet, and both require conversion to become
>> DMX, right? The choice of protocol shouldn't matter all that much,
>> should it? The upside with OSC is that udpsend and udpreceive are  
>> both
>> in Max already, you can quickly compile a client app to sit on any
>> machine, anywhere in the world...
>>
>> Andreas.
>>
>>
>> mark@markfell.com skrev:
>>> yeh i guess you are right. but i wanted to learn vvvv anyway..
>>> but i would like to know if anyone would write an artnet object.. i
>>> dont think it would need any experience of usb as its ethernet...
>>> m
>>>
>>> On 6 Jun 2007, at 16:55, Mattijs Kneppers wrote:
>>>
>>>>
>>
>>
>>
> ----------------------------------------------------
>
>
> --
> SmadSteck - http://www.smadsteck.nl
> Hard- and software for interactive audiovisual sampling

a couple of years ago i tried using an artnet to dmx box in order to 

control multiple led light fixtures ( i needed someting like 600 dmx 

channels and artistic license had one box with two dms universes out).

The whole of Artnet can do more than just dmx over ethernet, but if 

you are interested in only the dmx part their protocol is really 

simple: it is basically a list of all the dmx data plus an artnet 

If you use aka.datagram to format your data you can use udpsend (read 

the CNMAT compatibility thingie in the helpfile) to send them to your 

For receiving you'd need to decode packets received by udpreceive, 

don't remember now whether aka.datagram can do that too.

Below the abstraction I made at the time to send dmx values to an 

artnet box, I made it a couple of years ago, you should replace 

ot.udp by udpsend since times have changed and perhaps change the 

For the project I was working on at the time (see: 

www.lumen.nu/rekveld/wp/?p=121 ) I ended up buying two lanboxes under 

pressure of a deadline, and later it turned out that the artnet box I 

had was a faulty one. (They repaired it and I've never used it since, 

want to buy one ? it's a Net-Lynx O/P, i'll take any reasonable 

The lanboxes are great, by the way, they use a similar (but slightly 

more clever) dmx over ethernet protocol if you only want a ethernet- 

to-dmx converter, and the boxes can do much more. (You could even 

program them in forth and make them standalone controllers...) And 

they now come with max objects. They do not receive dmx, however.

On Jun 6, 2007, at 11:06 , mark@markfell.com wrote:

> my understanding is that the advantage of artnet over OSC is that 

> there are hardware units that can convert from artnet to dmx and 

> also increasingly many fixtures now come with artnet onboard. if i 

> was using OSC i would have to have a computer receiving it, and 

> then some from of dmx unit attached to the computer. but im not an 

> expert in lighting systems so if you know otherwise please let me 

a couple of years ago i tried using an artnet to dmx box in order to  
control multiple led light fixtures ( i needed someting like 600 dmx  
channels and artistic license had one box with two dms universes out).
The whole of Artnet can do more than just dmx over ethernet, but if  
you are interested in only the dmx part their protocol is really  
simple: it is basically a list of all the dmx data plus an artnet  
header.

If you use aka.datagram to format your data you can use udpsend (read  
the CNMAT compatibility thingie in the helpfile) to send them to your  
artnet box. No need for new externals.
For receiving you'd need to decode packets received by udpreceive,  
don't remember now whether aka.datagram can do that too.

Below the abstraction I made at the time to send dmx values to an  
artnet box, I made it a couple of years ago, you should replace  
ot.udp by udpsend since times have changed and perhaps change the  
patch a bit accordingly.

For the project I was working on at the time (see: http:// 
www.lumen.nu/rekveld/wp/?p=121 ) I ended up buying two lanboxes under  
pressure of a deadline, and later it turned out that the artnet box I  
had was a faulty one. (They repaired it and I've never used it since,  
want to buy one ? it's a Net-Lynx O/P, i'll take any reasonable  
offer....)
The lanboxes are great, by the way, they use a similar (but slightly  
more clever) dmx over ethernet protocol if you only want a ethernet- 
to-dmx converter, and the boxes can do much more. (You could even  
program them in forth and make them standalone controllers...) And  
they now come with max objects. They do not receive dmx, however.

> my understanding is that the advantage of artnet over OSC is that  
> there are hardware units that can convert from artnet to dmx and  
> also increasingly many fixtures now come with artnet onboard. if i  
> was using OSC i would have to have a computer receiving it, and  
> then some from of dmx unit attached to the computer. but im not an  
> expert in lighting systems so if you know otherwise please let me  
> know.
> m
>

thats a massive help and clarifies loads of issues.

i'll get back to you about the artnet box if i need to buy one...

On 6 Jun 2007, at 23:35, Joost Rekveld wrote:

> a couple of years ago i tried using an artnet to dmx box in order 

> to control multiple led light fixtures ( i needed someting like 600 

> dmx channels and artistic license had one box with two dms 

> The whole of Artnet can do more than just dmx over ethernet, but if 

> you are interested in only the dmx part their protocol is really 

> simple: it is basically a list of all the dmx data plus an artnet 

> If you use aka.datagram to format your data you can use udpsend 

> (read the CNMAT compatibility thingie in the helpfile) to send them 

> to your artnet box. No need for new externals.

> For receiving you'd need to decode packets received by udpreceive, 

> don't remember now whether aka.datagram can do that too.

> Below the abstraction I made at the time to send dmx values to an 

> artnet box, I made it a couple of years ago, you should replace 

> ot.udp by udpsend since times have changed and perhaps change the 

> For the project I was working on at the time (see: 

> www.lumen.nu/rekveld/wp/?p=121 ) I ended up buying two lanboxes 

> under pressure of a deadline, and later it turned out that the 

> artnet box I had was a faulty one. (They repaired it and I've never 

> used it since, want to buy one ? it's a Net-Lynx O/P, i'll take any 

> The lanboxes are great, by the way, they use a similar (but 

> slightly more clever) dmx over ethernet protocol if you only want a 

> ethernet-to-dmx converter, and the boxes can do much more. (You 

> could even program them in forth and make them standalone 

> controllers...) And they now come with max objects. They do not 

> On Jun 6, 2007, at 11:06 , mark@markfell.com wrote:

>> my understanding is that the advantage of artnet over OSC is that 

>> there are hardware units that can convert from artnet to dmx and 

>> also increasingly many fixtures now come with artnet onboard. if i 

thats a massive help and clarifies loads of issues.
i'll get back to you about the artnet box if i need to buy one...
thanks
mark

> Hi,
>
> a couple of years ago i tried using an artnet to dmx box in order  
> to control multiple led light fixtures ( i needed someting like 600  
> dmx channels and artistic license had one box with two dms  
> universes out).
> The whole of Artnet can do more than just dmx over ethernet, but if  
> you are interested in only the dmx part their protocol is really  
> simple: it is basically a list of all the dmx data plus an artnet  
> header.
>
> If you use aka.datagram to format your data you can use udpsend  
> (read the CNMAT compatibility thingie in the helpfile) to send them  
> to your artnet box. No need for new externals.
> For receiving you'd need to decode packets received by udpreceive,  
> don't remember now whether aka.datagram can do that too.
>
> Below the abstraction I made at the time to send dmx values to an  
> artnet box, I made it a couple of years ago, you should replace  
> ot.udp by udpsend since times have changed and perhaps change the  
> patch a bit accordingly.
>
> For the project I was working on at the time (see: http:// 
> www.lumen.nu/rekveld/wp/?p=121 ) I ended up buying two lanboxes  
> under pressure of a deadline, and later it turned out that the  
> artnet box I had was a faulty one. (They repaired it and I've never  
> used it since, want to buy one ? it's a Net-Lynx O/P, i'll take any  
> reasonable offer....)
> The lanboxes are great, by the way, they use a similar (but  
> slightly more clever) dmx over ethernet protocol if you only want a  
> ethernet-to-dmx converter, and the boxes can do much more. (You  
> could even program them in forth and make them standalone  
> controllers...) And they now come with max objects. They do not  
> receive dmx, however.
>
>
> hope this helps,
>
>
> Joost.
>
>
>
>
> On Jun 6, 2007, at 11:06 , mark@markfell.com wrote:
>
>> my understanding is that the advantage of artnet over OSC is that  
>> there are hardware units that can convert from artnet to dmx and  
>> also increasingly many fixtures now come with artnet onboard. if i  
>> was using OSC i would have to have a computer receiving it, and  
>> then some from of dmx unit attached to the computer. but im not an  
>> expert in lighting systems so if you know otherwise please let me  
>> know.
>> m
>>
>
>
> max v2;
> #N vpatcher 243 254 1086 859;
> #P origin -5 0;
> #N comlet write return (ints);
> #P outlet 292 542 15 0;
> #P window setfont "Sans Serif" 9.;
> #P newex 233 510 69 196617 aka.datagram;
> #N comlet write return (symbol);
> #P outlet 233 542 15 0;
> #P newex 184 321 27 196617 / 2.;
> #P newex 184 368 27 196617 << 1;
> #P newex 184 344 24 196617 ceil;
> #P message 184 392 51 196617 length $1;
> #P newex 184 298 30 196617 + 18;
> #P newex 579 439 65 196617 prepend host;
> #P newex 14 79 29 196617 t b b;
> #P message 511 392 45 196617 offset 0;
> #P newex 242 349 27 196617 t l b;
> #P newex 242 325 75 196617 pack 0 0 0;
> #P message 650 439 85 196617 tellmeeverything;
> #N comlet write return (ints);
> #P outlet 73 533 15 0;
> #P newex 14 501 69 196617 aka.datagram;
> #P newex 14 54 55 196617 route bang;
> #P newex 14 476 165 196617 otudp write 10.255.255.255 6454;
> #P newex 14 441 69 196617 aka.datagram;
> #P newex 532 65 89 196617 t b b b;
> #P message 532 87 33 196617 reset;
> #P newex 274 297 38 196617 & 255;
> #P newex 242 297 27 196617 >> 8;
> #P newex 301 191 27 196617 0;
> #P newex 99 369 30 196617 + 18;
> #P newex 242 260 27 196617 int;
> #P newex 121 259 27 196617 int;
> #P newex 121 230 52 196617 maximum;
> #P newex 121 196 44 196617 +;
> #P newex 121 172 33 196617 zl len;
> #P newex 60 135 49 196617 buddy;
> #P newex 59 108 50 196617 zl slice 1;
> #P message 99 393 51 196617 offset $1;
> #P newex 532 43 45 196617 loadbang;
> #P newex 610 123 35 196617 int $2;
> #P newex 571 123 35 196617 int $1;
> #P newex 375 161 27 196617 t b i;
> #P newex 338 191 64 196617 &;
> #P newex 338 161 27 196617 << 8;
> #P message 242 392 264 196617 65 114 116 45 78 101 116 0 80 0 0 14  
> 0 0 0 $3 $1 $2;
> #N comlet write return (symbol);
> #P outlet 14 533 15 0;
> #P newex 264 124 269 196617 route clear reset subnet universe ip  
> channels tellmeotudp;
> #N comlet clear , reset , subnet , universe , ip , channels ,  
> tellmeotudp;
> #P inlet 264 29 15 0;
> #N comlet bang(stuurt dmx) , list(offset , data1 data2..);
> #P inlet 14 30 15 0;
> #P comment 337 339 199 196617 Art-Net0 (8) opcode (2inv) revisionnr 
> (2) seq(1) phys(1) universe(2) length(2);
> #P comment 423 296 100 196617 opcode niet inv;
> #P connect 2 0 29 0;
> #P connect 29 0 36 0;
> #P fasten 15 0 27 0 65 419 19 419;
> #P fasten 39 0 27 0 189 427 19 427;
> #P connect 36 0 27 0;
> #P fasten 35 0 27 0 516 435 19 435;
> #P fasten 6 0 27 0 247 431 19 431;
> #P fasten 13 0 27 0 104 423 19 423;
> #P connect 27 0 28 0;
> #P fasten 37 0 28 0 584 464 19 464;
> #P fasten 32 0 28 0 655 469 19 469;
> #P connect 28 0 30 0;
> #P connect 30 0 5 0;
> #P connect 29 1 14 0;
> #P connect 14 1 15 0;
> #P connect 30 1 31 0;
> #P connect 14 0 15 1;
> #P connect 15 1 21 0;
> #P connect 21 0 13 0;
> #P fasten 15 0 16 0 65 163 126 163;
> #P connect 16 0 17 0;
> #P connect 17 0 18 0;
> #P connect 18 0 19 0;
> #P fasten 15 1 17 1 104 158 160 158;
> #P fasten 22 0 18 1 306 215 168 215;
> #P fasten 19 0 18 1 126 282 178 282 178 221 168 221;
> #P fasten 20 0 38 0 247 288 189 288;
> #P connect 38 0 42 0;
> #P connect 42 0 40 0;
> #P connect 40 0 41 0;
> #P connect 41 0 39 0;
> #P connect 27 0 44 0;
> #P connect 44 0 43 0;
> #P fasten 36 1 20 0 38 102 247 102;
> #P connect 20 0 23 0;
> #P connect 23 0 33 0;
> #P connect 33 0 34 0;
> #P connect 34 0 6 0;
> #P fasten 18 0 20 1 126 253 264 253;
> #P connect 3 0 4 0;
> #P fasten 25 0 4 0 537 114 269 114;
> #P fasten 20 0 24 0 247 288 279 288;
> #P connect 24 0 33 1;
> #P connect 44 1 45 0;
> #P connect 4 1 22 0;
> #P fasten 8 0 33 2 343 319 311 319;
> #P fasten 4 5 22 1 454 155 323 155;
> #P connect 4 2 7 0;
> #P fasten 10 0 7 0 576 149 343 149;
> #P fasten 9 0 8 0 380 185 343 185;
> #P connect 7 0 8 0;
> #P connect 4 3 9 0;
> #P connect 9 1 8 1;
> #P fasten 11 0 8 1 615 184 397 184;
> #P fasten 34 1 35 0 264 382 516 382;
> #P connect 12 0 26 0;
> #P connect 26 0 25 0;
> #P connect 26 1 10 0;
> #P fasten 4 4 37 0 417 199 584 199;
> #P connect 26 2 11 0;
> #P fasten 4 6 32 0 491 164 655 164;
> #P pop;
>