I use WIndows (Win 10 Pro). Am I correct in assuming that MIDI Ports in the Options Menu should pick up my midi ports from WIndows just like all other software I have used or does GP require some special method? I have watched the first half of the Getting Started video, looked for a relevant topic in the 390 page manual, and have scanned the community topics for relevant discussions. Note: I am not a beginner. I have been using midi for almost 40 years. I cannot figure out why the MIDI Ports sections (in and out) say No Devices.
I rebooted GP, even rebooted the PC. Any other software sees my ports. The only music software running is GP, so its not like other software is using those devices.
Thanks for the reply. In the meantime, I gave up on the Options and went straight to the Default Rackspace and since it looks like Kushview Element, I just did a modular hookup from the OMNI Input devices and to a couple of vst3s. They play.
No midi ports are listed under Options, but GP sees my devices anyway. The devices do show up in the section where I can set CCs to GP functions. Currently 5 devices show up when I try to assign one to GP functions (Edit under Global MIDI). As expected they are the 2 DIN ports from a usb midi interface, 2 usb midi devices (keyboard and a Korg nanocontroller), plus the midi port on my PCI audio interface.
The âno deviceâ threw me for a loop! I figured that since all my audio ports were listed under options, so should the midi ports.
Now is as good a time as any to recommend that you study the Rig Manager and apply it sooner, rather than later. It enables you to give virtual names to your MIDI devices and various controls. It might seem to be an advanced function at first, but if you change MIDI devices and hookups in the future, it will help you avoid needing to edit multiple Rackspaces. Instead, you modify your rig or create a new one, and the change ripples through your entire setup.
As an example, instead of your keyboard being âMIDI Input Deviceâ or something generic like that, you can call it, â88 Key Pianoâ, or ânanocontrollerâ, or whatever. (I have âTopâ and âBottomâ for my two keyboards.")
You can also call CC#64 from the 88 Key Piano âSustain Pedalâ and use it throughout your system. Later, if you plug your sustain pedal into a different MIDI device, you can just change the Rig and play.
Another good practice is to connect your Audio Input and Output in the Global Rackspace. Use the âTo Rackspacesâ and âFrom Rackspacesâ blocks to get the audio to/from the Rackspaces. In each Rackspace, use the âTo Global Rackspaceâ and âFrom Global Rackspaceâ blocks. You can find these To/From blocks by right-clicking the wiring view and selecting âGlobal Processingâ.
The idea here is similar. Connect your I/O once, globally, rather than putting those specifics in your Rackspaces. If you change audio interfaces or connections, you just need to apply the change once to the Global Rackspace.
While you donât need to use these practices for initial tests, you will want these methods before you build multiple Songs and Rackspaces.
Thanks for these practical suggestions. If I ever decide to reinstall GP again, I will keep them in mind. However, I donât think GP is for me. While I was able to set up two VST3s and have them function on two different midi channels as an initial test, GP crashed several times claiming at first it couldnât find my midi devices and then it couldnât find my audio devices. After rebooting I found that my PCâs audio no longer worked (either ASIO or Windows audio) and midi no longer worked either. Fortunately, I was able to successfully uninstall GP and get the audio and midi working again.
I experienced similar behavior in the beginning, but all on me.
Are there any any other applications open that are using your devices? Another host, DAW, application, �
Because if your audio card or interface does not allow multiple clients, and/or it is in exclusive mode, this might explain the behavior youâre seeing.
In my case, opening a browser to playback a reference track for sound design on YouTube, Spotify or other websites first, would make GP produce no sound. And vice versa, opening GP first, my browser produces no sound.
Similarly when programming my Nektar Pacer footpedal via that fancy website UI, would prevent GP from seeing and using it as a MIDI controller.
On other words: try closing all applications (maybe even after reboot), and start GP first.
Exactly⌠to integrate available Midi- and audio ports is such a low level-basic functionality for any DAW - if this was actually Gig Performerâs fault, the forum was flooded with hundreds of complaints. I am with @UrGuardian4ngel: Some programm (or driver) is âstealingâ the ports so that they are no more available in Gig Performer.
Yes, but my other music (and non-music) software can still use midi and audio. I suppose thereâs something about GP that might be different, though.
Thanks for sharing your experiences and suggestions. While trying to fix the problem, I rebooted my PC several times. I am familiar with issues arising from trying to use different music software at the same time. I suppose some of the resident helpers that stay resident even though they are not running might have caused issues for GP.
I will look to see if I can find a dump file. Where can I send it?
GP will list the ports that Windows reports. Even when other applications are using ports, those ports still show up in GP MIDI Ports list. You said the list was empty, so that implies a problem locally on the machine. It could be permissions, it could be how the controllers/devices are connecting to the machineâŚwhatever the case may be, thereâs some snafu there in your configuration.
EDIT: It was determined that the Cherry Audio Free edition of GP was being used, so there would be no MIDI ports listed in the Options menu.
The only dump file that was created was Arturiaâs ASC. That looks like it happened when GP was scanning plugins. It only happened once, so the scan might have triggered a call home.
Is there a way to install GP to bypass the scan and then to do the scan manually? The scan took a while (I didnât time it, but Iâd say at least 1/2 hour). Or is there a way to edit scan paths, or does GP look at everything? I know there were several plugins GP didnât like, but I am used to music software ignoring them. Is there a scan log that might show? Probably too late for yesterdayâs installation, maybe I will try it again,
Does the GP installation do anything with the PCâs registry, installation of Microsoft Redistributables, or reordering or changing drivers in the registry?
Hate to have to say this, but if the problem only happens with one particular software, all other software worked fine before install it. and worked again when I remove the software and did some repairs . . . .
I will make some time to try installing GP again because it looks like the program might be useful to me. If GP creates logs, those might be helpful if I experience problems.
This is good to know. I never had music software that used the MIDI devices but failed to list them. Thatâs why I was surprised to see them in other places but not the the MIDI Ports list.
It could be a permissions issue or a folder/file location issue. Where is the list kept? For example, if there a configuration file? If so, where would it be?
Thanks for the reply. This morning I started over from scratch. Good news! So far no crashes, possibly because I only scanned one plugin folder (after clearing my plug list). Also, with a very simple test (3 VST3s from one usb controller on each of 3 midi channels), I have not lost either audio or the use of midi devices in GP or Windows. But the MIDI Ports still show no devices (In or Out). Is it possible the Cherry Audio Edition is limited to wiring a single MIDI In Device and a single MIDI Out Device?
If I get a Gig Performer Error Reporter dialog, I will follow those steps. Thanks.
For my understanding:
You are able to play VST instruments in gig performer using your midi keyboard, but you do not see the midi device in the midi ports window in the global options?
Oh, you are using the free Cherry Audio Edition! That explains a lot!
Yes, in the free edition, there is only the MIDI In (OMNI) port and no MIDI devices are displayed in the Gig Performer Options window.
The get the full flavor of Gig Performer, the best is to download the 14-day trial. That is the full version and all MIDI devices are shown.
So far no crashes, possibly because I only scanned one plugin folder (after clearing my plug list). Also, with a very simple test (3 VST3s from one usb controller on each of 3 midi channels), I have not lost either audio or the use of midi devices in GP or Windows. But the MIDI Ports still show no devices (In or Out). Is it possible the Cherry Audio Edition is limited to wiring a single MIDI In Device and a single MIDI Out Device?