1.3.0 Bugs

[FBox467]

1.3.0 (Windows 10)
It just keeps getting worse with every new version.
DOES ANYONE EVEN TEST THIS???

1. Once recording starts, you can’t click or scroll anywhere—the recording window seems to block everything underneath it

2. Lightning export doesn’t work—it keeps getting stuck on “Prepare”

3. Timeline:
   After changing the speed to 0.5x, the clips overlap (zoom does too).

4. The clip lacks information about the set speed.

[meiiie]

Thanks for reporting this on 1.3.0 / Windows 10. I mapped the symptoms on current main as separate fixes, so no extra repro checklist from you yet:

• Windows 10 HUD/input blocking
• Lightning export stuck before useful progress
• speed-edited timeline overlap plus visible speed information

I labeled this as bug + priority. Next step is to split the fixes into small hotfix PRs and link them back here.

[meiiie]

Opened draft PR #582 for the Lightning/Auto route suspect: #582

That PR is intentionally only for the Prepare export path. The Windows 10 HUD/input blocking and timeline speed overlap still need separate small fixes.

Note: I have a question before continuing: did this bug appear in previous beta versions? (This helps us determine if this is a new bug or one that has appeared before.)

[Jdumps]

1.3.0 Win10
after updating i also have the same problem, i no longer see the count down and can't click nor scroll behind recordly. I did not have this problem before updating.

[meiiie]

Thanks, that is useful confirmation. Since this appeared after updating to 1.3.0, I am treating the HUD/input-blocking + missing countdown behavior as a Windows 10 regression in Recordly rather than a local setup issue.

#582 has already been merged for the separate Lightning export stuck on Prepare path. That does not fix the HUD/input blocker.

Next step is a separate small hotfix focused only on the recorder HUD mouse passthrough/countdown behavior, and I will link the PR back here before asking for more repro details.

[meiiie]

Opened draft PR #584 for the Windows 10 HUD/input-blocking part: #584

This is intentionally scoped to the recorder HUD mouse passthrough/countdown area only. #582 covered the separate Lightning Prepare export path; timeline speed overlap is still separate.

The local checks are green, but I am keeping #584 draft until we get a Windows 10 runtime smoke on the affected behavior.

[Litemint09]

1.3.0 (Windows 10) It just keeps getting worse with every new version. DOES ANYONE EVEN TEST THIS???

1. Once recording starts, you can’t click or scroll anywhere—the recording window seems to block everything underneath it
2. Lightning export doesn’t work—it keeps getting stuck on “Prepare”
3. Timeline:
   After changing the speed to 0.5x, the clips overlap (zoom does too).

4. The clip lacks information about the set speed.

Im on windows 11 pro, those 1 and 2 i havent experienced it, for number 3 i havent tried.

[meiiie]

Opened draft PR #585 for the timeline speed overlap and visible speed label part: #585

This is intentionally scoped to item 3/4 only. #582 already covered the separate Lightning export Prepare path, and #584 remains the separate Windows 10 HUD/input-blocking fix pending runtime smoke.

[meiiie]

Merged #584 for the Windows 10 HUD/input-blocking part: #584

Current main now includes the split fixes for the reported areas:

• fix(export): keep Windows auto off static layout first #582: Lightning export stuck on Prepare
• fix(recording): compact HUD fallback on Windows 10 #584: Windows 10 HUD/input-blocking fallback
• fix(editor): guard timeline speed overlap #585: timeline speed overlap and visible clip speed

Please retest on a build from latest main when available, especially the Windows 10 click/scroll/countdown behavior.

[webadderall]

1.3.0 (Windows 10) It just keeps getting worse with every new version. DOES ANYONE EVEN TEST THIS???

1. Once recording starts, you can’t click or scroll anywhere—the recording window seems to block everything underneath it
2. Lightning export doesn’t work—it keeps getting stuck on “Prepare”
3. Timeline:
   After changing the speed to 0.5x, the clips overlap (zoom does too).

4. The clip lacks information about the set speed.

This was indeed tested in a beta release, thank you for reporting! We'll work on fixes