Clicking "Cut" on a clip candidate immediately freezes the app Windows
title bar shows "AutoShorts (Not Responding)" right from the start of
the click not after a delay
Steps to reproduce:
- Import a long source video (71 minutes)
- Run Transcribe + Find Viral Moments (used Ollama/Qwen 2.5 7B locally)
- Select a clip candidate and click "Cut"
- App immediately shows "Not Responding" in the title bar
Observed:
- Task Manager shows ffmpeg.exe running with active CPU (15-17%) so
it's not fully dead but the UI is completely unresponsive from the
moment Cut is clicked
- Tested with two different short clip candidates (20s and 8s) both
from timestamps near the 69-71 minute mark of a 71-minute source file.
- Suspect ffmpeg may be seeking/decoding from the start of the source
file rather than jumping directly to the clip timestamp, which would
explain why cut time doesn't match the short output clip length.
Environment:
- Windows 11
- RTX 4050, i5 13th gen, 32GB RAM
- LLM engine: Ollama (Qwen 2.5 7B), local Whisper for transcription
- Source video: 71 min MP4
Clicking "Cut" on a clip candidate immediately freezes the app Windows
title bar shows "AutoShorts (Not Responding)" right from the start of
the click not after a delay
Steps to reproduce:
Observed:
it's not fully dead but the UI is completely unresponsive from the
moment Cut is clicked
from timestamps near the 69-71 minute mark of a 71-minute source file.
file rather than jumping directly to the clip timestamp, which would
explain why cut time doesn't match the short output clip length.
Environment: