Jump to content

Phazma

Member
  • Posts

    66
  • Joined

  • Last visited

Phazma's Achievements

Newbie

Newbie (1/14)

  • Week One Done
  • One Month Later Rare
  • One Year In Rare

Recent Badges

0

Reputation

  1. In fact, the inconsistency seems to be the problem. I use IOS for years and have no issue with doubleclicking the home button and swiping the screen. I use macOS since like 1 year and I also didn't really mind this until I got a few apps like Reaper or FL Studio that just close when pressing X and came to miss that in Logic. Not missing it in the other apple programs though, perhaps because they don't bring up a saving-dialog so it's very quick to press x and in the dock right-click-quit the app immediately afterwards. And when it come to Logic that dialog has some kind of "final" vibe to it so I often forget to right-click-quit it via the dock, which becomes annoying. However, as mentioned, probably it would be even more annoying having to restart Logic for each project I am opening.
  2. Well didn't think about this but makes sense. As it always scans the plugins on launch amog other stuff it actually saves a lot of time not having to reopen for each project while closing takes just 2 clicks more. Thanks for the info.
  3. Hmm actually yeah, also Safari for example behaves like this (just that it is annoying me less so I didn't pay attention). Don't get it why apple does it like that but probably they have some reasons.. I personally prefer apps that quit when you close them (specially if you have a warning dialog like in Logic, so you don't even risk accidentally quitting it).
  4. Just a small but somehow annoying issue. When I close all open projects/windows I would expect the application to quit, yet the app remains in the dock with the little dot underneath. Is there a way to have Logic quit for good with one click or do I always have to close the project and then go to the dock and also quit the application in order to not have unnecessary processes running while doing other things?
  5. For sure in someway it is possible as this plugin allows the creation of panels to control hardware synths and I am actually using it with a panel created by a user. However all those customisations require apart from deeper understanding of midi/sysex etc also a bit of scripting (in LUA language) which I am not able to do (and have not masses of time to dedicate understanding all of this just to modify some names).
  6. Hello, just wondering, is it possible to rename automation parameters? There are some plugins like the one in the picture where the creators have not given names to the controls and it is always a guesswork to find the right parameter to automate. Would be nice if I was able to test through those and give meaningful names and save them for the future (even just within a template).
  7. Yeah actually true. I am running a 2015 MBP (4-core i7 2.2ghz with 16gb ram) which by far isn’t the strongest Mac on the market and right now I am working on an (I admit unnecessarily) huge project, counting 160 channels with like a third of them being cpu-hungry plugins like Serum or EWQL libraries and countless fx on the mixer channels and with every plugin I keep adding I am surprised how my computer keeps handling it smoothly. But maybe it is only me not taking this for granted as I come from 32bit Fl Studio which already gave up at projects of 1/4 this size.
  8. Hmm wonder if they will include it in a reliably working manner some day in future when it won't be complicated to implement and keep up to date.. but I guess we can keep waiting if only a handful of people are interested in it.
  9. Really? Weird that they exclude features and downgrade on some things.. maybe in order to force people to buy new and stronger Macs instead of recycling old computers
  10. I see.. well I don't use VEP (yet) and as my computer can mostly handle what I am doing I think I won't mess around with this and risk introducing problems just to solve other problems that I don't even have. I thought if it just worked to plug another computer via ethernet as "spec-expander" (e.g. have more cores at disposition or if ever cpu or ram were fully used it started using the resources of the other computer) it would have been awesome, but seems like technology isn't yet advanced enough to make this possible. Would be great if Apple introduced this in some future macOS and upgraded Logic to support a multi-computer setup and split workloads while keeping all user interaction on one main computer.
  11. Oh ok I understand. So basically the only case it would work is for using few selected plugins (like VEP) which allow MIDI input from another computer. So it would be the same like using a Hardware Synth via MIDI with the difference being that the MIDI is not transferred via MIDI cable to a synth but via ethernet to the plugin on the other computer?
  12. Hello, I just got my Macbook Pro and have my Mac Mini laying around in the studio. I am wondering if there is a possibility to connect the Mac Mini to the MBP so that when both computers are switched on Logic on my MBP in addition to using it's own processor/cores uses those of the other computer? I have not found any sources on the internet stating explicitly that it is possible so I guess not but I figured I will ask here (where people are Logic/Mac experts) too in order to have a definitive "yes if" or "no chance".
  13. There are 3 main reasons for me: 1) working at the maximum resolution of Logic's faders without having to load a gain plugin each time to attenuate the audio in order to have enough headroom. 2) having the same loudness when listening to a mastered track, arranging my own track or mixing my track. 3) As I want to calibrate my monitoring to K-20 where -20dBFS equals 70-85 dBSPL (depending on your room, your preference and so on) I want to make sure that when working with sounds around -20dBFS no other sounds are triggered at 0dBFS, resulting in an unexpected blast of 90-105 dBSPL.
  14. So I opened Logic today to try lowering the output via master fader / dim and while it works as expected, it actually doesn't satisfy me. As I mix to match a mastered track the mixer channels all go into the red and while I know that Logic's audio engine allows this without clipping it annoys me a lot. Also I understood that VCA faders work pre-fader but post-insertplugins and the various metering plugins on the master all show me the hot signal instead of the dimmed. I tried to think of a solution and while always putting a gain-plugin at -20dB on each channel's first slot would seem obvious, it doesn't satisfy me either because I don't want to bother always loading one, hoping to not forget it or switch an instance off by accident and so on. Also I know I could save a default patch with it pre-loaded but it wouldn't load the default patch when dragging a sample from the finder into Logic. A much more satisfying solution without extra plugin would be a VCA fader that controls and attenuates all channels by -20dB. I know I could save a template with such a fader already loaded but also in this case I always have to assign all tracks to VCA1 manually, which I don't like for the same reasons as mentioned before. So my question is, is there any way in which I can trim all audio going through Logic automatically by 20dB in some "hardwired" way, maybe inside a template? Like so that I can load a mastered track into Logic and when playing it back, without any further adjustments (fader at the 0 position), its mixer channel peaks at -20dBFS?
×
×
  • Create New...