![]() ![]() I split off the project into double reels, OG style, in an effort to reduce project file size and RAM playback buffer needs, etc. ![]() Then I restarted, loaded my tiny project, started okay, reset the window, then loaded the big project. So I tried to load my big project, crash. Changing the primary monitor control, or going to dual screen and back again, reset that issue. only the top left quarter of the screen was visible. When it worked, R17b1 started in a whacked-out video mode that put its edit etc windows around 50% to the right and 50% down from the top left of the screen - i.e. Loading small ones (one video clip) were not. Nothing left in the background processes.ĭid the usual system checks, and then found a way around the problem. Plus I always backup the project files on the feature I'm working on anyway.Īnyway, upgraded, started, everything loaded fine - until I hit the play bar. I know there's a direct path to the original projects, so apart from feeling like an idiot, I'm short of wanting to kill myself. Updated my DB but like a fool didn't back up first. This worked okay (not great) on 16.2.7 with 4k 35mm scanned footage. Loaded all required drivers, I'm on Win10 on an HP Z820, 64MB RAM, OS and media both running on SSD's. Upgraded to R17b1 from 16.2.7 Studio versions both. ![]() I've posted this separately but I'd like to join the line here too.Ī little bit more detail, for what it's worth: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |