Heavy Logic X bug

Did anyone notice that when you add an audio file to a track and use the undo function after, Logic starts reloading ALL instruments including samples, this can be quite annoying when you work with big orchestral templates.

Then... as I said.. Im not able to recreate that issue here.. and nor have any of my clients reported such an issue to me
The only time I have seen such behavior and the only way i can recreate what you are apparently describing... is when either the Audio driver or Core Audio itself has to restart. (Say the driver crashes or the sample rates change. for example) for some reason... and then samples etc.... will reload.
Do the logs show anything interesting when this happens?
Applications/Utilities/Console and then look for Logic Pro X logs....

Similar Messages

Logic old bug in MIDI import

I've had this weird issue regarding importing midi files for a very long time.
I reported the bug to the Logic Pro Feedback several times but nothing is changed.
If I import this MIDI file in Logic http://dl.dropbox.com/u/2723724/test.mid
the first time only half of the instruments are recognized. The second time (without closing Logic) everything is fine.
So, to be sure, I always have to import the same file two times.
This is the first import
And this is the second one
of the same midi files.
(If you want to try please use my test file because this happens only with some specific commercial MIDI files, not all)
I can't believe after the release of Logic 9.1.7 the bug is still there... it seems that nobody at Apple is reading the feedback.

Samoreen wrote:
Sometimes, when I use the Synchronize Folder command or when I click on the Import... button, the Import dialog doesn't show up (sometimes meaning here "very often"). Obviously, the dialog has been loaded because at this time, LR is in a modal state (you can't use any user interface element - you just get a beep when clicking anywhere in the main window). The dialog is here but it is not visible.
Actually, it can happen that when the Import dialog is in this hidden state, trying to close Lightroom causes a message box to appear : "Do you want to close the Import dialog and quit?" (or something like that). Well, I don't want to close it, I want to see it !

Logic 8 Bug

This is a minor issue I encountered but hope the the Apple Logic Techs fix it quick. When I have a High sample rate set for my song like 96K and When I go into my browser to search for Kicks or snares to drag into Ultrabeat, When I play the Kick or other sound from my browser they play at High Pitch instead of the Real way its supposed to sound. When I drag that High Pitch Kick from the browser to the ultrabeat sampler, From the Sampler they play the right way but from the browser they play at high pitch. I guess because those samples are at 44.1K and In Logic my song is at 96K but I'm sure that bug could be fixed. Because the whole point of hearing it from the browser is to see if thats the sound that you want to drag in to ultrabeat. Thanks and Let us know when its fixed.

i'm having the same problem with logic 8 and my motu 828.
when i play something thru input 3 (mono recording), it also plays thru input 2.
very strange.
i've tested the interface with Live and other apps without a problem.
it's definately a bug and i hope apple fixes it right away.

Logic 8 Bugs/Crashing when importing audio

Hi,
Been running Logic 8 for a few months - some good things but lots of niggly bugs which we're trying to iron out.
We're getting a problem with Logic crashing everytime we import an audio file - however when Logic reloads the file is in the project and plays fine. Anyone come across something similar?
Also, for some reason audio files are playing randomly in a Logic sequence - for example the backing vocals will play at the start of the track even though they are not placed anywhere near there.
Hoping someone can help, we've installed the latest updates and everything - currently running a HD 192 TDM system on 10.4.11.
Thanks
Jack

I have had similar bugs like this even on 7. I think it might be a DAE/Logic issue that has been carried into the next generation. Just the wrong playback of an audio file in respect of the arrangement placement is new. I am having it too when i am in cycle mode. Only randomly though.

Has anyone come up with new workarounds for Logic routing bugs?

There have been many threads regarding what seem to be a set of similar bugs. These inlude an audio intrument not sounding after a while, or a channel of automation not being read; and the problem is easily fixed by closing and re-opening the song. That would be a fine workaround except that some songs take a long time to load. I used to have these problems occasionally, but recently they have become so common as to be almost constant. That's bad news, but it also is potentially good news since it means that something in my system has an influence on these bugs. I haven't found a thread in which anyone isolated a factor that helps or hurts, but it's hard to imagine all the keywords for this set of problems, so maybe I missed an idea.
Also a new similar bug has started appearing in my system. When I add a bus send, once in a while either some or all audio channels will go silent, even though the graphic indicators indicate that they should be heard. The silent channels might or might not include the one with the new bus send. Remove the bus send and the sound comes back.
It seems as though changes in routing have binding problems.
Thanks for any ideas!

Absolutely no ideas on workarounds. I have the exact same issues.
Most of the time restarting the computer and session will cure them, but there have been projects where no matter what I do, the faders will not follow the automation data and EXS24 instruments cut out at the same exact time in the arrangement. This occurs even with as few as 6 EXS24 instruments open when on some projects I have up to about 85 open and 30 streaming at the same before I get a CoreAudio error.
Terrible...terrible.
Any word on whether or not 7.2 addresses this issues?

Interesting Logic iTunes bug?

Hello all,
I have been trying to overcome this interesting problem the last few days. I have a great mix I've been working on for some time now, and when I bounce the file, everything seems to go fine. When I play the file in Finder, it sounds great, just how it should. As soon as I click and drag that file into iTunes, about a minute and half into the tune, it starts to sound... shaky. That's the only word I can use to describe it. Its not exactly "phasey" but its a mid point between choppy and phasey. Anyone else have this problem? This is brand new for me, and perhaps its an iTunes bug?
Thanks,
Brian Armstrong

Hi Brian,
I'm still on Panther, but never had that problem or knew about it.
If I get some information on it, I posted to you.
Cheers,
Jorge

Making Folder within Logic Express - bug?

When I select tracks in the arrange window and select the Pack Folder command, the tracks are moved into a folder but the original tracks remain in the arrange window.
The tracks are EMPTY, but they are still labeled. It is easy to delete the tracks, but I was wondering if this is a known bug with the Pack Folder command or if this is an issue with my app only.
Thanks
Quadzilla Mac OS X (10.4.3)
Quadzilla Mac OS X (10.4.3)

It's the same for me. Also, when I create a second folder and try to name that one, the first folder also changes its name to the same as the second... anyone?
Mac mini Mac OS X (10.4.3) LE 7

Logic Releases Bug-Fix and Enhancement List for 7.2 & 7.2.1

...I found this announcement on a post from nearly 1 month ago on www.logicprohelp.com...
"Yesterday, Apple released two new articles listing in detail the enhancements that found their way in Logic 7.2 and Logic 7.2.1"
Logic Pro/Express 7.2.1 Enhancements
=AND=
Logic Pro/Express 7.2.1 Enhancements

Woah.
Those are fixes? And there's still problems left? woah.
Like swiss cheese, this program is.
X
but I love it anyway.

If I download iTunes 8 will it jack up Logic w/ bugs?

just wanna see wutsup before i download iTunes 8. I dont wanna download/upgrade and then have Logic all buggy. Lemme know!
using Logic 8, on Tiger
Message was edited by: TEFnick

I've got iTunes 8 and Logic Pro on a couple of machines and I've not noticed any problems.
Are you being sarcastic ? Or is there an issue I'm unaware of ?
Thanks
James

Increase processor priority for Logic 8

I saw an interesting thread on the Final Cut Pro forum - where the users were concerned that rendering did not fully use all of their cores.
This might be of use to heavy Logic users?
http://discussions.apple.com/thread.jspa?threadID=819587&tstart=0
Is your Processor Performance set to "Highest" in your Energy Saver preferences?
To increase the priority of a process in Mac OS X, open the Activity Monitor in the /Applications/Utilities/ folder and get the process's pid. From here, open the Terminal, which is also in the Utilities folder, and enter the following:
sudo renice -20 pid
where pid is the number you found earlier. Press Enter and type in your password; nothing will appear in the window while it is being typed. The process in question will now run as fast as the computer can make it go. The effect of this command ends when the program quits.
-20 refers to the "nice" level of the process. UNIX operating systems have what is called a scheduler, a part of the kernel that decides when tasks run and for how long before CPU time is allocated to another task.
Processes with higher "nice" levels are nicer -- meaning that they get a smaller share of the processor time. Processes with a lower nice value are less "nice". Nice values range from -20 to +19. Basically, it's a hint to the kernel's scheduler that schedules processes to run about how aggressive it should allow a process be in using up processor time. It's conceptually distinct from the concept of "priority" which enters into the process scheduling a little differently.
You can do this automatically by opening the Script Editor in the /Applications/AppleScript/ folder and pasting in the following:
tell application "Final Cut Pro"
run
end tell
set the_lines to paragraphs of (do shell script "ps -U $USER")
set the_app to "Final Cut Pro"
set the_line to ""
repeat with this_line in the_lines
if this_line contains the_app then
set the_line to this_line
end if
end repeat
if the_line is "" then return
set the_pid to word 1 of the_line
do shell script "renice -20 " & the_pid password "yourpass" with administrator privileges
Provide your administrator password in the last line, and save the script as an application in a location easy to access. Open it whenever you want to open Final Cut Pro. More information about the command, including the purpose of the -20, is available in this article.
http://developer.apple.com/documentation/Darwin/Reference/ManPages/man8/renice.8 .html

Here is an application which allows just that:
NICER
http://www.versiontracker.com/dyn/moreinfo/macosx/9473
Nicer 2.1b ©2001 Ryan Stevens
This is a beta (preview) release. Use at your own risk. If you have comments, questions or feature requests drop me a line (see the Contact section).
Know bugs:
1) Application names get clipped at 16 characters. Until I figure out a sensible way to get the full names (without mass amounts of guesswork/workaround code) this will have to do, sorry! If you have a fix you'll let me know, right!?
2) Choosing "Quit [appName]" from the context menu doesn't let you save changes (if any) in the quitting app. (This may change in next release)
3) Choosing "Kill [appName]" or "Quit [appName]" from the context menu doesn't show an alert with the option to cancel. Select one and the app will quit -- unless the process doesn't belong to you, in which case you will have a chance to cancel.
4) Although not exactly a bug, Nicer doesn't gather much meaningful info on the process. I like the simple look so if/when we gather more info it may get put into an Inspector window.
5) [insert quirk/bug/missing feature here.]
Installation:
Drag n Drop install/uninstall. I recommend putting Nicer in /Applications/Utilities/ but it's really up to you.
License:
Nicer is freeware. Bam! Simple as that.

Logic pro x mixer window freezes main out VU with dual monitors

In a dual display configuration, with the mixer window in the left monitor and arrange window in the right monitor, the VU meter on the last channel strip to the far right of the mixer window(which is usually the main output) freezes and does not update. This seems to be a Logic X bug, since it does not occour in Logic 9 or any other DAW with the same configuration.
Can anyone confirm this or have a suggestion for a solution?
Thanks in advance

They have had four years to change this, and actually people were asking for it before that. If anyone knows a way, let us know, but I doubt it. Both Logic and Cubase are the only two DAWS that don't allow this....all the majors do....Pro Tools, DP, Studio One, etc. Cubase users have been asking for it forever as well.
I would have upgraded immediately if they had added this, they haven't, and I'm moving over to PT11.
TH

Will logical standby database be replaced by physical standby database?

Will logical standby database be deprecated or replaced by physical standby database because of Real Time Query?
As far as I know, because of the emergence of Real Time Query, physiacl standby database is easier to work than logical standby database. There are so many restrictions on using logical standby database.
Will logical standby database be deprecated in the future?
Message was edited by:
frank.qian

Good question - you are right that with the advent of Real Time Query, physical standby databases can provide the 'reporting database' functionality that you used to have to use a logical standby database for.
But remember that logical standby databases allow additional schema objects, like materialized views and indexes, that you can't have with a physical standby (for the reasons Hans mentions). For example, you could have a index-light primary database for OLTP style workload, and an index-heavy logical standby, with MVs and dimensions for reporting, DW, etc.
For this reason I don't expect logical standby will become deprecated.

Tempo List Reduced Functionality\Bug

Just a quick warning about L9's tempo list. It no longer supports a start bar number other than 1. So if you're transferring L8 synced to picture projects with starts defined with a bar number other than 1 it'll be knocked out of sync. This is either a bug or a horrible ball-drop for those of us using L9 to compose to picture.

It's an Intel/Logic Pro bug... unfortunately very repeatable.
If you click on the smpte position time within the Tempo List Editor, the value will go to 00:00:00:00.00
The only way to set a smpte offset or start time is to use the Synchronize window, It makes using multiple tempos & tempo curves to hit cue points virtually impossible. You used to be able to change the smpte time and the tempo prior to it would adjust accordingly, very frustrating when I know it's not broken if I use my old PPC G4. It's an Intel only bug.
Keith Moore

Logical shift negative numbers

So, I think i have found a bug in Labview. I am using Labview 8.5
I have a very very simple Vi Where i want to Right shift a negative number. For example:
-16 >> 2 = -4
What i get is 16380. If I mismatch the data types. Meaning I right shift from a 16 integar and place the result into a 8 bit integar I get -4.
It would appear that the function is padding with leading zeros and not ones when handling negative numbers.
Is this an issue that has been fixed already? Or am i using the function incorrectly?
Attachments:
Logical Shift bug.vi ‏7 KB

Gruntboy,
   What I think you're looking for is an arithmetic shift function, while the function in Labview is a logical shift. The difference is in the leading bit of the result when they shift a number to the right. A logical shift right pads the numbers with '0's and an arithmetic shift right pads the numbers with their copies of their most significant bit. This is very important when dealing with signed numbers, because the most significant bit (in standard two's complement notation) denotes whether or not a number is negative.
   The number four (4) represented in six bits would be: 000100, and in two's complement negative four (-4) would be 111100.
A logical shift right, which pads the numbers with a '0' on the left would be:
000100 --> 000010 (4 --> 2)
111100 --> 011110 (-4 --> 30)
An arithmetic shift right, which pads the numbers with whatever their most significant bit is would be:
000100 --> 000010 (4 --> 2)
111100 --> 111110 (-4 --> -2)
I don't see an arithmetic shift function in Labview, but you could build one by converting the number to an array of booleans and shifting to your heart's content.
When operating on signed numbers Arithmetic shift operations tend to be more useful, but I'm sure there would be quite a bit of confusion if the unsigned number 60 ("111110") gets right shifted and becomes 127! ("111111").
Finally, there is "one" (heh I'm so punny) special case for arithmetic shifting. Consider how right shifting (logical and arithmetic) 8 results in 4, then 2, then 1, then 0. What about arithmetic right shifting of -8? The results would be -4, then -2, then -1...... then -1, then -1, then -1, etc.
Worthwhile resources:
Two's compliment notation for negative binary numbers: http://en.wikipedia.org/wiki/Two's_complement
Logical shift explanation (w/ pictures!): http://en.wikipedia.org/wiki/Logical_shift
Arithmetic shift explanation (w/ pictures!): http://en.wikipedia.org/wiki/Arithmetic_shift
I hope this helps!
Hugs,
memoryleak
P.S. I noticed that you mentioned you were modeling number operations of an ASIC. This book (ISBN: 978-0534378042) was used in the Intro to Digital Logic class I took way too long ago, and I remember it hitting very hard on binary, signs and bit operations. Looks like a used copy can be had on Amazon for less than $40
Message Edited by memoryleak on 10-09-2009 11:00 AM

L9 - all tracks seem to "software monitor" when set to record! BUG?!

Hi Guys,
Not sure if this is another Logic 9 bug or if I am just going crazy!
Often when recording tracking parts, I need to record three or four tracks at the same time. For example, today I was recording vocals, keyboard and bass.
I always monitor the vocals through Logic, so the singer has some reverb in real time. However, for zero latency monitoring on piano and bass, I would usually just monitor them straight through the mixer and not through Logic.
To achieve this in Logic 8, I would press the "software monitoring" button (the green one beside the transport window). I'd also press the orange "Low latency mode" button to make sure the tracks that were software monitored would not have any latency.
Then I would select record for all tracks I was recording, and I would press the "i" button (orange button for input monitoring) for the tracks that I actually wanted to software monitor. Tracks with "i" pressed (usually just vocals) would monitor through Logic with effects, the rest would just be monitored through the mixer.
In Logic 9, this isn't working! Even if I only press the "i" button on one track, ALL of the tracks are coming through Logic. It seems to be applying software monitoring to ANY TRACK THAT IS IN RECORD MODE, even if the input button isn't pressed for that track!
So I either have to have ALL record-enabled tracks software monitored (which induces a little bit of latency for the keys and bass) or NONE (and leave the vocalist without any real-time effects in the mix while he sings).
Am I missing something here? Is there a new setting somewhere that automatically sets all record-enabled tracks to software monitor mode when the software monitoring button is pressed in the transport bar?
OR... is this a new bug?! It's a big one if it is!
I'd love to hear what other people think... or if anyone has a suggestion that might help with this? I might just be missing something obvious here, but I don't think so...
Thanks heaps guys!
Mike

yeloop wrote:
Hi Guys,
Not sure if this is another Logic 9 bug or if I am just going crazy!
Often when recording tracking parts, I need to record three or four tracks at the same time. For example, today I was recording vocals, keyboard and bass.
I always monitor the vocals through Logic, so the singer has some reverb in real time. However, for zero latency monitoring on piano and bass, I would usually just monitor them straight through the mixer and not through Logic.
To achieve this in Logic 8, I would press the "software monitoring" button (the green one beside the transport window). I'd also press the orange "Low latency mode" button to make sure the tracks that were software monitored would not have any latency.
That's not what Low Latency Mode does, it only bypasses high latency inducing plugins, there's a threshold setting in Logic. But that's not the problem...
Then I would select record for all tracks I was recording, and I would press the "i" button (orange button for input monitoring) for the tracks that I actually wanted to software monitor. Tracks with "i" pressed (usually just vocals) would monitor through Logic with effects, the rest would just be monitored through the mixer.
That's not how it works here (on version 8.02)
With software monitoring enabled any track in record mode is passed through Logic's audio engine. Input monitoring only works when a track is -not- record enabled. At least that's how it's working with my RME hardware.
Perhaps you're thinking of "Auto Input Monitoring", try adding that button to the transport bar and see if that's working the way you expect. Any tracks set to input monitoring and record will pass their signal thru Logic, tracks set to record only, will not. The sequencer has to be running so the vocalist wouldn't hear reverb until you actually start recording.
pancenter-

Heavy Logic X bug

Similar Messages

Maybe you are looking for