swedemason

Hi David, thanks for the response. Its a new setup, migrated from a configuration ive been using for years with relatively few problems. I've been using it about 3 months. The first couple of projects i had no issues, and haven't added any plugins or utilities since. I have 6 drives connected via a usb hub, then a dongle. However, all the audio i use in the project is stored on the internal ssd. Its 1tb APFS. I have now noticed that i cannot even copy the corrupt logic project to another location. Maybe its a hardware issue. This is a work computer and its had some encryption put on it - i cant boot from an external for this reason. If this is an issue unique to this machine I'm guessing that the encryption could be the culprit. Ta S

Hi, I'm having serious issues with Logic 10.4.6 with a macbook pro 2018 10.14.6. Last week I was unable to open a logic project - logic would crash when i opened it. I was able to salvage some of it by using an autosave from a couple of days previous. I presumed it was a one off, as I've never had a situation where ive been completely unable to open a project in nearly 15 years using Logic. Unfortunately the problem has reoccured on my current project. I've completely lost two days work and cant continue using logic on this mac, because i don't trust it anymore. I put weeks of painstaking work into my audio edits and it's not worth the risk to lose one close to completion. I've tried contacting apple support and they were absolutely useless, to put it lightly. I've tried all the usual things, removing plugins etc, resetting pram, smc, safe mode and all that. Ive scoured google for similar issues not found any. I think something is getting corrupted upon saving. The first project to get corrupted was mainly midi softsynths and plugins. This recent one is all audio. I suspect this is a bug within logic as it seems to be a problem with corrupt project data. How this is happening, i have no idea. The project is saved on my internal SSD if that makes any difference. Anyone had similar problems? Is there anyone out there who can help me to decipher the crash reports?! Thanks, S

Excellent work. I dub this plug in the Dewdman. Have a drink on me. Cheers. S

It's filtering mod and pitch also, probably all my ccs.

it's filtering out my aftertouch ccs also. I can live without them but is there any way of letting them pass through?

You absolute stallion. This is it. Amazing, thankyou! Is there anyway to prevent the old note cutting off and just having the next note sustain? I quite like the sound of this behaviour but id like to have the option to switch it off if possible. Ta S

Hi Atlas. I tried your suggestion. Unfortunately i cant get it to work. I've changed cc64 to 68 in the env. I can delay the cc with the delay line. I can route it out and back in via IAC. It is the only message going through logic from the environment but the smart control still maps cc64 in controller assignments?! I change the input to IAC and nothing happens in smart controls. Ive had this problem before but i cant remember the workaround. This is the end of the line for me in the smart control route. The control mapping in logic is so unintuitive for me I havn't the patience or time to persevere with it atm. From looking at monitors in the env the delay will just delay my initial input, and if my timing is out on the input then itl just shift this timing along by whatever value i choose. This isnt going achieve what im after unfortunately, i need something more forgiving of the initial input. Looks like I'm gonna have to learn how to script! Thanks for your help. Ta S

How do lads, thanks for the suggestions and sorry for the late reply, it's been a busy week. Let me try these and get back to you. Cheers. S

Hi Atlas, thanks for the reply. Ive tried smart controls but they don't quite do i what i want. I still need the note to sustain - using smart controls hijacks the normal midi behavior of the sustain pedal. Even if routing to an IAC I can't get the note to sustain at the same time as stopping the arp. The main issue with this method though is the the timing thing. I still have to be spot on, and hit the pedal after the note on message which I find unintuitive for live input. Basically what I want to say in script form is, when i press cc64 or whatever pedal, after next note on is received (from the arp), filter all note ons until the pedal is released. Is this possible? Ta S

Hello. Happy new year folks. Can anyone on here help me with a script for my live drum roll patch please?. Unfortunately I'm code illiterate and so Im pulling my hair out trying to cut and paste a script together. Basically I want to make my sustain pedal or any momentary on off cc switch to cut off midi notes coming from an arpeggiator at the top of the midi chain - simple enough, but i want to let the next note through just after i press the sustain pedal, and for that note to be sustained. The sustain part i have managed to achieve by filtering note offs - I altered this script that was posted on here: var thru = false; function HandleMIDI(event) { if (event instanceof ControlChange && event.number==64) { if(event.value < 50) { thru = true; } else { thru = false; } } if(event instanceof NoteOn && !thru) { return; } event.send(); } My problem with this script is that i have to press the pedal just after the note on from the arp, and before the note off, for it to work correctly. This is difficult to time right if the arp is anything above 8th notes, so it's crap for the live thing I'm after. My idea was to use the 'Note triggered midi event gate' factory script to make it wait for the next note on after id pressed the pedal, and then for it to filter out any note ons until the pedal is released, but whatever im doing isnt working. Is there any way to achieve this? Thanks Swede

Hi, Atlas, thanks for the reply! Turned out to be something id messed up in the environment

Hello, im trying to record a drum part using drumkit designer and an electric drumkit. Ive noticed that the opening and closing of the Hi hat part isnt playing back correctly. Ive ruled out my sloppy playing and the drum module by using the mod wheel and keyboard to play a simple opening, closing hat part to the click. When i record the part, the hi hat opens and closes in time with the click, but when i play back the recorded part the timing is off. The midi data in the region is recorded in time in the events list, and visually i can see it is written before the note in the region, but the plugin doesn't want to react quickly enough. I have to separate the data and nudge it forward to compensate. Ive only noticed this problem in the drum designer plugin. Has anyone else noticed this or am I missing something? Ta. S

Hi, Im having a problem with controller assignments in Logic 10.2.2. I have custom controller assignments set up for a nano control 2, but when unplug my mpk25 the input defaults to 'usb midi device1' and i have to reassign all my assignments manually back to the nano control. I also have a long list of 'usb midi device 1' in the input menu. See attached. Does anyone know whats going on here? How do i remove the usb midi device 1 from the menu? Ta S

Ok great. Thanks Eric.

I have a similar problem with my korg nano control defaulting to mixer control. Before the update it appeared in control surfaces set up and could simply be deleted, and used as a normal midi controller. Since the update it only appears in control assignments, and has to be deleted everytime i start logic for it to work as i want. I was hoping the update would have logic sack off fader data and have au use midi cc, or at least offer the option. It seems to have got even more convoluted from my perspective. Any advice anybody?