Mixing in Logic, problems with levels!

Mixing problem here: I can’t figure out how to get all my equipment/ software levels correct to get an accurate level/ sound. I use Logic Pro 7 on a Mac dual G5, my sound card is MOTU and my monitors (2) are Event 20/20 BAS. Here’s the problem I believe that something is too low and I am compensating in the somewhere else and I am getting distortion in my mix downs- but I can barely hear the song. Here are my levels/ gains:
Logic Main Mixdown track: 0.0 dB
MOTU Main out: -34 db
Event Monitors input level: 7 (max is 10)
My plug-ins and such are at the level that I load them at, I don’t mess with the gains on these too much.
Should I turn something down and turn something else up so that I can actually mix correctly? Thank you for your help!
Cappy

Hi.
I have the same problem as you. I have a dual 2.7 G5 mac using a PCI MOTU 424 with a 2408 mk3 interface. Before I updated my Logic software to 7.2, The audio seemed to work fairly deccently as far as levels. I even utilize a Presonus Digimax LT via adat pipeline into the MOTU which in the past has worked great to attenuate levels digitally and Logic and MOTU worked seemlessly BUT ever since the new intel revolution, I have noticed tons of problems with the universal version of Logic. So far I would say maybe at least 30 features doesn't work properly anymore with Logic 7.2 and 7.2.1. Seems like with each new updates, the version gets worse and worse with more problems for my G5 mac. Example, Bouncing audio. Several of my settings such as plugins, levels, crossfades getting skipped or ignored and at times even crashes. I also have other issues like cracks and pops in my audio recordings lately which really is beginning to **** me off to no end. My adat transfered audio has weird pops added to the audio when transfered digitally which it didn't do before. I also noticed several playback functions that are very unstable. Some of my song files wont even play back!! My levels are no longer accurate anymore when recording in Logic. I have to crank my presonus levels just to barely hear my guitar tracks being recorded which I didn't have to do in previous versions, which also means more hisses and noises added. Apple seriously needs to correct these issues with Logic especially when we have to pay for bad updates.
Scary thing is Logic 7.2.1 seems to run much smoother using the built in audio on my 2.0 intel macbook than my dual 2.7 G5 with my MOTU gear.

Similar Messages

  • Problem with levels/meters in logic pro 7.2.2

    Hopefully someone knows the answer to my problem.
    I've loaded a wavefile that is peaking at 0, very compressed, limited, mastered etc..
    For some reason, the audio track level meter shows that it's peaking at -3, and -3 on the master as well.
    If i run the track through a bus, it knocks off another 3db at the bus and shows up on the bus and the master at -6db
    This problem is becoming very frustrating. Any help would be greatly appreciated.

    Can you explain to me what the pan law setting means?
    My guess is that it's something to do with when 2 mono tracks are made stereo they probably add 3 db per channel and need reduction? Just a hunch
    I searched the reference manual but wasn't able to find it.
    g5 2ghz   Mac OS X (10.4.7)  

  • Problems with levels and blur effects when exporting

    I'm kinda new in After Effects. I was trying to to make the effect from this tutorial http://library.creativecow.net/articles/rabinowitz_aharon/CC_Flashback/video-tutorial wich I think it could be useful for a short film I'm working on. So... i did the whole thing and if I RAM render it looks pretty near; but the trouble comes when I export the video. A white rectangle appears, and as far as my knowledge can say, I think that the effects maybe aren't being exported well.

    What render settings do you use? Could be that one of the render overrides comes into play here and stuff is rendered at different quality settings liek without motionb blur or such. Also, since expressions are involved, do not use MP rendering. Some expressions do not give correct results with multiprocessor/ multicore rendering.
    Mylenium

  • Having problems with audio jacks, connections are shorting. i need an alternative solution for mixing in logic

    i am having problems with mac pros audio jacks,any alternative solutions ?

    If you're mixing in Logic, buy a FireWire audio interface. So many people make them, that it isn't funny. Personally, I'm a fan of M-Audio interfaces for a cheap, high quality device.
    Here's some FireWire interfaces, they also make USB products.
    http://m-audio.com/index.php?do=products.family&ID=FWinterfaces

  • Using Logic 7 with Alesis Multimix8 Firewire...problem

    Hi there,
    I'm running Logic 7 on my 2GHz Macbook (White) with Snow Leopard 10.6 and an Alesis Mutlimix 8 Firewire. The problem I'm having is that I can't seem to get the playback or output to come back through the Interface. I have done all the normal things of checking the audio midi setup (both in utilities and in Logic itself) but to no avail. The signal is definitely getting from the Multimix to the computer as I can record things, but I don't seem to be getting anything coming back. I tried doing the same in thing in Garageband but got the same outcome, which makes me think its not something in Logic that I'm doing wrong. in GB, I even set the output to the built-in out put, at which point I was able to hear playback through the speakers. I've been through the logic manual and the mutlimix one but can't find anything that helps - I do everything they suggest but get nothing. Any help?!
    K

    I am in front of an Alesis board now. If you have your monitors connected to the Main Outs, then the 2TK TO MIX Button must be depressed, and the Main Mix fader will control the level of playback.
    If you have your monitors connected to the CTRL RM OUT, then only the 2 TK button should be depressed, and the Headphone/Control Rm Knob will control the level of playback.
    Hope this is the problem, and it works. The nice thing about this setup is you can connect two sets of monitors and mix with either signal and quickly move between the two.
    Also, I'm assuming you've updated to the latest drivers and firmware on the Alesis site. I think they've stopped updating, but if you installed a driver from a disk, I'm pretty sure it will be older than what you can download.

  • 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.

  • 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.

  • I have an IMac running the latest level of Lion.  Since installing Lion and also being forced to replace the hard drive I have a problem with the screen intermittently go all white.  Happens about 8 to 12 times a day.  I am using Wild Blue as my ISP.

    I am looking for anyone in the west Tennessee area using Wild Blue along with Apple IMac who is having a problem with their screen going complelely white every so often.  Have had the maching into the Apple store in Memphis.  They could not get it to fail.  Help

    TutorDaddy, if this Mac is still covered by the initial warranty or under AppleCare, take it in and have it looked at. As the old label used to say, there truly are "no user serviceable parts inside." Kernel panics very usually indicate failing hardware.
    I have an older iBook G4 that started developing kernel panics and like you, despite reinstalling the OS from a freshly formatted volume, they kept continuing. I looked at the crash log and saw that in each instance of panic, the last bit of code to be accessed had something to do with AirPort. Knowing that the AirPort software was at then current levels, I surmised the problem to be a bad AirPort networking card which, on that particular model of the iBook, was a very small module attached directly to the logic board. Since the computer was out of AppleCare, I broke the machine down myself (I didn't realize that there could be so many barely visible screws in one machine) and removed the offending piece of hardware. My iBook lives but without WiFi, it now sits as a more or less desktop machine needing an ethernet connection to stay connected to a network.
    I do not suggest you break into your iMac. First of all, I'm guessing one would need to be able to pull off the glass and have the necessary glue to reattach it, which is not really available to us consumers. If you're feeling adventurous enough to read the crash logs from each panic, you might be able to surmise the hardware component (or badly written application or library; it can happen) that's causing the panic. If it's a software issue, remove the offending software app and see if the panics return. If it's a hardware issue, it's best to let a competent service tech qualified on Apple hardware to handle it.
    [edited to add:]
    After browsing through related problems in the discussions, I saw this link to a third-party web site being handed out. Perhaps you'll find it useful: http://www.thexlab.com/faqs/kernelpanics.html
    Message was edited by: Stephen Adams

  • Problem with advanced sidechaining in logic x

    probably best i explain what i'm trying to do first!
    I'm bussing 4 different audio tracks to  bus 1 (for example) which has eq / compressor etc and outputs to the master and also to bus 2
    bus 2 has a drastic high cut on it but has no output, it is intended to be used as a silent sidechain effector
    bus 3 has a compressor set to sidechain to bus 2, but instead of sidechaining to the high cut signal, it uses the dry one.
    i used to route the same thing the same way on logic 8 and 9 but on 10 i have encountered this problem, is there a setting i need to change or is it a problem with the softwar that i'll have to add extra busses to route around?
    thanks!

    When you send (or change the output) of a channel to a bus, an Aux is created automatically in the mixer for you.  You can create more Auxes manually and set their inputs to the same bus # if you need to.  For example you could create a submix of 4 gtrs by setting the output to bus 1.  In the mixer you will now have an Aux with bus 1 as its input.  You could create 2 more Auxes with bus 1 as their input.  So you have 3 channels all with the exact same submix of gtrs.  Now you could do some parallel processing:  1 Aux has distortion, 1 Aux is clean, etc.  Say you wanted to filter the crap out of the gtr submix and use it for a sidechain on something else, you take your third Aux and put your crazy filter on it, and change its output to Bus 2.  A new Aux is created, but you can either delete it or change its output to none.  Whatever you want to listen to the crazy filter in its sidechain listens to bus 2, where that filter has been sent (from the 3rd aux above).
    I'm bussing 4 different audio tracks to  bus 1 (for example) which has eq / compressor etc and outputs to the master and also to bus 2
    Does the AUX output to Master & send to Bus 2?  or is it bad grammar (not criticizing) and you mean the 4 audio tracks also go to Bus 2?
    bus 2 (You mean an AUX with bus 2 as its input) has a drastic high cut on it but has no output, it is intended to be used as a silent sidechain effector
    OK so far
    bus 3 has a compressor set to sidechain to bus 2, but instead of sidechaining to the high cut signal, it uses the dry one.
    I think what you want is to set the output of the AUX with the high cut to an open bus, and use that as the sidechain for whatever is on what "bus 3" is.
    Maybe think of it like this:  busses are pathways, they can even be potential pathways.  If you send something to a bus it's like you plugged in a cord to a jack.  The other end of that cord might not be plugged into anything.  Or it might be plugged into the sidechain of a compressor, or an AUX channel.  In Logic's virtual world, that cord is like a Y jack with, like, 250 ends on it.  If you plug one of those ends into a filter, and one into an AUX channel, and one into a sidechain, the sidechain isn't going to hear what came from the filter.   You need another cord (bus) to come out of the filter and then into the sidechain.
    If you want to be 'clean and conservative' with your busses (and who doesn't in this economy?), you could skip the intermediate bus/channel.  Unless the compression is critical to the silent sidechain signal, you could skip sending the compressed signal to bus 2.  Change the input of the drastic high cut channel to Bus 1, and set its output to Bus 2,  Make sure no AUXes are there with Bus 2 as their input.

  • Waveform Problem and Input Level problem with Onyx 1620

    I was reading an earlier post and saw that someone was having trouble with the gray boxes for the loops as compared with GB. I am also having that problem, but with my actual recordings. Is there a way to show the waveform instead of the gray box on the main screen?
    Also i've had another problem with my Onyx 160 firewire mixer. It seems that i have to turn the trim at least 3/4s or higher to get just a small read in Logic Express. I have the input on the computer turned all the way up and it still hasn't changed anything. I also used the main gain on the firewire card and turned it all the way up, but still no change. Does anyone have any experience using the Onyx with Logic? Could you give me some tips?

    Hey Matt,
    welcome to the forum!
    Well it seems that you've seen the question but not the answer. :o)
    Import the audio from the audio menu>import audio file, instead of the import from the file menu.
    About the Onyx, I don't have a clue.
    best regards,
    Jorge

  • Problems with audio track through US-122 in Logic Express

    Hi,
    This may be a completely stupid question, but I'm having problems with recording through my Tascam US-122 in Logic Express. I can't get anything to register on the level meter in Logic Express (neither direct input nor microphone input). However, I can get the input from the Tascam to register in the system preferences menu outside of Logic, and can get the built in mic on my IBook to register inside of logic. Does anyone have any ideas for me to try out? I've looked in the manual and I'm supposed to be getting the Logic Express training book soon, but I was hoping to record sooner than that.
    Thanks!
    Shawn J

    Sorry, ignore the above. I needed to enable record before the level would show up.

  • Timing problems with AU Ivory Piano + ESB and Logic 7.2

    I have problems with Ivory and Logic 7.2:
    The Ivory (AU version 1.50) plays well in tempo, but when I want to bounce (export track as audio file) the Ivory plays totally out of tempo.
    Even when I touch the record button on audio tracks or when I want to record my mix on 2 audiotracks, the Ivory plays out of tempo.
    Even freezing the Ivory track gives the same problem.
    Then I need to go back to my last saved version.
    The same actions with Emagic, Native Instruments and Spectrasonics AU plugins, and everything works fine.
    I throwed away already the Ivory prefs, no positive results.
    My Ivory sample files are on a separate 400 GB internal disk, and my Audio I'm recording on a external Glyph disk.
    I think I have this problem since I've upgraded from Logic 7.1.1 to 7.2 but I'm not sure. I didn't worked long with Logic 7.1.1.
    I don't work in Protools, but I use the DAE and Direct TDM (no Core Audio)
    It happens in the most simple application: no DAE or AU plug-ins, only one Ivory AU plug-in.
    This is my configuration:
    Ivory AU (Audio object-Direct TDM-Instr) output ESB 1-2 -> input ESB1 2 (Audio Object-DAE) -> Output 1-2 of my digidesign interfaces
    Ivory becomes totally unusable for me this way. Is someone having the same problems?
    Suggestions?
    Wim Claes
    Setup
    Logic 7.2
    Protools 7.1cs4
    192, 2x96i, 1x 96 interface
    G5 dual 2,7   Mac OS X (10.4.3)   4 GB RAM

    I tried already a lot of things, but it is very clear:
    1. Instantiating Ivory as AU- Ivory plays in tempo
    2. Record enable an audio track in the arrange window - Ivory plays out of tempo
    This happens with the default song of logic, no other plugins or AU-instruments are instanciated.
    I can not find a way to convert my Ivory-midi to audio without the timing problems;
    Bouncing, freezing, record to audio, export as audio file: all those things result in timing problems.
    I tried this all with emagic plugins (ES2...) and Native Instruments plugins and then I don't have the tempo problem

  • Restore Logic 7 after problems with Logic 8

    Hi Everyone
    Since i installed Logic 8 i have lost all of my own exs24 instruments. from Malmjso Acoustic Grand to my own samples instruments i created.
    I went into the Sampler Instruments folder and they have disappeared from here also.
    I tried to reinstall Malmjso Acoustic Grand from the original gig file. But after import into EXS24 on Logic 8 no matter which key i press on the piano it only ever plays the same one note.
    As Logic 7 is still installed, i opened it but the malmsjo piano is not in there either and my exs24 instruments (other than garageband) are also not there.
    As of now i DEEPLY regret installing Logic 8 over a perfect working Logic 7 as i am currently in the middle of an important project.
    The problem i have now is that even Logic 7 isnt working the way it did before i installed Logic 8. As well as problems with EXS24, alot of my songs have lost all of their settings for software instruments, they have been reset.
    My question is, : is there any way of restoring Logic 7 to its previous state and completely getting shot of Logic 8 from my computer ? At least until Logic 8 is updated.
    Thanks in Advance for all your help.
    Ram

    sweetsensi wrote:
    can anyone from Apple help me with this problem?
    This is a user-to-user forum, so you won't find direct Apple support here.
    Your mixer has a USB interface, so the first thing to do is install any software that came with your mixer (checking for updates first) and select the device in Logic Preferences -> Audio -> Core Audio -> Device
    What happens when you try that? Does Logic recognize the device?
    Is your mixer recognized in Audio/MIDI set up (in your utilities folder)?

  • Problems with Presonus Firestudio and Logic

    I am having problems with compatability with my brand new Presonus Firestudio recording interface and Logic pro 8. I am new to logic but not to home recording, and i cant understand what might be the problem. When i use the firestudio with garageband it works easily. In the garageband sound preferences there are input AND output channels that the user can define. (i.e. you can set your input channels to come from the firestudio while the output channels go to the computer speakers or headphone jacks or whatever you define it as).
    From what i have seen in logic, there is only one option for your audio settings. when in preferences and under audio, there is a "device" setting in which you can define your audio device. Wheather this is input AND output for the program, i do not know. but the problem i am experiencing is that whenever i choose the firepod as the input device, no sound from logic will play from the speakers whatsoever. My first thought was that maybe ouput was going straight to the firestudio, but after plugging headphones into it this also did not work. Has anyone had success getting their firestudio to work in logic? if so let me know what settings you had to use, and how you got to moniter your input from from the firestudio via your computer.
    p.s.
    another WIERD problem i have run into, is that if i shut off the firestudio while logic is open, alot of times it will shut down my whole computer. i have never heard of this happening. what am i doing wrong?
    thanks!

    SydSeale wrote:
    The new beta drivers are now here...
    http://www.presonus.com/forums/showthread.php?t=3957
    ah, I was hoping to find my solution here, but alas the thread is gone...
    I recently bought a Macbook running Leopard, and am having difficulties with my PreSonus Firestudio Project thru Logic and Mainstage. I can get audio input and output just fine, but there's a ton of distortion/crackle. Kickstarting the sample rate seems to clear it up for a minute or two, but then the crackle comes back. The recorded tracks sound clean if I unplug the Firestudio, so apparently it's only in the monitoring stage?
    On the PreSonus board, they're claiming it's Apple who needs to update drivers for Leopard; PreSonus says the "Firestudio Project is Leopard compatible."
    still searching for some answers...

  • Problem with a BAPI collecting dunning levels

    Hello all experts,
    I am having a problem with BAPI “DebtorCreditAccount” (called from a VB program), collecting dunning levels.
    The BAPIs is called like follows (only the essential code is shown):
    The first function (GetCustomerCurrentBalance) works fine but the second (GetCustomerHighestDunningLevel) doesn’t work.
        Public Function GetCustomerCurrentBalance(ByVal strCustomerID As String) As Decimal
            Dim objARAccount, objReturn, objActualBalance As Object
            Try
                objARAccount = Me.p_sapBapi.GetSAPObject("ARAccount", "1000", Me.ConvertCustomerID(strCustomerID))
                objARAccount.GetCurrentBalance(Return:=objReturn, ActualBalance:=objActualBalance)
                Return CType(objActualBalance.Value("TOTAL_BAL"), Decimal)
            Catch ex As Exception
                Return 0
            Finally
                objARAccount = Nothing : objReturn = Nothing : objActualBalance = Nothing
            End Try
        End Function
        Public Function GetCustomerHighestDunningLevel(ByVal strCustomerID As String) As Integer
            Dim objDebtorCreditAccount, objReturn, objHighestDunningLevelD As Object
            Dim objTEST1 As Object
            Try
                objDebtorCreditAccount = Me.p_sapBapi.GetSAPObject("DebtorCreditAccount", Me.ConvertCustomerID(strCustomerID), "0001")
                objDebtorCreditAccount.GetHighestDunningLevel(Return:=objReturn, HighestDunningLevelD:=objHighestDunningLevelD)
                Return CType(objHighestDunningLevelD.Value("DUNN_LEVEL"), Integer)
            Catch ex As Exception
                Return 0
            Finally
                objDebtorCreditAccount = Nothing : objReturn = Nothing : objHighestDunningLevelD = Nothing
            End Try
        End Function
    The error message I get is:
    Message: The runtime object of type DebtorCreditAccount with the persistent key 00000480060001 could not be created in the Business Object Repository.
    Message-Nr: 826
    Workarea: OL
    R/3 error message: Object does not exist
    Please give me some input on how to proceed!
    Best Regards,
    Niklas

    Thanks Vijaya for your fast reply. The parameters that I am giving as input are however correct.
    I have investigated the problem a bit further and tried some other calls.
    If I just chose to create an object of the type “DebtorCreditAccount” (without submitting any parameters) and then use the same method call as before (se code in topic above) I get the following error: “Mandatory parameter HIGHESTDUNNINGLEVELA missing.” This must mean that it knows that something is missing.
    objDebtorCreditAccount = Me.p_sapBapi.GetSAPObject("DebtorCreditAccount")
    objDebtorCreditAccount.GetHighestDunningLevel(Return:=objReturn, HighestDunningLevelD:=objHighestDunningLevelD) 
    If if add the mandatory parameter “HIGHESTDUNNINGLEVELA” I get the error message "The persistent key for an business object instance of type DebtorCreditAccount has not been set. Cannot invoke method GETHIGHESTDUNNINGLEVEL”. This I interpret as the object has not been right instantiated. This brings me back to square one.
    objDebtorCreditAccount = Me.p_sapBapi.GetSAPObject("DebtorCreditAccount")
    objDebtorCreditAccount.GetHighestDunningLevel(HIGHESTDUNNINGLEVELA:="0", Return:=objReturn, HighestDunningLevelD:=objHighestDunningLevelD)
    Grateful for a response!
    Regards,
    Niklas

Maybe you are looking for