ItsMeBobO Posted October 26 Share Posted October 26 There appears to be something inserting unwanted motion rows on S6.3.6. This freaked me out for bit but I think I have recovered by reverting back to S6.3.0 which behaves differently. When I opened 6.3.6 for the first time I found that ALL of my RGB props now had motion effect rows where they didnt exist before. I dont want them on each prop of a multi prop group. It makes no sense to me to create an effect for one string of a 32 string tree. The motion effect for me is only at the top of the 32 string group. Any way, I tried deleting them and saved the sequence and reopened it and the unwanted and deleted ME rows were present again. The manage ME rows functions did nothing. Link to comment Share on other sites More sharing options...
k6ccc Posted October 27 Share Posted October 27 Are those Motion Effects rows specified in the Preview? Link to comment Share on other sites More sharing options...
Jimehc Posted October 27 Share Posted October 27 (edited) In 6.3.6, LOR now "Secretly" adds a Motion Effect Row to any RGB Prop or Group that does not have one.... There use to be an Option to Add a Default Motion Effect Row, But, that option was removed... Edited October 27 by Jimehc Link to comment Share on other sites More sharing options...
Box on Rails Posted October 27 Share Posted October 27 22 minutes ago, Jimehc said: In 6.3.6, LOR now "Secretly" adds a Motion Effect Row to any RGB Prop or Group that does not have one.... There use to be an Option to Add a Default Motion Effect Row, But, that option was removed... If that's the case then I'm not upgrading until January. Why would the LOR Gods take that option away. I have mine set to 2 default ME rows and my plan was to increase that to 3 for 2025. I hope that is added back in subsequent updates. Link to comment Share on other sites More sharing options...
PhilMassey Posted October 27 Share Posted October 27 (edited) I have never added default rows in Preview and always turned down the offer when loading a preview. I make my own as needed, usually 3 per prop or group in motion row manager in Sequencer. Many are custom rows. They then get put into a grid view group to keep them organized.This update created a couple of default rows seemingly at random which I deleted in preview. It also changed the name of two rows which I had to fix in grid view, which meant a reimport into all the sequences. Edited October 27 by PhilMassey Link to comment Share on other sites More sharing options...
Jimehc Posted October 27 Share Posted October 27 Any "Default" Motion Effect Rows are Done via the "Preview Prop Definition" If the RGB Prop does not have any "Default" Motion Effect Rows > One is added for you... You can still Add Custom Motion Effect Rows in the Sequence... Link to comment Share on other sites More sharing options...
ItsMeBobO Posted October 27 Author Share Posted October 27 (edited) Can you expand on this? Its doesnt appear to be a solution to unwanted ME which are seen and cant be deleted using above S6.3.0 which is no longer offered on the DL site. SE has an action to delete ME rows, which used to mean something. Now yes you can delete it but close and reopen and it is present again. If there is no intent to allow delete then why is that option seen., This works in S6.3.0 Edited October 27 by ItsMeBobO Link to comment Share on other sites More sharing options...
MattBrown Posted October 28 Share Posted October 28 I agree that 6.3.4 was creating motion rows in undesired places, but this has been fixed in 6.3.6. 6.3.6 will add a single motion row to a prop if it uses pixels and: there are no motion rows for it when an existing sequence is opened, or when creating a new sequence and there are no defaults defined for it in the preview 6.3.6 will add a single motion row to a group if it's arrangement is not "none" and: there are no motion rows for it when an existing sequence is opened, or when creating a new sequence and there are no defaults defined for it in the preview If you don't want motion rows on a particular group, then set its arrangement to "none". If you want multiple rows on a prop or group when creating a new sequence, you should use motion row defaults in the preview. We hope to make the process of creating and managing motion row defaults easier in future releases. If you have ideas, please let us know. If you see the Sequencer do something that is not consistent with the description above, please create a help desk ticket and attach the sequence. Thanks for the feedback! Link to comment Share on other sites More sharing options...
ItsMeBobO Posted October 29 Author Share Posted October 29 This matrix is comprised of 60 props. The arrangement of the group Horizontal stack align tops. I have been using the group ME for the entire 60 column by 16 row matrix successfully. What do all the individual ME rows do and why are they desirable enough to force them on us? ME worked without them before. As a sequencer I personally would not use a ME on a single 16 rgb prop of a 60 prop set. Cant the rule be there should be one ME on the prop OR parent group? Each prop definition asks for zero default Motion rows. I have a feeling some may say convert this to a larger matrix. Unfortunately my arrangement is 'every other' for each prop. The 16 pixels are not consecutive. Instead they go down the column and back up to allow connection to the next drip prop. The light strings I purchased for the icicle drips are 16 pixels. The begin and end connectors are at the top so they can be chained together. Link to comment Share on other sites More sharing options...
Jimehc Posted October 29 Share Posted October 29 It was done to reduce Help Desk Tickets.... As you have shown the "Default Motion Rows" Option was removed... It may have solved an Issue for some, but it was force upon everybody else to deal with it.... Link to comment Share on other sites More sharing options...
Jeremiah Ackermann Posted October 29 Share Posted October 29 11 hours ago, ItsMeBobO said: What do all the individual ME rows do and why are they desirable enough to force them on us? I am curious, why expand the group's props and their children ME rows if you don't use them? They can just stay collapsed and not be used. That said, I believe the sentiment above is similar to a desire I have. I would like the idea of being able to setup a grid view configuration where the ME rows can just exist at the parent level in the tree and you did not have to see the whole tree structure of groups and props or require seeing all their ME rows. I will try to draw up that idea sometime today and share it here. In essence, it would be nearly like old school AC programming where you just had channel rows and user defined groups. This gives the user total control and flexibility of what AC channels/ME rows they see in a grid view, group them how they see fit, and avoid seeing the whole structure of groups, props, and all their ME rows. The main advantage of not seeing the whole tree structure is much less scrolling, expand/collapse, and exact ordering control (similar to unstructured ME row order). Link to comment Share on other sites More sharing options...
MattBrown Posted October 29 Share Posted October 29 14 hours ago, ItsMeBobO said: This matrix is comprised of 60 props. The arrangement of the group Horizontal stack align tops. I have been using the group ME for the entire 60 column by 16 row matrix successfully. What do all the individual ME rows do and why are they desirable enough to force them on us? ME worked without them before. As a sequencer I personally would not use a ME on a single 16 rgb prop of a 60 prop set. Cant the rule be there should be one ME on the prop OR parent group? Each prop definition asks for zero default Motion rows. I have a feeling some may say convert this to a larger matrix. Unfortunately my arrangement is 'every other' for each prop. The 16 pixels are not consecutive. Instead they go down the column and back up to allow connection to the next drip prop. The light strings I purchased for the icicle drips are 16 pixels. The begin and end connectors are at the top so they can be chained together. I agree that it shouldn't be creating motion rows on a prop where channel level sequencing has been enabled. That will be fixed in the next release. Thanks for providing the example! Link to comment Share on other sites More sharing options...
MattBrown Posted October 29 Share Posted October 29 Also note that many prop shapes support alternate node wiring: https://www1.lightorama.com/downloads/6.3.6/help/alternate-node-wiring.htm Link to comment Share on other sites More sharing options...
ItsMeBobO Posted October 29 Author Share Posted October 29 1 hour ago, MattBrown said: Also note that many prop shapes support alternate node wiring: https://www1.lightorama.com/downloads/6.3.6/help/alternate-node-wiring.htm Fantastic! Thanks for pointing that out. Next season I may try to redo this prop. Link to comment Share on other sites More sharing options...
PhilMassey Posted October 29 Share Posted October 29 3 hours ago, MattBrown said: I agree that it shouldn't be creating motion rows on a prop where channel level sequencing has been enabled. That will be fixed in the next release. Thanks for providing the example! Will the "hidden" new rows be removed or made removable by the update or are we stuck with them. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now