Hi Don,
Please contact [EMAIL PROTECTED] or [EMAIL PROTECTED]
right away. Using Fin2k6, I have had every entry in my document wiped
out like this twice in the past week. Once, it was when advancing a
measure in Speedy Entry. Just an hour ago, it was when adding
measures using the measure
This is not comforting, gentlemen!
Dean
On Oct 17, 2005, at 2:35 PM, Darcy James Argue wrote:
Hi Don,
Please contact [EMAIL PROTECTED] or [EMAIL PROTECTED]
right away. Using Fin2k6, I have had every entry in my document
wiped out like this twice in the past week. Once, it was when
advan
BTW, I have experienced much less serious, but irritating and
inexplicable (at least to me) probs, e.g., after weeks of playing
back the same way, all of the sudden a ritardando didn't occur, even
after I deleted it and replaced it with another ... still wouldn't
retard ... I have no idea
On 18 Oct 2005, at 2:01 AM, dc wrote:
On the contrary, wouldn't it be better to turn Autosave off?
Uh, no, because unless you have impeccable manual save habits (and of
course, some do), you will _lose everything_ and have to revert to
your last manual save, whenever that was.
Because i
Darcy James Argue wrote:
On 18 Oct 2005, at 2:01 AM, dc wrote:
On the contrary, wouldn't it be better to turn Autosave off?
Uh, no, because unless you have impeccable manual save habits (and of
course, some do), you will _lose everything_ and have to revert to your
last manual save, whe
On 18 Oct 2005, at 4:30 AM, dhbailey wrote:
But don't you then run the chance of encountering the autosave bug?
There is no "autosave" bug. There is a file overwrite bug, but it's
got nothing to do with the autosave feature. There was also (in
Fin2004) a text block bug that was triggered
But this is exactly what I reported a week ago!
Finale 2006 is unusable then...
> Hi Don,
>
> Please contact [EMAIL PROTECTED] or [EMAIL PROTECTED]
> right away. Using Fin2k6, I have had every entry in my document wiped
> out like this twice in the past week. Once, it was when advancing a
> meas
On 18.10.2005 Javier Ruiz wrote:
But this is exactly what I reported a week ago!
Finale 2006 is unusable then...
Did you write to MacSupport? That's really, really important if you want
to get it fixed. They are more likely to make it a top priority if many
people report the same bug.
Johan
I'm not messing with '06 until this is fixed. I'm back to '05 now. I
haven't had time of late to keep up with this list as religiously as I do
sometimes, so if there was any kicking and screaming about this situation
(which there should have been) it got by me. If I'd known about this bug
I'd ne
Well, I am going to ask for a refund...
> On 18.10.2005 Javier Ruiz wrote:
>> But this is exactly what I reported a week ago!
>> Finale 2006 is unusable then...
>
> Did you write to MacSupport? That's really, really important if you want
> to get it fixed. They are more likely to make it a top pr
>Well, I am going to ask for a refund...
I don't want to offend anyone, and will do my best not to, but anyone
who is in this attitude should not use personal computer. It is a fact
of life there is, and will not be in a near future, no such thing as bug-
free software.
Computer/software is a t
Hiro,
With all due respect to you and your support of MM, there is another way of
seeing this situation:
By continuing to renew a subscription to Finale (and that's what it in essence
has become), a user is sending to MM the following messages:
1. It's ok that you continue to release softwa
On 18.10.2005 A-NO-NE Music wrote:
Well, I am going to ask for a refund...
I don't want to offend anyone, and will do my best not to, but anyone
who is in this attitude should not use personal computer. It is a
fact
of life there is, and will not be in a near future, no such thing as
bug-
Williams, Jim / 2005/10/18 / 11:49 AM wrote:
>With all due respect to you and your support of MM, there is another way
>of seeing this situation:
Which I don't think anyone seriously agrees if MM or any software vendor
in business take such attitude. There are a few such companies I have
witness
Williams, Jim wrote:
[snip]>
Hiro, I don't think ANYONE expects totally bugless software, but there MUST exist some minimal standard to which users can hold a manufacturer.
Jim
Totally trashing the data in a file is certainly very different from a
bug where an expression doesn't stay where
First, let me say that I too get very frustrated with the bugs in each new
version, and I would encourage MM to be more diligent in vetting such problems
before that release the product. However, there should be a bit of slack
allowed.
First, the costs in software application development are i
At 10/18/2005 11:50 AM, Johannes Gebauer wrote:
>On 18.10.2005 A-NO-NE Music wrote:
>>> Well, I am going to ask for a refund...
>>
>>
>> I don't want to offend anyone, and will do my best not to, but anyone
>> who is in this attitude should not use personal computer. It is a fact
>> of life ther
A-NO-NE Music wrote:
Williams, Jim / 2005/10/18 / 11:49 AM wrote:
With all due respect to you and your support of MM, there is another way
of seeing this situation:
Which I don't think anyone seriously agrees if MM or any software vendor
in business take such attitude. There are a few suc
On Oct 18, 2005, at 10:16 AM, <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> wrote:MM provides a product that, in other profession, would command upwards of 3,000 US Dollars. For what they provide and the price they market it at, I can give them the benefit to get some bugs worked out. If I remember cor
On 18 Oct 2005 at 2:15, Darcy James Argue wrote:
> On 18 Oct 2005, at 2:01 AM, dc wrote:
>
> > On the contrary, wouldn't it be better to turn Autosave off?
>
> Uh, no, because unless you have impeccable manual save habits (and of
> course, some do), you will _lose everything_ and have to revert
On 18 Oct 2005 at 10:43, A-NO-NE Music wrote:
> While I don't wish to be a MM apologist, Finale has a long history of
> initial release being somewhat troublesome, and it takes 1-3 patches
> to get it right. It has been this way. At least it has been
> consistent so you can have certain expectat
Jim,
wrt your comment:
I don't think ANYONE expects totally bugless software, but there MUST exist some minimal standard to which users can hold a manufacturer.
what would you say the minimal standard should be? Thinking back over
the various "bugs" discussed on the list since I have part
[EMAIL PROTECTED] wrote:
[snip]
PS - The software that I use to design databases cost $3,700 US
dollars for one copy. If I wanted a personal copy, I was told they
could discount it for to $3,325 . In my opinion this product
does not have to handle as complex logic as required for music
engraving
David,
I never said that you or anyone shouldn't complain, just don't whine about
it.
My intent was only to offer a different perspective.
By the way, read my post again. My company does not sell any software
products. I am an end user and my company paid $3,700 for that product, and
they cons
I've had 2006 quit suddenly 3 times when editing chord suffixes.
Anyone else had this problem. I'm actually using auto-save now,
something I've never felt the need for before. I've gone back to 2005
and I think that the next major up-grade should be a free one!
Yours
Mike Greensill
www.m
Dear folks,
As a customer and as an adviser for music schools I have put more money in
Coda/MakeMusic pocket than in other software company. Many, many licenses...
I have been a defender of Finale over Sibelius in uncountable occasions.
Boy, I even bought SmartMusic with my last upgrade!
I simpl
You are probably right here. But this is not a question of money, it is a
question of professional ethics. They have to acknowledge that the problem
exists and it is very important.
Saludos, Javier Ruiz.
The 18/10/05 18:57, David W. Fenton escribió/wrote:
> I really do think this one is bad eno
There was one that was at least close, early 2.x I believe. If your machine
crashed or Finale hung, your file reverted back to where it was when Finale
was launched, or something like that.
I lost a whole day's work once and for a *long* time after that I made it a
practice of saving alternately
While I wouldn't go down the road Javier's traveling (at least not yet), I
would point out (as others have) that there are degrees of bugs. And as bad
as this bug is in what it does and what can't be undone, it's even worse
because of the unpredictability of it's arrival.
In my experience, and ev
Johannes,
What is your backup routine? I guess I don't understand how you'd be able
to confidently limit lost work to an hour with this bug.
Thanks,
Don Hart
on 10/18/05 10:50 AM, Johannes Gebauer at [EMAIL PROTECTED] wrote:
> I have used 2k6 since it came out, and have not been struc
Dear Mike,
My sudden quits have happened in different circumstances, and I've
lost a little data in the process (having to revert to the last auto-
save). It has happened to me in the middle of a playback - where the
cursor stops dead and then the application quits, or in a mass edit
proc
Friends:
Reading Chuck's comment, I can't figure out how from
they have not encountered this and cannot reproduce it
Chuck predicates
(and are therefor unconcerned about fixing it - they can't find it)
Seems reasonable enough to me, no matter how much one wants to find a
problem, if
On 18 Oct 2005, at 1:53 PM, David W. Fenton wrote:
Because if the bug strikes and you Autosave every minute (that's
what I do), you have more chances of saving the corrupt version.
IMO, autosave every minute is unwise, for exactly this reason. But if
you have it set to something reasonable,
Dear Noel,
You are right - my bad. I can't predict when this will happen. I
have reported as much pertinent information as I can find - system,
memory etc. I will send a copy of the file when it happens again
(and try to narrow the window of what might have caused it).
I was not trying
On 18.10.2005 Don Hart wrote:
What is your backup routine? I guess I don't understand how you'd be
able
to confidently limit lost work to an hour with this bug.
Well, if I save my work regularly (and only when I am reasonably
comfortable that the data is still intact), and also have autosave
ppening at the
time the problem occurs could help Mac or Finale Techs fix the problem for you
and averyone else.
Richard
>
> From: Noel Stoutenburg <[EMAIL PROTECTED]>
> Date: 2005/10/18 Tue PM 06:04:22 EDT
> To: finale@shsu.edu
> Subject: Re: [Finale] Scary bug!
Dear Noel,
You are right - my bad. I can't predict when this will happen. I
have reported as much pertinent information as I can find - system,
memory etc. I will send a copy of the file when it happens again
(and try to narrow the window of what might have caused it).
I was not trying
> First, FinMac (don't know about FinWin) is awful about keeping track
> of whether there have, in fact, been any real changes to a file
> before closing.
FinWin is the same. By the way, I notice that Finale2005 still cannot seem
to clean up its temp files when closing and wonder if all of these p
On Oct 18, 2005, at 6:41 PM, Richard Yates wrote:
By the way, I notice that Finale2005 still cannot seem
to clean up its temp files when closing and wonder if all of these
problems
are related somehow.
I wonder the same thing.
Christopher
_
On 18 Oct 2005 at 18:15, Darcy James Argue wrote:
[long explanation of Finale 2004 text block autosave file overwrite
bug]
> This bug was corrected in Fin2005b, but when working with Fin2004,
> it's not safe to use autosave when working with multiple documents.
Um, that's all very interesting,
quot; so to speak.
From: [EMAIL PROTECTED] on behalf of Christopher Smith
Sent: Tue 18-Oct-05 17:53
To: finale@shsu.edu
Subject: Re: [Finale] Scary bug!
On Oct 18, 2005, at 6:41 PM, Richard Yates wrote:
>
> By the way, I notice that Finale2005 still can
When is it reasonable to expect the debugged version?
Dean
On Oct 18, 2005, at 8:50 AM, Johannes Gebauer wrote:
On 18.10.2005 A-NO-NE Music wrote:
Well, I am going to ask for a refund...
I don't want to offend anyone, and will do my best not to, but anyone
who is in this attitude should no
On 19 Oct 2005 at 0:30, Johannes Gebauer wrote:
> Today I was working on something completely differently, I was editing
> a recording. I lost about an hour's work because the software crashed.
> Annoying, no doubt, but nothing to get worked up about. It only
> happens every once in a while, and a
On 18 Oct 2005 at 18:31, [EMAIL PROTECTED] wrote:
> As for functions such as
> playback, in the windows world, the application uses a wrapper but the
> actual work of sending the playback through the correct buffers/ports
> etc. is performed by Quicktime or Windows Media player or whatever
> produ
Williams, Jim wrote:
When I see all the bugs people find with no apparent difficulty, I am also led
to wonder what other bugs are lurking in the program, waiting to be unleashed
by some poor unsuspecting user.
I would suggest that to talk of the "bugs people find with no apparent
difficult
-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
David W. Fenton
Sent: Tuesday, October 18, 2005 5:23 PM
To: finale@shsu.edu
Subject: Re: [Finale] Scary bug!
On 18 Oct 2005 at 18:31, [EMAIL PROTECTED] wrote:
> As for functions such as
> playback, in the windows world, the ap
On 18 Oct 2005, at 6:37 PM, David W. Fenton wrote:
On 18 Oct 2005 at 18:15, Darcy James Argue wrote:
[long explanation of Finale 2004 text block autosave file overwrite
bug]
This bug was corrected in Fin2005b, but when working with Fin2004,
it's not safe to use autosave when working with mul
On 18 Oct 2005, at 8:19 PM, David W. Fenton wrote:
On 19 Oct 2005 at 0:30, Johannes Gebauer wrote:
Today I was working on something completely differently, I was
editing
a recording. I lost about an hour's work because the software
crashed.
Annoying, no doubt, but nothing to get worked up
On 19.10.2005 David W. Fenton wrote:
In that case, you *could* lose months of work -- all that's necessary
is a second forced save after the bug has struck to wipe out both
your Finale file and the backup copy. The autosave won't help you if
it kicks in *after* the bug has struck.
I don't
Dean M. Estabrook wrote:
When is it reasonable to expect the debugged version?
Dean
It is reasonable to have expected to find it in our shrink-wrapped
packages which were delivered when we ordered our upgrade and paid them
the money for a working version that wouldn't trash users' work.
David W. Fenton wrote:
My bet is that it's related to the new implementation of temp files
maintained in memory instead of on disk. That change is the source of
the vast decrease in save time (and in AutoSave interruptions), but
it looks like it came at a price in stability.
Not all tem
Richard Bartkus wrote:
David,
It was just an example. I hope that I don't have to make every statement
exhaustive so that you don't have to quibble. The point is that, Finale
passes the data (Midi or whatever) to system modules that use other common
system resources.
Richard
So does ev
Darcy James Argue wrote:
[snip]
The only caveat I mentioned was that you probably didn't want to set
Fin2006 to autosave _every minute_ because that vastly increases the
likelihood that when all of the entries in your file are mysteriously
erased, autosave might kick in before you had a chan
Yes, Johannes, but what happens if you don´t notice that the bug has
striked? In my case complete portions of finished copied music were erased.
Portions that were in the middle of the work, not at the end where I was
working.
And yes, I immediately looked for the backup copies, but they were alre
> trashed, that's too far. If it's so obvious that Stevie Wonder could find it,
> that's too far.
>
> I just don't want to be an "enabler," so to speak.
>
>
> From: [EMAIL PROTECTED] on behalf of Christopher Smith
I couldn't have said it any better. It would be worrying if MakeMusic didn't fix this bug soon, but otherwise we just have to live with bugs in new versions. I have used 2k6 since it came out, and have not been struck by this bug. That is not to say I won't be struck in the future. However, eve
lf Of
dhbailey
Sent: Wednesday, October 19, 2005 1:59 AM
To: finale@shsu.edu
Subject: Re: [Finale] Scary bug!
Richard Bartkus wrote:
> David,
>
> It was just an example. I hope that I don't have to make every statement
> exhaustive so that you don't have to quibble. The poi
On 19.10.2005 Bernard Savoie wrote:
It might be an hours time of work, directly speaking. But if this
happened in the middle of a major project, say a 2 hour opera with
full orchestra and you already have more than an hour's music input,
I'd be more then a little worried of it happening again.
Mike Greensill / 2005/10/18 / 04:04 PM wrote:
>I've had 2006 quit suddenly 3 times when editing chord suffixes.
If you copy/past the crash log of just one incident (not the entire log,
please) and send it to me privately, I will try to give an half-educated
guesses. So far, FinMac2006 crashes
Dean M. Estabrook / 2005/10/18 / 07:42 PM wrote:
>When is it reasonable to expect the debugged version?
If you mean debug version.
You don't wanna.
Debug version means an app with terrible logging which slow you down.
Even beta tester doesn't want to use debug version :-)
If you mean the bug of
Javier Ruiz / 2005/10/19 / 06:18 AM wrote:
>I just can´t imagine a sound technician saying to the Kronos Quartet: Sorry
>folks, we have to repeat the whole piece because ProTools just swallowed
>what you beautifully played...
>I know, I know ProTools is much, much more expensive.
>Wait a minute, n
On 19.10.2005 Javier Ruiz wrote:
I just can´t imagine a sound technician saying to the Kronos Quartet:
Sorry
folks, we have to repeat the whole piece because ProTools just
swallowed
what you beautifully played...
I know, I know ProTools is much, much more expensive.
Wait a minute, no, you can b
>
> Firstly, it is very unlikely that the Kronos Quartet would be recorded
> with ProTools.
I have no idea how KQ is recorded, but I certainly know serious professional
recording engineers who use ProTools for HD recording. (Including using
ProTools LE on location.) That KQ might be recorded w
On 19 Oct 2005 at 1:24, Darcy James Argue wrote:
> On 18 Oct 2005, at 6:37 PM, David W. Fenton wrote:
[]
> > And, of course, there's also the backup file that you can choose to
> > create each time you manually save a file, and that might save you
> > if you saved and the real file had the data
On 19 Oct 2005 at 1:29, Darcy James Argue wrote:
> If this bug hits, the best thing to do is close the file right away
> without saving, then revert back to the most recently autosaved
> version. So long as you do this quickly, and you're not very unlucky
> (i.e., the bug hits one second before
On 19 Oct 2005 at 8:56, Johannes Gebauer wrote:
> On 19.10.2005 David W. Fenton wrote:
> > In that case, you *could* lose months of work -- all that's
> > necessary is a second forced save after the bug has struck to wipe
> > out both your Finale file and the backup copy. The autosave won't
> > he
On 19 Oct 2005 at 11:07, Javier Ruiz wrote:
> Yes, Johannes, but what happens if you don´t notice that the bug has
> striked? In my case complete portions of finished copied music were
> erased. Portions that were in the middle of the work, not at the end
> where I was working.
>
> And yes, I imm
On 19 Oct 2005 at 15:20, Johannes Gebauer wrote:
> I am sometimes amazed how much people trust computers. You can't. In
> the end it makes no difference whether the software or the hardware
> fails, data will get lost, and you better have a backup somewhere.
> Better have several.
I want to secon
Robert Patterson wrote:
But simply jumping up and down and screaming "fix it, dammit"--while entirely
understandable (I've done it, too)--accomplishes nothing.
Ahh, but suppose one is holding one's newly poured, but not yet mixed
beverage, and that one does not demand "stirred, not shaken";
David W. Fenton wrote:
in this kind of situation, a program
that manages the deleted files on your hard drive would allow you to
revert to any version you chose.
and if one doesn't have, or doesn't want to buy or write such a program
it is easily simulated. When I start a large project, I c
On 19 Oct 2005 at 14:58, Noel Stoutenburg wrote:
> David W. Fenton wrote:
>
> >in this kind of situation, a program
> >that manages the deleted files on your hard drive would allow you to
> >revert to any version you chose.
>
> and if one doesn't have, or doesn't want to buy or write such a
> pr
Ah, thanks.
Dean
On Oct 19, 2005, at 1:52 AM, dhbailey wrote:
Dean M. Estabrook wrote:
When is it reasonable to expect the debugged version?
Dean
It is reasonable to have expected to find it in our shrink-wrapped
packages which were delivered when we ordered our upgrade and paid
them
Yeah, I meant the latter.
Dean
On Oct 19, 2005, at 7:22 AM, A-NO-NE Music wrote:
Dean M. Estabrook / 2005/10/18 / 07:42 PM wrote:
When is it reasonable to expect the debugged version?
If you mean debug version.
You don't wanna.
Debug version means an app with terrible logging which slow
David W. Fenton wrote, regarding my work protocols
Well, yes, but there's a margin for error there. What if you mis-type
the file name, or accidentally open the wrong file and start edits?
You can then screw up your successive versions.
OK. I concede that there is a margin of error, but the
Arguably clearer if instead of writing:
so that when op 129 is completed there may be thirty versions of the
file in the directory.
I had instead written,
"so that when op 129 is completed, the directory may contain many files,
each containing a different version of the file, and each beari
On 19 Oct 2005 at 18:00, Noel Stoutenburg wrote:
> David W. Fenton wrote:
> >That can't happen with a program that works in the background.
>
> In my personal experience, the biggest problems (that is, the ones
> with the largest adverse consequences) I have had were a direct
> consequence of havi
on 19/10/2005 Johannes Gebauer wrote: I don't get it: If I have a backup from yesterday, why would any more than the work from today get lost? It makes no difference whether I already have half the opera done, I will never loose any more than what I did since I last backed up to the external dri
On Oct 19, 2005, at 13:00, [EMAIL PROTECTED] wrote:Hiro wrote: One more thing. Even though the bug of loosing data is pretty bad, you can't call it file corruption unless the file cannot be opened without error message. Sorry to disagree with this one, corrupt for me means that the file does not d
At 10/20/2005 12:31 AM, David W. Fenton wrote:
>If an undelete program that works like the one I have were free and
>worked as well (no performance penalty and complete stability), would
>you use it?
Yes, is there one?
I used to use Norton Undelete on WinNT but it stopped working on Win2K.
Phi
David W. Fenton wrote:
If an undelete program that works like the one I have were free and
worked as well (no performance penalty and complete stability), would
you use it?
I'm always willing to look at something, whether a change in procedure,
or acquisition of a new software item that w
At 10/20/2005 08:34 AM, Noel Stoutenburg wrote:
>David W. Fenton wrote:
>
>>If an undelete program that works like the one I have were free and
>>worked as well (no performance penalty and complete stability), would
>>you use it?
>
>I'm always willing to look at something, whether a change in pro
Bernard Savoie / 2005/10/20 / 05:56 AM wrote:
>Sorry to disagree with this one, corrupt for me means that the file
>does not deliver the material which was saved to it, whether you get
>an error message or not.
Wait!
I think many, many people are confused here.
Both Darcy and Don said the la
On Oct 19, 2005, at 3:58 PM, Noel Stoutenburg wrote:
There has been a side benfit to this technique. On more than one
occasion, I was able to avoid spending a great deal of time and effort
removing items in a file when a client changed his mind about how he
wanted an item, simply by going ba
[Since MakeMusic Inc. Answered to my request I guess I can post again ;) ]
Yes, Hiro is right. The files are not corrupted, they are simply wiped out.
Cero. Sayonara.
[BTW Finale is _not_ aware of the problem. And they are not making a refund
because I bought it 2 months ago...Hint, hint!]
Salud
Javier Ruiz / 2005/10/20 / 12:41 PM wrote:
>Yes, Hiro is right. The files are not corrupted, they are simply wiped out.
>Cero. Sayonara.
What do you mean by this?
Both Don and Darcy said otherwise. They said they were able to go
backed to last saved, as the same as you lost your work when comput
At 10/20/2005 12:41 PM, Javier Ruiz wrote:
>[Since MakeMusic Inc. Answered to my request I guess I can post again ;) ]
>
>Yes, Hiro is right. The files are not corrupted, they are simply wiped out.
I guess "corrupted" means "damaged so badly that they cannot be reloaded".
So, if you have a file
I meant that complete portions, parts, fragments of the work you had been
working on simply disappear. Not all the music only 100 bars or so in my
case.
I am sorry, I am Spanish and I probably don't use the proper expressions to
explain the problem.
The files themselves do not look to be corrupted
Javier Ruiz / 2005/10/20 / 01:13 PM wrote:
>But, Hiro, it looks like you don't want to admit the possibility of this.
No, no. You are completely misunderstanding my point. I want the fact
straight because both Don and Darcy said closing without save will get
you last saved version back, while
Let me clarify, at least for myself - and I'm sorry if I was unclear at any
point.
I was able to go to the *backup copy made when I last saved* and was
fortunate enough to lose virtually nothing. I found no way to retrieve the
lost data in my original file. The undos I did trying to rectify the
On 20 Oct 2005 at 5:56, Bernard Savoie wrote:
> On Oct 19, 2005, at 13:00, [EMAIL PROTECTED] wrote:
>
> Hiro wrote:
> >
> > One more thing. Even though the bug of loosing data is pretty bad,
> > you can't call it file corruption unless the file cannot be opened
> > without error message.
>
> S
On 20 Oct 2005 at 7:03, Phil Daley wrote:
> At 10/20/2005 12:31 AM, David W. Fenton wrote:
>
> >If an undelete program that works like the one I have were free and
> >worked as well (no performance penalty and complete stability),
> would >you use it?
>
> Yes, is there one?
>
> I used to use
Javier Ruiz wrote:
[Since MakeMusic Inc. Answered to my request I guess I can post again ;) ]
Yes, Hiro is right. The files are not corrupted, they are simply wiped out.
Cero. Sayonara.
[BTW Finale is _not_ aware of the problem. And they are not making a refund
because I bought it 2 months ago
David W. Fenton / 2005/10/20 / 02:40 PM wrote:
>Finale files are database files
It is?!
What is the definition of the database file?
I don't consider it is a database if you don't push/pop and real-time
data I/O. If real-time data I/O then I will agree it is a corruption,
but Finale file is not
Hiro,
As I understand what Javier is saying is that the file loses data. If
he has inadvertently saved it, not realizing there was lost data in
portions not showing on-screen when he saved it, he has also overwritten
the last-good-version of the file. So all he is left with is the one
with
A-NO-NE Music wrote:
Javier Ruiz / 2005/10/20 / 01:13 PM wrote:
But, Hiro, it looks like you don't want to admit the possibility of this.
No, no. You are completely misunderstanding my point. I want the fact
straight because both Don and Darcy said closing without save will get
you last
On Oct 20, 2005, at 2:40 PM, David W. Fenton wrote:
From a database point of view (and Finale files are database files),
it's definitely corruption, and of the logical type. There are two
types of corruption in a database:
1. logical corruption
2. content corruption.
Logical corruption mea
On 20 Oct 2005 at 12:50, A-NO-NE Music wrote:
> Javier Ruiz / 2005/10/20 / 12:41 PM wrote:
>
> >Yes, Hiro is right. The files are not corrupted, they are simply
> >wiped out. Cero. Sayonara.
>
> What do you mean by this?
> Both Don and Darcy said otherwise. They said they were able to go
> back
On 20 Oct 2005 at 13:43, A-NO-NE Music wrote:
> Javier Ruiz / 2005/10/20 / 01:13 PM wrote:
>
> >But, Hiro, it looks like you don't want to admit the possibility of
> >this.
>
> No, no. You are completely misunderstanding my point. I want the
> fact straight because both Don and Darcy said clo
Andrew Stiller wrote:
There is a downside however: if you don't rigorously, religiously,
follow all the necessary steps required for this system, you can end
up with what I constantly get from this composer in Malta: revisions
applied to an outdated version of the score.
OK. I'm not quite
On 20 Oct 2005 at 13:08, Don Hart wrote:
> I was able to go to the *backup copy made when I last saved* and was
> fortunate enough to lose virtually nothing. I found no way to
> retrieve the lost data in my original file. The undos I did trying to
> rectify the problem (immediately after I notic
1 - 100 of 161 matches
Mail list logo
