smeighan / nutcracker

RGB Effects builder for Chistmas Animations
15 stars 15 forks source link

Importing NUTCRACKER into VIXEN #31

Closed keebler125 closed 11 years ago

keebler125 commented 12 years ago

when i imported my files into vixen, the FIRST file i have to remove several frames at the beginning manually

smeighan commented 12 years ago

Please always include your target, user and effect name. OR just paste the url from yoru animated gif. The url has all 3 bits of info.

it would help if you could make a video of this? I am not familiar with vixen so i would like to undertand the issue.

gsxrgirl7 commented 11 years ago

Sean it does the same with mine - in vixen as well, where once they are pasted it has like a string or two or a blurp of lines, i dont necessarily remember it doing that in LOR on the imports, or if it did, it was not near as noticeable. i do have a video on my iphone from vixen if you would like to see how it makes it jump abruptly. where would you like me to send it to or email it to? Here are a couple of links to my gifs that it does it to... http://meighan.net/nutcracker/effects/workspaces/419/JULIE_TESTER~RTOG_SPARKLESPIRAL1.gif

gsxrgirl7 commented 11 years ago

this one too http://meighan.net/nutcracker/effects/workspaces/419/JULIE_TESTER~CANDYCANE3_1.gif It does others, but was pretty noticeable in these two

kgustafson commented 11 years ago

gsxrgirl7 and keebler, need to know if you still have issues with Vixen from the "Kurt Project" export. I did a lot of reverse engineering into the crazy way that Vixen stores the vix file (trust me, it is crazy--but elegant in a way) and I am not seeing any issues now when I run my output on Vixen (which happens to be the sequencer I use the most).

Kurt

keebler125 commented 11 years ago

Where do i get the fix for vixen? Ill try it On Sep 30, 2012 1:53 AM, "kgustafson" notifications@github.com wrote:

gsxrgirl7 and keebler, need to know if you still have issues with Vixen from the "Kurt Project" export. I did a lot of reverse engineering into the crazy way that Vixen stores the vix file (trust me, it is crazy--but elegant in a way) and I am not seeing any issues now when I run my output on Vixen (which happens to be the sequencer I use the most).

Kurt

— Reply to this email directly or view it on GitHubhttps://github.com/smeighan/nutcracker/issues/31#issuecomment-9011372.

gsxrgirl7 commented 11 years ago

Ok I will have to test it and see. Thanks for the update and I will check it today and let you know!

Julie

Sent from my iPhone

On Sep 30, 2012, at 1:53 AM, kgustafson notifications@github.com wrote:

gsxrgirl7 and keebler, need to know if you still have issues with Vixen from the "Kurt Project" export. I did a lot of reverse engineering into the crazy way that Vixen stores the vix file (trust me, it is crazy--but elegant in a way) and I am not seeing any issues now when I run my output on Vixen (which happens to be the sequencer I use the most).

Kurt

— Reply to this email directly or view it on GitHub.

kgustafson commented 11 years ago

Just download the from github to your local. If you are using Meighan.net, the fixes are already in (although Meighan.net tends to lag github by a few days -- which is because we do extensive testing before committing all code to the 'production' server).

gsxrgirl7 commented 11 years ago

Sorry I have not been able to respond yet. Things got really hectic the last several days. I will try to test it tonight as I had hoped to the other day. And let you know.
Sorry for the delay. Julie

Sent from my iPhone

On Sep 30, 2012, at 1:53 AM, kgustafson notifications@github.com wrote:

gsxrgirl7 and keebler, need to know if you still have issues with Vixen from the "Kurt Project" export. I did a lot of reverse engineering into the crazy way that Vixen stores the vix file (trust me, it is crazy--but elegant in a way) and I am not seeing any issues now when I run my output on Vixen (which happens to be the sequencer I use the most).

Kurt

— Reply to this email directly or view it on GitHub.

keebler125 commented 11 years ago

OK, sorry got REAL hectic here lately,

Will d/l the fix and apply it and hopefully test it tonight.

Thank you

K

From: kgustafson [mailto:notifications@github.com] Sent: Monday, October 01, 2012 9:19 AM To: smeighan/nutcracker Cc: keebler125 Subject: Re: [nutcracker] Importing NUTCRACKER into VIXEN (#31)

Just download the from github to your local. If you are using Meighan.net, the fixes are already in (although Meighan.net tends to lag github by a few days -- which is because we do extensive testing before committing all code to the 'production' server).

— Reply to this email directly or view https://github.com/smeighan/nutcracker/issues/31#issuecomment-9033418 it on GitHub.

Image removed by sender.

keebler125 commented 11 years ago

Just checked it in VIXEN2.14

Works fine (thank you)

That leaves just one more problem

The color correction.

As I told sean, the colors that I create in nutcracker are WAY of fin vixen.

I am using ws2801 pixels

I showed sean a chart I made in excel showing the colors that I wanted to use in nutcracker and the way I had to modify them to (with the new hex codes) to make them work in vixen.

Sean said there might have been a way to adjust the intensity in nutcracker, but I have no idea how to do that.

Thank you again

Ken

From: kgustafson [mailto:notifications@github.com] Sent: Sunday, September 30, 2012 1:53 AM To: smeighan/nutcracker Cc: keebler125 Subject: Re: [nutcracker] Importing NUTCRACKER into VIXEN (#31)

gsxrgirl7 and keebler, need to know if you still have issues with Vixen from the "Kurt Project" export. I did a lot of reverse engineering into the crazy way that Vixen stores the vix file (trust me, it is crazy--but elegant in a way) and I am not seeing any issues now when I run my output on Vixen (which happens to be the sequencer I use the most).

Kurt

— Reply to this email directly or view https://github.com/smeighan/nutcracker/issues/31#issuecomment-9011372 it on GitHub.

Image removed by sender.

kgustafson commented 11 years ago

Okay, I see we have a separate bug track for the color issue, so I will close this as I think we are working in Vixen (just no color correction yet!)