Replies: 5 comments 3 replies
-
I didn't know if this was possible or whether it would cause issues. A lot of things depend on knowing the mapped channels. |
Beta Was this translation helpful? Give feedback.
-
Are you assigning channels manually or using the visualizer? What controllers do you have? Channels are only assigned at the model level, not groups or submodels. |
Beta Was this translation helpful? Give feedback.
-
They are just a subset of the model, but doesn't really matter since a submodel can have (and does) gaps in nodes, thus those channels are irrelevant. |
Beta Was this translation helpful? Give feedback.
-
Okay so I had this last year. Now I've updated my Mac as many of you know to an M4 24gb but still had quite a lag doing stuff in my layout. Still took forever to import a prop. So I stuck with making all changes in a test folder and then importing into main layout. So I don't know if it's attached to the recent update to detach layout from model view, but I can now do stuff in my main layout with very little delay. It was taking almost 20 minutes to import a prop at this time last year, and it's like 10-20 seconds. So not sure what change or changes made this happen but thank you to everyone. |
Beta Was this translation helpful? Give feedback.
-
@blun23 Brad, try the latest TestFlight on your orioginal show... |
Beta Was this translation helpful? Give feedback.
-
So I kinda started talking about this with a developer on Thursday night. Now I in no way have a small show (over 1.2 million channels). Whenever I change the name of a group or model, update number of strings, update string start channel, etc., it takes a couple of minutes for xlights to make the change in my main layout. Now if I'm on a blank layout only using a couple of props, it's instantaneous. My best guess is that not only is it updating a start channel for the groups, models and strings, but also for every group, model and submodel that is below It in order of channel #. No matter what, it's doing a lot in the background. It is basically the same no matter what PC or Mac I'm using and I have some fairly beefed up computers.
I'm curious if we could add an option to disable that until all changes are made similar to the disable rendering box in the sequence tab. Once all changes are made, there would be a button to click to update all Group, Model and Submodel start channels.
Beta Was this translation helpful? Give feedback.
All reactions