[LOGGED] Timeline interface and Izzy
kdobbe last edited by Woland
Izzy he has been a spectacular tool for a variety of projects that I’ve worked on over the years. When doing theater or dance, I often synchronize video projection, sound, and lights. Currently I send midi signals to trigger lighting events in a standalone application. It would be SO helpful to have a built-in timeline type of sequencer that is similar to the design in traditional music sequencers. The timeline could be tied to movies, sound, etc.
This would make the visual design and rehearsal aspects so much easier to work on. I would imagine the timeline capable of sending a variety of synchronized events out to include MIDI, audio, OSC, etc. This is of course currently possible, but is not elegant and intuitive.
For me, this would be by far my number one request for the continual improvement of this spectacular tool.
I fully support the idea, that would be awesome!
If Isadora have a timeline plugins I think it's fantastic 😍
CitizenJoe last edited by
Does this help? TROIKATRONIX : ISADORA - DX – Advanced Envelope Scrubber
kdobbe last edited by
Thanks. Yes, I followed this when shared some time ago. The plugin is very nice. I had previously created ways to do the same thing. I was simply suggesting that for future requests, having a timeline sequencer built directly into the interface would be a great addition. As a musician who has used the sequencer interface approach for many years, I have found this type of visualization of "time and triggered events" is second nature to many users. Thanks for the offer of your fine work.
I agree that it would be incredibly helpful for linear cueing, but one of the reasons we haven't gone in the direction of trying to emulate timeline-based software (which relies entirely on linear cueing) is because it would introduce a number of complexities (and some impossiblities) due to Isadora's focus on interactive cueing (e.g. video intensity or a transition being controlled by volume using a Sound Level Watcher or by sensors) and non-sequential cueing (e.g. A scene that's programmed to cycle through random Snapshots or an Activate Scene actor in scene 4 activating a background scene 2 with Sound or Movie Players) which simply cannot be tied into or accurately represented on, as you put it, "a timeline sequencer built directly into the interface". This timeline-based (and linear) engine would have to simultaneously exist alongside Isadora's current engine (where non-linear and interactive cueing is possible) and this gets extremely complicated very quickly.
That's not to say this isn't a great idea, it's a wonderful idea. The issue is that from a programming and User Interface/Experience design perspective, the thought, energy, and time required to create, test, and add a timeline functionality as one of the core mechanics of Isadora would be massive. I'm not saying that we can't or won't add this feature, (in fact I hope we do), but I can tell you that unfortunately, we can't implement it anytime soon, since we'd have to scrap a large number of the features that we're planning to implement in the near future in order to focus on incorporating a timeline into the heart of the program.