Sean Meighan
Welcome => Do You Need Help? Post it here => Topic started by: msiebri on November 23, 2017, 07:58:41 PM
-
I just started up xSchedule for the first time today, and I have a couple of questions:
1) When I first launch it, I get an error about not being able start the web server. Is it anything to be concerned with? The scheduler seems to work fine.
2) When I run Tools->Check Schedule, I get warnings on all my sequences that they have 2 more channels than are configured to be sent out. What is causing this? I don't see any models that go past my last defined channel.
Thanks for any help? Pics are attached.
-
#1. The best fix for this is to change the port xschedules web interface runs on. By default it is 80 but you can change it to 81 or 8080. But it will change the way you get to it on your phone. You will need to ad :81 or :8080 after your ip address
-
#2 you can ignore. It will go away in .38
-
Thanks very much! I didn't know there was a way to control things from your phone. Is there a manual or a video explaining this somewhere?
-
Videos.xlights.org
-
I was wondering the same thing about the warnings. Awesome to know that the fix is in place! Thanks for all the hard work on xlights and the scheduler!
Sent from my iPhone using Tapatalk
-
Interesting, I had the "two more channels" issue, but then realised I'd added two channels for a dmx device but hadn't added the device in layout. After I added it no more "two channel issue".
maybe something to check as well as wait for Keith's update?
-
spoke too soon :)
I seem to have this issue again, in version .39 and .40
"8480 channels when only 8448 channels are configured"
I'll check I'm not doing something dumb (I usually am)
-
Try render and save. Only other reason this could happen is you have a model which extends beyond the configured controllers. Check sequence will spot that.
-
Tried render and save - didn't fix issue
Check Sequence - no issues detected
Note: I did both of above before posting previous comment. I've learnt lots from @keithsw1111 but the biggest is to do the 2 things above before posting a question/issue :D
Turned out issue was somehow I'd saved and rendered as Master View, when I saved as my view (Christmas 2017) issue was fixed, except for 1 sequence. I've posted a new thread in the Bug section on this one.
So I was correct, I had done something dumb. ::)
-
Ahhh no. That doesn't explain it. Views make no difference to the render.