Would it be possible to unify the design of the trigger input ?

At the moment we have to different approaches:

"Send Control" the trigger input is the last input -> when we connect a value to both the input and the trigger - the new value will be send"Send Sys Ex" the trigger sits above the params input -> when we connect a value to both the input and the trigger - the old value will be send

meanwhile we could work with a trigger delay actor, but perhaps changing the internal order would bring the benefit to loose one more processing point, speeding transmissions up, the uncertain feeling how long a delay shall be.

thanks for listening

clemens

triggerinput_design.izz

Still I think it needs a good actor for this. There is already an movie to disk actor, I need to capture only 1 frame....Still working with Syphon capture and import it into Izzy

@DusX Thanks!

Hi, for a future request, is it possible to route all the 6 stages to black Magic thunderbolt to HD-SDI boxes?

I know this means going back to CPU actors but the fluidity of the video card/box is much better than a graphics card.

Thanks

since we can now vote for features, i want to push this one:

in order to track problems with js, midi, serial or … 
it would be great to have the capability to export the content of the monitor window. 
just copy and paste or even better as a .csv so we could import it into excel, sort the data, search for, etc.

Midi Monitor has the capability, but of course is limited to Midi.

the request is in the system under following
ticket number: 4499351 

Yeah, I've been using jumpbyname for years. It's been awesome. I usually disable the midi while editing.

Simple as it gets, save the stage setup with the patch, so it does not come back with the next open project. Better yet, save it separately and let us import and export the stage setups between patches.

@Woland

A good point about mapping.  I had only been thinking about Actor input and output values - I think that would probably avoid the situation you describe, but I stand to be corrected.

S

@DusX any idea of an ETA? I'm building a big mapping project starting mid august that runs a month. It would be great to get ahead with some new features...

I vote yes!

@Maximortal I can make it work, but. Streamline solution would be a great addition. Same place as the current fade controls at he bottom of the scene, but just separate audio and video times. Other solutions are not easy to reorder. The actual fades now are.calculated separately, by we can only set one time for both audio be video right now.

I'd be very interested in your application especially if it will be useable with minimal programing. The possibility to have the tweet/user name/tweet time as separate OSC messages would offer useful flexibility. Could there be an option to have the the tweets available as soon as they are posted as opposed to every 30 secs. 

I'm planning an interactive performance in which the public/audience contribute text messages that are integrated into the performance. I wasn't thinking of twitter but I suppose using social media exponentially extends the time/space/memory of participation beyond the present which is a good thing. 

@Fred

This really looks impressive.

Best Michel

Hi,

Same questions again :)

Any ETA if/when we'll have GLSL multipass rendering for the GLSL Actor ?

Everyone who has used a GLSL shader knows, that this feature will unlock incredible ideas for Isadora users.

Regards,

S.

Damn. Missed that.

H

@oscar

Well you can safe the user actor as a new instance, but then you are not able to change all together anymore. 

Best Michel

https://www.shadertoy.com/view...

https://www.shadertoy.com/view...

or just create an image with illustrator and beam it

@Michel & @artoo: thank you :) 

hihihi....

in fact this is a part of a macro... made with plenty of user actors...

the links on the left are like this 'cause i need to see them easily when i'm working on the patch.

@adolfalexander

I already have my MFA

Thanks anyway