FYI,
It was a corrupt Preference file, and it has been so long since I had such a
problem that I neglected to consider the possibility.
All is well now.
Chuck
On Sep 10, 2012, at 11:43 AM, Jari Williamsson
wrote:
> On 2012-09-10 20:15, Chuck Israels wrote:
>
>> Have you any insight into
Thanks for the JW Validate beta plugin tip, Jari!
I just tried it and caught 4 important errors in my so-called pristine template
file.
Nice.
-Randolph Peters
On 2012-09-10, at 1:48 PM, Jari Williamsson
wrote:
> On 2012-09-10 20:23, Robert Patterson wrote:
>
>> I look forward to seeing the
On 2012-09-10 20:23, Robert Patterson wrote:
> I look forward to seeing the plugin, btw.
FWIW, it's in the Beta Versions section on the tips site. The first beta
was released earlier today, but at this state it'll just mark it as an
error when a staff has not be assigned to an instrument. Later
On 2012-09-10 20:15, Chuck Israels wrote:
> Have you any insight into why I cannot change back
> to Alto Sax after having switched to Flute on a staff?
> The instrument change dialog shows Alto Sax as already
> selected, but the transposition and staff name remains
> Flute. I am stumped. I did s
That you are building a plug-in based on the instrument concept in no way
contradicts what I said, but I am not prepared to bore the list discussing
it. I look forward to seeing the plugin, btw. The instrument concept needs
a good plugin.
On Mon, Sep 10, 2012 at 12:43 PM, Jari Williamsson <
jari.w
That you are building a plug-in based on the instrument concept in no way
contradicts what I said, but I am not prepared to bore the list discussing
data relationships exposed in the plugin PDK. It's possible we are in
violent agreement: that happens a lot in the software biz. I look forward
to see
So, Dear Jari,
Have you any insight into why I cannot change back to Alto Sax after having
switched to Flute on a staff? The instrument change dialog shows Alto Sax as
already selected, but the transposition and staff name remains Flute. I am
stumped. I did send the file to MM Mac support, b
On 2012-09-10 18:37, Robert Patterson wrote:
> The basic problem I see is that MM is trying to introduce a UI concept,
> "Instrument", that (at least as of now) does not exist in the data.
This is incorrect. I'm building a 2012 plug-in right now that bases its
core functionality on the instrument
This is why I still subscribe to the list.
I knew that the Score Manager was modeless and was happy for that.
My problem with making a huge score was that I made the Score Manager window
very large and it never occurred to me to double-click behind the window onto
the score itself. Time to move
For a variety of reasons, I wanted to start from scratch. Your points are all
good ones, however.
My problem was not leaving the Score Manager open on another monitor. That
would have been more efficient than closing it all the time.
-Randolph Peters
On 2012-09-10, at 11:42 AM, SN jef chippewa
>complete each staff and fill out all the properties (names,
>abbreviations, positions, fonts, MIDI settings, etc.)
these should be largely set up in your default doc and you would only
need to change a few exceptional instances
>My question for the list is would it be a bad idea to be able to
I'm not a big fan of Score Manager, but I would remind you that it is a
modeless dialog. You can open the staff attributes any time you get ready
just by double-clicking the staff.
The basic problem I see is that MM is trying to introduce a UI concept,
"Instrument", that (at least as of now) does
Dear Finale Listers,
I just spent a few days creating a new master full orchestra template in Finale
2012b. It takes longer now.
Some of the functions that used to belong in the staff attributes are now in
the Score Manager. I find that having to open up separate windows to complete
each staff
13 matches
Mail list logo