stop-time not working in XP?

[cat6man]

"c:\program files\videolan\vlc\vlc" "c:\my music\track%1.wav" :sout=#duplicate{dst=std{access=file,mux=wav,url="c:\vlc%1.wav"}} --stop-time=%2 vlc:quit

the above command line works fine on my win2k machine (and stop writing the output file at %2 seconds) but not on my XP machine. if i set it to 30 seconds, i get a 30 second file.

on the XP machine, the stop-time option doesn't work properly. i get an output file but it doesn't stop at 30 seconds.

is this a known problem or something weird here?

thanks

[cat6man]

bump.....is anyone successfully using stop-time on an XP machine?

[cat6man]

a few more clues on my XP machine:

1) this works and plays the file for %2 seconds

"c:\program files\videolan\vlc\vlc" "d:\media\misc\track%1.wav" --stop-time=%2 vlc:quit
exit


2) this plays the entire file and write it out to vlc%1.wav.....it ignores the stop-time command entirely

"c:\program files\videolan\vlc\vlc" "d:\media\misc\track%1.wav" :sout=#duplicate{dst=std{access=file,mux=wav,url="d:\vlc%1.wav"}} --stop-time=%2 vlc:quit
exit

[cat6man]

yet more clues....maybe i'm homing in on the problem.

1) audio tests
my xp machine is quite a bit faster than my win2k machine.

therefore, when i try to stream to file a short segment for testing, the faster machine overshoots significantly because it is so fast.

when i tried a WAV file and set stop-time=20, it always went over 60 seconds on the xp machine.

when i tried stop-time=240, it was around 300 and when i set stop-time=360, it was around 363.

i conclude that stop-time can be erratic if the stop-time is exceeded before vlc gets to check for it.

2) video capture with dshow (MOT firewire capture)

apparently, the stop-time option has not been implemented yet for dshow, hence my inability to get a recorded file to stop.
in the message file, i found the following:

main debug: using access2 module "dshow"
main debug: pre buffering
main debug: received first data for our buffer
main debug: prebuffering done 48128 bytes in 0s - 1516 kbytes/s
main debug: creating demux: access='dshow' demux='' path=''
main debug: looking for demux2 module: 40 candidates
main debug: using demux2 module "ts"
ts debug: DEMUX_SET_GROUP 0 00000000
main debug: starting in synch mode
dshow warning: unimplemented query in control <=======
main debug: `dshow://' successfully opened


the message doesn't say exactly what is happening but i'm guessing that stop-time isn't implemented in dshow yet.

anyone know?

[DJ]

I'm running a 2.8 Gig machine and I just tried your little experiment.

When I asked for a 2 second file it gave me 5 seconds, when I asked for a 1 second file it gave me 4 seconds, so I went and looked at the buffer size and its default is 300 ms. Does this make some sense now?

Actually if I want to be precise I would rather transcode the file and load it into an editor and cut the exact thing I want rather that try the hit or miss during the transcode process and have to fool with the buffer that I will always forget to reset. Then something else wont work right and I can go troubleshoot my own stupidity.

But then again maybe your better at this than I am!

[cat6man]

dj,

do you get it to work with DSHOW?? that is the one that doesn't stop at all for me.

what i am trying to do is use a batch command line to record video from a MOT STB.......the short stuff was just for testing and the buffer makes sense as the cause of the time differential....when i set it to 4 or 5 minutes, the file length was fine.

i think it may be that it doesn't work with DSHOW......have you tried that?

"c:\program files\videolan\vlc\vlc" dshow:// :dshow-vdev="Motorola AV/C Tuner Device" :dshow-adev="" :dshow-size="" :sout=#duplicate{dst=display,dst=std{access=file,mux=ts,url="d:\media\temp\vlctest.ts"}} --stop-time=120

this is the command line i really need to get working.......we're trying to build a plugin to get it to work with the TV scheduler in BTV to get firewire recording from STB, but this
records and/or displays fine but never stops at all

cheers

[DJ]

dj,

do you get it to work with DSHOW?? that is the one that doesn't stop at all for me.

what i am trying to do is use a batch command line to record video from a MOT STB.......the short stuff was just for testing and the buffer makes sense as the cause of the time differential....when i set it to 4 or 5 minutes, the file length was fine.

i think it may be that it doesn't work with DSHOW......have you tried that?

"c:\program files\videolan\vlc\vlc" dshow:// :dshow-vdev="Motorola AV/C Tuner Device" :dshow-adev="" :dshow-size="" :sout=#duplicate{dst=display,dst=std{access=file,mux=ts,url="d:\media\temp\vlctest.ts"}} --stop-time=120

this is the command line i really need to get working.......we're trying to build a plugin to get it to work with the TV scheduler in BTV to get firewire recording from STB, but this
records and/or displays fine but never stops at all

cheers

I wouldn't think the answer would be different. The time revolves around the transcoding not the input that's why the buffer time is an addon to the total time. Unless it is having problem closing down with some inputs. ????? If so, it seems it would be a driver problem, but I could be wrong about this.