-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Importing NUTCRACKER into VIXEN #31
Comments
Please always include your target, user and effect name. 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. |
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... |
this one too |
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 |
Where do i get the fix for vixen? Ill try it
|
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:
|
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). |
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. Sent from my iPhone On Sep 30, 2012, at 1:53 AM, kgustafson notifications@github.com wrote:
|
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] 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). — Image removed by sender. |
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] 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 — Image removed by sender. |
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!) |
when i imported my files into vixen, the FIRST file i have to remove several frames at the beginning manually
The text was updated successfully, but these errors were encountered: