[abcusers] Quicktim 5 preview silences BarFly

2000-10-12 Thread Phil Taylor

Any BarFly users thinking of installing the newest version of
Quicktime should be aware that the Quicktime Musical Instruments
which come with it are seriously buggy.  I've tried it on two
machines, and in one case it just produced no sound (not only
with BarFly, but with Movie Player when trying to play MIDI or
music movies.) and in the other it would play only when "Highlight
Note Played" was selected, then crash at the end of the tune.

If you are going to install QT 5 preview, make sure that you keep
the QT 4.1.2 installer around so that you can revert to the last
good version.

Phil Taylor


To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html



Re: [abcusers] Quicktim 5 preview silences BarFly

2000-10-12 Thread Frank Nordberg



Phil Taylor wrote:
 
 Any BarFly users thinking of installing the newest version of
 Quicktime should be aware that the Quicktime Musical Instruments
 which come with it are seriously buggy...

Thanks Phil. I guess I'll stick to QuickTime 4 for a while then.



Frank
To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html



[abcusers] multible chord lines

2000-10-12 Thread Atte André Jensen

I'm wondering what is the status of abc's (lack of) ability to handle more
than one set of chords, alternatives printed above each other? I know that
yaps had a way of doing this, but is there any plans on getting it into
the standard, and does other abc-applications support this?

Also how are things looking with the (lack of) ability to give you the
triangle symbol in chords for major 7th chords, and the use of real
accidentals instead of # and b from the chord font?
-- 
Atte André Jensen

To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html



Re: [abcusers] A4/letter in abc2ps

2000-10-12 Thread Atte André Jensen

On 12 Oct 2000, Laura Conrad wrote:

  "Atte" == Jensen  Atte writes:
 
 Atte Hello As it is now my abc2ps seems to produce postscript
 Atte files in letter size. 
 
 That's odd, because the default has always been A4, and I've always
 had to do something to get letter.

Well I don't know if it's letter, that was just an assumption. But I know
that my printouts gets clipped, and I know that I dont like that
:-) Should I put examples on my sitespace for you to take a look at?

 
 Atte scale 0.60 
 ...
 
 Add:
 
 pageheight 29.7

That would be in the format file, right?

 
 I think.  If that's how many centimeters high an A4 page is.
 
 Or use acroread and set the "fit to page" option.

Not really userfriendly. The majority of people would grap the multi-page
.ps or .pdf file and when the first couple of pages (which doesn't
clip) look fine they'll print the whole thing without adjusting any
settings...

 
 Or use "psresize -pletter".
 
Where and how??

-- 
Atte André Jensen

To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html



Re: [abcusers] multible chord lines

2000-10-12 Thread Atte André Jensen

On Thu, 12 Oct 2000 [EMAIL PROTECTED] wrote:

 
 
 | I'm wondering what is the status of abc's (lack of) ability to handle mor=
 | e
 | than one set of chords, alternatives printed above each other? I know tha=
 | t
 | yaps had a way of doing this, but is there any plans on getting it into
 | the standard, and does other abc-applications support this?
 
 Perhaps it doesn't explicitly belong in the standard, other than as a
 comment  saying that it's a possibility.  Something that a lot of GUI
 software does is understand \n inside quotes as meaning  to  start  a
 new  line.   That  is,  a  chord symbol like "G\nEm" should produce a
 two-line bit of text, with "G" on the first  line  and  "Em"  on  the
 second.   All  we  really  need  is  for  the software to handle this
 correctly.
 
 Of course, if we really want to tweak the standard, we could also say
 that  something  like "G""Em" does the same thing.  That is, multiple
 chords are explicitly allowed, and should be handled however is  most
 appropriate  for  the  particular app.  A music formatter should show
 them both in some reasonable format.
 
 But I think I'd personally prefer for the \n notation to "just work".

Doesn't matter at all to me. I just really need this. Actually I need this
so bad for my main use of abc, which is entering jazzstandards, that I've
started shopping around for something else, like Lilypond. I've starting
putting together a ambitious (with correct melodies, lyrics
included, right chords) online fakebook, but for it to be serious you just
got to be able to have alternate changes sometimes. Some here might
just say "go away, you don't use abc for what it's supposed to do", but
abc has some obvious advantages over say Lilypond, and only needs a couple
of additional things to be *the* short/compact notation language.

 
 | Also how are things looking with the (lack of) ability to give you the
 | triangle symbol in chords for major 7th chords, and the use of real
 | accidentals instead of # and b from the chord font?
 
 Not much action there that I've seen.  Maybe we need you  and  a  few
 others to keep bringing it up until people pay attention.
 
I'll do that as long as I'm around :-)

 I wonder if it might help if someone collected PNG or GIF  images  of
 such musical symbols and put them on the Web somewhere?
 
I'd love to do that, even right now. I have a an old copy of the
postscript font that Encore uses for all its musical symbols. What format
should I convert them to (size/resolution). I know close to nothing
about postscript, but I'm certainly willing to help as much as I can.
-- 
Atte André Jensen

To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html



Re: [abcusers] A4/letter in abc2ps

2000-10-12 Thread Laura Conrad

 "Atte" == Jensen  Atte writes:

 That's odd, because the default has always been A4, and I've
 always had to do something to get letter.

Atte Well I don't know if it's letter, that was just an
Atte assumption. But I know that my printouts gets clipped, and I
Atte know that I dont like that :-) Should I put examples on my
Atte sitespace for you to take a look at?

Look at the postscript file in gv, and see what kind of page it thinks 
it is.  Then change the kind of page and see what kind doesn't
clip. (Or what kind does clip the way the pages you're seeing do.)

 Add:

 pageheight 29.7

Atte That would be in the format file, right?

Yes.

 Or use acroread and set the "fit to page" option.

Atte Not really userfriendly. 

No.  It's the best you can do if you have  a pdf file produced by
someone else using the wrong size, though.

 Or use "psresize -pletter".

Atte Where and how??

From the unix command line.  I think it comes with a package called
pstools. 

-- 
Laura (mailto:[EMAIL PROTECTED] , http://www.laymusic.org )

(Note the email and homepage address changes; please update your
address book, bookmarks, and links.)

To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html



[abcusers] Re: abcusers-digest V1 #365

2000-10-12 Thread Derek Lane-Smith

Date: 12 Oct 2000 09:50:24 -0400
From: Laura Conrad [EMAIL PROTECTED]
Subject: Re: [abcusers] Re: abcusers-digest V1 #364

 "Derek" == Derek Lane-Smith [EMAIL PROTECTED] writes:

Derek I honestly can't see why this whole discussion is such a
Derek great problem.  Why not simply have two separate key
Derek signature codes, one, K:, that can contain the key/mode,
Derek and the other, k: (say), that can contain the key
Derek signature.  That way you maintain compatibility, nearly,
Derek with old abc files, but have full scope for exercising
Derek personal preference.  Any tune can have either or both
Derek fields filled.

Surely not both.  It would confuse  people if they conflicted.  The
proposal we're arguing about is that there should be more options on
the current K: field.  I wouldn't support having a second field that
provides the same information in a different format.

I dunno, I think having two separate header fields would be cleaner and
less confusing than having several options for the current K: field.  If
the two fields were both filled it provides some redundancy.  If they were
in conflict, you can generate an error message, that would be missed if
there were only one.

Derek Incidentally, I would like to see a 'class' code, that
Derek would include one or more characters, each of which would
Derek represent a class of music to which the tune belongs.

And you can't figure out how to do this with all the current header
fields?  It seems to me that we already have too many options for this 
kind of thing.  From the standard:

A:areayes   A:Donegal, A:Bampton
B:bookyes yes   archive B:O'Neills
D:discography yes   archive D:Chieftans IV
G:group   yes yes   archive G:flute
I:information yes yes   playabc
N:notes   yes   N:see also O'Neills - 234
O:origin  yes yes   index   O:I, O:Irish, O:English
R:rhythm  yes yes   index   R:R, R:reel
S:source  yes   S:collected in Brittany
Z:transcription note  yes   Z:from photocopy

Couldn't any of these be used the way you're thinking of?

I suppose I: could be used to categorize the class of the tune, but the
name, 'information' suggests more verbose data than cryptic, single
character codes.


- -- 
Laura (mailto:[EMAIL PROTECTED] , http://www.laymusic.org )

Derek
To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html



Re: [abcusers] Re: abcusers-digest V1 #364

2000-10-12 Thread Jack Campin


Incidentally, I would like to see a 'class' code, that would include one or
more characters, each of which would represent a class of music to which
the tune belongs.  Then, if there is a large archive of tunes, you can pipe
it through a filter to extract all those in the archive that belong to the
class of music of interest to you, whether you know the names of the
individual tunes in the class or not.

We already have several header fields like this, all of them wildly
ambiguous and interpreted in every possible way by some transcriber
somewhere.  What do you want your new field to do, exactly?  What
*kind* of class? - I can think of class divisions like:

- transcription from live performance vs recording vs print

- raw transcription vs edited version

- final version vs draft

- fiddle vs pipe setting

- transposition for soprano vs alto voice

- grade V vs grade VIII difficulty level

- melody vs four-part harmonization

- copyright vs public domain

- laid out in portrait vs landscape format

- Gaelic vs English lyrics

- requires standard vs DADGAD guitar tuning

- banned or permitted under German anti-Nazi laws

- standard vs extended vs archaic ABC

- original copy or from a mirror site

- clean vs bawdy version

Two letters isn't going to do it, we need something extensible.  Putting
keywords in N: fields is a stopgap you can use meanwhile.


To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html