Hi there @mark, 

I agree with @DusX would be awesome if we can have the version in the help text.

Personally I would love to see an update to https://v8.dev/features/subsum... basically the feature allows future proof UTF-8 encoding for JSON strings. Something that happens quite often in the modern age. For example, directors that ask for UTF-8 encoded characters in strings that we have to recall. I believe that all other text features of Isadora already supports UTF-8 encoded strings.

Other then that, I partly agree with DusX regarding the syntax comment, still UTF-8 features are missing to say one.

@eamon

Glad to hear it works. Let us know if you run into any other problems.

Best Wishes,
Mark

Dear Mark,

I was running for the evil clowns the last couple of days, but I am back and managed to grap the file. I just tried it again and now it seems to work. I didn't change a thing in my project. But anyway, here is the file I used to test it. I can imagine that it makes finding the problem a bit difficult. Thanks!

Adri

Text File

Amazing, thanks! Very timely ;)

@craigw

yes, this is a known bug. It’s been reported and I’m waiting on a fix @DusX :-)

@johnnymoreno

Are you on MacOS or Windows? I sent you a suggestion via the ticket system (changing the "Display Refresh Lock:" setting to "Off") but I was assuming MacOS. Display Refresh Lock is only available on MacOS only.

Best Wishes,
Mark

Thanks Michel to point out this new feature.

Best, thomas

Bypass = off will mean no frame should pass through until you trigger the grab input.

Trigger the "grab" input when you want to grab a frame and freeze it there.

Hi Juriaan,

Thanks a lot! This was exactly what i was looking for. :)

@goddessmoon2017 Hey I figured it out. Apparently I was upgrading and paying for the beta version I was running. thanks for the help. up and running. :)

@michel said:

A very good alternative would be the AVF batch converter

 Yes, this is what I suggested Arthur use for batch conversions.

@mark

Hello Mark, my problem was already on 2.6.1 because I had to adapt my patch from 2.5.2 when I had to move to Mojave for other softwares. The random problem surprised me and it's the first time I have a bug during a show with izz in nearly 13 years.

Is stuff like wifi, updates or virusscanners checked ? 

@goddessmoon2017 so far the skeleton tracker needs NVIDIA cards for cuda acceleration and it is windows and Linux only.

It is early stages and resource heavy right now, and also still only available in the US and china. I had to get one forwarded from the US to develop with.

For sure it will get better and cross platform support but this is going to take quite a while to get there and then to stabilise (SDK wise)

Please open a support ticket (link is in my signature).
it seems we will need to dig a little deeper in your case.

@deflost said:

control value update on slider in 3.0.3

 Hi,

I have just started working on a patch wth a lot of control Sliders on Mac OS Mojave using Isadora 3.0.3. When entering next scene the 'linked value' behaviour of a Slider appears to be unexpected when progressing through scenes with the spacebar cross fade and when more than one scene uses the same 'control ID link'. For example I have a 'Colorizer' between a Movie Player and Projector with Control ID linking to Sliders in the Control Panel. When I progress the patch to the next scene using the spacebar I do not get the updated 'linked values' of the destination scene sent to the Sliders when more than one scene is linked to the same control ID number. However, the current linked values of a scene will appear just when the spacebar activates a cross fade to the next scene, but we do not get the values of the now current scene on the Sliders.

So what should the expected behaviour be? That each slider parameter is cross faded for the duration of the scene wide transition? Or that the slider is updated after the scene crossfade has been completed?

I am not sure what the implications are, but implementing a transition for individual parameters is most likely too costly in terms of processing power. But an update of control parameter values when the next scene transition has been completed is potentially a good option.

Best Wishes

Russell

@dusx

We relooked at the situation and after running through a number of factors it’s clear it isn’t the mapping but more likely a corrupt video file. Re-outputting that and will get back to you if it is still occurring. Thanks much

So generally speaking this suppose to be the solution - Aggregate device as a multiple audio interface. However, it is extremely buggy - it does not even root properly, especially with devices of various sample rate. 

So only solution is to have a proper headsets via radio over sound-card. It's pity as it could have been quick&cheap workaround for small works and testing. 

https://support.apple.com/en-g...

@jimmy-grima

Are you using Isadora 2 or 3? Have you set the external display to the same refresh rate as the frame rate of the movie? Mac or Windows?

Best Michel

Regarding your latest comment about the expansive list, I couldnt agree more. Mutable (the concept of it) is really silly and always causes some headaches with me anyway to solve the issue (I get the concept and how to solve it, still not a pleasant end-user experience)