Hi Bonnie,
As J D and Eric have mentioned, the Dolet 5 for Sibelius plug-in
exports MusicXML files from Sibelius 6 that Finale can read. It is
available for purchase from:
http://store.recordare.com/dolet5sib.html
The Dolet 5 for Finale plug-in does have a 10-day trial, but the
Sibelius
As I see it, Finale has created a climate of resistance to their
upgrades. The bugs are one factor, but for me, the much bigger factor
is the lack of file-level compatibility across releases. 100 bucks for
an upgrade is not much of an issue for me, even if the feature set were
marginal.
On 31 May 2009 at 23:27, Craig Parmerlee wrote:
The database doesn't have to be fast. The objects are stored in
memory during program execution. The penalty would only apply when
opening or saving files.
Yes, of course. Autosave would be intolerably slow (unless it saved
to some form of
David W. Fenton wrote:
On 30 May 2009 at 20:26, Craig Parmerlee wrote:
The obvious solution is to program each release such that it can read
future files but simply ignore any elements it doesn't recognize. If
Finale worked this way, I would automatically purchase every upgrade.
At 5/31/2009 01:14 PM, Craig Parmerlee wrote:
I agree with your comments about the trade-offs of filters versus XML.
I would be just as happy if I knew I could send a 2010 filter to any
collaborators so that they could open my 2010 files.
Not to nitpick, but 2 additional points:
1) Even in a
On 31 May 2009 at 14:04, Craig Parmerlee wrote:
David W. Fenton wrote:
On 30 May 2009 at 20:26, Craig Parmerlee wrote:
The obvious solution is to program each release such that it can read
future files but simply ignore any elements it doesn't recognize. If
Finale worked this
The database doesn't have to be fast. The objects are stored in
memory during program execution. The penalty would only apply when
opening or saving files. If there is a decoding penalty during runtime
it would surely be negligible.
But the underlying premise of that argument, if I
As I see it, Finale has created a climate of resistance to their
upgrades. The bugs are one factor, but for me, the much bigger factor
is the lack of file-level compatibility across releases. 100 bucks for
an upgrade is not much of an issue for me, even if the feature set were
marginal. The
At 8:26 PM -0400 5/30/09, Craig Parmerlee wrote:
The real issue for me is that every time I upgrade, I separate
myself from other Finale users who might be collaborators on a
project here and there.
I don't know if Sibelius is any better in that regard. But
considering that I don't know of
On 30 May 2009 at 22:44, John Howell wrote:
When MS brought out WinOffice2007 their .docx files could
not be opened in ANY previous version of Word, or in Word for Mac, so
there's a limit to backward compatibility when big changes are made.
But they quickly brought out file filters for
MusicXML transfer works like MIDI transfer between programs, but is
much more accurate for notation. You save a MusicXML from one program,
and then read the MusicXML file in another program.
For instance, Finale will not read a Sibelius file directly. Instead,
Finale 2007 will read a MusicXML
Hi Eric,
As Richard and David have mentioned, MusicXML is the most accurate way
to transfer files between Finale and Sibelius. If you have Sibelius as
well as Finale, you can use the Dolet 3 for Sibelius plug-in yourself.
Otherwise, the person with the Sibelius file will need to be the one
to use
Hi Richard,
As Noel and David have mentioned, you can use MusicXML format to go
between Sibelius and Finale. As with MIDI files, you write a MusicXML
file from Sibelius, then read the MusicXML into Finale. But you'll get a
lot more of the notation details with MusicXML than with MIDI, even with
13 matches
Mail list logo
