FoxKeegan
commented
3 years ago I've learned that using the crop/pad filter will also cause this problem, even if you're matching the resolution of the camera to the canvas size.
Closed FoxKeegan closed 3 years ago
FoxKeegan
commented
3 years ago I've learned that using the crop/pad filter will also cause this problem, even if you're matching the resolution of the camera to the canvas size.
Xaymar
commented
3 years ago For your interest, you should use the "Upload last log file" functionality in OBS Studio, instead of pasting it into the field. That's why it's a single line.
Xaymar
commented
3 years ago Failed to reproduce with the steps provided. I have tried with every virtual and physical Video Capture Device option, and none of them have this behavior. The only way to get this to happen is with Show/Hide transition set to Shader, which at the current time is not supported anyway. That would be a new feature request to support Show/Hide transitions for Shaders.
Xaymar
commented
3 years ago Closing in favor of #586.
Operating System
Windows 10 1903 and higher
OBS Studio Version?
27.0 (including Release Candidates)
StreamFX Version
0.10.1
Expected Behavior
When you attempt to show/hide the video input device, the image should simply cycle through the shader's transition effect, then vanish or appear, all while staying centered within the confines of the device's designated area on the OBS canvas. (Source border indicated by the blue/red resizable box)
Current Behavior
All of the expected behavior with one significant difference: just prior to the start of the transition effect, the image is scaled to the OBS "Base (Canvas) Resolution" proportional to any resizing the Source border has already had applied.
Steps to Reproduce the Bug
Example: If the canvas was 1920x1080 and the camera was set to 1080, no erroneous effects would be noticed. However, if--for example--said camera was switched to 720 in OBS, the next time it was made to be shown or hidden, the image would be scaled up from its current adjustments proportional to how large it would be at 1080, then the effect would take place. To better explain the last part: if the image was made to encompass the entire canvas at 1080, then switched to 720 and not manually resized/scaled in any fashion, if the transition were to take effect it would do so while the image was now encompassing the entire screen again, as it would have been scaled back up to 1080. If, however, the 720 image had been manually scaled down by 50%, when the device was hidden, the image would still scale up to 1080, becoming larger, but would now no longer encompass the entire screen--it would be proportionally smaller. (50%)
OBS Studio Log
Log
``` 14:23:40.482: CPU Name: Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz 14:23:40.482: CPU Speed: 3696MHz 14:23:40.482: Physical Cores: 6, Logical Cores: 12 14:23:40.482: Physical Memory: 49075MB Total, 31131MB Free 14:23:40.482: Windows Version: 10.0 Build 18363 (release: 1909; revision: 1440; 64-bit) 14:23:40.482: Running as administrator: true 14:23:40.482: Aero is Enabled (Aero is always on for windows 8 and above) 14:23:40.482: Windows 10 Gaming Features: 14:23:40.482: Game Bar: Off 14:23:40.482: Game DVR: Off 14:23:40.482: Game DVR Background Recording: Off 14:23:40.482: Game Mode: On 14:23:40.483: Sec. Software Status: 14:23:40.483: Windows Defender Antivirus: enabled (AV) 14:23:40.483: Windows Firewall: disabled (FW) 14:23:40.484: Current Date/Time: 2021-06-11, 14:23:40 14:23:40.484: Browser Hardware Acceleration: true 14:23:40.484: Portable mode: false 14:23:40.744: OBS 27.0.0-rc6 (64-bit, windows) 14:23:40.744: --------------------------------- 14:23:40.777: --------------------------------- 14:23:40.777: audio settings reset: 14:23:40.777: samples per sec: 48000 14:23:40.777: speakers: 2 14:23:40.777: --------------------------------- 14:23:40.777: Initializing D3D11... 14:23:40.777: Available Video Adapters: 14:23:40.779: Adapter 0: Radeon RX 590 Series 14:23:40.779: Dedicated VRAM: 4273823744 14:23:40.779: Shared VRAM: 4254928896 14:23:40.779: PCI ID: 1002:67df 14:23:40.779: Driver Version: 27.20.14501.18003 14:23:40.779: output 0: pos={0, 0}, size={1920, 1080}, attached=true, refresh=60, name=VW246 14:23:40.779: output 1: pos={0, -1080}, size={1920, 1080}, attached=true, refresh=60, name=VW246 14:23:40.779: output 2: pos={1920, 0}, size={1280, 1024}, attached=true, refresh=60, name=Rad-9 14:23:40.780: Loading up D3D11 on adapter Radeon RX 590 Series (0) 14:23:40.809: D3D11 loaded successfully, feature level used: b000 14:23:40.809: DXGI increase maximum frame latency success 14:23:40.809: D3D11 GPU priority setup success 14:23:41.167: --------------------------------- 14:23:41.167: video settings reset: 14:23:41.167: base resolution: 1920x1080 14:23:41.167: output resolution: 1920x1080 14:23:41.167: downscale filter: Bilinear 14:23:41.167: fps: 30/1 14:23:41.167: format: NV12 14:23:41.167: YUV mode: 709/Partial 14:23:41.167: NV12 texture support enabled 14:23:41.167: Audio monitoring device: 14:23:41.167: name: Out 1-2 (MOTU M Series) 14:23:41.167: id: {0.0.0.00000000}.{f2427f01-e4e0-4657-8a15-c3118b172702} 14:23:41.169: --------------------------------- 14:23:41.169: Skipping module '../../obs-plugins/64bit/chrome_elf.dll', not an OBS plugin 14:23:41.171: [CoreAudio encoder]: CoreAudio AAC encoder not installed on the system or couldn't be loaded 14:23:41.171: Failed to load 'en-US' text for module: 'decklink-captions.dll' 14:23:41.172: Failed to load 'en-US' text for module: 'decklink-ouput-ui.dll' 14:23:41.357: [AMF] Version 2.7.0 loaded (Compiled: 1.4.14.0, Runtime: 1.4.18.0, Library: 1;4;18;0;20.45.01.14;202011131446;CL#2201722). 14:23:41.388: [AMF]OBS Studio Crash Log
Any additional Information we need to know?
I can be contacted in the StreamFX Discord under "Fox" if you require additional information. Thank you.