toonscribe

Hi again, Des99. In researching to answer all your questions, I discovered that all my other SoundToys plugs (which were working fine) were v5. Microshift was v4. So, I paid to upgrade Microshift to V5 -- and that SEEMS to have solved my problem -- i.e. I was able to install and open it without the CantTutThis error. (I also upgraded to the most recent iLok License Manager, per your suggestion.) Thank you, again SO MUCH, for your time and expertise and steering me in the right direction simply by virtue of your questions -- and your offer to provide additional help. I *REALLY* appreciate it!

Hi Des99. THANK YOU, so much for your response!! I won't be able to access my studio computer to respond definitively to all your question for 24-48 hours. I do have other SoundToys plugs and I _think_ they were working okay. I will report back the answers to your questions as soon as I can -- and in the meantime, thank you again for you interest and help!!

I've been having the frustrating CantTutThis problem and I'm pretty sure in my case it's solely related to SoundToys Microshift. 1) I rarely use Microshift and it only happens in the project that includes it. 2) When I tried reinstalling Microshift, Logic couldn't validate it (in a new empty project). 3) When I had Plugin Manager rescan Microshift -- it crashed Logic at the end of the rescan process. (Repeateable.) 4) There have been many other entries on the internet signaling out SoundToys as their culprit for this problem. So, is there something I'm not understanding that still suggests this is a random problem which could be attributable to any plugin? I've written SoundToys support and not received a response in a couple of weeks. (Very disappointing -- and turns me off to SoundToys.) Anything else I can try other than just remove and avoid Microshift (and SoundToys in general)? (Or reinstalling all my plugins which would be a nightmare.) (I'm tempted to try to downgrade iLok Manager which I think I recently upgraded -- but god knows what chaos that would wreak on my many other iLok plugins!) Any advice or insight would be appreciated and thanks in advance! (Still on Logic 10.4.7 and Mojave 10.14.6).

Facej: Great and simple solution. I'd used the rename so regularly -- I never noticed the various drop-down menus for the options. There it was, right there. Worked perfectly. Many thanks!

I thought about that, but the challenge is that the filenames currently have no extension name to replace. I'm trying to ADD an extension where one does not exist. I might be missing the obvious but I don't see how this solution would work to accomplish that for a batch. (But thanks anyway!)

Thank you guys -- will f/u when I get back to my studio. I appreciate your help.

This is not a Logic question per se, so my apologies if not appropriate for this forum. Can anyone tell me a way to batch add a file extension to group of files at once in MacOs 10.14.5? I tried searching the web and the suggestions I found didn't seem to work. Thanks in advance for any help.

You...know...I THOUGHT I had remembered some setting for this -- but couldn't find it. Thanks for reminding me! Yup -- now working fine. Sorry for false alarm and thanks again!

I recently upgraded to 10.4.6 - Mojave 10.14.5. Is it just me, or has anyone experienced that Logic no longer automatically starts playback at the beginning of a marquis tool selection in a region? (It used to be that if you just highlighted a section with the marquis tool -- and hit play -- playback would only include that portion of the song which was highlighted. And, in fact, that is the expected behavior described in the manual.) Thanks!

That seems like a great solution for software synths -- thanks! But I like to run an occasional 32bit EFFECTS plugin and I'm not sure this would work for that or not? But I don't need to try it because I'm still using 32 Lives which has been continually updated and still works great! The guys at SoundRadix have been FANTASTICLY responsive about keeping my stuff working. I mainly use it for Abbey Road RS124 -- which to my knowledge has never been updated and re-released by anyone in 64 bit. 32 Lives/Sound Radix to the rescue!

In case anyone's interested -- I have finally troubleshooted my CoreAudio crash in this project to an instance of Sampletank. (Grrr.) I am in touch w/IK Multimedia support trying to get to the bottom of it. They have yet to be very helpful -- but I'm still working with them. But I must say I've had assorted other issues and anomalies since updating to Sierra and Logic 10.3.1 I've been having to spend too much time troubleshooting.

I used this Change-Gain (in Audio File Editor) function regularly -- without a problem -- in Logic 10.2.4/Yosemite and many versions prior. But since upgrading to Sierra and Logic 10.3.1 -- every time I try it, it fails to function and Logic freezes. (It doesn't crash per se -- but clicking of any kind only causes a bright flash on my screen and all options are grayed out. So I have no choice but to Force Quit. I reported this to Apple as a bug -- but I'm wondering if anyone else here is experiencing it? (Or should I start a new topic to pose this question?)

Yeah, I think I've eliminated Kontakt as a possible culprit. (But thanks anyway to Triplets for the suggestion. BTW, I didn't have Kontakt Memory Server enabled -- since I have 32gigs of ram.) The truly torturous aspect of my situation is that for each plugin or track I try to eliminate -- I have to play through 3/4 of the song -- in REAL TIME -- to see if it's had any impact. Just shoot me. I sent a bug report to Apple but doubt it'll be something they will find -- unless they're getting a lot of similar complaints. BTW, Realtwang, are you really still on Logic 10.2.4 as your sig says? Also I notice you use a MOTU interface. Wondering if maybe our problem is related to compatibility issues with the MOTU driver and Logic 10.3.1 and or Sierra 10.12.3. Anyone else out there using an MOTU interface having any issues on Sierra 10.12.3 Can anyone tell me if it's possible to use Time Machine to downgrade only the OPERATING SYSTEM back to 12.10.2 without reversing anything else? Thanks in advance for any further help/ideas/suggestions.

Triplets -- thanks for the response. I have no idea what Memory Manager is -- or even if it's a Kontakt function, Logic function or OSX function -- I'll try googling it. Are you suggesting I should be using it or that using it might be the source of my problem? I'm thinking tomorrow when I go back to my studio, I'll try removing Kontakt from the project and see what happens. The reason I don't think it's a plugin per se -- is the fact that it always happens at the exact same point in the song. That suggests to me that there is something bad imbedded in my project at that point in my timeline -- somewhere "under the hood" -- in an area I cannot see or access it. But...who knows. That's why I'm asking. I can't imagine what it would be that would screw up Core Audio "permanently" (until I either disable-re-enable it or close the project and re-open it.). Thanks again.

I very recently upgraded from Yosemite to Sierra and Logic 10.2.4 to 10.3.1 I'm working on a song that I started in Logic 10.2.1 (I think) -- and now -- always at the same point about 3/4 of the way though the song -- the audio makes a loud pop and then goes silent. On my interface (MOTU 828mk2) -- the meters are suddenly locked about 3/4 of the way up, but no sound is audible and nothing shows in Logic's Stereo Output meters. The only way to free up the audio in my interface -- and restore sound -- is to disable core audio and then re-enable it -- which makes a quick crackling noise -- then everything is normal. Then -- if I start the song fairly close to the problem spot -- it plays through okay without a problem! But if I play the song from the beginning -- I always get this same crash when it hits the exact same spot about 3/4 of the way through the song. FWIW, I also recently upgraded to Kontakt 5.6.6 and am using it in this project. Also using MANY 3rd party plug-ins. Here are the things I've tried: 1) Opened a new Logic song and imported everything in. 2) Checked my automation editing windows for each track looking for anything unusual at the problem spot. 3) Looked at all my tracks -- again looking for anything unusual or suspicious at the problem spot. 4) Reinstalled the most current driver for my interface -- although I really think the problem is in Logic because it always happens at the same spot -- and when I re-enable core audio (or simply close the Logic project and open a new one) the interface functions as expected. As you might imagine, this is pretty maddening. Wondering if anyone else has experienced anything similar -- and particularly wondering if anyone has some clue as to what might be causing this and/or troubleshooting suggestions. THANKS IN ADVANCE!