FL Beta 6.1 doesn't work after August 1st 2006

[speccyteccy]

# Some generators can now be threaded for some CPU gain on dual cores:
Fruity Wrapper, FL Keys, Wasp, Wasp XT, ReWired and SimSynth
# Introducing smart disable mode for generators as well.

Excellent news - can't wait to get home and try this out.

[james0tucson]

Now you see people are saving their projects, while there's a clear statement that it may not open in the next official release.

I'm not whining, the betas are starting to fix my audio problems since 6.x, but this savefile compatability thing could have been clearer. For instance, it's significant enough to mention in the same breath as "Please feel free to try the beta..." but there's nothing about it there. Now that I look for it, where is this "clear statement?" In the Save dialog?

[Vonbrucken]

can't remember where i saw it but i was aware that the songs made with 6.1 could have problem loaded in 6.08 but again it is always the same people that have problems

[Igor 4000]

Can the 6.2 beta be installed on top of 6.1, just like any other update?

[Igor 4000]

Now you see people are saving their projects, while there's a clear statement that it may not open in the next official release.

I'm not whining, the betas are starting to fix my audio problems since 6.x, but this savefile compatability thing could have been clearer. For instance, it's significant enough to mention in the same breath as "Please feel free to try the beta..." but there's nothing about it there. Now that I look for it, where is this "clear statement?" In the Save dialog?

You can't find the "clear statement" because there is no "clear statement".

[tony tony chopper]

Now that I look for it, where is this "clear statement?" In the Save dialog?

it's a beta, do you know what beta means? If you want everything to work properly, you don't use a beta or any piece of software. Beta is by itself a clear statement that not everything will work properly.

Plus, clear statement of forwards compatibility?? Just name me one software that's forward compatible. No software is forwards compatible unless stated otherwise. Did you really expect a beta to come with new features, and an older version to understand those new features?

[Vonbrucken]

[Jason Brian Merrill]

you're all obviously warez users anyway.

[Igor 4000]

Now that I look for it, where is this "clear statement?" In the Save dialog?

it's a beta, do you know what beta means? If you want everything to work properly, you don't use a beta or any piece of software. Beta is by itself a clear statement that not everything will work properly.

Does every beta expire, Gol? The only complaint some of us are having is that it would've been nice if it said somewhere clearly that the beta will expire. No one is persecuting Image Line.

I ask again...can the new beta be installed directly on top of the old one? That will save some of us (who don't know what "beta" means) a lot of hassle. Thanks for your help.

[james0tucson]

Now that I look for it, where is this "clear statement?" In the Save dialog?

it's a beta, do you know what beta means?

"Tony", I'm a professional software developer with 28 years experience.
I'm on your side.

[Jason Brian Merrill]

Now that I look for it, where is this "clear statement?" In the Save dialog?

it's a beta, do you know what beta means? If you want everything to work properly, you don't use a beta or any piece of software. Beta is by itself a clear statement that not everything will work properly.

Does every beta expire, Gol? The only complaint some of us are having is that it would've been nice if it said somewhere clearly that the beta will expire. No one is persecuting Image Line.

I ask again...can the new beta be installed directly on top of the old one? That will save some of us (who don't know what "beta" means) a lot of hassle. Thanks for your help.

what beta doesnt expire?

I cant think of any that dont.

except fxpansion betas.

does the Live 6 beta expire? What about betas of new microsoft stuff? Come on. lets list em. it will be fun and educational.

[DavenH]

what beta doesnt expire?

Gmail!

[Hink]

I'm confused...or I was, I thought I had re-installed 6.1 when I recovered from my hard drive crash last month...so I open it and FL was fine...I was about to say you guys are crazy, thankfully I checked the "about" under help and it said 6.08...so I accidently installed the wrong version, which apparently turned out right

[Jason Brian Merrill]

what beta doesnt expire?

Gmail!

...ouch

duh!

jerk, why do you have to be right

[kmonkey]

Beta

A beta version or beta release usually represents the first version of a computer program that implements all features in the initial software requirements specification. It is likely to be unstable but useful for internal demonstrations and previews to select customers, but not yet ready for release. Some developers refer to this stage as a preview, as a technical preview (TP) or as an early access.

Often this stage begins when the developers announce a feature freeze on the product, indicating that no more features requirements will be accepted for this version of the product. Only software issues, or bugs and unimplemented features will be addressed.

Beta versions stand at an intermediate step in the full development cycle. Developers release them to a group of beta testers (sometimes the general public) for a user test. The testers report any bugs that they found and sometimes minor features they would like to see in the final version.

A major example of a public beta test was when Microsoft started releasing regular Windows Vista Community Technology Previews (CTP) to beta testerm starting in January 2005. The first of these was build 5219. Subsequent CTPs introduced most of the planned features, as well as a number of changes to the user interface, based in large part on feedback from beta testers. Windows Vista was deemed feature complete with the release of build 5308 CTP, released on February 22, 2006, and much of the remainder of work between that build and the final release of the product will focus on stability, performance, application and driver compatibility, and documentation.

When a beta becomes available to the general public it is often widely used by the technologically savvy and those familiar with previous versions as though it were the finished product. Usually developers of freeware or open-source betas release them to the general public while proprietary betas go to a relatively small group of testers. In February 2005, ZDNet published an article about the recent phenomenon of a beta version often staying for years and being used as if it were in production-level [1]. It noted that Gmail and Google News, for example, had been in beta for a long period of time and were not expected to drop the beta status despite the fact that they were widely used; however, Google News did leave beta in January 2006. This technique may also allow a developer to delay offering full support and/or responsibility for remaining issues. Recipients of highly proprietary betas may have to sign a non-disclosure agreement.

A release is called feature complete when the development team agrees that no new features will be added to this release. New features may still be suggested for later releases. More development work needs to be done to implement all the features and repair defects.

As the second major stage in the development cycle, following the alpha stage, it is named after the Greek letter beta, the second letter in the Greek alphabet.

The term beta test applied to software follows from an early IBM hardware development convention dating back to punched card tabulating and sorting machines. Hardware first went through an alpha test for preliminary functionality and manufacturing feasibility. Then a beta test to verify that it actually correctly performed the functions it was supposed to, and then a c test to verify safety. With the advent of programmable computers and the first sharable software programs, IBM used the same terminology for testing software. Beta tests were conducted by people or groups other than the developers. As other companies began developing software for their own use, and for distribution to others, the terminology stuck and now is part of our common vocabulary.