SentaiBrad

2020 is probably a stretch? Who knows when their support for W7 ends, unless their site says.

Unless you have a powerful CPU, use the Balanced core though.

Which is totally fine. It works and I don't want to break is really all the answer anyone needs to give. Besides changing a few options though, which happens on every OS, Windows 10 has run flawlessly for me. Performs better than 8.1 did which did better than 7. My other computer had all 3 at one point. 8 had more kinks to overcome than 10 does though for sure. The UWP thing absolutely does not matter in terms of upgrading your OS. It's really not all that bad, the idea behind is fine, but it's kind of what ever. If you're not buying games from the Windows Store, and I sure as hell am not, then it should have absolutely zero bearing on your decision. I've run old applications and they don't all necessarily run better, but not any worse than 8 or 7.

If someone see's this, be very careful with those. As easy as it is to change it over so that you can remove 7 or 8.1, it's just as easy to mess it up.

But does the MBR reside with Windows 10? That never used to be the case, it used to reside with the first OS installed.

Not that this solves the ticket, but tomorrows tutorial is a Feature Specific on Controller Automation.

So a few misconceptions. If Windows 7 is your base OS and you try and remove it your drive will not boot. The Master Boot Record is kept with the first installed OS. The MBR will be tied to 7 / 8.1 and not 10. Once the promotion ends, it is unclear if you will be able to re-install the free upgrade of Windows 10. Their EULA is vague as all hell. I had two machines, one fresh and one the same. I wanted to install MY key of Windows 10 from my old PC to the new one, and it simply did not work. Re-installing Windows 10 on my old machine so my wife had a fresh Windows 10 worked great. If you replace the motherboard you need a new key, they will not provide you with one. If the motherboard is the same, the key is supposed to be kept in here so you don't need to enter it for a re-install, however I still needed to enter it in on my wife's PC anyways. The screwed up part? Our key's were EXACTLY the same. My mother in law's PC is the same. It's the same key they gave to everyone probably in batches or per IP potentially. I would have to confer with someone else and check their key. Another thing? They don't actually give you the key. I had to have software tell me what the key was, and I am glad I did. Belarc Advisor is supposed to work, but it did on one machine and not the other. I can't remember the other software I did use right this second. So, the free upgrade is still a good deal... but very BS. I mean... it's free, what did we expect? If you are on Windows 8.1, just run the upgrade. You're already half way there. The upgrade worked so well for my wife that Start 8, the Start Menu replacement we were using transferred to Windows 10 perfectly. It was obviously bugged so we had to uninstall it, but it was creepy how well the upgrade worked. Don't forget to prune the Windows.old folder when you're done with it. If you are on 7, it may be a harder sell. Honestly, I've actually enjoyed Windows 10 with some changes to their default settings, but most OSes are like this. There is a Windows 10 thread on the forums actually that goes over a lot of the changes I had made when I first upgraded and I shared with everyone.

Edit the XAML files. They're very powerful. It's literally what BigBox is created in, this is our themeing engine.

So, 15 frames a second, 4 seconds of rendering per 1 second of play time. 4 * 35 * 2000 = 77.7777778 hours. So it must be because I am using a higher bitrate generally speaking. In Premiere, my settings and times are way different. I am talking roughly about conversion, but that formula should be roughly correct for however you are currently encoding in to h265.

Yes. We would like to stay there, but then .Net will stop supporting Vista, and when that happens we have to move with it. Once it's unsupported though it also becomes very dangerous. At that point people should move forward. So the bigger thing pushing us forward is .Net, but more than likely when Vista support goes we will probably drop Vista support too.

Some of the later No-Intro sets get updates, but I think the last updates were over a year ago, and even the GoodSets get constant updates. So yea, at a certain point just enjoy your games.

That's also what I am driving at @Supreme. We have data that suggest and supports that users use Vita and 7 machines with extremely tight hardware configurations. We still want the entire community to be covered if they so were to want to use these. Regardless if OUR computers are fine, someone else's may not be.

No problem! I only want the regional exclusives myself, and then I prefer everything to be NTSC generally speaking, and No-Intro was a light at the end of a dark tunnel. Good Sets have their place, but they're miserable to trek through.

Well if we can push the frames per second (during encoding not playback) to make it viable, that's once thing. If you can nail a sweet spot with bitrate too the time to completion will be faster. I mean Cid, you have an octa-core CPU. Your encoder should be utilizing the multi-threading very well. Not everyone will have this to encode with. Assuming 30fps for playback, at 15 to encode that's 1 second of playback for 2 seconds of encoding time. What is the average length? Multiply the average across the total amount of video's left. You have a rough estimate, give or take, the length in which you can encode. It's also worth noting that I generally attempt to encode at higher bitrates. What was the bitrate you chose Cid? As for playback, a newer quad core atom should theoretically smash 265. I believe they have instructions on the hardware level to deal with 265. I would say, easily, anything within the last 4 years of tech that was released within those years is good to go. The farther back you go is really going to depend on software, users computer environment, the bitrate and resolutions.

The network can handle the smaller file size yes, but a more powerful machine is needed to run 265 video. More advanced algorithms and ways to decode and playback video. If you are streaming it over your network through something like Plex or the Universal Media Server then the machine the video is on is doing most of the leg work here. However, a lot of devices and hardware are shipping with 265 encoding and rendering capable parts, so this is less of a big deal. If you picked a laptop or a tablet of several years old, assuming you had the right codecs and the right software you could be looking at a loss in performance. Some users on the site do have older machines. I would be willing to bet your 1GB tablets would cry with BigBox + h265 video for example. Granted, these are extreme cases because... you wanted to, but still, it drives that point fairly well. Of course encoding also requires more powerful hardware. Like I said, I have a really good PC right now and it maxes out the performance of my CPU to encode 7-10 frames of video per second. The weaker the hardware the slower this will become. If you don't have HEVC / h265 capable hardware or special chips (like h264 has in pretty much everything for the last 8 years) then this will go slower, can possibly result in a corrupt video or refuse to do it. When h265 was finally approved, at first it was only software. That was the only way you could watch it, it was all software based. So phones and tablets of that era would lag or not even work. All codec packs needed updating, VLC and Windows Media Player Classic needed updating, everything. Now it's readily available, and even that took a while as there was controversy on how to handle h265. Some places wanted to own and monetize it unlike how h264 is, which is open and why it's available for everything and has become the standard. Even h265 isn't the "standard" yet. First, it was GPU's and CPU's that more readily handled h265 and now tablets and phones are starting to handle that with hardware as well as it becomes more and more of a thing. Now im not saying you need a super computer to play it, but it will either take forever or not even work to encode h265 on a lower speced machine. As far as playing it goes, if you tried playing a 1080p or a 4k h265 mkv or mp4 on a machine that is a little older, I wouldn't be surprised if you hit lag spikes every so often. Playing a 1080p h264 YouTube optimized video takes roughly 150mb of ram and 5% of my CPU. h265 1080p, lower bitrate (so not really optimized, but instead opting for a lower quality standard) started taking 7% of my CPU. I have an Intel i7 6700. So playing, certainly doable on most machines. However, for the best compatability because, lets face it, not a lot of people want to or can upgrade, is probably the best which is an optimized h264 for the time being. My quick stat checking was just in Task Manager also running the video through MPC. Kodi could be different, and then of course running the video through BigBox would be wildly different.

Ah, alright then. It's a bit more complicated than just a script, but that is more or less the deal. You'd also want to work in h264 if you are going to distribute them. Cid and I have discussed this too. h265 / HEVC is fantastic, but it takes a more powerful PC to run these, and much more powerful PC to render these. I don't have a slouch for a PC but converting a non-HD dvd TV episode from source to 265 took 5-8 frames per second, for the entire 24 min episode. This also wasn't an HD video, it was only 540p. Converting 264 to 265 took less time-ish, roughly 9-15 frames a second, but then you also have to add on the time it took to rip as 264 in the first place. So time it originally took + conversion. The end result is obviously great quality and lower file sizes. I would rip as 264 then batch convert in Handbrake to 265. As per settings. h264, 30FPS, 2500-10000kbps (depending on resolution and desired quality to size ratio), and 48,000Hz audio at 320kbps. That's a very common and well accepted baseline conversion. If you are gonna convert it to 265 I would give the video birate a higher kbps as well. So a 720p video, I would personally do 7mbps, 30fps, h264, 48,000Hz and 320kbps. Then convert all as-is to 265.

Video recording and editing is going to be fairly laborious @Supreme. I appreciate the dedication, I do, but are you sure you want to try and go down this road? I only ask because you said your PC knowledge is limited. Also, in the very first post Cid posted a lot of the settings he used for video recording and editing.

I'm agreeing with you. Audio stuttering when LaunchBox was open used to be a thing though too and has since gone away. The clipping audio was system wide though and actually had nothing to specifically do with emulators. You could be listening to music and it would happen.

The bad dumps are what I am talking about. All that extra crap. No-Intro sets have all 3 regions still I thought (could be wrong, it's been a while). I would think though that grabbing the single game that has these minor differences would be easier then sorting an entire set like this. Also, the No-Intro sets are comprised only of the good rips (denoted by [!]).

Well first, try No-Intro sets. A lot better than the Good Sets as it doesn't have all the extra crap. After that, just use the Windows search function, it will help cut down a lot. Try searching for "(U)" or "(J)" etc, and it will filter things out a bit for you.

There shouldn't be any clone or copies from the LB Importer either. Also yea, I never let LaunchBox move my roms either. Gets to be more confusing.

The best thing to do is backup your old media, and just download all new media. Unfortunately there is a limit to how LaunchBox can handle the new image folders.

Yea, even though the 950 was released as a budget card, and even though the new architecture is out now, going from pretty much nothing to a good something is a huge boon! xD

Is there a resolution or aspect stretch option? Might be a dirty way to do it, but.

I own Anachronox actually! So you're not alone. Also, I agree with the others, thank you for doing this! I've asked Jason to give you the permission to edit your posts. I will let you know when he does.