The VideoLAN Forums

Discussion and support for VLC media player and friends
http://forum.videolan.org/

Dshow color is wrong

http://forum.videolan.org/viewtopic.php?f=14&t=52736

Page 1 of 1

Dshow color is wrong

Posted: 14 Nov 2008 19:34
by Zeek
Hi,
When I play the Capture device with my webcam, the color is backwards, blue is red and vice-versa, and actually i go threw a program called Manycam, so I could change the color and see when I made it all blue on manycam it made it all red on vlc, which was really funny but anyways...

Just thought I'd point out the vlc has the colors backwards for dshow with webcams....



I guess I should post a screenshot to?
VLC
Image
ManyCam(it's suppose to be blue like that)
Image


edit:I was just using my desktop as a demonstration I know you can stream it from vlc, and another thing I'm using 0.9.6, so screen:// works fine just not dshow://

Re: Dshow color is wrong

Posted: 15 Nov 2008 16:16
by VLC_help
Which colorspace you chose from DShow options?

Re: Dshow color is wrong

Posted: 15 Nov 2008 22:35
by Zeek
colorspace? Where would I change that?

Re: Dshow color is wrong

Posted: 16 Nov 2008 15:09
by VLC_help
It is called Video input chroma format. (under advanced options)

Re: Dshow color is wrong

Posted: 17 Nov 2008 17:52
by Zeek
Ok it's set to nothing? What should it be?

Re: Dshow color is wrong

Posted: 18 Nov 2008 16:24
by VLC_help
YV12, RV24, YUY2, UYVY etc.

Re: Dshow color is wrong

Posted: 18 Nov 2008 16:55
by Zeek
Ok I tried the ones u mentioned there the RV24 is the only one that it would open it as, or I'd get a msg saying

Code: Select all

Your input can't be opened: VLC is unable to open the MRL 'dshow://'. Check the log for details. Capturing failed: The capture device "ManyCam Virtual Webcam" does not support the required parameters. or with my cam Capturing failed: The capture device "Microsoft LifeCam NX-3000" does not support the required parameters.

RV24 and the default works, but I noticed with the default blank, my cam will not show up at all in vlc it will open and the light will turn on that is on my web cam but no video shows. If I put RV24 in there I still get the crazy colors.

Re: Dshow color is wrong

Posted: 19 Nov 2008 15:52
by VLC_help
Tools -> Messages... (set Verbosity 2) before opening the webcam should show the supported colorspaces.

Re: Dshow color is wrong

Posted: 19 Nov 2008 16:04
by Zeek
I'm guessing,
dshow debug: selected video pin accepts format: I420
is what you mean?
That's what I use for it and nothing comes up, but if I use RV24
dshow debug: selected video pin accepts format: RV24
and it atleast comes up but with the crazy colors.

Code: Select all

qt4 debug: This shouldn't happen, please report qt4 debug: This shouldn't happen, please report qt4 debug: :dshow-caching=200 :dshow-vdev="" :dshow-adev="" :dshow-size="" :dshow-chroma="RV24" :dshow-fps=0 :no-dshow-config :no-dshow-tuner :dshow-tuner-channel=0 :dshow-tuner-country=0 :dshow-tuner-input=0 :dshow-video-input=-1 :dshow-audio-input=-1 :dshow-video-output=-1 :dshow-audio-output=-1 :dshow-amtuner-mode=1 :dshow-audio-channels=0 :dshow-audio-samplerate=0 :dshow-audio-bitspersample=0 qt4 debug: New item: dshow:// qt4 debug: New Option: :dshow-vdev=Microsoft LifeCam NX-3000 qt4 debug: New Option: :dshow-adev=none qt4 debug: New Option: :dshow-caching=200 qt4 debug: New Option: :dshow-vdev= qt4 debug: New Option: :dshow-adev= qt4 debug: New Option: :dshow-size= qt4 debug: New Option: :dshow-chroma=RV24 qt4 debug: New Option: :dshow-fps=0 qt4 debug: New Option: :no-dshow-config qt4 debug: New Option: :no-dshow-tuner qt4 debug: New Option: :dshow-tuner-channel=0 qt4 debug: New Option: :dshow-tuner-country=0 qt4 debug: New Option: :dshow-tuner-input=0 qt4 debug: New Option: :dshow-video-input=-1 qt4 debug: New Option: :dshow-audio-input=-1 qt4 debug: New Option: :dshow-video-output=-1 qt4 debug: New Option: :dshow-audio-output=-1 qt4 debug: New Option: :dshow-amtuner-mode=1 qt4 debug: New Option: :dshow-audio-channels=0 qt4 debug: New Option: :dshow-audio-samplerate=0 qt4 debug: New Option: :dshow-audio-bitspersample=0 main debug: adding item `dshow://' ( dshow:// ) main debug: rebuilding array of current - root Playlist main debug: rebuild done - 3 items, index 1 main debug: dying input main debug: control type=0 main debug: control: stopping input dshow debug: CaptureFilter::Pause qt4 debug: Updating the stream status: 8 main debug: dying input main debug: dying input dshow debug: CaptureFilter::Stop dshow debug: CapturePin::EndFlush dshow debug: releasing DirectShow dshow debug: CaptureFilter::EnumPins dshow debug: CapturePin::QueryDirection dshow debug: CapturePin::ConnectedTo [OK] dshow debug: CapturePin::Disconnect [OK] dshow debug: CaptureFilter::SetSyncSource dshow debug: CaptureFilter::JoinFilterGraph dshow debug: CaptureFilter::GetState 0 dshow debug: CaptureFilter::~CaptureFilter dshow debug: CapturePin::~CapturePin main debug: dying input main debug: dying input main debug: removing module "dshow" main debug: removing module "rawvideo" main debug: thread ended main debug: thread times: real 0m56.937500s, kernel 0m0.078125s, user 0m0.031250s main debug: thread 6188 joined (input/decoder.c:248) main debug: killing decoder fourcc `RV24', 0 PES in FIFO main debug: dying input main debug: removing module "swscale" vout_directx debug: DirectXCloseSurface vout_directx debug: DirectXCloseDisplay vout_directx debug: DirectXCloseDisplay clipper vout_directx debug: DirectXCloseDisplay display vout_directx debug: DirectXCloseDDraw main debug: thread ended main debug: thread times: real 0m56.687500s, kernel 0m0.062500s, user 0m0.609375s main debug: thread 5824 joined (video_output/video_output.c:536) vout_directx debug: DirectXEventThread terminating vout_directx debug: DirectXCloseWindow vout_directx debug: WinProc WM_DESTROY qt4 debug: Qt FS: Detaching Vout qt4 debug: Qt: Changing Fullscreen Mode main debug: removing module "qt4" main debug: thread ended main debug: thread times: real 0m56.765625s, kernel 0m0.046875s, user 0m0.000000s main debug: thread 6248 joined (directx.c:513) main debug: removing module "vout_directx" main debug: removing module "blend" main debug: dying input main debug: thread times: real 0m0.031250s, kernel 0m0.000000s, user 0m0.000000s main debug: thread 6296 joined (freetype.c:511) main debug: removing module "freetype" main debug: thread ended qt4 debug: Video is not needed anymore qt4 debug: Updating the geometry main debug: dead input main debug: thread times: real 0m57.078125s, kernel 0m0.031250s, user 0m0.015625s main debug: thread 5704 joined (playlist/engine.c:244) main debug: TIMER input launching for 'dshow://' : 101.000 ms - Total 101.000 ms / 1 intvls (Avg 101.000 ms) main debug: starting new item main debug: processing request item dshow:// node null skip 0 main debug: resyncing on dshow:// main debug: dshow:// is at 2 main debug: creating new input thread main debug: Creating an input for 'dshow://' main debug: waiting for thread initialization main debug: thread started main debug: thread 6112 (input) created at priority 1 (input/input.c:370) main debug: `dshow://' gives access `dshow' demux `' path `' main debug: creating demux: access='dshow' demux='' path='' main debug: looking for access_demux module: 1 candidate qt4 debug: Updating the stream status: 3 dshow debug: found device: ManyCam Virtual Webcam dshow debug: found device: Microsoft LifeCam NX-3000 dshow debug: using device: Microsoft LifeCam NX-3000 dshow debug: EnumDeviceCaps: output pin: Capture dshow debug: EnumDeviceCaps: input pin: Video Camera Terminal dshow debug: EnumDeviceCaps: trying pin Capture dshow debug: EnumDeviceCaps: input pin default format configured dshow debug: EnumDeviceCaps: input pin accepts chroma: RV24, width:352, height:288, fps:30.000030 dshow debug: CaptureFilter::JoinFilterGraph dshow debug: connecting filters dshow debug: CaptureFilter::EnumPins dshow debug: CapturePin::QueryDirection dshow debug: CapturePin::ConnectedTo [not connected] dshow debug: CapturePin::QueryPinInfo dshow debug: CaptureFilter::QueryFilterInfo dshow debug: CapturePin::QueryPinInfo dshow debug: CaptureFilter::EnumPins dshow debug: CapturePin::QueryDirection dshow debug: CapturePin::QueryDirection dshow debug: CapturePin::QueryAccept [OK] (width=352, height=288, chroma=RV24, fps=30.000030) dshow debug: CapturePin::ReceiveConnection [OK] dshow debug: CapturePin::NotifyAllocator dshow debug: filters connected successfully ! dshow debug: MEDIATYPE_Video dshow debug: selected video pin accepts format: RV24 dshow debug: found device: Microsoft LifeCam NX-3000. dshow debug: found device: Realtek HD Audio Input dshow error: can't use device: none, unsupported device type dshow error: can't open audio dshow debug: Playing... dshow debug: CapturePin::QueryPinInfo dshow debug: CaptureFilter::EnumPins qt4 debug: Destroy the Interaction Dialog qt4 debug: Hide the Interaction Dialog dshow debug: CapturePin::QueryDirection dshow debug: CapturePin::QueryPinInfo dshow debug: CaptureFilter::EnumPins dshow debug: CapturePin::QueryDirection dshow debug: CaptureFilter::EnumPins dshow debug: CapturePin::QueryDirection dshow debug: CaptureFilter::EnumPins dshow debug: CapturePin::QueryDirection dshow debug: CapturePin::ConnectedTo [OK] dshow debug: CaptureFilter::SetSyncSource dshow debug: CaptureFilter::Pause dshow debug: CaptureFilter::Run main debug: selecting program id=0 main debug: using access_demux module "dshow" main debug: TIMER module_Need() : 106.000 ms - Total 106.000 ms / 1 intvls (Avg 106.000 ms) main debug: looking for a subtitle file in D:\Program Files\VideoLAN\VLC\ main debug: looking for decoder module: 33 candidates kate debug: kate: OpenDecoder main debug: using decoder module "rawvideo" main debug: TIMER module_Need() : 1.000 ms - Total 1.000 ms / 1 intvls (Avg 1.000 ms) main debug: thread 5240 (decoder) created at priority 0 (input/decoder.c:217) main debug: thread started main debug: `dshow://' successfully opened main debug: control type=1 main debug: no usable vout present, spawning one main debug: window size: 384x288 main debug: looking for video output module: 6 candidates vout_directx debug: creating DirectXEventThread main debug: waiting for thread initialization main debug: thread started vout_directx debug: DirectXCreateWindow main debug: looking for vout window module: 2 candidates qt4 debug: waiting for interface... qt4 debug: requesting window... qt4 debug: Video was requested -1, -1 qt4 debug: New Event: type 1108 qt4 debug: New Event: type 1103 qt4 debug: Updating the stream status: 3 qt4 debug: Video is resizing to: 384 288 qt4 debug: Qt FS: Attaching Vout qt4 debug: Qt: Changing Fullscreen Mode main debug: using vout window module "qt4" main debug: TIMER module_Need() : 82.000 ms - Total 82.000 ms / 1 intvls (Avg 82.000 ms) vout_directx debug: created video sub-window main debug: thread 6080 (Vout Events Thread) created at priority 0 (directx.c:281) vout_directx debug: Vout EventThread running vout_directx debug: DirectXInitDDraw vout_directx debug: directx-device: vout_directx debug: DirectXEnumCallback: Primary Display Driver, display vout_directx debug: DirectXEnumCallback: Mobile Intel(R) 965 Express Chipset Family, \\.\DISPLAY1 vout_directx debug: selecting Mobile Intel(R) 965 Express Chipset Family, \\.\DISPLAY1 vout_directx debug: screen dimensions (0x0,1280x800) vout_directx debug: DirectDraw Capabilities: overlay=1 yuvoverlay=1 can_deinterlace_overlay=1 colorkey=1 stretch=1 bltfourcc=1 vout_directx debug: End DirectXInitDDraw vout_directx debug: DirectXCreateDisplay vout_directx debug: DirectXCreateClipper vout_directx debug: disabling screen saver main debug: using video output module "vout_directx" main debug: TIMER module_Need() : 154.000 ms - Total 154.000 ms / 1 intvls (Avg 154.000 ms) main debug: waiting for thread initialization main debug: thread started vout_directx debug: NewPictureVec overlay:yes chroma:YV12 qt4 debug: Updating the geometry vout_directx debug: YUV overlay created successfully vout_directx debug: End NewPictureVec (succeeded) main debug: got 1 direct buffer(s) main debug: picture in 352x288 (0,0,352x288), chroma RV24, ar 4:3, sar 12:11 main debug: picture user 352x288 (0,0,352x288), chroma RV24, ar 4:3, sar 12:11 main debug: picture out 352x288 (0,0,352x288), chroma I420, ar 4:3, sar 12:11 main debug: looking for video filter2 module: 19 candidates swscale debug: 352x288 chroma: RV24 -> 352x288 chroma: I420 with scaling using Bicubic (good quality) main debug: using video filter2 module "swscale" main debug: TIMER module_Need() : 2.000 ms - Total 2.000 ms / 1 intvls (Avg 2.000 ms) main debug: indirect render, mapping render pictures 0-7 to system pictures 1-8 main debug: thread 6236 (video output) created at priority 1 (video_output/video_output.c:502) main warning: late picture skipped (32000) main debug: looking for text renderer module: 2 candidates main debug: thread 6040 (fontlist builder) created at priority 0 (freetype.c:477) freetype debug: using fontsize: 18 main debug: using text renderer module "freetype" main debug: TIMER module_Need() : 2.000 ms - Total 2.000 ms / 1 intvls (Avg 2.000 ms) main debug: thread started freetype debug: using fontsize: 18 freetype debug: Building font database... freetype debug: Finished building font database. freetype debug: Took 0 seconds main debug: thread ended main debug: looking for video blending module: 1 candidate blend debug: chroma: YUVA -> I420 main debug: using video blending module "blend" main debug: TIMER module_Need() : 0.000 ms - Total 0.000 ms / 1 intvls (Avg 0.000 ms) qt4 debug: New Event: type 1109
I decided to put the message thing in here to show what's going on..

Something weird I did find out tho, if I use the clone feature in the Extended interface or anything that puts a overlay on it, the colors come out fine?

edit:Here is the settings I use that get it to atleast output, then I do the clone with 1 and it comes up fine,

Code: Select all

:dshow-caching=200 :dshow-vdev="" :dshow-adev="" :dshow-size="width:640 height:480" :dshow-chroma="RV24" :dshow-fps=30 :no-dshow-config :no-dshow-tuner :dshow-tuner-channel=0 :dshow-tuner-country=0 :dshow-tuner-input=0 :dshow-video-input=-1 :dshow-audio-input=-1 :dshow-video-output=-1 :dshow-audio-output=-1 :dshow-amtuner-mode=1 :dshow-audio-channels=0 :dshow-audio-samplerate=0 :dshow-audio-bitspersample=0
and this is what I get when I clone

Code: Select all

main debug: thread 6652 (suxor) created at priority 0 (video_output/video_output.c:1555) main debug: thread started main warning: kludge 601 destroyed while thread alive (VLC might crash) qt4 debug: New Event: type 1103 qt4 debug: New Event: type 1103 main debug: control type=17 main debug: removing module "rawvideo" main debug: thread ended main debug: thread times: real 0m3.703125s, kernel 0m0.046875s, user 0m0.015625s main debug: thread 5672 joined (input/decoder.c:248) main debug: killing decoder fourcc `RV24', 0 PES in FIFO main debug: removing module "swscale" vout_directx debug: DirectXCloseSurface vout_directx debug: DirectXCloseDisplay vout_directx debug: DirectXCloseDisplay clipper vout_directx debug: DirectXCloseDisplay display vout_directx debug: DirectXCloseDDraw main debug: thread ended main debug: thread times: real 0m3.656250s, kernel 0m0.062500s, user 0m0.015625s main debug: thread 5196 joined (video_output/video_output.c:536) vout_directx debug: DirectXEventThread terminating vout_directx debug: DirectXCloseWindow vout_directx debug: WinProc WM_DESTROY qt4 debug: Qt FS: Detaching Vout qt4 debug: Qt: Changing Fullscreen Mode main debug: removing module "qt4" main debug: thread ended qt4 debug: Video is not needed anymore qt4 debug: Updating the geometry main debug: thread times: real 0m3.734375s, kernel 0m0.000000s, user 0m0.000000s main debug: thread 6344 joined (directx.c:513) main debug: removing module "vout_directx" main debug: removing module "blend" main debug: thread times: real 0m0.000000s, kernel 0m0.000000s, user 0m0.000000s main debug: thread 6400 joined (freetype.c:511) main debug: removing module "freetype" main debug: control type=17 main debug: looking for decoder module: 33 candidates kate debug: kate: OpenDecoder main debug: using decoder module "rawvideo" main debug: TIMER module_Need() : 1.000 ms - Total 1.000 ms / 1 intvls (Avg 1.000 ms) main debug: thread 6108 (decoder) created at priority 0 (input/decoder.c:217) main debug: thread started main debug: no usable vout present, spawning one main debug: window size: 384x288 main debug: looking for video filter module: 1 candidate clone debug: spawning 1 clone(s) main debug: using video filter module "clone" main debug: TIMER module_Need() : 0.000 ms - Total 0.000 ms / 1 intvls (Avg 0.000 ms) main debug: waiting for thread initialization main debug: thread started clone debug: spawning the real video outputs main debug: window size: 384x288 main debug: looking for video output module: 6 candidates vout_directx debug: creating DirectXEventThread main debug: waiting for thread initialization main debug: thread started vout_directx debug: DirectXCreateWindow main debug: looking for vout window module: 2 candidates qt4 debug: waiting for interface... qt4 debug: requesting window... qt4 debug: Video was requested -1, -1 qt4 debug: New Event: type 1109 qt4 debug: Video is resizing to: 384 288 qt4 debug: Qt FS: Attaching Vout qt4 debug: Qt: Changing Fullscreen Mode main debug: using vout window module "qt4" main debug: TIMER module_Need() : 2.000 ms - Total 2.000 ms / 1 intvls (Avg 2.000 ms) qt4 debug: Updating the geometry vout_directx debug: created video sub-window main debug: thread 5744 (Vout Events Thread) created at priority 0 (directx.c:281) vout_directx debug: Vout EventThread running vout_directx debug: DirectXInitDDraw vout_directx debug: directx-device: vout_directx debug: DirectXEnumCallback: Primary Display Driver, display vout_directx debug: DirectXEnumCallback: Mobile Intel(R) 965 Express Chipset Family, \\.\DISPLAY1 vout_directx debug: selecting Mobile Intel(R) 965 Express Chipset Family, \\.\DISPLAY1 vout_directx debug: screen dimensions (0x0,1280x800) vout_directx debug: DirectDraw Capabilities: overlay=1 yuvoverlay=1 can_deinterlace_overlay=1 colorkey=1 stretch=1 bltfourcc=1 vout_directx debug: End DirectXInitDDraw vout_directx debug: DirectXCreateDisplay vout_directx debug: DirectXCreateClipper vout_directx debug: disabling screen saver main debug: using video output module "vout_directx" main debug: TIMER module_Need() : 64.000 ms - Total 64.000 ms / 1 intvls (Avg 64.000 ms) main debug: waiting for thread initialization main debug: thread started vout_directx debug: NewPictureVec overlay:yes chroma:YV12 vout_directx debug: YUV overlay created successfully vout_directx debug: End NewPictureVec (succeeded) main debug: got 1 direct buffer(s) main debug: picture in 352x288 (0,0,352x288), chroma RV24, ar 4:3, sar 12:11 main debug: picture user 352x288 (0,0,352x288), chroma RV24, ar 4:3, sar 12:11 main debug: picture out 352x288 (0,0,352x288), chroma I420, ar 4:3, sar 12:11 main debug: looking for video filter2 module: 19 candidates swscale debug: 352x288 chroma: RV24 -> 352x288 chroma: I420 with scaling using Bicubic (good quality) main debug: using video filter2 module "swscale" main debug: TIMER module_Need() : 1.000 ms - Total 1.000 ms / 1 intvls (Avg 1.000 ms) main debug: indirect render, mapping render pictures 0-7 to system pictures 1-8 main debug: thread 5988 (video output) created at priority 1 (video_output/video_output.c:502) main debug: got 8 direct buffer(s) main debug: picture in 352x288 (0,0,352x288), chroma RV24, ar 4:3, sar 12:11 main debug: picture user 352x288 (0,0,352x288), chroma RV24, ar 4:3, sar 12:11 main debug: picture out 352x288 (0,0,352x288), chroma RV24, ar 4:3, sar 12:11 main debug: looking for video filter2 module: 19 candidates swscale debug: 352x288 chroma: RV24 -> 352x288 chroma: RV24 with scaling using Bicubic (good quality) main debug: using video filter2 module "swscale" main debug: TIMER module_Need() : 0.000 ms - Total 0.000 ms / 1 intvls (Avg 0.000 ms) main debug: indirect render, mapping render pictures 0-7 to system pictures 8-15 main debug: thread 5760 (video output) created at priority 1 (video_output/video_output.c:502) main debug: looking for text renderer module: 2 candidates main debug: thread 6596 (fontlist builder) created at priority 0 (freetype.c:477) freetype debug: using fontsize: 18 main debug: using text renderer module "freetype" main debug: TIMER module_Need() : 2.000 ms - Total 2.000 ms / 1 intvls (Avg 2.000 ms) freetype debug: using fontsize: 18 main debug: looking for video blending module: 1 candidate blend debug: chroma: YUVA -> I420 main debug: using video blending module "blend" main debug: TIMER module_Need() : 0.000 ms - Total 0.000 ms / 1 intvls (Avg 0.000 ms) main debug: thread started freetype debug: Building font database... freetype debug: Finished building font database. freetype debug: Took 0 seconds main debug: thread ended qt4 debug: New Event: type 1109

Re: Dshow color is wrong

Posted: 20 Nov 2008 19:39
by VLC_help
Run without :dshow-chroma="RV24"

Re: Dshow color is wrong

Posted: 20 Nov 2008 19:48
by Zeek
If I run it with nothing we go back to what I started with funky colors lol......

Re: Dshow color is wrong

Posted: 21 Nov 2008 19:44
by VLC_help
It should display the available colorspaces when you run it without that option.

Re: Dshow color is wrong

Posted: 21 Nov 2008 22:41
by Zeek
Yes sorry, it said that IV20 and RV24 are the only two you can use. With the various scale sizes and frame rates.

Re: Dshow color is wrong

Posted: 22 Nov 2008 19:33
by VLC_help
And both ones give same wrong output? And if you use VLC snapshot, that snapshot also has bad colors?

Re: Dshow color is wrong

Posted: 22 Nov 2008 21:16
by Zeek
Yes that's how I got the picture is with vlc snapshot, and IV20 will not display anything, it will turn my camera on but nothing will come up. RV24 at least gets something to come up.

Re: Dshow color is wrong

Posted: 23 Nov 2008 19:17
by VLC_help
If the VLC snapshot feature gives wrong colors, it is most definitely colorspace issue. I just don't know how to fix that issue. You use latest drivers in your device?

Re: Dshow color is wrong

Posted: 23 Nov 2008 21:46
by Zeek
I'd have to check microsoft and see if I can get new drivers for my cam, I haven't gotten any new drivers for it since I got the thing, I'll snoop around and if I do find some I'll install em and see if I get any new results...


And hopefully not kill my web cam :S

Re: Dshow color is wrong

Posted: 14 Dec 2008 04:25
by newgel
I can confirm this bug. Using VLC 0.9.8a on Windows XP. When I stream my Webcam I get wrong colors, like blue instead of red. VLC sees my cam as USB PC Camera (ZS0211).
Have you found a solution/workaround for this?

Re: Dshow color is wrong

Posted: 14 Dec 2008 04:31
by Zeek
yea sorry for not updating u guys on this issue, I got my latest drivers and still no go, only way I have been able to get the correct colors is by cloning the video in the extended GUI, but as far as I know if you stream your cam it will get the regular discolored video.

Re: Dshow color is wrong

Posted: 14 Dec 2008 17:53
by VLC_help
I will buy webcam this x-mas so I can check some Dshow related errors. You can test nightlies if they do something differently.
http://nightlies.videolan.org/build/win32/?C=M;O=D

Re: Dshow color is wrong

Posted: 04 Mar 2009 19:24
by sle118
I have the same issue with a Microsoft LifeCam camera. Looking at the picture locally, the chroma is fine. However, trying to stream to WMV sends the wrong chroma across the network.

I wonder if this could be related to ticket #2546 which has the following description:

Code: Select all

TitleWrong chroma conversion from RV24 to I420 (swscale) Description Opening a directshow device with RV24 chroma (select it from dshow panel with :dshow-config) opens a video with scrabled colors. I suspect the GetPixels? method @ modules/video_filter/swscale.c not taking into account
The LifeCam only supports RV24 at higher resolutions.

Is it possible to disable swscale somehow? Otherwise, is there a different work-around?

Re: Dshow color is wrong

Posted: 05 Mar 2009 16:34
by VLC_help
Is it possible to disable swscale somehow? Otherwise, is there a different work-around?
if you compile your own VLC, you can disable swscale.
All times are UTC+01:00
Page 1 of 1
Powered by phpBB® Forum Software © phpBB Limited
https://www.phpbb.com/