Zarx264gui 1.3

[Drageer5]

My mp4 file isn't in the folder after i encode I know there have been other problems like this so i decided i'd post the info.

Starting...
x264 [info]: 720x480 @ 29.97 fps
Encoding video stream pass 1 of 1
x264 [info]: using cpu capabilities: MMX2
x264 [info]: profile Main, level 3.0
x264 [info]: frame I:1 Avg QP:17.00 size: 40537
x264 [info]: frame P:66 Avg QP:21.29 size: 23977
x264 [info]: frame B:132 Avg QP:23.61 size: 10425
x264 [info]: consecutive B-frames: 0.0% 0.0% 100.0%
x264 [info]: mb I I16..4: 100.0% 0.0% 0.0%
x264 [info]: mb P I16..4: 46.2% 0.0% 0.0% P16..4: 43.7% 0.0% 0.0% 0.0% 0.0% skip:10.1%
x264 [info]: mb B I16..4: 16.3% 0.0% 0.0% B16..8: 32.7% 0.0% 0.0% direct:20.6% skip:30.4% L0:38.3% L1:38.1% BI:23.6%
x264 [info]: coded y,uvDC,uvAC intra: 52.2% 58.8% 19.6% inter: 35.3% 36.7% 2.6%
x264 [info]: i16 v,h,dc,p: 32% 38% 14% 17%
x264 [info]: kb/s:3613.33
Unknown input file type
Error importing C:\Documents and Settings\OWNER\My Documents\Oblivion Overdose #12.avi-zarx264gui-temp.264: Requested URL is not valid or cannot be found
Finished!

My settings are the default settings as they fit the video I am working on

Thanks in advance,
Drageer

[LantisEscudo]

Try renaming the file so it doesn't include a #. Odd characters like that can cause issues.

[Qyot27]

Is there any ETA on when the additional features are going to be added? Even though I only use the CLI, weightp and the fact that mbtree now works with b-pyramid are really sort of invaluable. Just doing some really unrealistic testing, I can say that x264 truly frightens me. Using approximately the same level of settings I did on my latest video (that I released in February), the filesize on that video to come out of r1373 was less than half what was then - from 46 MBs to 19 MBs, for a 4-minute video. And without practically any visible loss. Granted, I sourced it from the distro encode that's also here on LOCAL, not my lossless copy or the 'master' H.264, but that's still really damn scary.

[Zarxrax]

I'm not sure what you mean by that. It's using build 1369, which was released a few days ago. I've also been keeping it up to date all along. (and currently updating to 1373, as I see something in the changelog that looks fairly important)

Regarding the filename issue. I'll see if I can't add a check to see if filenames contain any invalid characters. I'm not sure how plausible that will be though.

[Qyot27]

I'm not sure what you mean by that. It's using build 1369, which was released a few days ago. I've also been keeping it up to date all along. (and currently updating to 1373, as I see something in the changelog that looks fairly important)

Regarding the filename issue. I'll see if I can't add a check to see if filenames contain any invalid characters. I'm not sure how plausible that will be though.

Never mind, then. I'd neglected to check first and relied only on the latest comments to the thread here, and didn't know the incremental stuff had been done. Sometimes I really need to read more.

[Bakadeshi]

a problem I found on my sister's windows 7 PC (was helping her encode her video to upload), Directshowsource seems to cause x264gui to stop responding (IE if I add the file as an avi and let your program create the avs files, it just hangs. if I try again to open the avs file it creates, it still hangs. When I edit it and change to avisource, it works fine. Directshowsource seems to hang in virtualdub also, so it could be some problem with the version plugin i have and windows 7. Shouldn't opening an AVI in your program default to AVIsource instead of Directshowsource?

Qyot27: According to the docs, Weightp was introduced along with the preset and tune settings, so it should be in any of the builds that use them.

[mirkosp]

Qyot27: According to the docs, Weightp was introduced along with the preset and tune settings, so it should be in any of the builds that use them.

Nah weightp came only recently (after r1300 IIRC), preset and tune have been around since r1177.

[Qyot27]

Qyot27: According to the docs, Weightp was introduced along with the preset and tune settings, so it should be in any of the builds that use them.

I wasn't actually asking for myself - I use the CLI for x264, keep up with the development process near-daily, and compile my own builds on Windows and Linux. I was simply asking when those nicer features would be available for everyone that chooses to use Zarx's GUI, but I hadn't checked the newest build to see if it had been done at the time. I pretty much stuck my foot in my mouth because I'd not looked closer.

That said, the need to rely on DirectShowSource will soon be moot because input through FFmpegSource2 is in the pipeline, as part of the ability for x264 to load AviSynth's source filters directly (which was introduced within the, what, last 10 revisions or something?). Not that script input is being taken out, but x264's input system is becoming more general-purpose.

[Castor Troy]

a problem I found on my sister's windows 7 PC (was helping her encode her video to upload), Directshowsource seems to cause x264gui to stop responding (IE if I add the file as an avi and let your program create the avs files, it just hangs. if I try again to open the avs file it creates, it still hangs. When I edit it and change to avisource, it works fine. Directshowsource seems to hang in virtualdub also, so it could be some problem with the version plugin i have and windows 7. Shouldn't opening an AVI in your program default to AVIsource instead of Directshowsource?

Qyot27: According to the docs, Weightp was introduced along with the preset and tune settings, so it should be in any of the builds that use them.

Maybe this could be the reason why it's not working on my win7 machine.

[BasharOfTheAges]

The 64bit version should be slightly faster (I saw a 4-5% increase on my system), but the main advantage of this build is in memory usage. In the old version, both x264 and avisynth had to share a single 2gb pool of memory. When encoding at HD resolutions, this could easily lead to out of memory errors.

How much more RAM should it be using? I'm running Win7(pro)x64 using the 64 bit version of x264 and my entire system (including having firefox, Pidgin, etc. up) isn't breaking 2.5GB useage. I'm encoding a 15GB uncompressed 720p video too, so it's not like the file in question is tiny.