Capture the terminal on Ubuntu with OBS
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgO9GURib1T8z7lCwjOGLQaGtrueEthgQ8LO42ZX8cOfTqDK4jvDDpKkLFwf2J49kYCMNW7d4ABih_XCb_2UXdq5fPJDkoyg7-8g_YfRUot-XnaXkNYycsNp7lA5_TW9td0FFpLQ2APzKcZ/s1600/1.jpg)
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhYQ0N5W1qAOxLP7t7iOM6O6AzbZnkXUy16s7P_CWfOb5UbTQY_aDsc727chyphenhyphen5W4IppVNernMMQeaUFTB_rFzAd95_CDt-tnwN-nBx6JyUp2duGjPaL5-VgNO41AVsA_vu30EJcipdDG409/s400/Clash+Royale+CLAN+TAG%2523URR8PPP.png)
up vote
0
down vote
favorite
I'm attempting to capture the terminal on my Ubuntu 16.04 LTS computer with OBS 21.0.1, however when I select the terminal window using the "Window Capture (XComposite)" method, I just get a black screen. I can capture any other window fine with this method, and it seems to be a problem only with the terminal.
Any suggestions for fixing this, or will I have to move to another terminal emulator such as the PuTTY terminal emulator?
command-line desktop-recording obs-studio
add a comment |Â
up vote
0
down vote
favorite
I'm attempting to capture the terminal on my Ubuntu 16.04 LTS computer with OBS 21.0.1, however when I select the terminal window using the "Window Capture (XComposite)" method, I just get a black screen. I can capture any other window fine with this method, and it seems to be a problem only with the terminal.
Any suggestions for fixing this, or will I have to move to another terminal emulator such as the PuTTY terminal emulator?
command-line desktop-recording obs-studio
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm attempting to capture the terminal on my Ubuntu 16.04 LTS computer with OBS 21.0.1, however when I select the terminal window using the "Window Capture (XComposite)" method, I just get a black screen. I can capture any other window fine with this method, and it seems to be a problem only with the terminal.
Any suggestions for fixing this, or will I have to move to another terminal emulator such as the PuTTY terminal emulator?
command-line desktop-recording obs-studio
I'm attempting to capture the terminal on my Ubuntu 16.04 LTS computer with OBS 21.0.1, however when I select the terminal window using the "Window Capture (XComposite)" method, I just get a black screen. I can capture any other window fine with this method, and it seems to be a problem only with the terminal.
Any suggestions for fixing this, or will I have to move to another terminal emulator such as the PuTTY terminal emulator?
command-line desktop-recording obs-studio
command-line desktop-recording obs-studio
asked Mar 8 at 10:21
![](https://i.stack.imgur.com/zTUln.jpg?s=32&g=1)
![](https://i.stack.imgur.com/zTUln.jpg?s=32&g=1)
carefulnow1
1136
1136
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
0
down vote
A Solution
Avoid using terminal emulators with alpha channels (i.e. transparency support) such as those included in your distro. (In my case, it's the KDE Konsole.)
Instead, use a terminal without transparency support, such as XTerm or UXTerm, which should be included as part of any clean distro installation.
It may not look as nice at first or have the same feature set, but I can confirm that OBS is able to capture the source and display it correctly. (I confirmed this last night during a 4.5hr stream.)
To make it look nicer, you can press and hold Ctrl + R-Click to get the terminal's context menu and change font size, set it to use TrueType fonts, and so on. This definitely helps and is strongly recommended.
Problem Description
I ran into this issue yesterday and, after more searching, found out that this is a known bug in OBS, which was reported here back in Oct 31st, 2014 and last updated (to a closed status) on Nov. 26, 2016.
The issue is that OBS is not able to capture from a source that has an alpha channel. If you launch OBS from the terminal, you'll see the output below when you try to add a new Window Capture (XComposite) source to capture from a terminal. On my system a few minutes ago, the relevant output was:
info: User added source 'Terminal' (xcomposite_input) to scene 'Code - Mono'
info: xcompcap: [window-capture: 'Terminal'] update settings:
title: Desktop â Plasma
class: plasmashell
error: glCopyImageSubData failed, glGetError returned 0x502
error: device_copy_texture (GL) failed
error: glCopyImageSubData failed, glGetError returned 0x502
error: device_copy_texture (GL) failed
error: glCopyImageSubData failed, glGetError returned 0x502
error: device_copy_texture (GL) failed
error: glCopyImageSubData failed, glGetError returned 0x502
...
The terminal has an alpha channel, which is used for transparency, and this is what makes OBS flip out whenever you try to capture from that source.
As you can see from my terminal below (KDE Konsole: Settings â Edit Current Profile... â Appearance (tab) â Edit...), you can set the alpha channel (transparency) value to 0%, but you cannot really remove the channel to get a terminal without the alpha channel itself.
By the looks of it, it seems they have no way (or intention) to fix this bug, which is unfortunate either way.
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
A Solution
Avoid using terminal emulators with alpha channels (i.e. transparency support) such as those included in your distro. (In my case, it's the KDE Konsole.)
Instead, use a terminal without transparency support, such as XTerm or UXTerm, which should be included as part of any clean distro installation.
It may not look as nice at first or have the same feature set, but I can confirm that OBS is able to capture the source and display it correctly. (I confirmed this last night during a 4.5hr stream.)
To make it look nicer, you can press and hold Ctrl + R-Click to get the terminal's context menu and change font size, set it to use TrueType fonts, and so on. This definitely helps and is strongly recommended.
Problem Description
I ran into this issue yesterday and, after more searching, found out that this is a known bug in OBS, which was reported here back in Oct 31st, 2014 and last updated (to a closed status) on Nov. 26, 2016.
The issue is that OBS is not able to capture from a source that has an alpha channel. If you launch OBS from the terminal, you'll see the output below when you try to add a new Window Capture (XComposite) source to capture from a terminal. On my system a few minutes ago, the relevant output was:
info: User added source 'Terminal' (xcomposite_input) to scene 'Code - Mono'
info: xcompcap: [window-capture: 'Terminal'] update settings:
title: Desktop â Plasma
class: plasmashell
error: glCopyImageSubData failed, glGetError returned 0x502
error: device_copy_texture (GL) failed
error: glCopyImageSubData failed, glGetError returned 0x502
error: device_copy_texture (GL) failed
error: glCopyImageSubData failed, glGetError returned 0x502
error: device_copy_texture (GL) failed
error: glCopyImageSubData failed, glGetError returned 0x502
...
The terminal has an alpha channel, which is used for transparency, and this is what makes OBS flip out whenever you try to capture from that source.
As you can see from my terminal below (KDE Konsole: Settings â Edit Current Profile... â Appearance (tab) â Edit...), you can set the alpha channel (transparency) value to 0%, but you cannot really remove the channel to get a terminal without the alpha channel itself.
By the looks of it, it seems they have no way (or intention) to fix this bug, which is unfortunate either way.
add a comment |Â
up vote
0
down vote
A Solution
Avoid using terminal emulators with alpha channels (i.e. transparency support) such as those included in your distro. (In my case, it's the KDE Konsole.)
Instead, use a terminal without transparency support, such as XTerm or UXTerm, which should be included as part of any clean distro installation.
It may not look as nice at first or have the same feature set, but I can confirm that OBS is able to capture the source and display it correctly. (I confirmed this last night during a 4.5hr stream.)
To make it look nicer, you can press and hold Ctrl + R-Click to get the terminal's context menu and change font size, set it to use TrueType fonts, and so on. This definitely helps and is strongly recommended.
Problem Description
I ran into this issue yesterday and, after more searching, found out that this is a known bug in OBS, which was reported here back in Oct 31st, 2014 and last updated (to a closed status) on Nov. 26, 2016.
The issue is that OBS is not able to capture from a source that has an alpha channel. If you launch OBS from the terminal, you'll see the output below when you try to add a new Window Capture (XComposite) source to capture from a terminal. On my system a few minutes ago, the relevant output was:
info: User added source 'Terminal' (xcomposite_input) to scene 'Code - Mono'
info: xcompcap: [window-capture: 'Terminal'] update settings:
title: Desktop â Plasma
class: plasmashell
error: glCopyImageSubData failed, glGetError returned 0x502
error: device_copy_texture (GL) failed
error: glCopyImageSubData failed, glGetError returned 0x502
error: device_copy_texture (GL) failed
error: glCopyImageSubData failed, glGetError returned 0x502
error: device_copy_texture (GL) failed
error: glCopyImageSubData failed, glGetError returned 0x502
...
The terminal has an alpha channel, which is used for transparency, and this is what makes OBS flip out whenever you try to capture from that source.
As you can see from my terminal below (KDE Konsole: Settings â Edit Current Profile... â Appearance (tab) â Edit...), you can set the alpha channel (transparency) value to 0%, but you cannot really remove the channel to get a terminal without the alpha channel itself.
By the looks of it, it seems they have no way (or intention) to fix this bug, which is unfortunate either way.
add a comment |Â
up vote
0
down vote
up vote
0
down vote
A Solution
Avoid using terminal emulators with alpha channels (i.e. transparency support) such as those included in your distro. (In my case, it's the KDE Konsole.)
Instead, use a terminal without transparency support, such as XTerm or UXTerm, which should be included as part of any clean distro installation.
It may not look as nice at first or have the same feature set, but I can confirm that OBS is able to capture the source and display it correctly. (I confirmed this last night during a 4.5hr stream.)
To make it look nicer, you can press and hold Ctrl + R-Click to get the terminal's context menu and change font size, set it to use TrueType fonts, and so on. This definitely helps and is strongly recommended.
Problem Description
I ran into this issue yesterday and, after more searching, found out that this is a known bug in OBS, which was reported here back in Oct 31st, 2014 and last updated (to a closed status) on Nov. 26, 2016.
The issue is that OBS is not able to capture from a source that has an alpha channel. If you launch OBS from the terminal, you'll see the output below when you try to add a new Window Capture (XComposite) source to capture from a terminal. On my system a few minutes ago, the relevant output was:
info: User added source 'Terminal' (xcomposite_input) to scene 'Code - Mono'
info: xcompcap: [window-capture: 'Terminal'] update settings:
title: Desktop â Plasma
class: plasmashell
error: glCopyImageSubData failed, glGetError returned 0x502
error: device_copy_texture (GL) failed
error: glCopyImageSubData failed, glGetError returned 0x502
error: device_copy_texture (GL) failed
error: glCopyImageSubData failed, glGetError returned 0x502
error: device_copy_texture (GL) failed
error: glCopyImageSubData failed, glGetError returned 0x502
...
The terminal has an alpha channel, which is used for transparency, and this is what makes OBS flip out whenever you try to capture from that source.
As you can see from my terminal below (KDE Konsole: Settings â Edit Current Profile... â Appearance (tab) â Edit...), you can set the alpha channel (transparency) value to 0%, but you cannot really remove the channel to get a terminal without the alpha channel itself.
By the looks of it, it seems they have no way (or intention) to fix this bug, which is unfortunate either way.
A Solution
Avoid using terminal emulators with alpha channels (i.e. transparency support) such as those included in your distro. (In my case, it's the KDE Konsole.)
Instead, use a terminal without transparency support, such as XTerm or UXTerm, which should be included as part of any clean distro installation.
It may not look as nice at first or have the same feature set, but I can confirm that OBS is able to capture the source and display it correctly. (I confirmed this last night during a 4.5hr stream.)
To make it look nicer, you can press and hold Ctrl + R-Click to get the terminal's context menu and change font size, set it to use TrueType fonts, and so on. This definitely helps and is strongly recommended.
Problem Description
I ran into this issue yesterday and, after more searching, found out that this is a known bug in OBS, which was reported here back in Oct 31st, 2014 and last updated (to a closed status) on Nov. 26, 2016.
The issue is that OBS is not able to capture from a source that has an alpha channel. If you launch OBS from the terminal, you'll see the output below when you try to add a new Window Capture (XComposite) source to capture from a terminal. On my system a few minutes ago, the relevant output was:
info: User added source 'Terminal' (xcomposite_input) to scene 'Code - Mono'
info: xcompcap: [window-capture: 'Terminal'] update settings:
title: Desktop â Plasma
class: plasmashell
error: glCopyImageSubData failed, glGetError returned 0x502
error: device_copy_texture (GL) failed
error: glCopyImageSubData failed, glGetError returned 0x502
error: device_copy_texture (GL) failed
error: glCopyImageSubData failed, glGetError returned 0x502
error: device_copy_texture (GL) failed
error: glCopyImageSubData failed, glGetError returned 0x502
...
The terminal has an alpha channel, which is used for transparency, and this is what makes OBS flip out whenever you try to capture from that source.
As you can see from my terminal below (KDE Konsole: Settings â Edit Current Profile... â Appearance (tab) â Edit...), you can set the alpha channel (transparency) value to 0%, but you cannot really remove the channel to get a terminal without the alpha channel itself.
By the looks of it, it seems they have no way (or intention) to fix this bug, which is unfortunate either way.
edited Apr 2 at 18:23
answered Apr 1 at 22:12
![](https://i.stack.imgur.com/USV9e.jpg?s=32&g=1)
![](https://i.stack.imgur.com/USV9e.jpg?s=32&g=1)
code_dredd
5141413
5141413
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1013024%2fcapture-the-terminal-on-ubuntu-with-obs%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password