Error screen recording has stopped unexpectedly

Recently, this problem has begun to manifest itself, and is surely a very big issue. I am running vMix HD 12.0.0.131 x64 during a recording using the MPEG-2 codec. After some time, I receive:...

vMix Forums
 » 
General
 » 
General Discussion
 » 
Recording has stopped unexpectedly

lbgaus

 


#1
Posted
:

Sunday, July 20, 2014 6:37:35 AM(UTC)

lbgaus

Rank: Advanced Member

Groups: Registered

Joined: 11/30/2013(UTC)
Posts: 161
Location: Seoul, South Korea

Thanks: 39 times
Was thanked: 19 time(s) in 14 post(s)

Recently, this problem has begun to manifest itself, and is surely a very big issue. I am running vMix HD 12.0.0.131 x64 during a recording using the MPEG-2 codec. After some time, I receive:

UserPostedImage

I am recording to an NTFS formatted SAMSUNG 840 EVO MZ-7TE250BW 2.5″ 250GB SSD on a Windows 7 x64 system with these settings:

UserPostedImage

The recording logfile is as follows. Please help me get to the bottom of this.

7/18/2014 1:19:24 AM, Version: 12.0.0.131 x64
7/18/2014 1:19:24 AM, Size: 1920×1080
7/18/2014 1:19:24 AM, System: NTSC 59.94i or 29.97p
7/18/2014 1:19:24 AM, Codec: Microsoft MPEG-2 Encoder
7/18/2014 1:19:24 AM, Format: UYVY 16 1498831189
7/18/2014 1:19:24 AM, AudioDevice: vMix Audio
7/18/2014 1:19:24 AM, AudioFormat: 48000 Hz 16 Bit 2 Channels
7/18/2014 1:19:24 AM, AudioDelay: 0
7/18/2014 1:19:24 AM, RestartInterval: 0
7/18/2014 1:19:24 AM, BitRate: 25
7/18/2014 1:28:35 PM, StartRecording
7/18/2014 1:30:10 PM, StopRecording
7/18/2014 1:30:10 PM, Duration: 00:01:35
7/18/2014 1:30:10 PM, Frames: 2448
7/18/2014 1:30:10 PM, DroppedFrames: 401
7/18/2014 1:30:10 PM, DueToSourceFrameRate: 0
7/18/2014 1:30:10 PM, DueToHardDiskOrCPU: 401
7/18/2014 1:30:10 PM, DroppedSamples: 0
7/18/2014 1:30:10 PM, MissedSamples: 0
7/18/2014 1:30:10 PM, SyncedSamples: 0
7/18/2014 1:30:10 PM, AudioOffset: 0
7/18/2014 1:30:10 PM, AudioDelay: 0
7/18/2014 1:30:10 PM, AudioEngine
7/18/2014 1:30:10 PM, Running: True
7/18/2014 1:30:10 PM, SampleRate: 48000hz 16 Bit
7/18/2014 1:30:10 PM, MixingErrors: 0
7/18/2014 1:30:10 PM, Streams
7/18/2014 1:30:10 PM, Stream0
7/18/2014 1:30:10 PM, Samples: 2193530
7/18/2014 1:30:10 PM, Dropped: 0
7/18/2014 1:30:10 PM, Latency: 1
7/18/2014 1:30:10 PM, Stream1
7/18/2014 1:30:10 PM, Samples: 0
7/18/2014 1:30:10 PM, Dropped: 0
7/18/2014 1:30:10 PM, Latency: 0
7/18/2014 1:30:10 PM, AudioInputs
7/18/2014 1:30:10 PM, Cam 1
7/18/2014 1:30:10 PM, Latency: 60/67
7/18/2014 1:30:10 PM, Dropped: 0
7/18/2014 1:30:10 PM, Resampled: 1015 ms


Back to top

lbgaus

 


#2
Posted
:

Sunday, July 20, 2014 6:42:56 AM(UTC)

lbgaus

Rank: Advanced Member

Groups: Registered

Joined: 11/30/2013(UTC)
Posts: 161
Location: Seoul, South Korea

Thanks: 39 times
Was thanked: 19 time(s) in 14 post(s)

It is very suspicious to me how QuickTime MOV files in my project appear to be playing properly, but there are no Filters appearing in the settings…

Other files I have loaded that are not MOV shows filter list correctly.

Additionally, the first recording after this failure in the same vMix session produces a TS file with audio only and no video. Stopping recording and then beginning recording again after this appears to re-initialize the video codec in the recording, only for it to fail again soon after. It appears it *may* be failing predictably when recording when the active input is an MOV file, as it takes longer (if at all) for the recording to crash when the active input is a different file.

UserPostedImage


Back to top

admin

 


#3
Posted
:

Sunday, July 20, 2014 7:18:15 AM(UTC)

admin

Rank: Administration

Groups: Administrators

Joined: 1/13/2010(UTC)
Posts: 4,926
Man
Location: Gold Coast, Australia

Was thanked: 3840 time(s) in 1410 post(s)

What graphics card and CPU are you using?
What does the CPU usage and Render Time look like while recording?

There will be no filters in the list when playing QuickTime videos.

You can also try the latest vMix 13 preview to see if it helps.

Regards,

Martin
vMix


Back to top

WWW
BLOG

lbgaus

 


#4
Posted
:

Sunday, July 20, 2014 7:36:21 AM(UTC)

lbgaus

Rank: Advanced Member

Groups: Registered

Joined: 11/30/2013(UTC)
Posts: 161
Location: Seoul, South Korea

Thanks: 39 times
Was thanked: 19 time(s) in 14 post(s)

I have a Core i7 4770k processor and a ASUS GTX650TI-OC-2GD5 Video Card. The render time during recording says between 4-6ms, and the processor at 9%. I Will try the beta version and report back soon. The system does not look to be under much load.


Back to top

lbgaus

 


#5
Posted
:

Sunday, July 20, 2014 8:06:49 AM(UTC)

lbgaus

Rank: Advanced Member

Groups: Registered

Joined: 11/30/2013(UTC)
Posts: 161
Location: Seoul, South Korea

Thanks: 39 times
Was thanked: 19 time(s) in 14 post(s)

This problem exists in 13.0.0.136. When I begin recording and have this particular QuickTime file playing on the live output, recording crashes within a minute. I will try other QuickTime files to see if I can establish a pattern.


Back to top

admin

 


#6
Posted
:

Sunday, July 20, 2014 9:00:56 AM(UTC)

admin

Rank: Administration

Groups: Administrators

Joined: 1/13/2010(UTC)
Posts: 4,926
Man
Location: Gold Coast, Australia

Was thanked: 3840 time(s) in 1410 post(s)

Thanks for the info.

Would it be possible to send us a copy of the Quicktime file?
There might be a rare video/audio format in the file causing the player to corrupt the recording.

You can upload the file to https://fileobject.com/ and then email us at info@vmix.com.au

Regards,

Martin
vMix


Back to top

WWW
BLOG

lbgaus

 


#7
Posted
:

Sunday, July 20, 2014 9:57:50 AM(UTC)

lbgaus

Rank: Advanced Member

Groups: Registered

Joined: 11/30/2013(UTC)
Posts: 161
Location: Seoul, South Korea

Thanks: 39 times
Was thanked: 19 time(s) in 14 post(s)

I have tried it on an entirely different computer with the same results using this MOV file. I have emailed it to you. Hope it helps you debug.


Back to top

admin

 


#8
Posted
:

Sunday, July 20, 2014 10:27:34 AM(UTC)

admin

Rank: Administration

Groups: Administrators

Joined: 1/13/2010(UTC)
Posts: 4,926
Man
Location: Gold Coast, Australia

Was thanked: 3840 time(s) in 1410 post(s)

Thanks,

Just to confirm, this test should show the problem?

1. Open vMix 13.0.0.136
2. Add Intro.mov as input and play in loop.
3. Start MPEG2 TS recording at 1920×1080 29.97p / 59.94i 25Mbps

After a couple of minutes, recording should stop.

I’ve been running this test a few times so far and everything looks ok, so there
must be some other setting or input that contributes to this problem.

Regards,

Martin
vMix


Back to top

WWW
BLOG

lbgaus

 


#9
Posted
:

Sunday, July 20, 2014 11:04:02 AM(UTC)

lbgaus

Rank: Advanced Member

Groups: Registered

Joined: 11/30/2013(UTC)
Posts: 161
Location: Seoul, South Korea

Thanks: 39 times
Was thanked: 19 time(s) in 14 post(s)

I have done exactly as you described on two different machines and both exhibit this behavior. I will keep gnawing at this until I know the special conditions required to make this happen, or I give up in frustration.


Back to top

ovinas

 


#10
Posted
:

Sunday, July 20, 2014 12:01:39 PM(UTC)

ovinas

Rank: Advanced Member

Groups: Registered

Joined: 6/4/2013(UTC)
Posts: 308
Man
Location: Germany

Thanks: 1 times
Was thanked: 57 time(s) in 49 post(s)

You could share the file so some other users could test this.


Back to top

WWW
BLOG

thanks 1 user thanked ovinas for this useful post.

lbgaus

on 7/20/2014(UTC)

lbgaus

 


#11
Posted
:

Sunday, July 20, 2014 12:05:21 PM(UTC)

lbgaus

Rank: Advanced Member

Groups: Registered

Joined: 11/30/2013(UTC)
Posts: 161
Location: Seoul, South Korea

Thanks: 39 times
Was thanked: 19 time(s) in 14 post(s)

If anyone has any problems performing the tasks described by Martin above with this file, I would appreciate your feedback. I’m trying to figure out what’s the deal here, it seems very predictable on my end.

https://fileobject.com/jcmidcrxyjbccf/


Back to top

lbgaus

 


#12
Posted
:

Sunday, July 20, 2014 12:39:44 PM(UTC)

lbgaus

Rank: Advanced Member

Groups: Registered

Joined: 11/30/2013(UTC)
Posts: 161
Location: Seoul, South Korea

Thanks: 39 times
Was thanked: 19 time(s) in 14 post(s)

So far, the only thing I have discovered that makes any difference is when I uncheck Audio in the recording settings, the MPEG-2 TS recording does not terminate unexpectedly anymore. Checking it and hitting Record again crashes it within 60 seconds.

This holds true for both computers I am testing with:
(1) vMix 12.0.0.129 on Win7x64 Core 2 Quad w/ nVidia GTX 260
(2) vMix 13.0.0.136 on Win7x64 Core i7 4770K w/ nVidia GTX 650TI


Back to top

ovinas

 


#13
Posted
:

Sunday, July 20, 2014 12:42:07 PM(UTC)

ovinas

Rank: Advanced Member

Groups: Registered

Joined: 6/4/2013(UTC)
Posts: 308
Man
Location: Germany

Thanks: 1 times
Was thanked: 57 time(s) in 49 post(s)

Tested this several times with absolutely no problems.


Back to top

WWW
BLOG

cutter07

 


#14
Posted
:

Sunday, July 20, 2014 1:09:29 PM(UTC)

cutter07

Rank: Advanced Member

Groups: Registered

Joined: 6/2/2012(UTC)
Posts: 103
Man
Location: Germany

Thanks: 13 times
Was thanked: 10 time(s) in 9 post(s)

I got the same error.

http://youtu.be/zsKWPrc0l0o

19.07.2014 19:07:18, Version: 13.0.0.136 x64
19.07.2014 19:07:18, Size: 1920×1080
19.07.2014 19:07:18, System: NTSC 59.94i
19.07.2014 19:07:18, Codec: Microsoft MPEG-2 Encoder
19.07.2014 19:07:18, Format: UYVY 16 1498831189
19.07.2014 19:07:18, AudioDevice: vMix Audio
19.07.2014 19:07:18, AudioFormat: 48000 Hz 16 Bit 2 Channels
19.07.2014 19:07:18, AudioDelay: 0
19.07.2014 19:07:18, RestartInterval: 0
19.07.2014 19:07:18, Buffers: 10
19.07.2014 19:07:18, BitRate: 25
19.07.2014 19:07:18, StartRecording
19.07.2014 19:07:55, StopRecording
19.07.2014 19:07:55, Duration: 00:00:37
19.07.2014 19:07:55, Frames: 752
19.07.2014 19:07:55, DroppedFrames: 338
19.07.2014 19:07:55, DueToSourceFrameRate: 0
19.07.2014 19:07:55, DueToHardDiskOrCPU: 338
19.07.2014 19:07:55, DroppedSamples: 1
19.07.2014 19:07:55, MissedSamples: 0
19.07.2014 19:07:55, SyncedSamples: 0
19.07.2014 19:07:55, AudioOffset: 0
19.07.2014 19:07:55, AudioDelay: 0
19.07.2014 19:07:55, AudioEngine
19.07.2014 19:07:55, Running: True
19.07.2014 19:07:55, SampleRate: 48000hz 16 Bit
19.07.2014 19:07:55, MixingErrors: 0
19.07.2014 19:07:55, Streams
19.07.2014 19:07:55, Mixer
19.07.2014 19:07:55, Samples: 2303
19.07.2014 19:07:55, Dropped: Read 0 Write 0
19.07.2014 19:07:55, Latency: 0 ms
19.07.2014 19:07:55, Errors: 0
19.07.2014 19:07:55, Output
19.07.2014 19:07:55, Samples: 2302
19.07.2014 19:07:55, Dropped: Read 0 Write 1
19.07.2014 19:07:55, Latency: 0 ms
19.07.2014 19:07:55, Errors: 0
19.07.2014 19:07:55, Headphones
19.07.2014 19:07:55, Samples: 2301
19.07.2014 19:07:55, Dropped: Read 0 Write 2
19.07.2014 19:07:55, Latency: 0 ms
19.07.2014 19:07:55, Errors: 0
19.07.2014 19:07:55, A
19.07.2014 19:07:55, Samples: 2302
19.07.2014 19:07:55, Dropped: Read 0 Write 1
19.07.2014 19:07:55, Latency: 0 ms
19.07.2014 19:07:55, Errors: 0
19.07.2014 19:07:55, FFMpeg
19.07.2014 19:07:55, Samples: 1843
19.07.2014 19:07:55, Dropped: Read 0 Write 0
19.07.2014 19:07:55, Latency: 1000 ms
19.07.2014 19:07:55, Errors: 0


Back to top

thanks 1 user thanked cutter07 for this useful post.

lbgaus

on 7/20/2014(UTC)

lbgaus

 


#15
Posted
:

Sunday, July 20, 2014 9:25:00 PM(UTC)

lbgaus

Rank: Advanced Member

Groups: Registered

Joined: 11/30/2013(UTC)
Posts: 161
Location: Seoul, South Korea

Thanks: 39 times
Was thanked: 19 time(s) in 14 post(s)

This seems to be rather incredibly bizarre. In my testing, having it set to TS format, 1920×1080, 25Mbps, Audio enabled makes it crash within 60 seconds. Changing the bitrate, resolution, audio, or format makes it run for at least 25 minutes without problems (I stopped testing after 5 minutes).


Back to top

admin

 


#16
Posted
:

Sunday, July 20, 2014 9:34:02 PM(UTC)

admin

Rank: Administration

Groups: Administrators

Joined: 1/13/2010(UTC)
Posts: 4,926
Man
Location: Gold Coast, Australia

Was thanked: 3840 time(s) in 1410 post(s)

Ok, I have been able to re-create the problem.
The key thing appears to be running the vMix output at 59.94p and then recording to interlaced 59.94i.

Can you confirm this in your setup? If so that might be the common problem.


Back to top

WWW
BLOG

thanks 1 user thanked admin for this useful post.

lbgaus

on 7/21/2014(UTC)

lbgaus

 


#17
Posted
:

Sunday, July 20, 2014 10:03:37 PM(UTC)

lbgaus

Rank: Advanced Member

Groups: Registered

Joined: 11/30/2013(UTC)
Posts: 161
Location: Seoul, South Korea

Thanks: 39 times
Was thanked: 19 time(s) in 14 post(s)

The master frame rate in my project on both machines is 29.97p. Setting the project frame rate to 59.94p produces the same problem, I’m not sure if this makes sense with the problem you observed yourself. I still see at least a delay in the problem manifesting itself if I change any of the recording settings as I described above.

I started testing to try to reproduce this problem after it occurred in a soccer event about 90 minutes into the recording. At that time some MOV files, including this one I have used as a problem demo, were loaded in the project but were not the active input. Instead, we just showed this MOV file once as the introduction, then cut to other clips and live inputs for the rest of the broadcast, which I assume is why the recording took much longer before it failed.

For some reason looping this file during a recording seems to accelerate the hanging of the Microsoft MPEG-2 encoder.


Back to top

IceStream

 


#18
Posted
:

Monday, July 21, 2014 12:09:21 AM(UTC)

IceStream

Rank: Advanced Member

Groups: Registered

Joined: 3/7/2012(UTC)
Posts: 2,511
Man
Location: Canada

Thanks: 32 times
Was thanked: 481 time(s) in 452 post(s)

Not sure it is of any more help but the error occurred for me 29 seconds into the recording.
Win7 Pro x64
i7 950 3.07GHz 24 GB Ram
NVidia GeForce GTX 470
Video recording to Storage drive Hitachi 2TB HDD
Settings same as OP
Log file:

7/19/2014 11:28:55 PM, Version: 13.0.0.136 x64
7/19/2014 11:28:55 PM, Size: 1920×1080
7/19/2014 11:28:55 PM, System: NTSC 59.94i
7/19/2014 11:28:55 PM, Codec: Microsoft MPEG-2 Encoder
7/19/2014 11:28:55 PM, Format: UYVY 16 1498831189
7/19/2014 11:28:55 PM, AudioDevice: vMix Audio
7/19/2014 11:28:55 PM, AudioFormat: 48000 Hz 16 Bit 2 Channels
7/19/2014 11:28:55 PM, AudioDelay: 0
7/19/2014 11:28:55 PM, RestartInterval: 0
7/19/2014 11:28:55 PM, Buffers: 10
7/19/2014 11:28:55 PM, BitRate: 25
7/19/2014 11:28:58 PM, StartRecording
7/19/2014 11:29:28 PM, StopRecording
7/19/2014 11:29:28 PM, Duration: 00:00:29
7/19/2014 11:29:28 PM, Frames: 524
7/19/2014 11:29:28 PM, DroppedFrames: 349
7/19/2014 11:29:28 PM, DueToSourceFrameRate: 0
7/19/2014 11:29:28 PM, DueToHardDiskOrCPU: 349
7/19/2014 11:29:28 PM, DroppedSamples: 1
7/19/2014 11:29:28 PM, MissedSamples: 0
7/19/2014 11:29:28 PM, SyncedSamples: 0
7/19/2014 11:29:28 PM, AudioOffset: 0
7/19/2014 11:29:28 PM, AudioDelay: 0
7/19/2014 11:29:28 PM, AudioEngine
7/19/2014 11:29:28 PM, Running: True
7/19/2014 11:29:28 PM, SampleRate: 48000hz 16 Bit
7/19/2014 11:29:28 PM, MixingErrors: 0
7/19/2014 11:29:28 PM, Streams
7/19/2014 11:29:28 PM, Mixer
7/19/2014 11:29:28 PM, Samples: 161584
7/19/2014 11:29:28 PM, Dropped: Read 1 Write 0
7/19/2014 11:29:28 PM, Latency: 0 ms
7/19/2014 11:29:28 PM, Errors: 0
7/19/2014 11:29:28 PM, Headphones
7/19/2014 11:29:28 PM, Samples: 161579
7/19/2014 11:29:28 PM, Dropped: Read 0 Write 5
7/19/2014 11:29:28 PM, Latency: 0 ms
7/19/2014 11:29:28 PM, Errors: 0
7/19/2014 11:29:28 PM, A
7/19/2014 11:29:28 PM, Samples: 161578
7/19/2014 11:29:28 PM, Dropped: Read 0 Write 6
7/19/2014 11:29:28 PM, Latency: 0 ms
7/19/2014 11:29:28 PM, Errors: 0
7/19/2014 11:29:28 PM, DirectShow
7/19/2014 11:29:28 PM, Samples: 193
7/19/2014 11:29:28 PM, Dropped: Read 0 Write 0
7/19/2014 11:29:28 PM, Latency: 1940 ms
7/19/2014 11:29:28 PM, Errors: 0
7/19/2014 11:29:28 PM, DirectShow
7/19/2014 11:29:28 PM, Samples: 193
7/19/2014 11:29:28 PM, Dropped: Read 0 Write 0
7/19/2014 11:29:28 PM, Latency: 1940 ms
7/19/2014 11:29:28 PM, Errors: 0
7/19/2014 11:29:28 PM, DirectShow
7/19/2014 11:29:28 PM, Samples: 166
7/19/2014 11:29:28 PM, Dropped: Read 0 Write 0
7/19/2014 11:29:28 PM, Latency: 1400 ms
7/19/2014 11:29:28 PM, Errors: 0
7/19/2014 11:29:28 PM, DirectShow
7/19/2014 11:29:28 PM, Samples: 118
7/19/2014 11:29:28 PM, Dropped: Read 0 Write 0
7/19/2014 11:29:28 PM, Latency: 1120 ms
7/19/2014 11:29:28 PM, Errors: 0
7/19/2014 11:29:28 PM, FFMpeg
7/19/2014 11:29:28 PM, Samples: 5299
7/19/2014 11:29:28 PM, Dropped: Read 0 Write 0
7/19/2014 11:29:28 PM, Latency: 1020 ms
7/19/2014 11:29:28 PM, Errors: 0


Back to top

WWW

thanks 1 user thanked IceStream for this useful post.

lbgaus

on 7/21/2014(UTC)

admin

 


#19
Posted
:

Monday, July 21, 2014 4:27:58 AM(UTC)

admin

Rank: Administration

Groups: Administrators

Joined: 1/13/2010(UTC)
Posts: 4,926
Man
Location: Gold Coast, Australia

Was thanked: 3840 time(s) in 1410 post(s)

Thanks guys for the test results.
I have isolated the problem to 25Mbps and 29.97/59.94i only and I am working on a fix.

If anyone is able to create the same problem at any other bit rate or frame rate, submit the results here.

Regards,

Martin
vMix


Back to top

WWW
BLOG

admin

 


#20
Posted
:

Tuesday, July 22, 2014 8:13:59 AM(UTC)

admin

Rank: Administration

Groups: Administrators

Joined: 1/13/2010(UTC)
Posts: 4,926
Man
Location: Gold Coast, Australia

Was thanked: 3840 time(s) in 1410 post(s)

I have posted an update here that fixes this issue:

http://forums.vmix.com.a…ts&m=11018#post11018

The technical explanation is as follows:

vMix up until now has used CBR or constant-bit-rate for MPEG-2 recordings.
With the Microsoft provided encoder, what happens is if the bit rate is set to low and the
video being played back is too complex to fit into the selected bit rate, the encoder will throw its hands
up in the air and declare «i just can’t do it cap’n, i don’t have the power!»

This fix involves changing the recording to VBR or variable-bit-rate with a very high maximum bit rate.
So while the file size will still remain approximately the same size as before, in complex scenes the encoder will increase the bit rate to compensate.


Back to top

WWW
BLOG

thanks 2 users thanked admin for this useful post.

lbgaus

on 7/22/2014(UTC),

pasingshot

on 7/22/2014(UTC)

Users browsing this topic

Guest

vMix Forums
 » 
General
 » 
General Discussion
 » 
Recording has stopped unexpectedly

Forum Jump
 

You cannot post new topics in this forum.

You cannot reply to topics in this forum.

You cannot delete your posts in this forum.

You cannot edit your posts in this forum.

You cannot create polls in this forum.

You cannot vote in polls in this forum.

Some users have complained that the QuickTime recording stops randomly and unexpectedly for no apparent reason. You can use QuickTime to record movies and videos. You can also make a video recording of your Mac screen. I frequently use QuickTime. It is a very useful Mac app.

This error will prevent you from saving your QuickTime video files. As described by our users, this problem occurs after starting recording. Basically, users click the record button and a few seconds or minutes later, it just stops recording giving an error saying “Recording Stopped” (see the screenshot below). It appears that this error usually occurs somewhere between 3 to 15 minutes into an active recording session, for example, a lot of users said recording stops at 10:55.

Recording Stopped

I recommend you try these:

1. Update: Ensure that your Mac has the latest version of the macOS software. You can install the new updates (if there are updates) by going to System Preferences > Software Update.

2. Storage: I would recommend that you check to see if you have enough free storage space on your Mac. It is important to ensure that you have enough storage space on your Mac before you start your recording. If your recording is big, it can take up a lot of space.

On your Mac, go to Apple menu, choose About This Mac and click Storage. This screen will show you the amount of storage space available.

If your Mac storage is running low, I would recommend these articles:

  • How to Free Up Storage Space on your Mac
  • 7 Tricks To Free Up Hard Disk Space On Your Mac
  • “Other” Space in About This Mac and How to Remove It

3. Check your settings: Some users have said that adjusting the following settings fixed this problem for them. You may also try them:

  • Disable screen saver: Apple menu > System Preferences > Desktop & Screen Saver > Screen Saver. Deselect the “Show screen saver after” box.
  • If this is a MacBook, go to Apple menu > System Preferences > Battery , then click Battery again. And ensure that the “optimize video streaming while on battery” box is selected.
  • Then, again, go to the Battery setting (if this is a Mac notebook) by going to System Preferences > Battery > Battery. Then find the “Turn display off after” option (this is the top slider). Move the slider to the right and increase the amount of time. For example, make it one hour.
  • And when you are recording a video, especially if you are using an external camera, you can change the quality option. There are two options: High and Maximum. Ensure that High is selected. You can change this by clicking the Options pop-up menu in QuickTime.

4. Disable power nap: Some users have said that this QuickTime Stopped Recording issue was fixed when they turned off the power nap option. Please note that not all Macs have this option. Mac computers with flash memory support this feature. Here is how:

  • MacBook: Go to Apple menu > System Preferences > Battery, then click Battery or Power Adapter deselect “Enable Power Nap while on battery power.” or “Enable Power Nap while plugged into a power adapter.”
  • Mac desktop: Click Apple menu > System Preferences > Energy Saver and deselect “Enable Power Nap.”

5. Safe Mode: If the steps above do not fix your QuickTime issue, restart your Mac in Safe Mode. And test QuickTime in Safe Mode. Exit Safe Mode and test again.

See also:

  • How to Record your FaceTime Calls on your Mac
  • Your Screen is Being Observed on Mac, Fix
  • How to Secretly Record Zoom Meetings on Mac
  • How To Record Audio On Your Mac
  • How To Record Your Face and Screen On Your Mac

Dr. Serhat Kurt worked as a Senior Technology Director. He holds a doctoral degree (or doctorate) from the University of Illinois at Urbana / Champaign and a master’s degree from Purdue University. Here is his LinkedIn profile. Email Serhat Kurt.

It is very convenient to record iPhone, iPad, Mac screen with QuickTime on iMac/MacBook. But like any other applications, sometimes QuickTime screen recording is not working on Mac. You may be unable to record screen with QuickTime because of one of following these errors. Here is the troubleshooting. If none of the methods work, try to update your iPhone/iPad or Mac or record screen with a third-party recorder.

Troubleshooting QuickTime Screen Recording Problems

1. QuickTime Player quit unexpectedly

Q: During the screen recording, QuickTime stops and shows the error: QuickTime Player quit unexpectedly.

QuickTime Quit Unexpectedly

This is likely to be a storage issue. Make sure that there is sufficient storage in your Mac’s hard drive. And if you have plenty of space, try repairing the disk permissions.

  • Open Disk Utility;
  • Select your hard drive and click Repair > Repair Disk Permissions.

2. QuickTime recording stopped try recording again

Q: When pressing «Stop Screen Recording», Quicktime give you this error saying «Cannot Record. Try recording again.»

The error sometimes comes up when you are recording screen video with external audio. Therefore:

  • If you don’t need to record audio, change the sound input to the internal microphone.
  • If QuickTime won’t work with your microphone, switch to the different microphone.

3. QuickTime won’t recognizing iPhone/iPad

Q: You try to record iPhone/iPad screen with QuickTime but QT cannot recognize your iPhone/iPad. Your iPhone/iPad is connected to the Mac but does not show up in QuickTime. It only shows the FaceTime camera and you cannot choose iPhone/iPad as the camera.

Check if you are using a 30-pin to USB cable to connect iPhone/iPad to the iMac or MacBook. If you are, switch it to Apple’s lightning cable. QuickTime should recognize your device with the lightning cable.

If you are using applications like Micro Snitch on your Mac, quit the application.

Update Mac OS to the latest macOS 10.12 Sierra or macOS 10.13 High Sierra.

4. QuickTime screen recording is stuck on finishing

Q: After clicking stop recording, QuickTime is stuck at «Finishing Recording» progress bar and won’t complete.

If your Mac is totally stuck and you are unable to close QuickTime, please try:

  • Launch Terminal;
  • Type this command: top -u and press Enter;
  • Find the process ID(PID) of QuickTime Player. Note the ID;
  • Type in: sudo kill [PID]; Press Enter to quit QuickTime.

If you don’t want to lose the recorded video, you may find the screen video here:

$HOME/Library/Containers/com.apple.QuickTimePlayerX/Data/Library/Autosave Information/Unsaved QuickTime Player Document.qtpxcomposition/Screen Recording.mov

Remember: This .mov file is not a regular QT video file, but a container. To open the container, use Finder to locate the file and control-click on the file to open it.

5. QuickTime screen recording freezes

Q: QuickTime screen recording freezes suddenly. You are taking a video with QuickTime, suddenly the app just freezes.

This screen recording not working problem probably happen because of low RAM on your Mac. There is not much you can do about it. A Mac OS system update may help.

6. QuickTime movie recording: operation could not be completed

Q: When trying to start a new movie recording, QuickTime pops up an error: the operation could not be completed.

QuickTime Recording Operation Not Completed

This is actually a bug. Many users with iPhone 5s, iPad Air on iOS 10.3 and MacBook on macOS 10.12 reported such a QT recording problem. You can try:

  • Restart iPhone/iPad;
  • Make a backup and reset iPhone/iPad;
  • Update iOS devices and Mac system.

You May Like:

(2022) Screen Recorder for Mac: Record Screen Videos on MacBook/iMac (opens new window)

How to Record QuickTime Videos without Lags in Small Size (opens new window)


Get Mac/iOS Update & Reinstall QuickTime

In many occasions, QuickTime screen recording stops working because of a system bugs. Therefore, getting system updates is believed to be cure-all.

  • Update your MacBook, iMac to latest macOS.
  • If you are trying to record iPhone/iPad screen via QuickTime, update iPhone/iPad to iOS 11.
  • Reinstall QuickTime to keep the application up-to-date.

Get A Third-Party QuickTime Alternative

If your software is already up-to-date and there is no other solution to get QuickTime recording working again, you should record screen video with a third-party recorder: FonePaw ScreenMo (opens new window). The recorder can record iPhone, iPad, iPod Touch, Mac screen with audio. And it supports screen recording for multiple devices simultaneously. By using Airplay, you can record iOS screen video wirelessly.

Step 1 Download iOS Screen Recorder on your PC.

Free Download Buy with 20% off

Step 2 Put your iPhone/iPad/Mac and PC in the same Wi-Fi network.

Step 3 Follow the instruction on the program and airplay iPhone/iPad/Mac to PC.

iOS Homepage Enable Airplay

Step 4 Your iPhone/iPad/Mac will be mirrored on PC. Click record button to start recording. If you need audio, click microphone icon to record screen video with audio.

iOS Record Screen

Step 5 To stop recording, click record button again. A window pops up and you can choose Start Export to save the screen video.

iOS Export Video

Note: If you tend to record Mac screen with audio, the method above is good for you or you can try FonePaw Screen Recorder (opens new window) to capture Mac screen directly.

If you have other question about recording iPhone/iPad/Mac screen with QuickTime, leave your comment below.

Пользователи сталкиваются с множеством проблем, связанных с устройством записи экрана в Android 11. Хотя некоторые не могут записывать звук вместе с видео, другие сталкиваются с проблемами качества с устройством записи экрана. Точно так же для многих пользователей функция записи экрана останавливается на полпути.

Давайте проверим различные решения, чтобы исправить проблему, когда диктофон экрана не работает в Android 11.

1. Перезагрузите телефон.

Если до сих пор вы могли правильно записывать экран, а он внезапно останавливался, проблема могла быть временной. Просто перезагрузите телефон, и вы сможете записывать изображение с экрана.

2. Следуйте правильным инструкциям по использованию средства записи экрана.

Вы можете получить доступ к функции записи экрана Android 11 только в быстрых настройках. Если средство записи экрана не отображается, попробуйте различные способы исправить средство записи экрана, отсутствующее в Android 11.

Когда у вас есть экранный рекордер в быстрых настройках (проведите вниз по панели уведомлений, чтобы получить доступ к быстрым настройкам), нажмите на опцию Screen Record, чтобы начать запись. Появится экран с настройками записи экрана. Включите переключатель рядом с «Записывать звук» или «Показывать касания на экране», если вы хотите их использовать.

Нажмите на маленькую стрелку вниз рядом с надписью «Запись звука», чтобы выбрать источник звука для записи. Вы можете выбрать звук устройства, микрофон или и звук устройства, и микрофон. Наконец, нажмите Пуск.

3. Отключите принудительный режим рабочего стола.

Вы можете столкнуться с проблемами звука и видео при записи экрана, если в параметрах разработчика включен флаг «Принудительный режим рабочего стола». Значит, вам нужно отключить его.

Для этого откройте «Настройки» на телефоне и выберите «Система»> «Параметры разработчика». Вы также можете выполнить поиск параметров разработчика, используя поиск в настройках. Если вы не найдете параметры разработчика, проверьте другие решения. В разделе «Параметры разработчика» найдите «Принудительный режим рабочего стола». Отключите переключатель рядом с ним. Перезагрузите телефон, и вы сможете без проблем записывать.

Кончик: Ознакомьтесь с пятью скрытыми функциями параметров разработчика в телефонах и планшетах Android.

4. Включите Notch

Если ваше записанное видео выглядит как пиксельное или сжатое, это может быть из-за выемки. Вы отключили выемку на своем телефоне? Что ж, пора снова включить.

Чтобы включить выемку, перейдите в «Настройки»> «Система»> «Параметры разработчика». Прокрутите вниз и найдите Вырез для отображения или Имитация отображения без выреза в разделе «Чертеж». Нажмите на него. В списке выберите «Устройство по умолчанию» вместо «Скрыть». Перезагрузите телефон.

5. Снимите наушники или наушники.

Если вы пытаетесь записать внутренний звук на свой телефон, вам следует отключить все подключенные наушники или другие аксессуары, такие как наушники или динамики Bluetooth. После удаления аксессуаров выберите «Внутренний звук» в настройках звука средства записи экрана и попробуйте записать.

6. Удалите сторонние приложения.

Сохранение других сторонних приложений для записи экрана также может помешать нормальному функционированию встроенной функции. Вам следует удалить их и посмотреть, сможете ли вы записывать с помощью устройства записи экрана Android 11.

Кончик: Вы также можете перевести свое устройство в безопасный режим, чтобы исключить проблемы, вызванные сторонними приложениями.

Поскольку запись экрана — это новая функция Android 11, на данный момент очень немногие приложения поддерживают ее. Таким образом, вы можете столкнуться с проблемами при использовании его в определенных приложениях. Несмотря на то, что Google не упоминает об этом специально, вы не сможете записывать звук с помощью таких приложений, как Spotify, SoundCloud и т. Д., Также из-за ограничений DRM.

Совет профессионала: Если вы не можете записать звук при использовании параметра «Звук устройства» в настройке «Запись звука», воспроизведите звук через динамик телефона на высокой громкости и оставьте для параметра «Запись звука» значение «Микрофон». Это должно делать свое дело. Конечно, качество звука будет не таким уж большим.

Бонус: запись телефонных звонков с помощью средства записи экрана

Вы знали, что можете использовать программу записи с экрана для записи телефонных звонков? Просто выберите «Микрофон» в параметре «Запись звука» и включите громкую связь. Вуаля!

Отказ от ответственности: Ознакомьтесь с законами и правилами вашей страны, касающимися записи разговоров, поскольку такая деятельность считается незаконной в некоторых регионах и штатах.

Записывайте действия на экране

Мы надеемся, что одно из вышеперечисленных решений помогло вам решить проблемы, связанные с неработающим устройством записи экрана на Android 11. В качестве меры предосторожности мы предлагаем очистить кеш для сервисов Google Play и сбросить настройки приложения.

Следующий:

Хотите записывать видеозвонки из WhatsApp и Facebook? Посмотрите два способа сделать это по следующей ссылке.

Post Views: 2 942

Понравилась статья? Поделить с друзьями:
  • Error scalar object a requires one element in initializer
  • Error saving the task 80070534
  • Error saving settings file jbridge
  • Error saving file aseprite
  • Error saving changes make sure toggle hd mode is run as administrator