@fred

To my knowledge Apple does not sell a usb-c to HDMI (they resell Belkin)

I used a few different types

and I tried a few that I didn't not know the manufacturer

nothing changed via hdmi or Displaylink (Pluggable)

G

Just quick update on this. The JSON Bundler always seem to revert to object when I open my project. I have worked around this by including a "trigger text" actor to send a "key" to the jason bundler as a part of the scene initialization. This resets it to object. I'll see if this works moving forward, if not, I will use @DusX 's javascript option.

Definitely having issues with the bundler and unpredicably switching to "array". I am going to pivot to dusx's javascript method. Here is what i did to be able to add a custom key to the json values so i can use the isadora JSON Parser actor:

--------------

// input 1 (index 0) is the custom string for the key. The loop begins at 1 as opposed to 0

function main() {
    var customString = arguments[0]; // takes custom key string from input 1
    var output = {};

    for (var i = 1; i < arguments.length; i++) {
        // Creating a new key with custom string and index
        var key = customString + i;
        output[key] = arguments[i];
    }

    return JSON.stringify(output);
}

@nic

I haven't worked with the Azure so I can't speak to that.

@lundmk

Please open a support ticket using the link in my signature if you haven't already.

Best wishes,

Woland

@jtsteph

They'll be replaced automatically, but if you're interested in using the beta version right off the bat, feel free to send in a ticket using the link in my signature and I'll send you the form to sign.

Best wishes,

Woland

@jtoenjes said:

this behavior seems to be particular to Oculus screen cast

 There might not be anything we can do about it then, unfortunately :(

@dillthekraut said:

Mutable values (the ones with the green connectors) take the ranges from the actor values you connect them to

It sounds like this to me too. The Set and Get Global Values actors' 'value #' inputs/outputs start with a default range of "MIN" and "MAX". They can only have a set range if they're manually given one through a user setting a range via the Property Inspector or if they're connected to an input/output of another actor that has a set range. Perhaps a manual range was set for one instance of a Get Global Values actor that you were using for something, then you copied it and used it somewhere else.

It's worth saying that if you disconnect a mutable actor from the actors around it, right-click it, then select "Reset to Default Values" it'll set the ranges back to the default.  Another tip I'll give is that you can select the links connected to your mutable actor and use Actors > Detach Link at Input and Actors > Detach Link at Output to just take the links connected to a mutable actor and "store" them temporarily by attaching them to a random Gate actor or something, then you can free up your mutable actor, reset its values to default, then re-instate its connections using Actors > Detach Link at Input and Actors > Detach Link at Output to take them back from the "storage" Gates.

@Aolis @Woland 

Thales says there a been fix as been applied. Please notify us by opening a ticket if you see the download problem again.

Best Wishes,
Mark

@woland said:

Try setting "Display Refresh" (to the right of Target Frame Rate) to "Off"

 Yes, this!

@em_tx Have you tried to install emu ?

Your are right - i found out why. You have to go into in screen settings you have to go to advanced settings and then and the show all resolutions. After that you will get a list off all resolutions an d you can select the right one...

Isadora 3.2.6 ARM, Mac M2 Max, MacOS Sonoma 14.2.1

Opening an Isadora 2 file from 2014 and replacing missing media will cause the project to open completely blank.

Workaround:
Clicking "skip all files" will open the project successfully. Replacing missing media afterward in the converted Isadora 3 file causes no problems.

@kaju

Hmm seems to be a bug. For now, I'd suggest just swapping left and right body parts for whatever it is that you want to control.

@woland

Ah, yes, thanks, I thought that an idea could be to use my midi controller to controll the fades of as much video as possible, and then make some videos in the end and beginning for fades to new scenes that are not 3d...  Or..... Maybe an option could be to record the 3d live image so that it is a 2D video of a 3D surface - then it should be possible to make the transition?:)
Ill try that.
Thanks for the help:)Eva

It's the hdmi output from another mac.

Resolution is 1080p60.

I tried the three video setup (scale to smallest, largest, default).

With or without antialiasing...

Anyway, i tried it on a new patch, video in watcher straight to projector, so there should be no scaling nowhere.

When i let the mouse on the link, it tells the output from the video in watcher in 1080p60

For now, i'm using spout/syphon from madmapper to have the good image quality.

Once again, the setup was tested both on mac and pc, with a decklink duo 2 and a decklink 8k pro.

@mark ok. I'll open a ticket to get the new Leap Motion plugin. Thanks! and thanks to @tomthebom @Armando

@bram

MP4 is the preferred codec since it uses a newer Windows system, but you are correct Palindrome isn't a useable playback option with this codec. 

Here are some codec specs I recorded sometime ago:

Known Bad Codecs:

Decklink MJPEG CompressorMicrosoft RLEMicrosoft YUVToshiba YUV

Known Working Codecs:

DV video encoder (DS)Hap (vfw)HapA (vfw)HapQ (vfw)Intel IYUV (vfw)MJPEG Compressor (DS)MSScreen 9 Encoder (DMO)MS Video 1 (vfw)WMVideo8 encoder (DMO)WMVideo9 encoder (DMO)Black Magic HD 8 bit 4:2:2Black Magic 8 bit MJPEGBlack Magic 10 bit 4:4:4Black Magic 10 bit 4:2:2

Performance Grid: (cpu usage comparison during record of 30 sec clip at 1280x720, 30fps, 75% quality)

Average cpu usage at runtime of test patch is 14-18% and gpu usage also 10-14% Note: all recorded values are +- 2-3% and at start of record generally have a spike in usage not included in these usage stats.

CODEC

CPU usage

GPU usage

DV video encoder (DS)

34%

13%

Hap (vfw)

52%

13%

HapA (vfw)

53%

13%

HapQ (vfw)

53%

13%

Intel IYUV (vfw) *

28%

13%

MJPEG Compressor (DS)

46%

13%

MSScreen 9 Encoder (DMO)

46%

13%

MS Video 1 (vfw)

31%

13%

WMVideo8 encoder (DMO)

47%

13%

WMVideo9 encoder (DMO)

47%

13%

Black Magic HD 8 bit 4:2:2

27%

13%

Black Magic 8 bit MJPEG

30%

13%

Black Magic 10 bit 4:4:4

30%

13%

Black Magic 10 bit 4:2:2

28%

13%

* This video format does not playback in the correct color in Isadora since YUV support is dropped in Isadora 3 

-------------------------------------------------------------------------------------------------------------------------------

So based on these results, I lean towards using the 8-bit BlackMagic codecs myself. (installed with free blackmagic software)

Hi there @bonemap, 

Logged this for our web team, we are likely going to update our forum software soon hopefully we can then also resolve these issues :)

@mark, @dusx

I tried a few attempts at a workaround with the current Matrix Color Send to assign consecutive rows from a video stream to LED strip segments. I imagine using a single module is going to be best, but I got as far as using a series of Matrix Color Send modules in the Scene Editor. Then joining the outputs with a Text Formatter before the Artnet Send. The ability to flip and zigzag alternate rows is one of the features missed from the previous Matrix Color Send.

I found that the Matrix Color Send had the behaviour of not being configurable when positioned as a vertical series in the Scene Editor. For example, more than two Matrix Color Send actors placed one under the other became affected by the module above with the pixel indicators moving inside the pixel matrix viewer part of the UI when bringing the module close to and underneath the one above. This appeared to happen with three or more of the modules in the Scene Editor. I don’t know if it expected behaviour- seems odd to me.

Best wishes

Russell

@eva said:

Can you help?

 Have you opened a support ticket?

We will need to know the Codec of the Videos being played? Issues with the video themselves is the most common cause of stalled playback.