Sean Meighan
Software => xLights Convert => Topic started by: dgrant on June 15, 2019, 06:23:51 AM
-
I'm attempting to do something not normally done. I am trying to use a video in xLights to get a display on a 24x50 Matrix. I've managed to do that! Now when I wish to export it to an LMS file, it appears that its not possible as xLights is refusing to SaveAs a normal, exportable xLights file, rather, it only allows an XML or yesterday, I saw it was only allowing a CVS SaveAs format. Therefore, its not possible to select the file for formal export. I did try the Render and Export to an LCB file but it won't import into LOR. I've done a lot of this prior with various xLights effects which were by far better than I could create then with LOR and it worked beautifully. Just won't work with video.
-
A Video effect will export same as every other effect so something else is the cause. When we export its really just looking at the rendered data so it doesn't even know whether a Video effect was involved. Did you right-click the model to export it? Sounds like you were trying to use file save operations. At the file level you would need to use the Convert tool.
-
Yes, I tried the formal convert but since there was no xseq file, it can't export. It appeared that xLights refuses to allow a normal save process, rather opts for a CSV or XML save format, in this case. When I right clicked and selected the export option, it did save a file but it refuses to import into LOR.
Yes, I've done this before many times using xLights, because I like the effects a lot better than what LOR had available and it allowed me to create a more interesting show. No, I had never switched from using LOR to xLights because for a long time, xLights couldn't talk to LOR controllers, even though now it can. I'm using 19 LOR controllers and 6 E1.31 DMX controllers therefore a lot!
-
FYI, yesterday, I did finally have success at what I was trying to accomplish, but it was via LOR only. Turns out, I was trying to lower the image size to get it to the matrix with fewer problems but doing so, caused problems. Going back to a full image and scaling, it finally allowed it to run. I still liked what I saw run in xLights though because I was using smaller files and got the same results. Just can't get it to export properly to something LOR will accept.
-
The normal save process only allows saving for xLights. Doesn't sound like you used the Convert dialog correctly. There are some basic fundamentals of the dialog boxes you missed. Like "xseq" is not the only option that's just the top on in the list. You gotta use the drop down arrow to see all the option. You can choose the FSEQ file that has the data as the input file. Then for output again its a drop down and you can choose LMS and LCB as some of the options. Many of the export and import to LOR stuff requires channels to match in both programs when using Convert. Also there are more than one LOR version out there now so you never said if you were creating S4 or S5 clipboard data.
-
In xLights, it only allowed the one or two saving options...xml or csv. There were no other choices. The only difference between my project and a normal xLights project was that I was using a video file as the music source. As for LOR, I'm a long time user and currently on S5 Pro. I do a fairly sizeable show with two homes involved together. Dual Pixel trees, dual megatrees, E1.31 Arches, regular arches, firesticks and so much more. Halloween is much more simple other than the 24x50 Matrix but lots of fancy animatronics.
-
In xLights, it only allowed the one or two saving options...xml or csv. There were no other choices.
Yeah like I said you CANNOT use the normal save option. To get the other file formats use the CONVERT dialog and please go re-read everything I've said.
When it worked before you were on S4. When you upgraded to S5 you introduced new issues. We didn't put much effort into trying to correct all the issues LOR created with that upgrade.
-
I looked and looked, there was only the one save option but weird in that it was two different options on two days. First only option was CSV and the second day, it was only XML. I'm very computer savvy and usually know what I'm doing but the fseq, xseq and all the others, were simply not presented or available, therefore if it wouldn't save in any of those, I couldn't export that way. I agree, S4 to S5 is hugely different.
-
I'm talking about save options on the Convert dialog. I think you keep going back to some other thing you're trying to do. There are many ways to export so just saying you are trying to export is not clear enough for someone to know your steps.
-
I really do appreciate your thoughts and suggestions. The issue is that the "Convert" option, doesn't allow any of those options if the file/sequence wasn't first saved in one of those options. I can't save it in any of those options because the Save-As command, will only allow the XML and once, the CSV formats. If not saved in the proper format, I can't select that format in the "Convert" menu selector because they don't exist for this sequence.
-
Here is the screen shot. Hope it appears
-
You don't need to use Save As just do a normal save in xLights. Like I've said it saves the XML and FSEQ files. So open the sequence, hit the Render All button, then after it completes hit Save.
-
Thank You again. I'll try that today.
-
Hi Gilrock, Well, turns out that the "Save" and "Save-As", only allow the XML type file. When touching the Save Icon only, same thing, just an XML file is created. So, I'm guessing that something got dropped in the software and I just so happened to notice it. I was truly hoping it was something I stupidly missed.
-
Nothing got dropped from the software.
-
Save writes an XML and fseq every time it saves. Generally to the same folder unless told not to.
The other common save is the export of a rendered model which is how you would typically create a lcb but there are other file types you could create.
Finally there it the tools convert functions which convert to other sequencer file types.
-
I guess I was blind. Now the fseq file appeared. I didn't change anything. Wasn't there before and now its there. Oh well, like I said, I must be blind. Thanks to all!