convert last years XML to new XML 2016 version

[mgholland]

Ok I am lost here. I have watched several videos about converting xml files to now sequences and i must be doing something wrong.
I used xlights version 4 last year and have the newest version xlights 2016.50 now and have change my layout some and renamed other things and would like to import my sequences from last year to the new setup.
after starting a new sequence and selecting the song and timing 20ms and select done I am ready to import the old XML file. I select import select my old directory and select XML in bottom left and click ok. I get the following screen.  here is where I get lost. I am at the top of the import window and I am not finding any thing to match it to only MTree-pixel shows up.
how do I get or find the other items to select from?

[Gilrock]

You have to create a sequence and have all the models on the grid before they will be available in those drop down lists.  When you create a sequence use the All Models option with Quick Start and you'll have everything you've defined.

[dkulp]

Why import them?  Can't you just open them like normal?   For any models that no longer exist (renamed, for example), it will prompt if you want to map them to a different model or similar.

[mgholland]

Why import them?  Can't you just open them like normal?   For any models that no longer exist (renamed, for example), it will prompt if you want to map them to a different model or similar.

Ok I may try this. but adding a smaller Pixel tree and wanted to import the old one on to the new one so it would be showing the same thing and be sized right since it is smaller.  Is there an easy way to do that?

Thanks for both of your help.

[danj]

You can just copy/paste your existing megatree effects onto your new megatree in the sequencer.   I am doing that right now with a lot of this years' sequences, as I am adding two more megatrees to the two I had last year.   Well, this is one way to do it.   Dan/Gil might have a more eloquent way...

[mgholland]

OK I dont think just opening them and renaming and delting as needed is going to work because all the models have new channels also. It looks like when I just open one and tell it to use models its not showing correctly after that.
Trying to get import to work again but now only seeing pixel models and no single channel AC models.

[Phrog30]

Great news, xlights is all about models, not channels. You should try it first before you state it doesn't work.

Sent from my Pixel using Tapatalk

[Gilrock]

Yeah unless you were sequencing at the node level it will open just fine.  Only the model name matters for model level effects.

[jnealand]

Why import them?  Can't you just open them like normal?   For any models that no longer exist (renamed, for example), it will prompt if you want to map them to a different model or similar.

The reason I like to import last years is because I have more than one model and I have renamed a lot of stuff for simplicity.  If I open 8 sequences I have to do that renaming 8 times while if I import and create a mapping file I can effectively do the renaming once.

[mgholland]

Great news, xlights is all about models, not channels. You should try it first before you state it doesn't work.

Sent from my Pixel using Tapatalk

Well i did try it and it didnt come out correct. I am not saying Xlights dosnt work I am saying what ever was done the way I brought them in didnt work.  Will have to go back and retry and see if I am missing a step or something. Thanks fo the help

[mgholland]

Yeah unless you were sequencing at the node level it will open just fine.  Only the model name matters for model level effects.

not sequencing at the node level but I have got to be missing something that I am not thinking of or just out right missing a step or not have something configured correctly. Will try again maybe without changing chanels and channel number with offsets. I must have something set up wrong.  thanks for the help!

[mgholland]

Why import them?  Can't you just open them like normal?   For any models that no longer exist (renamed, for example), it will prompt if you want to map them to a different model or similar.

The reason I like to import last years is because I have more than one model and I have renamed a lot of stuff for simplicity.  If I open 8 sequences I have to do that renaming 8 times while if I import and create a mapping file I can effectively do the renaming once.

Yeay that is what I was kind of thinking too. That I wouldn't have to delete and rename models all over again in all my sequences .  Thanks!!

[dkulp]

The reason I like to import last years is because I have more than one model and I have renamed a lot of stuff for simplicity.  If I open 8 sequences I have to do that renaming 8 times while if I import and create a mapping file I can effectively do the renaming once.

You can use mapping files at Open time as well, but it's a little bit more annoying as for each unknown model, you have to say "map it" and then  the mapping dialog pops up. 

[mgholland]

The reason I like to import last years is because I have more than one model and I have renamed a lot of stuff for simplicity.  If I open 8 sequences I have to do that renaming 8 times while if I import and create a mapping file I can effectively do the renaming once.

You can use mapping files at Open time as well, but it's a little bit more annoying as for each unknown model, you have to say "map it" and then  the mapping dialog pops up.

May try this. Thanks Dan.