Also, on the topic of time-code, perhaps this bundle of add-ons will be useful to you.

https://troikatronix.com/add-o...

@gaspar

I have had growing connectivity issues with my focusrite Clarett pre8, but It is stable at the moment when wired into a desktop setup. The unit is a bit older now and has a Thunderbolt 2 interface. I assumed that some of my issues were a result of having to use converter dongles and docking devices to use the Thunderbolt 2 interface with current types of connectivity. When the interface is physically connected but not connected in software, I go back to the focusrite control app and it is usually also not detected there either- at that point I try to restart everything. I did have some nasty noise coming from one monitor when using Isadora directly with the focusrite - which was a surprise - but I turned everything off and restarted and didn’t have another hint of it. 

I have used Motu and Behringer interface before - some time ago - I was happy to leave the Behringer behind and have had less issues with the focusrite than I did have with the Motu.

 I think it will be great when Isadora releases a major audio update.

Best wishes

Russell

@woland

As usual, you out do yourself. That is a fascinating list of TC actors.

I can see myself using one or two of them already. 

A lot cleaner than my set up.

Many thanks.

eamon

@gaspar said:

even when Native drivers

 That sounds like a very positive change. I am surprised that wasn't the case before, perhaps the drivers became corrupt of something.
I have found that occasionally I can introduce audio crackles if I am using virtual audio cables, and my sample rates aren't matching between the virtual cables and my audio device. I would also ensure you have a clean USB connection with a trusted cable.
In studio I use a Roland Rubix 24 (much like a scarlett 24), and it has been stable.

@simon100 I found some more of my timecode things (this time more patches than User Actors). Maybe some will be helpful for your project.

Maybe some of these will be helpful:

patch-timecode-scrubber-2022-11-17-3.2.6.izz

percent-and-timecode-scrubbing-24-04-2024.izz

percentage-control-of-timecode-movie-player-v2.izz

movie_player_timecode_end_time-v2.izz

slider-control-of-timecode-movie-player.izz

slider-control-of-timecode-position.iua3

slider-control-of-timecode-position.iua4

time-to-timecode.iua3

time-to-timecode.iua4

timecode-jump-1.0.iua3

timecode-jump-1.0.iua4

timecode-trigger-user-actor.iua3

timecode-trigger-user-actor.iua4

timecode-user-actors.zip

Thanks @Michel @bonemap - exactly what I needed. And for the timestamp bonus @dbini @Woland 

Much appreciated!

S

@dbini

Hi John

Thank you very much for the tips and pointers.

I am sorry for the long delay in my response. Life has gotten in the way.

These have been very helpful. There are so many actors that I just do not think of.

Question1:

I agree with you that I have been over complicating the patch. I have simplified a few things and taken your points on board. I never thought of using a multi mix actor etc. 

I am working through this and will take note of your sample patch.

I think the idea of the Trigger Text actor seems the best way for me here. Again, I did not think of it and was looking at multiple text draw actors...

Question 2:

I have a perfect solution for this. The Trigger Value refererence's seconds in its value section. This was very helpful as I am trying to decipher time code for the trigger points. With the the help on an online TC convertor, I have worked out the values in seconds. I have used the "Trigger Value" actor in a macro and linked it to the various time slots/buttons in the Control Panel. A bit of rote work inputting the details but I have all 3 movements programmed up and it works like a charm.

I may yet not need this but it is very handy 

Question 3:

Thanks again here. I had a look again and did realise as well that my positioning of the control point was too early.

All is slowly working towards the intended plan.

I now just need to tidy up the running sequence vis a vis the TC & the Movement Information appearing throughout the film on the Conductors monitor.

I do not need this for another while yet but I am in a good position here.

Now to link the soon to be added SRT file!

Thank you John and all.

Very much appreciated.

eamon

Short update: I've updated drivers and now get sound output through Isadora from my Focusrite even when Native drivers, and the Focusrite(not found) are selected.

Maybe also the other issues are solved with the driver update, but still not sure to risk another painful fail. So any comments are welcome.

Re: [Multichannel Audio Interfaces under Windows for Theater Productions: Which One?](/topic/6237/multichannel-audio-interfaces-under-windows-for-theater-productions-which-one)

I saw the old post but since several years went by in the meantime I've decided to relaunch the query.

Last week my Focusrite Scarlett 8i6 (I blame it but can't say for sure it was its fault) failed twice during perfomances. Once running ableton on W11 and once on Isadora 4 on a W10 machine.
Now I'm a bit scared and I'm looking for alternatives. I saw the MOTU 4 is generally regarded as very robust, but then in the old post referenced at the beginning, @Fred mentioned that he had issues with it and would rather go for RME (which today is about three times more expensive).
I've had a look at the RME Babyface Pro FS, but it seems to have 4 analogue inputs (2XLR + 2 JACK) and 2 XLR Outputs, whereas I would like to have at least 2 inputs and 4 outputs.

Any suggestions? Reliability is probably the most important thing I'm looking for (more than sound quality itself).
I use the inputs just for MICS, at least for now.

A BIT MORE INFO ON WHAT HAPPENED IN THE ISADORA CASE:

The sound suddenly started crackling, so I slowly turned down the volume on the focusrite, muted the sound desk, switched it off, and turned it on again after some seconds. ISADORA did not recognise it again, even after restarting isadora. It saw it, but was listing it twice (once as "not found"). Regardless which one I selected, it turned to "not found" a few seconds later. Finally I went with the output of my laptop and could go on. MY FAULT... I just didn't notice that ISADORA switched back to NATIVE, when I turned off the Focusrite. Possibly if it had not been listed as an "available" card, I had noticed. Not sure if ISADORA could handle this in a better way. Now, after setting the drivers to ASIO again, instead of Native, the Focusrite works fine again. But I don't fully trust it.