| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 110528 | 2010-06-21 04:24:00 | Latest version of Ulead VideoStudio | FoxyMX (5) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 1111992 | 2010-06-22 23:09:00 | But 64-bit has nothing to do with large files or not. I've been editing 10GB+ video files for almost a decade now ... Long before even XP was 64-bit! | Chilling_Silence (9) | ||
| 1111993 | 2010-06-22 23:13:00 | Well whatever it didnt work. It loaded but editing it beyond 3 GB closed the program | Speedy Gonzales (78) | ||
| 1111994 | 2010-06-22 23:55:00 | I've been using VideoStudio X2 for quite a while with no problems and just upgraded to X3 last month. It runs a heck of a lot faster than X2 (on Windows 7 64bit) and is very stable (so far). Reads all formats I've thrown at it and produces excellent output DVDs. It has a trial version so throw it on and give it a try. Though I must admit the X3 interface is not that user friendly - a step backwards from previous versions - but the speed increases more than make up for that. |
Wheels (7227) | ||
| 1111995 | 2010-06-22 23:56:00 | That still doesn't mean the problem is with 32-bit software | Chilling_Silence (9) | ||
| 1111996 | 2010-06-23 00:24:00 | Well whatever it didnt work. It loaded but editing it beyond 3 GB closed the program Is it possible Speedy that when you had this problem you were using a FAT32 file system rather than NTFS? I haven't had any probs with large files in NTFS and a 32 bit O/S. |
Sweep (90) | ||
| 1111997 | 2010-06-23 00:49:00 | Nope, I always format in NTFS (none of these are formatted in FAT32). Must have been the program I was using, or because I was using the program in 64 bit. I dont know. Only other thing it may have been was it had something to do with the memory limit (even tho I'm not using 32 bit), with a 32 bit program in 64 bit? Oh well doesnt matter, I probably wont come across the same prob with Moviemaker |
Speedy Gonzales (78) | ||
| 1111998 | 2010-06-25 02:45:00 | This might be a frame rate / field order issue (interlacing). In Super there is a function that will give you a detailed analysis of your source file (the MOV off the camera). Can't recall if it's a double click or a right-click to get to this panel of info. Anyway, for the MOV to MPG stage you should aim to keep all variables the same from source file to target file. Frame rate unchanged, field order unchanged, aspect ratio and resolution unchanged. Do whatever with the audio. If the jerky motion is only involving vertical motion (arms going up or down seem jerky) then this is a field order issue, and you should swap the field settings from A to B / 1 to 2 / top to bottom (or vice-versa). Depends on your playback hardware whether or not you should use Progressive framing, but if it's for TV playback, then stick with the A/B, 1/2, Top/Bottom style of combed frames. Umm... most of that has gone right over my head. :o :lol: I don't see any of the settings highlighted in bold in my version. Here (www.imagef1.net.nz) is a screenshot of the settings I tried last. The results were OK but I feel they could be better. |
FoxyMX (5) | ||
| 1 2 3 | |||||