#Crosshair iv formula windows 10 ram speed keygen#
One might point out that all the rendered sequences are now GV codecs. The reason why I kept these large files intact instead of converting to HQ is that the coloring machine will be linking directly to the project media and it can't read GV codecs, hence the. I still can't believed this actually worked.Īll image sequences were rendered as soon as they imported, this was for playback purposes. I think the antivirus, which was said to be least intrusive, was a major factor. It's not a Pentium II anymore, its a 6-core again!!! Wow she runs so smoothly. To be honest, MPPais, I didn't think all those small tweaks would do much. Remember uncompressed files rely on the hard drive subsystem more than on the processor. If you convert, remove the uncompressed files from the drive as well. I say convert to HQ or HQX and don't look back. There will be a delay with large uncompressed files, especially if they are sequences. The fact that you have loaded more information onto that drive means it has to work harder to find them. SATA drives, unlike older SCSI subsystems, loose throughput as the drive fills up. If your current drive has more than 50% on it, you are loosing throughput. The less information that you have on that drive, meaning if it is 85% full, it will have a lower throughput speed than a drive that has used only 10%. If your drives can sustain at least 225-250MB/s, you should be able to edit 1 maybe 2 layers of 8bit YUV 4:2:2 uncompressed. If they are RGB 10bit, well all I can say is good luck. The speed that you need will depend on whether the files are RGB or YUV and 8 or 10bit. To work with uncompressed files you really should be running a raid.
Your hard drive subsystem is more than likely the cause on this. What type of uncompressed files did you receive? Have I hit a limitation with the program? Or is there something I'm not getting? RAM Disk comes to mind.Īnybody feel they have the golden information? Now, when starting the 20 minute process of opening the file, the disk slowly loads up the RAM 85MB at a time, far slower than the transfer speed 2 parallel SATA III drives offer.Īt first I thought I needed to expand the RAID, but they currently output more than what Edius is taking. So why so sluggish? And why the frequent pauses? When in the project, CPU is at 13%, RAM is at 4GB (50%) (ive also maxed out Edius buffer), DISKS are in casual reads. One would look at the machine as the bottleneck correct? But, where my confusion pops in is the machine is not being taxed in any area. (I have temporarily rendered the image sequences to play realtime.) After the VFX import, my Project now acts as a Pendium II, with frequent pauses while the cursor pends (as if autosaving every 15 seconds)(these pauses take 10 seconds themselves), and opening the project takes 20 minutes. Although VFX presence in the film is minor (5%), their lacking compression magnifies their size. Problem comes after I imported 200 more Gigs of VFX in Image Sequences, some in uncompressed avi. I can jog through the whole timeline without a studder. Windows 7, Edius 6.03, Kaspersky Antivirus.Įdius has ran fine, fast, and perfect with thousands of associated mov clips, aided with stepping read of the mirrored RAID1 drives.7200 System Drive SATA II, 2x1TB Scratch (RAID 1) SATA III 64MB cache.AMD 1090T (3.3Ghz, 6 core), ASUS Crosshair IV Formula, 8GB 1600 RAM (it's actually 1800 dropped for tighter timing).I'm runing an intermediate machine designed to handle this project while I build my Intel "monster": It's winding down and I've received most Visual FX back, ready to import and then send off for Coloring (which native forumer Matt-Matt has been generous in accommodating).įirst I'll give my system specs then the problem, so those can make an acurate diagnosis.
As few here know, I've chosen to cut a feature "film" with the program. As I am still new to Edius 6 (having only used it for a year), with these rarer situation instances I find myself learning new things about the program.