u/teton_blamer

I've taken up a video recording and editing project and I've found myself in a position where my phone is my main/only camera. I'm using a Pixel 6, so there is no MicroSD slot. But is there a way to set up my phone's camera app to save video files to a separate folder? The process of going into the phone's memory and waiting several seconds for the thousands of photos to load just for me to extract one or two video files is cumbersome to say the least and will get old fast.

I'd be willing to either download a 3rd party camera app or get my hands dirty with some coding if I have to. I've never poked around in any Android dev tools, but I'm a fast learner. All I want is for my videos and my photos to be in two separate folders. I'm just trying to avoid buying a new phone or camera just for this project.

I've taken up a video recording and editing project and I've found myself in a position where my phone is my main/only camera. I'm using a Pixel 6, so there is no MicroSD slot. But is there a way to set up my phone's camera app to save video files to a separate folder? The process of going into the phone's memory and waiting several seconds for the thousands of photos to load just for me to extract one or two video files is cumbersome to say the least and will get old fast.

I'd be willing to either download a 3rd party camera app or get my hands dirty with some coding if I have to. I'm just trying to avoid buying a new phone or camera just for this project.

Decided to fire up Oblivion Remastered, which used to run (almost) flawlessly, only to find a buggy mess that either chugs to nothing or just flat-out crashes immediately. Checked all my hardware, tested other games, all my stuff is good. Has anybody else had any luck getting this game to run even halfway decently?

I'm running a 2070 and an i7-9700k, which are slightly dated, but still run modern games with relative ease.

Specs: z390 Aorus Elite mobo, i7 9700k, 32gb ram, 2070 graphics, 500GB NVME SSD boot drive running Windows 11

When I try to boot, it gets stuck on the Aorus logo page for a very long time and sometimes says "Preparing Automatic Repair," then eventually boots, where it takes an additional 5-10 minutes to become usable -- everything is extremely slow and sluggish.

Once booted, it's also not recognizing one of my storage drives. It shows up as "Local Disk" instead of its name and it won't let me click on the drive or do anything to it.

I downloaded an SSD diagnostic program but it won't work properly/at all. It won't recognize any of my drives at all, and is also extreeemely sluggish.

Things I've tried:

• DISM
• System File Check
• Windows Memory Diagnostic
• Repairing boot files via Windows installation media USB (this wouldn't even let me try - when booting from installation USB, all I got was a blank blue screen.)

The diagnostic tools I have been able to run so far have come up with no errors.

Specs: Gigabyte Aorus Z390 mobo, 32GB of DDR4, i7-9700K, RTX 2070

I'll list the things that went wrong in the order that I experienced them.

• Tried to boot PC but it was stuck at the motherboard logo screen (Aorus) with a spinning loading icon. It would then, while staying on the logo screen, say "Preparing Automatic Repair," while still doing nothing much.

I tried tinkering with the mobo BIOS, enabling/disabling fast boot & making sure the right drive was set at the boot drive. At one point while using my laptop to Google symptoms, I left the PC alone and it simply booted up on its own.

• When it got to the login screen, I entered my password and logged in, which took a solid 5-10 minutes.
• Once I did load in, everything was sluggish. Windows Explorer was hardcore lagging.

After a few minutes of this, all seemed fine. I could use programs like normal, and did so, but that didn't last very long.

• Discord would not stay open. It kept randomly freezing up every 5-7 minutes, forcing me to restart the program, just for it to keep happening.

At this point, I decided to try and fix some things in the file system. I ran DISM and System File Checker, both of which reported back with no issues or errors.

I tried to restart the system to check and see if this fixed anything. It did not. I did, however, notice something that was probably there before, but when it gets stuck on the Aorus logo screen while booting, for a moment, it says "Repairing Drive F."

The next day:

• Booting takes just as long as before, but this time, the system is much more sluggish. At one point I'm forced to pull up task manager and restart Windows Explorer because my games folder stopped responding.

I tried to run Halo, which prompted an install screen. As it turns out, one of my storage drives seems to not be working properly, Drive F, which is a 1TB SSD that I only install games on.

• Drive F in my "This PC" screen no longer shows a capacity or a capacity bar and is listed as "Local Disk," rather than the name I gave it when it was installed. I right-clicked the drive and went to "Properties" to try and run an error check on the drive. It took about 4-5 minutes for the properties page to even show up. Once there, I clicked "Check" under "Error Checking." After another 4-5 minutes, I finally got a window that says "The disk check could not be performed because Windows can't access the disk."

This is where I'm at right now. I've made a windows 11 installation media USB for the purposes of repairing the boot files but I haven't used it yet because it actually boots now, albeit ungodly slowly. I'm not sure what to check or what could even be causing my problems. Any and all insight would be immensely appreciated.

*Note: A close friend of mine heard my story and said she had the exact same problem with her laptop yesterday (it kept saying "preparing automatic repair" while booting.) She is much less savvy and took it into a shop right away. They said it was caused by a recent Windows update and proceeded to reformat her boot drive and reinstall windows. I do not want to do that. But I did think it was a useful insight - my PC had an issue booting a few days ago after a Windows update that seemed fine after a couple of restarts. Maybe the update is part of the issue?