JEdgerly

Didn't think it is worth creating a new thread for but found another bug. Copying and pasting a media element, or task containing a media element which has control formula assigned from an Input with a single period in the Input Name (i.e: 'LED.SATURATION') will cause a crash. If the Input Name contains no period, or two or more periods, this issue does not occur. Thought I was chasing a corrupt show until I narrowed this down...

Is the SDI output support limited to the WatchMax, or is there support for other SDI cards like BlueFish, Datapath, Blackmagic, etc.?

I had a similar issue, that I eventually found the source of. Worked all day, show started, and production did nothing. Responded locally but not controlling displays. Restart production, works fine. My cause? I had a few elements that were HAP in free running loops, fairly short. If left running, after a few hours, they started to bog down production very quickly at some point. 10 second loop would lock up after a few hours. I rendered a much longer version, and found it would go days without locking up. It seems that after a certain number of iterations it would lock up. It happened twice, so I systematically ran my elements one by one every night until I found the issue. This was in 6.2.2 I believe. FWIW...

Simplest would be to change your show from 60 to 59.94. Your output is not running at 60, likely due to EDIDs. What is your output? (Monitor, projector, LED processor, etc.)

We had a similar issue when adopting wx9100 cards. What AMD driver are you using? Rolling back to 17q4 resolved the issues we were having. Played fine, then would stutter.

Glad to see you got it worked out. For something like this, I would usually just run 1920x1200 outputs. One virtual for each 2x5/2x6, arranged on the stage to match their physical arrangement, then neatly stacked with 4 or 5 per raster. Depends on the LED vendor's wishes.

I have seen similar behavior lately, I may be experiencing the same issue you describe. For example, if I have 6 identical displays and force EDIDs, using one for all displays, several will sometimes show no signal or 'out of range'. Inspection confirms there are no differences in the EDID's. I have a library of EDID's including from ImagePros that I cycle through until I find one the display 'likes' so to speak. I will try rolling back and see if the issue goes away. This is with w9100's on 17Q2. Win 7, both i7 and Ryzen builds.

How about being able to color code tasks in the Task Window? Similar to how mac does, would be great for quickly identifying different groups of tasks. White text on black background kind of runs together when you have 100+ tasks... Even with dummy tasks of "--------------------"! Would be great for those of us running shows from production.

Found a quirky behavior I believe to be incorrect. When applying an Offset tween with a negative value to lower black levels, then applying a contrast tween, the contrast is making any Offset values below 0 turn positive. Seems to be a math error of values going positve rather than remaining bleow 0 (and thereby 0). The following images illustrate the issue.

We feed LED walls, projectors and monitors 23.98/24. We do a lot of film and television work where we are syncing to cameras. Most TVs won't flicker but some will unless you feed them 23.98/24. Projectors and LED more so. Workflow for content delivery is often 23.98. I can sometimes work around it by doubling to 47.97/48Hz, but not everything supports that. Some will still lock to it thinking it is PAL. 24fps Content -> 24fps Watchout -> 24fps Displays -> 24fps Camera shooting it. With 23.98 content, I occasionally run into micro stuttering with smooth moving graphics. I always write custom EDIDs for the connected display and force the outputs. All our machines have FirePro w7100/w8100/w9100 w/s400 sync cards. I tell the graphics card what to do, the display is just along for the ride

Speak not of that which you nothing about. Not every WO show is made for consumption by the human eye. Frame rates DO matter. The VAST majority of content for television is still shot 23.98p/59.94i. There is a whole world outside of staging events...

With two PCIe 3.0 M.2's in PCIE cards, striped raid, we are seeing sequential reads of 7+ GB a sec. Running Windows 7. Separate SSD for the OS. FWIW

Would love to see the minimum framerate in Show Preferences dropped to 23.976...

Show Preference is set to 24. 30 Hz output throws the message and halts. Strangely, another Display computer driving 48 Hz to an LED wall works fine. Is there any method by which to force the previous behavior, perhaps a commandline switch? I can send you the EDIDs of the troublesome outputs for testing if it helps. FWIW, system specs are: AMD FirePro W9100 (w/s400 sync card) w/Active DP1.2 - HDMI 2.0a dongles Drivers: Radeon Pro and AMD FirePro Settings Version 2016.1204.1136.20853 Intel i7-5960X (8-Core, 3.00GHz) The Display Computers in question are outputting three 3840x2160@30Hz each. As an aside, would love to see the minimum framerate dropped to 23.976. I am often involved in dropframe workflow, which leads to micro-jitters in smooth animations when forced to run at 24.000

Hi all, So In the past I have always been able to force specific monitors to run at a different framerate... i.e. Show is running at 24 fps, but some monitors wont accept 24 frame, so I run modified EDIDs that force them to 30. Previously, Production would simply throw a caution in the Mesages window about framerate, and Display would go online as usual, applying frame blending. On this show I have updated to 6.1.5, but now I get the "Specified resolution and framerate cant be set..." I can't get past that point... Any thoughts on a cause for the difference in behavior? Should I be looking into a hardware/windows issue? ETA: Just rolled back to 6.1.4 and it works as it once had, giving the Caution in 'Messages'. Roll forward to 6.1.5 and it halts the display with "Specified resolution and framerate cant be set..."