Sean Meighan
Welcome => Do You Need Help? Post it here => Topic started by: gerry on July 31, 2015, 08:16:03 PM
-
The thread that I have linked to below has prompted me to ask about something that is on my to do list.
I have discovered that there is a channel overlap between two 'models' in my definitions of my LSP sequences that I have imported into xLights via the data layer imported method.
eg two channels of one of item overlap with the first two channel of one of my strips.
(As I have exactly the same definition in xLights , I will first correct the xLights definitions on the models and the setup) , followed by the same on the FP PI etc. The thread that I have linked to indicates that I should delete all the fseqs and resave them after making the change (within xLights) if I understand correctly .
My question is ,
- do I have to correct the definitions within LSP , re-export and then re-import to the data layer ?
- or just reimport the saved LSP definitions after correcting the xLights definitions
- or by just correcting the xLights definitions and (delete fseq/resaving), will the already imported LSP data layer map to the new definitions ?
There are about 10 to do , hence my question.. :(
http://nutcracker123.com/forum/index.php?topic=1277.0;topicseen (http://nutcracker123.com/forum/index.php?topic=1277.0;topicseen)
-
Imported data layers just map to raw channel numbers so it would have no idea about any changes you've done in your model setup. I'm not familiar with the process for importing from LSP but I do know that after import a data layer is just raw output data. It's actually an fseq file with just a different name to distinguish it.
-
Thanks Gil,
Understood. I assume that that is what the iseq file is for.
Should I chose to fix it , I will go back , correct and reimport. It is only one pixel, so let's see.. May live with the nuisance unless I find something else.