Jump to content
Vari-Lite Controls Support Forum

droiddk

Regulars
  • Posts

    35
  • Joined

  • Last visited

  • Days Won

    2

droiddk last won the day on October 12 2022

droiddk had the most liked content!

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

droiddk's Achievements

Explorer

Explorer (4/14)

  • One Year In
  • One Month Later
  • Reacting Well Rare
  • Week One Done
  • Dedicated Rare

Recent Badges

10

Reputation

  1. @Erics & @Davidmk Thank you for your input. I think I got it, roughly Kind Regards
  2. Hi Erics Thank you for your reply. What I do know is that, when working with linear movement it’s easy to do the calculation with 16bit, like this: coarse value = 65.536 / 256 and fine value = 65.536 % 256 and that is working fine, using 16 bit combining two channels. It also works well because when the movement is linear there will also be one full fine movement (0-255) before coarse increments with 1. For doing movement its better (one reason is the weight of the lamp) to use a sine-wave to generate the movement values, instead of linear-movement (sawtooth) so I use sine and cosine to calculate values from -1 to 1 (using degree 0-360) and calculate the DMX by this: dmxvalue = (sine * 127) + 127 and that is giving me a fine sine-curve, expressed in DMX -values ranging from 0-255. So, I can do the movement (using sine and cosine) for the coarse channel, but I would like to use the fine channel also, so I can get smooth movements even at low speeds. My problem is that sometimes the coarse DMX -values are like this: 128, 128, 129, 129, 130 with the same DMX -value in a row and the means no fine-movements between those values. Not sure if I’m on the right approach here? I'm still in the early days here, but when thinking about it, I don't think the "fine" should have the form as a sine-wave, I mean, the "fine" will (if using sine) go very, very, fast, both up and down, and that will mess things up if the "coarse" is still going "up". I guess the correct is that the "fine" will always have the sawtooth-shape -> sawtooth from zero to max when coarse is going up, and sawtooth from max to zero when coarse is going down. Does that makes sense? How will you do the math/programming when calculating coarse and fine DMX-values for at sine/cosine movement? Kind Regards
  3. Hi 😊 I know this may be (a lot) off-topic, not related to Zero 88, but I guess the coolest lightning-guys visits this forum so I give it a try, I hope it is ok with Zero 88. I’m a hobby programmer and at the moment I’m working on a small Java DMX-controller, a lot of fun in that. At the moment I’m working on the movement-generator but I could need some advice on how to do the 16bit movement. I think I know how to do it with 8bit but it gets a little bit more complicated when using 16bit (two channels) and doing non-linear movement (like using sine/cosine). So: Any programmers out there, maybe with some DMX-programming experience that would like to get in contact with me? I imagine some kind of mail-contact. I would love to a have an expert to ask a few questions, not related to Java, but how to approach (maybe specifically the math-part) the general concepts. I will show my ideas and progress so far and tell where I’m stuck. Kind Regards droiddk
  4. Hurraaaa. Down for...1 month...? Glad it is back! Kind Regards
  5. Hi @Edward Z88 Done I really like the new improved graphics in Phantom ZerOS. Kind Regards
  6. Hi Not directly related to ZerOs but any chance you could improve the image quality in ZerOS Monitor (Windows)? Its pixelated 😕 Kind Regards
  7. Looks palettes (on separate slide/fane) would be great!! Regards
  8. Remove option is in the update window. Regards
  9. I've just tested and also crash here. Regards
  10. Hi Sent you a PM. Regards
  11. Hi DMX-chart confirms what Edward said, DMX value 255 = "close" (from manual)/ dimmer at zero so desk is working as it should. Regards
  12. Hi @Edward Z88 Wow, I would LOVE that! Fantastic! Regards droiddk
  13. I now have the FLX S in daily use and I have to say that this is something that is very important to me. Speed and size on the same fader simply wont work for me. Please remove size I also work as sound-guy and when doing both it would be so nice to control the speed with the fader. Please. Regards
  14. Hi @Edward Z88 Thank you. Now I know that I am not doing anything wrong, its working as intended Have a nice weekend. Kind Regards droiddk
  15. Hi all Still playing with Phantom Jester before putting the console in use at a small job. I have the Jester 24/48, Jester ML24 & Jester TL. I will be using a few movers so the job will be done using ML24 or TL. Both consoles are great. I will probably use the TL since it is the smallest, but I have a question: Programming a simple chase, let’s say 4 steps with 1 dimmer channel going from 25%->50%->75%->100%. Works fine. Now I want to use that chase as a kind of cue-stack so back to program, press edit and sets the Chase Speed to manual, pressing edit to save. Back to run, on the ML I raise the Submaster (first step is outputting) and when button option is set to “Step/Go” I can press the button and the next step is outputting. Now exactly the same thing on the TL: There is no fader so I just try hitting the MFK but nothing happens. Overall, I guess my findings makes sense: That Go/Step (with manual chase) is only working on submasters with faders (the chase will start first step when fader is raised above 5%?) I am a little bit confused since this is in the manual (P28): “To advance a manual chase on a submaster, set the Flash Mode to Go/Step (using the Multi-Function-Keys when SPECIAL is active), select SUBMASTERS and use the Multi-Function-Keys (or use the submaster flash button on the JesterTLXtra)” Maybe I am just reading the manual wrong? Kind Regards droiddk By what way: Jester TL, what does TL stands for? In ML it stands for “Moving Lights”, yes?
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.