Hi Michael

Many thanks for the pointers and the help.

All now works perfectly.

I have been a long time fan of Isadora and have only just come back into the realm of it due to a new job. I do appreciate the effort and advice I have received. It has been very helpful and has made me look good to a lot of people...:)!

Thanks again.

Eamon

Thanks Michel!

Thanks that works a treat!

Hi @mark,

That is amazing! so grateful for the detail that you have provided in the tutorial, especially considering, as I understand it, that there are changes to how Isadora will handle multichannel audio in the Catalina and cross-platform future.

best wishes

Russell

You may also want to change the Direction on your Keyboard watcher to "Up" to prevent multiple triggers (since holding down the spacebar too long with the Keyboard Watcher set to "Down" can trigger the Keyboard watcher in the Scene your transitioning from AND the Scene you're transitioning into).

Adding a Multiblocker actor between the Keyboard Watcher and the Jump Actor is another way to prevent accidental activation of more than one Jump actor.

@mark 

[OFF TOPIC] Situations like this always take me to a philosophical point: how far do we go with Isadora in terms of things supporting certain kinds of features?

Personally I rarely have expectations about what new features are added to Izzy. But I would like to have the insight to implement/deploy whatever existing features or functionality are lurking there and waiting in Izzy - as a potential. 

Providing enough description to uncover the potential of a specific existing module is as powerful as adding new features IMHO. That is why the revelation about the AUMatrixMixer is so astonishing. Yes, it is logical for an audio technician - and anyone else, once the realisation ‘that audio, unlike video, carries multiple channels in a single stream’ and 'panning to separate individual tracks that have been forced into stereo pairs' is applied to unpack the problem. This simple statement unravels a whole chain of sequences and connections that resolve the implementation of multichannel audio. No matter how obvious that statement might appear to be!

I think, for me, I do have an expectation that what already exists in Izzy is a ‘supported’ feature and functional to the highest limit of its potential. To that end I will make noise when it appears that some parameter function is broken or appears to be not functioning as expected.

There are existing 3D modules incorporated into Izzy therefore the expectation, from a user perspective, is that they are supported. When I first approached using the 3D modules, I had no idea or insight into the extent of their potential. The joy of discovering what they are capable of producing has been a source of inspiration and a catalyst for imagining a way of working with Izzy that has lasted many years.

I have become accustomed to the statement that ‘3D is not a priority feature’. But, I would say that the existing 3D modules have so much ‘hidden’ potential that perhaps it is not a question of adding new 3D features, it is more about ensuring the current offering is functioning to a high level potential.

best wishes
Russell

DusX- thanks, understood! 

@mark 

dear Mark,

I have the FCP X version 10.4.7 (german) and it look like that: 

so I have to select "Rollen" (roles in english ?) to get the options you mentioned. They are looking so:

or to get really e.g. 6 separate tracks and not only one surround track:

best

Jean-François

What you can also do is use a Enter Scene Trigger and a Trigger value to 0, connect that to all your Audio Players, that way when you enter the scene all active fields get a zero causing them to become OFF instead of ON. :)

@dusx yes, I have done this, libraries are not needed to do the maths, but on the end we can only draw with Euler.

when you detach the links, the connection balls are probably green. When green they can be mutated (converted from one type to another) if you connect to another that is vid-gpu the link should switch type.

Depending on how old your file is you may need to replace some depreciated (classic actors, or other show in red) actors to fully modernize the project.

@dbini said:

but i think its almost ready, so i would estimate you would get it in weeks rather than months.

We very much appreciate you being helpful and answering questions here, but as outlined in the beta-testing contract, we ask that you please not discuss the timeframe of anything beta-related outside of the private beta forum. TroikaTronix will make an official announcement about the Body Tracking plugins when we are ready to do so. No harm done, but if for some unforeseen reason we end up not meeting the timeframe you gave Charles, then he would be in a spot of trouble if for some reason we didn't release the plugins when you said we would.

@Charles-Bata

If you create a support ticket I can add you to the Beta Silver Group so you can get access to the plugins immediately. (There's no fee or anything, I just need some information from you and to have you sign an agreement.)

I updated the guide, it can be found here:

http://mac.djebrallah.de

Yours

Timo

@jjhp3 said:

Just wondering... Mac; 3.0.2. Thanks, John

 We're doing the public announcement today or tomorrow morning latest.

Best Wishes,
Mark

Sorry, but we need a better description on what you wish to do..

A Control Panel with a Monitor or Stage Preview Control also basically does the same thing.

OK must I be going mad! thank you so much for confirming this!!

You guys are great! :)

@mark said:

thank you Mark, I have submitted a ticket and the crash report.

@mark said:

we should add a bug report

 Added to the sheet as "Name: Converting Strings to Timecode"

The provided test videos import and run in both Isadora v2 and 3 on my test machine, so I believe some type system configuration issue is responsible.

I am continuing to troubleshoot the issue with dritter via a support ticket.