Re: Re: Starting playback in the middle of a movement

[Andreas Schneider]

On 2019-12-14 12:27, Richard Shann wrote:

On Wed, 2019-12-11 at 11:34 +, Richard Shann wrote:

I get these two messages immediately when clicking playback start.
The
sound starts considerably later.


independent of where the playback start marker is. Playback
ends
with
the message

Here endeth a scripted playback


Are you using JACK or Alsa?


I am using JACK.


Mmm, that's something that I have even less experience with - does it
allow you to ask for messages to indicate when it does things - when
it
gets input? Did you upgrade to the latest Debian Stable? I haven't
done
that yet, which could account for the difference we are seeing.
This is contingent on the old versions of Denemo showing the same
behaviour (see below).


When writing that reply I was not thinking clearly enough: if you are
getting a long delay when starting in the middle of a movement and *not
*at the end then it must be that Denemo is doing something during that
delay. What might work is to run it under the debugger and use Control-
C to interrupt it during the long pause and then the command "where" to
find out which function it is in at the time (then "continue" and
interrupt it again). Doing this a few times may show up some loop in
the Denemo code (there will be more sophisticated ways of doing this
I'm sure but this may do ...

Thank you for the suggestion. This is what I get:

#0  0x75393819 in __GI___poll (fds=0x55e5baa0, nfds=3,
timeout=10)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7626a136 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7626a4c2 in g_main_loop_run ()
at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x76a61b15 in gtk_main ()
at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#4  0x555ea26f in  ()
#5  0x77e25753 in  () at
/usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
#6  0x77ed5250 in  () at
/usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
#7  0x77ea716e in  () at
/usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
#8  0x77edf563 in  () at
/usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
#9  0x77efe896 in  () at
/usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
#10 0x77e301ab in scm_call_4 ()
at /usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
#11 0x77ed50a6 in scm_catch_with_pre_unwind_handler ()
at /usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
#12 0x77ed5328 in scm_c_catch ()
at /usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
#13 0x77e255a2 in  () at
/usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
#14 0x77e2586b in scm_c_with_continuation_barrier ()
at /usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
#15 0x77ed201c in  () at
/usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
#16 0x77d54ef5 in GC_call_with_stack_base ()
at /usr/lib/x86_64-linux-gnu/libgc.so.1
#17 0x77ed2105 in  () at
/usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
#18 0x77ed2145 in scm_with_guile ()
at /usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
#19 0x5557bd5a in main ()

Can you see therein what the problem may be?

Andreas

Re: Titles

[Andreas Schneider]

By default Denemo creates a tagline "[filename] on [date]".
1) Is it possible to configure that, e.g. to have "Version from [date]"
instead, or is the text hard-wired?
2) When setting simple score titles (Score > Titles > Simple
Titles > Set Titles), the default tagline mentioned above is not shown
any more, even when not setting the tagline. That is due to the script
setting those entries not set decidedly to ##f. Is there an option to
select whether the default tagline shall be still printed or not?

Andreas

Re: Starting playback in the middle of a movement

[Richard Shann]

On Wed, 2019-12-11 at 11:34 +, Richard Shann wrote:
> > I get these two messages immediately when clicking playback start.
> > The
> > sound starts considerably later.
> > 
> > > > independent of where the playback start marker is. Playback
> > > > ends
> > > > with
> > > > the message
> > > > 
> > > > Here endeth a scripted playback
> > > 
> > > Are you using JACK or Alsa?
> > 
> > I am using JACK.
> 
> Mmm, that's something that I have even less experience with - does it
> allow you to ask for messages to indicate when it does things - when
> it
> gets input? Did you upgrade to the latest Debian Stable? I haven't
> done
> that yet, which could account for the difference we are seeing.
> This is contingent on the old versions of Denemo showing the same
> behaviour (see below).

When writing that reply I was not thinking clearly enough: if you are
getting a long delay when starting in the middle of a movement and *not
*at the end then it must be that Denemo is doing something during that
delay. What might work is to run it under the debugger and use Control-
C to interrupt it during the long pause and then the command "where" to
find out which function it is in at the time (then "continue" and
interrupt it again). Doing this a few times may show up some loop in
the Denemo code (there will be more sophisticated ways of doing this
I'm sure but this may do ...)

Richard