Jump to content

oortone

Member
  • Posts

    155
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

oortone's Achievements

  1. Thanks, will try that next time. Or maybe I am at the maximum version for High Sierra? 10.4.6 I think it was, not in the studio right now.
  2. Old topic, maybe once true but not anymore. In my case (High Sierra which is maximum system of this particular Mac) clicking Upate in App Store asks if I want to download an older version, click OK, App Store asks if I want to download an older version, click OK, App Store asks if I want to download an older version ... endless loop. Only thing that works is to click Cancel.
  3. I had a huge mess with files and filenames because I was sloppy but after reverting to original version and being more thorough it wasn't so hard to convert. Made sure i had the original 48k files and newly converted (with good converter) 44->48k files at hand in a separate folder. Opened original 44k project. Marked all files in media tab. Chose Convert/Copy files and set to 48k. Made sure I put the converted versions of audio in a separate folder. Saved and closed project. Removed ALL soundfiles associated with this project. Even the newly created. Reopened project and manually located each file from paragraph 1 above. Resaved under new name. Done 🙂
  4. For stupid reasons I have an old project with files originally at both 48k and 44k. Project was 44k but since most files are really 48k (those where once converted by Logic automatically to 44k) I tried changing the project sampling rate to 48 and thought I could re-reference files afterwards [*], when Logic had converted all to 48k. But that didn't happen, everything still at 44k alltough playback is at 48k. [*] There are some tricks for that.
  5. I work with hardware but I still want to automate things in plugins from time to time. Having that checkbox active all the time is very risky in some situations. A visual feedback of the state would harm no one.
  6. As far as I know this (see image) is not shown anywhere other than in preferences. There are shortcuts to alter them but you have to remember the states yourself.
  7. Yes, that's how I work also although it's bit bigger risk to make mistakes and also, Logic does not have any visual feedback telling you the automation states for the various categories, unless you open up the settings-menu which is quite unpractical. Thanks anyway, now I can stop looking.
  8. In ProTools you can select which parameters to automate. The others will be unaffected/unavailable. In Logic all plugin parameters are on for automation as default, if write automation for plugin is enabled. Is there some way to protect parameters from unintentional changes, say when using latch?
  9. Interesting discovery. It seems like my Frontier Tranzport (a very old DAW-controller) is partly the "offending" device messing things up. After doing some assignments in Logic with a Faderfox EC4 having only this one hooked up (in the living room) I then connected my computer to "all" my gear in studio and in that case Tranzport stole the port from EC4 so all EC4 assignments were changed to Tranzport. However, trashing the .cs and disconnecting Tranzport I got everything working with the other midi gear without issuses. Then finally connecting Tranzport the EC4 port was not stolen! Maybe always a good idea to try to wait to connect some oler devices until everything else works?
  10. Yeah, maybe I should look up Keyboard Maestro. But which part can you automate? Maybe Automator (Apple Script or whatever its called nowdays) also can do this? Scripting is powerful but a pain to set up. I tend to avoid it as long as possible... ;-/
  11. Yes, I have a lot of copies of .cs but that does not help if I switch midi interface for controllers that use oldschool midi (instead of USB). Since I have a laptop that tend to happen a lot...
  12. Ran into this again because I made som rearrengements in my setup. It's extremely frustrating, had to change something like 80 assignments manually. I don't get why there's no solution. I discovered that with controllers available via Setup the port can be changed globally in the Setup menu and it's reflected in the Controller Assignments window. So if I could add my own things manually via Setup this could be solved, but seems like I can't do that. Or is that possible?
  13. I have failed to find a way to change this setting for all assignments, I have to go into EVERY single one to make the change if I've failed to save the original .cs file... 😬 Kind of nostalgic feeling to go into Library>Preferences and replace a raw settings file to get things to work again...😄 Feels like twenty years ago.
  14. I don't get this. Just a about a month ago I corrected the midi port for all my controller assignments. For some unknown reason it had changed to the wrong port for EVERY assignment. Changed it back and saved the .cs file. Been away from the project using the controller a while and now when I start working with it the port is changed again. It changed to a port for a piece of equipment I haven't even used for a very long time. It's in storage so the computer has not seen it for months. Luckily I had the old .cs file but it's very annoying. Why does it change? I haven't even touched controller assignments since the last time but it changed anyway.
  15. Not shure what you mean. The question is about relative mode. I'm trying to find something similar to trim mode and preview in ProTools, especially in conjunction with a control surface and multiple channels in one go. I'll probably get back to this question by recording a video or something, I guess it's a bit hard to explain what I mean. But it's a perfectly normal and common workflow that seems overly complicated in Logic.
×
×
  • Create New...