After releasing 1.7.3 last night, we discovered a problem whereby cue points and loops might not display properly. With the weekend coming up, and no doubt some important gigs happening, we decided the safest thing to do was to pull the release, and get a fix out as soon as possible.
1.7.4 release candidate is in the public beta area, and fixes the problems where cue points and loops may not have been displayed correctly.
If you would like to try the public beta click here:
www.scratchlive.net
And now for some useful info about the public beta:
There is a new area set up for the duration of the public beta. This area will contain the beta downloads, and we will also manage feedback in this area. This area will only be visible if you are logged in.
There are some very specific requests, guidelines and rules for anyone who participates in the public beta, and you will have to agree to these rules before you can join in the public beta - you don't need to agree now, a full list of the conditions will be displayed before you can get to the beta, and you'll have to click on an "I agree button" to continue. But since many of you are probably keen to get involved, here's an overview of what's involved in being part of the public beta.
- The public beta should be treated as unstable.
Do not use it at your gig, only test the beta if you can afford to have the system fail on you in some way. We've been beta testing 1.7 for months now, but we make no guarantees, it is still a beta. Requests for help posted in the public beta area will be ignored. If you have a support issue with any of the versions previous to 1.7, post them in the help area and we'll help you out.
- Please read all of the release notes before using the Public Beta.
- Please be as descriptive as possible.
Every post should describe the scenario under which the bug occurred, what operating system you are using, what type of machine, and any other relevant information. Please try to name the thread in a way that clearly describes the problem. List the steps you went through to make the problem occur, and how to reproduce it. For example.
Step 1: Put The left Virtual Deck into REL mode
2: Load a track to the left Virtual Deck
3: Start the track and click the loop in button
etc
- Stay on topic.
We will be ruthless in locking threads that veer off topic, and bear in mind that the public beta area will be going away when the final version is complete, so if an interesting conversation develops, move it to the General Discussion area.
- Where possible, verify reported bugs.
If you see someone else reporting a bug, see if you can reproduce it on your system. This will help us to resolve the bug faster, and it will also differentiate between bugs that occur on any machine given a set of circumstances, or if it is specific to one machine.
- Don't be offended if your question goes unanswered.
The moderators who will be reading the public beta areas will be looking for specific things - namely bugs to fix. In many cases this information will be taken back to the lab, dissected, boiled and distilled, all with the intention of fixing the problem. Not every report will be responded to, for several reasons. We might have a good idea what the problem is, and wait until we have a fix, for example. Or there might be several bug reports which we can see are caused by the same underlying bug. If you have a question that isn't about the beta, and it hasn't been answered, post it again in the relevant thread - Help, Feature suggestions or General.
Why are we doing a public beta?
There are several reasons to do a public beta. The number one reason is speed. More people looking for bugs = finding bugs faster = getting started on the next version sooner = more cool stuff = less waiting.
Why doesn't it have feature xyz?
There is a balance between implementing lots of improvements, and timely releases. We try to keep the changes between each version small so that they come out more often. If it's not in this version, don't think the feature you are after isn't coming!
