FAQ
Cover
\
Build
\
Source
\
Bugs
\
Reference
\
Libraries
\
Tools
The bugs database has moved
here
.
Bug 280 : Capture.list() starts sound of default device
Last modified: 2007-02-03 12:18
P
roject:
processing
trash
Version:
unspecified
Co
m
ponent:
android
book
core
libraries
pde
reference
tools
web
Status:
RESOLVED
Resolution:
WORKSFORME -
Pr
i
ority:
P5
Severity:
normal
Platform
All
O
S:
All
Windows
Mac OS
Linux
Other
Reporter:
FloHimself
Assigned To:
fry
Attachment
Type
Created
Size
Actions
Description
: Opened: 2006-01-27 10:45
when executing this simple sketch, the sound of the default defice is
started and keeps playing even when the sketch is closed.
[code]
import processing.video.*;
void setup()
{
size(320, 240);
println(Capture.list());
}
[/code]
I don't know if this is a QTJava problem or the SequenceGrabber object
istn't disposed in Capture.list(). Maybe a grabber.disposeQTObject(); is
doing it.
Additional Comment
#1 From fry 2006-01-27 10:50
i've never had this happen, could you please be a bit more specific about
what situation? (platform, setup, capture card, vdig...)
Additional Comment
#2 From FloHimself 2006-01-27 10:59
hmm.. a MsgBox is popping up sometimes... complaining about the "0Pinnacle WDM
PCTV Video Capture-WDM : Problem connecting Video Output to Video Renderer"
and also the Capture.list(); gives a doubled output of the devices like:
Dual-Mode DSC(2770)-WDM
Dual-Mode DSC(2770)-WDM
Pinnacle WDM PCTV Video Capture-WDM
Pinnacle WDM PCTV Video Capture-WDM
I am running P103 on Windows XP SP2 with QT 7.0.3 and WinVDIG 1.0.5
Additional Comment
#3 From FloHimself 2006-01-27 11:26
Ok, grabber.disposeQTObject(); doesn't solve this.
Maybe it is just a problem with my old TV Capture Card and my
messy Windows box.
I will do some more tests.
If noone else ever reported something like this, you may ignore it...
Additional Comment
#4 From fry 2007-02-03 09:29
might be a problem with winvdig? apparently version 1.0.5 is a lot of
trouble. try an earlier release perhaps?
Additional Comment
#5 From fry 2007-02-03 12:18
closing this bug, though we'll reopen if somebody else runs into trouble
with it.