@fred said:

@paralion Threadripper systems are better for pure multicore performance, I am pretty sure the movie decode task is another thread but itself is not mulit-threaded. If you want AMD look at the ryzen 9 3900x and a high end mother board like the Asock 570x Creator. 9k for beamers is a very low budget, but in general rental would still work out, going for a cheaper lower lumen rehearsal beamer and then switch to the fancy ones a few days before the show.
I just rechecked, as silly as it is, we can use the beamer budget only for buying, not for renting. 

IMHO you will need to spend so much time and money creating a good mounting system to hang all 16 beamers in the right spot (there wont be any correction on the beamers so positioning needs to be great as without blending you will get ugly seams no matter what; also short throw beamers that you can get for 500 a piece are not going to be bright or good quality and you wont want to hold onto them - they will also likely not have even square images as is the case with cheap short throw lenses, they have a fish eye effect and they are pretty much never actually square).
https://www.optomaeurope.com/projectorproduct/gt1070xe 
These are the ones I have (atm only 4), they are not loud, and bright enough but concerning the squareness, I will probably run into dissapointment when I test out all 4 of them on monday. Last test I did was with only 2 of them, and it was close enough to seamless. (having said that, projector distance from wall was closer than in the real setup and I know 2x2 will be way trickier than 2x1)


With that budget buy the BrightLink Pro 1470Ui  beamers that @bonemap suggested and then sell them after the production - you will be well within budget, have a better image, less stress on your machine and in general a lot cheaper setup that is easier to manage and will have a better image (the image splitters to take the 4k image to 4 x HD - I am assuming datapath, are not cheap at all - €1500 a piece). 
I got these guys: https://www.amazon.de/gp/product/B0833WTY5V/ref=ppx_yo_dt_b_asin_title_o06_s00?ie=UTF8&psc=1
I already have 4 of them and from what I saw so far, they do a pretty decent job. 
But yeah, If I see the optomas look absolutely terrible, I'll consider switching to the Brightlink. Despite not being happy giving up the resolution. :/

With a seamless rear projection (does the rear projection film come in a size that big?) 4 unblended images to make a single wall are going to look a bit nasty at best.

Maybe I'll have to work with the nastyness... a lot of the stuff is dreamy and abstract.... I might have no choice. The 4k material is all made by me and a collegue. In any case I'll update this thread with my experience, so others can learn from my mistakes!

here my first test with splitter and 2 projectors.

@woland thank you for the response. I will submit a ticket. FWIW, this was also occuring on my 13" 2013 MBP which was running Mojave 10.14.6

@jg said:

I'm a little nervous switching to a beta for production- would another workaround be to alter the color profile of the image?

After some additional poking around, I did find a solution.

You can see this the current color profile in Photoshop by opening the document and choosing Document Profile" from the popup menu at the bottom of the window.

The current color profile of your image is sRGB 61966 2.1 (8bpc)

You need to change this profile to Generic RGB.

Photoshop:
1) Open your image in Photoshop
2) Choose "Assign Color Profile" from the Edit menu
3) Choose "Generic RGB Profile"
4) Save the file

Preview:
1) Open your image in Preview
2) Choose "Assign Profile" from the Tools menu
3) Choose "Generic RGB Profile" from the popup in the dialog and click OK
4) Save the file

Here's my test file showing this works.

uvwarp-color-profile.zip

Best Wishes,
Mark

@bennnid said:

although that could be convenient to have the rotation parameter shown so as for the resolution when we move a point.

 Yes, I already added that as well. :)

@woland I just took some time to check. Strange enough my Laptop does not have any other graphics card than the RTX 2070, at least not listed in device manager, nor NVIDIA control panel or elsewhere (It is an OCTANE VI built by PC-Specialist). So NVIDIA RTX 2070 is alreadly the one ISADORA is using. Nevertheless, there is a bunch of options I could activate, deactivate or change. Maybe I could tweak something there, but I've no clue in what direction. I've messed around by intuition, generally preferring performance over quality and sometimes allowing the application to decide. I'll see it that helped in any way (well right now it made a W10 update... always scary. I tend to not connect that system to the internet, but since it was not working well anyway, maybe now it does.

Hi,
I am testing with NDI signal. In Isadora, I connect a player to a Virtual Stage (1920x1080) and select NDI output in the Stage Setup and route it to MadMapper. Here the NDI input is not displayed correctly, rather it appears with another ratio (1920x540). I have also tried in NDISyphon app and I get the same result. The difference is that in NDISyphon app if I check "Receive like RGB?" displayed correctly. I understand that this is a matter of the color space in which the NDI signal is transported but the problem is that, for example, in Madmapper I do not have the possibility of receiving the input as RGB.
Best

Javi

Please open a support ticket. Isadora should not have any trouble outputing to any display recognized by your operating system.

A link to our support form can be found in my signature.

Hi all

Many thanks for the pointers and tips.

My lateness in replying was down to the multitude of work as per the usual last minute why have you stopped working moment! 

The issue lay with quicktime in the end. DusX's suggestion made me actually think about the problem as opposed to just restarting and hoping for the best.

 I went into the activity monitor and discovered that quicktime was frozen and taking up no RAM space etc. I quit the process and restarted. All worked fine and has done since.

I had never seen that type of issue before. I realised I had tried VLC but not actually Quicktime. It seems that the quicktime engine had a mild stroke etc. The computer in question is doing a lot of other jobs in terms of gallery control and I do not really have another spare unit like it. I have spares but would require a bit of work to reset this system even with file back ups.

Problem cured and all resolved.

Many thanks again

eamon

First of all, thanks very much to everyone who answered, that's what I love about this forum.

Special thanks to @Woland for your long and specific answer.

I've been doing some testing on these things, I post what I found in case somebody else finds it useful:

- The error in 2.6.1 was indeed caused by my 3D models, but not by the file itself, rather than the path. For some reason, if I put the 3D files in my desktop, Isadora has no trouble, but whenever the files are inside any folder, the error window pops up.

- The mouse watcher error only happens with an imported 2.6.1 patch. The mouse watcher works as expected in Izzy 3 if you make a new patch, but it doesn't if you open an old file. Maybe if I was able to save it (updating it in the process) it would behave correctly afterwards, but I have no way of knowing this... yet.

- As for the Blur taking up a lot of CPU usage, I found out that a missing FreeFrame plugin could be the actual problem. After I installed the FFMotionBlur (which was in the 32-bit plugins folder but not in the 64-bit one) the scene runs in Izzy 3 more or less the same way than in Izzy 2.

Thanks again everybody. I think I will be updating to Isadora 3 very soon, since it's clearer now than the problems were more closely related to using Izzy 2 in Mojave and I really want to try some of the new features (like Blind Mode and such). Cheers.

Hi @Eva 

Resetting preferences is often a remedy: Resetting Isadora Preferences

Best Wishes

Russell

@juriaan

I'm not sure that this functionality is something that we should change. If we change the way this works, it could break people's patches that have already been created to work with this behavior.

@dbini said:

a new ticket

 Yes, a ticket would be great. It'll be easier for use to follow and provide support than in the forum

@woland Hi, thank for reply i mainly need isadora 2 because i'm on windows and Isadora 3 cant get any sound input...

Ha okay ;) thanks!

@mark said:

Does this mixer allow you to get video into the Live Capture Settings using the Blackmagic driver? Or????

And in Windows it's the same: the ATEM input is seen as a Webcam in Isadora, and you just set the driver to Windows NOT Blackmagic.

Recovering Isadora 3.07 has been a big help in trouble shooting the stream setup to Blackboard Collaborate. I am still getting intermittent black video where it appears the stream is previewing in the Live Capture Settings but not then displaying through the Video In Watcher. After trying to pin this down, I think it requires a specific sequence of activation steps to maintain the through put of the video. I tried a bit harder with direct audio through the camera and can only conclude that Blackboard Collaborate is noisy and without a convenient way to monitor the audio stream before going live. I did manage some improvement by recording the stream and playing it back-that appeared to be the only way to know what the stream sounds like. Anyway after setting the sensitivity of the Senhieser radio transmitter to -24db I was able to reduce some of the noise. Monitoring audio through the camera sounds fine and through Isadora sounds fine, so my conclusion is that Blackboard Collaborate does not handle audio that well. But I will keep trying to get clean audio.

I am hoping to get the video and audio stream to run through Isadora, and I will keep trying to get a stable patch configuration.

Best wishes

Russell

I have confirmed this as fixed in the most recent internal beta, so it'll be solved for the next public release.

Thank you to be so focused on my problem. As you asked me, I should probably better open bug a ticket. But it's gonna be quite complicate to continue testing since this computer and the BM card and all stuff are not mine and belonging to a company, I finish the session tomorrow, leave to the other side of France and I am afraid will not be able to continue working with this computer before end of november ( a week before Première! )  But I will open a ticket as soon as I have time for that in the next days, including some samples of the scenes...

Just some last informations here about what you're asking : the computer is a 13 '  Intel Core i5 quadricœur / 10ᵉ generation 2 GHz (Turbo Boost until 3,8 GHz / 16 Go RAM LPDDR4X  3 733 MHz / Intel Iris Plus Graphics / SSD 512 Go.

I have tried to plug a mouse today to see the difference but I must confess in the concentration, I  forgot to use it most of the time, the force of habit with trackpad... :-(  

Every time it happen today, I have paid attention to the Load ratio in Isadora, but it was not specially high, from 20 to 40 maybe, but I guess I should rather watch the activity monitor. I will try tomorrow. 

In fact the Load ratio is going high and above 100% only when I activate the Video delay actor(s) , specially when I activate 3 in the same time :-) . But I not only bypass them when I don't use it, I also close a Gate actor between live feed and them, otherwise even with Delay actor bypass, it explode the Load ratio... And it is not specially when they are active that the problems happen... 

To relativize the problem, every time I have just played the scenes, actor window closed, everything just work fine ( with sometimes a frightening 150% load red light ! ) and troubles are only when I am building... So Isadora is still my favorite friend ;-)

Thank you @Michel !!!!!!

It is working for me now.

You rock!

-Alex