- Code: Select all
AVISource("E:\Exports\Main Comp.avi")
ConvertToYV12()
LanczosResize(832,512)
AVISource("E:\Exports\Main Comp.avi")
ConvertToYV12()
LanczosResize(832,512)
mirkosp wrote:Mmmmmmh... have you tried going to the bat tab, create a bat, and then run that to encode? If so, does the pc still shut down? Trying to isolate the issue, here, if it still shuts down, then it's some problem with x264 rather than the gui, and updating x264 itself might help (although I never had this issue with any of the x264 builds I used nor have I heard about it before).
If, on the other hand, the encode runs fine, then it's some issue with the gui and zarx will have to check out the code of the gui, I guess.

Krisqo wrote:mirkosp wrote:Mmmmmmh... have you tried going to the bat tab, create a bat, and then run that to encode? If so, does the pc still shut down? Trying to isolate the issue, here, if it still shuts down, then it's some problem with x264 rather than the gui, and updating x264 itself might help (although I never had this issue with any of the x264 builds I used nor have I heard about it before).
If, on the other hand, the encode runs fine, then it's some issue with the gui and zarx will have to check out the code of the gui, I guess.
Sorry if I'm a little tech-retarded but what and how do I make bat? I see it in the gui, but I have no idea what to do with it.
Zarxrax wrote:If your whole pc is shutting down that sounds like your cpu could be failing. Have you overclocked your cpu?
Qyot27 wrote:In essence, a .bat file is to Windows what AviSynth is to a video file. Just a series of commands stored in a script and executed - by the OS itself, in this case. The simplest ones are just regular command-line operations put on new lines so that the next operation runs after the last one is finished. This way you could have one line that encodes your audio, one line that encodes your video, and a third to mux them together into your container of choice. And all of this will be done automatically, without you needing to come back and do it yourself (in most cases, anyway).
All you have to do once you have the .bat file is double-click on it. Windows will do the rest.
Scintilla wrote:Use Task Manager or Norton System Doctor or whatever you want to check your CPU usage while the encode is running. If the CPU's being maxed out, then your system may just be failing due to overheating -- my solution for this back in the days when I had that problem was to remove the case cover (side panel).

Krisqo wrote:Hope not. It's a relativly new CPU. What confuses me is that it only happened when I used the zarx264gui. But when I tried VDubMod, no crash. Tossed in 4 nonstop hours of gaming on it. No crash. But I'll run the gui again tomorrow and see what I come up with.
Zarxrax wrote:Krisqo wrote:Hope not. It's a relativly new CPU. What confuses me is that it only happened when I used the zarx264gui. But when I tried VDubMod, no crash. Tossed in 4 nonstop hours of gaming on it. No crash. But I'll run the gui again tomorrow and see what I come up with.
x264 can easily max out all of the cores on a cpu. Virtualdub will only use 1 core unless you are using a codec that is multithreaded (most codecs aren't), and the games you are playing might not be utilizing all of your cpu cores fully.
To test if the problem is your cpu, i'd recommend running prime95 for a while and see if anything happens. Get the version that is appropriate for your operating system:
32bit: http://files.extremeoverclocking.com/file.php?f=103
64bit: http://files.extremeoverclocking.com/file.php?f=205

Krisqo wrote:Looks like it is the CPU. Computer shut off before the any test could be completed (use the Blend test thing). Guess i gotta start saving for a new one.
Zarxrax wrote:Krisqo wrote:Looks like it is the CPU. Computer shut off before the any test could be completed (use the Blend test thing). Guess i gotta start saving for a new one.
The problem is that your CPU is overheating. It could be that a fan inside your PC has failed, or something like that.

Krisqo wrote:Zarxrax wrote:Krisqo wrote:Looks like it is the CPU. Computer shut off before the any test could be completed (use the Blend test thing). Guess i gotta start saving for a new one.
The problem is that your CPU is overheating. It could be that a fan inside your PC has failed, or something like that.
Just did a check of my fans (thank god for clear cases) and all my fans are running. I remember a friend said that having too many fans could cause more heat. I'm using a thermaltake V1 case. Got one intake fan in the front. One big exhaust on the side, two in the back, and one on the top. Plus the heatsink fan.

Krisqo wrote:Turns out the thermal paste was slightly burnt which was causing my CPU temp to shoot up to about 120c when encoding.
Users browsing this forum: No registered users and 0 guests