ffmpeg -ss 60 -i Episode10_RmvAdVi_1_6299.mp4 -to 120 -c:v copy -c:a copy Episode10_RmvAdVi_1_6299_1.mp4
ffmpeg -ss 60 -i Episode10_RmvAdVi_1_6299.mp4 -t 120 -c:v copy -c:a copy Episode10_RmvAdVi_1_6299_2.mp4
imac> avinfo Episode10_RmvAdVi_1_6299.mp4
Episode10_RmvAdVi_1_6299.mp4
length: 00:04:01.34, start: 0.000000, bitrate: 3170 kb/s
stream: #0:0(eng): Video: h264 (Main) (avc1 / 0x31637661), yuv420p(tv, bt470bg), 720x576 [SAR 128:117 DAR 160:117], 2987 kb/s, SAR 787:720 DAR 787:576, 24 fps, 24 tbr, 24k tbn, 48 tbc (default)
stream: #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 189 kb/s (default)
ffmpeg -ss 60 -i Episode10_RmvAdVi_1_6299.mp4 -t 120 -c:v copy -c:a copy foo.mp4
Checked clip beginning, entire clip played, end of clip.
This means you'll see... well... no telling what... till you hit the next B frame, so if the time gap is long you might see all white, all black, gibberish...
You might also try using -t 60, as the -t + -to logic might run differently internally.
Using -t (duration), seems like ffmpeg somehow handles the gaps correctly, so first frame is always correct.
Or at least, using -t, I've never seen the problem you describe.