Re: Crackling sound when changing Slowdown slider in Playback Control

2021-10-30 Thread Lib Lists
On Sat, 30 Oct 2021 at 19:53, Richard Shann  wrote:
>
> On Sat, 2021-10-30 at 19:18 +0300, Lib Lists wrote:
> > Hi,
> > (Listen to the attached .mp3) When I change the Slowdown value in the
> > Playback Control (in this case to 1,2) I get this crackling sound. At
> > speed = 1 everything works fine. I thought the slider would change
> > the
> > BPM but it seems it tries to stretch the audio in real-time, am I
> > right?
>
> Yes, to change the BPM you use the button at the other end of the line
> where the BPM is given.
>
> The slowdown slider does real-time slowdown of the audio output, so
> everything, the attack, the decay all is slowed down. The quality isn't
> as good as when not slowed down but it doesn't have the type of
> distortion in your example. I take it you haven't got the volume too
> high? I was thinking it may just be a question of raw computing power,
> but I just tested it on a dual core 1.5GHz Asus laptop under Windows
> and it worked fine. That machine takes an age to typeset or do anything
> much.

No, the volume is not too high. However, I'm using Linux under
VirtualBox and I'm wondering if that could be the cause of this
problem.

> Anyone else tried the slowdown feature? (It's really for people
> transcribing from audio source - you load the audio and then it's handy
> to slow it down sometimes as you transcribe).
>
> Richard
>



Re: Crackling sound when changing Slowdown slider in Playback Control

2021-10-30 Thread Richard Shann
On Sat, 2021-10-30 at 19:18 +0300, Lib Lists wrote:
> Hi,
> (Listen to the attached .mp3) When I change the Slowdown value in the
> Playback Control (in this case to 1,2) I get this crackling sound. At
> speed = 1 everything works fine. I thought the slider would change
> the
> BPM but it seems it tries to stretch the audio in real-time, am I
> right?

Yes, to change the BPM you use the button at the other end of the line
where the BPM is given. 

The slowdown slider does real-time slowdown of the audio output, so
everything, the attack, the decay all is slowed down. The quality isn't
as good as when not slowed down but it doesn't have the type of
distortion in your example. I take it you haven't got the volume too
high? I was thinking it may just be a question of raw computing power,
but I just tested it on a dual core 1.5GHz Asus laptop under Windows
and it worked fine. That machine takes an age to typeset or do anything
much.
Anyone else tried the slowdown feature? (It's really for people
transcribing from audio source - you load the audio and then it's handy
to slow it down sometimes as you transcribe).

Richard




[bug #61360] Want an easy way to get transposed playback

2021-10-30 Thread Richard Shann
Update of bug #61360 (project denemo):

  Status:None => Invalid
 Open/Closed:Open => Closed 

___

Follow-up Comment #1:

Command: Transpose on Playback
Sets the MIDI transpose on each staff of the current movement up or down by
the number of semitones given.
Location: Object Menu ▶ Movements ▶ Playback
Internal Name: TransposeOnPlayback

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/




[bug #61382] When saving recording, need alert when Denemo is saving it.

2021-10-30 Thread Richard Shann
Update of bug #61382 (project denemo):

  Status:None => Fixed  
 Open/Closed:Open => Closed 

___

Follow-up Comment #1:

There is a progress bar and the display does not freeze now.

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/




[bug #61400] Ambitus not displayed in parts

2021-10-30 Thread Richard Shann
Update of bug #61400 (project denemo):

  Status:   Postponed => Fixed  
 Open/Closed:Open => Closed 

___

Follow-up Comment #2:

I occurred to me that this is just the sort of situation where you might want
to use an Inclusion Criterio - switching between typesetting ambitus or not.
So I've retired the Print with Ambitus command and instead have created:

Command: Ambitus
Typesets the Ambitus of each staff at the start of the first system. This can
then be turned off by the Inclusion Criterion Ambitus in the Print View.
Location: Object Menu ▶ Score ▶ Typesetter
Internal Name: AllowAmbitus



___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/




Re: Volume control on playback

2021-10-30 Thread Lib Lists
On Fri, 29 Oct 2021 at 16:30, Richard Shann  wrote:
>
> On Fri, 2021-10-29 at 13:24 +0300, Lib Lists wrote:
> > A note on the visual appearance of the Playback Control buttons. At
> > first it was confusing for me to find the play and stop buttons as
> > they are light grey on a light grey background. The record button
> > also
> > was hard to find as it is black, and that's not the colour I usually
> > associate with a recording button. Same with play, that I usually
> > associate with green or with the most visible button. However, I see
> > that green and red are used for the playback markers. I'd probably
> > make the stop button black, the play button green (and orange when
> > paused) and the record button red.
>
> The record button is red for me, which hints that the problem is
> "theming" - the idea that people can choose a color scheme to suit
> themselves. As it clearly doesn't work, I've replaced the themed icons
> with (rather crude) textual labels which hopefully will show up well.
>
> Richard
>

Thank you,
now it looks good!
Maybe I prefer the old look of the playback starting and ending point
arrows, as they looked different from the play button.
In any case now the play-stop-rec buttons are really good, thank you.

Lib


[bug #61400] Ambitus not displayed in parts

2021-10-30 Thread Richard Shann
Update of bug #61400 (project denemo):

  Status:None => Postponed  

___

Follow-up Comment #1:

Yes, the command Print with Ambitus creates a custom layout with ambitus set
on every staff in every movement (while leaving the default layouts
untouched). So to create a part with ambitus you need to execute the staff
ambitus command mentioned below.

While looking into this I stumbled across a bug:

If I take a new empty score insert c'' and c''' and execute the command:

Command: Print with Ambitus
Prints the score printing the range (ambitus) of each part at the start of the
staff
Location: Main Menu ▶ File ▶ Print
Internal Name: PrintWithAmbitus

Then a custom layout called "Ambitus" is created and typesets the staff with
ambitus showing c'' to c'''

If I start again with a new score, c'' and c''' and execute the command:

Command: (Print) Ambitus (On/Off)
Toggle the ambitus engraver for this staff on or off
Location: Object Menu ▶ Staffs/Voices ▶ Staff Properties
Internal Name: Ambitus

Then typeset the default layout it again typesets with ambitus.
If I re-execute that command (so toggling the ambitus off) and typeset then
the ambitus is gone as expected. However if I then re-execute the first
command (Print with Ambitus) the ambitus is *not* set in the custom layout as
it was when I first executed that command. This is strange as there does not
appear to be any difference in the scores - the difference must lie in cached
values for the score layout. Workaround is to Reload Score before creating the
Ambitus custom layout.



___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/