Hi there,It takes some extra steps seems to be the case, since apple caused some stuff to break. I personally don't own a mac, but it seems that you need to enter some terminal commands to make it happen. Personally I would go with a newer device, for example the https://www.enttec.com/product... that has an extra universe, it is worth the extra cost in the long run

@Keve  said: How about adding a visual indicator next to the parameter I agree, this is a great idea!  There is the control ID number in the parameter setting window that places a visual indicator as an extension on the actors input, so a visual indicator of the initialize parameter would be helpful. I think it would also be helpful to think about redesigning the basic Isadora actor block or UI so that all of these parameter settings are visible all of the time and can be checked and manipulated directly on the actor or a persistent parameter panel. The parameters like 'Scale min' and 'Scale max' have such a significant impact on how an individual actor functions. I know it might be too much going on the face of it, and it would disrupt the current Ui/UX, but it is also a great design challenge to think about. best wishes bonemap

@camilozkThis is a dialog provided by Quicktime, and since Apple is no longer developing quicktime, it will not be updated.On Windows: Luckily the issue is cosmetic only. It may be hard to read, but it still functions.On Mac: this is not an issue.The up coming Isadora 3, has removed Quicktime entirely, and you are presented with a different method of setting up you codec selection for recording. It uses the native directshow system on Windows and AV foundation on Mac.For reference, the text which appears unreadable in the 'Motion' section is:Frame rate (followed by 30 in the image above)frames (define the number of frames between keyframes)KB/sec (limit the data rate to this value)

@skulptureright.. tap tempo will help smooth out any change in BPM.You could also add a 'Smoother' actor to make abrupt changes have a transition.

@helendeneb since you want to be able to have the previous state remain.. (do you want all to remain as you move thru them?)I would consider doing the whole cactus portion of the show in 1 isadora scene. That makes displaying them all together very easy.I would build each Cactus bloom series as a User Actor, with trigger controls and Media IDs as inputs.Once you have 1 working.. you can add copies of the user actor, change the Media IDs, and you have now multiple sequences that can be triggered how ever you like.This isn't the most beginner thing to do.. but User Actors are one of the most power pieces of Isadora so learning them early is a great idea.I don't know exactly how you want things to work, or what media you are using.. but I think its an achievable goal. If you can supply details on how you plan to structure the media.. I would be happy to make a demo file with a User actor explaining the method I described.@dbini 's idea of laying the blooms over the background cactus sounds very good. So in that case, the Cactus, would be placed out side any user actor, and the blooms would overlay with alpha channels.

Cool! Thank you!

@salimelo you must cast osc data to 127.0.0.1 AND be sure to use the port where Isadora is listening ( default in Izzy is 1234 but often other programs use 8000 ) once you set all correctly in Isadora you must create the channels in osc menu. There some tutorial in how to section.

@rilWhat graphics card does your student have? Usually it is a matter of what version of OpenGL is supported by the graphics card, and not a library that needs to be loaded.Installing the latest graphics card driver, may help.