Re: [bongo-devel] Re: seek and volume

[Daniel Brockman]

address@hidden (Daniel Jensen) writes:

> Daniel Brockman <address@hidden> writes:
>
>> address@hidden (Daniel Jensen) writes:
>>
>>> Seeking to 0%; I get "Elapsed time not available", where
>>> it used to just stay at 0% while the key was pressed.
>>
>> Oh, I did that on purpose because VLC keeps saying it's at
>> zero seconds offset when playing a CD.  (In fact, it doesn't
>> seem to know the offset at all.)
>
> This is strange! It seems VLC shows progress correctly with `cdda://',
> but not with `cdda://@1'.

Oh, interesting.

> But I can't use `cdda://' in Bongo, vlc quits for some reason. Hm...

Yeah, I noticed that too.

wigwam:~$ vlc -I rc cdda://
VLC media player 0.8.5-1-svn-debian Janus
Remote control interface initialized. Type `help' for help.
status change: ( new input: cdda:// )
status change: ( audio volume: 256 )
status change: ( play state: 1 )
[00000291] main private error: cannot pre fill buffer
status change: ( stop state: 0 )
status change: ( new input: cdda:// )
status change: ( audio volume: 256 )
status change: ( play state: 1 )

As soon as Bongo ses the "stop state: 0" line, it terminates
the VLC process, believing that the file has been played.

I'm not sure what to do about this.

>> Can you think of a workaround?  I guess we could start off
>> assuming zero means "zero", but if we keep getting zero for
>> more than a few seconds, assume it means "don't know"?
>
> I have to assume this is a bug in VLC. Bongo should not have to do
> something funky because of this. Do you agree?

Yes, it looks like a VLC bug.  Do you feel like reporting it?
If not, I'll do it tomorrow.

>>> The mpg123 back-end now has problems with the progress bar.
>>> It stalls during seeking.
>>
>> I can't reproduce this and I'm not sure what you mean.
>> How does it stall and how you you provoke the stalling?
>
> I hold `f' down, my usual test. Seems to catch a lot of bugs. :-)
>
> After a while the (visual) progress stalls. But seeking is
> still going on in the background.

Thanks.  I will try to look into this tomorrow.

-- 
Daniel Brockman <address@hidden>