You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Idea came up while discussing on OHBM 2021 TF slack in connection to #10 . It would be nice to compile materials and references which would assist speakers and participants to prepare and provide "high quality" content (e.g. pre-recorded talks). so here are some ideas on "sub-components"
QA toolkit/container
automated CC system (or integration with some online) which would would assist testing recording for ability to provide CC for the talk given by the speak on own hardware
Sample text (with field specific text) to narrate, do CC, provide feedback on how well it could recognize the voice
Ability to record the voice and provide CC for fixup to a. assess quality of CC on a particular text; b. submit CC along with the talk
could include installation of OBS if in the container... For Linux guest systems singularity container would provide turnkey deployment... not sure if would work/worthwhile for OSX and Windows hosts
I personally use it all the time also for the "live" virtual talks along with v4l patch/plugin to provide "virtual camera" for zoom/jitsi to use. There is a PR to have that feature included in OBS (for Linux only ATM) itself.
Recommend some commodity hardware (headphones, camera, video) which is known to work well
Aux ideas
by @raamana -- suggest institutions to setup a good video recording room (greenscreen, good mic, video) etc to facilitate HQ recordings
The text was updated successfully, but these errors were encountered:
Idea came up while discussing on OHBM 2021 TF slack in connection to #10 . It would be nice to compile materials and references which would assist speakers and participants to prepare and provide "high quality" content (e.g. pre-recorded talks). so here are some ideas on "sub-components"
QA toolkit/container
Documentation
Aux ideas
The text was updated successfully, but these errors were encountered: