What do YOU (the user) want to see in Vixen 3? What feedback do you have?

**pjllah** · 07-15-2014, 04:45 PM

I would like to see Vixen 3 move over to the mac and linux user.

**Qbert-PNS** · 07-15-2014, 08:38 PM

The ability to move elements up and down in the programming list so you can set up sweeps and move elements for a different sweep.
This would be awesome.
Now you have to put them in the order you want them and limits effects.
This works well in LOR which I have moved from.

**jchuchla** · 07-15-2014, 10:03 PM

Qbert. If I understand your last two requests I think they've just been added. They should be in the next build.

-- Jon Chuchla --

Sent from my iPad using Tapatalk

**jchuchla** · 07-15-2014, 10:08 PM

Mac/Linux support isn't likely in the near term. The kinds of things that we're doing in the app would make it very difficult to port. When we rewrote the preview last year, we made the decision that we had to break with cross platform support to get the performance that users were demanding. The drawing routines in both the preview and the sequencer are heavily tied to windows accelerated methods.
What is more likely is the ability to export for playback on other systems.

-- Jon Chuchla --

Sent from my iPad using Tapatalk

**Spankyty** · 02-19-2019, 09:22 PM

Moving Heads!

**harpster** · 05-04-2019, 01:05 PM

I'd like to see the custom props feature working better. I had so may issues I just gave up. I could create the first instance (45 pixel snowflake) Ok but making duplicates just didn't work reliably. And naming all the pixels was a major headache and I think caused some of the problems I was seeing. I haven't gone back to look at this since January but I spent many frusterating hours on it and it's a feature I would really like to have working good. Also, just to be clear it's not the prop itself that is the problem, it's breaking the prop up into different groups, in my case I have ALL Pixels, Branches, Arrows and Stars grouped in one snowflake and it worked for the first snowflake I created but the copies made in the preview screen did not sequence right and editing them was a nightmare. Maybe some work has been done on this already, if so let me know... I need to get back in there to redo it all WAY before the holiday season starts. Thanks!

Thanks!

**jeffu231** · 05-06-2019, 09:04 AM

Originally Posted by harpster

I'd like to see the custom props feature working better. I had so may issues I just gave up. I could create the first instance (45 pixel snowflake) Ok but making duplicates just didn't work reliably. And naming all the pixels was a major headache and I think caused some of the problems I was seeing. I haven't gone back to look at this since January but I spent many frusterating hours on it and it's a feature I would really like to have working good. Also, just to be clear it's not the prop itself that is the problem, it's breaking the prop up into different groups, in my case I have ALL Pixels, Branches, Arrows and Stars grouped in one snowflake and it worked for the first snowflake I created but the copies made in the preview screen did not sequence right and editing them was a nightmare. Maybe some work has been done on this already, if so let me know... I need to get back in there to redo it all WAY before the holiday season starts. Thanks!

Thanks!

I think we would need to understand more about how you were doing things. It feels like you may be missing something in your approach. If you get the prop created correctly with naming tokens, you should just be able to import it multiple times and create the duplicate items you need. If you have not watched the video, I would encourage you to take a look at it. You can also create a separate thread about your process in the how to section and we can try to better help you work through it.

https://youtu.be/w6p6gcqfBTA

**harpster** · 05-11-2019, 12:58 PM

Thanks, I'm planning on trying to set this up again soon and I will document the process I use and take screen shots and will also watch the video again. I will create a separate thread as suggested when i have the data.

**Cmschleich** · 12-01-2019, 05:54 AM

More direct control of, or more intuitive if I am missing something, over the absolute address space. The more I do this the less I use (and think in) universe nomenclature, whenever possible. Falcon stuff is slick and that’s one of the reasons I think so.

Sent from my iPhone using Tapatalk

**jchuchla** · 12-01-2019, 11:04 AM

Vixen generally avoids the concept of absolute addresses everywhere except for the fpp export. Absolute addressing is a concept from xLights and FPP. It doesn't really exist outside of those products. In the grand scheme of things, most lighting hardware is addressed relative to the control protocol it speaks. So the way it currently is presented is a more universal approach.