I have purchased a new M4 MacBook Pro with Mac OS Sequoia. I had a Time Machine backup from my old M1 Desktop Mac which I have sold now. I have used the backup for the MacBook Pro. Now I have a strange problem. In Gig Performer I have most of my Gig Files setup with IAC Driver Bus 2 as a kind of standard MIDI In for my virtual instruments and than obviously the Drums are for example on IAC 2 Channel 10, the guitar on IAC 2 channel 3 and so on.
When I started Gig Performer for the first time on my new MacBook there were no IAC Channels appearing under MIDI Ports. So I went to the Apple MID Audio Setup and made I new configuration. So now there are on my Mac 8 IAC Buses and they appear in Gig Performer now also under MIDI Ports. The problem is that my Gig Files in the Wiring View are not configured anymore the way they were on my old system. Now in Wiring View every MIDI In is just a MIDI In. All the IAC routing information has disappeared! It would be a lot of work for me to fix this manually because we are speaking here of something like 50 songs and every song contains at least something like 30 virtual instruments. So that would mean that I would have to manually change for every virtual instrument in every song the MIDI IN Block from just MIDI IN to something like MIDI IN IAC 2 Channel 12 or whatever. The routing for the MIDI channel has not disappeared. So if the drums were on MIDI Channel 10 they are still on MIDI Channel 10, but the MIDI IN is no longer an IAC MIDI IN, but just a kind of general MIDI Input. So I got a real problem now.
this screenshot shows how it looks now. The drums are on channel 10, but it is not an IAC Midi Input.
And here I generated an IAC 2 Midi Input on Channel 10 for the sake of demonstration. This is this way I have setup all my virtual instruments in Gig Performer, but all those routings have disappeared!
In the meantime I have discovered that it is possible to change the routing for multiple Midi In Blocks at the same time. So it would be possible to route all blocks form general midi in to for example IAC 2 Midi In. The problem is that I have some pretty complex gig files where I use not only IAC 2, but also IAC 3, 4 etc. and now as all this routing info has disappeared I have no idea how to recover that routing information.
Curious as to why you’re using IAC ports at all.
I suspect that what happened was that when you recreated your ports on the new machine, you did not use exactly the same name that you used on your previous machine so GP can no longer find them. If you can check and fix that naming, you could try the original gig file again.
The Rig Manager was designed to help with this kind of thing but of course that doesn’t help you if you didn’t set the Rig Manager up from the beginning.
I have explained my workflow already a couple of times in this forum, but ok: I use Guitar Pro as a kind of Sequenzer/DAW wich sends MIDI notes to virtual instruments in Gig Performer. If you have more than 16 tracks than you will need something like for example a second IAC Bus to use the other virtual instruments in a certain song.
I am not yet familiar with the Rig Manager, but the thing is on a Mac you create IAC Buses and they always have the same name(s) like IAC Bus 1, IAC Bus 2 etc. by default. After that there might be options to change the names of IAC Buses within a certain software like Gig Performer or in your DAW, but I never did that! So I think that as much as I like Gig Performer let me put it like this: Gig Performer seems to be not able to kind of handle this exceptional situation in which I set up my new system based on a Time Machine Backup. So either Time Machine or Gig Performer or both are not able to recreate the complete “IAC environment” I had before. Maybe this is really a very unlucky constellation because in the Audio MIDI Manager obviously things were not correctly recreated after using the Time Machine backup. Not all of my MIDI Devices were appearing. So I had to generate a new configuration and there were not IAC Buses at all. I can understand that maybe with a new system there is just the necessity that the Audio MIDI Manager has to make a new scan of your MIDI Devices, but I find it a little strange that the Audio MIDI Manager is not able to preserve the IAC Buses.
Now I realize that you maybe meant that I have renamed IAC Blocks in the Wiring View of Gig Performer. That is correct, but even in cases where I did not rename IAC MIDI In Blocks they still don’t work and have to be corrected in some way with “Change MIDI Input Device”. At least I can change not so complex Gig Files with just one “Change MIDI Input Device” changing to IAC 2 very quickly, but as mentioned before there are more complex Gig Files where I can not just change everything in a brute fore manner to IAC 2, but ok I guess I just have some homework to do now.
My apologies, but if I had to read entire (often long) topics just to even see if info I needed was already there, I would spend my entire life reading topics and development would stop
The whole point of Rig Manager is to serve as an intermediate between physical devices and the names used in a gig file such that if physical names change, it is only necessary to update them once in the Rig Manager so that gigfiles will use the new devices without changes.
OK, I than I prefer that you continue developing instead of reading loooong topics
The thing with the Rig Manager sounds promising. I have to dive into it, but right now I have some other homework to do. I just wanted to ad that if anybody would get into such a situation like me that I did a fresh install of Gig Performer after having reestablished the missing IAC Ports with the Audio Midi Manager, but this didn’t help.
Maybe the last thing I will say about this because the whole issue remains a little bit cloudy (has GP a problem with replicating IAC Inputs from a Time Machine Backup or has Apple a problem or causes the interplay of both instances the problem I don’t know). Below you find two screenshots of IAC Ports. The first screenshot shows an IAC Block which did not work after this whole Time Machine Opera, the second screenshot shows a corrected IAC Block where I have used the “Change MIDI Input Device”. I don’t know if those screenshots can lead to any further ideas why the IAC Ports could not be replicated on the fresh Gig Performer Installation after the Time Machine Backup.
Can you post a screen shot of the MIDI Ports list in Options for both machines.
The names are different in your two blocks but I don’t know how much of that is due to you renaming stuff vs. underlying names.
For example, the upper block shows. IAC-Treiber Bus 2 but the slow just says IAC Driver Bus 2
So those are different and if you were not using aliases, it’s not a surprise that GP would not see the differently named version.
GP doesn’t replicate anything. It just sees whatever MIDI ports are on your physical machine and it looks like the IAC port names are different on your new machine. Why that is the case has NOTHING to do with Gig Performer.
I don’t have the old machine anymore. I would say I don’t want to bother you more with this IAC thing. I just have to rename some ports and then everything will be okay. Thank you very much for your advice.
Just seeing this conversation. I use IAC as well, because the mapping provided by the Rig Manager is insufficient to meet my needs. Sometimes I use the pads on my KeyLab (MIDI channel 10) for triggering certain actions and sometimes I use a different pad device. The only way I have found to get the flexibility I need is to have an entirely difference Gig file that maps physical inputs to IAC ports, and then I use the IAC ports in a separate instance as if I had separate physical devices. If only Gig Performer had a way of abstracting away physical devices by device name AND MIDI port, I could simplify my setup significantly.
I use rig manager with many different controllers. This includes some loop backs via IAC. I can use the same gig file across 4 machines and six different controllers. I suspect that you may be missing something in the way you are using Rig Manager. For me, RIg Manager was one of the main reason for switching to GP.
Sometimes the devil is in the details: The following only applies to Mac Systems:
I never cared so much about the IAC Ports. I just used them and everything was working fine, but after switching to a new Mac a lot of very stupid tings happened. The Audio Midi Manager wasn’t showing any IAC Ports at all anymore. On my old system I have used IACs 1 to 10 for internal routing purposes and never had any issues, but now I had to make a new Audio Midi Configuration and manually set up IACs 1 to 10. Ok, this is not a big deal, but after that I realized that in Gig Performer the IAC Ports on my old system had german names like “IAC Bus” instead of “IAC Port” so it seems that Gig Performer couldn’t work with the newly created IAC Buses in my old Gig Files because now everything was in english. Fortunately Gig Perfumer gives you commands to automatically reassign IAC Ports, but at least in my case that didn’t save me completely to make some reassignments manually. And I would have preferred to rather spend this time with making music or drinking a beer or whatever… And I still haven’t understood completely if the use of the Rig Manager would have saved me to get into such a situation or if it could save me in the future to avoid such situations. Don’t get me wrong. I don’t want to blame Gig Performer. I think the main root of the problem is the stupid way the Apple Audio Midi Manager is dealing with IAC ports.
Yes it would - in fact the ability to quickly remap ports whose names have changed was the original driving force behind the Rig Manager. The other driver was the need to be able to properly distinguish multiple identical controllers that had the same port names.
