[Ggseq-list] bug report

[Michael S. <mic...@gm...>]

hi

i used the statically link version you posted on this list with ubuntu
warty. since i didn't have any small wav sample files availabe, i used a
36.4 mb wav file for all testing. i do realize that ggseq is probably
not made to handle such large files, but i still want to report how i
went:

- when choosing from the menu 'file' - 'import package' and clicking
'ok' without entering a filename, ggseq displays an error dialog but
then my computers cpu usage goes up and all memory is used up, ggseq
doesn't respond anymore and needs to be killed.

-when enveloping a segment on a track, i can only see 4 envelope points.
the one in the middle overlaps with another one. when i drag the one in
the middle to the left or the right, the envelope point lying
underneath, becomes visible.

-when i doubleclick a file in the window which displays the files in a
directory, a loading bar appears and to left of that bar a button
appears. i cannot read the label on the button, since the bottom half of
the button does not get displayed.

-when i click on the above mentioned button, while loading is in
progress, the application terminates with 'segmentation fault'

-should there be a button to set the 'timeline location line' to the
start? it's is not very smooth having to click so close the the volume
buttons to get it to go to the start.

-should i be able to right click on a segment in the timeline to bring
up a context menu which contains 'edit sample' and 'envelope'? i think
it would the natural thing to do, instead of having to click on the tiny
button at the end of a segment. i know that you are copying a sample
with a rightclick, but couldn't you display a context menu if let's say
the mouse does not move out of the segment and the button is released?

-dragging the 36.4 mb wav file onto the timeline takes a long time. my
memory get's totally filled up, get's cleared and goes up to half full
again (that's on 256 mb of ram).

-displaying the 'edit sample' window takes a long time.

-the controlls for editing the sample hardly move (i suppose that's due
to the big file).

-time streching the sample makes cpu and ram usage go up to the top, and
it takes a long time. i eventually killed the application.

michael salcher
-- 
email: mic...@gm...
website: http://propirate.net/mike/