Feature Request - Transmit View - Manually Set FPS Hz

[EVeik]

Have a couple of sites that make heavy use of pixel mapping and other media using sACN as it's protocol of choice over the network. Some of these controllers use a refresh rate at high as 60hz (FPS).

During troubleshooting of the network, we found it difficult to reproduce that high of an FPS using anything except the third-party controller.

Was wondering if it is possible to have a field and manually set the FPS in the Transmit tool to a static level. This would help troubleshooting and give us a predetermined frequency of packets to look for.

My thought it to restrict the values to what is permitted by the protocol which I believe 1 or 2 FPS up to ...?
I am guessing since there are media controllers out there running at 60hz, that it's allowed.

[marcusbirkin]

"Fade Rate" under Fade Range of a transmit window allows you to alter the FPS.
Avaliable options are 0.5,1,2,5,10,25,50,75,100,500Hz

In practice the 500Hz option will actually be limited by the source hardware!

[marcusbirkin]

Static, while slightly inaccurate, fade rates are already avaliable by the effect generator.
Also links with #187 and #156

[RichardTea]

For clarification: Under "normal" operation, the maximum refresh rate permitted by the standard is 44 FPS for a full 512-slot universe.

However, the standard does explicitly permit implementations to have "user-configurable" rates faster than this, with no upper limit.

E1.31-2018, para 6.6.1:

E1.31 sources shall not transmit packets for a given universe number at a rate which exceeds the
maximum refresh rate specified in E1.11 [DMX] unless configured by the user to do so.
For a given universe that contains only E1.31 devices—a universe with no devices that convert from
E1.31 to DMX512-A—an E1.31 source may be configured to observe higher refresh rates than those
specified in the [DMX] standard or above. In order to maintain compatibility with non-E1.31 components,
the E1.31 source shall provide a user-configurable option to enable or disable these higher refresh rates

(My emphasis)
E1.11 specifies timings that work out as ~44 FPS for 512 slot zero start code packets. It's likely that a lot of equipment will not be able to process refresh rates much higher than this.

[marcusbirkin]

Having just looked at the effect engine, having that directly control the FPS from the fade rate is undesirable.
So reopening this request, so a seperate FPS can property can be exposed in the transmit window.