mavericks

pour whitecat ou :Light, le masque à toujours été 255.255.255.0
donc les 2 sont possibles?

le masque 255.255.255.0 fonctionne si ton IP est du style 192.168.x.x
pour les IP en 10.x.x.x ou 2.x.x.x, le seul masque possible est 255.0.0.0
étant donné que la norme ArtNet définie ces deux dernières adresses et uniquement celles là, il vaut mieux régler les cartes réseaux de la sorte.
maintenant, les adresses 192.168.x.x fonctionnent aussi, mais je pense que c'est pas bien de les laisser comme ça.

++

la 3.0.17_b7 est en ligne et doit fonctionner correctement sur le nouvel OS.
à tester.

++

@nico

Là je comprends plus rien.

Mon ODE fonctionne parfaitement avec l'adresse 10.20.24.20 et un masque en 255.255.255.0.

Qu'en déduire ?

ben ouais c'est bizarre.
fr.wikipedia.org/wiki/Classe_d'adresse_IP

ce site nous dit bien que 10.x.x.x c'est de la classe A et que le masque de sous-réseau qui peut s'appliquer c'est 255.0.0.0

:huh:

merci pour le lien, super j'ai enfin compris

On my spare laptop I uninstalled the FTDI-drivers so DLight would not ask for a password.

After upgrading to Mavericks and using 3.0.17_b7 I get this problem:

1. When choosing the USB DMX libusbx I get the osascript password prompt when switching on USB.
2. After typing in my password the USBDMX stays off.
3. When trying to switch on the USBDMX (pressing the red LED) I get the prompt again.
4. After typing in my password the USBDMX stays off.

I can repeat steps 2 > 4 ad infinitum.

The hardware I am using is an ENTTEC DMX USB PRO Mk2.

I read that the FTDI drivers are back in Mavericks and I removed them again but this does not help.
Remove I did (sudo):

in /usr/local/lib:

rm libftd2xx.dylib
rm libftd2xx.1.0.0.dylib
rm libftd2xx.1.0.2.dylib
rm libftd2xx.1.0.4.dylib

Tried to remove (but did not exist):

in /System/Library/Extensions:

rm -r FTDIUSBSerialDriver.kext

in /Library/Receipts:

rm -r TDIUSBSerialDriver.kext


[edit]
Same problem with 3.0.14 and 3.0.17_b6 so it is a problem with Mavericks and FTDI, not the newest beta of DL.
Do people here have the same problem and maybe a solution?
[/edit]

@Wilf
first, please read this, found on the web on the enttec website:
www.enttec.com/support-center/kb/article...s_(10.9)_-_IMPORTANT

for me, with maverick and the latest beta:
I re-install the ftdi drivers
apparently this has removed the AppleUSBFTDI.kext on my mac because I can't find this kext
usb MK2 works fine...

do you have this kext on your computer?
++

At this moment my version of Dlight refuses to listen to OSC after updating to Mavericks. Sending is OK.
Is this a known problem?

Best
Peter

@Wilf
I previously made the tests with dmxKing.com
I've tested with the MK2 and it fails.

but, I've a workaround...

in the file called DLight.tcl, find a function called ExeUL

and change it to looks like this:
tell me if it works.

++

@Peter,
I've just checked on maverick with the touchOSC layout on the Samsung SGS2 and listen/send is ok here.
at least with the latest beta.

++

@wilf
I've removed previously installed FTDI driver, reboot and tried the trick.
it works here.

++

The extra line of code to unload the Apple FTDI did the trick here too. Superbe!

Yes indeed. Sending and receiving OSC is fine again here too! Probably a reboot did the trick.
Thanks for the fast response.

Best
Peter

new testing phase with 3.0.17_b10

++