I've been using the DVDFab--FixVTS--DVDShrink--ImgBurn method of making discs if it matters.
One thing I'm wondering is when you Backup using DVD Shrink there is the option to run backup in low priority mode. Now does this affect the quality in anyway? I'd like to run it in low priority so I could still play poker or surf the web while backing up, but if it's going to result in lower quality videos then I'll just have to learn to leave my computer alone for a half hour or whatever while it's running.
Ok, apoligize if this is a dumb question, but it's been nagging me and since I'm going to back up my entire collection over the next couple months it could save me a lot of time or help me make better discs.
I always leave the backup in low priority mode ticked on all my backups,whether it's 0 compression or 40%. I'm not sure of a quality difference,but only adds a minute or 2 to the process time for me.
Now the Adaptive error compensation enhancements will help the quality. Any compression over 15% and I'll tick the Max Smoothness. 30% or more, I'll tick the Max sharpness. Those AEC enhancements will help the quality,but slows down the backup process time.
Multi-Tasking during the dvd backup process? I'm old school. I don't multitask during any of the dvd backup process.The newer dual cores/quad cores may handle it better.I just set it and forget.
A program I use is called SysMetrix,and it tells me how my processor and ram fair, while doing anything on my pc. When I use dvd shrink to analyze and encode to the HD,then it takes up 95%-100% of my processor-the dial glows.Dvd shrink is a resource hog. When nero kicks in to autoburn,then the processor stays below 4%.Dvd shrink is a resource hog. Anything kicking on like screen savers,windows/antivirus auto updates, while your processor is maxxed-then a chance for small errors/glitches. Others will tell you to not to multitask during the burn.
Okay sorry for asking, but if you're not using the computer for anything else then why put it DVDShrink in low priority? I thought that was the point of it, but again I am new so I'm just trying to learn. And thanks for the tip, I'll just start watching TV while it backsup.
You really shouldn't fk around with your PC too much when converting anything, especially videos.
Converting formats is always a CPU intensive process (around 100%), if you run the app at low-CPU priority or run too many programs on top of it, it can slow the process down and increase the time it takes to encode.
Just like if you tried playing a game with 20 applications running the background the performance hits the fan and you get all kinds of choppiness, artifacting, etc...
So with that logic you certainly could affect video quality.
I like to leave the computer alone and let it do it's thing ;)
I personally don't buy in to the 'not multitasking' while encoding/transcoding/AVI conversion thing, i've always multitasked (heavily) during those processes and not once have i suffered choppiness/artifacts etc in the output video (and that was on much slower computers than i use now); however when we're talking about the burn process, multitasking during burning most definitely can affect the resultant disc/output (running out of memory can also wreck the resultant disc as Windows will be using it's swap file ie the hard disc hence disc thrashing occurs and that's a killer for burnt video.
Multitasking during burning is supposedly do-able on more modern CPU's of course, i'm now running a quad core and have burnt the odd disc whilst running ConvertxtoDvdand DVD Rebuilder simultaneously, though i still prefer to leave the PC alone for the most part whilst burning, some old habits are a little hard to let go of in the world of burning dvd's
I'm still of the old school as well. I don't multitask during any of the process, especially the burning part. My laptop is dual core and would probably handle multitasking fine, it's just like Creaky said, old habits die hard.
Multi Tasking doesn't create errors, just delays. Especially if you have a lot of page swapping to do it. The only process I let run exclusively is the burning process (don't want any buffer under-runs)...
