Allez. (English follows)
Disponible ici: https://piobee.com/relink/
Ce patch n'a pas été créé par l'équipe qui développe TheLightingController, mais il a été testé rigoureusement avant de le publier.
Available here: https://piobee.com/relink/
Disclaimer: Unofficial firmware patch; but fixes connectivity issues with newer PCs flawlessly. Thouroughly tested before sending it out.
See next post for English version...
Qu'est ce que ça concerne? Les problemes de communication entre le port USB des Sweetlight Box et les nouveaux Controlleurs USB sur les PC.
Quels appareils sont touchés? Principalement SweetLight Standalone (SSA), Chauvet XpressPlus (meme chose que SSA), SweetLight
Problème Matériel? vraiment? Non. Ou.. Plutôtt oui et non vieux bogue firmware, anciennement sans conséquence, ressort maintenant.
Pourquoi le problème, à l'origine? Pour simplifier le Firmware/micrologiciel était livré avec un défaut sur le micrologiciel des BOX et SSA envoyant des paquets DMX vides, (de longueur 0) à l'ordinateur quand nous n'utilisez pas l'entrée DMX sur l'appareil. Ces paquets causent une désynchronisation entre le port USB du PC et l'appareil DMX. Anciennement, les vieux ports "lents" avait le temps de se recynchoniser malgré un paquet en erreur, mais les controlleurs modernes ne savent plus traiter ces paquets vides. C'est ce qui cause les glitchs au final.
Contexte: Je travaille en événementiel, et propriétaire de beaucoup d'appareils Chauvet et Sweetlight, j'était attristé par la fin du support de ces machines qui ont encore une durée de vie utile, quand j'ai lu sur le Forum. Par contre, étant aussi développeur un peu fou, (et surtout en voyant le coût de remplacement de tous mes appareil) je savais que l'explication ne tien pas la route: Windows identifie correctement la puce; pas de reconnexion répétées; le data passe. Juste des glitchs, et pas sur tous les ordinateurs: c'est une question logicielle. Ce patch est le résultat de plusieurs mois d'effort et d'obsession pour conserver ces appareils en vie,
Tout mes respects à M. Eric Fock-Hamelin qui (si je ne me trompe pas) avait développé ce projet. (...et a même signé son nom, bien caché dans le code) Et toutes mes félicitations pour avoir maintenu le support aussi longtemps.
Mais aujourd'hui j'ai l'honneur de vous dire que vous aviez tord; et je vais continuer à utiliser mes SSA et à me procurer aussi les nouveaux modèles
P.S. Je sort un patch pour le problème d'upload pour le SSA standalone dans les prochains jours compatible avec V9.4.5 et 9.4.7, mais s'il vous plait, prenez le 5 minutes que ça prend pour faire le correctif. Je peux même vous dire c'est où...
Merci
FIRMWARE Patch Available / disponible BOX et SSA
Re: FIRMWARE Patch Available / disponible BOX et SSA
Disponible ici: https://piobee.com/relink/
Ce patch n'a pas été créé par l'équipe qui développe TheLightingController, mais il a été testé rigoureusement avant de le publier.
Available here: https://piobee.com/relink/
Disclaimer: Unofficial firmware patch; but fixes connectivity issues with newer PCs flawlessly. Thouroughly tested before sending it out.
See next post for English version...
**What is this about?** Communication issues between the USB ports on SweetLight boxes and modern USB controllers found in newer PCs.
**Which devices are affected?** Mainly SweetLight Standalone (SSA), Chauvet XpressPlus (essentially the same as SSA), and SweetLight devices.
**A hardware problem? Really?** No. Well... Actually, yes and no. It's an old firmware bug that used to be harmless but has now resurfaced.
**What originally caused the problem?**
To put it simply, the firmware shipped with the BOX and SSA devices had a flaw that caused them to send empty DMX packets (zero-length packets) to the computer whenever the DMX input on the device wasn't being used.
These packets cause synchronization issues between the PC's USB port and the DMX device.
Back in the day, older, slower USB controllers had enough time to resynchronize despite receiving an invalid packet. Modern USB controllers, however, can no longer properly handle these empty packets. This is ultimately what causes the glitches.
**Background:**
I work in the event production industry and own quite a few Chauvet and SweetLight devices. I was disappointed to read on the forum that support for these devices had ended, especially since they still have plenty of useful life left in them.
However, being a somewhat crazy developer myself (and especially after seeing how much replacing all my equipment would cost), I knew the explanation didn't add up.
Windows correctly identifies the chip. There are no repeated disconnections or reconnections. Data is being transmitted. Just glitches, and not even on every computer.
That pointed to a software issue.
This patch is the result of several months of effort and obsession with keeping these devices alive.
I have the utmost respect for Mr. Eric Fock-Hamelin, who (if I'm not mistaken) originally developed this project (...and even left his signature well hidden in the code
). I also want to congratulate him on having maintained support for these devices for so many years.
But today, I have the honor of telling you that you were wrong. And I intend to keep using my SSA devices while continuing to purchase the newer models as well.
**P.S.** I'll be releasing another patch in the next few days to address the scenes upload issue on SSA Standalone devices, compatible with versions 9.4.5 and 9.4.7.
But please, take the five minutes it takes to implement the fix yourselves. I can even tell you exactly where to look in the code...
Thank you!
Ce patch n'a pas été créé par l'équipe qui développe TheLightingController, mais il a été testé rigoureusement avant de le publier.
Available here: https://piobee.com/relink/
Disclaimer: Unofficial firmware patch; but fixes connectivity issues with newer PCs flawlessly. Thouroughly tested before sending it out.
See next post for English version...
**What is this about?** Communication issues between the USB ports on SweetLight boxes and modern USB controllers found in newer PCs.
**Which devices are affected?** Mainly SweetLight Standalone (SSA), Chauvet XpressPlus (essentially the same as SSA), and SweetLight devices.
**A hardware problem? Really?** No. Well... Actually, yes and no. It's an old firmware bug that used to be harmless but has now resurfaced.
**What originally caused the problem?**
To put it simply, the firmware shipped with the BOX and SSA devices had a flaw that caused them to send empty DMX packets (zero-length packets) to the computer whenever the DMX input on the device wasn't being used.
These packets cause synchronization issues between the PC's USB port and the DMX device.
Back in the day, older, slower USB controllers had enough time to resynchronize despite receiving an invalid packet. Modern USB controllers, however, can no longer properly handle these empty packets. This is ultimately what causes the glitches.
**Background:**
I work in the event production industry and own quite a few Chauvet and SweetLight devices. I was disappointed to read on the forum that support for these devices had ended, especially since they still have plenty of useful life left in them.
However, being a somewhat crazy developer myself (and especially after seeing how much replacing all my equipment would cost), I knew the explanation didn't add up.
Windows correctly identifies the chip. There are no repeated disconnections or reconnections. Data is being transmitted. Just glitches, and not even on every computer.
That pointed to a software issue.
This patch is the result of several months of effort and obsession with keeping these devices alive.
I have the utmost respect for Mr. Eric Fock-Hamelin, who (if I'm not mistaken) originally developed this project (...and even left his signature well hidden in the code
But today, I have the honor of telling you that you were wrong. And I intend to keep using my SSA devices while continuing to purchase the newer models as well.
**P.S.** I'll be releasing another patch in the next few days to address the scenes upload issue on SSA Standalone devices, compatible with versions 9.4.5 and 9.4.7.
But please, take the five minutes it takes to implement the fix yourselves. I can even tell you exactly where to look in the code...
Thank you!