@video-architect said:

Sorry for the cross post. I didn't see his reply. 

 Don't worry about it, no harm done. :)

@eva-0

I might suggest going through my tutorial on building a video step sequencer. Once you complete the project in the tutorial you are sure to understand Isadora far better.  The tutorial is part of my Build It series: Isadora - Build It! - YouTube

Of course the Isadora 101 course may be worth looking at first: Isadora 101 - YouTube

@dusx I'm not surprised that it programmed in a bizarre fashion. That's all I got to work with. Here's to hoping Watchout 7 is a lot cleaner.

Makes total sense about the clipboard, it was wishful thinking. I'm also messing around with Vicreo listener and I see I could run a shell script so maybe there's a way still.

Ultimately, it's not that important - I've just been talking with programmers about fun ideas to make things faster and more interesting for us since we're stuck with what we have.

@mr_j

I agree with DusX, the best way is to copy the entire Scene over.

Snapshots are unique to the Scene in which they're created because they store the values of the actors' inputs in that specific Scene, so there's no mechanism for porting Snapshots from one Scene to another (which is essentially what you're asking) because Snapshots were never intended to be moved between Scenes.

The closest I can come to explaining this more understandably is this process:

Imagine you've got two copies of the same book.Now you highlight a sentence on a specific page of the first book.If you wanted that same highlighting in the second book, you'd either need to use a highlighter to reproduce the change in the second book, or you'd need to rip the page out of the first book and use it to replace the same page in the second book.

Not a perfect metaphor, but it's the best I can do.

@bonemap Thanks. I still don't see why I would need that particular behavior. But someone needed it... 

@anr said:

my next challenge is to see if I can get different touch points with the touch board working to trigger different projected animations

If you place a control watcher actor with default settings it'll look for every control message. Therefore, if you place a fresh one and then look at the 'controller' output after you touch each of your different points, you should be able to see if they each send different controller values. If they do send different values, you can make a Control Watcher listen for a specific value by changing the 'controller' input to the specific controller value you saw on the output when you touched that point.

(This won't work if all of your points are sending the same controller value though.)

@bonemap

thanks for the offer... it is 4AM... but I'm happy.
The trick was done by loading the model (collada DAE) into Blender, assign the textures to the model and export it as 3DS.
(The plugin is still there and can be activated, even though there is a warning).

After that ISADORA recognised the textures and applied them properly so I could see the model.
As noted in previous posts in this forum I had to rename several of the texture files so the names were short enough not to cause any problems.

@laverdi said:

What do you all recommend for LTC in Isadora 3?

I have used Figure 53's free, Mac-only application Lockstep to convert LTC to MTC so that I could trigger Isadora via LTC for a show.

@gaspar

This may be a difference between supporting "Natural" voices vs. the lower quality "Legacy" voices as described in this article. It has instructions for installing new voices.

Let us know if this helps.

Best Wishes,
Mark

@kdobbe

This has been requested before: https://community.troikatronix.com/topic/8621/logged-remove-unused-media?_=1703077729820

TLDR: Certainly would be a good feature, but it's also a bit tricky because the media files targeted by Player actors can be changed programmatically, so the command could only consider media you are currently using in an actor, but wouldn't know to keep any media that you cycle to programmatically.

@woland Looks great, I'll give it a go...

@margiem Its working...! 

@garygalbraith

Using namespaces for your Classes should allow you to create the modular structure you are after.
Try defining your Class like:

var MyApp = MyApp || {}; MyApp.MyClass = class { constructor(param1, param2) { this.param1 = param1; this.param2 = param2; } method1() { this.param1 = this.param1 + this.param1; } method2() { this.param2 = this.param2 + this.param2; } }

Then create an instance in main() like:

const myInstance = new MyApp.MyClass(3, 5);

This should allow you to name each class uniquely and include them from external files.

@armando said:

Maybe it should be in the manual or in the knowledge base ?

Certainly, there are just many more relevant things to create documentation about and, since the execution order rarely actually matters for the vast majority of use cases and is tricky to explain and understand, it's not been very high on the list in terms of topics that we've prioritized when it comes to creating documentation.

@jpg-wav said:

I would have never been able to put this all together!

 I needed help from chatGPT to find the right equation ;)

@woland

i , thanx to the help of all of you i managed to finalise my eos  fixture  and the corresponding izzy  patch. works like charm. than again.izzyeos.zipin  the zip file you will find the patch, the eos fixture file and the blur qua

best  

peter

@gapworks

Isadora files created in 3.2.6 should work fine on macOS or Windows (unless you used the Mac-Only CI, QC, or AU plugins in the file).

@woland

This file plays 4 chan of audio 

That did it. Thank you so much!

@woland Very helpful. Thank-you!