Thanks for your idea to use site search on Google and other. I forget about this useful function. It could temporary replace find option here. On some site, I have seen find option, which momentary redirects to Google result with "site:" search option turned on. Maybe it would be good idea to use google search system and internal system on community. About new section: i think sharing of custom user actors will be very effective both for new users of Isadora(they could find sample how to build actors) and advanced users(they could discuss and improve their actors in community). A lot of basics functionality actors could be shared there. It just an idea for your team. Thanks!
[@Fred](/troikatronixforum/profile/Fred)
Can you point me to where the wish list thread has moved too, would I be right in thinking this is now under Features?
Michel's post has reminded me of some welcome requests thats resulted out of the Bang the FX workshop.
Thanks,
Jaygo
Yes, I've plan to show freezed picture after scaler, but how to determine, that GPU-stream to scaler is Picture-stream?
I have two different user Actors: first one is producing GPU (PicturePlayer/MoviePlayer/WatchChannel, second one is outputting userActor, which scales GPU to certain size(screen size) and shows on stage. Maybe there is a way to determine frame changes in GPU? this would be the best option!
@dusX
I made a illustration. The essence of the idea is reducing connections by broadcasting directly to inputs, wherever they are. And in a perfect world, with an option to do so global across scenes. And also to expand the broadcast actors capabilities, which I now understand is less relevant since there is the global values actor.
@bonemap exactly, just like the control ID link
I have faced the same issues recently, when using Bin Picker for realtime mixing. Being able to force a poster frame would be a good solution. In addition, it might assist to be able to resize or otherwise work with the file names in the Bin Picker.
best wishes
bonemap
I could imagine another menu option for, 'development status' perhaps.
Where this information was supplied like Fred mentioned.
Since bugs are tracked in a database, and labeled, it is possible.. we may need to adjust our current labels etc, to allow for cleaner queries..
This is something I get into often too. I think, at least the editing of points should be restricted to the splice/layer that is actually marked/active.