From 86c89e24f57b63883775f932c0a2354b5fe4660c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?IOhannes=20m=20zm=C3=B6lnig?= Date: Fri, 13 Jun 2008 11:36:22 +0000 Subject: dmx4pd (currently linux only) svn path=/trunk/externals/iem/dmx512/; revision=9989 --- dmx512/README.txt | 4 ++++ 1 file changed, 4 insertions(+) create mode 100644 dmx512/README.txt (limited to 'dmx512/README.txt') diff --git a/dmx512/README.txt b/dmx512/README.txt new file mode 100644 index 0000000..96579bc --- /dev/null +++ b/dmx512/README.txt @@ -0,0 +1,4 @@ +DMX512 +====== + +controlling DMX from within Pd -- cgit v1.2.1 From 3d0ac4fc230dfdebd5dcc1eaab4a7ad222279193 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?IOhannes=20m=20zm=C3=B6lnig?= Date: Mon, 16 Jun 2008 10:24:42 +0000 Subject: [dmxout] now can be used to set entire ranges svn path=/trunk/externals/iem/dmx512/; revision=10009 --- dmx512/README.txt | 61 +++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 61 insertions(+) (limited to 'dmx512/README.txt') diff --git a/dmx512/README.txt b/dmx512/README.txt index 96579bc..7cb93f8 100644 --- a/dmx512/README.txt +++ b/dmx512/README.txt @@ -2,3 +2,64 @@ DMX512 ====== controlling DMX from within Pd + + + +A. setting up dmx4linux +======================= +note: there are debian(etch)-packages for dmx4linux, + but these seem to be pretty old (2.5) + i haven't really tried these. + instead i used dmx4linux-2.6.1 + +first get dmx4linux from http://llg.cubic.org/dmx4linux/ +and extract it. + +the drivers should compile fine with 2.6.18 kernels, but +alas! i am using 2.6.25 and there are some quirks to make +these work. + +first of all i had problems compiling the ISA/PCI/parport drivers, +but since i only wanted to use a USB device, i just disabled those. +second, dmx4linux's build-system tries to override CFLAGS when building +the kernel-modules, which newer kernel versions (e.g. 2.6.25) do not like +at all. i had to modify the makefiles in order to use the EXTRA_CFLAGS + +all the changes i did can be found in the dmx4linux2.6.1.patch +just run: +% patch -p1 < dmx4linux2.6.1.patch + +then do +% ./configure +(which will produce a /tmp/dmxconfig.mk) +and run +% make + +finally become root and do +# make install + + +load the appropriate kernel modules + + +B. permissions +the dmx device-files created by udev will be owned by root.root and not be +read/writeable by anyone but root. +in order to use them as an ordinary user, become root and create a group +"dmx" and add users who need access to the dmx-devices to this group: +# addgroup dmx +# adduser zmoelnig dmx + +in theory this should be enough to allow you access to your dmx devices +the next time you load a dmx-driver +if you have problems, try plugging your device out and in again + + + + + + + + + + -- cgit v1.2.1 From 2dd16c5ca5fe4ccfc995f23df1b752299108a488 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?IOhannes=20m=20zm=C3=B6lnig?= Date: Thu, 19 Jun 2008 13:14:39 +0000 Subject: updated readme.txt like vincent rioux suggested; fixed configure to also search for libdmx4l (which is the library installed by he upstream dmx4linux package) svn path=/trunk/externals/iem/dmx512/; revision=10044 --- dmx512/README.txt | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) (limited to 'dmx512/README.txt') diff --git a/dmx512/README.txt b/dmx512/README.txt index 7cb93f8..3eda9d8 100644 --- a/dmx512/README.txt +++ b/dmx512/README.txt @@ -38,11 +38,14 @@ and run finally become root and do # make install +after all has gone well, load the appropriate kernel modules -load the appropriate kernel modules + +btw, it is always a good idea to read the readme that comes with dmx4linux... B. permissions +============== the dmx device-files created by udev will be owned by root.root and not be read/writeable by anyone but root. in order to use them as an ordinary user, become root and create a group @@ -55,9 +58,26 @@ the next time you load a dmx-driver if you have problems, try plugging your device out and in again +C. compiling the Pd-objects +=========================== +so now it is time to get the Pd-objects going. +for this change into the "./src" directory of the iem/dmx512/ folder +(this might well be the folder that holds this README.txt you are currently +reading) + +if you have obtained the source-code via subversion, you will first have to run +% autoconf +(this should not be needed if you downloaded the sources as a release tarball; +that is: if the person who created the tarball has not forgotten to do it for you) + +then run +% configure +% make +you should now have 2 binary files in the src/ folder called [dmxin] and [dmxout] +go on and use em! -- cgit v1.2.1 From caaefca7ebe5a15d99f358b68dd84a7ad47bd317 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?IOhannes=20m=20zm=C3=B6lnig?= Date: Mon, 30 Jun 2008 10:45:57 +0000 Subject: ... svn path=/trunk/externals/iem/dmx512/; revision=10117 --- dmx512/README.txt | 3 +++ 1 file changed, 3 insertions(+) (limited to 'dmx512/README.txt') diff --git a/dmx512/README.txt b/dmx512/README.txt index 3eda9d8..346934e 100644 --- a/dmx512/README.txt +++ b/dmx512/README.txt @@ -57,6 +57,9 @@ in theory this should be enough to allow you access to your dmx devices the next time you load a dmx-driver if you have problems, try plugging your device out and in again +if you don't care for a clean setup, you could also just grant everyone read/write permissions. +this might be a security risk. + C. compiling the Pd-objects =========================== -- cgit v1.2.1 From 0743593e7adec852e293e5e42d851256c225cd74 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?IOhannes=20m=20zm=C3=B6lnig?= Date: Mon, 30 Jun 2008 11:01:03 +0000 Subject: split the readme into several files svn path=/trunk/externals/iem/dmx512/; revision=10118 --- dmx512/README.txt | 82 ++++++++++++++----------------------------------------- 1 file changed, 21 insertions(+), 61 deletions(-) (limited to 'dmx512/README.txt') diff --git a/dmx512/README.txt b/dmx512/README.txt index 346934e..327c744 100644 --- a/dmx512/README.txt +++ b/dmx512/README.txt @@ -3,68 +3,13 @@ DMX512 controlling DMX from within Pd +this readme assumes that you have a running dmx4linux setup. +if not, read the README.dmx4linux.txt file for hints on how to +get it going... - -A. setting up dmx4linux -======================= -note: there are debian(etch)-packages for dmx4linux, - but these seem to be pretty old (2.5) - i haven't really tried these. - instead i used dmx4linux-2.6.1 - -first get dmx4linux from http://llg.cubic.org/dmx4linux/ -and extract it. - -the drivers should compile fine with 2.6.18 kernels, but -alas! i am using 2.6.25 and there are some quirks to make -these work. - -first of all i had problems compiling the ISA/PCI/parport drivers, -but since i only wanted to use a USB device, i just disabled those. -second, dmx4linux's build-system tries to override CFLAGS when building -the kernel-modules, which newer kernel versions (e.g. 2.6.25) do not like -at all. i had to modify the makefiles in order to use the EXTRA_CFLAGS - -all the changes i did can be found in the dmx4linux2.6.1.patch -just run: -% patch -p1 < dmx4linux2.6.1.patch - -then do -% ./configure -(which will produce a /tmp/dmxconfig.mk) -and run -% make - -finally become root and do -# make install - -after all has gone well, load the appropriate kernel modules - - -btw, it is always a good idea to read the readme that comes with dmx4linux... - - -B. permissions -============== -the dmx device-files created by udev will be owned by root.root and not be -read/writeable by anyone but root. -in order to use them as an ordinary user, become root and create a group -"dmx" and add users who need access to the dmx-devices to this group: -# addgroup dmx -# adduser zmoelnig dmx - -in theory this should be enough to allow you access to your dmx devices -the next time you load a dmx-driver -if you have problems, try plugging your device out and in again - -if you don't care for a clean setup, you could also just grant everyone read/write permissions. -this might be a security risk. - - -C. compiling the Pd-objects +A. compiling the Pd-objects =========================== -so now it is time to get the Pd-objects going. -for this change into the "./src" directory of the iem/dmx512/ folder +for this, change into the "./src" directory of the iem/dmx512/ folder (this might well be the folder that holds this README.txt you are currently reading) @@ -80,9 +25,24 @@ then run you should now have 2 binary files in the src/ folder called [dmxin] and [dmxout] -go on and use em! +B. Installation +=============== +you should install the binaries (+helpfiles) somewhere Pd can find them. +i would suggest to put them into + /extra/dmx512/ +and add this path to the startup-flags of Pd. + + +C. Usage +======== +there should be help-files in the ./help directory +if not, the useage should be very similar to that of [ctlin] and [ctlout] +(it's just using DMX512 instead of MIDI) +D. Help! +======== +read the FAQ -- cgit v1.2.1