recording countdown needs to go away

Logged In: YES
user_id=13489

Agreed on MIDI, but I think we do need to keep a countdown
for audio.

Lots of people who could afford 200+GB drives don't
actually have them. Particularly laptop users. Also we
should adjust the countdown to take into account the fact
that .wav files are limited to 32 bits (i.e. 90-odd mins
per stereo track at 48KHz).

Logged In: YES
user_id=663564

I'm passing this buck. You deleted all the audio recording
countdown infrastructure. It's commented out in a 1.0
tarball, but there's no remaining trace of it in SVN.

It sure isn't worth my time to fish it out of the trash bin
and put this back, since I think the recording countdown
thing is pointless and annoying anyway.

I'm just going to comment out the ->show() calls so nobody
will see it, and you can figure out what, if anything, to
do from there.

My vote is just to root out all the supporting cruft and
let the whole business go into the annals of history.

Logged In: YES
user_id=13489

Gosh, does that mean the audio recording countdown in
1.2.3 and 1.2.4 always counts to the end of the
composition? i.e. if you don't have enough disk space to
record to the nominal end of the composition, you'll just
run out without the countdown ever warning you about it?

That's a bit crap, if so. OK, I'll have a little look and
see what happened to the code.

Logged In: YES
user_id=663564

1.0 says:

/ #1045380 ("minutes of audio recording" just insanely
confusing) -- No, let's not use this. We should count
to the end of the composition in both cases.
[...]/

So I assume that it does, in fact, mean we've been counting
to the end of the composition for the past 18 months to two
years.

Thinking about this a bit more, I think what we should do
here is leave audiorecordminutes in the CVS archives, and
instead make the countdown run to the end of available disk
space, and/or the end of the maximum possible 90-minute
file size.

Some indication of how you're doing using up a finite
resource is a good thing, but have an arbitrary,
pre-selected limit on the maximum length of a recording
session smacks back to the bad old days of a non-expanding
composition. I don't like the idea of resurrecting that
arbitrary limit at all.

Logged In: YES
user_id=13489

You know, I'd quite forgotten there ever was an arbitrary
limit. That was pretty dismal. Ugh.

No, I wasn't trying to argue for restoring that -- I was
trying to argue for the same thing you just were, i.e. a
countdown to a full disk (or WAV file overflow).

I thought the pre-1.0 behaviour took disk space into
account -- in fact I was thinking that that was all it
did, as I'd forgotten the arbitrary limit as mentioned --
so I was surprised that disk space didn't continue to be a
factor through to 1.2.3. But then I think quite a bit
changed in the countdown logic in that time (and I might
have misremembered about disk space ever being accounted
for).

Chris

Logged In: YES
user_id=663564

OK, good then, it's agreed.

I didn't realize you didn't realize what I was going on
about. I think the default limit used to be either three
or five minutes, and if you wanted to record for 10
minutes, you had to change both the comp length and the
audio limit. That need to change things in two different
places is what you were seeking to abolish just prior to
1.0 when you got rid of the audio recording time limit.

I think the remaining limit was supposed to run to the end
of the comp or the end of disk space, but the code I see
here does not appear to take disk space into account.
Since the comp has no hard end, and there is no longer any
audio recording time limit, that's why I've been ranting
about the pointlessness of this dialog. When you get past
the soft limit, it starts reporting nonsense.

A redone dialog that serves some sensible purpose, now, on
that we are agreed.

Logged In: YES
user_id=663564
Originator: YES

What audio countdown?

The countdown dialog was removed from sequencemanager.cpp in [r7366]. I'm contemplating cleaning up the old code related to this, so I figured I'd leave a clue here in case anyone in the future decides to work on [feature-requests:#453].