Bug 21777

Summary:	Grip does not display correctly the encoding progress bar and speed when using oggenc
Product:	Gentoo Linux	Reporter:	Lorenzo Bicci <bicci>
Component:	Current packages	Assignee:	Markus Nigbur (RETIRED) <pYrania>
Status:	RESOLVED CANTFIX
Severity:	minor	CC:	wolfwood
Priority:	Low
Version:	1.4_rc2
Hardware:	x86
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Lorenzo Bicci 2003-05-27 13:03:07 UTC

Grip does not display correctly the encoding progress bar and speed when using 
oggenc: the progress bar becomes full at the beginning of the encoding process, and 
then it remains full until the process has finished. The displayed encoding speed is 
wrong: it starts with 0x and, after a while, it shows impossibly high speeds.

Comment 1 Arcady Genkin (RETIRED) gentoo-dev

2003-10-02 18:32:09 UTC

I'm trying to reduce the number of packages I maintain.
Punting back to bug-wranglers.

Comment 2 wolfwood 2003-10-04 22:09:57 UTC

Lorenzo, what versions of grip and oggenc are you using ?  Does this problem
still exist in the latest version of grip that is in Portage (grip-3.0.3)
or the latest unstable version (grip-3.1.1-r1) ?

Looks like:
http://sourceforge.net/tracker/index.php?func=detail&aid=601672&group_id=3714&atid=103714

May be answered by:
http://www.nostatic.org/grip/doc/faq.html

This may not be a bug, just grip's inability to accurately guess filesize
for files produced by oggenc, which is understandable since ogg bitrates
are adaptive.

Comment 3 Markus Nigbur (RETIRED) gentoo-dev

2003-10-07 23:05:34 UTC

Q: The progress bar doesn't seem to be completely accurate when encoding.
Why can't it get it right?

A: The progress bar is done based on the size of the output file. If you
have the kbits/sec set properly, Grip should estimate the size properly.
Note that if you use variable bitrate encoding (supported by encoders like
LAME and xing) Grip has no way to accurately guess the file size.

Thanks Nicholas.