Targetting version 0.9

[brunoherbelin]

The versioning of vimix is organic, following the stream of ideas I have and requests that users post. The evolution of previous versions and list of releases shows the past. Here I welcome your input to give the target for the future !

I see two main directions:

1. Towards video mapping : multiple output areas in geometry view, control multiple windows, link to video mapping software, etc.
2. Towards video sequencer : time-control of events, cyclic animation of sources, recording of user actions and replay, etc.

But maybe you see something else? Please feel free to give you opinion on the priority for you and ideas you have for vimix! I am not saying that this will be done, nor when it could be done, but guarantee that I will take your input into account for establishing the list of priorities for the upcoming version 0.9 !

[MoorPoor]

Fore sure vimix needs (and has already) the best of both of two worlds ;)

Concerning Video sequencer and control of contend chaitaigne opened up a lot for me. Sensors Inputs, audio reactivity and so on, all stuff I was missing in vimix. But actually there is no need to implement it anymore as a combination of this two softwares is a dream.

Mapping of contend on the other hand needs to be done in vimix from my point of view. Also I tend to say, that it is fundamental to get the video material where it needs to be, no madder, if you re mapping or VJing or just producing.

So even thought I want to raise my hand for both ways, I tend to 1. as it is just much more useful for my work.

Thank you so much for your work! And your general openness for use suggestions! Big benefit for artidts and friends of open software

[lupin3rd]

I agree with @MoorPoor. The priority could be to work on video mapping.
A quick solution could be to support existing video mapping software.
(For example use Splash software by piping through shmdata.)
In the long term it would be nice to have basic video mapping functionality within Vimix, so that you don't need another software unless you need advanced functionality.

[brunoherbelin]

Well, lucky for you, vimix already supports shmdata sharing with Splash;

It works out-of-the-box with the flatpak packages of vimix and Splash. Select shmdatasink in vimix Settings of SHM plugin, and enter as shm link file `.shm_vimix0' (with full path for home directory) in Splash

[brunoherbelin]

Update: Improved support for shmdata in latest commits and fixed compilation instructions in README.

[lupin3rd]

I tested... and works very fine with last beta!
In README you must change:
cmake -DCMAKE_INSTALL_PREFIX:PATH=/usr -DCMAKE_BUILD_TYPE=Release -DWITH_PYTHON=0 -DWITH_SDCRASH=0 -DWITH_SDFLOW=0 ../shmdata-build
with:
cmake -DCMAKE_INSTALL_PREFIX:PATH=/usr -DCMAKE_BUILD_TYPE=Release -DWITH_PYTHON=0 -DWITH_SDCRASH=0 -DWITH_SDFLOW=0 ../shmdata

[zcbernard]

Good morning
The desires regarding the facilities of Vimix depend on how we conceive of live editing and improvisation. Everyone wants them in view of their practice. For my part, playing video in conjunction with an improvising musician, I quite like the "cut" edit. That is to say moving from one session to another instantly and over very short periods of time. To put it better: a session takes place, we "play" it, we wish to switch to another, would only be for a few seconds, then resume the previous one where it had been stopped.... Intersperse a third... while keeping the planned course of a session with possible or already prepared actions. I will be able to take the image of an instrument with its sound facets.
Bernard

[a-1219]

Hi, I would say video mapping is one of the main lacking functionalities in the open source landscape atm. Splash has always been somewhat clunky for me. I tried using ossia score as a VJ software and it's pretty capable, but not as smooth as vimix, although it has really interesting controlling and compositing capabilities. It also has a video mapping approach that worked better for me than figuring out splash.