1/24 in Allabreve

[Simon Albrecht]

Hello everybody,

I just noticed that Lily by default beams semiquaver triplets in 2/2 
time 12 and 12, i.e. by half measure. That seems clumsy to me, and I’d 
vote for beaming them 6+6+6+6 by default. Any opinions?


Best, Simon

PS. Found this in Schubert, D 672, m.18ff.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: lilypond syntax for markdown pigments codehilite

[Noeck]

Hi all,

I found it: ly.colorize.HtmlWriter was what I was looking for. Thanks
for all the hints.

Cheers,
Joram

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: lilypond syntax for markdown pigments codehilite

[Noeck]

Hi Urs,

Am 01.06.2016 um 19:57 schrieb Urs Liska:
> If any of these sounds interesting I can give you more details.

Yes. I am currently looking into python-ly (document, colorize). It
seems like there is something to be found. But if you have a link how to
do this:

html_with_pgyment_classes = somefunction(lilypondcode)

or

doc = Document(lilypondcode)
doc.export2html()

or similar, that would be very much appreciated (inside python-ly or
your github code). I am more interested in python code than js, but the
wrapper could also give a hint.

Best,
Joram

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: lilypond syntax for markdown pigments codehilite

[Urs Liska]

Am 1. Juni 2016 19:28:40 MESZ, schrieb tisimst :
>On Wed, Jun 1, 2016 at 11:21 AM, Noeck [via Lilypond] <
>ml-node+s1069038n191304...@n5.nabble.com> wrote:
>
>> Hi,
>>
>> does anybody have a lilypond style for pigments codehilite?
>>
>> What I am able to do with python markdown is this:
>>
>> ```python
>> if i == 0:
>> print(i)
>> ```
>> and I get an html file with classes to style the code block.
>>
>> What I want to do is the same with lilypond code:
>> ```lilypond
>> \relative { a'4 c }
>> ```
>>
>> I assume I could add some kind of config file with the lilypond
>keywords
>> and other syntactic elements to the markdown codehilite extension
>> settings.
>>
>> Has anybody done that before?
>> Does Frescobaldi do something similar to highlight the code?
>> Or lilypondblog?
>>
>
>On lilypondblog and my blog, we both use a CSS file that defines the
>classes and then use Frescobaldi to export the input file as properly
>classified html.

This can also be done on the command line using the python-ly package.

I have also written a Node module wrapper for that. 
And a plugin for Gitbook.

If any of these sounds interesting I can give you more details.

Best
Urs

>
>HTH,
>Abraham
>
>
>
>
>--
>View this message in context:
>http://lilypond.1069038.n5.nabble.com/lilypond-syntax-for-markdown-pigments-codehilite-tp191304p191305.html
>Sent from the User mailing list archive at Nabble.com.
>
>
>
>___
>lilypond-user mailing list
>lilypond-user@gnu.org
>https://lists.gnu.org/mailman/listinfo/lilypond-user

-- 
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: lilypond syntax for markdown pigments codehilite

[Noeck]

Am 01.06.2016 um 19:28 schrieb tisimst:
> On lilypondblog and my blog, we both use a CSS file that defines the
> classes and then use Frescobaldi to export the input file as properly
> classified html.

Thanks, Abraham. That's good to know. Probably, my assumption that
surely you, Urs, et al. did this before, is wrong then.

But I will have a look at the Frescobaldi html export.

Cheers,
Joram




___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: lilypond syntax for markdown pigments codehilite

[tisimst]

On Wed, Jun 1, 2016 at 11:21 AM, Noeck [via Lilypond] <
ml-node+s1069038n191304...@n5.nabble.com> wrote:

> Hi,
>
> does anybody have a lilypond style for pigments codehilite?
>
> What I am able to do with python markdown is this:
>
> ```python
> if i == 0:
> print(i)
> ```
> and I get an html file with classes to style the code block.
>
> What I want to do is the same with lilypond code:
> ```lilypond
> \relative { a'4 c }
> ```
>
> I assume I could add some kind of config file with the lilypond keywords
> and other syntactic elements to the markdown codehilite extension
> settings.
>
> Has anybody done that before?
> Does Frescobaldi do something similar to highlight the code?
> Or lilypondblog?
>

On lilypondblog and my blog, we both use a CSS file that defines the
classes and then use Frescobaldi to export the input file as properly
classified html.

HTH,
Abraham




--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/lilypond-syntax-for-markdown-pigments-codehilite-tp191304p191305.html
Sent from the User mailing list archive at Nabble.com.___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

lilypond syntax for markdown pigments codehilite

[Noeck]

Hi,

does anybody have a lilypond style for pigments codehilite?

What I am able to do with python markdown is this:

```python
if i == 0:
print(i)
```
and I get an html file with classes to style the code block.

What I want to do is the same with lilypond code:
```lilypond
\relative { a'4 c }
```

I assume I could add some kind of config file with the lilypond keywords
and other syntactic elements to the markdown codehilite extension settings.

Has anybody done that before?
Does Frescobaldi do something similar to highlight the code?
Or lilypondblog?

Thanks for any pointers,
Joram

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: keyboard graphic

[Phil Holmes]

- Original Message - 
From: "Jim Tisdall" 

To: 
Sent: Wednesday, June 01, 2016 3:14 PM
Subject: keyboard graphic



I need to display small graphics of a piano keyboard with selected
notes indicated by color.

It will be used similarly as the guitar fret diagrams and actually
in conjunction with them (and with standard and tablature notation,
and explanatory comments) as guitarists examine chord voicings.

I've found a few things but thought I'd ask here if some lilypond user
has developed such a graphic in the system.  Or, an expert advice on
where to begin to develop one myself within lilypond, would be most
appreciated.

My wish list is parameters for range, width/height, and pressed keys;
labels under the pressed keys would be a nice plus.

Thanks,
Jim



Attached is a piano-key version, which is nowhere near as cleverly automatic 
as I remember David's version being, but may give you some further pointers 
about how this can be done.


(I used this at college when I had to play the marimba, xylophone or 
glockenspiel.)


--
Phil Holmes 
\version "2.17.28"
\pointAndClickOff

#(define KEY-POS-LIST '(   
   (c.1) (cis  .  1.5) (des . 1.5) (d.2) (dis  .  2.5) (ees  .  2.5) (e   .  3) 
   (f.4) (fis  .  4.5) (ges . 4.5) (g.5) (gis  .  5.5) (aes  .  5.5) (a   .  6) 
   (ais  .  6.5) (bes  .  6.5) (b   .   7)))

#(define (black-key? num )
   (member num '(cis  des  dis  ees  fis  ges  gis  aes  ais  bes)) )

#(define (key-to-pos key ypos scale)
  (let ((keypos (assq key KEY-POS-LIST)))
   (if (not keypos)
(ly:error (_ "keyboard diagram error - unknown note '~a'") key)
(cons (* (- (cdr (assq key KEY-POS-LIST)) 0.5) scale) (+ (* (- scale 1) 0.32) ypos)

#(define (make-keys l1 width off height scale)
   (if (null? l1) 
   empty-stencil
   (ly:stencil-add 
  (ly:stencil-translate
(make-line-stencil 0.1 0 0 0 height) 
   (cons (* (- (car l1) 1) scale) off ))
  (make-keys (cdr l1) width off height scale

#(define (make-keys-black l1 width off height scale)
   (if (null? l1) 
   empty-stencil
   (ly:stencil-add 
  (ly:stencil-translate
(ly:round-filled-box `(0 . ,(* width scale)) `(0 . ,height) 0) 
   (cons (* (- (car l1) (/ width 2)) scale )  off))
  (make-keys-black (cdr l1) width off height scale

#(define (make-dot key scale)
  (if (black-key? key)
(ly:stencil-in-color 
  (ly:stencil-translate (make-circle-stencil  (* 0.27 scale) 0 #t) (key-to-pos key 2.5 scale)) 1 1 1)
(ly:stencil-translate (make-circle-stencil  (* 0.32 scale) 0 #t) (key-to-pos key 0.5 scale)) ))

#(define (make-dot-list l1 scale)
   (if (null? l1) 
   empty-stencil
   (ly:stencil-add 
  (make-dot (car l1) scale)
  (make-dot-list (cdr l1) scale 

#(define-markup-command (keys layout props arg1 arg2) (list? number?) 
(ly:stencil-add
  (make-line-stencil 0.1 0 0 (* 7 arg2) 0)
  (make-line-stencil 0.1 0 6 (* 7 arg2)  6)
  (make-keys   '(1 2 3 4 5 6 7 8) 10 6 arg2)
  (make-keys-black '(1 2   4 5 6) 0.65 2 4 arg2)
  (make-dot-list arg1 arg2)))

key_scale=1.9

\relative c' {
  \textLengthOn
  c4 ^\markup \keys #'(c) #key_scale
  cis ^\markup \keys #'(cis) #key_scale
  d ^\markup \keys #'(d) #key_scale
  ees ^\markup \keys #'(ees) #key_scale
  e ^\markup \keys #'(e) #key_scale
  f ^\markup \keys #'(f) #key_scale
  fis ^\markup \keys #'(fis) #key_scale
  g ^\markup \keys #'(g) #key_scale
  gis ^\markup \keys #'(gis) #key_scale
  a ^\markup \keys #'(a) #key_scale
  bes ^\markup \keys #'(bes) #key_scale
  b ^\markup \keys #'(b) #key_scale
}___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: keyboard graphic

[David Kastrup]

Jim Tisdall  writes:

> I need to display small graphics of a piano keyboard with selected
> notes indicated by color.
>
> It will be used similarly as the guitar fret diagrams and actually
> in conjunction with them (and with standard and tablature notation,
> and explanatory comments) as guitarists examine chord voicings.
>
> I've found a few things but thought I'd ask here if some lilypond user
> has developed such a graphic in the system.  Or, an expert advice on
> where to begin to develop one myself within lilypond, would be most
> appreciated.
>
> My wish list is parameters for range, width/height, and pressed keys;
> labels under the pressed keys would be a nice plus.

Here is something that is not a piano keyboard but has the advantage
that it works automatically.  You'll need to redo the graphics, of
course.

\version "2.18.0"

#(define (c-griff start end pressed)
   (define (add-circle prev n filled?)
 #{ \markup \combine #prev
	\translate #(cons (- 3 (modulo n 3))
			  (- (/ n 3)))
	   \draw-circle #0.35 #0.1 #filled? #})
   (let loop ((i start)
	  (m #{ \markup \null #})
	  (pressed (member start (sort pressed <) <=)))
 (if (> i end)
	 m
	 (loop (1+ i)
	   (add-circle m
			   (- i (- start (modulo start 3)))
			   (and (pair? pressed) (= (car pressed) i)))
	   (and pressed (member i pressed <))

Dia_engraver =
#(define-scheme-function ((parser location low hi) context)
   (ly:pitch? ly:pitch?)
 (let ((pitches '()) (cause #f))
   (make-engraver
	((start-translation-timestep engraver)
	 (set! pitches '())
	 (set! cause #f))
	(listeners
	 ((note-event engraver event)
	  (set! pitches (cons (ly:event-property event 'pitch) pitches))
	  (if (not cause)
	  (set! cause event
	((process-music engraver)
	 (if cause
	 (let ((g (ly:engraver-make-grob engraver 'LyricText cause)))
	   (set! (ly:grob-property g 'text)
		 (c-griff (ly:pitch-semitones low)
			  (ly:pitch-semitones hi)
			  (map ly:pitch-semitones pitches)

#(use-modules (scm accreg))

treble =
\relative {
  \tag full \clef "treble"  \discant "10"
  r8 s32 f'[ bes f] s e[ a e] s d[ g d] s16 e32[ a]
  \discant "121"
  << { r16  r  r  } \tag full \\
 { d r a r bes r } >> |
  1
}

\new PianoStaff
<<
  \new Lyrics \with { \consists \Dia_engraver a b' }
  \removeWithTag full \treble
  \new Staff \treble
  \new Staff \relative
  { \clef "treble"  \freeBass "1"
r8 d'32 s16. c32 s16. bes32 s16. a32[ cis] s16
\clef "bass"  \stdBass "Master"
<< { r16 ^"b" r ^"am" r ^"gm" |
 1^"a" } \\
   { d8_"D" c_"C" bes_"B" | a1_"A" }
>>
  }
>>


-- 
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

keyboard graphic

[Jim Tisdall]

I need to display small graphics of a piano keyboard with selected
notes indicated by color.

It will be used similarly as the guitar fret diagrams and actually
in conjunction with them (and with standard and tablature notation,
and explanatory comments) as guitarists examine chord voicings.

I've found a few things but thought I'd ask here if some lilypond user
has developed such a graphic in the system.  Or, an expert advice on
where to begin to develop one myself within lilypond, would be most
appreciated.

My wish list is parameters for range, width/height, and pressed keys;
labels under the pressed keys would be a nice plus.

Thanks,
Jim

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Harmonic notehead style

[Andrew Bernard]

Hi Paul,

Thanks so much for this. That has given me the impetus and understanding to
code my solution. In your context you are using an engraver, so you simply
omit the notehead styles such as harmonic. In my case, I am overriding the
notehead stencil to draw my own custom shapes, and so what I do now is to
check when the style is ‘harmonic and provide my own drawing routine for
that, rather than omitting it. This is really perfect, because the whole
point of my custom override is to generate a very particular look and feel
for my composer’s noteheads, and other stylistic appearance considerations.

Yet again, thanks!

Andrew


On 1 June 2016 at 10:38:18 PM, Paul wrote:


Yes, you'll want to check the 'style property of the note head grob and
when it is 'harmonic then leave the default stencil alone (or provide your
own harmonic note head stencil).  There are a number of different note head
styles like this.  See my custom note head engraver below (for Clairnote
music notation[1]) which just leaves the default stencil in place for a
given list of styles.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Harmonic notehead style

[Paul]

Hi Andrew,

On 05/31/2016 09:48 PM, Andrew Bernard wrote:
I am using a custom stencil for noteheads, to achieve a certain look 
and ellipticity and rotation compared to the default noteheads. 
Suddenly doing a guitar piece I have to use \harmonic style and this 
does not have any effect when using a custom notehead symbol.


Do I need to add scheme code in my stencil function to take cognisance 
of the \harmonic style instruction and also draw my own shapes for 
that, or am I missing something?


Yes, you'll want to check the 'style property of the note head grob and 
when it is 'harmonic then leave the default stencil alone (or provide 
your own harmonic note head stencil).  There are a number of different 
note head styles like this.  See my custom note head engraver below (for 
Clairnote music notation[1]) which just leaves the default stencil in 
place for a given list of styles.


HTH,
-Paul

[1] http://clairnote.org/software/

#(define Cn_note_heads_engraver
;; Customizes stencil, stencil-width, stem-attachment, rotation.
(make-engraver
 (acknowledgers
  ((note-head-interface engraver grob source-engraver)
   ;; make sure \omit is not in effect (i.e. stencil is not #f)
   ;; and do nothing for certain notehead styles
   (if
(and
 (ly:grob-property-data grob 'stencil)
 (not (memq (ly:grob-property-data grob 'style)
(list 'harmonic 'harmonic-black 'harmonic-mixed
  'diamond 'cross 'xcircle 'triangle 'slash
;; TODO: better handling of various notehead styles
;; http://lilypond.org/doc/v2.18/Documentation/notation/note-head-styles
;; output-lib.scm
(let*
 ((context (ly:translator-context engraver))
  (black-note (= 0 (modulo (cn-notehead-semitone grob) 2)))
  (dur-log (ly:grob-property grob 'duration-log))
  (stil-proc (ly:context-property context 'cnNoteheadStencilProcedure))
  (width-scale (ly:context-property context 'cnNoteheadWidthScale 1))
  (height-scale (ly:context-property context 'cnNoteheadHeightScale 1))
  (rot (ly:context-property context 'cnNoteheadRotation #f))
  (stem-attach (ly:context-property context 'cnStemAttachment #f)))

 (ly:grob-set-property! grob 'stencil
   (stil-proc grob context black-note dur-log))

 (if (>= dur-log 1)
 (if (not (and (= 1 width-scale) (= 1 height-scale)))
 (ly:grob-set-property! grob 'stencil
   (ly:stencil-scale
(ly:grob-property grob 'stencil)
width-scale height-scale

 (if (and rot (>= dur-log 1))
 (ly:grob-set-property! grob 'rotation (list rot 0 0)))

 (if (and stem-attach (>= dur-log 1))
 (ly:grob-set-property! grob 'stem-attachment
   (if black-note
   (car stem-attach)
   (cdr stem-attach
 ))


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Spare SSD anybody?

[David Kastrup]

Alexander Kobel  writes:

> recently I was afraid about my SSD for the same reason, so I asked our
> institute's IT service staff who cares for some dozens (hundreds?) of
> laptops and desktops with SSDs.
>
> They say that even power users of hibernation with high rate of data
> turnover didn't manage to damage their SSDs lately; the horror stories
> for the first generations of SSDs seem not to apply anymore.

Well, I am not sure I have significantly later than first generation...

=== START OF INFORMATION SECTION ===
Model Family: Samsung based SSDs
Device Model: SAMSUNG SSD PM810 2.5" 7mm 128GB
Serial Number:S0NRNEAB524258
LU WWN Device Id: 5 f0 0
Firmware Version: AXM08D1Q
User Capacity:128,035,676,160 bytes [128 GB]
Sector Size:  512 bytes logical/physical
Rotation Rate:Solid State Device
Device is:In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS, ATA/ATAPI-7 T13/1532D revision 1
SATA Version is:  SATA 2.6, 3.0 Gb/s (current: 1.5 Gb/s)
Local Time is:Wed Jun  1 12:23:20 2016 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

> You still have to take a bit of care (try to have some empty space,
> and run fstrim once in a while), but other than that you should be
> fine.  As you experienced, the SMART information is rather unhelpful
> unless you have additional context by the manufacturer; more often
> than not, the only semi-reliable source are the manufacturer's own
> toolkits (which, unfortunately, are hardly available on Linux).

> That being said: which form factor/connector do you need?

SATA, 2.5".

> I can ask if I can grab something. Many parts from few-year old
> machines are sorted out regularly here. Not sure about hard disks,
> though - there might be regulations for data protection that prevent
> them from giving out old drives.

Sure, it would be nice to keep in mind.  I'm not really sure what the
expected lifetime of the disk I have is.  Maybe I just need to keep
making backups in sane intervals and otherwise am still fine.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Spare SSD anybody?

[Phil Holmes]

- Original Message - 
From: "Michael Hendry" 

To: "David Kastrup" 
Cc: ; 
Sent: Wednesday, June 01, 2016 10:44 AM
Subject: Re: Spare SSD anybody?


Surely an SSD is entirely Solid State, so can’t wear out in the way a 
mechanical device does.


Wrong. 
http://techreport.com/review/27909/the-ssd-endurance-experiment-theyre-all-dead


--
Phil Holmes 



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Spare SSD anybody?

[David Kastrup]

Michael Hendry  writes:

>> On 1 Jun 2016, at 10:07, David Kastrup  wrote:
>> 
>> David Kastrup  writes:
>> 
>>> Hi,
>>> 
>>> my current development SSD, graciously donated by James, currently has
>>> the following readings:
>>> 
>>> Vendor Specific SMART Attributes with Thresholds:
>>> ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED
>>> RAW_VALUE
>>>  5 Reallocated_Sector_Ct 0x0033 099 099 --- Pre-fail Always - 13
>>>  9 Power_On_Hours 0x0032 094 094 --- Old_age Always - 25748
>> 
>> Ok, I might have been panicking because of all the lines with "Pre-fail"
>> and "Old_age" but they only indicate the _category_ of the respective
>> settings.  Sorry for that.
>> 
>> I'm still trying to figure out the readings as such though.  The
>> "documentation" including online is not much help.
>
>
> Surely an SSD is entirely Solid State, so can’t wear out in the way a
> mechanical device does.

Seriously?  .  Which is
why SSD drives are great for servers and are put through the mills as
swap drive.

> Eventually, I suppose, even solid state devices will fail, but I doubt
> that SMART monitoring will give you advance warning of this.

It can keep track of the individual block wear pretty well, and the
average number of reliable block erasures is also known.  So failures
are not _exceptional_ but predictable.  So storage deterioration is
predictable as well as monitorable (either CRC errors or uncleared bits
directly after erasure).  You can get a hint about the bearings of a
rotating disk by monitoring its spinup (and noticing irregularities in
operation) but actual failures tend to come suddenly as platter damage
affecting an area.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Spare SSD anybody?

[Michael Hendry]

> On 1 Jun 2016, at 10:58, Phil Holmes  wrote:
> 
> - Original Message - From: "Michael Hendry" 
> To: "David Kastrup" 
> Cc: ; 
> Sent: Wednesday, June 01, 2016 10:44 AM
> Subject: Re: Spare SSD anybody?
> 
> 
>> Surely an SSD is entirely Solid State, so can’t wear out in the way a 
>> mechanical device does.
> 
> Wrong. 
> http://techreport.com/review/27909/the-ssd-endurance-experiment-theyre-all-dead


Damn! Should have done some Googling before making a fool of myself!

M


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Spare SSD anybody?

[Alexander Kobel]

On 2016-06-01 11:07, David Kastrup wrote:

David Kastrup  writes:


Hi,

my current development SSD, graciously donated by James, currently has
the following readings:

Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME  FLAG VALUE WORST THRESH TYPE  UPDATED  
WHEN_FAILED RAW_VALUE
   5 Reallocated_Sector_Ct   0x0033   099   099   ---Pre-fail  Always   
-   13
   9 Power_On_Hours  0x0032   094   094   ---Old_age   Always   
-   25748


Ok, I might have been panicking because of all the lines with "Pre-fail"
and "Old_age" but they only indicate the _category_ of the respective
settings.  Sorry for that.

I'm still trying to figure out the readings as such though.  The
"documentation" including online is not much help.


Hi David,

recently I was afraid about my SSD for the same reason, so I asked our 
institute's IT service staff who cares for some dozens (hundreds?) of 
laptops and desktops with SSDs.


They say that even power users of hibernation with high rate of data 
turnover didn't manage to damage their SSDs lately; the horror stories 
for the first generations of SSDs seem not to apply anymore. You still 
have to take a bit of care (try to have some empty space, and run fstrim 
once in a while), but other than that you should be fine.
As you experienced, the SMART information is rather unhelpful unless you 
have additional context by the manufacturer; more often than not, the 
only semi-reliable source are the manufacturer's own toolkits (which, 
unfortunately, are hardly available on Linux).


However, there have been a few reports in the past about shaky power 
supply for the disks, probably when laptop batteries grow older. Some 
SSDs cope with that without problems, others are very sensitive to 
voltage differences (?) and suddenly become unstable. Signs of this 
behavior are ATA warning messages concerning the "ATA interface" in 
dmesg output, such as those:

  https://lime-technology.com/wiki/index.php/The_Analysis_of_Drive_Issues
Quote: "There have been too many cases of drives thrown out or returned 
by an RMA process, when the problem was just a bad cable!" - which 
exactly matches the experience of our IT.
If drives barf out for those reason, they have always been able to copy 
the contents with an external adapter - annoying, but not dangerous.



That being said: which form factor/connector do you need? I can ask if I 
can grab something. Many parts from few-year old machines are sorted out 
regularly here. Not sure about hard disks, though - there might be 
regulations for data protection that prevent them from giving out old 
drives.



Cheers,
Alexander

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Spare SSD anybody?

[Michael Hendry]

> On 1 Jun 2016, at 10:07, David Kastrup  wrote:
> 
> David Kastrup  writes:
> 
>> Hi,
>> 
>> my current development SSD, graciously donated by James, currently has
>> the following readings:
>> 
>> Vendor Specific SMART Attributes with Thresholds:
>> ID# ATTRIBUTE_NAME  FLAG VALUE WORST THRESH TYPE  UPDATED  
>> WHEN_FAILED RAW_VALUE
>>  5 Reallocated_Sector_Ct   0x0033   099   099   ---Pre-fail  Always  
>>  -   13
>>  9 Power_On_Hours  0x0032   094   094   ---Old_age   Always  
>>  -   25748
> 
> Ok, I might have been panicking because of all the lines with "Pre-fail"
> and "Old_age" but they only indicate the _category_ of the respective
> settings.  Sorry for that.
> 
> I'm still trying to figure out the readings as such though.  The
> "documentation" including online is not much help.


Surely an SSD is entirely Solid State, so can’t wear out in the way a 
mechanical device does.

Eventually, I suppose, even solid state devices will fail, but I doubt that 
SMART monitoring will give you advance warning of this.

Michael
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Spare SSD anybody?

[David Kastrup]

David Kastrup  writes:

> Hi,
>
> my current development SSD, graciously donated by James, currently has
> the following readings:
>
> Vendor Specific SMART Attributes with Thresholds:
> ID# ATTRIBUTE_NAME  FLAG VALUE WORST THRESH TYPE  UPDATED  
> WHEN_FAILED RAW_VALUE
>   5 Reallocated_Sector_Ct   0x0033   099   099   ---Pre-fail  Always  
>  -   13
>   9 Power_On_Hours  0x0032   094   094   ---Old_age   Always  
>  -   25748

Ok, I might have been panicking because of all the lines with "Pre-fail"
and "Old_age" but they only indicate the _category_ of the respective
settings.  Sorry for that.

I'm still trying to figure out the readings as such though.  The
"documentation" including online is not much help.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Σχετ: Arrow Accidentals Code Error v.2.19

[dtsmarin]

Thanks Abraham, I was missing a line of code that caused the error and not the 
parser since I fixed this a while ago.
 

Στις 8:39 π.μ. Τετάρτη, 1 Ιουνίου 2016, ο/η tisimst [via Lilypond] 
 έγραψε:
 

  On Tue, May 31, 2016 at 6:58 PM, dtsmarin [via Lilypond] <[hidden email]> 
wrote:

 Hi everyone,
this code doesn't work anymore. Any ideas why?
http://lsr.di.unimi.it/LSR/Snippet?id=784


Looks like all you need to do is remove the "parser" argument from the line:

#(ly:parser-set-note-names parser pitchnames)

so that you get

#(ly:parser-set-note-names pitchnames)

HTH,
Abraham 
 
 
   If you reply to this email, your message will be added to the discussion 
below: 
http://lilypond.1069038.n5.nabble.com/Arrow-Accidentals-Code-Error-v-2-19-tp191276p191280.html
   To unsubscribe from Arrow Accidentals Code Error v.2.19, click here.
 NAML 





--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Arrow-Accidentals-Code-Error-v-2-19-tp191284.html
Sent from the User mailing list archive at Nabble.com.___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Spare SSD anybody?

[David Kastrup]

Hi,

my current development SSD, graciously donated by James, currently has
the following readings:

Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME  FLAG VALUE WORST THRESH TYPE  UPDATED  
WHEN_FAILED RAW_VALUE
  5 Reallocated_Sector_Ct   0x0033   099   099   ---Pre-fail  Always   
-   13
  9 Power_On_Hours  0x0032   094   094   ---Old_age   Always   
-   25748
 12 Power_Cycle_Count   0x0032   093   093   ---Old_age   Always   
-   6196
175 Program_Fail_Count_Chip 0x0032   099   099   ---Old_age   Always   
-   9
176 Erase_Fail_Count_Chip   0x0032   100   100   ---Old_age   Always   
-   0
177 Wear_Leveling_Count 0x0013   085   085   ---Pre-fail  Always   
-   545
178 Used_Rsvd_Blk_Cnt_Chip  0x0013   077   077   ---Pre-fail  Always   
-   450
179 Used_Rsvd_Blk_Cnt_Tot   0x0013   079   079   ---Pre-fail  Always   
-   844
180 Unused_Rsvd_Blk_Cnt_Tot 0x0013   079   079   ---Pre-fail  Always   
-   3188
181 Program_Fail_Cnt_Total  0x0032   099   099   ---Old_age   Always   
-   13
182 Erase_Fail_Count_Total  0x0032   100   100   ---Old_age   Always   
-   0
183 Runtime_Bad_Block   0x0013   099   099   ---Pre-fail  Always   
-   13
187 Uncorrectable_Error_Cnt 0x0032   100   100   ---Old_age   Always   
-   0
195 ECC_Error_Rate  0x001a   200   200   ---Old_age   Always   
-   0
198 Offline_Uncorrectable   0x0030   100   100   ---Old_age   Offline  
-   0
199 CRC_Error_Count 0x003e   253   253   ---Old_age   Always   
-   0
232 Available_Reservd_Space 0x0013   077   077   ---Pre-fail  Always   
-   1566
241 Total_LBAs_Written  0x0032   032   032   ---Old_age   Always   
-   2933093682
242 Total_LBAs_Read 0x0032   058   058   ---Old_age   Always   
-   1798843749

In the interest of continuity, it seems like a good idea to replace it
soon.  I might return to a rotating disk (which has quite less wear but
is more sensitive to movement, draws more current, and of course is
slower).  After changing my kernel to 64bit, I am currently in the
situation that the computer will no longer wake successfully from sleep
mode (screen stays black), so I have to use hibernation instead.  That's
nice on the battery but sloshes out gigabytes of memory to disk each
time.  So it's not really helping with regard to SSD wear.  I don't have
all that much free capacity either, so what I have is being cycled
often.

Anybody with something to spare?  The current size I have is 120GB.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user