Notifications
Clear all

Vixen3

14 Posts
8 Users
0 Reactions
6,342 Views
Posts: 631
Topic starter
(@stampedeboss)
Honorable Member
Joined: 13 years ago
[#37086]

While I love the design of Vixen3 and the approach you have taken on elements and sequencing, I believe you choice of programming language and Microsoft .Net will eventually doom Vixen3. Most people will not, can not afford or wish to upgrade computers every year to keep up with the software bloat of MS.

I for one feel forced to make a decision and I am moving on to XLights due to the excessive compute resources needed by Vixen3. Xlights is far less resource intensive, but is not as easily configured as Vixen. It may take me more time, but that's allows me to spend my funds on more pixels and props instead of computer upgrades. By the way I also have a 8 Core Desktop that is starting to struggle due to the large size of my display this year. After upgrading to the new .Net, I can no longer sequence or even run my older sequences on my 1 year old mid-level laptop. I have been in the IT industry for over 30 years and see that even now many larger companies are starting to abandon the MS development suite for faster and nimbler options. Microsoft has never been known for efficient utilization of resources

The subject of language choice has always been a religious debate in the industry and I'm not trying to say your current choice is bad, just that your compute needs are excessive. Many of the large compute demands would be significantly reduced with C++ or other lower overhead language choices.

I fully realize you use the tools you know, but please take a look at compute demand requirements, I strongly believe your design and approach are the most superior among all the sequencers. I am sad that it appears Vixen3 is no longer available to me.


13 Replies
jchuchla
Posts: 8698
(@jchuchla)
Illustrious Member
Joined: 15 years ago

A lot of the resource requirements have more to do with the design model than the choice of language. The very things that you praise are the things that take a lot of work. Vixen 3 is the only sequencer (that I know of) that works at a high level and performs real time rendering of every effect on every element. Without this engine doing all of the work on the fly, all of the flexible goodness would be lost.
We're well aware that it takes a big computer to design a big show using vixen, but in all reality that doesn't seem to come into play with most users. We know where the bottlenecks are and how to fix them but it's really a huge undertaking that will completely stall any other new features for years. When it comes down to it, it just hasn't been a big enough problem that drives any of us to tackle it. And vixen 3 is way too far along to change languages. It would be easier to start over than to port it at this point. Porting would be more work than fixing the actual problem. Maybe vixen 4 will start in a new language?
Most of us are developers of some sort. I personally look at it this way: a good powerful computer can be had for less than $900. That's the same value as 6 hours of my billable time. That same number is a small percentage of my annual Christmas budget. So it seems like a fair amount to spend (as opposed to wasting time) to get a good size show running. At the same time, I sequence very effectively using a 2010 MacBook. It's a nice machine but not exactly a brand new modern powerhouse. My show runs from a core 2 duo that I bought as a refurb for $150 two years ago. I sequenced and ran a 10 universe show last year without performance issues (that weren't bug related). It's not exactly a huge show. But it's on the higher end of the mid range.
That being said the new version (forthcoming) is more responsive than the last. Since the last release, there's been a lot of improvements on inefficient routines. The new version will require .net 4.5.2 and that upgrade alone has provided a good jump in performance due to better efficiencies in .net memory management. It will continue to get better and better but we can't promise it will be at the same speed that you grow your show. More likely, it will improve to suit the needs of the devs writing it. If our shows grow beyond vixen's sweet spot, that will likely drive us to make it work better, I faster and smarter. Most of the features and priorities in the past 3 years have been driven solely by one of us getting frustrated or wanting a better way to do something. There's a lot of that coming in the next release.

--Jon Chuchla--

Sent from my iPhone using Tapatalk


Reply
Posts: 853
(@roterhead)
Prominent Member
Joined: 15 years ago

With the release of DotNet as Open Source I expect some of the Non-Windows community make look at this differently. Obviously this has a way to go, however I just see DotNet getting better and better.

For me, the flexibility of the V3 Object Model is way better than Grid Sequencers for large models, but that is my opinion and to each their choice, which is the great idea of what we have in this Hobby. Heck, many people just gotta have LOR...

Having said that, I find the changes in XL.NC V4 to be very interesting. Adding models into that symphony was a very good move and I see this as a validation of the V3 direction. I've tried the new version and I like it and I can see how the choice between XLNCv$ and V3 is now more difficult. I think when V3 is released with it's new version people will find many things they like. My fear is this may be too late for people to choose for their displays this year... I would love to help in V3 but my spare time has gone from "Some" to about "0DegK" and cannot help.


Reply
Posts: 1049
(@phrog30)
Noble Member
Joined: 12 years ago
Roterhead wrote:My fear is this may be too late for people to choose for their displays this year.

I couldn't agree more. This was the devs choice. They think most don't work on things until September. So, a summer release is not bad. But like you said, it will be hard for the new users.


Reply
brianweb
Posts: 245
(@brianweb)
Reputable Member
Joined: 13 years ago

Many users are using Falcon Pi Player to run their Vixen 3 shows. The V3 team adding that option last year kept a lot of people on Vixen 3 for its design and user interface, but then have the FPP do the heavy lifting. You can drive thousands of pixels and more without a single hiccup from the Pi, all for less than $50. I also don't have to worry about running Ethernet from the house out to the display since I have the Pi tucked away in one of my CG boxes.


Reply
Posts: 853
(@roterhead)
Prominent Member
Joined: 15 years ago

Yup. I now have three PIs for this very reason...


Reply
TazChaLet
Posts: 3042
(@tazchalet)
Famed Member
Joined: 13 years ago

after testing them all for a while I used the sequencer in vixen 3 and then exported it out too a vixen2.1 file so I could import it into xlights and use the scheduler too run show with a old xp computer I have I love vixen 3 for the way it works as a sequencer I dont have money for a new show computer and my main computer I use daily so didnt wanna use it for show


Reply
jchuchla
Posts: 8698
(@jchuchla)
Illustrious Member
Joined: 15 years ago
Phrog30 wrote:I couldn't agree more. This was the devs choice. They think most don't work on things until September. So, a summer release is not bad. But like you said, it will be hard for the new users.

We actually do quite a bit of data collection in deciding what to work on and when. Sure there's some people working on sequencing now. But not that many. And those that are, tend to be seasoned vets that are taking their time and are fairly comfortable with the status quo. The vast majority of people ramp up on sequencing in September. And even still, these tend to be experienced blinkers. The newbies tend to show up in droves the week before thanksgiving trying desperately to wrap their head around everything that "didn't seem so hard" on the surface. This has been the pattern we've been seeing for the past several years. So much so that I actually plan my vacation schedule (from my day job) around the thanksgiving rush.
We're getting close to a release. Our user base is so big now that we really don't like releasing features prematurely. If you must get your hands on this stuff early, you're more than welcome to try the development builds, they've been pretty stable lately. (standard warnings apply). Just make sure to practice safe backups and such when using them. Especially within the first few days of them being posted. We do take down the bad builds when they happen, but it often takes us a few days to even discover there's a problem. If it's been up there for several days, chances are it's safe enough to use without major problems.

--Jon Chuchla--

Sent from my iPhone using Tapatalk


Reply
Posts: 1049
(@phrog30)
Noble Member
Joined: 12 years ago

Jon, just a curious question, do you have a guess on how many use Vixen 3?


Reply
Posts: 686
(@traneman)
Prominent Member
Joined: 16 years ago

I use it


Reply
Page 1 / 2
Share: