Sean Meighan
Welcome => Do You Need Help? Post it here => Topic started by: Chris A on January 19, 2016, 05:27:32 PM
-
I know this is something I'm missing.
I have my matrix set up as a model. No matter what effect I place in the sequencer, the matrix just shows up as all white. The matrix shows up when it is supposed to, but it's all white. What simple mistake am I making?
Thanks, Chris
-
Check Dimming Curve - should be 0s versus blank (or remove from xml completely).
http://nutcracker123.com/forum/index.php?topic=2451.msg15069#msg15069 (http://nutcracker123.com/forum/index.php?topic=2451.msg15069#msg15069)
-
I checked my xml and it was incorrect. I changed them to 0 and I still see all white. I really thought that was the problem. I have attached my xml file. Thanks for the help.
Check Dimming Curve - should be 0s versus blank (or remove from xml completely).
http://nutcracker123.com/forum/index.php?topic=2451.msg15069#msg15069 (http://nutcracker123.com/forum/index.php?topic=2451.msg15069#msg15069)
-
your dimming curve for your p10 model has R,G,B Gamma's set to 0.0.
Why?
Normal is 1.0
As soon as i changed the dimming values to 1.0 and dropped a butterfly on to your model, it displayed correctly
-
your dimming curve for your p10 model has R,G,B Gamma's set to 0.0.
Why?
Normal is 1.0
As soon as i changed the dimming values to 1.0 and dropped a butterfly on to your model, it displayed correctly
Because he was told to 2 posts ago.
I recommend this thread be updated so it won't cause confusion for somebody else.
James
Sent from my SM-G900V using Tapatalk
-
James is correct I was following the advice from another post referenced above. I'm not sure how the dimming value changed to begin with because I wouldn't have messed with it, since I don't know what it is and how it affects my model.
It is working now. Thanks everybody.
your dimming curve for your p10 model has R,G,B Gamma's set to 0.0.
Why?
Normal is 1.0
As soon as i changed the dimming values to 1.0 and dropped a butterfly on to your model, it displayed correctly
-
Ok, I see. The post that was referenced was talking about brightness and gamma being blank and to restore them to original values they need to be zero and one. Mararunr only picked "blank" goes to a zero, where the complete answer is default brightness is zero, default gamma is 1.0.
(Referenced link:)
<dimmingCurve>
<red brightness="" gamma=""/>
<green brightness="" gamma=""/>
<blue brightness="0" gamma=""/>
</dimmingCurve>
Whereas this is what it should look like by default:
<dimmingCurve>
<red brightness="0" gamma="1.0"/>
<green brightness="0" gamma="1.0"/>
<blue brightness="0" gamma="1.0"/>
</dimmingCurve>
I didn't need to edit the xlights_rgbeffects.xml file to fix your issue, I went into your P10 model and clicked dimming curve and put in 1.0 on gamma. For all my models (I have 80), I never touched the dimming curves on them. Dimming curves can fine tune your display elements.
Sorry for the confusion
-
Yeah I believe the problem is a user clicks the dimming curve button out of curiosity but doesn't actually change the values and it causes it to create invalid values in the xml file. I mentioned it to Dan and I believe he was adding a check on those values but not sure if it got done or maybe its done but just not in a new release. We need to double check it.
-
....Mararunr only picked "blank" goes to a zero, where the complete answer is default brightness is zero, default gamma is 1.0. ....
Sorry for the confusion
And my apologies for adding to the confusion. Was only trying to help. Glad to see Gil's post where maybe it will get checked in a future release. For me, I have gone back to version 4.2.24 for now (the one I used for this past season).
-
That's exactly what I did. See you in Vegas. Come on March.
I didn't need to edit the xlights_rgbeffects.xml file to fix your issue, I went into your P10 model and clicked dimming curve and put in 1.0 on gamma. For all my models (I have 80), I never touched the dimming curves on them. Dimming curves can fine tune your display elements.
Sorry for the confusion
-
....Mararunr only picked "blank" goes to a zero, where the complete answer is default brightness is zero, default gamma is 1.0. ....
Sorry for the confusion
And my apologies for adding to the confusion. Was only trying to help. Glad to see Gil's post where maybe it will get checked in a future release. For me, I have gone back to version 4.2.24 for now (the one I used for this past season).
Why would you go backwards? Dimming curves were added way before that version and there's been nothing but improvements and bug fixes since then.
-
Why would you go backwards? Dimming curves were added way before that version and there's been nothing but improvements and bug fixes since then.
Because it works without issues for me. I put together a new 3x3 P10 matrix in the lab/garage and had issues with the newest version (similar to this thread and others). Spent two hours thinking it was wiring on my part, then thought about reverting to the previous version I used during the season and voila, it worked fine. I have since read about the gamma/dimming and have not gone back to try again.
It's not affront to the hard work that you all do, it's just what worked for me. It's a suggestion to try something different when there's a problem. It was much easier to try a previous version than the 2 hours of wiring and rewiring trying to find the hardware problem.
Just my opinion.
Hopefully this weekend and I go back and try the whole dimming/gamma thing and see if I can use a new version.
-
In all likelihood going backwards wasn't what really fixed the problem. I really don't want anyone thinking they should install an older version that just causes more problems for us.
-
Everyone should also be aware that going backwards and then forwards can also have unintended side effects. Sometimes we add code to detect older versions of files to make adjustments to an effect. We don't normally have code in there to handle a newer version of a sequence being opened in an older version of xLights. I'd have to test I'm not sure what we do with the version number. If you open a newer sequence in an older version and hit save does it end up with the older version number in the header? If so then that would cause any effect adjustment code we've added to run twice. Many times when we make changes to effects we have code in there that detects older sequences and then runs a conversion to adjust the effect to the new changes. If you jump around versions I'm afraid you may get those adjustments multiple times.
-
Thanks for the advice Gil.
Sent from my SM-G900V using Tapatalk
-
It does give me the idea we might want to block opening a newer version sequence in an older version of xlights.
-
Gil does bring up a good point. I wrote the original code many years ago that converts old xml to current. Now if u use a new release can u just go back a version? Yes , mist of the time. Here is the issue, say picture effect gets a x, y slider added. We need to add new xml tags for that. What happens if that new picture effect gets opened by an old version, sliders are ignored. Most releases do NOT change the xml structure so u are safe opening your current xml with old xl 4 versions. The farther back u go the mire likely u will have an issue. U cannot open xl4 sequences in xl3, xml files are totally different. So going back a few versions mostly will work but we dont test it and do not spend any effort making current xml work in older versions. Just a heads up
Sent from my iPhone using Tapatalk
-
Just make sure you backup your files first if going backwards. There are times when it's nice for us to know if going backwards fixes something. I hope we've gotten better about new versions not breaking things as much as before but that might regress once we start introducing new versions this year since we are dramatically rearranging a lot of things. There has been a lot of work done that is mostly transparent to the user but it putting us in a better position to add more effects in the future with better organization in our code and making it easier for new developers to join in and add effects.
I agree with not upgrading versions when it gets close to December. But its January back up the files and take the plunge. :)