Results 1 to 5 of 5

Thread: Export to Vixen 2.1

  1. #1
    Join Date
    Mar 2010
    Location
    Delaware, OH
    Posts
    670
    Post Thanks / Like

    Default Export to Vixen 2.1

    Vixen 3 now has the ability to export sequences to Vixen 2.1, beginning with development build #37.

    As with the other export types, you should have all of your required display elements to controller outputs fully patched in the Display Setup.

    The output file is a flattened sequence with each channel names based upon the Vixen 3 element name.

    Enjoy! (And report any bugs you may find!)

    Ed

  2. #2
    Join Date
    Dec 2011
    Location
    Xenia, Ohio
    Posts
    1,354
    Post Thanks / Like

    Default Re: Export to Vixen 2.1

    Now you are making it hard not to try V3. I was going to wait until after this season but I may have to give it a shot now.

    Thanks for all your work on this Ed.
    [COLOR=#008000]2016 - 5th. year - Over 18,000 channels E1.31 including 350 Channels Renard, Video Projection - XL/NC - On Falcon Player, up to four megatrees.
    [/COLOR][COLOR=#008000]2017 - 6th. year - Moved display to a public park, Over 45,000 E1.31 channels, down to 100 Channels of serial Renard - XLights running on Falcon Player on a raspberry PI.[/COLOR][COLOR=#008000]
    2018 - 7th, year - Still at Shawnee Park, over 52,000 E1.31 channels, down to 96 channels of Renard - [/COLOR][COLOR=#008000]XLights running on Falcon Player on a raspberry PI.
    [/COLOR][COLOR=#008000]
    [SIGPIC][/SIGPIC]
    [/COLOR]
    Randy: X[URL="http://www.xenialights.com/"]enialights[/URL] on [URL="https://www.facebook.com/pages/XeniaLights/420036314711206"]Facebook[/URL]

  3. #3
    Join Date
    Nov 2011
    Location
    Chicago - Southwest Suburbs
    Posts
    7,961
    Post Thanks / Like

    Default Re: Export to Vixen 2.1

    I just wanted to point out that while vixen 3 can both export and import from vixen 2 format your workflow should not bring these files back into v3. As Ed pointed out, these files are "flattened" which means that all of the intelligence that the effects had in V3 Is lost on export. The vixen 2 format does not support all of the advanced features that makes vixen 3 so easy to use. So what you reimport will most likely not contain the same easy to edit effects that you exported. And also, this reimported file will require a lot more pc overhead to process all the extra small effects.
    For example, If you were to export a pulse effect that fades in, when you reimport, you might get 20 set level effects instead.
    So the intended workflow for tees tools is as follows:
    If you have old sequences created in vixen 2, or any other timeslice based sequencer, you can import them into V3
    Once you've imported these sequences into V3, you should consider this result as a reference for reworking it in the V3 style. You would go thru the sequence and look for effects that can be condensed by using the power of V3 effects.
    When your sequence is complete, you can then export it as a vixen 2 file for playback in another scheduler like xlights. Or you could export it in Fseq format for playback on the falcon player.
    If you want to add a few nutcracker effects that aren't available in vixen 3 using the newer version of nutcracker you can do that after you've exported from V3 and on it's way thru the xlights workflow.


    --Jon Chuchla--

    Sent from my iPhone using Tapatalk

  4. #4
    Join Date
    Dec 2010
    Location
    Griswold, Connecticut
    Posts
    318
    Post Thanks / Like

    Default Re: Export to Vixen 2.1

    Thanks for the info and heads up. I'll look forward to using this.

    Regarding nutcracker effects not available in V3: If I understand you correctly if these nutcracker effects are brought in after exporting from V3 on the way through xlights, these effects would need to be re-done each time the reference V3 sequence is modified. In other words since we shouldn't import anything done outside of V3 the reference file wouldn't include these nutcracker effects that can't be done within V3?

    Or is it just V2 files that won't contain all of the information when imported to V3?

  5. #5
    Join Date
    Nov 2011
    Location
    Chicago - Southwest Suburbs
    Posts
    7,961
    Post Thanks / Like

    Default Re: Export to Vixen 2.1

    It's the first concept.
    The reason is because when you import into vixen 3, the importer has to guess what kind of effect that you were going for so that it can choose the correct vixen 3 effect to take its place. It can handle basic fixed levels and some linear ramps and fades, but anything more complicated than that will be converted as many tiny effects. And that will become almost impossible to work with in V3 and it will bog down the system. The importer may recognize some parts of a NC effect as fades and such. But it will be one huge mess of disconnected little effects. The import will take forever, and the file will be very difficult to work with.
    The good news is that we are exploring ways to directly integrate the nutcracker code into V3 so that it will stay up to date with Sean's progress on nutcracker. The way it stands today, nutcracker and vixen 3 are written in two different languages and it has to be translated by hand to bring any of Sean's work into V3. So updates he makes take a long time (and someone whos willing to do the tedious work) to make it into V3.


    -- Jon Chuchla --

    Sent from my iPad using Tapatalk

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •