Isadora 3 - Status Report from Mark

mark

Exciting. @Mark, how did you get around NiTE's licensing restrictions, which prohibit using it with non-Primesense devices and prohibit redistributing it?

Uh, well, I guess I wasn't aware of that particular restriction. From that license agreement:

You shall not (and shall not permit third parties to): (a) integrate the NITE with any products other than the Authorized Hardware; (b) distribute the NITE in any manner; (c) use or make available the NITE pursuant to an open source license; (d) modify the NITE;

There are other drivers out there (libfreenect2) that allow you to use NITE with Kinect 2, which is not a Prime Sense device, which is in violation of clause (a).

Obviously Processing, NI Mate and others are distributing the library, which is in direct violation of the clause (b)

I would guess that this github is in violation of clause (d) because it includes NITE.

In other words, there Prime Sense (which was bought up by Apple) don't seem to be enforcing this or going after people. They don't even have a website anymore (the URL www.openni.org reroutes to Apple.) But, now that I'm aware of this, we may simply have to ask people to install NITE themselves if they wish to use that part of the system.

We will investigate further.

Best Wishes,
Mark

bonemap

@kurt said:

how did you get around NiTE's licensing restrictions, which prohibit using it with non-Primesense devices and prohibit redistributing it

How can this be considered evidence of a current license? It appears to be linked to a the Internet Archive's capture of a discontinued Openni website dating from 2014. There appears to be no directly accessible current/active reference to the functioning Openni.org enterprise or the licensing agreement that is referenced in the archive.

It appears a bit harsh to sign up to this form and drop what appears to be a redundant licensing clause without pointing to current information or specifications.

Please correct me if I am wrong.

best wishes

bonemap

kurt

That's the most up-to-date NiTE licensing information available, since Apple took down the website.

I just don't want to see TroikaTronix sued by Apple's less-than-magnanimous legal team — that would be bad for all of us.

mark

@bonemap said:

It appears a bit harsh to sign up to this form and drop what appears to be a redundant licensing clause without pointing to current information or specifications.

Well, I appreciate knowing this actually. We have to take care with these things. I mean, it super easy to install NiTE on MacOS using Homebrew, and just a tiny bit more tricky on Windows (though it could probably be handled by a script.) If we force the users to install it then I think we're safe. (Homebrew, by the way is another indication about this: https://github.com/totakke/hom...)

Still, I'll write on the github for the Processing plugin I mentioned above and see what they say.

Best Wishes,
Mark

ppp586

@mark said:

@bonemap said:
It appears a bit harsh to sign up to this form and drop what appears to be a redundant licensing clause without pointing to current information or specifications.
Well, I appreciate knowing this actually. We have to take care with these things. I mean, it super easy to install NiTE on MacOS using Homebrew, and just a tiny bit more tricky on Windows (though it could probably be handled by a script.) If we force the users to install it then I think we're safe. (Homebrew, by the way is another indication about this: https://github.com/totakke/hom...)
Still, I'll write on the github for the Processing plugin I mentioned above and see what they say.
Best Wishes,
Mark

Hi，Mark

I know that Millumin software support Kinect v2 in Macos ,and it is easy to use that the software check the kinect and install the drivers for it automatically.

Could you tell me our Isadora V3 will support the kinect V2?

Thank you！

Jimmy Zhang

Woland

@ppp586 said:

Could you tell me our Isadora V3 will support the kinect V2?

It is our plan to include this, yes.

deflost

hello all, and a happy new year.

what is with asio and vst support in win version, it was promissed so often, till years? is it in?

thx for answer...

r.h.

Juriaan

@deflost

Hi there,

It is unsure, one of the Isadora Staff have to answer it, there are no signs about it in the released news sources on the forum so I doubt it.

@Woland Could you please ask Mark or this feature is planned for the upcoming 3.0 release, honestly this is a feature that we really need to make sure that Isadora stays relevant for Interactive work / installations / theatre pieces that rely on multiple audio outputs / multiple audio inputs + audio support for Windows of Isadora doesn't cut it.. Thanks buddy :)

Eamonn

Hello,

I was wondering if there are any updates or rumors floating out there about when the big 3.0 release will be. I'm heading into a tech in a couple weeks for a big show with ten outputs and dreading the prospect of having to program it on Qlab...

Thanks,
Eamonn

ksateler

Hi, any news about the release date? I lost my isadora usb key, and I prefer to wait for version 3 for buy again, because if I buy the old version 2.6, then I pay again for the upgrade.

Woland

@ksateler said:

if I buy the old version 2.6, then I pay again for the upgrade.

Actually a new USB Key Isadora 2 license would cost you $535 and the upgrade to Isadora 3 would only cost you $100 (since you'd have bought it after March 28th, 2018). Total cost: $635

The price for a new Isadora 3 USB Key License is $650.

AshChristopher

Really looking forward to this!

GoddessMoon2017

@woland is there a projected date to when the new Izzy will be available?

Woland

@goddessmoon2017

As soon as we have an official release date, we'll be sure to post in on the forum, Facebook, etc. :)

Fred

@woland

I know this is a tough question, but I am liking the features of V3, I have been very busy on projects so not a lot of time for testing, but I am in a bit of a bind. I have a project that is presenting in 5 weeks. I have to finalise the software I use and I would prefer go with V3. It has been 3 months since the initial beta and lots of radio silence in between. Instead of a release date is it possible to get an end deadline, a date when the new version will definitely be done, I would like to put Isadora as the tool I will use but need to commit very soon.

Woland

@fred said:

@woland I know this is a tough question, but I am liking the features of V3, I have been very busy on projects so not a lot of time for testing, but I am in a bit of a bind. I have a project that is presenting in 5 weeks. I have to finalise the software I use and I would prefer go with V3. It has been 3 months since the initial beta and lots of radio silence in between. Instead of a release date is it possible to get an end deadline, a date when the new version will definitely be done, I would like to put Isadora as the tool I will use but need to commit very soon.

I will discuss this with Mark on Monday and get back to you. We are all working as hard as we can on Isadora 3, especially Mark.

Bennnid

1st Thanks for you amazing work !

Do you have an idea of a

month regarding the release? waiting to choose the osX update...

thanks a lot !

Juriaan

@bennnid

Hi there, sadly there is no release date yet. They are working around the clock to get it out :) Keep an eye out on the social platforms of Isadora to get a notifaction when the new version is out :)

mark

@fred said:

I know this is a tough question, but I am liking the features of V3, I have been very busy on projects so not a lot of time for testing, but I am in a bit of a bind. I have a project that is presenting in 5 weeks. I have to finalise the software I use and I would prefer go with V3. It has been 3 months since the initial beta and lots of radio silence in between. Instead of a release date is it possible to get an end deadline, a date when the new version will definitely be done, I would like to put Isadora as the tool I will use but need to commit very soon.

Hello everybody, it's Mark, rising from the bowels of coding.

I know everybody wants us to set a date. And, the fact is, we have a date in mind that's not very far away. So then, you might rightly ask, why are we not saying that date out loud?

Because we don't want to promise something and then not make it, which we've already done with our original release date.

I've consulted with two close colleagues -- one who worked at Apple for many years and other who has been a consultant to Adobe since Photoshop 1.0 -- in other words, high level experts. I tell them I'm freaking the "f" out because we're late, and they both say the same thing: don't rush because of your anxiety. If you release a dog you'll lose users forever. If you're late, they'll forgive you.

And that's the road we're taking.

Four weeks ago there were 110+ significant crashes listed in our bug database. Now there are 16 -- some of which only happen under relatively unusual/bizarre situations. As of this Monday (Feb 4) there were 210+ "failures" (i.e., stuff not working right, importance varying from significant to cosmetic) and now, three days later, that number is 150. These failed items will fall off relatively quickly.

In addition, we have had two special beta testers -- one on Mac and one on PC -- that are using the beta for significant projects that are live right now. Because of this, a handful of super serious bugs and/or reliability issues that might have escaped our attention have been fixed.

In other words, it's getting close. And I do believe we can make the date we have in mind. But I'm still not going to say it out loud... not just yet.

Honestly folks, it's coming up on a year since I started converting Isadora to 64 bit and adding the new features; I've never worked so hard for such a long period in my whole life. The team is working just as hard. We must deliver you the best and most totally reliable version of Isadora ever if we're going to continue to thrive in the future.

We'll give you a definite date as soon as we can be 100% sure we'll meet it.

Sincerely,
Mark

bonemap

@mark said:

Mark, rising from the bowels of coding.

It appears to be a very rarefied situation at Isadora HQ. I feel the pain and frustration of waiting, but empathise with the pace of development. The torch still burns. And I have deep respect for Mark’s ambition to reach the next level with the Isadora platform. We will enjoy many more years of relevant and timely features that pay back our patience and investment. Power to the code!

Best wishes

Bonemap