Yoshimi marks Qtractor session dirty/changed immediately after loading session (with Yoshimi in some tracks)

[suedwestlicht]

Yoshimi LV2 plugin does something after being loaded that makes Qtractor think the session has changed. This might affect other DAWs/sequencers as well.

I tried to find out which commit introduced this behaviour:

785a508dd7880d00b9ad013ab2a6625522a3d02b marks Qtractor session dirty/changed immediately after loading session

11da28eb845d6825ee017bae5e69ea9ce7727ac7 doesn't build on my machine

67f4ca1c7546a8c758f845fe92cd3eba5380eeaf doesn't build on my machine

932611eca324a71d8ce4f802e22c7c8fb0678938 doesn't build on my machine

7bc02a15ebb953d5dd92d360e9d5e3bafa6bfaf0 ok, normal behaviour

[suedwestlicht]

I noticed that this versions causes an xrun, too, at session load. No big thing but this didn't happen with 7bc02a1

[Ichthyostega]

Thanks for pointing that out.
As you've probably noticed when looking at the History, we did somewhat far reaching clean-up and modernisation under the hood, mostly related to how the GUI is launched at start-up and can then communicate with the core.
What makes the situation with LV2 difficult for us is the fact that Yoshimi (right from start) used a non-standard extension to the LV2 standard for launching its GUI. The Yoshimi application violates some fundamental requirements for a LV2 plugin, and it was rather through creative trickery that it became possible to make it work within most known LV2 hosts.

[abrolag]

I haven't had time to look at this, but it might be related to finding the user guide. That changed quite significantly.

…

-- Will J Godfrey

[suedwestlicht]

Yes, that might be the cause. Qtractor says:

XRUN(8 skipped)
XRUN(9): some frames might have been lost.
manual found

[abrolag]

On Thu, 03 Oct 2024 01:44:25 -0700 suedwestlicht ***@***.***> wrote: Yes, that might be the cause. Qtractor says: ``` XRUN(8 skipped) XRUN(9): some frames might have been lost. manual found

I haven't had time to look at this in detail yet, but at startup Yoshimi checks the installed manual version against the actual version, and updates the config file if necessary. Possibly it is also updating the config file when it's NOT necessary - i.e. already the same one.

…

-- Will J Godfrey {apparently now an 'elderly'}

[suedwestlicht]

With 79e749b no more xruns when loading a Qtractor session with yoshimi.
But the Qtractor session is still marked dirty/changed immediately after loading.

[abrolag]

On Fri, 11 Oct 2024 09:01:44 -0700 suedwestlicht ***@***.***> wrote: With 79e749b no more xruns when loading a Qtractor session with yoshimi. But the Qtractor session is still marked dirty/changed immediately after loading.

Thanks for the update. Currently looking for the cause of the 'changed' issue.

…

-- Will J Godfrey {apparently now an 'elderly'} https://willgodfrey.bandcamp.com/ http://yoshimi.github.io Say you have a poem and I have a tune. Exchange them and we can both have a poem, a tune, and a song.

[abrolag]

Still haven't found the cause, but not forgotten.

[abrolag]

On Fri, 11 Oct 2024 09:01:44 -0700 suedwestlicht ***@***.***> wrote: With 79e749b no more xruns when loading a Qtractor session with yoshimi. But the Qtractor session is still marked dirty/changed immediately after loading.

I've a suspicion that the cause of this is that Qtractor scans the tracks for program changes and then applies them. This means Yoshimi will load them (even if they were already there) so has indeed been 'changed'. It doesn't happen with Ardour, presumably because this doesn't do the same load in advance.

…

-- Will J Godfrey {apparently now an 'elderly'}

[suedwestlicht]

The session in Qtractor is marked dirty although I have Bank=None and Program=None in all tracks.

[abrolag]

On Sat, 28 Dec 2024 01:45:54 -0800 suedwestlicht ***@***.***> wrote: The session in Qtractor is marked dirty although I have Bank=None and Program=None in all tracks. 

Hmmm. That's Odd - will have to investigate :(

…

-- Will J Godfrey {apparently now an 'elderly'}