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.

 
Wrong Filesize Display Before Muxing Avi+ogg
« Next Oldest | Next Newest » Track this topic | Email this topic | Print this topic
UncasMS
Posted: Jan 11 2003, 01:52 PM


Unregistered









hi guys,


first of all congrats on this terrific tool!



the problem i encountered is this one:

i loaded an avi file + 2 ogg streams into vdmod 1.4.13
my aim was to mux and cut in one go. thus i selected the part of the movie i wanted to have saved as part 1 of 3.

taking a look at the filesize in the "statusbar" gives me WRONG values.
take a look at these two screenshots pls:

1.) AFTER muxing with oggmux:
user posted image


2.) avi + oggs loaded in vdmod:
user posted image


picture number one shows an oggfile, which i have muxed BEFOREHAND with oggmux. this picture shows the CORRECT frames/size in mb.

picture number two shows my avi + 2 ogg files loaded in vdmod.

you'll see i have picked the same frame as cutting point.
cutting like way number 1 results in the right filesize of the final ogg; i.e. 700mb

in case i HAD NOT MUXED before using oggmux (094) or vdmod for that matter and if i wanted vdmod to display the cutting point for an 700mb file, i would have gone a couple of frames further into the movie which would have resulted in a file bigger than 700mb!

i mean, it is no problem reaching my desired filesize by FIRST muxing the file and afterwards cutting it. but this would mean more hdd-space needed and more important an additional step to go.

could it be that no overhead calculation was done for the muxing part in vdmod?


regards, UncasMS

 
  Top
UncasMS
Posted: Jan 12 2003, 01:04 AM


Unregistered









sorry guys,

shame on me!


this has been reported before by bb8

*****
Date: 2002-12-31 03:13
Sender: bb8
Logged In: YES
user_id=658286

VirtualDubMod 1.4.13.1 still doesn't show the MB position correctly
in the above mentioned case (streams not yet muxed). Looks like
the muxing overhead is not taken into account.

*****

despite this changelog:
****
- Fixed a bug not taking into account external Ogg/AC3/MP3/SRT streams when computing file
position.
****

 
  Top
Belgabor
Posted: Jan 12 2003, 02:55 AM


Developer of VirtualdubMod


Group: VirtualdubMod Team
Posts: 100
Member No.: 998
Joined: 24-November 02



The changelog just says these streams are now taking into account, not that it now calculates muxing overhead.

--------------------
[VirtualDubMod Homepage]
Please submit any bugs/patches/feature requests also using the respective tracker on our sourceforge page
 
     Top
UncasMS
Posted: Jan 12 2003, 11:46 AM


Unregistered









whatsoever rolleyes.gif

at least i'm pretty sure now it will be taken care of!


keep up the good work!!
 
  Top
Suiryc
Posted: Feb 11 2003, 09:03 PM


Developer of VirtualdubMod


Group: VirtualdubMod Team
Posts: 222
Member No.: 468
Joined: 10-October 02



Sorry for posting so late ^^'
Actually this is not really a bug. The fact is that when opening an AVI file the position shown is the one in the AVI file (since there are still VDubMod users who cut AVI files wink.gif). When an AVI file is opened I don't know if you want to cut the AVI or mux it in OGM and cut it on the fly.
In the latter case I would have to compute OGM overheads (which is not easy by the way).

--------------------
OGM tools, VirtualDubMod [SourceForge : Tracker/DL] (FAQ)
Don't forget the Needed DLLs for VirtualDubMod. Post bugs/requests in our Tracker.
We give 100% of your donations to the Open Source community
 
      Top
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:
4 replies since Jan 11 2003, 01:52 PM Track this topic | Email this topic | Print this topic

<< Back to Testing / Bug Reports