Log in or register to post comments

Samasung Galaxy Grand (I9082) camera preview black

March 4, 2013 - 4:37am #1

when i run imagetarget sample on Samasung Galaxy Grand (I9082) camera preview remains black,but it detects markers.
what is possible solution plz suggest.

Samasung Galaxy Grand (I9082) camera preview black

March 21, 2013 - 6:02am #32

Thanks for the additional precisation about Cloud Reco.

Samasung Galaxy Grand (I9082) camera preview black

March 21, 2013 - 5:22am #31

AlessandroB wrote:

@ yogendra and ALL interested in i9082 black background issue:

The issue has been identified in the incorrect location of the following lines of code in the _renderFrame() function:

#ifdef USE_OPENGL_ES_1_1        
    glDisable(GL_TEXTURE_2D);
    glDisableClientState(GL_VERTEX_ARRAY);
    glDisableClientState(GL_NORMAL_ARRAY);
    glDisableClientState(GL_TEXTURE_COORD_ARRAY);
#else
    glDisableVertexAttribArray(vertexHandle);
    glDisableVertexAttribArray(normalHandle);
    glDisableVertexAttribArray(textureCoordHandle);
#endif

Currently those lines are located AFTER the "for loop" (near the end of the renderFrame function) and on some devices produce a GL error;

the solution is to move those lines inside the "for loop", immediatly after the glDrawElements() call.

That should solve it (as we verified with our I9082)

 

 

thank you soooo much...

for those who are facing this in cloud reco sample.

move these lines :

 

glDisable(GL_DEPTH_TEST);
glDisableVertexAttribArray(vertexHandle);
glDisableVertexAttribArray(normalHandle);
glDisableVertexAttribArray(textureCoordHandle);
 
 

to just below this line  renderAugmentation(trackableResult);  in renderframe()    

 

 

Samasung Galaxy Grand (I9082) camera preview black

March 21, 2013 - 3:35am #30

@ yogendra and ALL interested in i9082 black background issue:

The issue has been identified in the incorrect location of the following lines of code in the _renderFrame() function:

#ifdef USE_OPENGL_ES_1_1        
    glDisable(GL_TEXTURE_2D);
    glDisableClientState(GL_VERTEX_ARRAY);
    glDisableClientState(GL_NORMAL_ARRAY);
    glDisableClientState(GL_TEXTURE_COORD_ARRAY);
#else
    glDisableVertexAttribArray(vertexHandle);
    glDisableVertexAttribArray(normalHandle);
    glDisableVertexAttribArray(textureCoordHandle);
#endif

Currently those lines are located AFTER the "for loop" (near the end of the renderFrame function) and on some devices produce a GL error;

the solution is to move those lines inside the "for loop", immediatly after the glDrawElements() call.

That should solve it (as we verified with our I9082)

 

Samasung Galaxy Grand (I9082) camera preview black

March 20, 2013 - 9:15am #29

Hi, thanks for sharing this info;

concerning your observation:

Removing the mUILayout is not a sloution, as this is the layout that actually holds the GLSurfaceview, on which the graphics are drawn.

 

this is not true, since the GLSurfaceView is added in this code:
 
addContentView(mGlView, new LayoutParams(LayoutParams.MATCH_PARENT,
                        LayoutParams.MATCH_PARENT));

 

and it is not a sub-view of mUILayout.
 
Actually, removing mUILayout may not solve the problem, but it would be something to try out.
 

Samasung Galaxy Grand (I9082) camera preview black

March 20, 2013 - 7:45am #28

I am seeing a very similar (if not the same) issue on both the HTC OneX and Sony LT26i (android 4.0.4, api-15) and on the LG Nexus4 (android 4.2, api-17):
The background remains black. while tracking and foreground rendering works perfectly. (Well i'm using some quite bad trackables, but both the names and the modelviewprojection-matrices are fine if i nurse the position of the images a little). I am rendering a textured sprite on top of the target. My app is based upon the ImageTargets example and the native code uses Vuforia 2.0.31 (2.0.30 has the same issue)

Using a Samsung Galaxy Nexus phone, the camera background works fine (android 4.2.1, api-17)  - and two days ago with api-16 before i upgraded it, although the code was slightly different then...

I'm getting some irregularities in the logcat with the Nexus4 when i start and stop the camera:

 

03-20 14:58:09.373: I/QCAR(17282): Java_dk_unibrew_booster_scan_ScanFragment_startCamera
03-20 14:58:09.381: I/AwesomePlayer(4056): setDataSource_l(URL suppressed)
03-20 14:58:09.443: I/AwesomePlayer(4056): setDataSource_l(URL suppressed)
03-20 14:58:09.474: I/CameraClient(4056): Opening camera 0
03-20 14:58:09.474: I/CameraHAL(4056): camera_device open
03-20 14:58:09.716: I/QCAR(17282): Configure Video Background : Video (640,480), Screen (720,1184), mSize (888,1184)
03-20 14:58:09.943: D/DOMX(4056): ERROR: failed check:(eError == OMX_ErrorNone) || (eError == OMX_ErrorNoMore) - returning error: 0x80001005 - Error returned from OMX API in ducati
03-20 14:58:09.943: E/CameraHAL(4056): Error while configuring rotation 0x80001005
03-20 14:58:10.068: D/DOMX(4056): ERROR: failed check:(eError == OMX_ErrorNone) || (eError == OMX_ErrorNoMore) - returning error: 0x80001005 - Error returned from OMX API in ducati
03-20 14:58:10.068: E/CameraHAL(4056): Error while configuring rotation 0x80001005
 
03-20 14:58:48.756: I/QCAR(17282): Java_dk_unibrew_booster_scan_ScanFragment_stopCamera
03-20 14:58:48.756: E/CameraHAL(4056): Adapter state switch PREVIEW_ACTIVE Invalid Op! event = 0xf
 
BTW:
Removing the mUILayout is not a sloution, as this is the layout that actually holds the GLSurfaceview, on which the graphics are drawn.
 
I really hope we can fine the issue.
Cheers
Christian

Samasung Galaxy Grand (I9082) camera preview black

March 18, 2013 - 3:33pm #27

Hi, thanks for the info;

actually, one hypothesis is that the UI layout (overlay layout) used in ImageTargets and CR samples may be responsible for the issue on that device;

could you do the following:

open ImageTargets.java, find all occurrences of a variable called mUILayout;

just remove (or comment out) the lines of code that refers to mUILayout (so, essentially, remove any sage of such variable in the code);

then run again and see if it makes any difference...

 

Samasung Galaxy Grand (I9082) camera preview black

March 18, 2013 - 3:54am #26

adding one more thing:

after few seconds of run following error comes in this device only in cloudreco sample.

 

03-18 16:16:56.222: E/SurfaceTextureClient(6126): dequeueBuffer failed (Out of memory)
03-18 16:16:56.222: E/ViewRootImpl(6126): OutOfResourcesException locking surface
03-18 16:16:56.222: E/ViewRootImpl(6126): android.view.Surface$OutOfResourcesException
03-18 16:16:56.222: E/ViewRootImpl(6126): at android.view.Surface.lockCanvasNative(Native Method)
03-18 16:16:56.222: E/ViewRootImpl(6126): at android.view.Surface.lockCanvas(Surface.java:88)
03-18 16:16:56.222: E/ViewRootImpl(6126): at android.view.ViewRootImpl.drawSoftware(ViewRootImpl.java:2341)
03-18 16:16:56.222: E/ViewRootImpl(6126): at android.view.ViewRootImpl.draw(ViewRootImpl.java:2304)
03-18 16:16:56.222: E/ViewRootImpl(6126): at android.view.ViewRootImpl.performDraw(ViewRootImpl.java:2172)
03-18 16:16:56.222: E/ViewRootImpl(6126): at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:1983)
03-18 16:16:56.222: E/ViewRootImpl(6126): at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:1135)
03-18 16:16:56.222: E/ViewRootImpl(6126): at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:4579)
03-18 16:16:56.222: E/ViewRootImpl(6126): at android.view.Choreographer$CallbackRecord.run(Choreographer.java:725)
03-18 16:16:56.222: E/ViewRootImpl(6126): at android.view.Choreographer.doCallbacks(Choreographer.java:555)
03-18 16:16:56.222: E/ViewRootImpl(6126): at android.view.Choreographer.doFrame(Choreographer.java:525)
03-18 16:16:56.222: E/ViewRootImpl(6126): at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:711)
03-18 16:16:56.222: E/ViewRootImpl(6126): at android.os.Handler.handleCallback(Handler.java:615)
03-18 16:16:56.222: E/ViewRootImpl(6126): at android.os.Handler.dispatchMessage(Handler.java:92)
03-18 16:16:56.222: E/ViewRootImpl(6126): at android.os.Looper.loop(Looper.java:137)
03-18 16:16:56.222: E/ViewRootImpl(6126): at android.app.ActivityThread.main(ActivityThread.java:4935)
03-18 16:16:56.222: E/ViewRootImpl(6126): at java.lang.reflect.Method.invokeNative(Native Method)
03-18 16:16:56.222: E/ViewRootImpl(6126): at java.lang.reflect.Method.invoke(Method.java:511)
03-18 16:16:56.222: E/ViewRootImpl(6126): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1038)
03-18 16:16:56.222: E/ViewRootImpl(6126): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:805)
03-18 16:16:56.222: E/ViewRootImpl(6126): at dalvik.system.NativeStart.main(Native Method)
 

please look into this.

Samasung Galaxy Grand (I9082) camera preview black

March 18, 2013 - 3:34am #25

AlessandroB wrote:

ok, could you change it to LANDSCAPE (just to exclude that issue) ?

 

sorry to say but black in LANDSCAPE also

Samasung Galaxy Grand (I9082) camera preview black

March 18, 2013 - 3:23am #24

ok, could you change it to LANDSCAPE (just to exclude that issue) ?

Samasung Galaxy Grand (I9082) camera preview black

March 18, 2013 - 3:19am #23

i already using:

 int screenOrientation = ActivityInfo.SCREEN_ORIENTATION_PORTRAIT;

 

 

Samasung Galaxy Grand (I9082) camera preview black

March 18, 2013 - 3:04am #22

Thanks yogendra for the test; 

actually, CloudReco and ImageTargets have a few commonalities that might indicate where the issue is; 

may I ask you to go to ImageTargets.java and in the initApplication() function replace this line:

 

int screenOrientation = ActivityInfo.SCREEN_ORIENTATION_SENSOR;
 
with this line:
 
int screenOrientation = ActivityInfo.SCREEN_ORIENTATION_LANDSCAPE;
 

And then run ImageTargets again; does it make any difference on your device ?

 

Samasung Galaxy Grand (I9082) camera preview black

March 18, 2013 - 3:01am #21

AlessandroB wrote:

@ yogendra (and to anyone interested in the Samsung I9082 device issue),

we have done some testing and we were able to reproduce the problem in ImageTargets, but not in other samples;

it would be nice if you could mae the same kind of test, so to have a confirmation from your device too, i.e. run a few more samples from the Vuforia SDK and tell us which one shows the black camera issue and which ones don't.

 

i tried imagetarget,videoplayback and cloudreco samples.

 

Bad News:

camera frame black in  imagetarget and cloudreco samples.

 

good news:

camera working fine in videoplayback sample

 

any idea what is going on?

Samasung Galaxy Grand (I9082) camera preview black

March 18, 2013 - 1:42am #20

I don't know if it is related, but I have tried on my LG Nexus 4 the Image Targets and User Defined Targets examples this far and I have the black screen. Just building an empty project with only the ARCamera prefab in it gives a black screen.

However, if I hold pressed the power button and the switch off menu appears, I get the Camera image rendered correctly in the back.

 

 

 

 

Samasung Galaxy Grand (I9082) camera preview black

March 18, 2013 - 1:26am #19

@ yogendra (and to anyone interested in the Samsung I9082 device issue),

we have done some testing and we were able to reproduce the problem in ImageTargets, but not in other samples;

it would be nice if you could mae the same kind of test, so to have a confirmation from your device too, i.e. run a few more samples from the Vuforia SDK and tell us which one shows the black camera issue and which ones don't.

Samasung Galaxy Grand (I9082) camera preview black

March 13, 2013 - 1:21am #18

I would like to report a very similar issue. 

I am using a Nexus 4 as device, with Android 4.2.2, Unity 4 and Vuforia 2.0.31.

In order to clarify a bit more the problem, here is the description: when I run my application I get a black screen after the splash screen. I can not see the Camera view on my app. However, everything works. When I find a trackable, the hidden objects show. In my app, OnTrackingFound() launches a small animation of a car moving and entering the scene. After 5sec it stops and a menu is shown. This menu uses NGUI. The depth value of the NGUI Camera is put to be rendered on top, but what I get is my menu masked by the objects.

This is what I see in my app with Nexus 4:

 

This is what should be seen (and is seen in a Samsung Galaxy SII or any other device I have tryed):

In addition to this, when I use the Dalvik Debug Monitor to capture screen shots, I get the correct image in all devices. Same, when I tap the "menu" key or hold the "switch on/off" hardware button and let the switch off menu be shown, I can see the camera view working correctly.

I copy here a piece of the log that may be useful:

03-12 19:13:09.606: D/QCAR(665): cameraDeviceInitCamera
03-12 19:13:09.606: I/AwesomePlayer(161): setDataSource_l(URL suppressed)
03-12 19:13:09.616: D/overlay(158): Set pipe=VG0 dpy=0; 
03-12 19:13:09.656: I/AwesomePlayer(161): setDataSource_l(URL suppressed)
03-12 19:13:09.726: I/CameraClient(161): Opening camera 0
03-12 19:13:09.776: E/qcom_sensors_hal(531): hal_process_report_ind: Bad item quality: 11 
03-12 19:13:09.806: E/mm-camera(222): sensor_load_chromatix: libchromatix_imx111_preview.so: 30
03-12 19:13:09.876: D/overlay(158): Unset pipe=VG0 dpy=0; 
03-12 19:13:09.916: E/mm-camera(222): vfe_ops_init: E
03-12 19:13:09.926: E/mm-camera(222): vfe_legacy_stats_buffer_init: AEC_STATS_BUFNUM
03-12 19:13:09.926: E/mm-camera(222): vfe_legacy_stats_buffer_init: AEC_STATS_BUFNUM
03-12 19:13:09.926: E/mm-camera(222): mctl_init_stats_proc_info: snap_max_line_cnt =30096
03-12 19:13:09.986: D/QCAR(665): cameraDeviceGetVideoMode
03-12 19:13:09.986: D/QCAR(665): cameraDeviceSelectVideoMode
03-12 19:13:10.036: D/dalvikvm(665): GC_CONCURRENT freed 428K, 10% free 9775K/10752K, paused 5ms+3ms, total 24ms
03-12 19:13:10.056: D/QCAR(665): cameraDeviceStartCamera
03-12 19:13:10.076: D/dalvikvm(665): GC_FOR_ALLOC freed 181K, 10% free 9774K/10752K, paused 18ms, total 18ms
03-12 19:13:10.076: I/dalvikvm-heap(665): Grow heap (frag case) to 10.126MB for 580112-byte allocation
03-12 19:13:10.106: D/dalvikvm(665): GC_FOR_ALLOC freed 566K, 14% free 9774K/11320K, paused 24ms, total 24ms
03-12 19:13:10.136: D/dalvikvm(665): GC_CONCURRENT freed 2K, 14% free 9774K/11320K, paused 4ms+2ms, total 29ms
03-12 19:13:10.136: D/dalvikvm(665): WAIT_FOR_CONCURRENT_GC blocked 26ms
03-12 19:13:10.136: I/dalvikvm-heap(665): Grow heap (frag case) to 10.127MB for 580112-byte allocation
03-12 19:13:10.146: D/dalvikvm(665): GC_FOR_ALLOC freed <1K, 9% free 10341K/11320K, paused 15ms, total 15ms
03-12 19:13:10.176: D/dalvikvm(665): GC_EXPLICIT freed 1K, 9% free 10342K/11320K, paused 1ms+2ms, total 26ms
03-12 19:13:10.176: E/QCameraHWI(161): android::status_t android::QCameraHardwareInterface::setPreviewWindow(preview_stream_ops_t*): mPreviewWindow = 0x0x410f9b60, mStreamDisplay = 0x0x400b76c8
03-12 19:13:10.176: D/QCameraHWI(161): android::status_t android::QCameraHardwareInterface::startPreview():  start preview now
03-12 19:13:10.176: I/QCameraHWI(161): android::status_t android::QCameraHardwareInterface::startPreview2():Setting ZSL mode
03-12 19:13:10.176: E/mm-camera(222): config_proc_CAMERA_SET_INFORM_STARTPREVIEW
03-12 19:13:10.176: E/mm-camera(222): config_update_stream_info Storing stream parameters for video inst 1 as : width = 800, height 480, format = 1 inst_handle = 810081 cid = 0
03-12 19:13:10.186: E/mm-camera(222): config_update_stream_info Storing stream parameters for video inst 3 as : width = 640, height 480, format = 1 inst_handle = 830083 cid = 0
03-12 19:13:10.186: E/mm-camera(222): config_update_stream_info Storing stream parameters for video inst 4 as : width = 512, height 384, format = 1 inst_handle = 840084 cid = 0
03-12 19:13:10.196: E/mm-camera(222): config_decide_vfe_outputs: Ports Used 3, Op mode 1
03-12 19:13:10.196: E/mm-camera(222): config_decide_vfe_outputs Current mode 0 Full size streaming : Disabled
03-12 19:13:10.196: E/mm-camera(222): config_decide_vfe_outputs: Primary: 800x480, extra_pad: 0x0, Fmt: 1, Type: 1, Path: 1
03-12 19:13:10.196: E/mm-camera(222): config_decide_vfe_outputs: Secondary: 640x480, extra_pad: 0x0, Fmt: 1, Type: 3, Path: 4
03-12 19:13:10.196: E/mm-camera(222): config_update_inst_handles Updated the inst handles as 810081, 830083, 0, 0 
03-12 19:13:10.337: E/mm-camera(222): sensor_load_chromatix: libchromatix_imx111_zsl.so: 26
03-12 19:13:10.427: E/mm-camera(222): camif_client_set_params: camif has associated with obj mask 0x1
03-12 19:13:10.427: E/mm-camera(222): config_v2_CAMERA_START_common CAMIF_PARAMS_ADD_OBJ_ID failed -1 
03-12 19:13:10.427: E/mm-camera(222): vfe_operation_config: format 3
03-12 19:13:10.427: E/mm-camera(222): vfe_operation_config:vfe_op_mode=5
03-12 19:13:10.427: E/mm-camera(222): Invalid ASD Set Params Type
03-12 19:13:10.427: E/mm-camera(222): vfe_set_bestshot: Bestshot mode not changed
03-12 19:13:10.457: D/QCAR(665): markerTrackerStart
03-12 19:13:10.457: D/QCAR(665): imageTrackerStart
03-12 19:13:10.457: D/QCAR(665): cameraDeviceGetVideoMode
03-12 19:13:10.487: E/mm-libcamera2(161): PROFILE HAL: First preview frame received: 1363111990.499583509
03-12 19:13:10.487: E/BufferQueue(665): [unnamed-665-7] dequeueBuffer: min undequeued buffer count (2) exceeded (dequeued=6 undequeudCount=0)
03-12 19:13:10.577: E/BufferQueue(665): [unnamed-665-7] dequeueBuffer: min undequeued buffer count (2) exceeded (dequeued=5 undequeudCount=1)
03-12 19:13:10.647: I/Unity(665): Num trackables detected: 1
03-12 19:13:10.647: I/Unity(665):  
03-12 19:13:10.647: I/Unity(665): (Filename: ./Runtime/ExportGenerated/AndroidManaged/UnityEngineDebug.cpp Line: 43)
03-12 19:13:10.647: I/Unity(665): Trackable target_1 found
03-12 19:13:10.647: I/Unity(665):  
03-12 19:13:10.647: I/Unity(665): (Filename: ./Runtime/ExportGenerated/AndroidManaged/UnityEngineDebug.cpp Line: 43)

Thank you for your help

Samasung Galaxy Grand (I9082) camera preview black

March 12, 2013 - 12:17pm #17

Maybe a good idea.

Samasung Galaxy Grand (I9082) camera preview black

March 12, 2013 - 11:46am #16

Thank you for your quick reply, should I copy my issue in this other thread?

Samasung Galaxy Grand (I9082) camera preview black

March 12, 2013 - 11:36am #15

@ haitzika,

thanks for the report: this is similar (or same) issue reported in this thread:

https://developer.vuforia.com/forum/unity-3-extension-technical-discussion/android-422-no-camera-display

You may want to follow the progress there as well (currently under investigation).

 

 

 

Samasung Galaxy Grand (I9082) camera preview black

March 8, 2013 - 12:22am #14

We are still looking at it, but it may take some time.

Samasung Galaxy Grand (I9082) camera preview black

March 7, 2013 - 10:02pm #13

AlessandroB wrote:

Thanks, I will use that info and let you know.

 

any solution? it's giving me headache...:(

Samasung Galaxy Grand (I9082) camera preview black

March 6, 2013 - 11:27am #12

Thanks, I will use that info and let you know.

Samasung Galaxy Grand (I9082) camera preview black

March 5, 2013 - 8:43pm #11

AlessandroB wrote:

Hi, I would still need one piece of information, i.e. what CPU is your device equipped with:

in order to get this information from your device, you can do this:

  • open the cygwin console and type:
    • adb -d shell
  • this will open a shell on your device
  • then type the following:
    • cat  /proc/cpuinfo

The shell will display some info, could you then copy-paste it here ?

 

 

cpu information:

 

 

Processor       : ARMv7 Processor rev 0 (v7l)
processor       : 0
BogoMIPS        : 624.06
 
processor       : 1
BogoMIPS        : 624.06
 
Features        : swp half thumb fastmult vfp edsp thumbee neon vfpv3
CPU implementer : 0x41
CPU architecture: 7
CPU variant     : 0x3
CPU part        : 0xc09
CPU revision    : 0
 
Hardware        : CAPRI_SS_BAFFIN
Revision        : 0005
Serial          : d7e2cf004100af11
 
 

Samasung Galaxy Grand (I9082) camera preview black

March 5, 2013 - 9:51am #10

Hi, I would still need one piece of information, i.e. what CPU is your device equipped with:

in order to get this information from your device, you can do this:

  • open the cygwin console and type:
    • adb -d shell
  • this will open a shell on your device
  • then type the following:
    • cat  /proc/cpuinfo

The shell will display some info, could you then copy-paste it here ?

 

Samasung Galaxy Grand (I9082) camera preview black

March 4, 2013 - 5:57am #9

AlessandroB wrote:

BTW: could you check your logs and see if you get any error message that might help us investigate the issue ?

 

 

 

 i checked logs but there is no error regarding any camera issue.

 

i am using latest version of vuforia. 

Samasung Galaxy Grand (I9082) camera preview black

March 4, 2013 - 5:50am #8

BTW: could you check your logs and see if you get any error message that might help us investigate the issue ?

 

Also (and most importantly): what version of Vuforia are you using ?

 

Samasung Galaxy Grand (I9082) camera preview black

March 4, 2013 - 5:47am #7

AlessandroB wrote:

Ok, thanks for the model details; I will investigate the issue and report back as soon as I have some findings.

 

 

since it's one of the popular phone currently ,it's very critical .

Samasung Galaxy Grand (I9082) camera preview black

March 4, 2013 - 5:38am #6

Ok, thanks for the model details; I will investigate the issue and report back as soon as I have some findings.

Samasung Galaxy Grand (I9082) camera preview black

March 4, 2013 - 5:29am #5

AlessandroB wrote:

I see. Can you post the full details of that device (please check the device Settings), including model number and Android version please ?

 

 

model : Samasung Galaxy Grand (I9082)

 

android version: Android OS, v4.1.2 (Jelly Bean)

 

 

plz help me out...:(

Samasung Galaxy Grand (I9082) camera preview black

March 4, 2013 - 5:24am #4

I see. Can you post the full details of that device (please check the device Settings), including model number and Android version please ?

 

Samasung Galaxy Grand (I9082) camera preview black

March 4, 2013 - 5:13am #3

yes ...other views are there but camera  preview is completely black.

 

and this is the only samsung device behaving like this...i don't know what to do?

Samasung Galaxy Grand (I9082) camera preview black

March 4, 2013 - 5:07am #2

Hi, just to make sure I correctly understand: 

do you see the 3D teapot models (which prooves the markers are detected and tracked) on top of a black background (i.e. no video background behind ) ?

 

 

Log in or register to post comments