Apple Logic Pro /LogicExpress Discussion

Dear Users,

I recently attempted to use Logic to record a recital live.  According to the Docs, if  'maximum 
recording time' is unchecked in Audio/set recording path, the maximum recording time of a 
pass will be determined the amout of available space on  one's HD.  I recently did such a 
recording and ran out of time after c. 71 minutes of recording, yet , after the file was saved, 
there   were still over 20 Gigs available on my HD, yet the Logic file would record no more.  
Can anyone shed light on this?  I should have much more recording time available, according 
to the Docs.

Michael

Am 05.12.2005 um 06:35 schrieb Michael Sirotta:

> [..] and ran out of time after c. 71 minutes of recording, yet ,  
> after the file was saved

This is what I do if I know that I have more than one hours to record.

	- disable maximum recording time in record window
	- pull the song length delimiter completely to the right (two  
thousand something bars)
	- decrease bpm to get more time per bar
	- disable record forerun during recording

After that you'll be able to record hours of continous music with a  
simple mouseclick or short key.

HTH Daniel

-- 
Daniel Hojka
University of Music and Dramatic Arts
Institute 8 (Jazz)
Moserhofgasse 39-41
A-8010 Graz

Many thanks, Daniel.

BTW, I can't seem to figure out what your last step is about (record forerun).  Doesn't seem 
to affect anything (meaning, not knowing what it is, I didn't do it, but still had the 
extended capacity with the previous steps). Seaching the docs for 'forerun' yields nothing.

Thanks,again,

Michael

--- In Logic_Cafe@yahoogroups.com, Daniel Hojka <daniel.hojka@t...> wrote:

>
> Am 05.12.2005 um 06:35 schrieb Michael Sirotta:
> 
> > [..] and ran out of time after c. 71 minutes of recording, yet ,  
> > after the file was saved
> 
> This is what I do if I know that I have more than one hours to record.
> 
> 	- disable maximum recording time in record window
> 	- pull the song length delimiter completely to the right (two  
> thousand something bars)
> 	- decrease bpm to get more time per bar
> 	- disable record forerun during recording
> 
> After that you'll be able to record hours of continous music with a  
> simple mouseclick or short key.
> 
> HTH Daniel
> 
> -- 
> Daniel Hojka
> University of Music and Dramatic Arts
> Institute 8 (Jazz)
> Moserhofgasse 39-41
> A-8010 Graz
>

Am 05.12.2005 um 20:59 schrieb Michael Sirotta:

> BTW, I can't seem to figure out what your last step is about  
> (record forerun).  Doesn't seem
> to affect anything (meaning, not knowing what it [..]

Yeah, I'm sorry, I may have translated it wrong. I was referring to  
the (song-)option where you can tell Logic to wind back and count in  
like four or eight fourths before it starts recording. Although it  
'may' record from the first second on, it takes forever to count in  
four fourths @10bpm :)
But that is only for cosmetical reasons, I want to have a recording  
that starts at bar one and a audio file that carries such a timestamp.

Regards, Daniel

-- 
Daniel Hojka
University of Music and Dramatic Arts
Institute 8 (Jazz)
Moserhofgasse 39-41
A-8010 Graz

the docs dont tell the entire story
your max recording time is a function of contiguous hard disk space not just unused hard disk space
so if you defrag your drive first you will find your recording time will more or less be your available disk space

----- Original Message ----- 
From: Michael Sirotta 
To: Logic_Cafe@yahoogroups.com
Sent: 12/4/2005 9:38:46 PM 
Subject: [Logic_Cafe] Recording Time Question


Dear Users,

I recently attempted to use Logic to record a recital live.  According to the Docs, if  'maximum 
recording time' is unchecked in Audio/set recording path, the maximum recording time of a 
pass will be determined the amout of available space on  one's HD.  I recently did such a 
recording and ran out of time after c. 71 minutes of recording, yet , after the file was saved, 
there   were still over 20 Gigs available on my HD, yet the Logic file would record no more.  
Can anyone shed light on this?  I should have much more recording time available, according 
to the Docs.

Michael 





SPONSORED LINKS Logic analyzers Wedding music Logic control 
Pop music Case logic Wedding music cd 



YAHOO! GROUPS LINKS 

 Visit your group "Logic_Cafe" on the web.
  
 To unsubscribe from this group, send an email to:
 Logic_Cafe-unsubscribe@yahoogroups.com
  
 Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.

wouldn't it just create fragmented files if there is not enough contiguous space? 

-----Original Message-----
From: Howard Lipp <digitalwizzard@...>
To: Logic_Cafe@yahoogroups.com
Sent: Wed, 7 Dec 2005 22:27:11 -0800
Subject: RE: [Logic_Cafe] Recording Time Question


the docs dont tell the entire story
your max recording time is a function of contiguous hard disk space not just unused hard disk space
so if you defrag your drive first you will find your recording time will more or less be your available disk space
 
 
 
----- Original Message ----- 
From: Michael Sirotta 
To: Logic_Cafe@yahoogroups.com
Sent: 12/4/2005 9:38:46 PM 
Subject: [Logic_Cafe] Recording Time Question


Dear Users,

I recently attempted to use Logic to record a recital live.  According to the Docs, if  'maximum 
recording time' is unchecked in Audio/set recording path, the maximum recording time of a 
pass will be determined the amout of available space on  one's HD.  I recently did such a 
recording and ran out of time after c. 71 minutes of recording, yet , after the file was saved, 
there   were still over 20 Gigs available on my HD, yet the Logic file would record no more.  
Can anyone shed light on this?  I should have much more recording time available, according 
to the Docs.

Michael 







YAHOO! GROUPS LINKS 

 Visit your group "Logic_Cafe" on the web.
  
 To unsubscribe from this group, send an email to:
 Logic_Cafe-unsubscribe@yahoogroups.com
  
 Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.

On Dec 8, 2005, at 7:27 AM, Howard Lipp wrote:

> the docs dont tell the entire story
> your max recording time is a function of contiguous hard disk space  
> not just unused hard disk space
> so if you defrag your drive first you will find your recording time  
> will more or less be your available disk space

Where on earth did you get that idea?

Maurits.

Am 08.12.2005 um 08:15 schrieb Maurits van de Kamp:

> On Dec 8, 2005, at 7:27 AM, Howard Lipp wrote:
>> your max recording time is a function of contiguous hard disk space
> Where on earth did you get that idea?

*rotfl* I guess if you have a really really slow hard disk, the  
change from sequential writing might cause a delay long enough to  
make Logic's engine cough a little bit. But to be honest, I never had  
such a slow disk nor do I know somebody :)

Cheers, Daniel

-- 
Daniel Hojka
University of Music and Dramatic Arts
Institute 8 (Jazz)
Moserhofgasse 39-41
A-8010 Graz

> >> your max recording time is a function of contiguous hard disk space
> > Where on earth did you get that idea?
> 
> *rotfl* I guess if you have a really really slow hard disk, the  
> change from sequential writing might cause a delay long enough to  
> make Logic's engine cough a little bit. But to be honest, I never 
> had  such a slow disk nor do I know somebody :)

Well actually, I used to work with a G4 with a not-big-enough harddisk, and I
never actually managed to totally run out of space; instead I got an
increasing number of random "harddisk too slow" messages as the amount of free
space decreased, because of the increasing number of small fragments that had
to be searched and used. But this only became an issue when the drive was over
95% full..

Which also proves that Logic does NOT only record on contiguous harddisk
space. :o) (By the way, it couldn't even, because it has no idea what
"contiguous space" is; it just asks OSX for some drive allocation and gets it).

Maurits.

--- In Logic_Cafe@yahoogroups.com, "Maurits van de Kamp" <maurits@b...> wrote:
>
> > >> your max recording time is a function of contiguous hard disk space
> > > Where on earth did you get that idea?
> > 
> > *rotfl* I guess if you have a really really slow hard disk, the  
> > change from sequential writing might cause a delay long enough to  
> > make Logic's engine cough a little bit. But to be honest, I never 
> > had  such a slow disk nor do I know somebody :)
> 
> Well actually, I used to work with a G4 with a not-big-enough harddisk, and I
> never actually managed to totally run out of space; instead I got an
> increasing number of random "harddisk too slow" messages as the amount of free
> space decreased, because of the increasing number of small fragments that had
> to be searched and used. But this only became an issue when the drive was over
> 95% full..
> 
> Which also proves that Logic does NOT only record on contiguous harddisk
> space. :o) (By the way, it couldn't even, because it has no idea what
> "contiguous space" is; it just asks OSX for some drive allocation and gets it).
> 
> Maurits.
>
Agreed, stop buying os x updates, had a nightmare of a year with tiger

>> Which also proves that Logic does NOT only record on contiguous  
>> harddisk
>> space. :o) (By the way, it couldn't even, because it has no idea what
>> "contiguous space" is; it just asks OSX for some drive allocation  
>> and gets it).
>>
> Agreed, stop buying os x updates, had a nightmare of a year with tiger


Only buy updates you need.. anyway, ehm.. what did that have to do  
with what I said? :o)

Maurits.