1
Do You Need Help? Post it here / Re: system requirements
« on: February 05, 2018, 02:02:13 PM »
Your specs are fine ... its a better machine that I use.
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.
2
Do You Need Help? Post it here / Re: system requirements
« on: February 05, 2018, 02:01:27 PM »
I suggest you run check sequence. From your logs it is evident not all is right with your layout. I suspect you have a number of custom models with no nodes and you may have other issues.
Check Sequence can be found in the tools menu.
Check Sequence can be found in the tools menu.
3
Do You Need Help? Post it here / Re: 2018.1 xlights crashing
« on: January 11, 2018, 09:38:38 PM »
Your rgbeffects file is essentially empty. If you were to delete it and reopen xLights it would be no worse than it already is. If you were expecting to see models in the file I would be noting its size and then go back through your backup folders until you find one significantly larger than it currently is and copy that into your show directory and try again.
4
Do You Need Help? Post it here / Re: 2018.1 xlights crashing
« on: January 11, 2018, 08:42:33 PM »
If that doesnt work try starting xlights from a cmd shell with the /w switch ...
"c:\program files\xlights\xlights.exe /w"
"c:\program files\xlights\xlights.exe /w"
5
Do You Need Help? Post it here / Re: 2018.1 xlights crashing
« on: January 11, 2018, 08:39:46 PM »
So it seems to be hanging
2018-01-11 19:58:34,546 7384 log_base [DEBUG] Backup completed.
2018-01-11 19:58:34,623 7384 log_base [DEBUG] Loaded network config C:\Users\russe\Documents\Christmas 2015\xlights_networks.xml
Can you send us the xlights_networks.xml, keybindings and rgbeffects xml files.
2018-01-11 19:58:34,546 7384 log_base [DEBUG] Backup completed.
2018-01-11 19:58:34,623 7384 log_base [DEBUG] Loaded network config C:\Users\russe\Documents\Christmas 2015\xlights_networks.xml
Can you send us the xlights_networks.xml, keybindings and rgbeffects xml files.
6
Do You Need Help? Post it here / Re: Send sequence from xlights..... red test lights go out
« on: January 01, 2018, 07:29:46 PM »
So when you clicked output to lights it looks like the controller received data (the lights went out). When you click output to lights that is exactly what xLights does ... sends lots of zeroes. So it sounds like it is working ok.
To get it to send non zero data you need to click on an effect on a model mapped to the controller or press play and play your sequence.
To get it to send non zero data you need to click on an effect on a model mapped to the controller or press play and play your sequence.
7
Do You Need Help? Post it here / Re: Difficulty installing 64bit vamp plugins
« on: October 30, 2017, 01:04:23 PM »
That log has no vamp messages at all in it? Did you try to use Vamp just before grabbing the log? Its possible those messages are gone because so much else has gone on. I need a log which has vamp related messages to help.
8
Do You Need Help? Post it here / Re: FPP and xLights Channels Out of Sync Due to USB DMX Dongle
« on: October 10, 2017, 12:33:16 PM »
Oh ... and upgrade to .32
9
Do You Need Help? Post it here / Re: FPP and xLights Channels Out of Sync Due to USB DMX Dongle
« on: October 10, 2017, 12:32:54 PM »
It sounds to me like your models are mapped to channel 1 instead of being tied to the first channel of your first e131 universe. Have you run check sequence?
10
Bugs in xLights/Nutcracker / Re: Xlights freezing
« on: October 10, 2017, 12:30:40 PM »
On a really old PC I would consider dropping the OpenGL version back to 1 or 2 ... it is entirely possible those old video drivers just cant handle the way we draw those graphic elements on the screen.
This should not in any way impact the scheduler as it does not rely on openGL at all.
This should not in any way impact the scheduler as it does not rely on openGL at all.
11
Do You Need Help? Post it here / Re: Add USB / Renard Output - channel mapping lost
« on: October 10, 2017, 12:26:59 PM »
As renard does not support universes you need to use one of the following start channel formats:
Absolute - just specify the channel number listed on the setup tab ... but dont insert anything before that point later or you will need to go back and renumber the models start channels.
output:start channel - Where output is the number in the left hand column on the setup tab. Again dont insert anything or reorder anything on the setup tab after this point or you will need to renumber things. In this mode the start channel is the start channel within that output.
>modelname:channel offset - This chains the model to the end of the prior model ... this is great when models are physically chained to each other ... it can also be used when you know exactly the order models are plugged in ... but once that changes you will need to go back and fix the chains. Breaking the chains also generates annoying errors when you switch tabs.
Unfortunately for renard we dont have a simple #universe:start channel format as there is no universe number to specify. I have thought about letting you specify an optional ID which would be unique which would allow you to use the #universe:sc format but have not gotten around to it.
Absolute - just specify the channel number listed on the setup tab ... but dont insert anything before that point later or you will need to go back and renumber the models start channels.
output:start channel - Where output is the number in the left hand column on the setup tab. Again dont insert anything or reorder anything on the setup tab after this point or you will need to renumber things. In this mode the start channel is the start channel within that output.
>modelname:channel offset - This chains the model to the end of the prior model ... this is great when models are physically chained to each other ... it can also be used when you know exactly the order models are plugged in ... but once that changes you will need to go back and fix the chains. Breaking the chains also generates annoying errors when you switch tabs.
Unfortunately for renard we dont have a simple #universe:start channel format as there is no universe number to specify. I have thought about letting you specify an optional ID which would be unique which would allow you to use the #universe:sc format but have not gotten around to it.
12
Bugs in xLights/Nutcracker / Re: Check Sequence Reports Incorrect Overlap Channels
« on: October 08, 2017, 12:46:20 PM »
Two things ... try .31 it may already fix the warning.
That being said I think your start settings are wrong. You have 6 strings when in fact it should be 1. That may also be creating problems which check sequence is also calling out:
Model nodes not allocated to layers correctly
WARN: Star model 'CoroStar' Node Count and Layer Size allocations dont match.
That being said I think your start settings are wrong. You have 6 strings when in fact it should be 1. That may also be creating problems which check sequence is also calling out:
Model nodes not allocated to layers correctly
WARN: Star model 'CoroStar' Node Count and Layer Size allocations dont match.
13
Bugs in xLights/Nutcracker / Re: Node type not changing / updating
« on: October 08, 2017, 12:37:24 PM »
You can ignore this ... it will not in any way impact your sequencing ... the only problem you may see is one of the test modes that tries to turn lights red, green blue may get it wrong.
14
Bugs in xLights/Nutcracker / Re: wxWidgets Debug Alert
« on: October 08, 2017, 12:35:48 PM »
Dan made a change in .31 to disable these errors ... to be honest they should not have been appearing in the first place. They are meant to be excluded from the final build but on the mac one of the compile options was causing them to be included.
15
Enhancement Requests / Re: Update Button for layer settings
« on: October 08, 2017, 12:32:51 PM »
The problem is not technical it is user interface related. I wrote the code and it worked fine ... it was just impossible to be sure what the user wanted when they pressed the button. Did they want everything updated? or just some things updated? There are so many attributes on that panel that it is unlikely they want everything updated all the time ... and if it isnt obvious what will be updated then I am better off not doing it at all ... so the code was thrown away.
Before you go and write 2 pages about why this is wrong go back and look at the dialog and see all the options ... and think about adding an update button ... do you and every other user on the planet at every time expect the update button to make each and every field on every tab in that dialog the same ... because if not then the button will get confusing and I will have an enhancement request to add 2 or 3 or 10 buttons and on it goes. The design has to be better than just add a button.
Before you go and write 2 pages about why this is wrong go back and look at the dialog and see all the options ... and think about adding an update button ... do you and every other user on the planet at every time expect the update button to make each and every field on every tab in that dialog the same ... because if not then the button will get confusing and I will have an enhancement request to add 2 or 3 or 10 buttons and on it goes. The design has to be better than just add a button.