Author Topic: Import problems  (Read 2472 times)

Offline Oldgezzer

  • Newbie
  • *
  • Posts: 12
    • View Profile
Import problems
« on: August 09, 2016, 08:30:18 PM »
I am trying to import last years sequences to this year's new and different layout, with no luck.  I am using 2016.44 version.  I have a working layout with some new songs already functioning which use all of the basic models  form last year minus some and with RGB lights added to some.  When I try to import  last years songs all goes well up to the point of mapping.  The models for current year are all present but when trying to call the old models to choose from I get a list with either missing models or a list with most of the models not even active for that song.  I even went back and made sure the view for last year had all of the models.   I have run all the old songs with the current version and saved them with no problem.  I must be doing something wrong.  Please help.

Offline danj

  • Hero Member
  • *****
  • Posts: 895
    • View Profile
Re: Import problems
« Reply #1 on: October 05, 2016, 09:08:22 PM »
Having the same problem here.  Did you ever get any PMs or anything on this one??

Here's what I am seeing.   I posted earlier this year and developed a mapping file that worked for a few sequences back in May 2016 timeframe.   I should have moved everything over then but I didn't.  Anyway, when I either do the steps in the manual or try to use the mapping file from the spring, I am only seeing two selections, 3m megatree and 5m megatree, from last year's setup, whereas I also had 6 arches and 16 minitrees that should be showing up in the drop down (I think???).   I pulled up the rgbeffects xml from last year's folders and I am seeing all models there.   Is that where xlights pulls from for the drop down when mapping sequence info from last year's models to this year's models?   I also am able to run the 2015 sequences with the 2015 setup, so that looks good at least when looking at last year's overall setup!!   

...sure I am missing something easy; usually the case....
« Last Edit: October 05, 2016, 09:41:02 PM by danj »

Offline jnealand

  • Hero Member
  • *****
  • Posts: 1421
    • View Profile
Re: Import problems
« Reply #2 on: October 06, 2016, 08:36:57 AM »
I have just imported multiple sequences to map to my 2016 layout without any system problems.  A few thoughts/notes

- Keep the old and new sequences in different folders.  ie. 2016 Christmas is current sequences and 2015 Christmas has the old sequences.
- It takes multiple clicks in the box on the right side to bring up the list of models in the old sequence.  You can also dbl click the old model to get it to expand.
- Watch out for effects that may not be at the model level, but underneath them in strands.  I found this one with a star that had 3 strands/sub models of inner, middle and outer.
- Be careful with the mouse scrolling wheel.  After you select an element in the old sequence if you scroll the wheel the selection changes and you may not notice.  This one caught me big time.
- If you have a map file loaded and you make changes it is possible to save it with the same name or you could make multiple map files for different scenarios - one for mega trees, one for yard elements only, one for house mounted elements only, etc  just be sure to name them appropriately.  You can rerun a map file on a sequence that has already had an import done on it once, but you will lose anything you might have changed since the first element.
Jim Nealand
Kennesaw, GA

Offline Gilrock

  • Supporting Member
  • Hero Member
  • *
  • Posts: 6946
    • View Profile
Re: Import problems
« Reply #3 on: October 06, 2016, 09:42:18 AM »
danj you need to add the models to a sequence before they will be available in the dropdown for mapping.  You can use a premade view or the All Models option with the Quick Start button when creating a sequence to automatically get all the models in your sequence.

Offline danj

  • Hero Member
  • *****
  • Posts: 895
    • View Profile
Re: Import problems
« Reply #4 on: October 06, 2016, 11:20:34 AM »
Thanks for the replies.   I'll play around with this a bit when I get home tonight.   I may not have added the models to the new sequence.  I saw all the models/groups on the sequencer screen so I thought they were there & ready to go...   But maybe not.  I'll check that carefully tonight.   And I'll be very careful as Jim noted.

THANKS

Offline danj

  • Hero Member
  • *****
  • Posts: 895
    • View Profile
Re: Import problems
« Reply #5 on: October 10, 2016, 09:09:22 PM »
I fooled around with several 2015 sequences tonight and even kind of surveyed some of the 2015 to 2016 sequences for which I was able to import the 2015 sequence into the 2016 files earlier this year..    Found nothing that jumps out at me.    I'm sure I am missing something easy.   I did exactly as you suggested, Gil and tried both of the routes written in the manual (new sequence/existing sequence)---opened up new/existing sequence, chose all models under the quick start menu (for the new only of course...) to make sure all the models are present in the sequencer, saved, then opened up import effects to map the 2015 models to the 2016 models using the 2015 files from the 2015 folder.  That was a no go.   I am only typically seeing two of the 2015 models in the mapping dropdown, two 2015 megatrees.   I tried several different sequences to see if there was any difference from one to another; in that case I am also seeing all 60 strands of arch #1 (out of 6 arches total) and the "arches" model.....all in the mapping dropdown...  Any more ideas?  I'm just about at the point where I am ready to start re-sequencing these.  I posted my 2015 & 2016 rgbeffects files in case that might shed some light on some little thing I am missing....   THANKS

Edit 10/11/16--I opened up one of Tindivall's sequences that he shared last year the way the manual says to do it, and all of his models are showing up in the drop down; no problems there...   So I mapped eight arches as a check, saved, and I am seeing the effects he set in my 2016 models--no problems there!!!   So, I guess I am doing something wrong when trying to use my own 2015 files or somehow goofed those files up when trying to map...   Any ideas???
Thanks.
« Last Edit: October 11, 2016, 07:24:52 PM by danj »

Offline sean

  • Administrator
  • Hero Member
  • *****
  • Posts: 1727
    • View Profile
    • Xlights and Nutcracker Forum
Re: Import problems
« Reply #6 on: October 12, 2016, 08:35:12 AM »
please also post the mapping file you are using and a 2015 sequence xml file.

we cant duplicate what you are seeing without both. also a video of you going through the import process would be helpful.
Sean
Littleton, CO
Latest releases http://nutcracker123.com/nutcracker/releases
xLights/Nutcracker Forum http://nutcracker123.com/forum/index.php
Fbook [url=https://www.facebook.com/groups/62

Offline danj

  • Hero Member
  • *****
  • Posts: 895
    • View Profile
Re: Import problems
« Reply #7 on: October 12, 2016, 04:51:29 PM »
Thanks Sean.   Here is the mapping file that I thought I successfully saved this spring that I used to pull a few xml files from 2015 folder into 2016 folder, along with an example 2015 sequence xml file.   I will do a screen capture with how I am doing the steps in a few minutes.   I am pretty sure I am doing the steps correctly because I was able to use one of Tindivall's sequences last night with no problems whatsoever.

I was not able to save a vid file; too big.   I am pretty sure the method I am using works since I was able to use one of Tindivall's sequences last night and this afternoon with no problems.    So I think I am good there...

When I look at the mapping xml file, though...   I am 100% that I mapped everything (May 2016 timeframe) from last year's models to this year's models.  But the mapping file doesn't represent that now; it only shows half of the minitrees I mapped and none of the RGB models.   

10/13/16 edit:
I tried using v32 of xlights, which is about the version I was using when I successfully mapped my channels on some sequences earlier this year (on another PC).   I was thinking maybe changing PCs between then and now was a potential impact (both running W10, so not likely I realize....).   No difference there either (I expected no change but figured it was worth a shot).   I was not able to pull my own channels over from 2015 to 2016 but I was <again> able to use the channels from Tindivall's shared sequences from last year.

Is there anything I could do inside the mapping xml file maybe??  I would sure like to be able to pull over the sequencing I did on my minitrees in 2015 into 2016 and not have to redo it....
thanks.
« Last Edit: October 14, 2016, 08:53:21 AM by danj »

Offline danj

  • Hero Member
  • *****
  • Posts: 895
    • View Profile
Re: Import problems
« Reply #8 on: October 14, 2016, 08:54:57 AM »
Last night I tried using v32 of xlights, which I think is the version I was using when I successfully mapped my channels on some sequences earlier this year (on another PC).   I was thinking maybe changing PCs between then and now was a potential impact (both running W10, so not likely I realize....); the PC I was using in early spring totally died on me, but I was able to get the files from it before it totally kicked the bucket.   Using v32 did not work either (I expected no change but figured it was worth a shot).   I was still not able to pull my own channels over from 2015 to 2016 but I was <again> able to use the channels from Tindivall's shared sequences from last year.

Is there anything I could do inside the mapping xml file maybe??  I would sure like to be able to pull over the sequencing I did on my minitrees in 2015 into 2016 and not have to redo it....
thanks.

Offline jnealand

  • Hero Member
  • *****
  • Posts: 1421
    • View Profile
Re: Import problems
« Reply #9 on: October 14, 2016, 01:55:52 PM »
In the Groove gallery sequence there are no mini tree effects.  Maybe you are thinking of stuff in the iseq file.  I'm not a LOR user and have not converted any effects so I  do not know how that works.  The only effects I can find in that sequence are in the two mega tree models and the arches.

But you are correct in that the mini tree models do not show up in the mapping window.  I wonder if that is because they are defined as LOR models?
« Last Edit: October 14, 2016, 02:56:11 PM by jnealand »
Jim Nealand
Kennesaw, GA

Offline danj

  • Hero Member
  • *****
  • Posts: 895
    • View Profile
Re: Import problems
« Reply #10 on: October 16, 2016, 08:37:15 PM »
John-thanks for looking at the files.   I can see the effects on the minitrees in the sequence panel (you are right; the mini trees were originally sequenced in LOR....).   Out of curiosity, I tried to copy the sequence effects on those models in the 2015 sequence and found that they are not "copyable".  For comparison, the RGB sequence effects I sequenced in xlights can be copied....    Regardless of the copyable/not copyable thing.... I was thinking if I had the xlights models laid out in the sequence and the models are showing up in the sequence panel, I should be able to map the models from year to year.   You might be right..   I am sure I sequenced those particular on's & off's in LOR....