I'm the one still doing 20 hours... :(
Don't see what it could be....encoding to 7200rpm Hard Drive, with 512MBs SDRAM and a 1GHz Athlon Thunderbird. I normally encode to 480x480...using this kind of script: Code:
LegalClip() |
hi PyRo..
I wish I could help ya, but I'm still using AVIsynth v1.0 beta 5, and most of those filters mergechroma(blur( 1.58 )) and mergeluma(blur( 0.3 )) for ie, don't work, not to mention the others that require v2.x and higher. I'd give that script a test, but I can't :cry: Well, I don't use that many filters anyways, and I guess that one of my delimas in making the switch. Besides, I had so many issues w/ color in my privious encodes of yesterdays, (the past) that I'm just fighting the switch. Defraging your hd won't do much for your processing time, but it can't hurt. I have an idea though.. :idea: How about running a few tests.. for instance, just take ONE item out, and run an encode. But, don't "go all the way" he he.. actually, just wait to see TMPG give you an estimation. Then, do the same with each, and also do a few combinations of filters and see what TMPG's estimation is. Once you have found a short time estimate, you're on your way to finding the cause of your filter that is causing your "slow up". If I had only had the exper. w/ those filters, I'd of probably guesed what was causing the slowness :cry: Good luck anyways. -vhelp |
Quote:
-kwag |
hi Kwag,
ok.. just thought that you had one.. being that you love so much being on top of latest in just aobut everything :wink: Well, I'm waiting for my Osprey-210 analog capture card - - ta add to my list of video devices. I heard a few GOOD things about it, and want to give it a try. Don't get me wrong. I LOVE my ADVC-100 but lets face it, and don't forget.. that its video source is "compressed" hence DV. Anyways.. And, there IS a difference between DV vs. Analog (uncompressed) but not by much. But I believe it is depend (quantity'wise) per Capture card and Maker - we'll see in my next testings of my Osprey-210. I hope it proves positive :wink: I'm always looking for the best Analog Capture card out there, and I think the Osprey-210 is it (so far) after shopping around on-line, I was able to locate a fair price @ $165 (retail $199) - - should arrive around Monday or Tuesday - can't wait :D :D -vhelp |
.
And, here is a comment snipped on it's notary from: ducas NEWS.. Quote:
. http://www.digitalfaq.com/archives/error.gif just realized that it may have ben modified, being that there's TWO pics. FROM: RealNetworks - read the specs there too. . or . http://www.digitalfaq.com/archives/error.gif And, the on-line store, where I ordered it from: DV Direct and some specs from www.ht.com Quote:
|
What chipset is in that card :?: That's the most important thing :!:
Is the ADC 8, 9 or 10 bit :?: -kwag |
Hay Kwag..
I just edited the previous page. Apparently, there may have ben a revision made to the 210 model. The first pic looks like my ATIW cards' breakout connection (the one w/ the circle at top) so do have a look - at least out of curiosity. Kwag Wrote: Quote:
it's probably 8 bits 8O * Any chance you might know what our WinTV-GO is rate at ?? * And, how about the ATI-TV Wonder pci card ?? * Oh, and the DC10+ ?? Thanks for bringing this up though. I didn't realise how important this is to an Analog Capture device. I'm sure the higher the bits, the better! I just did a search on vcdhelp, but they don't have a review. Guess no one has it there yet or they just didn't post a review for it (probably bad) Maybe I'll post first he he.. In any event, I'll give you a heads up :wink: -vhelp |
Quote:
Quote:
-kwag |
hay Kwag..
..back again, after a tiring search. ok, here is what I found on this card, though it's only hear-say from another forum.. basically, it's basd on a BT878 chipset, but again, this is not conclusive, rather someone's assumption. But, I'm tempted to believe the above anyways though. It's looking more so, an 8bit card. There is a cheap 10 bit card out there, that I'm researching on. I think PixelView is using the chipset in one. I started a thread on the Osprey-210 card, for discussions, so not to taint THIS thread's original topic. You can find the link below: --> Capture card: Osprey-210.. my experience.. Kwag.. Thanks for the heads-up on the 10 bit. -vhelp |
@Kwag,
Kwag wrote: Quote:
Divx 2-pass. You run VirtualDub using 2-pass and after the first pass run divx4log to normalize the bitrate allocated to each frame. Then substitute the log created by div4log to do the second pass. It forced Divx to follow the bitrate normalized by divx4log. It didn't work well, but only due to the developer's algo. His algo was suppose to improve allocating bitrates to fast scenes and complicated (e.g. water, smoke) scenes. :) -black prince |
Quote:
-kwag |
Quote:
I've chosen DVD2AVI for this purpose, as we all use DVD2AVI to process our files. So I've integrated this functions transparently in DVD2AVI, so that there is no user interaction. This is how it works: You run DVD2AVI as usual. When you save your project file, say you saved to a name like "movie.d2v". This is an example of what you'll get: Code:
movie.d2v Code:
0 -> I Frame If I get this to work, and I find out how to get the bit rate for each B, P, and I frame, then the actual information will be something like this: Code:
0,I,5203121 Here's the executable so you can try it. It's DVD2AVI 1.76 modified, now named DVD2AVI+Stats. Also I compiled it with full speed optimizations with VC++ Enterprice Edition, so it should be a little bit faster than the regular DVD2AVI 1.76 :wink:. http://www.kvcd.net/dvd2avis.exe Try it :D -kwag |
@Kwag,
Kwag wrote: Quote:
where is SansGrip these days. :?: If this could work, WOW!!! What control you would have over Tmpgenc for bitrate and motion search. Keep working on this Kwag, it has great possibilities :D -black prince |
hi Kwag..
wrote.. Code:
0,I,5203121 * But, how or where would you plug in those values in TMPG ?? * or, how would TMPG use those values, if it uses ANY form of numbers .. for any special purpose ?? * I take it that the 1st digit (before the P/B's) are the actual FRAME no's ?? * And, would this (the numbers) be fed in like "frameserved" or something, .. or would it just be you tipicle .TXT file of some sort ?? Yes, VERY http://www.digitalfaq.com/archives/error.gif interesting http://www.digitalfaq.com/archives/error.gif in deed Thanks, -vhelp |
@vhelp,
vhelp wrote: Quote:
Load>movie.txt (this contains frame number, p or b or I frame type and hopefully in the future bitrate). An external program will need to be developed to change the bitrate for each frame to force Tmpgenc to do a better job with normailzation and motion search. 8) The end result will be a smaller encode and an improvement in picture quality :D Some avs filters won't be needed and that increases the encoding speed. This could be a BIG step forward to improving KVCD even more. -black prince |
Hi vhelp,
That code sniplet, 0,I,5203121, etc., would be the intermediate data spitted out by the modified version of DVD2AVI. This text file is then processed by another program that I still have to make, and that program would process that data and create a file in TMPEG's "Force Picture Type" format which is something like this: Code:
0,I,BitRate=CBR:1800 Go into TMPEG and under GOP tab, click on "Force Picture Type", and there you'll see what we're talking about :) -kwag |
hi Kwag.. black_prince.. and guys,
Thanks for response. Hay, something's wrong w/ your FORUM Kwag.. cause I didin't get any e-mail noticifcation on any responds after my last one !! 8O What's up w/ that 8O 8O 8O Anyhows.. I think I know what you're talking about (got too envolved w/ WWF.. Trish got her ahzz whipped) but I'll have another look into TMPG's GOP tab. @Kwag.. I had time earlier to check out your revised DVD2AVI. Worked like a char !! :lol: :lol: ..what calculating statistics from these numbers. Are their any uses for them in addition to ?? Code:
0,I,BitRate=CBR:1800 .. and/or that can be.. say.. "switched" w/ your NEW table of values he he.. .. "obviously, you're working on this, I realize, but.." Here's what DVD2AVI+ outputed for an encodes (based on a captured source) Thanks to good old Excel.. Code:
FRAMES -- "B" count -- "P" count * also, are you taking into consideration that not all TMPG version are or .. may not act alike in features. You know how THAT song goes.. w/ each .. version tsumi (<-- spelling) makes. -vhelp |
I'm still not sure if I can set bit rate independently for each I, B and P frame. I might just write a dummy ascii file, and then load it with TMPEG's "Load" button under "Force Picture Type", and see if it follows the forced pattern I set in the ascii file. Have a lot to test :roll:
-kwag |
Hey Kwag,
if you can tell me processing needs to be done with your stats file to create the appropriate tmpgenc file, i'll write a perl or php script to do this until an app is developed (i'm a *nix developer, don't have any coding packages for windows). People could either use it locally on a web server on their PC or it could be run off a few websites and people can load their stats log file into the webpage and it would spew out the appropriate tmpgenc file. Would do in the meantime, Cheers, |
@Kwag,
Kwag wrote: Quote:
frame must be the problem. Next, I want to use auto-setting for a .d2v input file and save this as text. If this works, I'm going to play with bitrate for each frame and try to create a small .mvp file to look at my results. I can control the frame range with source range. If I'm lucky, I can pick scenes that could be tested (e.g. water, fire, smoke, etc.) adjusted for bitrate. The magic is using a program to do this auomatically :) -black prince |
Site design, images and content © 2002-2024 The Digital FAQ, www.digitalFAQ.com
Forum Software by vBulletin · Copyright © 2024 Jelsoft Enterprises Ltd.