Re: Starting playback in the middle of a movement

2020-01-08 Thread Richard Shann
On Mon, 2020-01-06 at 19:44 +0100, Andreas Schneider wrote:
> On 2019-12-21 13:27, Richard Shann wrote:
> > On Wed, 2019-12-18 at 23:24 +0100, Andreas Schneider wrote:
> > > On 2019-12-18 11:22, Richard Shann wrote:
> > > > On Mon, 2019-12-16 at 19:39 +0100, Andreas Schneider wrote:
> > > > > [...]
> > > > 
> > > > I've been looking at the code and I see a promising place for
> > > > the
> > > > trouble to lie - I've made a change which may even fix the
> > > > problem
> > > > you
> > > > are having. Meanwhile - does the "loop" button work for you?
> > > > And,
> > > > if
> > > > you have "Listening to Notes" set, can you hear yourself play
> > > > while
> > > > the
> > > > big pause is happening?
> > > 
> > > I have built the latest version from git and it still shows the
> > > same
> > > behaviour.
> > 
> > I don't know whether you have tested earlier versions of Denemo,
> > but I
> > have just reverted the bit of code that I suspect is causing JACK
> > trouble to the version that Dominic Sacré wrote. Perhaps you can
> > test
> > this (the reversion is only for _HAVE_JACK_ but my limited testing
> > shows it working for portaudio too).
> > I'll forward this email if it doesn't get delivered to you, until
> > it
> > does.
> 
> Sorry for taking so long to respond, I was on holiday and thus could
> not
> test. With the new version, the problem is fixed, playback again
> works
> as expected

Can you let me know you come across anything broken in that version -
there will be (or was) some reason for the alternative code that is
failing on JACK ...

Richard







Re: Starting playback in the middle of a movement

2020-01-06 Thread Andreas Schneider
On 2019-12-21 13:27, Richard Shann wrote:
> On Wed, 2019-12-18 at 23:24 +0100, Andreas Schneider wrote:
>> On 2019-12-18 11:22, Richard Shann wrote:
>>> On Mon, 2019-12-16 at 19:39 +0100, Andreas Schneider wrote:
 [...]
>>>
>>> I've been looking at the code and I see a promising place for the
>>> trouble to lie - I've made a change which may even fix the problem
>>> you
>>> are having. Meanwhile - does the "loop" button work for you? And,
>>> if
>>> you have "Listening to Notes" set, can you hear yourself play while
>>> the
>>> big pause is happening?
>>
>> I have built the latest version from git and it still shows the same
>> behaviour.
>
> I don't know whether you have tested earlier versions of Denemo, but I
> have just reverted the bit of code that I suspect is causing JACK
> trouble to the version that Dominic Sacré wrote. Perhaps you can test
> this (the reversion is only for _HAVE_JACK_ but my limited testing
> shows it working for portaudio too).
> I'll forward this email if it doesn't get delivered to you, until it
> does.

Sorry for taking so long to respond, I was on holiday and thus could not
test. With the new version, the problem is fixed, playback again works
as expected. Thanks for investigating and fixing.

Andreas



Re: Starting playback in the middle of a movement

2019-12-21 Thread Richard Shann
On Wed, 2019-12-18 at 23:24 +0100, Andreas Schneider wrote:
> On 2019-12-18 11:22, Richard Shann wrote:
> > On Mon, 2019-12-16 at 19:39 +0100, Andreas Schneider wrote:
> > > [...]
> > 
> > I've been looking at the code and I see a promising place for the
> > trouble to lie - I've made a change which may even fix the problem
> > you
> > are having. Meanwhile - does the "loop" button work for you? And,
> > if
> > you have "Listening to Notes" set, can you hear yourself play while
> > the
> > big pause is happening?
> 
> I have built the latest version from git and it still shows the same
> behaviour.

I don't know whether you have tested earlier versions of Denemo, but I
have just reverted the bit of code that I suspect is causing JACK
trouble to the version that Dominic Sacré wrote. Perhaps you can test
this (the reversion is only for _HAVE_JACK_ but my limited testing
shows it working for portaudio too).
I'll forward this email if it doesn't get delivered to you, until it
does.

Richard





Re: Starting playback in the middle of a movement

2019-12-19 Thread Richard Shann
On Wed, 2019-12-18 at 23:24 +0100, Andreas Schneider wrote:
> On 2019-12-18 11:22, Richard Shann wrote:
> > On Mon, 2019-12-16 at 19:39 +0100, Andreas Schneider wrote:
> > > [...]
> > 
> > I've been looking at the code and I see a promising place for the
> > trouble to lie - I've made a change which may even fix the problem
> > you
> > are having. Meanwhile - does the "loop" button work for you? And,
> > if
> > you have "Listening to Notes" set, can you hear yourself play while
> > the
> > big pause is happening?
> 
> I have built the latest version from git and it still shows the same
> behaviour. I guess that with "Listening to Notes" you refer to the
> option "Play back entered notes immediately" under Preferences >
> Audio?

No, I meant one of the three settings of the button in the MIDI in
Controls that is set by default to Appending/Editing Pitches but can be
set instead to checking or listening to pitches, with that you can play
an accompaniment to a piece while it is playing back.

> I have that set, and I hear the sound when entering notes during the
> pause during playback. The loop button works, but there is a pause

"a pause" that gets longer the further you are from the beginning I
guess?

> between the repeated playbacks when the playback start marker is not
> at
> the beginning.

ok, the message when it starts playing has changed - it should now give
two times, what are they in the circumstances when you start from the
beginning and when you start toward the end?

Richard






Re: Starting playback in the middle of a movement

2019-12-18 Thread Andreas Schneider

On 2019-12-18 11:22, Richard Shann wrote:

On Mon, 2019-12-16 at 19:39 +0100, Andreas Schneider wrote:

[...]


I've been looking at the code and I see a promising place for the
trouble to lie - I've made a change which may even fix the problem you
are having. Meanwhile - does the "loop" button work for you? And, if
you have "Listening to Notes" set, can you hear yourself play while the
big pause is happening?


I have built the latest version from git and it still shows the same
behaviour. I guess that with "Listening to Notes" you refer to the
option "Play back entered notes immediately" under Preferences > Audio?
I have that set, and I hear the sound when entering notes during the
pause during playback. The loop button works, but there is a pause
between the repeated playbacks when the playback start marker is not at
the beginning.

Andreas



Re: Starting playback in the middle of a movement

2019-12-18 Thread Richard Shann
On Mon, 2019-12-16 at 19:39 +0100, Andreas Schneider wrote:
> On 2019-12-16 10:23, Richard Shann wrote:
> > On Sat, 2019-12-14 at 20:14 +0100, Andreas Schneider wrote:
> 
>  >> [...]
> > > Can you see therein what the problem may be?
> > 
> > No, this Ctrl-C has just interrupted some uninteresting part of the
> > loop - did you try it a few times to see if you could catch it
> > doing
> > something else? If so I'll look into the code to find a few places
> > to
> > try breaking in and finding whereabouts the long pause comes.
> 
> I have tried it a few times, but haven't seen anything interesting.
> 
> Example:
> 
> #0  0x75392819 in __GI___poll (fds=0x571b5470, nfds=3,
> timeout=9)
>  at ../sysdeps/unix/sysv/linux/poll.c:29
> #1  0x76269136 in  () at /usr/lib/x86_64-linux-gnu/libglib-
> 2.0.so.0
> #2  0x762694c2 in g_main_loop_run ()
>  at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
> #3  0x76a60b15 in gtk_main ()
>  at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
> #4  0x555ea26f in  ()
> #5  0x77e24753 in  () at
> /usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
> #6  0x77ed4250 in  () at
> /usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
> #7  0x77ea616e in  () at
> /usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
> #8  0x77ede563 in  () at
> /usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
> #9  0x77efd896 in  () at
> /usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
> #10 0x77e2f1ab in scm_call_4 ()
>  at /usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
> #11 0x77ed40a6 in scm_catch_with_pre_unwind_handler ()
>  at /usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
> #12 0x77ed4328 in scm_c_catch ()
>  at /usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
> #13 0x77e245a2 in  () at
> /usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
> #14 0x77e2486b in scm_c_with_continuation_barrier ()
>  at /usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
> #15 0x77ed101c in  () at
> /usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
> --Type  for more, q to quit, c to continue without paging--
> #16 0x77d53ef5 in GC_call_with_stack_base ()
>  at /usr/lib/x86_64-linux-gnu/libgc.so.1
> #17 0x77ed1105 in  () at
> /usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
> #18 0x77ed1145 in scm_with_guile ()
>  at /usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
> #19 0x5557bd5a in main ()
> 
> As it's random when Ctrl-C is pressed, it is maybe easier to build on
> what we know. For instance, it is striking that the output always
> states
> that playback starts at 0.0. Can you recommend a place to set a
> breakpoint to debug that further?

I've been looking at the code and I see a promising place for the
trouble to lie - I've made a change which may even fix the problem you
are having. Meanwhile - does the "loop" button work for you? And, if
you have "Listening to Notes" set, can you hear yourself play while the
big pause is happening?

Richard




Re: Starting playback in the middle of a movement

2019-12-17 Thread Richard Shann



On Mon, 2019-12-16 at 19:39 +0100, Andreas Schneider wrote:
> On 2019-12-16 10:23, Richard Shann wrote:
> > On Sat, 2019-12-14 at 20:14 +0100, Andreas Schneider wrote:
> 
>  >> [...]
> > > Can you see therein what the problem may be?
> > 
> > No, this Ctrl-C has just interrupted some uninteresting part of the
> > loop - did you try it a few times to see if you could catch it
> > doing
> > something else? If so I'll look into the code to find a few places
> > to
> > try breaking in and finding whereabouts the long pause comes.
> 
> I have tried it a few times, but haven't seen anything interesting.

This could be tricky to debug - the JACK backend is not something I
wrote, nor have I got a setup to use it. However we can try -
If you use Control-C to interrupt Denemo under gdb and then issue

b start_playing 
c

and the start play in the middle of a long piece it should hit the
breakpoint straight away. If not then I'll look into why not. But
assuming it does start straight away you can try the commands:

8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><

b src/audio/jackbackend.c:200
commands
p playback_frame
c
end
c

8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><

and then start play - it should start spewing out frame numbers. The
interest would be if this does happen straight away and what happens
when playing actually begins. 


Did you manage to run any older version of Denemo that you know used to
work?

The emails to you are not being delivered again this morning - you will
need to check the list archive to see what I've sent :(


Richard



> 
> Example:
> 
> #0  0x75392819 in __GI___poll (fds=0x571b5470, nfds=3,
> timeout=9)
>  at ../sysdeps/unix/sysv/linux/poll.c:29
> #1  0x76269136 in  () at /usr/lib/x86_64-linux-gnu/libglib-
> 2.0.so.0
> #2  0x762694c2 in g_main_loop_run ()
>  at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
> #3  0x76a60b15 in gtk_main ()
>  at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
> #4  0x555ea26f in  ()
> #5  0x77e24753 in  () at
> /usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
> #6  0x77ed4250 in  () at
> /usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
> #7  0x77ea616e in  () at
> /usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
> #8  0x77ede563 in  () at
> /usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
> #9  0x77efd896 in  () at
> /usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
> #10 0x77e2f1ab in scm_call_4 ()
>  at /usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
> #11 0x77ed40a6 in scm_catch_with_pre_unwind_handler ()
>  at /usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
> #12 0x77ed4328 in scm_c_catch ()
>  at /usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
> #13 0x77e245a2 in  () at
> /usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
> #14 0x77e2486b in scm_c_with_continuation_barrier ()
>  at /usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
> #15 0x77ed101c in  () at
> /usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
> --Type  for more, q to quit, c to continue without paging--
> #16 0x77d53ef5 in GC_call_with_stack_base ()
>  at /usr/lib/x86_64-linux-gnu/libgc.so.1
> #17 0x77ed1105 in  () at
> /usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
> #18 0x77ed1145 in scm_with_guile ()
>  at /usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
> #19 0x5557bd5a in main ()
> 
> As it's random when Ctrl-C is pressed, it is maybe easier to build on
> what we know. For instance, it is striking that the output always
> states
> that playback starts at 0.0. Can you recommend a place to set a
> breakpoint to debug that further?
> 
> Andreas



Re: Starting playback in the middle of a movement

2019-12-16 Thread Andreas Schneider

On 2019-12-16 10:23, Richard Shann wrote:

On Sat, 2019-12-14 at 20:14 +0100, Andreas Schneider wrote:

>> [...]

Can you see therein what the problem may be?


No, this Ctrl-C has just interrupted some uninteresting part of the
loop - did you try it a few times to see if you could catch it doing
something else? If so I'll look into the code to find a few places to
try breaking in and finding whereabouts the long pause comes.


I have tried it a few times, but haven't seen anything interesting.

Example:

#0  0x75392819 in __GI___poll (fds=0x571b5470, nfds=3,
timeout=9)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x76269136 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x762694c2 in g_main_loop_run ()
at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x76a60b15 in gtk_main ()
at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#4  0x555ea26f in  ()
#5  0x77e24753 in  () at
/usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
#6  0x77ed4250 in  () at
/usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
#7  0x77ea616e in  () at
/usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
#8  0x77ede563 in  () at
/usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
#9  0x77efd896 in  () at
/usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
#10 0x77e2f1ab in scm_call_4 ()
at /usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
#11 0x77ed40a6 in scm_catch_with_pre_unwind_handler ()
at /usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
#12 0x77ed4328 in scm_c_catch ()
at /usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
#13 0x77e245a2 in  () at
/usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
#14 0x77e2486b in scm_c_with_continuation_barrier ()
at /usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
#15 0x77ed101c in  () at
/usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
--Type  for more, q to quit, c to continue without paging--
#16 0x77d53ef5 in GC_call_with_stack_base ()
at /usr/lib/x86_64-linux-gnu/libgc.so.1
#17 0x77ed1105 in  () at
/usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
#18 0x77ed1145 in scm_with_guile ()
at /usr/lib/x86_64-linux-gnu/libguile-2.0.so.22
#19 0x5557bd5a in main ()

As it's random when Ctrl-C is pressed, it is maybe easier to build on
what we know. For instance, it is striking that the output always states
that playback starts at 0.0. Can you recommend a place to set a
breakpoint to debug that further?

Andreas



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

2019-12-16 Thread Richard Shann
On Sat, 2019-12-14 at 20:14 +0100, Andreas Schneider wrote:
> 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?

No, this Ctrl-C has just interrupted some uninteresting part of the
loop - did you try it a few times to see if you could catch it doing
something else? If so I'll look into the code to find a few places to
try breaking in and finding whereabouts the long pause comes.

Richard




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

2019-12-14 Thread 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: Starting playback in the middle of a movement

2019-12-14 Thread 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






Re: Starting playback in the middle of a movement

2019-12-11 Thread Richard Shann
On Wed, 2019-12-11 at 11:46 +0100, Andreas Schneider wrote:
> On 12/11/19 11:09 AM, Richard Shann wrote:
> > On Mon, 2019-12-09 at 20:28 +0100, Andreas Schneider wrote:
> > > On 2019-12-08 21:36, Richard Shann wrote:
> > > > On Sun, 2019-12-08 at 20:51 +0100, Andreas Schneider wrote:
> > > > > When moving the playback start marker away from the beginning
> > > > > of
> > > > > a
> > > > > piece
> > > > > (using the playback control), I encounter the new behaviour
> > > > > that
> > > > > after
> > > > > stating playback it takes quite a while until the actual
> > > > > playback
> > > > > starts, or more precisely it seems that it plays back
> > > > > silently
> > > > > from
> > > > > the
> > > > > beginning of the movement and starts producing sounds when it
> > > > > arrives
> > > > > at
> > > > > the playback start marker. At least I guess that from the
> > > > > time it
> > > > > takes
> > > > > to start playing. I assume that this is a bug?
> > > > 
> > > > I am not seeing that behaviour, and I don't think anything has
> > > > changed
> > > > for a long time in that area of the program. Are you seeing the
> > > > messages announcing the starting and ending of playback on the
> > > > console?
> > > > I just did a few tests
> > > > 
> > > > Denemo - MESSAGE : Starting playback
> > > > Denemo - MESSAGE : Starting playback at 28.005368
> > > > Here endeth a scripted playbackstarting audio playback at
> > > > 56.010664
> > > > Denemo - MESSAGE : Starting playback
> > > > Denemo - MESSAGE : Starting playback at 56.010664
> > > > Here endeth a scripted playbackDenemo - MESSAGE : Using channel
> > > > 0
> > > > prognum 0
> > > > Denemo - MESSAGE : Using channel 1 prognum 0
> > > > starting audio playback at 54.010402
> > > > Denemo - MESSAGE : Starting playback
> > > > Denemo - MESSAGE : Starting playback at 54.010402
> > > > Here endeth a scripted playback
> > > > 
> > > > I was setting the start place via the Playback Control green
> > > > "|"
> > > > button
> > > > but I am getting the same immediate response with Ctrl-F5 and
> > > > with
> > > > Ctrl-Alt-Drag of the start playback marker followed by F5
> > > 
> > > When starting playback, I get the messages
> > > 
> > > Denemo - MESSAGE : Starting playback
> > > Denemo - MESSAGE : Starting playback at 0.00
> > 
> > Do you get these two promptly when you start playback, or are they
> > delayed until playback actually starts?
> 
> 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).

> 
> > > Do you have a suggestion how to debug?
> > 
> > Are you able easily to run an old version of Denemo to check that
> > it is
> > something external and not some difference within your Denemo
> > binary?
> 
> Yes, I can just install some old Debian packages or build an old
> version. Is there a specific version you have in mind?

Well, I guess the last version you used which didn't show that
behaviour, but you could go a long way back before you would find a
version with different audio source code I think. You do realize you
don't need to install when you have built Denemo? You can execute it
directly from the src directory if you built without a --prefix in the
configure step. An older version would pick up the old .denemo-x.y.z if
you still have it around, otherwise it will create a new one and ignore
later .denemo-x.y.z files.

Richard







Re: Starting playback in the middle of a movement

2019-12-11 Thread Andreas Schneider
On 12/11/19 11:09 AM, Richard Shann wrote:
> On Mon, 2019-12-09 at 20:28 +0100, Andreas Schneider wrote:
>> On 2019-12-08 21:36, Richard Shann wrote:
>>> On Sun, 2019-12-08 at 20:51 +0100, Andreas Schneider wrote:
 When moving the playback start marker away from the beginning of
 a
 piece
 (using the playback control), I encounter the new behaviour that
 after
 stating playback it takes quite a while until the actual playback
 starts, or more precisely it seems that it plays back silently
 from
 the
 beginning of the movement and starts producing sounds when it
 arrives
 at
 the playback start marker. At least I guess that from the time it
 takes
 to start playing. I assume that this is a bug?
>>>
>>> I am not seeing that behaviour, and I don't think anything has
>>> changed
>>> for a long time in that area of the program. Are you seeing the
>>> messages announcing the starting and ending of playback on the
>>> console?
>>> I just did a few tests
>>>
>>> Denemo - MESSAGE : Starting playback
>>> Denemo - MESSAGE : Starting playback at 28.005368
>>> Here endeth a scripted playbackstarting audio playback at 56.010664
>>> Denemo - MESSAGE : Starting playback
>>> Denemo - MESSAGE : Starting playback at 56.010664
>>> Here endeth a scripted playbackDenemo - MESSAGE : Using channel 0
>>> prognum 0
>>> Denemo - MESSAGE : Using channel 1 prognum 0
>>> starting audio playback at 54.010402
>>> Denemo - MESSAGE : Starting playback
>>> Denemo - MESSAGE : Starting playback at 54.010402
>>> Here endeth a scripted playback
>>>
>>> I was setting the start place via the Playback Control green "|"
>>> button
>>> but I am getting the same immediate response with Ctrl-F5 and with
>>> Ctrl-Alt-Drag of the start playback marker followed by F5
>>
>> When starting playback, I get the messages
>>
>> Denemo - MESSAGE : Starting playback
>> Denemo - MESSAGE : Starting playback at 0.00
>
> Do you get these two promptly when you start playback, or are they
> delayed until playback actually starts?

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.

>> Do you have a suggestion how to debug?
>
> Are you able easily to run an old version of Denemo to check that it is
> something external and not some difference within your Denemo binary?

Yes, I can just install some old Debian packages or build an old
version. Is there a specific version you have in mind?

Andreas



Re: Starting playback in the middle of a movement

2019-12-11 Thread Richard Shann
On Mon, 2019-12-09 at 20:28 +0100, Andreas Schneider wrote:
> On 2019-12-08 21:36, Richard Shann wrote:
> > On Sun, 2019-12-08 at 20:51 +0100, Andreas Schneider wrote:
> > > When moving the playback start marker away from the beginning of
> > > a
> > > piece
> > > (using the playback control), I encounter the new behaviour that
> > > after
> > > stating playback it takes quite a while until the actual playback
> > > starts, or more precisely it seems that it plays back silently
> > > from
> > > the
> > > beginning of the movement and starts producing sounds when it
> > > arrives
> > > at
> > > the playback start marker. At least I guess that from the time it
> > > takes
> > > to start playing. I assume that this is a bug?
> > 
> > I am not seeing that behaviour, and I don't think anything has
> > changed
> > for a long time in that area of the program. Are you seeing the
> > messages announcing the starting and ending of playback on the
> > console?
> > I just did a few tests
> > 
> > Denemo - MESSAGE : Starting playback
> > Denemo - MESSAGE : Starting playback at 28.005368
> > Here endeth a scripted playbackstarting audio playback at 56.010664
> > Denemo - MESSAGE : Starting playback
> > Denemo - MESSAGE : Starting playback at 56.010664
> > Here endeth a scripted playbackDenemo - MESSAGE : Using channel 0
> > prognum 0
> > Denemo - MESSAGE : Using channel 1 prognum 0
> > starting audio playback at 54.010402
> > Denemo - MESSAGE : Starting playback
> > Denemo - MESSAGE : Starting playback at 54.010402
> > Here endeth a scripted playback
> > 
> > I was setting the start place via the Playback Control green "|"
> > button
> > but I am getting the same immediate response with Ctrl-F5 and with
> > Ctrl-Alt-Drag of the start playback marker followed by F5
> 
> When starting playback, I get the messages
> 
> Denemo - MESSAGE : Starting playback
> Denemo - MESSAGE : Starting playback at 0.00

Do you get these two promptly when you start playback, or are they
delayed until playback actually starts?
> 
> independent of where the playback start marker is. Playback ends with
> the message
> 
> Here endeth a scripted playback

Are you using JACK or Alsa?
> 
> Do you have a suggestion how to debug?

Are you able easily to run an old version of Denemo to check that it is
something external and not some difference within your Denemo binary?

Richard




Re: Starting playback in the middle of a movement

2019-12-09 Thread Andreas Schneider

On 2019-12-08 21:36, Richard Shann wrote:

On Sun, 2019-12-08 at 20:51 +0100, Andreas Schneider wrote:

When moving the playback start marker away from the beginning of a
piece
(using the playback control), I encounter the new behaviour that
after
stating playback it takes quite a while until the actual playback
starts, or more precisely it seems that it plays back silently from
the
beginning of the movement and starts producing sounds when it arrives
at
the playback start marker. At least I guess that from the time it
takes
to start playing. I assume that this is a bug?


I am not seeing that behaviour, and I don't think anything has changed
for a long time in that area of the program. Are you seeing the
messages announcing the starting and ending of playback on the console?
I just did a few tests

Denemo - MESSAGE : Starting playback
Denemo - MESSAGE : Starting playback at 28.005368
Here endeth a scripted playbackstarting audio playback at 56.010664
Denemo - MESSAGE : Starting playback
Denemo - MESSAGE : Starting playback at 56.010664
Here endeth a scripted playbackDenemo - MESSAGE : Using channel 0
prognum 0
Denemo - MESSAGE : Using channel 1 prognum 0
starting audio playback at 54.010402
Denemo - MESSAGE : Starting playback
Denemo - MESSAGE : Starting playback at 54.010402
Here endeth a scripted playback

I was setting the start place via the Playback Control green "|" button
but I am getting the same immediate response with Ctrl-F5 and with
Ctrl-Alt-Drag of the start playback marker followed by F5


When starting playback, I get the messages

Denemo - MESSAGE : Starting playback
Denemo - MESSAGE : Starting playback at 0.00

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

Here endeth a scripted playback

Do you have a suggestion how to debug?

Andreas



Re: Starting playback in the middle of a movement

2019-12-08 Thread Richard Shann
On Sun, 2019-12-08 at 20:51 +0100, Andreas Schneider wrote:
> When moving the playback start marker away from the beginning of a
> piece
> (using the playback control), I encounter the new behaviour that
> after
> stating playback it takes quite a while until the actual playback
> starts, or more precisely it seems that it plays back silently from
> the
> beginning of the movement and starts producing sounds when it arrives
> at
> the playback start marker. At least I guess that from the time it
> takes
> to start playing. I assume that this is a bug?

I am not seeing that behaviour, and I don't think anything has changed
for a long time in that area of the program. Are you seeing the
messages announcing the starting and ending of playback on the console?
I just did a few tests 

Denemo - MESSAGE : Starting playback
Denemo - MESSAGE : Starting playback at 28.005368
Here endeth a scripted playbackstarting audio playback at 56.010664
Denemo - MESSAGE : Starting playback
Denemo - MESSAGE : Starting playback at 56.010664
Here endeth a scripted playbackDenemo - MESSAGE : Using channel 0
prognum 0
Denemo - MESSAGE : Using channel 1 prognum 0
starting audio playback at 54.010402
Denemo - MESSAGE : Starting playback
Denemo - MESSAGE : Starting playback at 54.010402
Here endeth a scripted playback

I was setting the start place via the Playback Control green "|" button
but I am getting the same immediate response with Ctrl-F5 and with
Ctrl-Alt-Drag of the start playback marker followed by F5

Richard




Starting playback in the middle of a movement

2019-12-08 Thread Andreas Schneider

When moving the playback start marker away from the beginning of a piece
(using the playback control), I encounter the new behaviour that after
stating playback it takes quite a while until the actual playback
starts, or more precisely it seems that it plays back silently from the
beginning of the movement and starts producing sounds when it arrives at
the playback start marker. At least I guess that from the time it takes
to start playing. I assume that this is a bug?

Andreas