Welcome Guest ( Log In | Register )


Important

The forums will be closing permanently the weekend of March 15th. Please see the notice in the announcements forum for details.

Pages: (14) « First ... 6 7 [8] 9 10 ... Last » ( Go to first unread post )
Test Thread: Virtualdub 1.7.x, 1.7.X?
« Next Oldest | Next Newest » Track this topic | Email this topic | Print this topic
squid_80
Posted: Jan 3 2008, 09:07 AM


Advanced Member


Group: Members
Posts: 594
Member No.: 13813
Joined: 22-January 05



Fair 'nuff then, as long as one of the two is fixed I'm happy. Both of them combined meant I couldn't actually scroll to the section of the video I was working on when trying to crop.
 
     Top
kewl
Posted: Jan 5 2008, 11:59 PM


Newbie


Group: Members
Posts: 3
Member No.: 22726
Joined: 31-December 07



I agree Phearon let's go with the 1.8.0 experimental, you'll also get more feedback and bug reporting. This is such a powerful release it is worth an experimental release rather than waiting for the remaining issues to be all cleared.

 
     Top
T&T
Posted: Jan 6 2008, 02:25 PM


Advanced Member


Group: Members
Posts: 39
Member No.: 22497
Joined: 26-November 07



Dear Phareon,

I have tested the /capfilealloc argument added in 1.7.X.test10. I think it is not working properly.

In 1.7.7 if I set this option manually the output file size become the given size, during capturing the system load is cca. 30-40% and at the end the file size become the size of the captured bytes.

In 1.7.X.test10 if I set /capfilealloc argument in command line it works contraverted. The file size is growing (not preset to the given value), the system load is 60-70% (as it would be if this parameter is not set) and at the end the file size become the preset value. Even if I capture a 30 s film the file become 18 000 MB as I added to /capfilesize.

Good byte!

TT
 
     Top
phaeron
Posted: Jan 7 2008, 08:38 PM


Virtualdub Developer


Group: Administrator
Posts: 7773
Member No.: 61
Joined: 30-July 02



Hmm, seems to work for me. This allocates a 10MB capture file and then captures with it:
CODE
vdub /capture /capfile e:\test.avi /capfilealloc 10 /capdevice screen /capstart 1s /x


Did you place the /capfilealloc switch after /capfile?
 
    Top
T&T
Posted: Jan 8 2008, 09:00 AM


Advanced Member


Group: Members
Posts: 39
Member No.: 22497
Joined: 26-November 07



Dear Phareon,

no! I did something like this:

CODE
VirtualDub.exe /capture /capfile test.avi /capstart 50s /x /capfilealloc 1000


and later

CODE
VirtualDub.exe /capture /capfile test.avi /capstart 50s /capfilealloc 1000 /x


I'll try to put the /capfilealloc right after the /capfile option as You have written...

THX!

TT
 
     Top
T&T
Posted: Jan 8 2008, 11:06 PM


Advanced Member


Group: Members
Posts: 39
Member No.: 22497
Joined: 26-November 07



Hi,

I've tested what You suggested:

CODE

'/cygdrive/c/Program Files/VirtualDub_1_7_X_test10/VirtualDub.exe' /capture /capfile 'test.avi' /capfilealloc 1000 /capstart 52s /x


It really worked nicely concerning the file sizes. At first it allocated 1000 MB and at the end the file was cut to cca. 77 MB.

But there is a little problem. If I set the allocation size and stop condition manually then VDub uses 29-39% CPU. If I set them and start capturing automatically from command line it uses 55-62%. Even if I set the allocation size from command line and I set the stop condition manually it also uses the lower value.

This is misthical...

THX!

TT

 
     Top
phaeron
Posted: Jan 9 2008, 11:33 AM


Virtualdub Developer


Group: Administrator
Posts: 7773
Member No.: 61
Joined: 30-July 02



Not that surprising. NTFS sucks and all, but 30% of a modern CPU is a bit much for the filesystem to be using.

Does the real-time profiler show anything obvious between capturing with and without preallocation? (It's in the Capture menu.)
 
    Top
T&T
Posted: Jan 10 2008, 10:15 AM


Advanced Member


Group: Members
Posts: 39
Member No.: 22497
Joined: 26-November 07



Dear Phareon,

QUOTE

NTFS sucks and all, but 30% of a modern CPU is a bit much for the filesystem to be using.


What I don't understand why there is difference if I set the preallocation size manually or from the command line.

QUOTE

Does the real-time profiler show anything obvious between capturing with and without preallocation? (It's in the Capture menu.)


I started real-time profiler during the capture, but I do not understand what I ought to see... :-) Can U drop me a link about some doc?

TIA && Good byte!

TT
 
     Top
phaeron
Posted: Jan 10 2008, 10:30 AM


Virtualdub Developer


Group: Administrator
Posts: 7773
Member No.: 61
Joined: 30-July 02



QUOTE
What I don't understand why there is difference if I set the preallocation size manually or from the command line.


Neither do I. VirtualDub has special optimizations to reduce file allocation code during capture -- it grows the file 16MB at a time, and it uses an alternate call that bypasses pre-zeroing -- so this shouldn't be happening continuously anyway.

Do you have a virus scanner running? Have you tried adding AVI files in your capture folder to the exclusion list?

QUOTE
I started real-time profiler during the capture, but I do not understand what I ought to see... :-) Can U drop me a link about some doc?


You need to start it before the capture. It'll come up anyway if you start it during the capture, but it'll be missing information.

What the real-time profiler shows is snapshots of what VirtualDub is doing at different times. Different bars show up that mean different tasks that VirtualDub does during the capture. For example, V-Compress is video compression, and V-Filter is video filtering. There are markers showing divisions in milliseconds, and the longer the bars are, the more time a task is taking. This gives you an idea what's taking CPU time, or what's periodically taking too long and screwing up your capture.

What you're looking for is bars that only show up or are longer when you don't preallocate the file. A-Write and V-Write correspond to audio and video writes, respectively. The arrow keys change the resolution of the snapshot.
 
    Top
squid_80
Posted: Jan 10 2008, 01:37 PM


Advanced Member


Group: Members
Posts: 594
Member No.: 13813
Joined: 22-January 05



I'm getting a crash when I try and direct stream copy an avi when the very first frame is a drop frame (stupid h264 in avi). I tried changing VDDubIOThread::ReadNullVideoFrame a bit:
CODE
VDRenderVideoPipeFrameInfo frameInfo;
frameInfo.mLength   = 0;
frameInfo.mDisplayFrame  = displayFrame;
frameInfo.mTimelineFrame = timelineFrame;
frameInfo.mSrcIndex   = sourceIndex;
frameInfo.mbFinal   = true;

if (displayFrame >= 0) {
 frameInfo.mRawFrame   = -1;
 frameInfo.mFlags   = (vsrc->isKey(displayFrame) ? 0 : kBufferFlagDelta);
 frameInfo.mDroptype   = vsrc->getDropType(displayFrame);
 // Following line has been moved from above
 frameInfo.mTargetFrame  = vsrc->displayToStreamOrder(displayFrame);
} else {

Now it saves the file without crashing, but the new file is nothing but drop frames.

Edit: Bold tags don't work in code sections on this forum.
 
     Top
Barough
Posted: Jan 16 2008, 06:15 PM


Advanced Member


Group: Members
Posts: 95
Member No.: 22677
Joined: 24-December 07



@ phaeron

Maybe a little progress report on how things r going?

--------------------
user posted image
 
    Top
phaeron
Posted: Jan 17 2008, 04:26 AM


Virtualdub Developer


Group: Administrator
Posts: 7773
Member No.: 61
Joined: 30-July 02



Sorry, I was sick for over two weeks and also got sidetracked on a couple of things, so I'm afraid there's not much progress here.
 
    Top
VladSh
Posted: Jan 17 2008, 01:24 PM


Newbie


Group: Members
Posts: 3
Member No.: 22652
Joined: 20-December 07



Hello, I again concerning a audio stream plug-in "stretch".

Restriction on quantity of decimal signs is really removed.
But the plug-in works only in a stretching mode. To set a negative number for audiostream compression (for example 0.01 or -1.01) on it turns out.
Whether it is possible to add such possibility?

Whether it will be possible to supplement it?
 
     Top
phaeron
Posted: Jan 18 2008, 04:08 AM


Virtualdub Developer


Group: Administrator
Posts: 7773
Member No.: 61
Joined: 30-July 02



Huh? The stretch value is a factor. A value of 0.01 means that you're asking the plugin to compress the audio to 1% of its original length, and -1.01 would be 101% in reverse if it were supported. To compress, you use a value between 0 and 1.
 
    Top
Barough
Posted: Jan 18 2008, 04:11 AM


Advanced Member


Group: Members
Posts: 95
Member No.: 22677
Joined: 24-December 07



QUOTE (phaeron @ Jan 17 2008, 05:26 AM)
Sorry, I was sick for over two weeks and also got sidetracked on a couple of things, so I'm afraid there's not much progress here.

Thnx for the reply. Hope that u get feel better and get back on ur feets soon.

--------------------
user posted image
 
    Top
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:
196 replies since Oct 17 2007, 05:26 AM Track this topic | Email this topic | Print this topic
Pages: (14) « First ... 6 7 [8] 9 10 ... Last »
<< Back to Testing / Bug Reports