Jump to content
Light-O-Rama Forums

S6 - 6.3.2 & 6.3.4 Error Message on Groups set to "None"


Jimehc

Recommended Posts

I have been getting this error message on Sequences that Have Groups set to None - These Groups are not tagged...

And there has never been any Motion Effects assigned to this group.. But the Props in the Group use Motion Effects..

Although just clicking OK, allows the sequence to open, but it does not show the sequence was update or changed ( no * )

They are my Singing Face Group... looking at the RGBPlus Halloween Preview - The Face Group is Tagged, But set to "None"

Image00117.jpg

Edited by Jimehc
Link to comment
Share on other sites

6.3.4  - Motion Effects not following the correct order when assigning a different preview.....

ie - New RGBPlus Christmas vacation > 32x50 Tree....  Bottom 2 Effect Rows - Pushed to the top to Rows in assigned sequence...

Edit:

More Feedback:

Also I do not like that you can no longer  > Edit the Default Motion Effect Rows in The Preview - while in the Sequencer using Manage Motion Effect Rows....

The Pencil should be a Pencil (Hold Shift to draw a rectangle - minus the cursor odd looking arrow ) & the Eraser an Eraser (Hold shift to erase a rectangle - minus the odd looking cursor arrow)

I have created a custom PreviewTags.txt, placed it in the following Paths

"C:\ProgramData\Light-O-Rama\Downloads\previews\previewtags.txt"

"D:\LIGHT-O-RAMA\LORInternal\Downloads\previews\previewtags.txt"

The one in LORinternal is always over written as soon a Sequencer is Opened, so must be written from within an application...

 

I have attached the Assigned Preview for testing 6.3.4 Motion Effects, I am going back to 6.2.12...

Edit Note:

6.2.18 does the same thing with the 32x50 tree

 

Our House - Christmas 2024.lorprev

Edited by Jimehc
Not Liking
Link to comment
Share on other sites

Matt - I received the same message as JIMEHC while loading some of last years sequences.  Things looked to work EXCEPT my FLOODS.  All Motion Rows were removed from them and crossed out.  I found if I make them two PIXELS it allows a motion row  to be added to the view.  If I change them back to a single PIXEL they go back to being crossed out.  FLOOD 1,  I changed the preview to 2 PIXELS instead of one. This is why it allowed a MOTION EFFECT ROW to be added.   This is the first time loading some of these sequences since upgrading to 6.3.4 Pro.

Screenshot 2024-10-18 200816.png

Edited by RouthHurwitz
  • Like 1
Link to comment
Share on other sites

2 hours ago, MattBrown said:

I'm trying to replicate the issues you list above. In Tools > Sequencer Preferences > Motion Effects tab, what motion row order do you use?

https://www1.lightorama.com/downloads/6.3.4/help/motion_effect_preferences.htm

 

Foreground on Bottom - I Message Aubrey a Testing Sequence yesterday on Facebook...

Link to comment
Share on other sites

27 minutes ago, RouthHurwitz said:

Matt - I received the same message as JIMEHC while loading some of last years sequences.  Things looked to work EXCEPT my FLOODS.  All Motion Rows were removed from them and crossed out

I tried the update tonight and can confirm this is happening with the floods I have. I do not have any default ME rows in the previews and just relied on new ones being created with sequence creation.

Link to comment
Share on other sites

@MattBrown

Assign this Preview to the > National Lampoons Christmas Vacation-Greatest Movie Themes-LOR-RGBPlus Sequence

You will notice that the Motion Effects have been moved/ pushed down 2 effect rows on the 32x50 Tree... 

The 16x25 & 16x50 appear to be correct...

Our House - Christmas 2025.lorprev

Link to comment
Share on other sites

1 hour ago, RouthHurwitz said:

Matt - I received the same message as JIMEHC while loading some of last years sequences.  Things looked to work EXCEPT my FLOODS.  All Motion Rows were removed from them and crossed out.  I found if I make them two PIXELS it allows a motion row  to be added to the view.  If I change them back to a single PIXEL they go back to being crossed out.  FLOOD 1,  I changed the preview to 2 PIXELS instead of one. This is why it allowed a MOTION EFFECT ROW to be added.   This is the first time loading some of these sequences since upgrading to 6.3.4 Pro.

Screenshot 2024-10-18 200816.png

The issue with single pixel props losing their motion effect rows in 6.3.4 will be fixed in the next release. Should come out some time next week.

Link to comment
Share on other sites

Is there any work around until then? I use a bunch of floodlights to light up Halloween signs and such.

Link to comment
Share on other sites

On 10/18/2024 at 8:58 PM, Jimehc said:

@MattBrown

Assign this Preview to the > National Lampoons Christmas Vacation-Greatest Movie Themes-LOR-RGBPlus Sequence

You will notice that the Motion Effects have been moved/ pushed down 2 effect rows on the 32x50 Tree... 

The 16x25 & 16x50 appear to be correct...

Our House - Christmas 2025.lorprev 260.98 kB · 4 downloads

1) I set my motion row order to Foreground on Bottom

2) I opened National Lampoons Christmas Vacation RGB Plus sequence.

3) I ran 2 tests: one assigning the 2024 preview, and the other assigning the 2025 preview.

4) In both cases, the motion row order did not change

Perhaps we could continue this investigation using a LOR help desk ticket so that it is easier to share files?

 

Christmas Vacation 2024 compare.png

Christmas Vacation 2025 compare.png

Link to comment
Share on other sites

I found If i use 3 pixels together I can get my rows back. Odd its 3 for me and 2 for Routh. So at least I can get them running in groups of 3. This big bummer is when this update took away the rows, It took out the programming. The programming did not come back once the motion row was reenabled. Bah!

Link to comment
Share on other sites

53 minutes ago, Scott011422 said:

This big bummer is when this update took away the rows, It took out the programming. The programming did not come back once the motion row was reenabled. Bah!

You DO have previous versions of the sequencing saved - right?  If so, once this issue is resolved or you use the work-around, open the previous version and copy the sequencing that was saved in that version and paste into the new sequence where the sequencing was lost.  If you don't have previous versions saved, maybe you should start saving older versions.  Personally every time I save a sequence,. it gets saved with a new filename - example: Joy to the World 2024-10-20a  The a means that it was the first version saved on that date.

 

Link to comment
Share on other sites

6 hours ago, MattBrown said:

1) I set my motion row order to Foreground on Bottom

2) I opened National Lampoons Christmas Vacation RGB Plus sequence.

3) I ran 2 tests: one assigning the 2024 preview, and the other assigning the 2025 preview.

4) In both cases, the motion row order did not change

Perhaps we could continue this investigation using a LOR help desk ticket so that it is easier to share files?

 

Christmas Vacation 2024 compare.png

Christmas Vacation 2025 compare.png

Look at the Motion Effect Rows in the actual Sequence - how the Rows transferred over into the sequence (Actual sequencing) using the 2025 Preview - look at the sequenced rows on the 32x50 Pixel Tree (the transferred Sequencing is off by 2 Effect Rows)...   Never Mind, I followed my own advice - It is the Actual RGBPlus Sequence...............

And Aubrey was giving an Animation Sequence from "Jim Covert" in Facebook messages - that opens in 6.3.4 - with Motion Effect "Group Error"

Edited by Jimehc
Link to comment
Share on other sites

Version 6.3.6 is now available. Your sequences that have motion rows on props with a single pixel (like RGB floods) should now work fine.

Link to comment
Share on other sites

On 10/21/2024 at 1:50 PM, MattBrown said:

Version 6.3.6 is now available. Your sequences that have motion rows on props with a single pixel (like RGB floods) should now work fine.

@MattBrown  Version 6.3.0 was working for me.   But the versions since are adding unwanted ME rows which can not be removed.   The delete ME row does remove it from the screen.  But a save/close/open puts it back.   This is blocker to upgrading. 

Link to comment
Share on other sites

18 hours ago, ItsMeBobO said:

@MattBrown  Version 6.3.0 was working for me.   But the versions since are adding unwanted ME rows which can not be removed.   The delete ME row does remove it from the screen.  But a save/close/open puts it back.   This is blocker to upgrading. 

I agree this was happening in 6.3.4, but have had no reports of it happening in 6.3.6. If it is, then please create a help desk ticket and attach the sequence.

It can happen on groups of traditional props that have an arrangement other than "none". If you don't want motion rows on a group, then set the arrangement to "none.

Link to comment
Share on other sites

Funny, Because the first post was about a warning message in regards to NOT having Motion Effect Rows, because the Group was set to "None" in 6.3.2 & 6.3.4...

I assumed the "Fix" for it in 6.3.6 was to secretly insert one Effect Row

Edited by Jimehc
Link to comment
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...