N64(Composite)+Koryuu+OSSC (Rainbow Output Screen)

NewHome Forums OSSC & OSSC Pro OSSC – Discussion and support N64(Composite)+Koryuu+OSSC (Rainbow Output Screen)

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #37907
    the_leviathan
    Participant

    Hey guys.

    As the title implies, I’m trying to capture my NTSC Stock N64 via Composite to my Koryuu. Then output component to component in on my OSSC and then routed to my monitor. I’ve tried FireBrand’s optimal profile for N64 (but just changed it to not RGB) and no capture. Just a rainbow static test screen. I’ve tried from a clean empty profile and nothing seems to make it change. According to the OSSC, it’s outputting at 625i which is strange considering the signal from the N64 should be 320×320. Any thoughts on how to get the chain to work in tandom?

    Thanks!

    #37910
    the_leviathan
    Participant

    Also, I’d like to note that after taking the OSSC out of the equation, it works perfectly fine hooked up to my actual TV via component, minus no sound, which I’m not sure how you workaround. So there has to be some messed up setting on the OSSC.

    #37911
    the_leviathan
    Participant

    EDIT: Ok, so I’m not sure if this is a for sure reason, but I plugged the the Koryuu back into the OSSC and booted everything on in the following order. OSSC>Changed to AV2 input (YPbPr)>Koryuu>then the console and now I see it. Now the problem is routing the audio. How does one do that with the Koryuu?

    #37912
    the_leviathan
    Participant

    EDIT 2: Figured out the audio, instead of connecting the red and white component audio that’s connected to the end you’d plug into the OSSC, you just plug in the white and red from the composite cable. I should probably not make posts like this till I completely troubleshoot yeah? lol.

    #37969
    BuckoA51
    Keymaster

    Glad you figured it, the rainbow screen means the Koryuu is outputting its test pattern and not getting a signal.

Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.