Difference between revisions of "Windows XP + e:cue"
Jump to navigation
Jump to search
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | + | This applies to Windows 7 and MXWendler version 4.2 and above | |
| − | ''Problem | + | '''Problem''' |
| − | |||
| − | + | If you use e:cue programmer 5.2 ( and possibly other versions ) to send dmx data to MXWendler, some values drop to 0.0 every two seconds, or stay at 0.0 for two seconds and jump to the desired value for a short time. | |
| − | |||
| − | ''Solution/Workaround | + | '''Reason''' |
| − | + | ||
| − | + | e:cue sends wrong values. | |
| + | |||
| + | '''Solution/Workaround''' | ||
| + | |||
| + | e:cue supports sending up to 4 universes. <br> | ||
| + | If you use different universes, the problem appears, if you use the same universe 4 times the problem disappears. | ||
Latest revision as of 14:25, 1 October 2019
This applies to Windows 7 and MXWendler version 4.2 and above
Problem
If you use e:cue programmer 5.2 ( and possibly other versions ) to send dmx data to MXWendler, some values drop to 0.0 every two seconds, or stay at 0.0 for two seconds and jump to the desired value for a short time.
Reason
e:cue sends wrong values.
Solution/Workaround
e:cue supports sending up to 4 universes.
If you use different universes, the problem appears, if you use the same universe 4 times the problem disappears.