Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - brichi

Pages: [1] 2 3 ... 8
1
Bugs in xLights/Nutcracker / 2019.24 - Mac - crashing constantly
« on: May 05, 2019, 09:02:20 AM »
I've attached a few of the zip files that are created on crash. During sequencing even just this morning .24 is constantly crashing and popping up logs or just closing with no log being created, program just disappears and then 20 seconds later I get a message if I want to reopen.

When it crashed I was doing 1 of a few things, either dragging an effect to make it a shorter time or clicking on an effect and going to choose a render mode, as I clicked on render mode the program just closed

crash logs



UPDATE: went back to .22, crashed while rendering, I only have a small video on my matrix that was rendering when it crashed, no other props have effects one them, added the log

Also added a XSchedule crash, was just sitting idle, when I came back to my Mac it was close with a crash screen, this is .20 which is the latest release added to downloads

This is on a Mac mini, i5 2.6, 8GB ram and a 1TB SSD running 10.14.4

2
Bugs in xLights/Nutcracker / Re: 2019.23 Locks up on Save
« on: May 01, 2019, 09:24:37 AM »
The compression will definitely take some time, but that big of a difference is much larger than I would have expected.  On my "GreatestShow" sequence, it goes from 1.8 seconds to 8.2 seconds, but the size drops from 1.1GB to 93MB.   

That said, it's something we can easily change.   The zstd compression library supports over 40 different compression levels.   The version on the Pi/BBB supports levels from 0-25 and the version we use for xLights supports negative levels down to -20 or so.     Currently, the default is level "10" as that seemed (at the time) to be a good balance between compression and speed, particularly on the Pi/BBB I was testing it on.   However, it may make sense to drop it lower.   For example, dropping to "1" drops the save time down to 2.1 seconds, but increases the file size to 104MB, so 10% larger.  On the flip side, increasing the level to 15 makes it take 35 seconds to save, but only drops the file size to 89MB.

gotcha! I can try a few versions out for ya to see whats a happy medium, I may be one of very few that have large FSEQ files of that size so wouldn't want the compressed file size to get bigger just to make a few people happy.

3
Bugs in xLights/Nutcracker / Re: 2019.23 Locks up on Save
« on: May 01, 2019, 08:53:56 AM »
I really don't know the details of the V1 vs V2 but I thought V2 was using compression.  So saving V1 data all xLights has to do is write what's already in the render buffer to a file.  For V2 it would need to compress that data first and then write to file.  I would be curious to know the 2 different file sizes you end up with.  Now 40 seconds sounds like way too long to do the compression.  I would expect it to only take a second or two.

exactly Gil, thats why I wasn't sure if its really a matter of it being an issue with Xlights or simply the fact that V2 is compressing it down.

On V1 the FSEQ is 1.49GB and V2 compresses it down to 335MB so that will obviously take some time but not sure if 40 seconds is too much time

4
Bugs in xLights/Nutcracker / Re: 2019.23 Locks up on Save
« on: May 01, 2019, 08:15:28 AM »
Is it normal even in .24 for V2 FSEQ to take up to 40 seconds to save vs V1 taking 4 seconds?

I have a 4 minutes sequence with video in it for my p10's and on V1 it saves instantly but when i switch to v2 it locks up for 40 seconds when it saves.

If this isnt normal i can upload the sequence so you can take a look

Im on 2 macbook pro's and mac mini, i5 processors and 16GB of ram, SSD drive with plenty of room

heres a video comparing the V1 to V2 save - https://youtu.be/LfAuL1I8AKo
from roughly 20 seconds to 1 minute xlights is completely locked up on saving

5

Most likely, this affects the Text and Tendrils effects as those use some of the native drawing routines that are affected by color spaces.

yes Dan you are correct, the tendril is effected also, I just tested

6

Most likely, this affects the Text and Tendrils effects as those use some of the native drawing routines that are affected by color spaces.

glad you saw something with it Dan, thank you guys, please let me know if theres anything I can test out for ya

7
So if you go back to .19 the issue goes away?  And what is happening with green or blue?

correct, if I go to .19 the issue goes away

green and blue work perfect on all versions. just the red is the issue on .20 and above

8
There were a few submodel changes in that release.  Does the model you are putting text on have Submodels?

Hey Gil, there was no submodels, I opened up a brand new install of xlights, added a matrix quick and dropped on some text using the OS font of my choice

9
I'm just telling you about the XL fonts.  By the way you aren't supposed to mess with the color of the Font where you were doing it.  The color is supposed to come from the swatch you select on the Color Panel in xLights.

I only went into there to see if it made a difference as a test. using all the same settings, just opening .19 makes the scrolling matrix red so theres definitely something up with a change from .19 to .20. Is there anything I can supply you guys with to test? it seems to be a Mac only issue so not sure who can really test this. also if I go into any other effect the red works properly, its only on the text effect using os fonts

10
Brichi the "XL Fonts" were bitmap fonts I created so the fonts giving you a problem are the ones that have been in the program forever.

Hi Gil, the fonts giving me the issue is when I choose "use OS Fonts". they work fine in .19 but anything after .19 the red is outputted as orange. Tested on 2 separate Macs and have the same results so something in .20 and higher doesn't like something using red OS Fonts

11
Bug in "Text"effect when using red in .19 and higher on Mac.

If I set a test scrolling text red in .18 it plays as it should, if I switch to .19 or higher the red looks fine in the preview but its outputting orange to the pixels, not red. If I use other effects like bars and such then red is red on pixels but once I switch to text effect, red outputs orange.

I found a setting in the text area if you choose your own size custom font like arial and the "XL FONT" dropdown says "USE OS FONTS" that's when I get orange from red BUT if I choose a XL FONT preset and don't use OS fonts, then its red. I am also on Mojave so I wonder if thats part of it too.

here's one video I made for Keith to show - https://www.youtube.com/watch?v=oqGlAZB3TUk

heres another too I posted on FB group - https://www.facebook.com/brian.chiaino/videos/10214820748465063/

12
I would still like to see a log file. It may well hint at what it was doing just before it crashed.


Sent from my iPhone using Tapatalk

Here they are Keith, I posted them earlier but you may have missed them - https://drive.google.com/file/d/1jorHg8Ka6tUHHp3X0n7M9eFstELnv2NB/view?usp=sharing

13
Guess the only solution is leave the program open.

not a bad idea, lol....

I disable google drive from syncing and running some tests now, maybe its crashing because while xlights is closing google is also trying to backup the file as you mentioned

14
Its usually something you're doing that is different from average....otherwise it would happen to us and we would fix it.  My bet is you are working in the cloud.  I've seen nothing but trouble when users don't keep their files local to their hard drive.

Hey Gil, I do save stuff to google drive as backup but the files are local on my MacBook, they auto sync up to google drive when saved. I have never had this issue in the past, its only been happening the last couple of versions and I have been doing the same structure in folders since late 2017

15

TFSVolumeInfo has something to do with a mounted volume, usually.   Kind of wonder if there is a stuck dmg or something that's in a half unmounted stated.   If you completely reboot, does it still happen?

after a reboot I got it to crash again Dan so don't think thats the issue

Pages: [1] 2 3 ... 8