Skip to main content

Recent Posts

Object Plugins / Re: 0.1
Last post by Mike Shawaluk -
Thanks for the kind words, and you're very welcome.

I just looked up tempo equations in Behind Bars, and they don't show brackets (parentheses) around them; they only show the parens for a numeric tempo marker that is not preceded/followed by text (the same as NWC's tempo marker).  Still, it would not be difficult to include an option for this, if there is a need for it.  However, BB also shows optional arrows on either side of the equation, which I could theoretically add. They also suggest centering the "=" on the barline, which I haven't done yet, but should probably do.
User Tools / Re: Copy and past measures of mutiple staves
Last post by Opagust -
Hi David, thanks for your response.

First of all: this isn't an object, but a tool. The difference might not be clear for every user, so let me explain:
* an object is inserted in a file, you do it once, and it'll do whatever it's supposed to do every time the file is shwon, printed, played.
* a tool can be invoked from within a file and does then his job with the file, but the tool itself is not permanently included in the file.

That said, let me comment on your thoughts:

1.I have been thinking of it, but I wanted to keep the dialog short. The user can easily insert a system or page break himself.

2. At the start of the first measure of the top staf of the imported part, the tool will insert a text marker above the staff with the song title with the font 'Page Title Text'. Again, the user might insert a boundary offset change, if needed.

3. For as it is now, the tool checks that, for every staff in the imported part, there's a staff in the destination file wit the same name. If not, the tool ends with a simple error message (on the first mismatch). If all the imported staves have a match, they inherit all properties of the matching staff in the destination file.
Maybe I should check more then the name alone and provide more elaborate information when there's a mismatch. The properties shown in the score review panel might be an inspiration?

4. The song title is now a text marker at the beginning. Maybe I can also insert the song tile + ' - end' in a text market at the end (with a smaller font).

Again, thanks for your input,


(And whoever wants to comment on this, please don't hesitate!
General Discussion / Re: taping pages together
Last post by Rick G. -
For binding 2-4 sheets, I use these pricing labels. Not cheap. ~10 years ago, I picked up a 3 roll pack for $10USD. (they are only sold with a replacement ink cartridge) But they really stick! I've not had one come off even on much used music that was bound several years ago. 3 stickers - 1 inch from top and bottom and 1 center. A three roll pack has over 3000 stickers. I've used about a roll and a half.
The link was to Monarch 1110 white labels. It is no longer any good. A quick search found a few suppliers, some of which don't require that you buy an inker. I'm down to about a half a roll on the pack I bought 17 years ago. They still stick after 17 years.
General Discussion / Re: taping pages together
Last post by David Palmquist -
Well, after 15 years it may be time for an update. 

Magic tape didn't last  (sigh.  :( ).  Masking tape dries, becomes brittle and breaks. 

A couple of ideas from - book binding tape and hinging tape.

Has anyone tried these for taping two or more pages of instrumental parts together?  Results?
Hi Opagust,

I haven't tried the object yet; won't have time this weekend to get really into trying it.

Some quick thoughts though, if you haven't dealt with them already?

I think there are two uses for the tool: Creating two or more songs on the same page of printed music, or alternatively, to combine songs into a medley. 

I might want:

1. Options to have the transferred song continue with or without a system break.

2. Where there's to be a system break, it would be useful to have an option to increase the upper vertical space on the first top staff of the transferred bars to allow space to include a large, bold song title.

3. Some way to help the user remember to ensure the transferred staffs have the same instruments in the same sequence (that probably has been dealt with manually by the user before using the tool), and with transposition settings consistent with the  destination file's existing staffs.

4. If you use simple text markers, perhaps there should be two: one at the beginning and one at the end of each copied section.  This might help if two or more groups of staffs are added to the target file.

And of course pounding the desk in frustration didn't help, I bet!
Dunno. It is one approach to diagnosing intermittent electrical connections  ;D
...I was working on a file accessed from a memory stick. This was loosely plugged in and any vibration of the desk caused the stick to rattle and repeatedly reconnect and superimpose multiple search screens on top of the music program's active screen...
And of course pounding the desk in frustration didn't help, I bet!

Glad you've solved it.
Object Plugins / Re: 0.1
Last post by David Palmquist -
In the two entries I tried, it seems to be almost perfect, Mike.  Thanks for creating this.

Usually the equation should be bracketed, so I think there should be an opening parenthesis, a little white space, the equation, a little more white space, and then the closing parenthesis.

I've had some success in the past with PgTxt.nw, but I'm now an infrequent user (3 or 4 times a year),  I don't remember what worked and what didn't, the last times I used the object.  I remember being very happy with it last fall.  But now I'm struggling.

I think there are too many unexplained variables in the PgTxtMaestro and PgTxt.nw dialogue boxes to use them efficiently. 

Are the object variables documented somewhere so the user can see what each means without killing an hour or more to figure out how to do something that can be done in minutes with ordinary text entries? 

If there is documentation, does it actually explain awkwardities such as Laurie points out?
You can't have two PgTxt objects if the same kind on the staff - the latter will always override the earlier one

Oops - interesting - never heard of such a problem! But good for you that you found out what was the trouble.