Hi again Rob, the zoom does not have a switchable rate as such, when it powers up initially which I have to do at W7 startup you take it into AI mode before opening any progs (BIAB or CB) and its default is 44100 24 bit. When I have CB open waiting for use of the PGin it operates with a test track which I have loaded into CB after creating empty proj in CB. So at each stage of trying to use the PGin I am able to check by using the test track to see if all is well within CB. This has been fine and as I open the PGin it (CB) remains operational.
I can either then open an existing file from the PGin and it will drag the style along with it, or I can remake the track from within the PGin by selecting style and typing the chords in. As long as I don't generate from within the PGin all appears to work fine, the test track in CB continues to run and if I operate the transport within the PGin (without having generated) the PGin runs through its playing chords but obvs without sound. If I then generate the progress seems to go smoothly with the pop up messages but if I watch the AI whilst this is in progress at some point towards the end of generation the AI flips to 96000 and I take it that some message from within the generation has been sent to the AI to cause this. Of course the test track in CB is not now audible, to move the AI back to make the test track audible I have to close CB and shut the AI down, restarting it from W7 basic login whereon it will start at 44100 OK.
This forced change to the AI status comes when generation is triggered either from an imported MGU or a built track within the the PGin.
The Tech support at PG music have not replied other than to say we acknowledge yr email and we'll call you. They first knew I had a problem on 12th Jan, I wouldn't mind but I've only been a customer for 25 years, I must have spent 1000's on versions going back to when there were only about 30-50 styles. Hope yr keeping safe in these difficult times. not sure what my next step will be