![]() ![]() Why is this, when I’d already done these two steps and saved the file? Now every time I reopen the gig file, I have to do the following all over again: 1) point an instance of Battery to its Library, and 2) open every single Battery instance, all 37, to get them to make sound. But now it’s functioning normally, so I save the gig file and close it. Now, weirdly, I have to actually OPEN every single Battery instance (there are 37 of them) in order to get it to make sound. In each rackspace, I do “Change MIDI Input Device” for all MIDI IN plugins (I’m using the same MIDI interface, and the Rig Manager has the same aliases for its ports as it does on Win10). In order to make this gig file work on the Mac, I open a Battery instance and tell it where to find its Library. I saved a new version of the gig file, which now has only Win10-added Battery instances, and opened it on my MacBook. As a workaround, I’ve opened the macOS-created gig file on Win10 (without opening any Battery instances, which would crash), replaced every Battery instance with its Windows VST2 file, and then successfully loaded the relevant Kit into the instance. ![]() I’m in touch with Native Instruments about the fact that Battery crashes on Win10 every time I open a Battery instance in the gig file.īut I want to bring up something else that seems to be more of a GigPerformer issue. Since upgrading to Battery 4.2.0, I’ve had major issues trying to open our 37-rackspace macOS-created gig file on Windows 10. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |