"Presonus faderportV2" is not your Presonus audio-interface. You can search on the Presonus product pages and see, that the Faderport and your audio-interface are two different devices serving two different purposes. The Faderport is a device usually known as a MIDI Controller device. Waveform calls Control Surfaces the configuration entries which define how Waveform shall interact with a specific MIDI Controller.
We wish to see that the Soundcraft audio-interface does NOT become falsely recognized as a MIDI Controller, so that signals and data send from the Soundcraft audio-interface to Waveform could not trigger functions like the RECORD ABORT button in the DAW. No audio-interface shall have a Control Surface entry, only MIDI Controllers should have it. Confirming that for your audio-interface does not appear there an entry helps to exclude such weird misconfiguration as a possible cause.
Best would be if you could upload screenshots showing all entries in that Surface Control list. I would be much surprised if there would appear something which doesn't belong there. But, your issue is strange, so better to exclude even strange things.
When back at the Soundcraft device, make sure to create a new project and test for the issue in the newly created project, just to make sure that a maybe re-used project is not corrupted under the hood and causing the problem.
We wish to see that the Soundcraft audio-interface does NOT become falsely recognized as a MIDI Controller, so that signals and data send from the Soundcraft audio-interface to Waveform could not trigger functions like the RECORD ABORT button in the DAW. No audio-interface shall have a Control Surface entry, only MIDI Controllers should have it. Confirming that for your audio-interface does not appear there an entry helps to exclude such weird misconfiguration as a possible cause.
Best would be if you could upload screenshots showing all entries in that Surface Control list. I would be much surprised if there would appear something which doesn't belong there. But, your issue is strange, so better to exclude even strange things.
When back at the Soundcraft device, make sure to create a new project and test for the issue in the newly created project, just to make sure that a maybe re-used project is not corrupted under the hood and causing the problem.
Statistics: Posted by talby — Fri Sep 27, 2024 11:14 pm