Setting repeat count

[DjordjeMandic]

Is it possible to change count of repeats in any other tab besides hardware? I need to enter my own count of repeats.

[bengtmartensson]

I am not quite sure what you want. The framed quantity describes the number of repeats contained in a received IR sequence; on the hardware tab you enter the number of repeats (= count - 1, if the intro is non-empty) you want to send.

You can possibly invoke harchardware (which is installed as a command line program when you install IrScrutinizer in some installations) to solve your problem.

This command line command turns on my Sony TV (which ignores just one copy)

$ harchardware --globalcache --ip 192.168.1.70 send --protocol sony12  --names D=1,F=21 --count 3

(Normally, I use another method to turn on the TV :-) ).

If this does not help, you have to give more details.

[DjordjeMandic]

I copied the rendered signal into the Scrutinize Signal tab and used the Transmit button from there. I was wondering if there’s any other way in the GUI (or even in the textual representation of the IR code) to set a custom repeat count, since the dropdown menu in the Hardware tab doesn’t allow fine adjustments.

Thanks for the command-line suggestion—I’ll give it a try! But for now, when using the GUI, I seem to be limited to the predefined repeat counts in the Hardware tab.

[bengtmartensson]

I copied the rendered signal into the Scrutinize Signal tab and used the Transmit button from there.

There is a "Transmit" button on the Render pane too...

I was wondering if there’s any other way in the GUI (or even in the textual representation of the IR code) to set a custom repeat count,

Short answer is "No".

since the dropdown menu in the Hardware tab doesn’t allow fine adjustments.

Errr... what is "fine adjustments" to an integer parameter?

If you have an enhancement to suggest, please do so (for example as issue), including a motivation, as detailed as possible.
Possibly you are even able to code it and submit a PR? However note that IrScrutinizer (as the name suggests) is not meant as a deployment solution . Also, I am somewhat reluctant (but not a priori dismissive) to spend time of pure GUI-fiddling that does not improve functionality.