I produced an lms file. It is located here: meighan.net/htdocs/nutcracker/effects/workspaces/2/AA+FLY_0_0.lms
This file loads with no issues into LOR
I produced an lms file. It is located here: meighan.net/htdocs/nutcracker/effects/workspaces/2/AA+FLY_0_0.lms
This file loads with no issues into LOR
I haven't tried this, but I wonder what would happen...
what if you saved back the lms file from LOR after it was imported "with no issues"... would the newly-saved file also result in similar warnings when you imported THAT file into xLights?
If no messages you might compare the before/after effect of the LOR software to the file.
Is there something here that says the channel is duplicated?
<channel name="S1-P6-G" color="65280" centiseconds="0" deviceType="LOR" unit="1" circuit="17"
<channel name="S2-P1-R" color="255" centiseconds="0" deviceType="LOR" unit="2" circuit="1" savedIndex="300">
Is there something here that says the channel is duplicated?
<channel name="S1-P6-G" color="65280" centiseconds="0" deviceType="LOR" unit="1" circuit="17"
<channel name="S2-P1-R" color="255" centiseconds="0" deviceType="LOR" unit="2" circuit="1" savedIndex="300">
Hi-
I may be subject to correction, but I believe the duplication is related to the way xLights and LOR files define specific circuits/channels. xLights assumes that each LOR controller (unit) has 16 channels (circuits), using the formula: xLights channel # = ((LOR Unit Number - 1) * 16) + LOR Circuit Number. Thus, within LOR, channel/circuit 17 can be represented as either unit="1" circuit="17" or unit="2" circuit="1". Both S1-P6-G and S2-P1-R have defined the same xLights channel, which would mean you would not get an error in LOR, but would get the channel duplication issue in xLights. Hope that helps.
tlh/Terry
P.S. I am just getting started with Nutcracker, and find it most impressive!
So the root cause of the error is the assumption that lms files will be driving LOR hardware. Probably normally valid, but i am creating lms files with 16 strings of 128 pixels for example. This allows people to also import the lms file into LOR.
I think LOR folks are using ELOR and E681's and are going to get more than 50 pixels on a string. LOR seems to correctly import the lms files i create.
Can the warning just be ignored or is it an issue.
BTW, i produced the exact same butterfly effect as a Vixen vir file, imported into vixen and saved as a vix file. xLights read that file in with no errors. Xlights apparently does not have this assumption about strings and pixels for Vixen files.
So the root cause of the error is the assumption that lms files will be driving LOR hardware. Probably normally valid, but i am creating lms files with 16 strings of 128 pixels for example. This allows people to also import the lms file into LOR.
I think LOR folks are using ELOR and E681's and are going to get more than 50 pixels on a string. LOR seems to correctly import the lms files i create.
Can the warning just be ignored or is it an issue.
BTW, i produced the exact same butterfly effect as a Vixen vir file, imported into vixen and saved as a vix file. xLights read that file in with no errors. Xlights apparently does not have this assumption about strings and pixels for Vixen files.
I do not use LOR to run my shows (I use xLights), but I think it is an issue that cannot be ignored. Quoting the LOR help file, "do not simply set up two different channels having the same unit number, circuit number, et cetera in the two tracks; this will have unexpected and undesired results, as the two different channels will compete with each other for control of the same circuit." I can attest to the undesired results - I had two channels with the same ID, and it was ugly.
I suspect that you'll have to adopt LOR's channel system in order for the files to play correctly (in xLights or LOR). For example, with a 128 string node (assuming a starting channel of 1), the first string would have a Unit (Hex) ID of "1" and Circuit # 1. The remaining 383 channels for that string could follow sequentially on Unit 1 through circuit 384. For string two, the Unit (Hex) ID would be 19 (i.e., the 25th, 16-channel), with a Circuit ID of 1.
Again, that is my hunch, and others will have to verify. Last year, I ran 12 flex strings programmed with SuperStar Lights in LOR and converted to xLights. It was important that the channels did not overlap, and I had to watch the Hex IDs closely.
tlh/Terry
My goal , i believe, is to get my show from Nutcracker to xlights.That would be the ideal scenario.
-------------------------------------- | -------------------------------------- | -------------------------------------- |
Software: | Can import... | Can export... |
LOR S3 | .las (LOR II Animated Sequence) .lms (LOR II Music Sequence) | .las (LOR II Animated Sequence) .lms (LOR II Music Sequence) |
-------------------------------------- | -------------------------------------- | -------------------------------------- |
LSP 2 | .asq (Animated Sequence) .dls (Downloadable Sounds?) .lms (LOR II Music Sequence) .mpj (Animated Lighting Routine) .msq (Musical Sequence) .vix (Vixen Standard Sequence) | .asq (Animated Sequence) .lms (LOR II Music Sequence) .mpj (Animated Lighting Routine) .msq (Musical Sequence) .oms (Optimized Musical Sequence) |
-------------------------------------- | -------------------------------------- | -------------------------------------- |
Vixen 2 | .vix (Vixen Standard Sequence) | .vix (Vixen Standard Sequence) |
-------------------------------------- | -------------------------------------- | -------------------------------------- |
Nutcracker 4/30/12 | none | .hls (Helix Sequence) .lcb (LOR II Clipboard) .lms (LOR II Music Sequence) .vix (Vixen Standard Sequence) |
-------------------------------------- | -------------------------------------- | -------------------------------------- |
Ok, i made a change that sets the unit number to be
multiples of 16.
i have a 16x100 tree.
First string , pixel 1 the unit is 1 and the circuit is 1
second string, pixel 1 the unit is 19, circuit is 1
Almost all of those cross mapping error messages are gone.
I suspect that you'll have to adopt LOR's channel system in order for the files to play correctly (in xLights or LOR). For example, with a 128 string node (assuming a starting channel of 1), the first string would have a Unit (Hex) ID of "1" and Circuit # 1. The remaining 383 channels for that string could follow sequentially on Unit 1 through circuit 384. For string two, the Unit (Hex) ID would be 19 (i.e., the 25th, 16-channel), with a Circuit ID of 1.
Now i am getting a bunch of these
WARNING: channel 'S2-P99-G' is unmapped
WARNING: channel 'S2-P99-B' is unmapped
WARNING: channel 'S2-P100-R' is unmapped
WARNING: channel 'S2-P100-G' is unmapped
WARNING: channel 'S2-P100-B' is unmapped
WARNING: channel 'S3-P1-R' is unmapped
WARNING: channel 'S3-P1-G' is unmapped
WARNING: channel 'S3-P1-B' is unmapped
WARNING: channel 'S3-P2-R' is unmapped
WARNING: channel 'S3-P2-G' is unmapped
WARNING: channel 'S3-P2-B' is unmapped
WARNING: channel 'S3-P3-R' is unmapped
WARNING: channel 'S3-P3-G' is unmapped
WARNING: channel 'S3-P3-B' is unmapped
WARNING: channel 'S3-P4-R' is unmapped
WARNING: channel 'S3-P4-G' is unmapped
WARNING: channel 'S3-P4-B' is unmapped
WARNING: channel 'S3-P5-R' is unmapped
WARNING: channel 'S3-P5-G' is unmapped
WARNING: channel 'S3-P5-B' is unmapped
WARNING: channel 'S3-P6-R' is unmapped
WARNING: channel 'S3-P6-G' is unmapped
WARNING: channel 'S3-P6-B' is unmapped
WARNING: channel 'S3-P7-R' is unmapped
WARNING: channel 'S3-P7-G' is unmapped
WARNING: channel 'S3-P7-B' is unmapped
WARNING: channel 'S3-P8-R' is unmapped
WARNING: channel 'S3-P8-G' is unmapped
WARNING: channel 'S3-P8-B' is unmapped
WARNING: channel 'S3-P9-R' is unmapped
WARNING: channel 'S3-P9-G' is unmapped
WARNING: channel 'S3-P9-B' is unmapped
WARNING: channel 'S3-P10-R' is unmapped
WARNING: channel 'S3-P10-G' is unmapped
Strange, LOR gives no errors when it loads this file and the preview looks correct.
meighan.net/htdocs/nutcracker/effects/workspaces/2/AA+FLY_0_0.lms
I think you are getting close! What lighting networks do you have do you have defined in xLights? This error means that the channels you are importing don't match up to the networks you have defined in xLights.in my case, I had 9 strings of 85 pixels each defined in nutcracker, and exported as LMS.
Matt
Ok, i made a change that sets the unit number to be
multiples of 16.
i have a 16x100 tree.
First string , pixel 1 the unit is 1 and the circuit is 1
second string, pixel 1 the unit is 19, circuit is 1
Almost all of those cross mapping error messages are gone.
I suspect that you'll have to adopt LOR's channel system in order for the files to play correctly (in xLights or LOR). For example, with a 128 string node (assuming a starting channel of 1), the first string would have a Unit (Hex) ID of "1" and Circuit # 1. The remaining 383 channels for that string could follow sequentially on Unit 1 through circuit 384. For string two, the Unit (Hex) ID would be 19 (i.e., the 25th, 16-channel), with a Circuit ID of 1.
Now i am getting a bunch of these
WARNING: channel 'S2-P99-G' is unmapped
WARNING: channel 'S2-P99-B' is unmapped
WARNING: channel 'S2-P100-R' is unmapped
WARNING: channel 'S2-P100-G' is unmapped
WARNING: channel 'S2-P100-B' is unmapped
WARNING: channel 'S3-P1-R' is unmapped
WARNING: channel 'S3-P1-G' is unmapped
WARNING: channel 'S3-P1-B' is unmapped
WARNING: channel 'S3-P2-R' is unmapped
WARNING: channel 'S3-P2-G' is unmapped
WARNING: channel 'S3-P2-B' is unmapped
WARNING: channel 'S3-P3-R' is unmapped
WARNING: channel 'S3-P3-G' is unmapped
WARNING: channel 'S3-P3-B' is unmapped
WARNING: channel 'S3-P4-R' is unmapped
WARNING: channel 'S3-P4-G' is unmapped
WARNING: channel 'S3-P4-B' is unmapped
WARNING: channel 'S3-P5-R' is unmapped
WARNING: channel 'S3-P5-G' is unmapped
WARNING: channel 'S3-P5-B' is unmapped
WARNING: channel 'S3-P6-R' is unmapped
WARNING: channel 'S3-P6-G' is unmapped
WARNING: channel 'S3-P6-B' is unmapped
WARNING: channel 'S3-P7-R' is unmapped
WARNING: channel 'S3-P7-G' is unmapped
WARNING: channel 'S3-P7-B' is unmapped
WARNING: channel 'S3-P8-R' is unmapped
WARNING: channel 'S3-P8-G' is unmapped
WARNING: channel 'S3-P8-B' is unmapped
WARNING: channel 'S3-P9-R' is unmapped
WARNING: channel 'S3-P9-G' is unmapped
WARNING: channel 'S3-P9-B' is unmapped
WARNING: channel 'S3-P10-R' is unmapped
WARNING: channel 'S3-P10-G' is unmapped
Strange, LOR gives no errors when it loads this file and the preview looks correct.
meighan.net/htdocs/nutcracker/effects/workspaces/2/AA+FLY_0_0.lms
I think you are getting close! What lighting networks do you have do you have defined in xLights? This error means that the channels you are importing don't match up to the networks you have defined in xLights.
Matt
Do you just have one pixelnet network defined in xLights? Since Pixelnet is 4096 channels and your configuration requires 4800, I'm just wondering what you are doing with the last 704 channels.
Try adding a second pixelnet network in xLights and changing the LOR sequence mapping in xLights to single network.
Matt
OK, your file does not actually import into LOR S3 correctly. Unit IDs are limited to 1 through 240 (01 to F0). When using 16 circuits per unit id, you are limited to 3840 channels per network. You need 16x100x3=4800 to represent you configuration. You can see the error in LOR if you open the channel configuration grid and scroll down to S14-P1-R. You'll notice there that the network is empty. That is because you generated an invalid unit id (241-255/F1-FF). You also generate unit ids above 255, which LOR just chops off the higher order bits. So on channel S15-P28-R, which is listed in the file as unit 264, it shows as unit id 08 (264 modulo 256) in LOR.
To fix it, I think you are going to need to generate the network attribute in your lms file. So S15-P28-R should be:
unit="8" circuit="82" network="1"
Hope that helps,
Matt