Confused with Logic level meter

Hi guys, could anyone help me with some piece of advice?I have a problem with track levels, my mixes are usually quiet, but my aim is to get them to the yet fatiguing but still standard very loud level. Also when mixing I can hear that the arrangement is groovy and punchy, but when I get it through Ozone or Logic mastering plug-ins it turns into a komplete mess without any definition, the waveform of the track is brushed heavily . One person said to get a loud nice master I need to watch the Logic Output fader meter for headroom about 6 or 3 dbs before zero and RMS about -9 db, the thing is I'm konfused now with the Level meter as RMS showing displays red klips , but the signal is actually lower, and I can see it, for ex. when klipping the signal is about - 15 dbs RMS, could anyone explain me the real way to get loud tracks, and what approximate settings should I stick to, as it starts getting on my nerves already cause I start to think I just can't do music..

First, try to separate the concepts of mixing and mastering. They're two entirely different processes. I'd suggest you first concentrated on getting your mix 'right' for you, and don't worry about the relative loudness until you've completed this first mixing stage. I wrote a brief blog post about this here which might help a little.
In general terms, you don't need to worry about occasional high levels on your individual tracks - only on mix bus on your stereo output, where a good peak level might be around -8 dbFS. That's the only place where you can't 'go into the red.'
Once you have your mix as good as you can get it, *regardless of volume,* then open that bounced file in a new Logic session. That's where you can experiment with Ozone, Adaptive Limiter, Multiband compression and other tools you can try.
You might want to do some further reading about mastering. Here are a few articles/forums which may help get you going:
http://www.soundonsound.com/sos/aug04/articles/computermastering.htm
http://community.sonikmatter.com/forums/index.php?/topic/4200-mastering-in-logic /
http://www.musicbizacademy.com/articles/mastering.htm
and there are dozens of posts in this forum - just search for "mastering"

Similar Messages

Level Meter Plug In -VS- Output 1/2 meter...Inconsistencies...

I'm mixing an 18 minute long recording for vinyl release. The vinyl pressing company has a minimum dbl on recordings they master and press. If the level is under, they charge hundreds of dollars more to re master and increase the volume via massive compression.
So to check and double check the overall volume in Logic Express 8, all I can find for a meter is the "Level Meter" in the visualization plug in toolbox. So I have the Level Meter "plugged" into the Output 1/2 track...The problem with the Level Meter is that it is showing levels around 8 dbl lower than the Output 1/2 meter. This could potentially be an expensive discrepancy not to mention may have a negative effect on the end product's sound quality.

Eriksimon wrote:
If you used a meter as an insert, it comes, like other effects plugins, before the fader. Sorry, I didn't read attentively the first time.
Still, the effect is the same as pre-fader metering. The signal passes the meter before it goes to the fader. If you turn pre-fader metering on you'll see that your faders don't affect the channel strip level meters anymore and behave like inserted level meters as well.
So if you lower the fader on channel 1&2 so you no longer see clipping, how does it work?
1. Does it lower the output simply telling you that you are not clipping going out from fader 1&2?
or
2. Does it lower the input from all contributing channels so that the source coming to fader 1&2 no longer clips?

The level meter is so sensitive:-)

i knew the Logic level meter is that kind of said "digital meter". but i'm still lost
in it. what's exactly the "digital" here mean? seems it's related with frequencies and spectrum. any one knows that?

maybe not. specially that output tracks. the same audio tracks data, in Cubase SX3 never clip but in Logic....i have to pull down tracks' level down much.
i can handle the clip level on multi-tracks by my experience in both ProTools and CubaseSX. but in Logic, sometime i have to pull down fader again and again...

OS UDM with instace level logic

I am working upon a logic which is written in perl script. This particular logic trigger's an event after checking for each database instance when running from a cron. Now that i am using same script to trigger alert with in OEM. As i see with in SQL UDM i have a target property for instance %SID%. But when it comes to OS UDM i dont see any such kind as expected as i am dealing with OS level. So here is my problem, i would like to know how can i use this perl script to check for all the instance with in the server and trigger us an alert.
Your responses are very helpful for me to nail this down.
Thanks.

Sorry for not being clear .. let me put in this way, Say i have an Perl script which checks if any users have user id are equal to password with in a database. This script works on server if we set the database environment and then run this script. So now if i want to place this script with in OS UDM ,As EM doesn't set up the database environment and we can't check for all the instance upon a server with in single UDM. I am puzzled in here how to make this script to be worked as per the need. As in case of corrective action if i take if i use same script to be ran for a corrective action of an event, i have a target property called, %SID% which takes the SID value with in SQL UDM. and i couldn't find similar target property for instance in OS UDM.
Thanks.

After downloading and installing additional content, no sound will play. Logic has no connection to sound library. No level meter activity. Right before i installed additional content I was working on a project, and everything was OK.

After downloading and installing additional content, no sound will play. Logic has no connection to sound library. No level meter activity.
Right before i installed the additional content I was working on a project, and everything was OK. What is wrong. How do I make Logic reconnect to the instrument files?

Whitelab Records wrote:
So, 20 views and nobody's anybody the wiser?
A small update to this issue....
I have been trawling the forums to find an answer but to no avail...
And... I've tried exporting and bouncing individual stems and the full session, either by muting all bar the stem or soloing the stem.....and still nothing.
Same problems.....everything is audible in audition but nothing plays on playback.
Since the 'prelisten' channel strip is Solo safe this would indicate that you have a track or channel strip soloed somewhere else, out of sight. Are the Mute buttons on your channel strips blinking?
To view all objects in your mixer, click the button. You may have to scroll sideways to check the whole mixer.

The problems with Logic (as I see them)

Hello Everyone,
Please keep in mind that I am writing this with the intention of expressing my frustrations, and what I feel would make Logic a better program. I realize not everyone will agree with the importance of what I say, but I am a firm believer of HAVING THE OPTIONS. Let the users choose what works for them and how they can best accomplish the tasks that they need to with their individual workflow.
That being said, here is my list of Logic's faults and why I often call Logic "Illogic".
General:
* Logic should have a feature to automatically save your song every X number of minutes. Final Cut Pro does this, why doesn't Logic? It should prompt you "Logic can automatically save your project if you save it" (assuming the current file is 'autoload') to remind users that they should create a project name and save their work.
* There should be a preference option for all windows to open as 'float'. Once upon a time holding option while double clicking parts would open them as a float (though having to hold down option every time in my opinion is an inconvenience, because I personally ALWAYS want my windows open as a float), however.. now in 7.2 that does not seem to work anymore. So, theoretically after you set your prefence to 'always float', then the when you hold option or control and click on a particular window, it will bring that window to the foreground...
* The loop region at the top of the screen is larger than the time-line ruler tab. This is the #1 annoying thing about logic. so many times, I click on an area of the ruler tab to start playing at a specific section.. and somehow I ACCIDENTALLY click on the loop area... If I could ask for ANYTHING it would be that there is an option to disable LOOPING turning on and off from clicking up there. My 2nd request would be that the ruler tab be re-sizeable so that it can be larger than the loop area. This is especially the case for the matrix window where it default opens up to a sizing where the actual time line is so tiny, and the loop region is HUGE.... Every time I open a matrix window I have to resize this and again the loop area is 2x as big as the timeline area, so I end up wasting screen space just to avoid the annoying loop feature being trued on. My suggestion is, require that the loop button on the transport be the only way to turn on the loop feature (other than key commands), and only when it's turned on can loop points to be set. Why is the loop area so big anyway?!?!
* Logic should offer a TALK BACK MIC button which will utilize the built-in apple microphone or iSight microphone and allow that to be sent to the audio interface. This would be an extremely useful feature for studio recording setups.
* Starting logic takes approximately 5 minutes for me. It says "scanning exs24 instruments" for the majority of the time, and I admit my sample library is huge. however, my sample library has not changed in over a year. Why does logic have to continuously scan it??? Can it not make a reference of how many files, compare and if its larger-- then scan???
Song Loading:
* When audio files are not found during loading a song, it asks you the first time what you want to do "search", "manual", and "skip"... if you click "skip", and then it finds another missing file, it no longer presents you with the "SKIP" option.. but forces you to either search or skip all.. Let's say you have a project that used 5 audio files that are all missing because you had them on a different hard drive, but have copied the data somewhere else. The first two files it asks for you don't need.. but you know where the 3rd file is.. So your plan is to skip the first two files and then click manually for the 3rd.. but oh.. YOU CAN'T DO THAT! You have to find your first 2 files if you want to even have the option to locate your 3rd file... Unless you are planning to locate the files within the audio window-- but still, Logic should not be so unfriendly.
Further, If you choose "manual", and what you're looking for isn't where you thought it was-- You realize you actually want to search for it.. So you click cancel and guess what.. It assumes you want to skip it, and so you either have to reload your project again, or deal with this in the audio window. Bottom line is this window should always have "Search", "Manual", "Skip", and "Skip All".
* When you open another project, Logic DUMPS all of the audio instrument data in memory. This is one of the worst things about logic. If you are working between multiple files-- such as when scoring a film, and you are using different files for different cues, then this becomes a complete nightmare and a waste of your time. Logic should be assessing "What instruments are in common between these two projects"... And utilizing all audio instruments to the best of the machine's memory capacity. There is no reason for Logic to behave like this.. I've had to revert back to previous versions of the same song because some data was different, and I am just trying to visually compare various settings one from the other.. Just clicking from one project's window to the other requires me to have to wait 3-4 minutes while Logic loads all these audio instruments (WHICH ARE IDENTICAL IN BOTH PROJECTS BY THE WAY!!!).. This is just incredibly dumb, and creatively stifling.
* BUG * -- Mind you, if you have two projects open, and you close one.. Logic begins loading all the audio instruments of the remaining project.. If you close that project as it's loading audio instruments, Logic will crash.
Matrix Stuff:
* BUG * If you have a part with lots of notes, and you begin to make a selection and scroll horizontally through all the content until then entire part is covered in the selection... After you release the mouse button and make this selection, quite often many random notes are unselected. This can be demonstrated by watching the following quicktime move:
http://www.collinatorstudios.com/video/logicbug.mov
* When you select a single note in the matrix window, it sounds.. This is a GREAT feature... However, when you make a selection of multiple of notes, they all sound at the same time.. This is just plain dumb. It once blew up my speakers... There is NO reason why a multiple selection would need to sound.. It's just dumb.. bad for your speakers, bad for your ears. The rule should be, if selection box = yes, then sound = no... else, sound = yes.
* When viewing the matrix window while recording, all note events disappear until after recording stops. This is highly annoying (and illogical) as it causes confusion if you are relying on watching the note events in that part to know where you are supposed to come in.
* The grid cannot be set to divisions other than 2 or 3. Musicians use 5 and 7!!! And also, can logic please offer an option to display the grid as NOTE symbols... It is much more musician friendly to see a 16th note with a 3 over it than "24". 24 means nothing to me as a musician.
* Quantizing should allow custom input for tuplets.. So that users can quantize odd figures such as 13:4 for example.
* If you move the song locator to a specific time location in the arrange window, and then double click a part to open it in the matrix window, the window is not opened to the locator's position. Thus causing annoyance and confusion as far as what the user is even looking at.
* During horizontal scrolling of the window, the locator temporarily disappears, making it difficult to find where the locator is-- which usually is a marker for us to know what we are trying to find-- ESPECIALLY WHEN YOU OPEN A WINDOW AND IT'S NOT EVEN DISPLAYING THE SONG LOCATOR'S POSITION!!!
* If you have two parts on the same arrange track, adjacent to each other and you enter the matrix window of the first part.. (assuming the link/chain icon is lit) When you scroll to the end of the note data, logic automatically takes you to the next part... The problem with this as it is, is that it does not take you to the FIRST note event of the text part, but rather continues to align the song locater with where ever it previously was (so you end up viewing somewhere further down in the next part).. To clarify, say you have a part what begins at MM-7 and ends at MM-14, the 2nd part begins at MM-15 and ends at MM-22.. If you begin scrolling the song locator past measure 15, then suddenly you see measure 22. When you really should be seeing measure 15. This is confusing and weird.
* Every time you enter the matrix window of a part, the chain/link button is on. For me, this is incredibly annoying. There should be a way to set this so that the button's default is OFF...
* When you move the mouse around the matrix window, whatever pitch corresponds to the vertical location of the mouse--- that particular key of the piano keyboard on the left side of the window should highlight so you could clearly see what note you are hovering over.. Logic tries to help with this by offering things like contrast options for C D E, but this clearly would be much more helpful.
* With the velocity tool you can (MOST OFTEN ON ACCIDENT) double click on empty space in the window and cause all note events in all parts to appear on the screen-- Yet once you do this, you can't double click on a particular part's note to only display that part again. You have to switch to the arrow tool to do this. This is inconsistent and ILLOGICAL...
ON A SIDE NOTE: PLEASE ENABLE A FUNCTION TO DISABLE THIS "ALL NOTES OF ALL PARTS APPEAR" when double clicking on empty space feature! I want NOTHING to happen when I double click within the matrix window... Make it a button within the window or just an option in the drop down menu only. * BY THE WAY * When you DO double click the background of the matrix window and multiple parts appear.. If you move notes of one part to match it up with other, it is incredibly slow. there is a 1-2 second pause each time you move a note move.. My g5 fan goes on each time I do this.. I'm sorry, there shouldn't be anything too CPU intensive to accomplish this simple task!!! I am only viewing 2 parts at the same time and it's slowing down my cpu...
* Occasionally when I adjust note lengths, I accidentally double click on an actual note.. This opens the event list editor, and there is an intermittent bug where this note sounds-- and for some reason when the event list opens, the note sounds on top of itself a million times, so the result is a super loud flanged note which again, almost blows up my speakers and hurts my ears... PERSONALLY, I would like an option that DISABLES the note event list from opening by double clicking. Preferences currently has "double clicking a midi region opens: <selectable>"--- why not also have "double clicking a NOTE in matrix window does: <selectable>"-- and please allow "DO NOTHING" to be one of the options.
* Why does the finger tool only change the end position of the note event??? Should this not be replaced with the bracket tool which appears automatically when using the arrow tool on closely zoomed in notes? This finger tool seems like an outdated old logic feature which has been replaced and improved upon. What would be nice is to have this bracket tool where we can be assured we are altering note start and end positions without moving things.
* In the hyper-draw >> note velocity section--- This is highly annoying to work with... It's far from user friendly. first of all, to move a note's velocity position, you have to click on the "ball".. if you click on the line, it does nothing.. Because the ball is so small to begin with, quite often the user is going to miss the ball and somehow begin to "START LINE"-- Which is weird because it's activated by holding the mouse button down briefly. There really should be a "line tool" for this, because "START LINE" is too easily accidentally activated-- this is frustrating for the user. Most important though, these 'velocity markings' should be adjustable by clicking on the line as well-- not just the ball.. there should be a 2-3% area around each ball/line which logic will recognize as part of the ball/line so that it can easily be moved. I also feel that there should be some specific features for this section, such as a way to select multiple note velocities and apply a random pattern to them, or apply a logarithmic curve to the line tool. Yes, you can accomplish this stuff somewhat with the transform tool-- but this way would be more user friendly, and allow a lot more creative flow.
Event list/Tempo list:
* When one event is selected, by moving down X number, holding shift+clicking SHOULD select all events between those two points. However, the shift key for some reason acts as the OPTION key does in the finder-- (meaning it will only add one additional selection at a time).. This is highly inconsistent with the actual behavior of a Mac... Open a finder window and hold shift and click on items that are not vertically next to each other and a group is selected... Now do it in logic, and it causes GREAT frustration and annoyance. What happens if you have a million note events that you want to erase? You have to go page by page and click with shift on each one?? Or drag a selection and wait for logic to scroll you to where you want to go?????????? No thanks.
Arrange stuff:
* "REGIONAL CONTENT" (meaning the visual representation of note events) does not accurately depict the event data as note lengths cannot be visually identified. Everything shows up as a generic quarter note... My #1 suggestion is that regional content should be customizable so that you can view it in a miniature matrix data style. The biggest problem for me is that I cannot see where my notes end-- I can only see where they start, this makes it very difficult to identify what I am looking at.
* Track automation data should only be inputable by the pencil tool. I cannot mention how many times automation data has accidentally altered when using the arrow tool. The pencil tool should allow you to raise and lower the lines reflecting automation data... What is the point using the pencil tool for automation if it's only function is to create "points" yet you can also create points with the arrow tool..??? Pencil tool should act as the arrow tool does in the sense that it raises or lowers automation data.
* Recording preferences do not offer the option to automatically merge new part with existing part when a region is NOT selected. How annoying is it to have to select a part every time you want to record something just so it will be included in that original part!
* Ruler at the top of the screen should also give an option for tuplets. 5, 7, etc.
* When in record mode, if you click on the ruler to another time position, all audio instruments cut out and it takes approximately 3-4 seconds before tracks begin playing audio. This becomes very annoying if you are trying to do a pick up and want to just start 1 measure before hand.
* There should be a way to EASILY (without having to cable two tracks together in the environment) temporarily link multiple tracks together so that automation data will be duplicated. So theoretically you can link 3-4 tracks together, and by adding automation data to one, you are adding it to all 4.
* If a part is soloed, and you hit record. The part stops being soloed and you can no longer hear it. This makes it impossible to record a pick up on a soloed track unless it's locked, but it shouldn't need to be locked.
* When you are zoomed in tightly, and you are trying to align notes within two parts on different tracks (meaning using the PSEUDO NOTATION DATA that appears in the part to align), there needs to be a VERTICAL line that snaps to the note closest to the mouse cursor. When trying to do this in parts that are a far vertical distance apart, it becomes VERY difficult to eye this alignment. Logic does this with automation data.. but for some reason they left it out for actual part alignment...
* There should be a way to force the downbeat of a measure to occur at any given moment... What I mean by this, is composing for film is an absolute PAIN in Logic. Scenes, last for odd amounts of time, and Logic's reference manual claims that you can solve this by using various tempo tricks, however it is ineffective for the most part. What Logic needs is the ability where you can click on a drop down menu item within the arrange window and FORCE that where ever the song locator is, the rest of the measure is eliminated and a new measure downbeat occurs right there. This will allow you to always have new scenes on the downbeat of a measure without having to mess with your tempo and meter.
Hyper Edit Window:
* I can't even begin to comment on this... The hyper edit window is one of the worst things I have ever seen in a music/audio program. It is a horrible interface, you can't get it to do anything correctly without messing everything up. This thing needs a complete overhaul... I mean, just try to create a simple crescendo with note velocity and it will take you all night.. Try to add pitch bend data, and it adds note velocity data as well.. It's a total nightmare, and I would love to hear someone's practical application of this window.
Score Window:
* The method that the song position locator moves along with the notation is very strange. It is not at all how a person's eyes function when reading music. A much more logical approach to this would be for a transparent colored block of some type to highlight an entire measure, and each note head will glow as it sounds. The current way is so strange, it speeds up and slows down-- makes absolutely no sense, and it is more disruptive than anything.
* When the Hyper Draw > note velocity area is exposed, if you use the velocity tool to increase/decrease a particular note's volume, the data in the hyper draw window does not update in real-time as you use the velocity tool. This behavior is inconsistent with the matrix > hyper draw's note velocity section-- where as in that area, the velocity ball/lines do update in realtime.
EXS24:
* when you are in many levels of subdirectories and you are auditioning instruments, it becomes very time consuming and annoying to have to continually trace through all the subdirectory paths. There should be a feature directly under the load instrument window that takes you to the subdirectory of the current instrument.
* Seems when SONG SETTING > MIDI > "chase" is turned on... When starting sequences using audio instruments, (I am using a harp sample within the exs24), there is a latency hiccup upon starting, which is very disruptive when trying to listen to a short isolated moment in a composition. And I do want to chase note events in general-- but this present situation makes it difficult for me to work. I would suggest that you can specify tracks to exclude chasing.. Or fix the latency hiccup issue.
Thank you.
-Patrick
http://collinatorstudios.com

this is excellent patrick. can you number your points so that the thread can be discussed?
1. yes
2. ok
3. great idea
4. even better idea. you could set something up with aggreagate device i suppose but it would be better to have the feature to hand.
5. you need to look into your project manager prefs. scan the paths and the links to the audio files will be saved meaning they will load up in a fraction of the time.
6. yes this is nuts. you can skip all and sort it out with PM but then you shouldn't have to.
7. this exists already. perhaps it ought to be a default but you need to set your esx prefs to 'keep common samples in memeory when switching songs'. then it will do just as you wish it to. you can also use the au lab in the devlopers kit which will allow you to load in au units etc seperately from logic, which logic can then access. this is a good way of getting around the 4 GB memory limit with logic too.
8. ok, don't know about this bug.
9. yep happens here too.
10. doesn't worry me this one. you can turn off midi out.
11. yes this is silly.
12. well, i think this is something we can get used to. i am a musician and i am used to seeing '24'.
13. you can already set up groove templates to allow for quantizing irrational tuplets. i do it all the time. i would like to see step input for irrational tuplets though.
14. yes this is silly. the button for the KC 'content catch' is getting very worn out.
15. ok.
16. not sure i understand this one.
17. yes this drives me nuts too. i have to lock screensets to get this to stay off.
18. you can use KCs for 'go into/out of sequence' - but yeah.
19. ok
20. there are a couple of features that use old technology that cause hangs and poor performance. score is a good example of that. maybe the matrix is too. the score is being updated we assume with newer technology maybe the matrix will too.
21. there are probably better ways of adjusting velocity than using matrix or hperdraw velocity. have you tried holding control-option and click dragging a note in score?
22. as i pointed out in 20, this is an old feature. you could change things to be consistent with modern macs and annoy long term users such as myself, or leave them and let them be inconsistent to confuse newbies. i think depending on what it is we oldies could upgrade our work habits.
23. this one doesn't worry me so much.
24. good point (no pun intended).
25. well, i find the opposite - that merging new parts to objects i have accidentally selected to be annoying. perhaps more detailed prefs?
26. yep.
27. this will be down to your audio settings. you can improve this lag but it will be dependant on the capabilities of your system.
28. i don't know why this feature doesn't work in logic. it is supposed to have ti already and i just don't understand why it doesn't. maybe it will be fixed in the next upgrade.
29. agreed.
30. ok - i have other work flows for this but it would be nice.
31. i don't agree that logic is a pain to score with to film, i do it nearly everyday. but you are discribing an interesting feature which might be worth discussing more. i think you might find yourself getting alarming and unmiscal results doing this that will end up having to be sorted out the conventional way. but its a good idea.
32. oh yes.
33. yeah - this could be improved.
34. ok, well i wouldn't go about it this way, but yeah there is generally sticky spots with regards to updating of information al around logic.
25. very very good idea.
26. there are lots of problems with the chase function. very annoying. i certainly agree with this.
in general, some of these could well be done as their own threads. some of the missing functionality may exist. if you can confirm a bug then you are on stronger ground when you submit feedback. but this list is full of fantastic ideas.

The Problems With Logic (as I see them) - PART TWO!

Hello again,
It seems to be a tradition now that as I compose on a track, I keep a text editor open so that I can jot down all the annoyances and problems that I encounter during my creative process... Anyone who missed the previous edition of this topic, please visit PART ONE, here:
http://discussions.apple.com/message.jspa?messageID=3605456#3605456
That said, here I give you "The Problems With Logic Part II":
1. Logic should clear the playback buffer everytime you play. Quite often you start playing and there is trailing reverb/note events from various audio instruments and plug-ins.
2. The sample edtor "save selection as" has no memory of where you previously were in the file browser.
3. If you double click on a wave form, the sample editor opens up with the wave form you double clicked on... Great.. But now, if you go and double click on another wave form somewhere, it just takes you back to the sample editor with the same previous wave form selected (not great). This is incredibly annoying if you are attempting to save out certain edits-- Quite often you will end up saving 5 or 6 of the same exact waveform, thinking you were saving each individual one. GRR!
4. Key commands.. if you try to assign a key command to something that is already used by another feature, you are presented with a window warning you that it already exists.. If you click cancel, then you can no longer enter any keys in the key field.. You are forced to close the key commands preferences window and start over.
5. Key command window: You should be able to search by command.. For example, if I want to find out what "o" is assigned to, I should be able to search by O-- Further, you should be able to sort the key commands by clicking the column titles "key", "command" -- or "midi"... After all, we can sort by name, date, size, etc in the finder by clicking on these column titles.
6. Tempo Tap feature-- I am quite confused by this. There should be a simple way to tap and define a tempo. When ever i try to do this, the tempo is only temporarily changed until I stop playing, and most of the time I get error alerts about trying to sync audio and midi (mind you, when there are absolutely no parts in the entire arrange window). The manual states that with "tempo recording" checked on the tempo interpreter window, that the taps will record tempo changes, but this does not work. I tried doing this, tapping the key command I defined to tempo tap (ctrl-shift-t), and I was tapping at various speeds-- many taps fast.. and Logic recorded tempos of 99-101bpm.. I was tapping atleast around 175-180bpm. I then tried tapping slowing, and Logic recorded tempos of 99-101 again... so this feature obviously is full of bugs.
7. When loading songs, as soon as various plugins such as Kontakt, exs24 begin loading samples, it brings logic to the front. If you're working in the background in other applications while waiting for your songs to load, you are rudely interrupted from what you're doing (such as, selecting from a menu, typing a document, etc) only to be forced to watch a status bar fill up.. and then all key presses at that point become error beeps.
8. Logic's sample memory easily becomes messed up and crazy. Quite often when using AU instruments such as BFD, Culture, and even Synthogy's Ivory. I will switch to that particular track to play on my keyboard, and each sample will be full of horrible pops and clicks-- the kind that destroy speakers. Other times, in a sample of a string for instance, all of a sudden after one second will be a pop and then the sample will be playing at a completely different pitch... I have to remove the AU instrument and reload it at this point.. This happens quite often. Logic should offer a 'buffer reset' so that you can just flash plugins but they reload whatever preset they were set to.
9. Volume faders resolution are lame! There is no reason why you shouldnt be able to access +1.0, +1.1, +1.2, +1.3, +1.4, +1.5, +1.6, +1.7, +1.8, +1.9... Further the display is only so wide and you can't even read the decimal values for numbers -10 and lower. They just appear as 10.
10. When a movie is open, and you are viewing the video output via FIREWIRE, there is a mini-floating window which contains the smpte, position, and movie start information-- However you cannot modify any of these values. You have to switch video output back to "WINDOW" to change the start position of the movie. This is obviously a bug.
11. Changing the movie's start time is very user unfriendly. There should be a simple way to specify to start at a moment of time relative to SMPTE-- So you can just say "+9:15" for example, and it would take you in 9 minutes and 15 seconds, rather than how it is now where you have to think backwards from SMPTE code and subtract.
12. You cannot view video as a window AND output to firewire. There is no reason why you shouldn't be able to do this. For example, if I wanted to output my video to a monitor in a vocal booth-- I can do this.. but I can't see what the vocalist is seeing on my own screen! This is just nonsense. You should be able to output to the screen (desktop mode or floating window) as well as an external firewire device.
13. Saving a song with a movie open should mean that when you load that song, the movie should be up and exactly as it was prior to saving. As it is now you have to select "open movie again".
14. There is still definitely a bug in track automation-- this was really bad back in version 4, but there is still something not quite right here where starting playback will not always guarantee that the automation data is being read.. And in my experiences it results in volumes being incorrect until you stop and play again, and in some cases it will not work at all unless you plot some automation points. This is an intermittent issue-- but quite often activated by placing an audio region from the audio window on a track (SEE VIDEO).
WATCH VIDEO OF THIS BUG:
http://collinatorstudios.com/www/logicbugs/logicautomationbug.mov
15. In the arrange window, sometimes when zoomed in tightly, all parts on a track are selected, and you think that only the part that you are looking at is selected.. you move this part, and now all of your parts are off. Logic should have some kind of visual aid to let you know when ever you are moving multiple selections... Something like, the parts you are moving will highlight a dfferent color or something... This is a similar problem I have with the loop area of the screen.. You can accidentally turn it on when in the matrix window, and have no idea unless you look down at the transport, but with me for example, my transport is at the very bottom of the screen and I am not looking there most of the time.
16. Automation data, when two points are semi-close to each other, suddenly the value of the data is no longer shown.. I can understand that when you are zoomed out, and there is simply no space for this to visually appear, that's appropriate. But as it is now, it doesn't display this information when there is plenty of space for it to be visible.
17. Logic should let you set audio track inputs to the various outputs (1-2, 3-4, etc) and buses.
18. clicking on a track selects ALL parts. This is so so so annoying. How many times have I been editing voice over, and selecting a track, thinking I am shrinking the length of a part, and to find that ALL parts have been shrunk.. SO ANNOYING!!!! This needs to not happen, and there should be a simple way to right-click a track and it will have an option "select all regions"... also, when you click on a track and all parts are selected, if you horizontally zoom, logic zooms into the beginning of the track, rather than the song locator. I don't know what the LOGIC behind this is, but it's not very helpful, it actually is very frustrating.. Zooming should always move towards the song locator position.
19. EXS 24 should have a "reverse/backwards" button so that samples played are backwards.
20. Logic should offer a way to globally increase or decrease a specific automation type (especially volume) globally for all tracks... So if you have detailed crescendos that start at -3.8 and end at +1.6, you can add 3db to this and it will now be at 0.8 and end at 4.6.
21. If you have multiple tracks of the same track (such as three Audio track #1's)-- say you are recording guitar parts, and just copying the track and muting the previous track as a method of maintaining multiple takes for later auditioning. If you draw automation volume data on this track (it appears on all 3 tracks), and then if you delete the audio from one of the muted tracks and tell logic to KEEP it, suddenly all automation data is gone. GRR!!!
22. Several times I have opened Kontakt, and attempted to load an instrument while outputting a movie via firewire video to my monitor. As soon as I try to load the instrument, the firewire video output on my monitor goes crazy, and then comes back on.. Logic then crashes. This has happened 3 times randomly...
23. UNDO does not work on every function. for example, if you change an output to bus 1 instead of 1-2, you cannot undo this. Undo should undo whatever the last command was, no matter what it was. This is what the word LOGICal is supposed to represent.
24. Floating windows (as in plugin windows) should close with apple-w!!!
25. *BUG* If you are in a part that is say 10 measures long, zoom in horizontally 100% in the matrix window-- You then isolate one specific quarter note pitch in the middle of this measure, and have cycle turned on, looping over this one quarter note, if you are not looking at this note event/loop region when you hit play, the display will jump to the beginning of the part and never show you this note event as it loops. However if you have the note event on screen when you hit play, then it will behave properly. This makes it extremely difficult and frustrating to perform detailed hyper-draw work. (SEE VIDEO)
WATCH VIDEO OF THIS BUG:
http://collinatorstudios.com/www/logicbugs/logicloopbug.mov
26. *BUG* Host Automation is not accurate. I assigned Kontakt's tune knob to C#000, and If I place a dip, the knob begins to move way before the automation data is even present.... So basically what I was trying to do, can't even be accomplished because Logic screws everything up by pitching the instrument too early... Such a shame.. By the way, I previously mentioned the importance of being able to display part data in the arrange window as matrix data (horizontal lines) rather than score data. Someone argued what good this would do-- Well this is a perfect example, if I am attempting to affect a particular section of a note with automation, I can't possible visually see where this is because the length is not described by the current score representation. Having a horizontal representation would solve this problem... (SEE VIDEO)
WATCH VIDEO OF THIS BUG:
http://collinatorstudios.com/www/logicbugs/logicctrlchngbug.mov
27. There should be a way to convert stereo samples to mono in the sample editor.
28. When you view "as text" in the environmentt, you cannot drag an object to the arrange window-- Such as to create a bus track.. Now mind you I don't know why you can't just select "BUS" when editing a track in the arrange window in the first place, however there is no reason why 'view as text' should behave differently than when it's viewed as icons.
29. When you drag a bus from the environment to the arrange window, it replaces whatever track was there. It should ADD a track instead of replace-- atleast there should be a preference for how this behaves.
30. Occasionally when dragging a bus from the environment, there is some visual garbage in the track automation (see screenshot).
31. There should be a way to LOAD and SAVE selections in the arrange window. Quite often when editing audio from a countless number of parts/regions, it becomes painful when you have to select and move 100s of audio files. There should be a way that you can just select a ton of regions and save that selection, and reload it at anytime. There are a few 'select' tools/options under the edit window, however they are song specific-- not track specific. So they are completely usesless for what I need.
32. Logic should offer a feature to collect sysex data from midi devices so that patch names show up and can be selected via program change.
33. When no track or part is selected, and you vertically zoom in, Logic should zoom into the center most track.. It behaves very oddly and zooms in more towards the top. This becomes extremely annoying when dealing with a sequence involving 100 tracks, and a part is selected but you scroll far below where the part is.. When you begin to zoom in, it takes you towards the selected part, yet it's not displayed on the screen and you have no reference for what you are even looking at. The rule should be this: If the part is on the screen, zooming vertically will bring you to it. If it's off the screen, you will zoom into the center track of whatever is currently on the screen.
34. I mentioned this in a thread earlier... http://discussions.apple.com/thread.jspa?threadID=752485&tstart=0
There is a bug when using the transform tool involving the 'position' variable. In my example, I was attempting to reverse the time placement of three chords, that occured in a part somewhere in the middle of my song. By selecting the measure start and end of this part, Logic was unable to select or operate with the transform tool (and I tried a variety of transform options). If I moved this part to the beginning of the song, then the transform tool would suddenly work. After some research, I found online someone had said "Position Time position of the event, referenced to the start of the MIDI Region (not of the song)."--- But if I still doubt this is true, because I then placed the part on a new track with no other data, and placed it in the middle of the sequence and in the transform tool under position I selected '1 1 1 1' to '5 5 5 5' as well i tried setting the position to 'all', and none of this worked. This obviously is a bug... If it's not then it's a very serious design flaw. The position should relate to measure numbers of a song, and nothing else.
WATCH VIDEO OF THIS BUG:
http://collinatorstudios.com/video/transform.mov
That is all for now...
For those who firmly agree with me and all of the points that I have brought up now and in the past, I encourage you to contact Peggie Louie, (the Logic HR department contact) at (408) 996-1010 and suggest that she hire me as a consultant to help eliminate Logic's many annoyances. I have tried to pursue this heavily in the past, but sadly I was completely ignored by her on all levels. Maybe you all can help make a difference?
Fighting the good fight,
Patrick J. Collins
http://collinatorstudios.com

11. Changing the movie's start time is very user
unfriendly. There should be a simple way to specify
to start at a moment of time relative to SMPTE-- So
you can just say "+9:15" for example, and it would
take you in 9 minutes and 15 seconds, rather than how
it is now where you have to think backwards from
SMPTE code and subtract.
For this one I'd suggest getting SMPTE calculator. Entering timecode numbers and having to add and subtract is not so difficult, and AFAIC part of a composer's gig. But what I would add, instead, is that it would be fantastic if Logic provided a timecode calculator (edit: even if it was in the form of a custom Logic widget).
13. Saving a song with a movie open should mean that
when you load that song, the movie should be up and
exactly as it was prior to saving. As it is now you
have to select "open movie again".
This doesn't always happen. I've struggled with this for a long time, and I don't know why sometimes the movie will load and not other times. I would also add here that Logic should show the file pathname to the movie. Somewhere...
18. clicking on a track selects ALL parts. This is
so so so annoying.
You can prevent this from happening if you have cycle turned on and set to a set of locators that "contain" the parts you might want to select en masse. I always work with cycle=on so this is not a problem.
21. If you have multiple tracks of the same track
(such as three Audio track #1's)-- say you are
recording guitar parts, and just copying the track
and muting the previous track as a method of
maintaining multiple takes for later auditioning. If
you draw automation volume data on this track (it
appears on all 3 tracks), and then if you delete the
audio from one of the muted tracks and tell logic to
KEEP it, suddenly all automation data is gone.
GRR!!!
Never had that happen. In my experience, telling Logic to keep the data always works.
23. UNDO does not work on every function. for
example, if you change an output to bus 1 instead of
1-2, you cannot undo this. Undo should undo whatever
the last command was, no matter what it was. This is
what the word LOGICal is supposed to represent.
Undo in Logic is highly problematic for other reasons. Here, I think there should be a specific Environment Undo, just like there's a separate undo for audio edits.
29. When you drag a bus from the environment to the
arrange window, it replaces whatever track was there.
It should ADD a track instead of replace-- atleast
there should be a preference for how this behaves.
Right. This is a matter of personal preference. But still there are other ways to get an object assigned to a track. The "thru tool", for instance. No dragging required.
32. Logic should offer a feature to collect sysex
data from midi devices so that patch names show up
and can be selected via program change.
My guess: considering how much sheer time it takes to write this kind of software, let alone debug it with every conceivable device, it's not likely this is going to happen.
That is all for now...
For those who firmly agree with me and all of the
points that I have brought up now and in the past, I
encourage you to contact Peggie Louie, (the Logic HR
department contact) at (408) 996-1010 and suggest
that she hire me as a consultant to help eliminate
Logic's many annoyances. I have tried to pursue this
heavily in the past, but sadly I was completely
ignored by her on all levels. Maybe you all can help
make a difference?
Wait in line buddy!
(LOL)
I must say, I'm very impressed with your list and attention to detail. And I feel your pain, trust me. But many of the things you've listed are feature requests and not bugs. And some of the behaviors you've described I have yet to run across. So this is typical with Logic, that it can be operated in so many diverse ways that no two people run it in the same way, nor would two people conceive the program's capabilities in the same way. But I digress...
I also think there's a certain amount of Logic convention that I don't think you've adopted yet, hence your wish for behaviors that don't yet exist.
I don't disagree with most of your feature requests, and I'm (quite unfortunately) able to say that I'm familiar with most of these bugs and about 9 dozen more. But again, it's important to distinguish between bug, feature request, time to RTFM, and errant behavior that's experienced by a very limited number of users.
There's no doubt that this program has its problems. In particular, your #1 re the playback buffer. And I'm glad you've brought many of the bugs into the light for people to read. Good work.

Number of elements at logical level / odbc driver

Hi everyone,
I'm new in BI area and I cannot understand one basic thing.
I study documentation about BI server, exactly chapter about "creating dimensions" and I'm confused about setting "number of elements at logical level"
It looks for me that "number of elements at logical level" is static.
What will be when someone update data in the table and number of elements will be different than number of elements in our logical level?
example:
current column with distinct values:
channel_desc:
direct sales
tele sales
catalog
internet
partners
in this case I set number of elements at logical level 5.
after a while some update data in the table and our column looks (see below)
column after update with distinct values:
channel_desc:
direct sales
tele sales
catalog
internet
partners
others (added value)
Does it mean that I have to change it to current numbers of elements?
I'm sure that this is misunderstanding in my case, but I don't know where?
Second problem which I have:
BI with oracle database is on linux
client software on windows
I can import data from database like sybase or flat files to the physical model, I can view data, but when I create whole model (physical, bussines model and mapping, presentation) and I try access data from "Answers" I have this error:
"Data source name not found and no default driver specified"
regards
Bart

Number of elements is just an indication used by the BI Server (e.g. when generating LOV's in Answers). It won't cause any problems when it doesn't hold the exact number of elements available in the dataset.

No of elements in a logical level.

Hi
I am very much confused with the following one. How do we know that there should be some "n" number of elements in one logical level?
"No of elements at this level......." ?
Thanks&Regards
Suresh.

Hi Kishore
thank you very much for your answer. I was searching this on google for the past one month and all searches went in vain.
But your answer is extremely valuable.
Thank you very much and keep it up.
Thanks&Regards
Suresh.

Bounce Problem with Logic

I have a good mix; Vocals, acoustic guitar, second guitar. My levels are all ok in logic, no clipping, but when I bounce , my levels are higher and there is allot of clipping. I tried with and without normalizing. Any Ideas? the mix sounds totally different from within logic to what I get on the bounce.
Help
John

Hi,
even if your levels on every single track aren't clipping, the sum of them may clip. Look at the level meter of your "out 1-2" channel, since this is the channel the bounce is made from. Is it really never ever above 0db?
Try lowering all levels to about -12db, so the mix shall be okay.
Another question: Do you use a compressor/limiter plugin in the out 1-2 channel? If not, make it a habit to do so. The limiter will prevent the master from clipping but if levels are very loud, it doesn't sound very good. Try a compressor, preferably a multipressor (Slim Slow Slider has a good free one - http://www.kvraudio.com/get/950.html )
Cheers,
Fox

Question about Level Meter Plug in

I know how to change the channel meter between pre/post fader metering is there a way to do this with Logic's Level Meter plug in and with Inspector?

Plugins are always pre-fader, as the audio path hits the plugins and then goes into the fader.
What you'd have to do is route your audio through a fader (eg aux channel) to control the level, and then leave the fader on your output set to 0dB and meter in your plugins on that.

Level meter stops randomly during input

using 64bit Logic 9- latest version. While using a channel with audio input with "I" selected in channel strip, the level meter will randomly go flat but sound is still passing. usually toggling the "R" box will get it working again, but repeatedly it will drop out- anyone experience this?? if so, any conclusions?
thanks!

I suspect a problem with your audio interface. The next time it happens, you could test that theory by trying this. Open Preferences > Audio and uncheck "Enabled" (under "Core Audio"). Press the button Apply Changes. Then check Enabled, and Apply Changes again. Does that fix it? Maybe your audio drivers need an update, or there is some other issue related to your audio interface.

Logic cpu meter spike while recording / monitoring?

Hey, I just checked Logic's internal CPU meter, and noticed something quite weird is happening.
I have only ever had one overload message, which I think was caused by changing a BFD2 setting, so the fact Logic believes that it's maxing out one of my cores confuses me a little more.
Anyway, in a template project (just unused audio tracks), if I click the record (or the monitor) button, my first core tops out in Logic's meter, but in the activity monitor, little changes, and sometimes even shows the load changing between cores, with Logic still insisting the overloading core is doing the work.
If I deselect the button, the core returns to no/little load. It doesn't seem to affect Logic's performance, but I'm more than curious about this.
Anyone have the same thing happen to them, or is there a reason for this?
Screenshots are here:
http://i4.photobucket.com/albums/y136/Ed91/Picture1.png
and here:
http://i4.photobucket.com/albums/y136/Ed91/Picture2.png
Thanks, Ed
Message was edited by: Ed Davies
Message was edited by: Ed Davies

From another post of mine:
An observation about lopsided CPU behaviour: a reliable source(an AU and hardware developer) remarked the other day that according to his tests all stuff that is on record enabled/monitored tracks can only run in a single thread using the (small) i/o buffer on one CPU.
This 'real time' CPU can easily be overloaded, while the rest of the CPU's may be idling.
You can have loads and loads of CPU hungry stuff on tracks that are in playback mode(and that use a large buffer because logic knows what is coming) on an octocore, but for record/monitor enabled tracks the octocore is just as good as a single core/cpu machine with the same specs(CPU speed/cache/RAM speed etc.)
Haven't tested this myself yet, but is sounds plausible and it would certainly explain some of the trouble I've seen with CPU overtloads.

Connecting Interface and recoding with Logic Express 9

Hi apologies if I've posted this in the wrong location. I need some help.
I have just bought an iMac (with Logic express 9) along with a focusrite saffire pro 14 sound interface.
i'm having difficulties getting a line in and out of the focusrite and into logic.
I currently have passive monitors plugged into an amp, which is then plugged into the headphone jack on the iMac, the focusrite is connected via firewire.
my mic is connected via xlr with phantom power into the focusrite, and my guitar (via an effect unit with built in pre-amp) is connected into the 1/4'' input. both signals are showing levels on the focusrite mixer software - but no sound. the only output from the sound interface is the firewire.
I can record, and play back in logic using my usb midi controller- USB direct into the iMac.
i've selected the focusrite as the driver in logic, also as the input device in system preferences on the iMac.
any ideas when I am doing wrong?
any help would be good
thanks
Chris

Hi,
there are some points where the big bear trap might have snapped onto your feet
First: You said you have selected the focusrite as the core audio input device in Logic. This is okay. But have you selected the correct inputs for the audio tracks you are recording to? You focusrite has 4 possible line inputs (1 and 2 are combined on the front in the middle of the XLR jacks, which are also inputs 1 and 2 for mics, and 3 and 4 are on the back).
When you connect a headphone to your focusrite, can you hear your mic or your guitar? (turn up the monitor volume as well as the headphones volume!)
Given you really have a good signal that goes into your focusrite, the same signal should be available in Logic *for the appropriate inputs* . It won't work if you have plugged your guitar into input 3 and have input 1 or 2 selected in the channelstrip's input selector tab.
Second: Given there's a signal coming into Logic, where does it go from there? The focusrite has 4 outputs, and you should connect your amp&speakers to them. If your amp&speakers are still connected to your iMac's headphone jack, you must select your Mac's "built in output" as the output device in Logic. The OS X preference pane has nothing to do with Logic's preferences. Don't confuse them.
Cheers,
Fox

Logical level in Fact tables - best practice

Hi all,
I am currently working on a complex OBIEE project/solution where I am going straight to the production tables, so the fact (and dimension) tables are pretty complex since I am using more sources in the logical tables to increase performance. Anyway, what I am many times struggling with is the Logical Levels (in Content tab) where the level of each dimension is to be set. In a star schema (one-to-many) this is pretty straight forward and easy to set up, but when the Business Model (and physical model) gets more complex I sometimes struggle with the aggregates - to get them work/appear with different dimensions. (Using the menu "More" - "Get levels" does not allways give the best solution......far from). I have some combinations of left- and right outer join as well, making it even more complicated for the BI server.
For instance - I have about 10-12 different dimensions - should all of them allways be connected to each fact table? Either on Detail or Total level. I can see the use of the logical levels when using aggregate fact tables (on quarter, month etc.), but is it better just to skip the logical level setup when no aggregate tables are used? Sometimes it seems like that is the easiest approach...
Does anyone have a best practice concerning this issue? I have googled for this but I haven't found anything good yet. Any ideas/articles are highly appreciated.

Hi User,
For instance - I have about 10-12 different dimensions - should all of them always be connected to each fact table? Either on Detail or Total level.It not necessary to connect to all dimensions completely based on the report that you are creating ,but as a best practice we should maintain all at Detail level only,when you are mentioning any join conditions in physical layer
for example for the sales table if u want to report at ProductDimension.ProductnameLevel then u should use detail level else total level(at Product,employee level)
Get Levels. (Available only for fact tables) Changes aggregation content. If joins do not exist between fact table sources and dimension table sources (for example, if the same physical table is in both sources), the aggregation content determined by the administration tool will not include the aggregation content of this dimension.
Source admin guide(get level definition)
thanks,
Saichand.v

Confused with Logic level meter

Similar Messages

Maybe you are looking for