nightkrawler

Anyone else might be able to weigh in on this issue? I'm 99% certain it's not a symptom of a demo plugin, because I've been able to reproduce it in a Logic session with only stock plugins. What's strange is if I render the exact same song 3 times, it may happen in 1 or 2 of the renders but not all of them and it will happen at various times for 1-2 seconds only. However on some heavier sessions it happens consistently. It seems the less CPU intensive the session is the less chance it has of dropping audio. I've attached a screenshot of a problematic render where you can see the audio dropouts towards the end of the waveform. I can upload the session, though I'm not sure it will be of much help in debugging, as this is clearly something going on with my CPU and happens in every session I try to render. I haven't changed anything on my system in the past week since this started happening, though I am using an HDD from 2011. Could it be a symptom of a failing hard drive? I'm at my wits end and would really appreciate any input. http://i.imgur.com/VWPuBJC.png

I'm using an Apogee Duet and drivers are up to date. Would the interface have anything to do with rendering drop out? Strangely this only occurs when rendering and not during playback at all. I just opened a different project and disabled every 3rd party plugin and the project rendered fine. Then i rendered it again a second time without changing anything, and the silence appeared again. I'm at my wits end on this one

I tried disabling nearly every single third-party plugin in the file and re-bouncing one by one and this still occurs. I also haven't installed any new plugins recently. This is really driving me nuts. Is there anyway I can determine which plugin might cause this or perhaps? I tried a few more sessions and it happens in those too, so I'm not sure if it's a plugin or something going on with my system now? Strangely this never happens on playback, only when rendering. The silence is always at random parts in the songs and if I render the same project twice the silence will be at different times. Any help would be greatly appreciated, I'm at my wits end on this one

I've bounced this project dozens of times without issue but since last night I keep getting random seconds of silence in the song (see waveform, this isn't intended in the song). No matter how many times I bounce, tried refreshing logic etc. The silence keeps happening in different parts of the song and there's no automation or anything that would cause this. I'm not sure how to debug this, I haven't changed drastic anything on the project in the past few days and it bounced fine earlier this week. Anyone have any ideas how to fix this? http://i.imgur.com/hBD5vuK.png Logic 10.3.1 iMac 3.5ghz i7 16gb ram

Just upgraded to Logic 10.2 and discovered this dialog. This might be one of the most annoying things Apple has added to Logic. I submitted a feedback request to Apple. Hopefully they get it sorted, seems like a bug to not have a preference to save this information.

Thanks David, I will check out the environment. It seems to be specific to this project (thankfully?) What's even more strange is it seems to break after 75 tracks. So If I delete 5 tracks (audio or midi), then I can create 5 new tracks perfectly fine, but the 6th one will be blank like above. Very bizarre, indeed!

I have been working on a session for many weeks and all of a sudden can no longer create any new audio or midi tracks. When I try to create a new track it just shows up like the attached screenshot. The audio tracks are blank as well, there isn't even a fader on them. But the current tracks work fine, and I can even open the plugins. All my other projects work fine. Has anyone seen this before? I really hope I won't lose all my work from this session Using RME FF 800, OSX 10.10.1, Logic X 10.1 software track

Hi guys, Anyone know if a way that I can get the output of a midi file after using the Transposer Midi FX on a channel? I need to be use the transposed midi in another session

you may also consider checking out a plugin like LFOTool or Kickstart which allows you a lot more control over the envelope they are very cheap plugins (<$20 each)

Wow thank you Jordi, you seem to have led me in the right direction. When I delete all the additional MIDI GM devices except the first one (set to Channel: All), I can drag and drop as many more MIDI files into the session on new tracks and they all work! However, every time I drag a new MIDi file into the session it creates a new GM MIDI device in the environment. Is this normal behavior? Is there some threshold of these devices that causes Logic to choke? Everything appears to work correctly without any of these GM devices at all and I rarely if ever use multi instrument midi tracks in my projects Regardless, deleting these appears to solve the issue for now - I will report back after doing some more testing Thank you! This has literally been bugging me for years and cost me hours of work to date

nobody has any ideas on this?

Attached is a session with the broken midi channel. I deleted all channels except the broken example one. What's also strange is after deleting every channel, creating new midi tracks now works as expected again - however if I had left them all the problem would have persisted Please let me know if I any more info is need, would really kill to find a fix for this! CORRUPT MIDI SESSION.zip

Hey guys, I'm having a very weird issue for sometime now and really hope I can find a solution or workaround. Please bare with me as it's a very strange issue and requires some explanation. In my day to day work I work a lot with sourced MIDI files. As a result, I often have to drag from the finder into my Logic session. However, after dragging a certain arbitrary amount of MIDI files into my session, the MIDI tracks just stops working properly. I create a new track, and the region will not play even though there are notes, all I see is the MIDi I/O on my Fireface light up. I can play the track via the MIDI keyboard and get sound, it's just that no regions on that track will play. I even see the meters running on that channel during playback, just no audio output comes out from these tracks. All the previously created MIDI tracks work fine, but any newly creates will not play the regions. As mentioned, this seems to happen after a "threshold" of MIDI tracks have been imported. As an example, my current session is working fine. I can create new tracks and draw new midi regions, as many as I want, all works well. However, if I drag just ONE more region in it from the Finder - the MIDI will break and any tracks I create after that will not playback the MIDI regions. I've tried opening the session in LX, same issue. Tried another computer, same issue. Anyone have any ideas on this?? I can upload a Logic session with the "corrupt" MIDI track later tonight if it helps.

Is Spire really on point with Sylenth sound-wise? Haven't tried it yet.

Dislcaimer: I fully support 64-bit and think it was a bold but wise decision for Apple to move Logic to 64-bit only. However I also sympathize with users of Sylenth1, which is a staple for most dance music producers and as developer has more or less fallen off the face of the earth, there is likely no chance it will ever be upgraded to 64-bit. As such, here are 3 ways you can use Sylenth1 with LPX: 1. Use Native Instruments' Maschine to host the VST version of Sylenth, then jBridgeM for 32-bit support (tested, works like a charm) 2. Vienna Ensemble Pro (have not tested, but told it works) 3. Run LP9 alongside LX and print audio Hope this helps somebody 8)