Vixen Features

[Duke]

I'm an idiot

[biffklg]

Being new you probably don't know but KC makes vixen on his own and works for LOR making their software also.

[Duke]

DOH! I'm an idiot. What do I know?

[biffklg]

Why did you erase the rest of your post, there were other questions that could have been answered, make me look like an idiot now...

[ppohlman]

Makes more sense now. I thought I missed some sort of inside joke.

[Duke]

I erased it because I was totally embarassed. I had no idea that KC worked for LOR. But now that I'm back here it does raise the question that if KC is the author of Vixen and he is employed by LOR isn't that a conflict of interest in one software package versus the other? Now I'm really confused as to how Vixen can stay "alive" when the author of it works for a commercial company. Which software would get the newer features added to it first? Seems like priorities would be swayed by $$$$ and Vixen could be left to wither away with the exception of plug-ins or add ons. Very strange relationship indeed.

Back to my original post (and I have posted this in LOR's board as well) I had asked for the author(s) (in this case KC for both?) to take a look at midi sequencing software and adopt it's control features, GUI, track (channel) mute/solo, waveform, and in some cases video display and roll them into Vixen/LOR2. Unless I'm missing something (idiots like me usually do) would it not be a lot easier to write a plug-in to work with s'ware already on the market and have the midi sequencing s'ware control the boards rather than starting from scratch? There is a free (For 30 days) trial version that can be downloaded from here:
http://www.cakewalk.com/Support/kb/kb20061101.asp
Take a look at it, try it out, play with its control and editing features and I think it will be clear in regards to editing features. Granted Sonar has wayyyyy more capabilities than we would need for light controllers but I'm just asking for them/him or anyone to do with this stuff to have a look at it. Then fire up Vixen or LOR2 and see what's missing. You'll get the idea.

[Trepidati0n]

KC made Vixen before he went to LoR. That is why LoR hired him AFAIK. As long as LoR is aware that he is writing Vixen...there is no conflict of interest. Also, what better way to improve LoR than to use Vixen as a "beta test" grounds for people who think bugs are opportunities to fix something ;)

[RavingLunatic]

Duke,

Since you are new, a short history lesson.

KC developed Vixen first, then the folks at LOR realized what a talent he was and hired him last spring/summer.

As far as the relationship between what KC does for LOR and Vixen, that is entirely between him and LOR.


Now on to your suggestion/request...

Again since you are new I'll try to be gentle.

When you are making suggestions/requests for features you need to be specific about what you are looking for and how it might work. Using the generic "look at this software and you'll see" won't get much action.

I'm sure you now realize that KC is a pretty busy man and doesn't have alot of free time to work on Vixen as it is, so he sure doesn't have time to d/l and evaluate new software looking for new features.

KC has always been very agreeable about making changes and adding features but it makes his life alot easier when you can provide as many details as possible when making a request.


Now dig deep into Vixen and figure out what you think can be improved and how it might be done. It is the job of the whole community to make Vixen the best it can be.


Oh yeah, Welcome to DIYC!