 | VL.Kairos | 74 Members |
| VL.Kairos library discussions and news | 3 Servers |
| VL.Kairos | 74 Members |
| VL.Kairos library discussions and news | 3 Servers |
| Sender | Message | Time |
|---|---|---|
| 8 Apr 2024 | ||
 sunep | I have been using Ableton Live for both recording of controls and non real-time playback. I have made some custom devices with Max4Live that match my vvvv devices. They send osc and there is a little device receiving osc and time in beats and bars so the vvvv patch can step through the Ableton Live timeline. | 17:46:25 |
 TremensS | Sure M4L is great for exotic setups but for general purpose I just find that Reaper's curve editing tools, multiple tracks/curves stacking, and curve naming saved us hooooours when you have dozens of curves. It is also way lighter/stable than Live so when there is no deal-breaking reason to resort to M4L it has become our goto tool over the years for syncing lights/visuals to a performance and/or spatial audio arrangements. And usually 14-bit MIDI sent locally or over the network via RTPMidi is plenty to not miss MIDI/OSC conversion. Also Reaper has native OSC mapping to a lot of the commands, transport included. If you havent already, do give a try to this workflow! Haven't touched M4L in a while since we tried this path. Just eagerly waiting for Kairos to have more explicit parameters instead of having Excel sheets to keep track of parameter correspondance haha 🤡 | 20:30:25 |
| 9 Apr 2024 | ||
| sunep | TremensS: I have been trying to use Reaper and do still once in a while. I just have so many years of experience with Ableton Live, that the cost of switching is too high for me to actually spending the time. But I really like the pricing model and I cheer for the success of Reaper. | 06:38:36 |
| 11 Apr 2024 | ||
 Natan Sinigaglia | In reply to @tremenss:matrix.orgTremensS: Can you elaborate a bit the last comment? if you create tracks from global channels you already have correspondence with external data, right? what would be your setup and how would you like kairos to mirror it? | 10:48:50 |
| TremensS | Natan Sinigaglia: hey! Sorry the sentence was not ambiguous indeed. "Waiting for Kairos to have more explicit parameters" was not in the sense of "waiting for Kairos to implement this feature" but rather "I can't wait to make the switch to Kairos in order to benefit the feature" 😘 | 10:57:41 |
 phlegma | Next Meeting, Monday 15. April, 18pm CETHey Kairos people, We've scheduled a new meeting for Monday. If you're still on track, please give a quick thumbs up. We'll meet here: https://hs-mainz-de.zoom-x.de/j/69843643710?pwd=MU9weXdOanZiUUU2MHhUclNQeDVXUT09 We want to discuss how VL.Touchy is integrated with Kairos, following Natan Sinigaglia VL.Touchy introduction last time. If you want to catch up, you can watch the last session here: https://nx46024.your-storageshare.de/s/P39reWJy6miYzqf Also, catweasel , sunep , and TremensS , you were discussing your timeline experiences in the chat. Do any of you have time to show us your timeline experience? See you on Monday! | 17:51:48 |
| sunep | I can attend and demo my use of Ableton Live as a timeline | 18:01:34 |
| 12 Apr 2024 | ||
| Natan Sinigaglia | As said last time, I'm gonna guide you through the implementation of vl.touchy in kairos UI patches, correct? | 07:22:38 |
| phlegma | In reply to @Aion:matrix.orgThat would be cool. | 08:00:03 |
 chk | a recording would be nice! | 08:28:56 |
| phlegma | We will do. Just like every time so far. Link to Recordings can be found in the miro board. | 09:04:48 |
| 13 Apr 2024 | ||
 catweasel | I'll try and get something to show... | 11:30:24 |
| 15 Apr 2024 | ||
 @thomas_helzle:matrix.org | I currently take a break from VVVV so won't be around, but wish you all the best. | 12:42:14 |
| @thomas_helzle:matrix.org left the room. | 12:42:30 | |
| phlegma | Unfortunately, I won't be able to make it to the meeting today for family reasons. However, the zoom room is open and can be used. Please record the meeting. I will then send you a link to upload the recording. Hopefully we can clarify everything later. | 13:20:04 |
| Natan Sinigaglia | Sorry to hear that, I hope it's not something serious. thanks anyway for organizing the zoom call. make sure any of us can operate as "admin" and recording ;) 🙏 | 15:06:14 |
| phlegma | Redacted or Malformed Event | 15:42:32 |
| phlegma | i need some persons mail adresse to add them as host | 15:47:46 |
| phlegma | * i need some persons mail adress to add them as host | 15:48:16 |
 gregsn | How about posting. Would love you phlegma to have as a host as you did a fantastic job | 15:52:52 |
| gregsn | * How about postponing like to next Monday ? Would love you phlegma to have as a host as you did a fantastic job | 15:53:35 |
| Natan Sinigaglia | I'm not gonna be available next monday | 15:58:17 |
| Natan Sinigaglia | i think is better to do it anyway | 15:58:35 |
| Natan Sinigaglia | not sure when everybody can next time | 15:58:53 |
| sunep | I can be host | 16:02:02 |
| sunep | sunep@galakse.dk | 16:02:06 |
 ravazquez | I had a last minute situation I had to handle, I'll catch up on the recording later, apologies | 17:50:49 |
| 17 Apr 2024 | ||
| Natan Sinigaglia | Hello hello, Just a quick recap of the last kairos call we had on Monday: Initially we looked at a workflow example of Ableton+vvvv timeline usage, shown by sunep: After we dived deep into the kairos timeline UI patches. I showed specifically how vl.Touchy (interaction library) is implemented in the timeline UI, from the top to the key frames level. Quite technical, but rich of thoughts and insights on what to do next. How to proceed from now on: There are two branches that can proceed in parallel. 1- there could be a call open to all users where we collect ideas for the timeline UI and we define in detail the specification of how the UI should look and behave. During the call we could use the Miro board to structure the information and make the specification. This is not gonna be a technical call, so people shouldn't feel scared to join. Collecting and processing ideas and needs from the creators point of view. Here is were we define the next timeline tool version, so people are very welcomed to participate!! 2-the second call is gonna be a technical one, mainly reviewing the interaction tests and prototypes that we discussed in the last call. As I said, these are two completely independent appointments, therefore not synchronized. Ball back to the community to organise this. Best Nat Soon the video recording of the last call will be available in the Miro board. | 10:54:30 |
| Natan Sinigaglia | * Hello hello, Just a quick recap of the last kairos call we had on Monday: Initially we looked at a workflow example of Ableton+vvvv timeline usage, shown by sunep: After we dived deep into the kairos timeline UI patches. I showed specifically how vl.Touchy (interaction library) is implemented in the timeline UI, from the top to the key frames level. Quite technical, but rich of thoughts and insights on what to do next. How to proceed from now on: There are two branches that can proceed in parallel. 1- there could be a call open to all users where we collect ideas for the timeline UI and we define in detail the specification of how the UI should look and behave. During the call we could use the Miro board to structure the information and make the specification. This is not gonna be a technical call, so people shouldn't feel scared to join. Collecting and processing ideas and needs from the creators point of view. Here is were we define the next timeline tool version, so people are very welcomed to participate!! 2-the second call is gonna be a technical one, mainly reviewing the interaction tests and prototypes that we discussed in the last call. As I said, these are two completely independent appointments, therefore not synchronized. Ball back to the community to organise this. Best Nat Soon the video recording of the last call will be available in the Miro board. | 11:01:51 |
| Natan Sinigaglia | * Hello hello, Just a quick recap of the last kairos call we had on Monday: 1- there could be a call open to all users where we collect ideas for the timeline UI and we define in detail the specification of how the UI should look and behave. During the call we could use the Miro board to structure the information and make the specification. This is not gonna be a technical call, so people shouldn't feel scared to join. Collecting and processing ideas and needs from the creators point of view. Here is were we define the next timeline tool version, so people are very welcomed to participate!! 2-the second call is gonna be a technical one, mainly reviewing the interaction tests and prototypes that we discussed in the last call. As I said, these are two completely independent appointments, therefore not synchronized. Ball back to the community to organise this. Best Nat Soon the video recording of the last call will be available in the Miro board. | 13:06:03 |