Hi,
I need to revisit this topic. ChatGPT didn’t provide enough clarity, and the Gig Performer manual only answered parts of my questions. Before expanding the discussion further, I’d like to understand which workflow is generally recommended.
I’m currently dealing with an issue where Gig Performer freezes during certain actions. @dhj suspects a MIDI loop. It’s possible that this might be caused by an incorrect structure in my Rackspaces, because the freezes seemed to start around the time when I first began using Local MIDI Ports in GP.
Regardless of the freezing, I want to make sure that my overall MIDI routing is correctly set up.
Could someone explain the exact difference and intended purpose of
Local Ports versus physical ports?
What do you recommend in real-world use?
– Should I directly select the hardware ports?
– Or should everything be routed through Local Ports?
Right now I’m using a mix:
Keyboards are connected via physical ports, and controllers were learned directly via MIDI. However, this causes the issue that the MIDI messages only reach the assigned widgets and are no longer accessible through the physical port.
First of all stop depending on ChatGPT it basically just regurgitate with somebody else fed in to it.
Secondly, it would be much better if you explain what you were trying to accomplish rather than just telling us that you’re getting a freeze.
Thirdly, the main purpose of the local GP port is to allow plug-ins that generate mini messages to be routed back into gate performer, as if they came from the outside, for the specific purpose of controlling widgets. However, anything that is sent to a GP local port will also be received by a MIDI In Omni port. Unless you know exactly what you were doing. That is a recipe for a midi feedback loop.
The general rule: if you use a GP local port or any other kind of virtual mini ports like the Mac IAC ports, you should avoid MIDI Omni ports
Yes, I was aware of the post. However, I hid it because I was only looking for why GP freezes. But thanks for the tip. I’ll take a look at that MIDI Thru option. However, I’m not using MIDI Loopback. I need to keep investigating what loop is causing this.
Yes, I know. But I also had a pretty steep learning curve when I started with GP. And I didn’t have to bother you with minor things.
My long-term goal is to find out the reason for the freezing. I can well imagine that I have a loop somewhere in my programming between local ports and physical ports—just like you suggested. Similar to the recent post by mtrombetta, who had a loop with Loopback. Your GP program is incredibly powerful, and for me, it’s very complicated to explain what I want. The short-term goal is to figure out which MIDI inputs I’m accessing on the physical ports and which on Local GP. I haven’t programmed the Omni Port MIDI In Block in any Rackspace.
Ok….I would have assumed that your long term goal was to have reliable gigfile for performance and consequently what exactly you were trying accomplish with your implementation of your rackspaces, songs, and widgets etc.
For example, why are you even using the GP Local Port?
I think you’re already on the right track for solving your issue and you may have already checked your mioXL config but just in case it matters, take a look through your mio config to make sure you haven’t inadvertently created any looping between the physical ports, usb ports, and daw ports. I’ve been bitten by that in the past.
I spent all day today implementing @pianopaul’s idea and removed all local GP ports from my Rackspace. It’s hard to believe how much time I wasted on it. I’m just seeing it as learning by doing. Next week, I’ll reprogram the songs using the physical ports and only then will I see if it actually works. The first song, at least, was successful. Thanks again for your input. Once I’ve successfully completed the tests, I’ll mark it as solved. I hope that also resolves the issue with GP freezing.
