Author:
Date:
Subject:
Gareth Magennis
2008-07-07 23:55:20
Audacity recording times
Hi,
a guy saturday tried to record the entire nights music onto his PC laptop,
using Audacity. This is 8 to 9 hours total. The screen showed the
appropriate stereo waves right up to the end I believe, I was keeping an eye
on levels most of the night. Apparently when he first tried to save the
single file, it showed a size of zero.
I got a text from him to say that he eventually managed to save the first
hour and a half, and that he had to manually piece together 16000 temp files
to get the total recorded up to 6 hours or so, losing the last hour and a
half.
What is the maximum recording time, and/or is there a way to do a better
job of recording in the first place? I don't know any details of his system
at all, just wondered if I could help him out. He's somewhat embarrased and
frustrated, as he tried to do the same last month but didn't realise that
when he shut the laptop lid down, Audacity stopped recording, so only got
the first hour and a half.
Cheers,
Gareth.
Author:
Date:
Subject:
Gareth Magennis
2008-07-08 00:00:03
Re: Audacity recording times
The OS might be Linux
Gareth.
Author:
Date:
Subject:
Richard Crowley
2008-07-07 18:33:45
Re: Audacity recording times
"Gareth Magennis" wrote...
> The OS might be Linux
That may significantly reduce your chances of getting a
response from someone who actually uses Audacity on
Linux.
Unless you want to brave one of those Linux newsgroups.
But PLEASE don't cross-post anything from Linux-land to
over here to the real world! It always leaves r.a.p littered
with rubbish whenever the Linux guys show up.
Author:
Date:
Subject:
Scott Dorsey
2008-07-08 09:41:44
Re: Audacity recording times
Richard Crowley <[email protected]> wrote:
>"Gareth Magennis" wrote...
>> The OS might be Linux
>
>That may significantly reduce your chances of getting a
>response from someone who actually uses Audacity on
>Linux.
I use Audacity on Linux, and I don't see any limits that I would expect
to hit other than file size limits. But the honest truth is that I have
never tried to record six hours straight with it. Nor would I even TRY
such a thing. Stop and save files often if you're using a computer. If
you're using a tape machine in the field, use confidence monitoring and
don't use the longest posisble tapes.
>Unless you want to brave one of those Linux newsgroups.
>But PLEASE don't cross-post anything from Linux-land to
>over here to the real world! It always leaves r.a.p littered
>with rubbish whenever the Linux guys show up.
Sadly agreed.
--scott
--
"C'est un Nagra. C'est suisse, et tres, tres precis."
Author:
Date:
Subject:
Les Cargill
2008-07-08 18:31:43
Re: Audacity recording times
Scott Dorsey wrote:
> Richard Crowley <[email protected]> wrote:
>> "Gareth Magennis" wrote...
>>> The OS might be Linux
>> That may significantly reduce your chances of getting a
>> response from someone who actually uses Audacity on
>> Linux.
>
> I use Audacity on Linux, and I don't see any limits that I would expect
> to hit other than file size limits. But the honest truth is that I have
> never tried to record six hours straight with it.
The audience and performers have to go to the bathroom sometime. Maybe
even the recordist...
> Nor would I even TRY
> such a thing. Stop and save files often if you're using a computer. If
> you're using a tape machine in the field, use confidence monitoring and
> don't use the longest posisble tapes.
>
>> Unless you want to brave one of those Linux newsgroups.
>> But PLEASE don't cross-post anything from Linux-land to
>> over here to the real world! It always leaves r.a.p littered
>> with rubbish whenever the Linux guys show up.
>
> Sadly agreed.
> --scott
--
Les Cargill
Author:
Date:
Subject:
Max
2008-07-09 10:54:03
Re: Audacity recording times
"Les Cargill" <[email protected]> wrote in message
news:4873eaa7$0$12019$9a6e19ea@unlimited.newshosting.com...
> The audience and performers have to go to the bathroom sometime. Maybe
> even the recordist...
It only becomes a problem if the mikes are sensitive and can pick up what
goes on in there ;-)
Author:
Date:
Subject:
Richard Corfield
2008-07-09 08:11:36
Re: Audacity recording times
On 2008-07-09, Max <max_> wrote:
> "Les Cargill" <[email protected]> wrote in message
> news:4873eaa7$0$12019$9a6e19ea@unlimited.newshosting.com...
>> The audience and performers have to go to the bathroom sometime. Maybe
>> even the recordist...
>
> It only becomes a problem if the mikes are sensitive and can pick up what
> goes on in there ;-)
Recently experienced when the presenter at a trade stand popped off for
a break leaving his radio mic on. Those mics have excellent range!
I was there as first aider and wondered whether it would have been
professional or not to nip behind his stall and mute it before he finished
and came back. Interfering with someone else's audio setup may not have
gone down well, no matter how well intentioned.
- Richard
Author:
Date:
Subject:
geoff
2008-07-10 10:31:40
Re: Audacity recording times
Richard Corfield wrote:
> On 2008-07-09, Max <max_> wrote:
>> "Les Cargill" <[email protected]> wrote in message
>> news:4873eaa7$0$12019$9a6e19ea@unlimited.newshosting.com...
>>> The audience and performers have to go to the bathroom sometime.
>>> Maybe even the recordist...
>>
>> It only becomes a problem if the mikes are sensitive and can pick up
>> what goes on in there ;-)
>
> Recently experienced when the presenter at a trade stand popped off
> for
> a break leaving his radio mic on. Those mics have excellent range!
>
> I was there as first aider and wondered whether it would have been
> professional or not to nip behind his stall and mute it before he
> finished and came back. Interfering with someone else's audio setup
> may not have gone down well, no matter how well intentioned.
Spoil-sport. He might have gone out for a shag or a shit or something which
would have amuzed everybody greatly !
geoff
Author:
Date:
Subject:
Richard Corfield
2008-07-10 07:51:30
Re: Audacity recording times
On 2008-07-09, geoff <[email protected]> wrote:
>>
>> Recently experienced when the presenter at a trade stand popped off
>> for
>> a break leaving his radio mic on. Those mics have excellent range!
>>
>> I was there as first aider and wondered whether it would have been
>> professional or not to nip behind his stall and mute it before he
>> finished and came back. Interfering with someone else's audio setup
>> may not have gone down well, no matter how well intentioned.
>
> Spoil-sport. He might have gone out for a shag or a shit or something which
> would have amuzed everybody greatly !
This was an event for older people.
I may have amused everybody greatly!
- Richard
Author:
Date:
Subject:
geoff
2008-07-11 10:29:50
Re: Audacity recording times
Richard Corfield wrote:
> On 2008-07-09, geoff <[email protected]> wrote:
>>>
>>> Recently experienced when the presenter at a trade stand popped off
>>> for
>>> a break leaving his radio mic on. Those mics have excellent range!
>>>
>>> I was there as first aider and wondered whether it would have been
>>> professional or not to nip behind his stall and mute it before he
>>> finished and came back. Interfering with someone else's audio setup
>>> may not have gone down well, no matter how well intentioned.
>>
>> Spoil-sport. He might have gone out for a shag or a shit or
>> something which would have amuzed everybody greatly !
>
> This was an event for older people.
>
> I may have amused everybody greatly!
I once used to do stand-up comedy shows at old-peoples'-homes. I wasn't
very funny, but they pissed themselves anyway.
geoff
PS - not really
Author:
Date:
Subject:
philicorda
2008-07-08 12:07:42
Re: Audacity recording times
On Tue, 08 Jul 2008 00:00:03 +0000, Gareth Magennis wrote:
> The OS might be Linux
>
>
>
> Gareth.
If he is using Linux, then Ardour is better for this kind of thing.
It supports Wav64, so can handle large files.
He could also run two copies simultaneously and save/record with overlaps
between them.
As with any computer based recorder, I'd do a test run first to make sure
everything is working right. Record the radio for eight hours and then
check the jack logs to see if there were any xruns while recording
(buffer underruns).
|
