Apple Logic Pro /LogicExpress Discussion group photo

Yahoo Groups archive

Apple Logic Pro /LogicExpress Discussion

Index last updated: 2026-04-28 23:06 UTC

Thread

Can't Freeze files w plug-ins. error -40

Can't Freeze files w plug-ins. error -40

2005-08-19 by Michael Sirotta

Hi folks,

I get the following error message whwn I try to freeze my softsynth tracks:
"Attempt to position before start of file
result code = -40"

Consequently, the freeze audio will not be created (even though Logic treats the the track 
as frozen for any editing operations) and processing power at playback is not optimized.

Any idea what's wrong?

Thanks,
Michael

Re: [Logic_Cafe] Can't Freeze files w plug-ins. error -40

2005-08-19 by GAmoore@aol.com

I get the following error message whwn I try to freeze my softsynth tracks:
"Attempt to position before start of file
result code = -40"



Never asaw that. Did you move the start of the song? You can start at bar 0 or -1 or -10 or whatever. Or you could have a region starting at bar -1 but the song start at bar 0. I would investigate that. You can go to the ruler bar, and drag the start point left or right.


Consequently, the freeze audio will not be created (even though Logic treats the the track
as frozen for any editing operations)



I think you can just hit the freeze button, but not hit play, so it had not gone through the freezing process but it still won't allow you to edit anything. Another weird thing is if you freeze a track and then lengthen the number of bars, it just cuts out (say if there is a loop). I also don't understand why the freezing process on empty parts takes as long as it does. If you have a single region from bars 100 to 120, you will see it jumping from 1 to 2 to 3.... albeit quickly, but it should not take any time at all.

and processing power at playback is not optimized.


even when frozen and it decreases processing load, it raises disk load.

Line Level or Mic Level For Guitar & iMic

2005-08-19 by rec

Hi there,

I have a Fender Strat with lace-sensor pickups (Red, Silver, Blue) which are
the original ones not the newer ones. As I understand it, lace-sensor have a
higher output. For now I'm using an Griffin iMic connected to the USB input
on my PowerBook. 

Does anybody know for sure if the output of these pickups is line level or
mic level? The iMic give a choice to select between line or mic.

I think they are line-level but I don't know for sure. Also, what
measurement of output qualifies as line level?

Thanks, 

Robert

Re: Can't Freeze files w plug-ins. error -40 (solved)

2005-08-19 by Michael Sirotta

--- In Logic_Cafe@yahoogroups.com, GAmoore@a... wrote:
> > I get the following error message whwn I try to freeze my softsynth tracks:
> > "Attempt to position before start of file
> > result code = -40"
> > 
> 
> Never asaw that. Did you move the start of the song? You can start at bar 0 
> or -1 or -10 or whatever. Or you could have a region starting at bar -1 but the 
> song start at bar 0. I would investigate that. You can go to the ruler bar, 
> and drag the start point left or right.
> 


Problem solved (in the Apple support database):

There is a 2 MB limit to freeze audio files.  For some reason, the sequence length of the 
file (song end point) in question was over 2,000 measures in length, even though the MIDI 
data ended at 40 bars. That much time of audio, silent or not, will be incredibly large 
bytewise.  Problem was solved by moving the song end point left to the real end of the 
note data.

Btw, I encounter these absurd song lengths often when some of my .mids are imported to 
Logic.  I don't know if the original sequences were saved with those track lengths or not 
(they were made in Opcode's Vision).  I can't imagine why they would be. Another related 
problem I've found in importing MIDI's is that some of the note-off values don't always 
import correctly, resulting in rediculous notes that are sustained for many, many bars 
(sometimes in the hundreds or more - going off right side of the matrix editor). These 
note durations all have to be manually corrected by dragging the end point, or retyping 
values in the event list (the latter method is fastest & simplest when the notes are really 
long or if one can't 'see' the end of the note).

I wonder if others have encountered any of these (seemingly related)  importation issues 
and if there is any other knowlege about it.

And also , btw, I'm still seeking for the 'simple' method of preventing plug-in reload when 
switching between multiple open songs.  Someone on this group had mentioned that they 
had heard of a way, but couldn't remember it.

Thanks,
Michael

Re: [Logic_Cafe] Re: Can't Freeze files w plug-ins. error -40 (solved)

2005-08-19 by GAmoore@aol.com

Problem solved (in the Apple support database):

There is a 2 MB limit to freeze audio files.



Thanks for reporting the solution back to the group. I think this is 2 GB though isn't it? With stereo 16 bit audio taking 10mb/minute.


For some reason, the sequence length of the
file (song end point) in question was over 2,000 measures in length, even though the MIDI
data ended at 40 bars. That much time of audio, silent or not, will be incredibly large
bytewise. Problem was solved by moving the song end point left to the real end of the
note data.

Btw, I encounter these absurd song lengths often when some of my .mids are imported to
Logic. I don't know if the original sequences were saved with those track lengths or not
(they were made in Opcode's Vision). I can't imagine why they would be.



Try opening them in the even editor. Probably there is some control event at the 2,000th measure. Maybe that was the end for the song in Studio Vision, and they had the style to put a control message there.


Another related
problem I've found in importing MIDI's is that some of the note-off values don't always
import correctly, resulting in rediculous notes that are sustained for many, many bars
(sometimes in the hundreds or more - going off right side of the matrix editor). These
note durations all have to be manually corrected by dragging the end point, or retyping
values in the event list (the latter method is fastest & simplest when the notes are really
long or if one can't 'see' the end of the note).



You need to introduce yourself to one my most commonly used keycommands in the matrix editor - the one that shortens the lengths so there is no overlap. I forgot the exact name because i have been using my own keycommand for many years. I'll look it up and report back. it usually works well in all cases - just select all and correct note overlaps by shortening the lengths by the keycommand or the menu item. At most you'll have the very last note to fix manually.


And also , btw, I'm still seeking for the 'simple' method of preventing plug-in reload when
switching between multiple open songs. Someone on this group had mentioned that they
had heard of a way, but couldn't remember it.



I'd like to know that too. It can take a minute or more when switching songs. And despite that, it seems that RAM is filled up quite easily when both songs are open.

Re: Can't Freeze files w plug-ins. error -40 (solved)

2005-08-19 by Michael Sirotta

--- In Logic_Cafe@yahoogroups.com, GAmoore@a... wrote:
> > Problem solved (in the Apple support database):
> > 
> > There is a 2 MB limit to freeze audio files.  
> > 
> 
> Thanks for reporting the solution back to the group. I think this is 2 GB 
> though isn't it? With stereo 16 bit audio taking 10mb/minute.

Yes, I believe you are right. Sorry about that.

> > 
> > Btw, I encounter these absurd song lengths often when some of my .mids are 
> > imported to
> > Logic.  I don't know if the original sequences were saved with those track 
> > lengths or not
> > (they were made in Opcode's Vision).  I can't imagine why they would be. 
> > 
> 
> Try opening them in the even editor. Probably there is some control event at 
> the 2,000th measure. Maybe that was the end for the song in Studio Vision, and 
> they had the style to put a control message there.
> 

You mean 'event editor'?

> 
> > Another related
> > problem I've found in importing MIDI's is that some of the note-off values 
> > don't always
> > import correctly, resulting in rediculous notes that are sustained for many, 
> > many bars
> > (sometimes in the hundreds or more - going off right side of the matrix 
> > editor). These
> > note durations all have to be manually corrected by dragging the end point, 
> > or retyping
> > values in the event list (the latter method is fastest & simplest when the 
> > notes are really
> > long or if one can't 'see' the end of the note).
> > 
> 
> You need to introduce yourself to one my most commonly used keycommands in 
> the matrix editor - the one that shortens the lengths so there is no overlap. I 
> forgot the exact name because i have been using my own keycommand for many 
> years. I'll look it up and report back. it usually works well in all cases - just 
> select all and correct note overlaps by shortening the lengths by the 
> keycommand or the menu item. At most you'll have the very last note to fix manually.
> 

But what does that global operation do to notes whose duration is intended to go beyond 
the onset of other notes?

> 
> > And also , btw, I'm still seeking for the 'simple' method of preventing 
> > plug-in reload when
> > switching between multiple open songs.  Someone on this group had mentioned 
> > that they
> > had heard of a way, but couldn't remember it.
> > 
> > 
> 
> I'd like to know that too. It can take a minute or more when switching songs. 
> And despite that, it seems that RAM is filled up quite easily when both songs 
> are open.
> >

Sometimes much more than a minute (it seems) in the case of EWQLSO plugs (well, it 
seems like much more than a minute -  a 'minute or more' can seem like an hour when 
you're trying to work).

MS

Re: [Logic_Cafe] Re: Can't Freeze files w plug-ins. error -40 (solved)

2005-08-19 by GAmoore@aol.com

> > ...resulting in rediculous notes that are sustained for many,
> > many bars
> > (sometimes in the hundreds or more - going off right side of the matrix
> > editor).
> You need to introduce yourself to one my most commonly used keycommands in
> the matrix editor - the one that shortens the lengths so there is no overlap.

But what does that global operation do to notes whose duration is intended to go beyond
the onset of other notes?



it works really well on mono stuff - and makes no overlaps. surprisingly, it works pretty well on polyphonic stuff too - for example block chords. Its actually quite cleverly designed. However, once in a while, it messes up, so in those cases I hit UNDO, and select only the notes I want to process. That always works fine. This can also be used to get rid of duplicate notes.

I think its called "Note overlap correction" in various windows. Its really a pain to find how a keycommand is defined. In previous of logic, you could open the key command window and type a key and it would highlight its assignment. but not now, no matter what I do. I guess logic is 3 steps forward, 1 step back. There is also a "force legato" which extends the lengths to fill in the gaps.



> > And also , btw, I'm still seeking for the 'simple' method of preventing
>; > plug-in reload when
> > switching between multiple open songs. Someone on this group had mentioned
> I'd like to know that too. It can take a minute or more when switching songs.
> And despite that, it seems that RAM is filled up quite easily when both songs
>; are open.
Sometimes much more than a minute (it seems) in the case of EWQLSO plugs (well, it
seems like much more than a minute - a 'minute or more' can seem like an hour when
you're trying to work).


Oh I know. It drives me up the wall. also the error messages that memory is running out, and refusing to move notes or claiming something is frozen when its not. If you find out, please let us know.

RE: [Logic_Cafe] Line Level or Mic Level For Guitar & iMic

2005-08-23 by Howard Lipp

robert
unless they are active pickups it is very ulikely that they are line level
line levels are 1volt peak to peak maximum

howard
Show quoted textHide quoted text
----- Original Message ----- 
From: rec 
To: Logic_Cafe@yahoogroups.com
Sent: 8/18/2005 10:26:38 PM 
Subject: [Logic_Cafe] Line Level or Mic Level For Guitar & iMic


Hi there,

I have a Fender Strat with lace-sensor pickups (Red, Silver, Blue) which are
the original ones not the newer ones. As I understand it, lace-sensor have a
higher output. For now I'm using an Griffin iMic connected to the USB input
on my PowerBook. 

Does anybody know for sure if the output of these pickups is line level or
mic level? The iMic give a choice to select between line or mic.

I think they are line-level but I don't know for sure. Also, what
measurement of output qualifies as line level?

Thanks, 

Robert




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.

Re: [Logic_Cafe] Re: Can't Freeze files w plug-ins. error -40 (solved)

2005-08-26 by GAmoore@aol.com

In a message dated 8/26/05 9:04:55 AM, loudon@... writes:

Its really a pain to find how a keycommand is defined. In previous of logic, you could open the key command window and type a key and it would highlight its assignment. but not now

Huh, I use his feature all the time and it is working perfectly. Open the Key commands window and start hitting keys on the keyboard and it highlights the command. Or go to the search field and search for a command to assign, no problem. Logic 7.1 express & Pro


- try searching for something like "nudge" then try hitting one of your key commands like "L" or "F1". They go to the same search box rather than looking up the commands.

- In Logic #<7 there used to be a button whether you wanted a key to find the key command or learn that key command for whatever command was chosen - that is no longer there. and if you define a key command for some action, then choose a new action I believe it will record whatever keycommand you have and overwrite that one. Again it gets stuck in the most recent mode without a way to get out of the mode.

- try defining two key commands to the same key (something never done on purpose, but can happen inadvertenly) - then try finding that key command again - i think it chokes and won't find either

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.