On 01/01/2026 17:23, Ted Felix wrote:
On 12/29/25 11:26 AM, Lorenzo Sutton wrote:
Unfortunately I still seem to get this with latest git and Ardour
Ardour8.12.0, in this case starting playback with jack transport
enabled /and /ardour set to sync with JACK Transport, then starting
playback in either rosegarden or Ardour eventually crashes Ardour
with an 'POOL out of memory' kind of error.
I tried empty composition and project and ran for 100 bars with
rosegarden and ardour kept up and did not crash. I'm running 8.12 in
debug mode built from source.
Do you get the crash when playing an empty rg composition and ardour
project for 100 bars?
I can still get this with Rosegarden (just built from git) and Ardour8.12.0.
I have a blank session in Ardour set-up to sync with JACK Transport and
a new file in Rosegarden (100 measures). What works:
- start/stop in both with mutual sync
- re-positionong playhead in rosegarden (ardour follows)
What doesn't work
- Repositioning in Ardour while _not_ rolling (rosegarden only follows
upon playback *in Ardour*, else if playback is initiated in Rosegarden
it will go to the rosegarden position)
How to trigger an Ardour 'crash':
- Select 'JACK Transport auto stop' in the preferences. Go to the end of
measure 100 in Rosegarden, then in Ardour, start play - This even if
'Stop playback at end of last segment' is *disabled*
- Go directly at end of piece (end of measure 100 in this case) by e.g.
pressing 'END' key in rosegarden even if not rolling, with all of the
jack options activated _and_ 'Stop playback at end of last segment'
selected in rosegaden
In rosegarden the playhead appears to remain still, in Ardour the
playhead seems to quickly bounce forward and then back to the
original position.
I don't see anything like this.
Philip has fixed a few additional issues. Try the latest in git
[ddf51c6f93] and see if that improves things.
I am still getting the issue of 'unmovable' playhead and inability to go
to start in _some_ files, which makes me think 'something' (TM) in a
specific file, segment, etc. can influence the behaviour (or maybe
'breaks' some more recent changes?). But I'm wondering what in a
specific (possibly a bit older) rosegarden file can influence this?
Lorenzo
Ted.
_______________________________________________
Rosegarden-user mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user
_______________________________________________
Rosegarden-user mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user