NewHome › Forums › Koryuu Transcoder › Connecting Multiple Inputs To Koryuu With A Switcher
Tagged: Koryuu OSSC
megari.
So I have multiple composite/s-video systems I am trying to run through my OSSC via the Koryuu. I am wondering if it is possible to run a switcher to the Koryuu instead of a single console. I have a Pelican composite/s-video switcher, as well as a gcompsw component switcher (which also accepts a composite input) at my disposal. If that works, then there are the red/white RCA audio inputs left to deal with, since the Koryuu only accepts video inputs, and since the two switchers are already connected directly to the OSSC, would those just simply remain plugged into the switchers? Thanks for any help!
Hi!
I do not see any fundamental issue that would prevent using a switcher, provided excessive noise is not introduced. If the Koryuu is outputting video to the OSSC, the audio inputs can remain connected to the OSSC.
NewHome › Forums › Koryuu Transcoder › Connecting Multiple Inputs To Koryuu With A Switcher
Tagged: Koryuu OSSC
megari.So I have multiple composite/s-video systems I am trying to run through my OSSC via the Koryuu. I am wondering if it is possible to run a switcher to the Koryuu instead of a single console. I have a Pelican composite/s-video switcher, as well as a gcompsw component switcher (which also accepts a composite input) at my disposal. If that works, then there are the red/white RCA audio inputs left to deal with, since the Koryuu only accepts video inputs, and since the two switchers are already connected directly to the OSSC, would those just simply remain plugged into the switchers? Thanks for any help!
Hi!
I do not see any fundamental issue that would prevent using a switcher, provided excessive noise is not introduced. If the Koryuu is outputting video to the OSSC, the audio inputs can remain connected to the OSSC.
| Cookie | Duration | Description |
|---|---|---|
| _gat | 1 minute | This cookie is installed by Google Universal Analytics to restrain request rate and thus limit the collection of data on high traffic sites. |
| Cookie | Duration | Description |
|---|---|---|
| __gads | 1 year 24 days | The __gads cookie, set by Google, is stored under DoubleClick domain and tracks the number of times users see an advert, measures the success of the campaign and calculates its revenue. This cookie can only be read from the domain they are set on and will not track any data while browsing through other sites. |
| _ga | 2 years | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. |
| _gid | 1 day | Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. |
| Cookie | Duration | Description |
|---|---|---|
| IDE | 1 year 24 days | Google DoubleClick IDE cookies are used to store information about how the user uses the website to present them with relevant ads and according to the user profile. |
| test_cookie | 15 minutes | The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies. |
| Cookie | Duration | Description |
|---|---|---|
| ct_checked_emails | session | No description |
| ct_has_scrolled | session | No description |
| ct_mouse_moved | session | No description |
| ct_screen_info | session | No description |
| wordpress_apbct_antibot | session | No description |
| wp_woocommerce_session_9cc3598a6315be16da4f85bb374cf6a5 | 2 days | No description |
