This is a plea to use DarkStar's thread by PMing him fixed issues, so the thread can establish it's entire usefulness. It's idea is to collect issues and fixes in one nice list. There's so many new features introducing (of course) even more new bugs and issues to the alphas these days, it's hard to keep track of them all. DarkStars thread to me has shown to be a big help in this respect. It is also the place I look when I am not sure if that bug I just found hasn't been reported yet, which would help to keep the 'Bugs only' threads cleaner if everybody did the same. The problem is, that not many people seem to report fixed issues to DarkStar, so he can keep the list up to date. I made it a habbit to scroll down that list with every new alpha release and check if bugs I reported are fixed by now, those fixed I PM to DS and they can be taken from the list. It's a rather quick job and every person doing that enhances the significance of the list. No one single person should be bothered to check for all bugs and everyone knows how to reproduce those bugs he reported best himself. That is why that thread's validity depends on everybody contributing. Please help to make the bugs list shorter and the fixed list longer by checking if "your" reported bugs are fixed with a new alpha and PMing those to DarkStar. I think it would be a very good idea to sticky that thread. Thanks for listening
RE: Please mind (and use) the 'v2.99 Status of Bug Reports' thread.
... now that 3.00 Alpha 2 is released, please retest all your Reported Bugs and let me know which ones have been fixed/resolved Here's the link to the Bug Reports Status thread, just search for your own name:
RE: Please mind (and use) the 'v2.99 Status of Bug Reports' thread.
PLEASE retest the bugs that you have reported, in V3 Alpha 3, and let me know which ones have been fixed. Without your updates, those summary lists will become out of date and less useful for everybody. Thanks :)
RE: Please mind (and use) the 'v2.99 Status of Bug Reports' thread.
OK: [liteon] changing envelopes values change the numeric value in a JS FX, but not the slider position [liteon] Show ReaControlMIDI..." should be only active when tracks are present imo. [liteon] "Set all tracks to automatic record...." does not execute with no tracks. (also in 2.56) [liteon] there is a 'moment' where 8 big fx knobs fit in the same height of 8 small knobs. (threshold?) [liteon] ME: The 'continuation' of a (looped) midi clip is shown on the right, but when resizing the clip's length it's gone. Think this one only happens when the midi editor is at default settings (zoom=100%). [liteon] ME: Entering a very small number for grid division results in a crash [liteon] ME: Moving the loop markers within the ME, cannot make the loop span more than the actual midi clip length.