Sean Meighan

General => Show Assets => Topic started by: jnealand on October 11, 2015, 01:58:06 PM

Title: How to import a shared or old (last years) xml file
Post by: jnealand on October 11, 2015, 01:58:06 PM
I am a terrible sequencer creator.  Thanks to folks who are willing to share their gems I have been able to put up a show for years.  This year I had to learn new ways to import shared xml files or even my last years xml files since the layout and props have changed/been updated.  I finally have the steps down so that it seems to work pretty good.  I documented my process and am sharing that for others to try.  If you find errors or areas that you think need clarification please let me know.

Jim

Edit - updated the file for 2016 updates and a few more tips
Title: Re: How to import a shared or old (last years) xml file
Post by: kevinp on October 11, 2015, 06:38:21 PM
Awesome work.  Looks like we'll have to create a new section in the manual for this.  Gerry, Steve?
Title: Re: How to import a shared or old (last years) xml file
Post by: gerry on October 11, 2015, 10:58:15 PM
Awesome work.  Looks like we'll have to create a new section in the manual for this.  Gerry, Steve?

Hi Kevin,

Have already been in touch with Jim :)
Title: Re: How to import a shared or old (last years) xml file
Post by: jnealand on October 12, 2015, 09:17:08 AM
I need for someone to try this out to see if I got it right.  I've done several sequences and did another one while I was trying to document the process, but another set of eyes is needed, IMHO.  I wrote it because I had trouble getting started the first couple of times and after I figured out the correct order of steps it has worked great.
Title: Re: How to import a shared or old (last years) xml file
Post by: danj on November 16, 2015, 09:22:52 PM
Thanks Jim.
Title: Re: How to import a shared or old (last years) xml file
Post by: ahb2ukeith on November 17, 2015, 05:08:07 PM
Thanks Jim
Title: Re: How to import a shared or old (last years) xml file
Post by: jnealand on November 30, 2015, 07:03:12 PM
In the first post I updated the file to cleanup the process and I hope simplify it a little.
Title: Re: How to import a shared or old (last years) xml file
Post by: scuba on November 30, 2015, 07:10:09 PM
Great Job Jim!!!
Title: Re: How to import a shared or old (last years) xml file
Post by: tindivall on December 02, 2015, 01:13:33 PM
I don't quite do it that way (maybe I am doing it wrong)... but I do like you say (view the layout to get an idea of models etc and what I want where compared to my layout)...

I then just copy the xml file to my file location and open it in the sequencer tab.  The system will give error messages about can't find " model name "... I hit the ok button until those all go away... then another window box opens... this window has the model listed and 2 options... 1) Delete Element or 2) Rename Element with a drop down box of my models to rename to.

I go through and for each one Delete if I don't want or Rename to the model I want it to match....  Once done I save the sequence.

Done




Seems to work just fine for me, but like I said could be doing something wrong and don't know it... anyone with any thoughts on this process?
Title: Re: How to import a shared or old (last years) xml file
Post by: jnealand on December 02, 2015, 09:30:10 PM
I have done what you describe until I found the way I documented.  The problem with your technique is that if you want to go back and do it again you have to run thru that whole delete / rename option again.  I had one sequence where the donor had 96 models and I only wanted 12.  What a pain.  The same thing applies if you have more than one sequence shared by the same person.  For instance you have shared 6 sequences which I have downloaded.  I will get around to trying them on my layout.  I only have to build a map file once (if I do it right) and I can import all of your sequences to my layout in about 10 min or less.  What a great thing this is.  I have several sequences from another person.  I built a map file and converted all the sequences, then realized I wanted to pick the whole house element from his xml which left holes in the sequence.  I went back and made a new map file and reconverted all the sequences in the time it takes to load them and save them after I had the map fixed.  Unfortunately there is no way to edit the map - cannot delete a model and the map file contains every node when all I need is model to model.  I have put in an enhancement request but who knows when that will bubble to the top.
Title: Re: How to import a shared or old (last years) xml file
Post by: tindivall on December 03, 2015, 11:29:08 AM
Good thoughts!!  I knew that my way had to be wrong/backwards in some way!!!  Thanks
Title: Re: How to import a shared or old (last years) xml file
Post by: markrvp on January 24, 2016, 11:29:55 PM
Thank you Jim, very much appreciated  :D
Title: Re: How to import a shared or old (last years) xml file
Post by: chadowamsley on March 07, 2016, 07:52:39 PM
Thanks Jim. This should really help me out with my first year sequencing with pixels.
Title: Re: How to import a shared or old (last years) xml file
Post by: sean on March 07, 2016, 11:05:59 PM
Great job Jim!

Your flow is the same as I use. Have two xlights running, run through the source sequence , see what it looks like on their house. Decide what models from their sequence that will match your own house.

For example when we mapped the sequences Lilia did on our house, we had 22 arches. We were moving the seuqnce to Dave Pitts house, he had only 10 arches. Some of the sequencing Lilia did started with our Arch 7 and did effects both directions. We then decided to map our Arch 7 to Daves Arch 3.

The point is , look at the source and imagine moving those effects onto your house. It can be that our arches will go to your eaves.

I think this is the hardest part. When Lilia does this for a client, she makes a list to map source model names to target model names. When this paper list is complete then she uses the "import, Sequence" to build the mapping file.

again, great job!

sean
Title: Re: How to import a shared or old (last years) xml file
Post by: jnealand on March 08, 2016, 08:59:58 AM
Thanks Sean.  One of the beautiful things with xlights is that you can map anything to anything although some of the effects don't look good on widely dissimilar elements.  But, I have put starbursts on mega trees, roof lines on arches, bushes to mini trees, etc.  I am a terrible sequencer so shared sequences are a life saver to me. 
Title: Re: How to import a shared or old (last years) xml file
Post by: dkulp on March 08, 2016, 10:13:05 AM
I'm also a terrible sequencer.   I have very little rhythm (I tried tapping out beat tracks several times and if I did the same song three times, I got 3 very different beat tracks) and am not much of an artist.   That's why I've spent so much time working on xLights imports and mapping capabilities.  I figured I'd let the true artists do the artistic stuff and then hopefully they'll share some of that with the rest of us that aren't as good at it. 
Title: Re: How to import a shared or old (last years) xml file
Post by: jnealand on March 08, 2016, 12:32:33 PM
Now if you would just fix the xml import so we do not have to see strands and nodes in the mapping window (at least for xml import) the mapping function would be much easier.
Title: Re: How to import a shared or old (last years) xml file
Post by: kevinp on March 08, 2016, 02:11:47 PM
Didn't Sean, at one point in recent history, tease a feature they were working on (or would) to make sharing sequences easier between users?  I'm wondering if this is still in the roadmap plans for this year?
Title: Re: How to import a shared or old (last years) xml file
Post by: sean on March 08, 2016, 02:13:44 PM
still on roadmap. I am going though process with my wife, Lilia, as she does this mapping for others who are buying her sequences.
Title: Re: How to import a shared or old (last years) xml file
Post by: jnealand on May 09, 2016, 09:38:01 AM
1st post has been updated to include a v3 of the writeup with notes resulting from 2016 changes and a couple of tips learned by me and from others.