xx 2016.56 released

[sean]

Release 2016.56. Prob last release this year ..

Thanks to Dan Daniel Kulp, Gil Jones, Chris Debenham and Keith Westley!

Spatial color gradients on more effects. Pinwheel, Fan effects improved (no holes on large models, faster to render).
New Tools,Package Sequence
Improved Galaxy effect

I made a video highlighting some things in this release
https://vimeo.com/197634619

XLIGHTS/NUTCRACKER RELEASE NOTES:
---------------------------------
2016.56  Dec 31, 2016
   -- enh (gil)     Rounder ends for the Galaxy effect.
   -- enh (gil)     Use dynamic step angle to prevent holes in Galaxy effect for large radii.
   -- enh (gil)     Update Fan to support spatial colors and not leave any holes.
   -- enh (gil)     Update Shockwave to support spatial colors and not leave any holes.
   -- bug (gil)     Fix cell highlight movement that was broken by other fixes in August.  Fixes #755.
   -- enh (keithsw) Add sequence packaging to the tools menu    "Tools,Package Sequence"
   -- bug (keithsw) Make xbkp auto recovery smarter. Dont trigger after a sequence is discarded. Dont trigger when doing batch rendering.
   -- enh (keithsw) Add more sub buffer panel right click menu options for fast setting sub buffers
   -- enh (keithsw) Add manual sub buffer editing allowing more precise control over sub buffer sizing
   -- enh (keithsw) Add home (start of song) /end (end of song) /pause (pause playing song) shortcut keys in sequencer
   -- enh (keithsw) Add spatial color curves to single strand
   -- enh (keithsw) Add spatial color curves to pinwheel
   -- enh (keithsw) Add reset to default on remaining effects when you select a different effect to the one currently selected (fan/morph/shockwave/dmx/fill/galaxy)

Software is on www.xlights.org

[kentd]

I gather that the feature of opening the controllers from this version would require the network they are hooked to to be on the xlights computer and not the FPP? Is there a way to look at the controllers through the FPP?

If I have needed to make changes I have unplugged the Ethernet cable from the hub and plugged it into the computer then input the controller's address.

[keithsw1111]

Sure you can if you have a wifi enabled Pi and you setup network routing.

[kentd]

Keith I see the checkbox to enable network routing, after it is checked and saved is there anything else to make it work?

[babybear]

what I found was this.  Your IP addresses will be different   
my IP addresses  give you a starting point
Router 192.168.1.1  to  wlan0 PFF 192.168.1.22   to  eth0 PFF 192.168.3.35  to  eth0 F16v2 192.168.3.36


1. Set their default gateway address on your show controllers to that of the PI's Ethernet address. 
2. Go into the network settings of the PI and check the Enable Routing Between Network Interfaces checkbox.
3. On your PC, open a command line and enter the following command:  route -p add 192.168.3.0 mask 255.255.255.0 192.168.1.22
 
This will allow your PC to communicate with the show network thru the PI

This is in windows

[kentd]

OK my PI is 10.0.1.13 from my computer or iPad and my controllers are 10.0.0.70 thru 73 so how do I get the FPP to give me it's router IP

From the FPP Network Page
Eth0 is 10.0.0.13 Static
DNS Server 10.0.1.1 Manual
Lan0 10.0.1.13 Static
Mask 255.255.255.0
Gateway 10.0.1.1

[babybear]

  wlan0

From the FPP Network Page select wlan0 instead of Eth0
  that will give you the set of wifi IP address setting
 What we are looking for are your FPP wlan0 and Home router setting.
Home router setting you can get out of the manual Internet sometimes of the bottom of the unit
   Unless you had changed it. From what you have given me this is what I'm getting

Eth0   10.0.0.13
wlan0  10.0.1.13
Home router 10.0.1.1

 route -p add 10.0.0.0 mask 255.255.255.0 10.0.1.13

[kentd]

I did this in command mode as administrator it said OK however when I try to get it to open it times out. The FPP is still running the lights on the roof only at this time.

I was after 10.0.0.70 but tried 10.0.0.71 with the same result timed out.

I did an ipconfig /all and here is the first entry back, Is this the problem

Windows IP Configuration

   Host Name . . . . . . . . . . . . : DESKTOP-SBR7HU0
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Changed IP Routing to enabled still nothing

[babybear]

By any chance when you're in the internet explorer and type in the controller IP address can you get there.  Not sure how you are looking at .  through/using fpp or xlights

[kentd]

I can access 10.0.1.13 from Explorer but not 10.0.0.70 through the FPP. If I remove the Ethernet Plug from the FPP that feeds 10.0.0.70 and plug it directly into the Computer I can access the controller but not through the FPP

One thing that might enter into this equation, my computer I am trying to get to talk to the controllers through the FPP is a laptop running Windows 10 and this is the one I have been talking about, however my upstairs computer is the link to the internet via fiber optic with the laptop connecting through wi-fi. This might be making a difference.

[keithsw1111]

There are several things that need to be right for this to work.

1. Your wired and wireless networks must be in separate subnets
2. Your controllers must have the gateway set to be the eth0 IP address on the Pi
3. The route checkbox in fpp must be set
4. A static route must be setup on your pc or router (if it supports it) to tell it to route requests to your controllers subnet to the wlan0 IP address of the Pi.

[kentd]

Keith here is a run down of what I have as I am not very good at networks. My router has the wi fi and is hooked directly to the fiber optic and runs to a switch that the computer upstairs is wired to. If I wanted to run the controllers from that computer with the Ethernet cable I had to set the one to 10.0.1.70 not 10.0.0.70 like I have for the FPP to run them from it's switch. The Lap Top also uses 10.0.0.70 with the cable plugged into it. 10.0.1.13 gets me into the FPP and if upstairs I do a command prompt and a ipconfig /all I can see the FPP.

What do I actually need in terms of commands to make this work otherwise I will just do like I have always done, unplug the cable put it in the Lap Top and configure the Controller.

Aren't these two different subnets?
Eth0   10.0.0.13
wlan0  10.0.1.13

I guess my question is how to set up the static route, as that is what seems to be missing.

I just tried to go into my spare 10.0.0.70 via cable as I use this to test strings and because of messing with the different commands I now can not get access to it to do anything. HELP how do I get back to where I was before?

[keithsw1111]

To tell a windows PC how to get to your show network:

1. Run a cmd prompt as an administrator.
2. know your pi's wireless ip address ... this needs to be fixed. lets call it <pi_wifi_ip>
3. know your pi's show network ip and mask as well. we need to turn it into a masked ip .. so if it was 192.168.1.34 and your show network subnet mask was 255.255.255.0 it becomes 192.168.1.0 ... ie where there are 255s int the mask we copy the value. Where there are zeroes in the mask we put zeroes. Lets call this <shownetwork>
4. know your shows network subnet mask ... again likely 255.255.255.0. lets call this <show_subnetmask>
5. Type this command "route add <shownetwork> mask <show_subnetmask> <pi_wifi_ip> -p"

You can then run "route print" and somewhere in all that output should be the pi.
you should be able to ping <pi_eth0_ip> if everything is setup correctly.
If you can do that but not ping controllers then that is likely a controller gateway setting problem.

[kentd]

Problem Solved with Keith's help
The computer can now talk to my in house controller which is what I needed