Vixen 3 export to FPP

[jeffu231]

I am guessing you are using the individual export in the sequence. If you use the bulk export wizard and the FPP is accessible on the network, it will push it up there for you along with the audio and sequence files.

[pmiller]

Jeff, I'm using the bulk export. I would rather export to a folder and then upload to fpp. That way I can keep files as a backup without downloading from fpp.

Sent from my SM-T710 using Tapatalk

[dkulp]

Note: this export format is likely not going to work very well for FPP 2.0 as it has switched completely over to json config for the universes.

[jchuchla]

Note: this export format is likely not going to work very well for FPP 2.0 as it has switched completely over to json config for the universes.

We will likely eventually create an option for which version of file to generate. Now that we have the ability to generate the universe data, the actual output format is fairly trivial.

[jeffu231]

Note: this export format is likely not going to work very well for FPP 2.0 as it has switched completely over to json config for the universes.

Is there somewhere the 2.0 format is documented that I can see. Also is there some way to know which version of FPP is running? I know there was talk at one time about a full web api for doing a lot of this, but I lost track of any of those conversations.

[pmiller]

Right now I'm using FPP 1.10 . I'm hesitant switching to 2.0 because it's been running flawlessly.

Sent from my SM-T710 using Tapatalk

[dkulp]

Is there somewhere the 2.0 format is documented that I can see. Also is there some way to know which version of FPP is running? I know there was talk at one time about a full web api for doing a lot of this, but I lost track of any of those conversations.

2nd question first: with 1.x, not really. With 2.0, you can do a GET on "/fppjson.php?command=getSysInfo" and it returns a JSON with a bunch of information with the version being one of the values. For xLights, if we do a GET and it works, then it uses the version, else we do a GET on / and try to parse the Version from the HTML via a regex. Kind of sucky. That's why 2.x has the getSysInfo thing.

1st question: no docs that I'm aware of. Best bet is likely the the xLights code to write the file:

https://github.com/smeighan/xLights/...s/FPP.cpp#L258

(and note that with 2.x, the INPUTS and OUTPUTS are separate files/configurations) . Example:

{
	"channelOutputs": [
		{
			"type": "universes",
			"enabled": 0,
			"startChannel": 1,
			"channelCount": -1,
			"universes": [
				{
					"active": 1,
					"description": "",
					"id": 1,
					"startChannel": 1,
					"channelCount": 512,
					"type": 0,
					"address": "",
					"priority": 0
				}
			]
		}
	]
}

[jeffu231]

2nd question first: with 1.x, not really. With 2.0, you can do a GET on "/fppjson.php?command=getSysInfo" and it returns a JSON with a bunch of information with the version being one of the values. For xLights, if we do a GET and it works, then it uses the version, else we do a GET on / and try to parse the Version from the HTML via a regex. Kind of sucky. That's why 2.x has the getSysInfo thing.

1st question: no docs that I'm aware of. Best bet is likely the the xLights code to write the file:

https://github.com/smeighan/xLights/...s/FPP.cpp#L258

(and note that with 2.x, the INPUTS and OUTPUTS are separate files/configurations) . Example:

{
	"channelOutputs": [
		{
			"type": "universes",
			"enabled": 0,
			"startChannel": 1,
			"channelCount": -1,
			"universes": [
				{
					"active": 1,
					"description": "",
					"id": 1,
					"startChannel": 1,
					"channelCount": 512,
					"type": 0,
					"address": "",
					"priority": 0
				}
			]
		}
	]
}

Thanks. I appreciate the info. That will get me started. All 4 of my FPP instances are still on 1.x and will likely stay that way this season. I have a spare floating around that I may load 2.0 on and I can play around with this.

[Strawberry]

Thanks for the added feature. It will save me lots of time this year.

Sent from my SM-G950U using Tapatalk