One more thing to add,  now that my export project with project manager is complete,  all the clips I had on the timeline were exported to a new project file that kept them on the timeline, along with the original in out points I set, but it also had the extra 300 frames before and after the clip I could expand the clip to if needed.  The clip that was saved as its own file on the HDD still had the extra 300 frame handles, but at least the new project file kept the original in out points.  Maybe this methode also will work in some cases for you.    I guess at some point if your time, once your timeline is perfect, you can use the export project manager feature and not add any extra frames for the handles, and this would the only way I can think of to tweak the in out points if the needs to have adjusted points and you want to export as a seperate clip file afterwards. ... View more

Yes, I would check every cut also.  I will say that Adobe's aprouach to detection is different that Resolve (which uses histogram modeling and detects the amount of changes different).  Resolve requires you to pick tolerences etc if I recall correct.  With Adobe version there is no adjustments to make, I have tested it on over 8 hours (in 2hour blocks) of old footage from a Hi8 analog tape.  It was near flawless,  It was very surpirsing how well it worked.   It is however a very good idea to check each automatic cut point, as comming of 16mm film might make not work as well.  I will say, that when you drop the clip the AI created on your timeline, you can move the in/out points, but it doesnt update the in out in the bin, which is what is needed to happen if you want to export the clips with different in out points than the AI detects.   Not sure how to create new in out points when using the export methode I detailed in my first post.  I tried it in the source window, in the timeline, and even dragging it back into the bin from the time line after I adjusted the in out points, it always keeps the original timecode in out points...   The only way I found that seems to (somewhat) work, is to use project manager, (screen shot below) and change the handles before and after each clip to something bigger than you need, so you can trim it in your final project.  In this case I tried with 300 extra frames before/after each sub-clip.  It works, but it will mean you have to edit each clip for new inout points when you drop them into your final timeline, but at least the handles give you extra footage to trim if needed.   Hopefully, the AI detected points work good enough for your project....  that will save you tons of time if it does.   ... View more

I think I might understand what your trying to do...  so I will take a swing at answering it, hopefully. If your clip from Kodak is all one big file and the audio is already part of the video....   Run Scene Edit Detection, and select the option to put the clips in its own Bin like this dialog shows:   Once this process is completed, there will be a BIN in the media area.  you can select all of the clips it put into that Bin,  the icon for these new clips looks like this: With all the clips selected, you can then press CTRL-M which will bring up the export dialog.  you can make your typical export setting, and then export it using Media Encoder.  This will create a file for every clip as a stand alone video file, it will include the sound etc.   Not sure if this was exactly what you were looking for, hope it helps. ... View more

curt0D45 Your inquire should be posted as a new topic so people can find it.  Its been lost within this thread and thus no one has been respoding.  With that said, when you start the new thread, please include more details about your hardware, what the source footage is, size, bit rate etc.  The laptop model and specs would be very important in helping you alogn with what version of Premier your using, if your running internal HDD, or USB etc.    With all this said, please open it as a new thread, as I am pretty sure your issue is not the same as what the OP started this thead for. ... View more

Ebalma if your short space, go ahead and use HVEC/H265.  The hardware resources on your system are not going to hurt much (especialy if its 1080p).  What you will notice is that hitting pause, or moving the playhead to a new location will take a little extra before it done drawing the video frame.  But if your short space and comfortable with  HVEC, then its okay to use.  Everythign is a trade off, if you know what you get in return for what you trade, then by all means proceed.   I am really impaintent, so that 1/2 second delay when I scrub the timeline really bothers me...  I work with drone footage which is really hard on the system (and often in h264/265), so I use proxies for everything I can.  Its a big help as the timeline is VERY snappy.      I look forward to your confirmation this work around also worked for you.   There is nothign wrong with working around the constraints one has, make the best from what you have. ... View more

mgrenadier; I can tell you know your stuff, anyone that prefers all iframe format knows more than enough to know its ideal.  It will use more space (not a big deal these days).    As a foundation statement for others reading this, when your using all Iframe it has all the info it needs to display the full video frame (It is a the full and complete picture nothing missing) contained within that one frame.  The format the OP is using requires that the decoder reads all the frames from the prev iframe up to the frame it needs to displayed (its like puzzel peices the software needs to arrange so they all fit together and the more distance between iframes the harder the computer works to arrange more of those peices).      My thinking for the OP is that a reencode would be enough for them to work on thier project and avoid the redraw issues.   If they are comforable, they could encode in any new format, like prores and it will also solve the issues.  I was trying to avoid complications in explaining the different codecs one could use.   For this footage, it seems like any format will allow them to work around the issue.    With that all said, for a really solid editing experaince that is snappy, and often avoid many issues in these high compression formats,  ProRes seems to be ideal, very happy it was added to Premier for Windows.   Also, Welcome to the World of Windows!  I came off a Mac about 4 years ago, but when they made that new version of Final Cut X (glorified imovie), I had to leave, I hated that version, windows was very atractive back then for the performance you could get. ... View more

Ebalma,  I dont know what 'best' for you, you will have to try something that works for you.  I posted another response with my thoughts as to why this "might" be happening, so I will not rewrite it here (I'm sure if you have an interest, you will read through it).   I think the logical step for you is to update the firmware of the device you used to record this and check it change log to see if anything is noted about .mov files enhancements.  I would say, that typicaly, PC users will use the .mp4 container when editing on a PC.  So if using .mp4 as the recording container for your camera's works, I would stick to that format if it is possible, and doesnt cause you any workflow issues.   h265 is harder to work with than h264 formats, takes considerable more resources to decode than a h264 stream, but your machine should have no issues to handle it (scubbing performance might me a little slow but tolerable).     I would also suggest that you look into a proxy workflow;  there is some good youtube videos out there for this...  but ONLY look at the recent ones, in the last 6 months maybe (proxy workslow has been recently revised and is way easier than the old way).  This will give you very snappy timeline performance and in general a smooth editing experinece.   I wonder if footage created by that camera that has not been recorded in the slow motion format exhibits the same symptoms?  If you have standard footage from it, I would be open to check that.      In the mean time,  I would test a conversation to avoid this .mov container.  Prores is an ideal format to use, but I will venture a guess and say that encoding it to h264 @ 100mps (or what ever your camera gears original but rate was) is going to be fine.  The goal would be to rewrap the file so it gets the video structure it needs for premier to not have issues.  We can call this a work around...  I think your issue is a edge case, and its not likly to be seen by many.   But do try the firmware update for that camera that created that.  All of this to tell you, I dont think there is anythign wrong with your PC or premier install.  Once you recode those files to MP4, and if you find no issues, you will know one way or the other.  It might be worth putting in a bug report for Adobe with that video file as a sample, as I do think that your source file triggers the issue, but I dont know if its the cause or just exposes a bug within premier.   Id like to hear back from you after you try the re encoding.  If you have a project built aroudn this files, I thiink you can even swap the media into your original footage so you dont have to apply all your edits to it.  I have not done this myself, but I think I saw somewhere there was a media swap procedure if you need it. ... View more

mgrenadier I am interested to see what you find.  To me this looks like a subtle differnce in how the .mov container is handled.  Your findings would be of significant interest to me on this matter.  If I had to bet, I think its Adobe rewrite of timeline HW acceleration at the root.  For me the issue only presented when scrubbing very quick.  It feels like the routine to read the frames on the timeline is designed for performance, and will not read back far enough to rebuilt the frame the head rests on when you stop.  In theory if you look that frame structure of his source, we may find that when he recorded in slow motion [(it looks like 25FPS footage to me) as he indicated that you need to apply a 400% speed up to get it to play real time], that the frame structure may not have full frames close enough to each other to rebuild the entire frame that premier is expecting.   My gut says that is an edge case because it was recorded as a slow motion clip and the container may not have been build to the exact standards adobe is looking for and thus they dont search frames far enough back from the playhead when drawing the requested frame to get a full proper frame.  I suspect this is the case as a frame by frame inspection shows they are all intact, further, the slow motion likly is not putting enough full frames into the stream as it might be taking a encoding shortcut in order to maintain the recorded frame rate.  My suspecion is that on its own, the source footage would be fine as we see with media player and VLC, but adobe frame look back for a redraw is just not far enough back (every frame they look back will slow down performance of that 'snappy' time line we expect.  If its not adobe code, then its the nvidia SDK they use for the nvenc encoder itself.  Overall, a minor issue that is not likly to be commonly found by users, and thus has been undetected in testing.   But all that said, I am very interested to learn what you discover, as it sounds like your have used AVCHD way more than me.  Pleae keep in mind that your Mac would not be using the nvenc/nvidia software for timeline redrawing (like the OP and my system does) and is likly to have a different frame look back and thus no redraw issues.  I suspect the foundatinal software code to be different between the PC and MAC versions for this sub-routine.  I noted that you said your 'ancient' mac had no issues.  My system didnt have any issues with this footage either for resources as it didnt even use 2% of the video card, and didnt break 3% of the CPU when playing it.  The file is actualy not hard to redraw frames, and that 2012 macs performance doesnt suprise me for this footage. ... View more

Okay, I downloaded you file and found somethign very interesting..... The file is perfect by the way, not a single frame is damaged. Premier and media player will play it perfect at the native frame rate, also plays fine at 200%, 300% and 400% when using frame sampling (The default).  I had to do no rendering, despite the timeline being red and in same cases yellow is played fine;   If I changed the blend mode to Optical Flow;  it starts to look like the sample you provided.  I will attempt to attach the screen shot.  Once I changed it to Optical flow;  the playback issues started to show up.  I could change it to frame blend or frame sample, and the issues were still present.  If I scrubbed the timeline the issue would appear on different parts of the video, not always the same   I decided to render preview the timeline, and then when scrubbing all those artifcats were no longer present.  It didnt matter how hard I tried, scrubbing didnt reveal the artificats pictures below.      I will also say, that its 100% repeatable,  I can very seldom scub without issue.  Playback was always fine for me after I rendered the preview files without fail.   This is the timeline after I enabled optical flow, and started to scub it agressive.  The quicker the movement of the playhead, the easier it was to get this result.   I then decided to use Media encoder to drag the file you provided into it, and used the YouTube Present and converted it to a MP4 container.  The file performs flawless on all scubbing and I could not duplicate the issue at all that I captured above.  The MP4 container takes a marginal split second that you can notice to render the frame the frame you stop at when scrubbing.  But in 100% of the testing, there was never any artificating.   I am can say that 100% of every single frame of video you provided is fine.  There is somethign wrogn with the encoding or decoding of the .MOV container you were using.  I lean towards the decoder in premier for the timeline itself, as media encoder had no issue using the NVENC encoder to convert it to a MP4 file, and it scubbs and plays back perfect at 100%, 200%, 300% and 400% with agressive time line scrubbing.   Does this help you?     ... View more

EBalma;  Have you tried to convert your videos to H264 using media encoder (or handbrake) before importing them and see what happens?  If you provide a dropbox to download a sample of your footage, I would be prepared to check if I see the same artificating you do on my system for you if that would be helpfull.   ... View more

mgrenadier; You are manging your workflow very well.  7200 RPM drives are typicaly fine for even a few 4k streams (depending on the bit rate and quality of the HDD).  What I find is people forget that they need to defrag them to keep the file system good shape for video.   The use of Proxys is reducing the demand on those drives signficiantly.  I would say one needs more knowledge to use a HDD then they would an SSD/NVME, especialy as the projects get more complex.  Your workflow shows that its possible, but some people dont spend the time to refine the workflow for thier system in the same way as you have.   SSD/NVME allow users to basicaly not worry about managing the workflow (until 8k is involved).  It also depends on the source that creates the content,  some equipment makes very taxing h264/h265 files despite on paper they should not be an issue (like Chroma Subsampling: 4:4:4 vs 4:2:2 vs 4:2:0 where 4:4:4 is easier to decode than the lower quaility ones because of better support in hardware/codec).   This users issue is interesting as there really is no reason why it should occur.  I provided some ideas in a long post a few min ago that I hope will help the OP.  Based on what was posted so far, that HDD he has should be fine playing back the files with the project complexity indicated so far, at the same time the use of a HDD SATA drive is not somethign I would use or recomend for preview drive either - I really think that HDD fragmentional can dramaticaly effect playback performance/dropped frames.    I eagerly await thier feedback,  what really intrigues me is that In every way I can think of this problem, the expected outcome would be dropped frames, not block/artificat issues like  they present with.  I will admit that the recency of NVENC decoding for the timeline gives me a hard time to wrap my thoughts around why they see artificating vs dropped frames.  This could mean a much more complex issue is occuring, even in my most demanding timelines, I see dropped frames (until rendered), never seen those artificacts before. ... View more

I use 460.89 (Dec 15, 2020) nvidia driver, and have no issues.  Provided as a data point for you. ... View more

I have a few tips for you to try, I read the whoel thread, but there is a ton of details in it, if I am repeating something apologies in advance;   First, do not use this drive for previews: Seagate 2TB SATA 7200RPM HDD (for project files, Auto Saves and Preview Renders)   Previews, generates lots of drive fragmentation, which is the enemy of video files. Basicaly, I would ONLY use this drive for exported projects.   The other thing you want to do, is run the trim command on all your SSD/NVME drives.  When you do this, also run the defragment command on the SATA drive I noted above.  If you are not sure what Trim/Defrag are its best to google it, but run these commands.   Second, depending on what version of windows / build number, you may have the version with the issues with the trim command, that wasnt working proper.  If you can, upgrade to the latest Windows Builds, also, look for option drivers while you update, windows 10 update doesnt make it very clear when it offers options updates, but look for them on the update page.   Also, if you have not downloaded the samsung magition software, down it, and check to ensure firmware is up to date on those drives.  They also offer a NVME enhanced driver (I use it) and it will help.   Turn off the MSI game mode boost.  Often, game mode boost stuff disables certain things that can allows errors to show up in the math it does.  Your driver / Bios setup should be focused on quality, not speed.     I dont know if you have screen recording software installed, but sometimes, driver packages etc can offer OBS install ot specific tunning, please ensure thats all off/unistalled (unless you use it, in which case try it as trouble shooting).   Do your mother board bios updates, if you have any.  Thats a very new Chip, and they may have updates that you need.  I have nto run AMD before, but for intel, there is often a 'chipset' driver package for the operating systems that match the Bios update path.  AMD might have a simular path.   What your seeing on that screen appears to be envenc decode issues.  I suspected that your root issue has to do with the overclock of video card at first, but it appears to me that your issue progressed from none, to increase in occurances.  This leads me to belive that 7200RPM drive fragmentation and possible TRIM and firmware for the SSD/NVME might be playing a role.   I had a issue with the NVME driver causing me all sorts of issues in the late fall,  I had to install the driver again as a windows update appeared to damage the driver, but device manager was reporting it was current.  You might have the same issues, so best to install the NVME driver again (full install/overwrite).   Here is a half decent link for the driver details, but download it from samsung direct, I never trust these 3rd party sites for links to drivers: Samsung NVMe SSD Driver Download v3.3 (guru3d.com)   And please, stop using that 7200RPM SATA drive for preview files,  between the speed of the drive and the fragmention issues with that type of drive, it will cause you greif at some point. (run the defrag also as noted earlier).   And last thing,  if you have antivirus software installed, remove it for at least testing.  I have used windows defender and have had no issues, but if your running other scanners, they tend to be very agressive, and when you create/read/move a file (such as block of preview video) the anti virus wants to read the block first, and this gets in the way of playing it back.    Hopefully one of these steps gets you further along, if you have not tried them already.  I am interested in your feedback on this topic.   as a side note,   I run the multiple 970, 960 drives, an RTX 3090, with the current studio driver and current premier CC, with no play back issues.  The GPU is NEVER busy enough in playback to give me any reason to think that a 3070 would have issues (I do note you tried multiple other video cards).     As a side note, I am not a big fan of the ADATA brand,  I would suggest if you can (not already) for your testing, try putting your source footage on a the samsung for testing.  If you open task Manager, you will see that the disk actrivity for all those drives, and those NVME's are not very busy at all, so for testing using the samsung for source is fine.  The reason why dont have an good opnion of ADATA is mostly because I dont trust thier specs.  I dont know which version you have, but its possible they are using QLC (slower) memory, and often they dont include cache on the drive, or too little cache, and this creates challanges for writting data mostly, but can for reading data also.  However, ven the worst NVME drive should be okay for 4k video, but if not already, try to exclude the ADATA and the SATA for testing purposes.   Apologies for the long response, hopefully somethign that can help you will be found within it.   ... View more

I should also add, please find a way to speed up saving process. It appears Warp Stabilize saves the data inside the project file, and when you have any notable amount of clips with stabilize effects, the saving process is dramaticaly slow.  It would be nice if the stabilize data was stored seperate from the project file, and that way any save requests would be fast.   Something that maybe would be worth while doing short term, is at least with auto-save, to avoid resavings the stabilze data.  I have projects that can take over 5 min to save because of the stabilization data in an autosave.  My system is not slow, everything is on seperate NVME drives, 128GB and an RTX 3090 video card...  the warp stabilize contributes significantly to the save time of projects files and slows down the edits.  I have resorted to stabilization, then export each clip, and then import them back into the project to avoid this limitation. ... View more

Okay this is exciting news.... Can I add one suggestion for the team,  can you add a way to "exclude" parts of the frame from how itcalculates the stabilze?  Not sure how big of deal it would be to most people, but I sometimes find that it helps to have a way to ignor parts of the video frame.  Right now if Warp Stabilize fails to work well enough, I switch over to Mocha (so I can exclude stuff), but I prefer the simplicty and more automatic modes of Warp Stabilize.    As a second suggestion,  can you make it so that if you are doing multiple clips at the same time, that it works better when you have 10 clips or more being processed.  I like to have it process the footage, then tweak the settings for each clip.   Would be nice to also add ability after a past effect command to automaticaly start the process too :-), not trying to be greedy, but I had to ask. ... View more

So glad that you now know the exact cause of your issues. Try downloading software called handbrake, it’s free, and take the videos you downloaded from the internet use that to convert them to a MP4 file of some sort. Handbrake might be able to fix the issue in the file. I will point out, if those downloaded files are DRM (digital rights managed) I’m not going to help break that protection. I don’t know the nature of the files so I’m uncomfortable providing any advice that serves to bypass the protection. As far as I know handbrake will not break DRM, but it can sometimes fix internal file structure errors that might be causing your issues. If the files are not fixable with handbrake and they are not DRM files, FFMPEG I believe has a way to fix file structures also, but it’s command line and a touch complex to use (windows only as far as I know also). Report back what happens with handbrake, But please understand advice to get around DRM is not going something I will provide. Good luck in the next step. ... View more

That is very interesting.  Nothing stands out as a contributing factor.  If I can a few other questions. 1) What is your sequence settings? 2) Is all the footage from the same camera / same settings, like 4k, h264/h265 etc? or mixed footage? 3) when you put your footage on the timeline, did you set your sequence manualy or did you get the popup saying the settings didnt match, and asked to keep settings or change them (and what did you do?). 4) have you tried to change (and can you confirm) the settings your using on export, such as hardware encoding, software encoding and what the export format you choose is.  Also are you exporting to Media encoder? or just with Premier encoder?   As a side note, if your exporting to Media encoder, teh defaulty setting is to do nothing, until you press the play button on the top right of the screen, then it starts the jobs the in the que...   This is somethign thats easy to miss a a new user of media encoder. ... View more

Sorry for the extra post,  I failed to mention that the CPU usage is also very different; Denoise in Clip is < 65% Denoise in Adjustment/Nest < 45% GPU Usage was the same at approx < 6% for each of the variants.   The system used was a Intel 10980XE/128gb and RTX 3090 as a referance.   So, for sure, applied in clip direct is much faster / better way. ... View more

This spark my interest to see what would happen today;  I created 3 two min projects, 1x Denoise in clip, 1x Denoise in Adjust and 1x Denoise in Nest.   The export estimates in media encoder came back: Denoise in Clip < 30min Denoise in adjustment < 2hours Denoise in nest < 2 hours (pretty exactly the same as in adjustment).   Watching them for a few min each, I think they were accurate (directionaly).  It seems to be different than what I first experisced a few years / versions back.  It it very slow to process when in adjustment layer and nested.  I opened a old project, and did in fact find I was applying it to clips when I needed the Denoise.    I post this, only to correct myself, that Denoise in a nest might work, but its very slow....  best way is as you indicated to apply it to the clip.  Thanks for giving somethign interestign to work on for a few min and learn something too.  Hopefully it helps the OP (or someone else in the future). ... View more

Makes sense today,   back then I was just leaving Final Cut Pro and first time back to premier in many years, so many new things to learn at the time.  The BorisFX support team were fantastic, after a short (inaudible) chuckle, they got me up to speed.   The O.P. might have some effect applied that has an exepected behavior, the story was more an examle of how something like use of the adjust layer could trigger his condition with the use of certain effects.   ... View more

I have had something like this before, and I was using adjustment layers and certain effects didnt work on adjustment layers.  The solution was to use nesting.    Your inquire doesnt have any indication of the structure of your project, so this may not apply.  If you can give us a summary of the type of project file it is (codec, nested, adjustment layers, heavy effects use, 3rd party stuff installed and/or used as examples), it may assist someone in knowing how to respond with a more approiate answer for you.        My 3rd party tool was BorisFX, I thought I was being cleaver by used noise reduction in the adjustment layer vs apply to hundreds of clips...  the feeling of cleaver was gone the next morning when it was stuck at basicaly 0% complete like you mention. ... View more

Frankly, thats a rude response to anyone trying to help you. Not sure why I should go to the trouble of installing an old version to prove to you its the same for me - I have no motiviation or gain to make such a claim.  Two people dont make a pattern.  But thousands not here to complain about this specific issue probably means its not the software in general as you belive.     If people telling you they have no issues, and suggest that a clean install of the video drivers is viable investigative path and your not willing to try it, I suggest you open an offcial support ticket with Adobe.  I didnt come here tonight to be abused in anyway, I demonstrated respect to you - I have not done anything to you to warrant being the attention of your frustraton.   For the record, I never said your problem was not real, never questioned what you posted, even read (and watch watched the two videos) what you and others posted before responding to you.  I belive you are seeing a problem, I dont agree that everyone with version 14.6 has the issue.   I think I solved your problem,  your not going to dealing with this "you people", so you can rest now, no more frustration ahead for you.  I truly hope you find your answer so you can start to focus on your creativity again. ... View more

Not sure what to tell you,  swithing the decoder and encoder for sure makes a differance to to the utlization of each resource without fail.   I'm leaning towards something else is goign on with your setup.  Can you confirm your using the latest studio driver 457.30 for the nvidia card?   I know its a major dissruption, but you may have to trash the preferances and clear out the cache or maybe even do a clean install of premier/media encoder.   What your describing should not be possible, there will for 100% sure be a variance when switching encode/decode.  The 5.5 hours you described reminds of pre GPU enabled encoders and the CPU was doing all the work.  I think it would be worth it to do a clean install of at least Premier and your video card drivers (The check box in the studio driver installer should do the trick, but the gamers use some 3rd party tool to truly delete all the video card files that might be better in your case).   At this point, not sure how else to help you, I will however say its not a wide spread issue with premier code as the worst I ever get is 1:1 for render times....  you have something specific to your enviroment happening, that clean install may help you.   ... View more

I dont have a quicksync enabled CPU (I have a 10980xe), so may have other combiantions that makes sense, like using quicksync for decode may fair better than CPU.  To the best of my memory, I think the older versions used quicksync to decode video even when the GPU encode was added.  Since I didnt have quicksync I never paid much attention to that note I read, but it may be helpfull to you.  You already likly know this, but quicksync encode doesnt look very good comapred to nvenc or CPU, so probaby not worth trying quicsync for encode.   As a side note, update the video drivers, not sure what driver versions your using but the early studio drivers for nvidia gave me trouble, the latest versions are better.   Good luck in the quest,  I will say the stats from your original post for render times are a bit alarming, I have not seen anything that dramatic.  Hopefully a driver package update (if available) and trying the different encode/decode settings helps you narrow in on the issue. ... View more

There is also one major thing not being discussed here.  I use Media encoder for pretty much every export.  The latest versions use the GPU for both decode and encode.  In the preferances in media encoder you can now tweak it to use CPU for Decode and only GPU for encode, or other combinations like CPU for encode, and GPU for Decode.   I have done some extensive testing as part of my work of switching over to the RTX 3090 and I can say that in some cases, turning on CPU for Decode and GPU for encode works signficantly faster than GPU for both encode/decode work.  I have not spent enough time to figure out in what cases this can be repeated.  But the this change, might be why you are seeign differances,  the older versiosn you referance, only used GPU to encode and always used CPU to encode.   I suggest, if you have nto already, to try this setting in media encoder preferances and see if explains some of your concerns. ... View more

Have you tried clearing out the cache files,  that seemed to work for other people.  Also, you identify two seemigly different outcomes..  A Crash, and your computer turnign off are two things to most people  If the application crashes or window crashes it can restart the computer with a seriose error, but if your system turns off and stays off when running scence detection for s while its more likly its over heating.   I have noticed this process takes significant GPU and Memory,  my CPU workload was light but that might be because I have 18 cores, less cores might be working harder.  Either way,  check your thermals, clear out the cache and see what happens.  also, make sure you are in fact at 14.4 and not runnign the beta for some reason.   if all that fails, maybe others will have some ideas. ... View more