A few random points (UI, behaviour)

Thanks very much for the replies. Here we go...

MIXER - MOUSE SCROLL WHEEL
Tested in r4046 and it's fixed. Thanks :-)

MUTE/SOLO MULTIPLE TRACKS
> you have this kind of "boolean" approach behavior
Thanks - wasn't aware of that. I've had a play and it looks like this does basically what I need. The behaviour seems to be:

Shift-click Mute/Solo: Enable/disable state on all tracks. Takes its cue from the current state of the button actually clicked (if currently disabled = enable all tracks; if currently enabled = disable all tracks)
Ctrl-click Mute/Solo: Enable/disable state on this track only. e.g. Ctrl-solo-ing a track with other tracks already solo-ed, will un-solo those other tracks, leaving just the target track solo-ed
Shift-click Record; Ctrl-click Record: No special function

Is this the desired behaviour? Please confirm whether it's working as intended and, if so, I'll add this information to the wiki, as it doesn't appear to be there at the moment... unless, that is, you want to keep it as an Easter Egg :-)

AUTOMATION NODES - DESCRIPTIVE TEXT
OK. It's not a huge issue, but will definitely make things "nicer" if/when you do eventually find the time.

X-RUN/CLIPPING INDICATORS
> and what do you really want to do with that information anyhow?

Here are some examples:

x-run
As bouncing from MIDI to audio is real-time it can take a while on a long piece, so I'd like to be able to leave Qtractor running and come back when it's finished. If I come back and find an x-run reference in the Messages window, I know there was/could have been a problem, but won't know where this occurred (unless I methodically count backwards to the time code quoted or something). I don't get x-runs very frequently, but they can occur. Having a visual representation tells you exactly where the problem occurred so you can check and, if necessary, re-bounce just that area straight away. This saves a lot of time on a long piece. And even if you are present during bouncing, you may not be watching at the exact time the x-run occurs, so the visual representation is useful in any case.

Clipping
Much like the x-run situation, after making an audio recording and returning to the PC to check it (I record away from the PC to minimise noise), it'd be nice to see at a glance if anywhere had clipped, so I could check/re-record that section straight away. As you say, you should trust your ears and, of course, I'll be listening to the recording in its entirety at some point, but if the DAW can alert you to possible problems before you start more detailed listening, it can save a lot of time.

In terms of the actual representation, anything would be fine, but I was originally thinking of something like you see in Audacity.

In terms of formats, I usually record in FLAC, which (as I understand it) would produce clipping. The reason I use FLAC is, because it's lossless, I can then convert freely to other formats and it takes up less disk space than WAV. If you think there's a better format to record your "master" audio in (e.g. use Float WAV and take the disk space hit, to guard against clipping), I'd be very interested in any advice.

Neither of the above is a "must have", but I think they'd be very useful and would improve people's workflow (certainly mine, anyway).

SAVE SESSION WINDOW (FILE/SAVE AS)
Aha, yes that "fixed" it (I'm using xfce, by the way). Looks like it's not a Qtractor issue then, but new users may still get caught out (this window was where I first learnt about the different file formats, ages ago). I suppose they'll just have to read the documentation...

OK, have updated the wiki. Unfortunately though, after testing/eating the Easter Egg a bit more, it seems it isn't going to be as useful as I first thought: I can use it in some situations, but I often need to mute/solo just all audio tracks or just all MIDI tracks and, without a way to distinguish between the two/Shift-click multiple tracks/group tracks, this isn't possible. Looks like I'll have to continue doing things the long way :-(

And one more problem has cropped up this weekend, related to audio recording. I'll list what's happening below. Please let me know if you need more info, or want a ticket/qtz uploaded (have recreated on a clean file, for what it's worth):

----
(times quoted are just examples; actual times seem irrelevant)

STEPS TO REPRODUCE
- Connect mic to record audio directly into Qtractor (am using a Samson C01U USB mic)
- Start recording at 0 seconds; audio clip will be drawn on-screen as the transport moves (correct behaviour)
- Stop transport at 10 secs, using space bar/Play icon/Stop icon. Audio clip will sometimes "shrink" back - for example, though it was being drawn up to 10 seconds during actual recording, only the portion from 0 to, say, 5 seconds will now be seen

OTHER INFO
- Upon stopping the transport at the 10 second mark, it will remain there (correct behaviour)
- Start of the clip will always be correct - it's only ever the end of it which is affected
- Audio file actually records OK, but the clip isn't drawn correctly. You can drag the right edge of the clip to reveal the missing audio. You can also drag the recorded file from the Files window to the same position in an adjacent track and will see that it's correct - it will match the start of the original recording (0 secs) and the end (10 secs)
- Repro rate was about 70% on a project with a few tracks. Now, on a clean file, it's less than 5%
- I haven't seen this problem when bouncing audio tracks from MIDI (which was previously my main use for audio tracks); have only encountered it recently with direct recording
----

And, as per the above, if you have any advice on recording/clipping avoidance (stick to WAV, or whatever), please let me know.

I've just been adding some info to the wiki and realised I need to check something with you just in case. As mentioned here ("Be aware that session files..."), if the the user saves multiple "snapshots" of a session and changes the content of a MIDI clip in one of them, this change will be reflected in all snapshots. Is this the desired behaviour? It seems logical enough, but people who aren't familiar with the way Qtractor saves files may get caught out - they may think they can edit freely across multiple snapshots, when in fact, this isn't the case.

Please let me know if this is OK. (If it is working as intended and you'd prefer a different name to "snapshots" to avoid confusion, I can change it).