@Vasyl-Voloshyn

Hi.

I forgot to ask. Are you running Windows 8.1?

Ray.

Hi

I'm using Windows 10 and NVIDIA GeForce GTX 1050

The file is captured by the Camera Application from my Google Pixel 4a

@Vasyl-Voloshyn

Hi.

If your keyboard doesn't have a print screen key you can use the Fn + Windows key + the spacebar to capture a screenshot and use snip and sketch or paint to save as a jpg to upload here.

You are several build versions behind with Windows 10. you should be on build 19044.1706.

Check you have the nvidia driver version 30.0.15.1277

4GBs of ram is really not enough to run Windows 10 and the program. Just typing away to you here with no other applications open and just the one tab open on Firefox I am using 3.9GBs of motherboard ram. Just opening Movie Studio without loading a project pushes that to 6GBs. I'm not sure the last point will make a difference to what you see happening in the program but the program would be quite sluggish to respond as it makes swap files go to the C: disk during use as it runs out of motherboard ram.

Try updating Windows and the nvidia driver.

If that doesn't make a difference please upload a problematic video clip either Dropbox or Google drive for us to test out to see if it is a file problem. It has to be a file sharing application and not somewhere else where the file will get converted for use.

Once one or two members let you know they have the file to test, please either delete the link on your post using the edit button of remove the content from your Dropbox / Google account. Once we have done testing we will delete the file from our systems as it is not ours.

One last option would be to use Handbrake to convert the file to something your system may be able to cope with more easily such as MP4.

Ray.

@CubeAce @Vasyl-Voloshyn

Ray,

One last option would be to use Handbrake to convert the file to something your system may be able to cope with more easily such as MP4.

You mean "convert to H264".

4GBs of ram is really not enough to run Windows 10 and the program. 

Interestingly, for years I was running on 4gb of RAM, even though I had 12gb installed. Due to some glitch, 8gb was "hardware-reserved" ie not useable. After I sorted that out, I haven't really noticed a massive performance improvement. I'm not editing HEVC files though.

@Vasyl-Voloshyn

Hi.

Sorry, I misread your last post. You meant the video comes from your camera.

I can't find out much about the file format the phone records to and H265 is very customisable by individual companies so there could be anything non standard within the codec. It does state that it shoots at NTSC standard frame rates though but it is also doing a slightly weird pixel shift thing and combining images to give a pseudo HDR effect. That could be achieved (In theory) by combining BT601 and BT701 colour spaces but is not really HDR as it is still within the normal colour space for 8 bit recordings.

At this point the file is probably not being read correctly as the program cannot use two colour spaces at once.

Really I think it time to provide a quick sample for us to test.

Thank you.

Ray.

@Vasyl-Voloshyn

Hi

. . . . NVIDIA GeForce GTX 1050 . . . .

Are the drivers up to date - the latest version is 512.95 (30.0.15.1295) ?

If the drivers are up to date or updating does not fix the issue, in the Program settings, Display options tab set the Video mode lower option to Microsoft Basic Render Driver.

John EB
Forum Moderator

@CubeAce

Hi Ray

The Pixel 4 has three colour profiles features two of which are enhancements.

Color primaries                          : BT.601 PAL
Transfer characteristics                 : BT.709

I think the video has been shot using one of these 'enhancements' which is basically shooting BT 601 - the old analog TV Broadcast colour standard - and specifying it to be displayed as BT 701 to stretch the colour space.

John EB

@AAProds

Hi Al.

Hardware reserved ram is a Windows thing normally reserving ram for graphics or audio buffer use. At a time when video and still image applications required more as a percentage of system ram reserved to run, more reserved System ram was in use, just not accessible to anything other than what the operating system decided. Windows 7 was quite hog for reserving ram. Windows 10 on the other hand is only system reserving 157MB of motherboard ram on my current system. As more graphics cards got larger and faster vram, programmers began to switch from using motherboard ram to the vram on graphics cards for processing.

Note how some plugins and main programs now specify a minimum amount of vram as well as motherboard ram.

I myself have recently come up against not having enough vram in my system for some of the things I have tried to do that has caused the program to trip out rather than crash. It has just stopped exporting, disabling the Intel graphics chip as the vram needed within the project has exceeded the amount I have on my nvidia 1650 Super. The program has not crashed, nor has it produced a BAK file, nor refused to load the project in working order again. It has simply stopped the export as the Intel GPU has been cut of from the reserved ram.

How much reserved ram Windows now decides may well be down to how much ram I have. It used to be possible to change that in the bios but I don't know now if it is possible or make a difference. I don't know but if anyone has more than 32GB of ram and can tell me how much reserved system ram their system has reserved by Windows maybe we will find out. The other may be down to the Intel HD 630 GPU chip I have, as more modern integrated GPU chips have dedicated vram as well, and more of it.

Ray.

@johnebaker

Hi John.

That's how I see it.

An odd way to go about it in my opinion but that is phone companies for you. Always trying to bamboozle the customer into thinking they are getting more than is actually there.

Time for a video clip sample me thinks.

Ray.

Hi All. I've just updated windows and NVidea drivers to the latest version. It looks like after that Movie Studio starts working more stable. But I still get frozen and even crash the app. I've tried to create a simple solution with 1 file added to it a few times, and move it randomly on the timeline for a few minutes. After that Movie Studio has been frozen. Here is that simple file I've shot for this test today. Please have a look.

Thanks,

Vasyl.

https://drive.google.com/file/d/1WkZs6zwFHbEmoHfGaQtYdcq0TRldc0eq/view?usp=sharing

@Vasyl-Voloshyn

I downloaded your file, opened it in Movie Edit Pro Premium (so the same program and version as you are running), it played without any problem. I dragged the file around to various points on the timeline, still no playback problem! Same Windows version as you (the rest of my computer spec is in my signature).

Jeff

Hi @johnebaker

I've renamed the post with the correct name of the Studio version.

Here are the settings I was using.

I've played with the file you converted for 5 or 10 mins and it looks like Movie Studio works correctly with it. It wasn't frozen during that period.

Could you please advise settings for Handbrake to convert files to get the same result as yours?

thx in advise

@johnebaker @Vasyl-Voloshyn @emmrecs @johnebaker

Hi.

I too am not having any problem with playback of the file and can also add several effects without suffering any playback stuttering let alone freezing. Even opening the monitor view to full screen.

I think your first image is OK for settings but the second image, personally I would have 'automatically create frame table during export' ticked And your setting should reflect the file which is NTSC based not PAL. You can convert to a different frame rate if you wish on export.

Although the nvidia card is probably powerful enough for such files, the rest of the system is struggling with the data bandwidth needed.

Ray.

@CubeAce

Ray,

Hardware reserved ram is a Windows thing normally reserving ram for graphics or audio buffer use.

Not in this case. Mine stayed stuck on exactly 8gb (I had 4gb useable, 8gb HR, 12gb total). I did some sleuthing and found that it is caused by a BIOS-level glitch that seems to occur when adding/changing RAM sticks, which I had done over the years. I found a method which involved removing all the RAM, then starting the computer with only one stick, then shutting down, then adding another then starting again. This reset the BIOS somehow and now I have all my RAM available with only a couple of hundred Megs reserved.

My machine did run quite happily with the 4gb and 1920x1080 files; not the fastest box on earth but it worked for many years with MEP.