Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
3rd November 2009, 20:03 | #201 | Link | |
契約者
Join Date: Jun 2008
Posts: 1,576
|
Quote:
|
|
4th November 2009, 11:42 | #202 | Link | |
Registered User
Join Date: Apr 2006
Posts: 1,008
|
Quote:
Pause/Suspend Mode doeasnt work here sometimes? |
|
4th November 2009, 12:01 | #203 | Link |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Just be patient, it may take a moment
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ |
10th November 2009, 04:51 | #205 | Link |
Registered User
Join Date: Oct 2007
Posts: 1,060
|
LoRd_MuldeR
I'd just like to express my gratitude for this software. I could not praise it enough. The interface, simple, but extremely well designed. I couldn't fault the interface. It is just so ergonomically designed, with the auto save setting, to the command line, to displaying avisynth, avi2yuv, and x264 messages. It is simply fantastic. I'm not sure I've given out such praise for a long time, since I'm usually EXTREMELY HARD TO SATISFY. Maybe a little simplicity is what I needed in my complicated software life. |
10th November 2009, 18:23 | #207 | Link |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Maybe I will implement a "real" suspend option one day
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ |
11th November 2009, 02:08 | #208 | Link |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Updated x264 to r1332 (JEEB's builds). I also added a Suspend/Resume button, finally. That was more complicated than I had assumed
(The Win32 API makes it pretty hard for us to suspend a process by ID. Finding grandchild-processes created by your child-process isn't very simple either ^^)
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 11th November 2009 at 02:16. |
12th November 2009, 08:21 | #210 | Link | |
Registered User
Join Date: Apr 2006
Posts: 1,008
|
Quote:
Another Problem is that the gui crashes when encoding is done with a Apprcash Error ? |
|
12th November 2009, 10:56 | #211 | Link |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Give my exact steps to reproduce the problem. It never happened to me...
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ |
12th November 2009, 17:41 | #212 | Link |
Registered User
Join Date: Dec 2001
Posts: 1,219
|
Regarding buffer size, what if the buffer was a multiple of frame size? Wouldn't this give optimal performance, as you would always be sending x264 exactly what it needs to encode an entire frame? Since avs2yuv is outputting raw data, we can calculate this from the resolution.
|
12th November 2009, 17:52 | #213 | Link | |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Quote:
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ |
|
12th November 2009, 22:25 | #214 | Link |
Registered User
Join Date: May 2008
Posts: 1,840
|
If you look through the benchmarks in this thread you'll see 1 and 2 MB buffer are more often faster than 4, 0 and 8 are some times faster as well, although about 5% max gain. I think it should an option, after all what use is a benchmark to find the fastest encode if you can't all the benchmark settings?
A very significant speed up is using x86 with first pass and veryfast, ultrafast presets, you can gain 20% fps in these situations and in my tests 2 pass is always significantly slower with x64 then it is x86 because you lose 10-15% fps on the first pass. I've coded both of these in and reduced min x264 version to 1300 because 1332 is much slower, weightp breaks coreavc and is forced unless mbtree, psy-rd is disabled or interlaced is enabled. Also as it's a new feature without any public testing bugs can be expected. The only thing is I get a statement was expected but found a procedure error when compiling and I can't figure out what is causing it. Source here if anyone wants to look at it. EDIT: also couldn't figure out how to set buffer size with a combobox. Last edited by turbojet; 12th November 2009 at 22:43. |
12th November 2009, 23:25 | #215 | Link |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Weight-P is optional. It's on by default with "smart" (weightp=2) mode, yes. But you can reduce it to "blind" (weightp=1) mode or even disable it (weightp=0).
Additionally some of the faster presets reduce/disable Weight-P. The "baseline" profile will disable Weight-P too! CoreAVC only has problems with "smart" mode. And even that only in Non-CUDA mode. Furthermore we shouldn't restrict our encodes, just because one decoder is broken. Instead we should spread weightp=2 encodes and encourage the decoder developers to get their code fixed asap
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 12th November 2009 at 23:27. |
13th November 2009, 00:24 | #217 | Link |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
I highly doubt a GUI problem, especially if the GUI window does still respond.
Also nothing changed on the GUI's side recently, as long as you don't use the new Suspend/Resume functionality. So you may want to run x264 x64 from the console, just to be sure! And it may also be Avisynth (or one of the filters/decoders involved) that stops delivering new data to x264...
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 13th November 2009 at 00:31. |
13th November 2009, 09:34 | #218 | Link |
Registered User
Join Date: Dec 2001
Posts: 145
|
I also got this freeze with the latest. Just a "AviSource" (DV) and interlaced encoding (crf 22, bff, nalhrd, vbv params set & sar, otherwise medium default high profile without tunings, so weight-p was disabled too).
Worked fine from command line (just copy/pasted from GUI log). Couldn't replicate from GUI either later with another file, so seems random. I find it unlikely GUI would cause something like this (especially since GUI remained functional), unless the "suspend" gets triggered somehow (unlikely). Maybe some kind of thread-deadlock in new x264, but hard to say at this time. |
13th November 2009, 11:37 | #220 | Link | |||
Registered User
Join Date: May 2008
Posts: 1,840
|
Quote:
Quote:
Quote:
I've also had the random freezes with x264.nl and jeeb's builds. x264 doesn't crash it just stops updating and cpu drops to 0. It's happened with gui and cli on 4 full movie sources so far. I haven't been able to complete a second pass. x264 1319 worked on the same sources without a problem. Tough to rely on this gui when it's locked to x264 1332. |
|||
Thread Tools | Search this Thread |
Display Modes | |
|
|