@clafarge

Did that work?

Actually... this converter works so well the trick might be just to work in ISF land and convert, worry about the details later. It'd be nice to have some more documentation so if it exists I'll take it, but I can make progress now. Thanks again.

@dbini

I see it now--brilliant! I'm embarrassed I didn't catch that sooner. Thank you!

@tr742

Yes, if I remember correctly the decision was made to save the Stage Setup with the Isadora file. If you have a setup you need to use in many files, you may want to create a 'Template' file with your stage setup, and then cut and paste you v2 scenes into these new v3 files. Allowing the Stage Setup to be saved as external config files and loaded into files is something we hope to implement moving forward.

@gpeddino

I don't really know what delay you are seeing, but it sounds like it's probably due to the Film being preloaded for playback. This time will vary due to system resource changes.

You could trigger Isadora to Start the scene and pause Ableton (if possible), and then again trigger Ableton to continue from Isadora (once playback has begun). That might eliminate the delay, as Ableton shouldn't require any additional load time.

Hi, I use a streamdeck every day with midi. I think this is what you mean by show up as a midi devise.

Currently OSC can't be assigned in the Edit Go Triggers dialogue, however, how I have worked around this in the past is to set up a MIDI trigger in this dialogue and create a User Actor that receives OSC, and sends MIDI (to a MIDI loopback). 

Of course, you need to add the User Actor to every scene (or a constant background scene).

I'll make sure we have, adding OSC to the Go triggers Dialog, in the feature requests!

thanks @dusx your suggested change means the trigger doesn't happen until after the delay, whereas i'm wanting the trigger to pass immediately and then wait until after the delay until the next trigger passes through

@paz This helps! Thanks so much 🙂

@woland Thanks - I didn't know Text/ure was outdated, good to know. The manual I am looking at is from 2019 so perhaps that's why. I'll try Text Draw instead.

@jfg that is clever, it does work too. Though I don't love using little micro delays, feels a bit like a hack and like something could easily get out of sync wrong if the computer stutters... But it does work and is simple. And that counts for a lot.

It's encouraging to me as a beginner that the community has found so far three different ways of solving this: I appreciate the help!

@chameau132 said:

A second replacing the path by "extandida" : but it read "caidadata" array ! 

 Did you trigger the 'read' input on the Data Array actor after changing the file path so that it reads in the new file?

@jfg Wow O_O look so stupid 😃 

Thanks for help  

@woland It worked! Thank you so much, that saved me a ton of time!

@tease Yeah probably Rutt Etra set to solid I'd say. Can be pretty GPU heavy but worth it! 

@juriaan

Thanks a ton!

Would have never figured that out.

Ah thanks all for the pointers and examples 🙂

Appreciate this community in my Isadora journey!

@juriaan ah! Thank you. This was my first post so it was in the moderator queue and so I never got to check it until now and notice the images hadn't worked.

That said I was able to fix it shortly after I wrote the above: I read the manual again and found that you can double-click on a User Input (or User Output) to set the data type of the actor. It's behavior unique to the User Input/User Output actors.

Can mark this as solved. Hopefully the answer above helps someone else.

@woland Thank you so much! This helps a lot!

Would love to see some of these solutions uploaded to the Add-Ons Page if anyone has the time 🙂

@vidasonik said:

scale min to 0 and scale max to 1

 Here you are telling this side of the system to expect values from 0 thru 1.0, it can't scale anything because it has no reference point. 

These min and max settings require that they exist on both sides of a link between actors. If on the first side you set min= 0 and max = 1, Isadora will expect values between 0and1 to be output, then on the other end of the link if min is set to = 10 and max = 30, the values from 0 to 1 will be scaled to 10-30.

This works in the same way as the Limit Value Scale actor.

I don't know what you full range of incoming values are, but if you use a Limit Value Scale actor, you should be able to scale to 0-1 or 0-127 depending on where you want to send that data.