-
Notifications
You must be signed in to change notification settings - Fork 221
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash Report #5208
Comments
Perhaps a combination of layering and new video effect. Can you upload the videos? looks like perhaps a .mov file? If it is just this sequence, I wonder about the .mov format. |
All I get is Failed to upload "Like It's Christmas.mov" |
You need to zip that first then assuming it is not too big, upload it. I wonder if the special characters in the name are killing something. (Shouldnt) .. can you remove the effect where that is used to see if it is indeed that file? |
Every video in the sequence is cautioned in yellow. "contains characters in the path or file name that will cause issues in xLights. Please rename it." The issue is the sequence worked fine 2 months ago. And none of the mp4s or the mov have odd characters. FPP didn't have an issue with it, either. I see I acquired it in 2021, so I hope I didn't pay much for it. |
I reverted back to 2024.20, and it rendered just fine. I'll stick with that version for now. |
The new code is in .03 and going forward. We cant fix it without some more pieces. |
I can't fix my problem with it crashing before I can fix it. If you DM me an email address in FB, I can send you the sequence video. |
Thread: 0000027960 Whole House Model - Rendering layer effect for frame 2803 of Whole House Model, layer 3: CHECKBOX_Palette2=1,CHECKBOX_Palette3=1,CHECKBOX_SynchroniseWithAudio=0,CHECKBOX_Video_AspectRatio=1,CHECKBOX_Video_TransparentBlack=0,CHOICE_BufferStyle=Per Preview,CHOICE_Video_DurationTreatment=Normal,FILEPICKERCTRL_Video_Filename=C:\Christmas Sequences 2021\Like It's Christmas\1080_Pop_Up_Trees_Red_Videvo.mov,TEXTCTRL_Duration=0:30.040,TEXTCTRL_Fadein=.5,TEXTCTRL_Fadeout=1,TEXTCTRL_Video_CropBottom=0,TEXTCTRL_Video_CropLeft=0,TEXTCTRL_Video_CropRight=100,TEXTCTRL_Video_CropTop=100,TEXTCTRL_Video_Speed=1.5,TEXTCTRL_Video_Starttime=0.00,TEXTCTRL_Video_TransparentBlack=0 |
The double stack of this one video is causing the crash. If I remove one, its fine. So it could be a case of the new video + the layering code. Need to diagnose. |
Just an update .. its not really the actual video that is the problem. The 2 layered effects ... the bottom is a full buffer, the top is only a small slice of the buffer. Something is happening on the clean up of that after the render causing the crash. |
I traced that sequence back to Pixel Sequence Pros, so you might want to warn Tim about this glitch.
…________________________________
From: Daryl ***@***.***>
Sent: Sunday, February 16, 2025 9:00 AM
To: xLightsSequencer/xLights ***@***.***>
Cc: BrianSchoenecker ***@***.***>; Author ***@***.***>
Subject: Re: [xLightsSequencer/xLights] Crash Report (Issue #5208)
Just an update .. its not really the actual video that is the problem. The 2 layered effects ... the bottom is a full buffer, the top is only a small slice of the buffer. Something is happening on the clean up of that after the render causing the crash.
—
Reply to this email directly, view it on GitHub<#5208 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BPROK2UVZ7W5KDSG7VXS7XT2QCRZHAVCNFSM6AAAAABXG6M42OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRRGQ3DSNZVGM>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
[derwin12]derwin12 left a comment (xLightsSequencer/xLights#5208)<#5208 (comment)>
Just an update .. its not really the actual video that is the problem. The 2 layered effects ... the bottom is a full buffer, the top is only a small slice of the buffer. Something is happening on the clean up of that after the render causing the crash.
—
Reply to this email directly, view it on GitHub<#5208 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BPROK2UVZ7W5KDSG7VXS7XT2QCRZHAVCNFSM6AAAAABXG6M42OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRRGQ3DSNZVGM>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Fixed it, thanks.
…________________________________
From: Daryl ***@***.***>
Sent: Sunday, February 16, 2025 8:12 PM
To: xLightsSequencer/xLights ***@***.***>
Cc: BrianSchoenecker ***@***.***>; Author ***@***.***>
Subject: Re: [xLightsSequencer/xLights] Crash Report (Issue #5208)
I got the bug addressed - Unrelated, but I noticed your layout as an old "issue". Your stars on the trees with layers. You need to go into the layers and change the layer sizes from small to large, inner to outer.
image.png (view on web)<https://github.com/user-attachments/assets/ec5c5529-18a2-495c-91f8-ed1e7f60a93c>
—
Reply to this email directly, view it on GitHub<#5208 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BPROK2XPFQJ6DVOUZGMCXX32QFAR3AVCNFSM6AAAAABXG6M42OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRRG44TSOJTGU>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
[derwin12]derwin12 left a comment (xLightsSequencer/xLights#5208)<#5208 (comment)>
I got the bug addressed - Unrelated, but I noticed your layout as an old "issue". Your stars on the trees with layers. You need to go into the layers and change the layer sizes from small to large, inner to outer.
image.png (view on web)<https://github.com/user-attachments/assets/ec5c5529-18a2-495c-91f8-ed1e7f60a93c>
—
Reply to this email directly, view it on GitHub<#5208 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BPROK2XPFQJ6DVOUZGMCXX32QFAR3AVCNFSM6AAAAABXG6M42OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRRG44TSOJTGU>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
In next release. |
1 sequence out of 66 crashes during render. I added some props for this year. It ran fine last December.
xLights_dbgrpt-19088-20250215T170514.zip
The text was updated successfully, but these errors were encountered: