cc3dsfs: A Multi-Platform Capture Card Software, with Fullscreen support

ossnorry
Posts: 10
Joined: Tue Jun 06, 2023 2:08 pm

Re: cc3dsfs: A Multi-Platform Capture Card Software, with Fullscreen support

Post by ossnorry » Sat May 02, 2026 8:41 pm

What causes this to appear?

Code: Select all

miniaudio WARNING: [WASAPI] Failed to find suitable device format for device info retrieval.miniaudio WARNING: [WASAPI] Failed to find suitable device format for device info retrieval.miniaudio WARNING: [WASAPI] Failed to find suitable device format for device info retrieval.miniaudio WARNING: [WASAPI] Failed to find suitable device format for device info retrieval.miniaudio WARNING: [WASAPI] Failed to find suitable device format for device info retrieval.[cc3dsfs] Connected to N3DSXL - nxl848774
I have my device set to 16-bit, 44.1khz in windows, should I be using a more ideal sample-rate or a different one? Curious how this error manifests. What audio format does cc3dsfs prefer?

Lorenzooone
Posts: 203
Joined: Tue Mar 26, 2024 2:10 am
Contact:

Re: cc3dsfs: A Multi-Platform Capture Card Software, with Fullscreen support

Post by Lorenzooone » Sun May 03, 2026 5:56 pm

ossnorry wrote: ↑
Sat May 02, 2026 8:41 pm
What causes this to appear?

Code: Select all

miniaudio WARNING: [WASAPI] Failed to find suitable device format for device info retrieval.miniaudio WARNING: [WASAPI] Failed to find suitable device format for device info retrieval.miniaudio WARNING: [WASAPI] Failed to find suitable device format for device info retrieval.miniaudio WARNING: [WASAPI] Failed to find suitable device format for device info retrieval.miniaudio WARNING: [WASAPI] Failed to find suitable device format for device info retrieval.[cc3dsfs] Connected to N3DSXL - nxl848774
I have my device set to 16-bit, 44.1khz in windows, should I be using a more ideal sample-rate or a different one? Curious how this error manifests. What audio format does cc3dsfs prefer?
These are just "warnings"... Does the audio work fine, aside from that?

ossnorry
Posts: 10
Joined: Tue Jun 06, 2023 2:08 pm

Re: cc3dsfs: A Multi-Platform Capture Card Software, with Fullscreen support

Post by ossnorry » Sun May 03, 2026 8:48 pm

Lorenzooone wrote: ↑
Sun May 03, 2026 5:56 pm
ossnorry wrote: ↑
Sat May 02, 2026 8:41 pm
What causes this to appear?

Code: Select all

miniaudio WARNING: [WASAPI] Failed to find suitable device format for device info retrieval.miniaudio WARNING: [WASAPI] Failed to find suitable device format for device info retrieval.miniaudio WARNING: [WASAPI] Failed to find suitable device format for device info retrieval.miniaudio WARNING: [WASAPI] Failed to find suitable device format for device info retrieval.miniaudio WARNING: [WASAPI] Failed to find suitable device format for device info retrieval.[cc3dsfs] Connected to N3DSXL - nxl848774
I have my device set to 16-bit, 44.1khz in windows, should I be using a more ideal sample-rate or a different one? Curious how this error manifests. What audio format does cc3dsfs prefer?
These are just "warnings"... Does the audio work fine, aside from that?
I've experienced a couple drop-outs, and sometimes it seems a little harsh so I'm curious how it's being resampled. I'll compare it with Loopy's app and 3.5 to see if it's plaecbo.

**but very specifically in Persona Q I have issues with drops and pops every time the game loads something.

But I'll do some more testing on that, to see what the cause is. I'll post my results and my data here on it later.

**I can post it to github if you prefer**

Lorenzooone
Posts: 203
Joined: Tue Mar 26, 2024 2:10 am
Contact:

Re: cc3dsfs: A Multi-Platform Capture Card Software, with Fullscreen support

Post by Lorenzooone » Sun May 03, 2026 9:43 pm

ossnorry wrote: ↑
Sun May 03, 2026 8:48 pm
Lorenzooone wrote: ↑
Sun May 03, 2026 5:56 pm
ossnorry wrote: ↑
Sat May 02, 2026 8:41 pm
What causes this to appear?

Code: Select all

miniaudio WARNING: [WASAPI] Failed to find suitable device format for device info retrieval.miniaudio WARNING: [WASAPI] Failed to find suitable device format for device info retrieval.miniaudio WARNING: [WASAPI] Failed to find suitable device format for device info retrieval.miniaudio WARNING: [WASAPI] Failed to find suitable device format for device info retrieval.miniaudio WARNING: [WASAPI] Failed to find suitable device format for device info retrieval.[cc3dsfs] Connected to N3DSXL - nxl848774
I have my device set to 16-bit, 44.1khz in windows, should I be using a more ideal sample-rate or a different one? Curious how this error manifests. What audio format does cc3dsfs prefer?
These are just "warnings"... Does the audio work fine, aside from that?
I've experienced a couple drop-outs, and sometimes it seems a little harsh so I'm curious how it's being resampled. I'll compare it with Loopy's app and 3.5 to see if it's plaecbo.

**but very specifically in Persona Q I have issues with drops and pops every time the game loads something.

But I'll do some more testing on that, to see what the cause is. I'll post my results and my data here on it later.

**I can post it to github if you prefer**
You may want to go to the "Audio Settings" to increase the "Max latency", then...
Something similar can happen when using bluetooth headphones, and increasing the "Max latency" by 1 or 2 usually fixes it.

Phlimbob84
Posts: 3
Joined: Sun Dec 14, 2025 10:26 pm

Re: cc3dsfs: A Multi-Platform Capture Card Software, with Fullscreen support

Post by Phlimbob84 » Tue Aug 11, 2026 8:49 pm

Hello! So I have an Optimize board installed on my Original 3DS XL by another individual whom I've unfortunately lost contact with. More recently, the board was replaced by the same person because the previous board was having problems. I don't know the hardware revision or firmware version of the replacement board. I've been having trouble getting it to work with the n3DSview software that he originally recommended using with the first board, and which I had been using with the first one with decent (though sometimes inconsistent) results until it apparently broke. When I found that you made this cc3dsfs program, that was huge for me! Unfortunately I'm still having trouble getting it to work consistently.

I tried the latest stable release first. Every time I tried connecting my 3DS it would briefly say "Connected" for a moment before showing the error "Disconnected: Read Error". Then I tried downloading and installing a cypress driver you had linked on a github closed issue (latest from Microsoft Update Catalog). Then when I tried connecting it gave me video and audio feed (though with an occasional flickering grey screen and much garbled audio). Now that it was connected, the "Optimize Settings" option appeared in the GUI menu and I was able to add my optimize key. However, after disconnecting and trying again, I only got the "Disconnected: Read Error" every subsequent attempt.

So next I tried the latest nightly build. I ran the driver installer bat file, restarted my computer (Windows 11, HP Pavilion Laptop) and tried again. First, it gave an error right away that said "Capture Start: Failed." Then after trying to connect again it gave video and audio for a second before disconnecting and giving the "Disconnected: Read Error." Then, every subsequent attempt resulted in the same error but without the brief video & audio.

In my device manager I find the following details:
Device: Cypress FX2LP No EEPROM Device
Provider: Cypress
Driver date: 6/24/2024
Driver version: 1.3.0.5
Hardware IDs:
USB\VID_04B4&PID_8613&REV_:001
USB\VID_04B4&PID_8613
(The Hardware IDs were unchanged from before the nightly driver installation.)

One other potentially relevant detail is that the original Optimize board installed in this same 3DS XL also had somewhat inconsistent capture behavior. It always had at least one n3DSview mode that worked, but different modes would work inconsistently, and I was never able to get proper-color 3DS game capture reliably. The replacement board behaves differently, but I'm still having the connection issues described above.

I have also tried multiple USB cables and ports but to no noticeable difference.

I would appreciate any help or insight you may have in the matter. I know you have incorporated more support for Optimize board recently, so I look forward to hearing from someone who knows what to look for with these boards since documentation appears very sparse. Please let me know if there is any additional information you think would be helpful for diagnosing a problem and I would be happy to help. I am really really hoping I can get capture working again with my 3DS like I did over a year ago with my old board when it was working.

Phlimbob84
Posts: 3
Joined: Sun Dec 14, 2025 10:26 pm

Re: cc3dsfs: A Multi-Platform Capture Card Software, with Fullscreen support

Post by Phlimbob84 » Tue Aug 11, 2026 11:26 pm

Phlimbob84 wrote: ↑
Tue Aug 11, 2026 8:49 pm
In my device manager I find the following details:
Device: Cypress FX2LP No EEPROM Device
Provider: Cypress
Driver date: 6/24/2024
Driver version: 1.3.0.5
Hardware IDs:
USB\VID_04B4&PID_8613&REV_:001
USB\VID_04B4&PID_8613
(The Hardware IDs were unchanged from before the nightly driver installation.)
Update: I discovered that manually uninstalling the Optimize drivers with the nightly's uninstall script, then manually installing the cyusb3.inf from the nightly's drivers/cypress_usb folder and rebooting Windows produces a different USB device identity (VID_04B4&PID_1004) and has allowed stable 3DS-game capture. The previous configuration showed VID_04B4&PID_8613. I'm currently getting somewhat stable video (many frame drops at times) and very garbled audio, but progress is progress!

Post Reply