I am trying to use GP4 without using an audio interface. 'I assumed this was a possibility by selecting Audio Device type: ASIO and Device:ASIO4ALL,
however even though ASIO4ALL shows in the GP options menu, Selecting it brings up that red screen of death that says “Audio interface disconnected”. HELP!
Maybe make sure it is set up in your computer audio setup too? (That is what I would try while floundering around)
Jeff
ASIO4ALL (v2.15) works perfectly with GP4.
Surprisingly, with low latency and low buffer sizes of 96 samples, too.
I have it on my live production laptop as backup, but only if my RME Babyface Pro main audio interface would fail for some very unlikely reason.
Or if I forgot to bring my Babyface from one studio or rehearsal room to another, which happened sometimes. ASIO4All worked fine with GP4 instantly on that occassions.
i assume without external audio inteface?
What would you expect if you don’t have an internal or on-board sound device, as well?
1 Like
Yes I meant without an external audio interface.
UPDATE: I finally got GP to play a plugin without an external audio interface AND with the WIDI Pro Bluetooth midi… (The goal was to illiminate the need for an external audio interface for both audio AND MIDI. THE NEW PROBLEM: Whenever I change a Midi channel on my keytar to play a different plugin…GP crashes…SO I am back to sare one!
Let’s see the crash report please
Where can I access that?
Where can I access that?
Log Name: Application
Source: Application Error
Date: 4/22/2024 7:10:45 PM
Event ID: 1000
Task Category: Application Crashing Events
Level: Error
Keywords:
User: DESKTOP-CI2IAS4\Rich Tancredi
Computer: DESKTOP-CI2IAS4
Description:
Faulting application name: GigPerformer4.exe, version: 4.5.8.0, time stamp: 0x626bf709
Faulting module name: korgbm64.drv, version: 1.12.2.1, time stamp: 0x58d36f0e
Exception code: 0xc0000409
Fault offset: 0x0000000000005443
Faulting process id: 0x0xFAC
Faulting application start time: 0x0x1DA950A44826F52
Faulting application path: C:\Program Files\Gig Performer 4\GigPerformer4.exe
Faulting module path: C:\WINDOWS\SYSTEM32\korgbm64.drv
Report Id: 03e6b430-a046-4b69-bf9d-c3596254bdbe
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
1000
0
2
100
0
0x8000000000000000
1209
Application
DESKTOP-CI2IAS4
GigPerformer4.exe
4.5.8.0
626bf709
korgbm64.drv
1.12.2.1
58d36f0e
c0000409
0000000000005443
0xfac
0x1da950a44826f52
C:\Program Files\Gig Performer 4\GigPerformer4.exe
C:\WINDOWS\SYSTEM32\korgbm64.drv
03e6b430-a046-4b69-bf9d-c3596254bdbe
Here is another crash log:
GigPerformer4.exe
4.5.8.0
626bf709
korgbm64.drv
1.12.2.1
58d36f0e
c0000409
0000000000005443
0x29b8
0x1da950a71ac7950
C:\Program Files\Gig Performer 4\GigPerformer4.exe
C:\WINDOWS\SYSTEM32\korgbm64.drv
a416fa06-b5ae-4dca-a94b-4f2630c3ddf9
Thanks, the crash is occurring in
Faulting module path: C:\WINDOWS\SYSTEM32\ korgbm64.drv
Presumably some kind of driver from Korg
Unfortunately, thats the Bluetooth Midi Driver I use so I dont have to use a mii interface…
I would never rely on bluetooth.
1 Like
Whynot? I use it for my keytar so I don’t trip over a 25ft midi cable…lol
I am using MIDI Beam.
Bluetooth is a very unreliable protocol.
1 Like
wireless MIDI — MIDI products by pandaMidi? Thats the 2nd time in a week someone has recommended that.
So you come out of your computer via USB on the main unit and the other , to your keyboard?
Yeah, I have a panda as well. Works great. I agree completely with @pianopaul I would never use bluetooth in a live performance environment. Heck, half the time, one’s phone doesn’t even stay connected to a car via bluetooth, never mind needing 100% reliable real-time behavior.
I use widi bud pro - no external driver needed-
Also I use panda midi with keytar
Never had any issues- on win 11
I use the CME WIDI