Logic Pro X Logic Pro 10.5. released

Fabulowsky

Logician
screenset with extra transport.png

I'm running Mojave 10.4.6 and now Logic 10.5, the screen upper shows an example of an extra transport window on the bottom added from nowhere. when i removed, unlocked and locked the screenset again it kept bugging like that, but not on all my screensets.
It seems that the current code suffers sensitivity to side effects from switching from one set to another.
Also logged another bug, where if you restore a project with a hyperedit window as an example, it will start empty, then when using a different screen number ; it is hanging there until you open a window (i.e. main window), weird too but at least i have a workaround for the last problem.

EDIT: to reproduce one weird problem you may try to simply put one transform window but in two different screensets and also at different positions, then lock each screenset you created and then try use them -> you should get the transform window always at the same location...
 
Last edited:

rainguitar

Logician
Some of this may also be an issue specific to either Mojave or Catalina. I'm still on the former. Replika and Replika X are working fine here but not Phasis, which crashes if I change a preset.
 

Fabulowsky

Logician
Just found another bug with external instruments:
When using both the environment multi-instruments with their addtional respective audio external instrument track (so at least one pair of audio+midi track) so that you get the monitoring and also the real-time bouncing as well as program changes from environment ; and you hide audio tracks using the 'H' functions, then save a template ; then create a new project from that new template:
-> the monitoring does not happen anymore, unhide the tracks and then monitoring works again.

EDIT: Actually even when restoring with audio tracks that are _not_ hidden, i can get the same problems, the problem goes aways if you click first on the audio track and play some notes, then click on the midi multi instrument corresponding to that audio track with the external plugin.
That last workaround may not be minimum but seems to always work.
It seems the problem occurs when restoring, so hiding tracks was in fact not related to it...

Anyone with external instruments having similar problems (using both audio and midi external tracks and then hiding the audio tracks)?
 
Last edited:
Top