Opus Quad Issue - Recording past 3 Hour Limit file corruption bug

There is currently a serious and very frustrating bug with the Opus Quad's internal recording option to USB.

If a recording hits the 3 hour mark (the length limit), functionality is supposed to transition seamlessly into a second recording file, allowing recording to continue.

The issue is that when this occurs, the initial 3 hour file is corrupted and is unable to be used or played on devices including MacOS (where the corrupted file is actually invisible in the FInder) or Windows (where the file is unplayable due to corruption).

While I'm sure there is a way to fix the corrupted file using 3rd party software, the file is easily lost when trying to correct the corruption. And the corruption should not be occurring in the first place.

The only way I've found to manage this at the moment is to ensure recording is stopped any time before 3 hours and restarted manually.

I have lost 6 hours of professional mixes thanks to this Opus Quad Bug.

Any comment from others or Pioneer staff?

Thanks,

Ollie

Ollie de Vries 10 novembre 2023 00:10

Vous devez vous connecter pour laisser un commentaire.

Date Votes

2 commentaires

That sounds incredibly frustrating, especially if you’re recording long sets and only discover corruption after the 3-hour mark. Issues like this remind me how important proper file handling and accurate identification are in tech, just like in nature. I work with a tool called bug identifier free that uses image recognition to identify insects, and even small data inconsistencies can affect results. Hopefully Pioneer addresses this quickly, since reliable recording is essential for live performers.

Hugo Olivia 3 mars 2026 17:51 0 votes

I experienced the same issue.

The first 3 hours were recorded perfectly, and the first WAV file plays without any problems.

After the automatic 3-hour split, the OPUS-QUAD still showed REC and the timer kept running, so everything looked normal on the display. However, when I checked the USB drive afterwards, the second file was 0 bytes.

In my case, the USB drive was a completely new and empty SanDisk Ultra USB 3.0 32 GB drive, which I wanted to use for recordings only. Since the first 3-hour file is perfectly fine and the issue happened exactly after the automatic split, this really looks like a recording/file-splitting bug rather than a general USB write-speed issue.

For a device this expensive, this is really not acceptable. This is a basic function that should work without any problems.

m.schachinger97 . 29 juin 2026 16:50 0 votes