On Fri, 11 Jan 2013 10:40:24 +0000, Chris Cannam wrote: Well I do find it a bit awkward. The representation of the focused area is just right, but as I've said - I find it much better to stop and start play by right click. Don't really need a context menu in that area and the mouse is always to hand - whereas the play button on the toolbar is far away and I lose focus. I don't use a keyboard unless I'm entering a fair bit of text really. So all I would do to create a 'region' would be load the wav and probably right click anywhere on the display area to start play. It would start from the beginning as the play head position hasn't been set (by left clicking). SV shows a representation of the entire file, great, but I'd like to adjust its height if possible and it should extend across the entire window, nearly. It's OK with a small gap either side. A single left click in there should update the main display to that position and carry on playing from there. Right click in there does the same (play/stop) as in the main area. Now an area of interest is in view, I'd stop and left click within the display to set the position at which play starts when I right click. It becomes a simple matter to get the exact position at which a newly created region would start. Now I would click a button to 'mark beginning'. If it's just a short passage and the end is in the view - it's simply a matter of left clicking somewhere near and then right click to start playing the start of what will be outside the new region. If it's not in view - just one click on the full representation would move and keep playing from there. Once found, the 'mark end button is clicked and a dialogue opens for naming and attributing etc. Couple of essentials would be that the wav files should only be opened for reading, and that there should be no gaps when going from the end of one region to the start of the next, in a play list which may point to many pretty large files on various HDDs. Thanks for reading and sorry for all the clicking :| -- John.

On Fri, 11 Jan 2013 21:46:02 -0500, Paul Davis wrote: I was able to use ardour to export labels iirc. It was very useful for creating a CUE file. Hugely anticipating v3. Thanks. Seems to me, although I always underestimate what's involved, that my needs are so basic compared to the high functionality everything I've seen provides. If you, or anyone similarly capable, could knock up something like I've described - you'd be surprised how quickly new regions can be marked. A configurable default naming scheme would allow annotation to be a secondary process, so that an entire file could be marked in not much time at all. The growing region list would be shown in a side panel... -- John.

On Wed, 16 Jan 2013 19:24:22 +0100 (CET), SxDx wrote: Y O U M E T S U P E R H A C K E R !!11qz I'm sorry but I am not worthy to make your acquaintance. I'm having a pretty good week, to be honest. Looks possible I'll be credited for testing some code to enable SteelSeries SRW-S1 racing wheels in future Linux kernels - and now I find you've kindly written something for me. And it works. Yes. No complaints, but I already have libsndfile and co, so all dependencies were met. Plot produced an output channel in qjackctl and it plays. Instantly. I can use it so naturally, by mouse, that I want for nothing more, except - The other channel output (of course). Lower view area to track play, although the way I can just move up to the upper section and quickly get the play head in view again - is fine really. I'm quite surprised there's so much detail from the chunk file. It's just enough for the entire file view, but a little more would be good in the lower section. Or maybe closer inspection of an area could be a secondary feature. Perhaps only when 'superzoom' is engaged a more detailed visualisation is derived from the area around the current play head position. Reduce did one of my 1.3GB files in about 3 seconds with a resulting size of about 1.3MB. They are very clear. Thank you. I don't see any high CPU while playing. Far from it in fact, compared to similar display in Wine, although I think that may have been more to do with how Wine does sound... 23% kwin and 14% Xorg if I drag plot's window around my desktop frantically while playing (as a reference point). 6% and 4% respectively playing normally. Xorg drops to 5% when plot is stopped. (i5 CPU). All by 'top' so not accurate. All my files are 48k so Jack is set for that. Famous names really. So many fine libs... Everything is there. Status bar area info is good and resize-ability isn't essential, although, if possible a scale option for the whole main window is a must for a generally available fixed size program window. It's all too small for squintless operation (for me) as is. My 'monitor' is a 32" Tv at 1920x1080 at 96dpi (forced). Of course. 64b here too. Maybe a fellow with 32b could test? Thanks a million for this Cédric, and I hope you can find the time to carry on with it a bit. I think it could develop into something which very many people could find useful. With both output channels working I'm sure it'll be my default wav player... Sincerely, John. --