Jump to content
Vari-Lite Controls Support Forum

jw-lighting

Regulars
  • Posts

    85
  • Joined

  • Last visited

About jw-lighting

  • Birthday 08/24/1993

Recent Profile Visitors

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

jw-lighting's Achievements

Enthusiast

Enthusiast (6/14)

  • First Post
  • Collaborator
  • Week One Done
  • One Month Later
  • One Year In

Recent Badges

0

Reputation

  1. Hi, I've tried and succeeded to connect our FLX to a ENTTEC Datagate MK2 yesterday. However, if I disconnect the FLX from the network switch (physically) to test how the whole system performs in case of errors, I noticed that I have to restart the FLX to get the sACN working again. I'm not sure if it's a bug, but is there any possibility to get sACN (havn't tested Art-Net) working after a network reconnect automatically? When I disconnect and reconnect the Datagate from the network switch while the FLX stays connected to the switch, everything is working correctly after the reconnect of the Datagate. Hence the problem is not at the Datagate, isn't it? Regards, Jan
  2. I almost expected this, however i wanted to give you that hint. Maybe you have a chance to get a used one (or a LeapFrog).
  3. Hi Klaus, the five fixtures spare could hardly be enough if you're planning to add moving lights in the future. On the other side, you're not using the 24 dimmer channels from the Jester ML24. For that reason have a look on the Solution as well. Here you're able to control your LED fixtures like generic dimmers with additional colour parameters. additionally you're not as limited in the number of fixtures as you are with the JesterML. Redards Jan PS: Du kannst hier auch auf Deutsch schreiben, wenn es dir leichter fällt. // You could write german as well if it's easier for you.
  4. Thanks OllieB for your post! I'd like to add another tought to it: Why don't let the users do the calibration for the fixtures they use, and provide a simple possibility to give it back to the community, improving the library? This way Zero88's staff a) do not have to calibrate every fixture, even those that are never or seldom used have a lower workload.
  5. I'm sorry, I hadn't the time to read through it, so I had just taken a short look into the paper. What you'd like to say is that the differences with amber are bigger than those with red, green and blue? It would be very interesting how other console manufactures solved the problem, because there are a few with support for amber (or even more colours) in the picker. One more question on my list for the PLS fair in Frankfurt
  6. Hi Jon, thanks for your answer. My impression is, you're approaching a very perfect solution. I really like people seeking for the perfect solution... But maybe you're making things too difficult for yourself: RGBA/RGBAW only applies for LED fixtures, doesn't it? All discharge lamps are combined with subtractive colour mixing (CMY). Supporting RGB fixtures you currently have the same problems: What frequency does the red/green/blue LED emitter have? How long are they in use? Are there any differences in colour between the different fixture types or batches from the same fixture? Why don't you try to implement RGBA/RGBAW with approximated amber wavelength (average frequency from popular LED emitter datasheets: Osram, Luxeon, Seoul, ...)? You could improve it later, if possible
  7. Hi Jon, I knew that a few other consoles on the market (different manufacturer) are able to "translate" RGB values from the picker (or those related to a color from LEE, Rosco, etc) to RGBA, RGBW, RGBAW or even ETC's color mixing with seven different LED emitters. Do you have a feature like this on the roadmap?
  8. Thanks Jon, that's perfect
  9. Related to this: When I load my old showfile after the update or reset, are fixture profiles used in my show (not part of the standard library) restored with it or is it necessary to do this manually before loading the old show?
  10. Hi Kevin, I have the same problems and experience with the effect engine, your reply is very helpful, because I havn't got the time to work through the manual and the tips here and try everything out. Now I could assume that it is not my fault. Yes - and I hope it does not took ages. But I knew it's not a simple task and should be done carefully. Jan
  11. Thanks for your response, Jon. I was afraid my post could have annoyed you - now I'm glad it hasn't. I've written a lot about this, maybe it was to much for somebody to read and participate. To be honest I hadn't the impression you (and the zero88 team) has realized that there is strong need to rework the effect engine before your reply. Therefore this are very good news. I'm looking forward to get a more detailed impression on your vision. You have an abstract of my wishes and ideas in my post above. Of course I could write even more, but in my opinion this doesn't make much sense. Suggestion: you try to get some mockups for us or you could mail me an alpha release of it (so I can try how it feels "live") and then we give you our opinion, ideas and improvements. Is this OK for you?
  12. Hello everybody! by reading the forum from time to time, I got the impression that a couple of users are not familiar or 100% satisfied with the effect engine of zerOS. Maybe I'm wrong with my impression (let me know), but I would like to take this occasion to talk with the other FLX users (or other zerOS-consoles) about possible improvements. The current effect engine has a scientific approach in the sense of how it works. Mainly it is based on mathematical functions to chance fixture parameters. This makes it flexible and powerful. On the other hand, this seems to be less user-friendly and intuitive than the effect engines of zero88's competitors. In my opinion, an effect engine has to give the designer or operator a very easy and effective way to select and configure often used effects. E.g. a rainbow, moving a couple of fixtures in a wave, or a fly in / out. Let me use this examples to show what I mean: Rainbow: The build in rainbow effect-palette does not include the primary colours red, green and blue alone. There are only mixed colors with at least two primary colors active. This is caused by the underlaying waveforms. From the designers point of view a rainbow should go like this: From red to yellow, than reducing the red part going to green, than keeping green on and increasing blue going to cyan and so on. It's very hard (if not impossible) do to exactly this with the currently used waveform-based effects. Moving fixtures in a wave: Select a couple of fixtures, apply a sine effect to tilt and wonder: All fixtures are moving equal. Where is the sinewave? Hidden by an zero-offset. This could be easily fixed (and is no problem at all for experienced users) by applying an offset using Shift+<Wheel>. Imagine the selected fixtures are part of a truss-circle - so we would like that the first fixture exactly follows the last one to get a closed, stepless wave. I found it very hard to find the correct offset value in such cases. Sometimes, I used half an hour for that before I finally give up... Fly in/out: In this case, we have to sync different attributes and have to care about the moving speed of the fixture: First the fixture has to go to the top tilt value with zero intensity. Than we should wait a moment so that the fixture can perform the movement (this is important!). Now we can open the shutter and move to bottom, close the shutter at bottom and repeat. Synchronisation between the waveforms for the different attributes is hard to reach. Wait between steps to let the fixture move is not possible. Possible improvements: Use intuitive units for effect parameters: Speed in BPM or Hz, Offset in degree, Size in %. There are no units at all currently. Thus it's hard to get an understanding of what the effect engine is doing. Implement a function to automatically spread the offset between all selected or a specific # of fixtures More improvements could be made if the approach is changed: Don't limit effects to waveforms: E.g. self (or build-in) step patterns could fasten the programming of chasers. Develop new creative approaches for creating effects. Think from the designers point of view (often this couldn't be done by programmers) Provide build-in effects not only as palettes, but also as a quick solution for often needed exercises: Fly in, Fly out, Rainbow - all those effects where it is not possible to do them perfectly with waveforms, because parameters are depending on each other and so on. Those effects should be configurable with different parameters - depending on which parameters it could be possible worth for the designer to have influence on I hope you understand this post as constructive criticism - this is my intention. All in all I'm glad to use the FLX. Especially I really appreciate that you are interested in your users needs. This is why I wrote this - hoping to initiate a step in the FLX's way to be the perfect lighting console. It's not in my nature to write long (and complicated) texts in english language. I hope you could easily understand my intention and that Google Translator hasn't fooled me. At last I'd like to invite every user to participate at this discussion. Best regards Jan
  13. As far as i know, MagicQ supports all popular operating systems. It's available for mac here https://secure.chamsys.co.uk/download Just to be mentioned: all zero88 desks support saving shows to and loading shows from USB, and a offline software for PC is also available.
  14. Hi Jon, do you intend to include pixel mapping within the first zerOS 8 release or is it lower priority and therefore included in a later release?
  15. jw-lighting

    Udks

    Hmmm. Now, I'm not sure at all if there is a Solo option for the UDKs. The playbacks have one. As a workaround you could use a playback instead.
×
×
  • 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.