In reply to @davidbrrrr:matrix.org
zeos_: please get in contact with jeanne concerning the exhibition. The tricky part about live participation onsite is of course that nobody will give us the guarantee that the event can actually happen.. this makes it incredibly complex and risky to plan ahead for live performances that require real space interactions

In reply to @davidbrrrr:matrix.org
@room I would be very curious what you think are the main reasons why this years call for workshops did not find a proper response until now.. was it mainly due to corona which hit us basically right after the call? Or what is the overall concern here?

for me it was a combination of a lack of time as well as being not sure what will be possible due to the corona-situation travelling-wise. right now it is really hard to plan for anythings that is more than one month in the future.

furthermore, a workshop for an online audience is different to teaching in class and i did not have a mind yet to think about what this actually means for topics i'm considering to offer. however, it would probably be a good idea to roll the drums once more and clarify that node20 will happen in a hybrid form and what kind of workshop formats will be possible.

proposing a beta workshop feels wrong since it isn't promoted as the tool to use anymore (by the vvvv group).
it's a pitty that we didn't manage to communicate this better. But if you only look at the technical aspects you will see that vvvv beta and vvvv gamma benefit from our work on VL. there are libraries popping up that were realized with VL and come with node sets for beta and gamma. there is even some vvvv beta specific stuff coming up like a new contribution manager that should make it much easier to setup the system. the installer for vvvv beta is another thing that happened on that "product line". So as it is true that our hopes and wishes regarding a pure VL based system are high, we always made sure that vvvv beta benefits from our developments. So I would argue: whatever works. If the current state is having two systems where one isn't quite replacing the other, then I say use vvvv beta. Tha's what I would tell a user that knows beta well. However regarding workshops: It does feel a bit weird to teach vvvv beta without mentioning VL and teaching both at the same time is probably overwhelming. So yes. it is tricky

proposing a beta workshop feels wrong since it isn't promoted as the tool to use anymore (by the vvvv group).

it's a pitty that we didn't manage to communicate this better. But if you only look at the technical aspects you will see that vvvv beta and vvvv gamma benefit from our work on VL. there are libraries popping up that were realized with VL and come with node sets for beta and gamma. there is even some vvvv beta specific stuff coming up like a new contribution manager that should make it much easier to setup the system. the installer for vvvv beta is another thing that happened on that "product line". So as it is true that our hopes and wishes regarding a pure VL based system are high, we always made sure that vvvv beta benefits from our developments. So I would argue: whatever works. If the current state is having two systems where one isn't quite replacing the other, then I say use vvvv beta. Tha's what I would tell a user that knows beta well. However regarding workshops: It does feel a bit weird to teach vvvv beta without mentioning VL and teaching both at the same time is probably overwhelming. So yes. it is tricky