From: Florian J. <flo...@gm...> - 2013-01-30 21:18:30
|
Am 29.01.2013 05:43, schrieb Tim E. Real: > On January 29, 2013 01:09:15 AM you wrote: >> Am 29.01.2013 00:29, schrieb Tim E. Real: >>> On January 28, 2013 03:53:43 PM you wrote: >>> Although it is early, one bug I noticed is that I simply imported a small >>> existing wave file, and then the wave part's length was way too long, >>> like hundreds of bars IIRC. > > Checked: It is after I moved the wave event in the wave editor, > that the part length suddenly became 100's of bars long. fixed, was a design bug in schedule_resize_..._parts: it applied desired frame length as tick length. > > Also: Cannot move the red playhead cursor from zero :( > Each time I click in the time line, the cursor goes back to position zero. > Blue range markers OK though. fixed, was a mismatched }, which caused code to execute which would zero the position. plus, PosLens (i.e. especially WaveEvents) can now have a start position in TICKS, but a length in FRAMES. this allows you to do effects or drums as wave events, with successfully aligning them with tempo changes, but without stretching or clipping them. i made this the default for the moment, because wave stretching isn't implemented (yet). this will change. please play around with the branch a bit, it should work fine, except for loading and saving songs. greetings flo |