I am in the midst of consolidating some old DVD's.
When using media import directly from a DVD, it starts out pretty fast and as it progresses, the import REALLY slows down.
Depending on the size of the import, it will slow down tremendously between 10 and 35 percent. So slow that it takes longer to import than to watch the DVD.
I believe I need to allocate a bit more resources to the I/O.
In the old DOS days, all that was needed would be to increase the quantity of "buffers" in the config.sys file.
I have searched everywhere I can think of to find an equivalent statement or variable in the registry.
Anyone know what variable to change to allocate more resources to the I/O in XP?
Slow Import
Started by
barryware
, Oct 11 2007 09:28 AM
6 replies to this topic
#1
Posted 11 October 2007 - 09:28 AM
#2
Posted 11 October 2007 - 10:23 AM
QUOTE (barryware @ Oct 11 2007, 01:28 PM) <{POST_SNAPBACK}>
I am in the midst of consolidating some old DVD's.
When using media import directly from a DVD, it starts out pretty fast and as it progresses, the import REALLY slows down.
Depending on the size of the import, it will slow down tremendously between 10 and 35 percent. So slow that it takes longer to import than to watch the DVD.
I believe I need to allocate a bit more resources to the I/O.
In the old DOS days, all that was needed would be to increase the quantity of "buffers" in the config.sys file.
I have searched everywhere I can think of to find an equivalent statement or variable in the registry.
Anyone know what variable to change to allocate more resources to the I/O in XP?
When using media import directly from a DVD, it starts out pretty fast and as it progresses, the import REALLY slows down.
Depending on the size of the import, it will slow down tremendously between 10 and 35 percent. So slow that it takes longer to import than to watch the DVD.
I believe I need to allocate a bit more resources to the I/O.
In the old DOS days, all that was needed would be to increase the quantity of "buffers" in the config.sys file.
I have searched everywhere I can think of to find an equivalent statement or variable in the registry.
Anyone know what variable to change to allocate more resources to the I/O in XP?
How much available free space do you have on your hard drive where you are storing yourdata? Have you defragmented your hard drive before starting the import? How much data are your trying to import during one "import session"?
Walt
Dell Dimension 4500S;Windows XP Home Edition SP3; Intel® Pentium® 4 CPU 2.00GHz, 784MB RAM
(NVIDIA GeForce FX 5200, 128 MB memory disabled because of failure)
Intel® 82845G/GL/GE/PE/GV Graphics Controller; DirectX 9.0c (4.09.0000.0904)
SoundMAX Digital Audio
SamsunG CDR/DVD-ROm SM 332B
HLDS GSA-5120D External LG Super-Multi ReWriter
WDC WD400BB-75DEA0, 40 GB HD; Prolific PL3507 Combo External Hard Drive, 80 GB; Maxtor 6 L200R0 USB Hard Drive, 250GB
HP Pavilion dv6 Notebook; Intel Duo CPU 64 bit, T6400 @ 2.0Ghz; 4.0 GB RAM; Vista Home Premium 64bit
Toshiba MK3252GSX ATA 286GB hard drive; HL-DT-ST DVDRAM GSA-T50L ATA burner
Intel 4Series Express Chipset
#3
Posted 11 October 2007 - 10:45 AM
QUOTE (myguggi @ Oct 11 2007, 01:23 PM) <{POST_SNAPBACK}>
How much available free space do you have on your hard drive where you are storing yourdata? Have you defragmented your hard drive before starting the import? How much data are your trying to import during one "import session"?
My "work drive" is is pretty much empty unless a project is in the works. To answer your question, there is just a little under 700gb free.
As it is empty, I defrag it and it takes just a few seconds to complete.
The amount of data varies. Typically, I have a DVD with 15 - 20 minutes of video. In HQ, thats about 13mb a minute.
As I said.... It starts off fine. But after 10% - 35% (depending on the size of the import), it really slows down.
Last time I did this, I think I was using EMC V8. Maybe I'll install V8 on a different rig and see if it does anything different.
I know there is a way to allocate more resources to the I/O. In the old days, it was the "buffers = XXX" in the config.sys file. I can not find any information on the variable in the registry that I need to tweak.
#4
Posted 16 October 2007 - 06:20 AM
Just a little update...
I have spent the last couple of days trying to figure out why the import function of V9 seemed so slow.
To recap.. Once a year or so, I consolidate DVD's that were made throughout the year of events that were taken with a camcorder.
During this consolidation, the import of a DVD using V9 import feature, it would start out pretty quickly, then once into it, would slow down to a crawl. A 20 minute clip (title, chapter, whatever) would take 35+ minutes to import.
During my experimentation, I imaged my drives so I could restore an image and get my rig back to where it was right before the image.
I first tried the import on another rig I have that has V8 on it. The import was as fast as I remember.
To rule out any hardware differences, I uninstalled V9 & installed V8 the the rig I usually use for my multimedia work. The import of V8 was a dramatic improvement (in speed) over V9.
So... There is some difference between V9 & V8 import routine.
But.... I also stumbled across something else which I still can not believe...
If I import a DVD that was mastered with software other than V9 (meaning V8 & non Roxio), the V9 import routine was "lickidy split".
I can't figure out why but the comparison is night & day.
Now before you guys get on me about media (blank DVD's), I purchase my media in bulk and I bought 500 DVD-R's a year & a half ago and I am still working out of the same pile.
I went from V8 to V9 late last December. I date the DVD's I master so I know when they were created.
All the DVD's I have made whether using V8, V9, or non roxio, they all play on set top players, computers, etc so I would say that they are all "good".
Summery:
V9 import of a V9 disk, not so good.
V9 import of a V8 disk, better.
V8 import of a V9 disk, better.
V8 import of non roxio disk, good.
V9 import of a non roxio disk, good.
Probably doesn't matter to anyone. I found it interesting.
I have spent the last couple of days trying to figure out why the import function of V9 seemed so slow.
To recap.. Once a year or so, I consolidate DVD's that were made throughout the year of events that were taken with a camcorder.
During this consolidation, the import of a DVD using V9 import feature, it would start out pretty quickly, then once into it, would slow down to a crawl. A 20 minute clip (title, chapter, whatever) would take 35+ minutes to import.
During my experimentation, I imaged my drives so I could restore an image and get my rig back to where it was right before the image.
I first tried the import on another rig I have that has V8 on it. The import was as fast as I remember.
To rule out any hardware differences, I uninstalled V9 & installed V8 the the rig I usually use for my multimedia work. The import of V8 was a dramatic improvement (in speed) over V9.
So... There is some difference between V9 & V8 import routine.
But.... I also stumbled across something else which I still can not believe...
If I import a DVD that was mastered with software other than V9 (meaning V8 & non Roxio), the V9 import routine was "lickidy split".
I can't figure out why but the comparison is night & day.
Now before you guys get on me about media (blank DVD's), I purchase my media in bulk and I bought 500 DVD-R's a year & a half ago and I am still working out of the same pile.
I went from V8 to V9 late last December. I date the DVD's I master so I know when they were created.
All the DVD's I have made whether using V8, V9, or non roxio, they all play on set top players, computers, etc so I would say that they are all "good".
Summery:
V9 import of a V9 disk, not so good.
V9 import of a V8 disk, better.
V8 import of a V9 disk, better.
V8 import of non roxio disk, good.
V9 import of a non roxio disk, good.
Probably doesn't matter to anyone. I found it interesting.
#5
Posted 16 October 2007 - 10:39 AM
I could care less…
No, just kidding but the harsh reality is that it is irrelevant. V10 is the only version in production. Based on past experience, you will never see any change/update for V9…
Of course I normally just change the vob to mpg which only takes a second or 2.
No, just kidding but the harsh reality is that it is irrelevant. V10 is the only version in production. Based on past experience, you will never see any change/update for V9…
Of course I normally just change the vob to mpg which only takes a second or 2.
Dell 8300 3.0ghz 1.5gb RAM 300gb & 200gb HDs
XP Pro/SP2
NVIDIA GeForce4 MX 440 w/AGP8X
XP Pro/SP2
NVIDIA GeForce4 MX 440 w/AGP8X
#6
Posted 16 October 2007 - 11:20 AM
QUOTE (james_hardin @ Oct 16 2007, 01:39 PM) <{POST_SNAPBACK}>
I could care less…
No, just kidding but the harsh reality is that it is irrelevant. V10 is the only version in production. Based on past experience, you will never see any change/update for V9…
Of course I normally just change the vob to mpg which only takes a second or 2.
No, just kidding but the harsh reality is that it is irrelevant. V10 is the only version in production. Based on past experience, you will never see any change/update for V9…
Of course I normally just change the vob to mpg which only takes a second or 2.
Actually.... It should read "I couldn't care less".. Meaning you could not care any less than you do now.
Enough of grammar for the day
I hear you about renaming the VOB's.. Import lets you import a title, or a chapter within a title and if the clip spans across more than one VOB, then you have to recompile the clips again but the import get everything you need.
On an old DVD project, all the editing has already been done into titles & chapters. That why I do it the way I do.
Never expected another update to V9 (assuming the 9.1 patch is considered an update). We'll see how V10 shakes out when all the smoke clears.
#7
Posted 17 October 2007 - 04:06 AM
Thanks for the grammar tip, but after all these years of saying it incorrectly, I don't know if I can change…
It would be interesting if you could locate a fixable cause.
Even with the careful scenario you painted, I still don't buy into needing to import. I can change the extensions, load all of them or just the ones around the target area and trim it out before you ever get to 20% of your import of your first vob…
Of course this is of no help to someone who cannot get the rename to work with their files!
It would be interesting if you could locate a fixable cause.
Even with the careful scenario you painted, I still don't buy into needing to import. I can change the extensions, load all of them or just the ones around the target area and trim it out before you ever get to 20% of your import of your first vob…
Of course this is of no help to someone who cannot get the rename to work with their files!
Dell 8300 3.0ghz 1.5gb RAM 300gb & 200gb HDs
XP Pro/SP2
NVIDIA GeForce4 MX 440 w/AGP8X
XP Pro/SP2
NVIDIA GeForce4 MX 440 w/AGP8X
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users






