Menu
Home
Forums
New posts
Search forums
What's new
Featured content
New posts
New media
New media comments
New resources
Latest activity
Media
New media
New comments
Search media
Resources
Latest reviews
Search resources
Nyuuz
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Menu
Log in
Register
Install the app
Install
Home
Forums
Labrish
Nalij
Jinaral kantent
OBS can miss MidiStickers widgets on your screen
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
[QUOTE="Bombastus, post: 91441, member: 2178"] MidiStickers’ Overlay Mode places its widgets over other applications, while OBS Window Capture records the contents of one selected window. Your desktop can show a piano and staff that never appear in the recording. The selected window may still be captured perfectly. When you demonstrate [B][URL='https://goldmidi.com/community/threads/midistickers-pro-has-added-lessons-and-sight-reading-tools.76838/']MidiStickers’ sight-reading practice tools[/URL][/B], the changing notes need to reach the student's screen. Check the captured picture while playing a few notes, because a correctly framed music application doesn't prove the teaching widgets are included. [HEADING=2]The capture must include MidiStickers itself[/HEADING] Open the properties of the capture source in OBS and check which window it targets. A source pointed at your digital audio workstation, or DAW, captures that window's contents. MidiStickers sitting above it doesn't become part of the DAW. For a lesson that needs both applications as arranged on your desktop, use Display Capture on Windows and select the monitor containing them. On a Mac, use macOS Screen Capture and select the whole display containing the lesson. Mac application capture offers a narrower option, collecting visible windows belonging to a chosen application. Selecting only the DAW still excludes MidiStickers, which runs separately. Use that distinction when deciding whether you need the desktop arrangement or just one application's windows. If the lesson needs only MidiStickers, its Focus Mode puts the app inside a window that fills the screen. Try capturing that window directly, then play notes and confirm that every required widget appears before adjusting the picture further. [HEADING=2]A tight crop can cut off the lesson[/HEADING] Once the widgets appear, crop the capture to the teaching area using Edit Transform in OBS. You can also hold Alt on Windows or Option on Mac while dragging its edges. Leave room for the full staff and keyboard you intend to show. For a second lesson scene, add the existing display source again. Give each scene its own crop through Edit Transform. You can keep one view on the keyboard and another wide enough to include notation. A Crop/Pad filter instead changes the underlying source wherever you use it. If tightening the keyboard view cuts the staff off another scene, remove that shared filter and crop through each scene's transform. A display crop keeps a fixed area of the captured image, so moving a widget beyond that area removes it from view. Save the arrangement as a MidiStickers layout, then lock it to prevent accidental changes to widget placement and settings. OBS saves scenes and sources in a Scene Collection, while MidiStickers saves its own widget arrangement separately. Reopening the right OBS collection won't restore a MidiStickers widget you've moved elsewhere on the desktop. If the source contains the widgets but the finished scene hides them, inspect the Sources list. Items higher in that list can cover items below, so an old DAW capture may obscure your newly added display capture. Use the eye icons to hide competing sources while checking which image contains the lesson. [HEADING=2]The virtual camera can send a different picture[/HEADING] Your widgets can appear in OBS yet be absent from the call because the virtual camera is sending a single source. Open its settings using the gear beside the virtual camera control and inspect the output choice. Source sends only the selected source, which might be your webcam or the original DAW capture. Scene sends one chosen scene regardless of the main output. For a fixed teaching view, select the scene containing the captured notes and any camera image you want alongside them. Program sends OBS's normal output and suits a lesson where you deliberately switch between several prepared scenes. A virtual camera fixed to a Scene will keep showing its chosen scene while those main-output changes happen elsewhere. In Studio Mode, the editable Preview and the live Program can show different scenes. If you've prepared the corrected lesson in Preview, use Transition to send it to Program. Merely selecting the scene for editing doesn't put that view into the normal output. Choosing Preview for the virtual camera exposes that editing view to the call, including the changes you make there. If OBS looks right but [B]your lesson video loses its overlays[/B], check which view the virtual camera actually sends. Start Virtual Camera in OBS and choose OBS Virtual Camera as the camera in the calling application. Play a short sequence and inspect the application's video preview for the changing notes. If your OBS Program looks right but the call doesn't, recheck both camera selections before rebuilding the capture. [/QUOTE]
Insert quotes…
Name
Post reply
Home
Forums
Labrish
Nalij
Jinaral kantent
OBS can miss MidiStickers widgets on your screen
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
Accept
Learn more…
Top