Jump to content

figgypudding18

Member
  • Posts

    14
  • Joined

  • Last visited

Recent Profile Visitors

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

figgypudding18's Achievements

  1. Great question! I really don’t know. One thought I had was disk space but I have like 28/128g free and it still is giveing me the spinning beach ball indefinitely with logic. I don’t think I can really clear much more disk space, without digging into the 50g of “other” which I don’t really know much about. I should mention too that the other issues with my Mac are that the screen is pixelated (not a big deal) and also that it now is unable to be woken up unless I carefully crack it open and extend it gradually (will only stay awake up to a 40 degree angle about). Not being a Mac expert by any means Im not sure what to do other than get a new one, bc I’m sure Apple would say it’s worth nothing or would cost way too much to fix. Not sure what other people would do in this situation? Already bought the MacBook Pro with 16gb of ram but I’m genuinely curious!
  2. Hi All, I'm looking to purchase a new macbook. My 2017 literally does not run logic any more (I learned to turn off automatic logic updates too late), and probably shouldn't have upgraded the OS to Big Sur...but anyway... *current specs in signature* Which of these three would work for just simple, logic use (nothing crazy, amateurish levels of production, no orchestral scores etc), but plugin use from Universal Audio. I'd like to grab the cheapest option available that won't give me problems, and would maybe like to leave open the possibility of doing some bigger projects. Which of these options would be best, or do you have other suggestions? I would like to buy new. Thank you! Macbook Air - $1259 Apple M1 chip with 8‑core CPU, 7‑core GPU, 16‑core Neural Engine 16GB unified memory 512GB SSD storage 13-inch Retina display with True Tone Two Thunderbolt / USB 4 ports Macbook Pro - $1579 Apple M2 chip with 8‑core CPU, 10‑core GPU, 16‑core Neural Engine 16GB unified memory 512GB SSD storage 13-inch Retina display with True Tone Two Thunderbolt / USB 4 ports Macbook Pro (14 inch) - $1849 Apple M1 Pro with 8-core CPU, 14-core GPU, 16-core Neural Engine 16GB unified memory 512GB SSD storage 14-inch Liquid Retina XDR display Three Thunderbolt 4 ports, HDMI port, SDXC card slot, MagSafe 3 port
  3. Hello All, I've noticed I'm getting a spinning beach ball when I basically try to do anything in Logic. I guess I have automatic software updates on because I noticed I am updated to 10.7, which I'm thinking may be why I'm getting the spinning beach ball pretty much when I click around at all, or especially when I minimize Logic and try to bring it back up. My specs are in my signature. Any suggestions? Thanks for your help in advance.
  4. Hi All, I hope I'm posting this in the right place. It's not entirely Logic related, although I'm running Logic, and planning on going through the apple certified Logic book soon. I'm in the process of setting up my first little home studio and I've got a bit of a conundrum on my hands. I was lucky enough to purchase an Apollo Twin DUO X interface and an Arturia KeyLab Essential 49 midi controller, as well as some monitors. My MacBook Pro specs are the following: OS: Big Sur 11.2.3 2017 Macbook Pro, two Thunderbolt 3 ports Processor: 2.3 GHz Dual-Core Intel Core i5 Memory: 8 GB 2133 MHz LPDDR3 As my storage is way too small, I have to use an external hard drive that connects to a thunderbolt port. This carries my logic sound library and will probably also have my apollo stuff that's not on the interface itself, so it needs to be plugged in. Problem is, one of those ports also needs to be used for the charging cable, another for the interface. That's 3 ports that I need, 4 if I was wanting to have the midi controller plugged in at the same time. Is there a way to get more thunderbolt 3 ports without compromising performance? I've heard something about "daisy-chaining" but also how it gives less bandwidth to each device, and not sure if that would be a good idea with all this stuff. Is there some sort of device that would solve this issue? Thanks so much for any help and wisdom you can offer!
  5. Hi all, I’m looking to really buckle down and get more serious about learning how to produce on logic. I need to buy a midi controller. I’m probably going to start going through the Apple certified logic book. Can’t spend too much money right now, maybe 100-$200. Would like something with a decent feel. Is there a midi controller that most people use for logic? Thanks! Then for audio interface, I’m thinking the basic focusrite Scarlett.
  6. Hello, I have a 2017 Macbook Pro with the OS Mojave. I currently have Logic 10.4.8 and I cannot figure out how to update to the newest version. I thought that maybe I needed to update the OS to Big Sur, but due to my very small amount of storage (128gb), I don't think I will be able to do that. If I go to the app store it just says go to app and does not offer the option to update. Any help appreciated. Thank you! EDIT: Sorry everyone, I was just missing the update button--I found it. I'm gonna have to figure out how to get the space available I guess.
  7. Thanks for your replies and help everyone! Much appreciated!
  8. It's all pretty much brand new to me, I have watched quite a few videos on compression and know the definition of all those things you mentioned until you get to true peak, LUFS, and RMS, but I think true peak is the highest decibel range in the song, and LUFS and RMS describe the overall volume level....but yeah just started learning. It's just a project for a video, so no streaming platform.
  9. No. Just was using the numbers as some kind of standard to go by.
  10. Just saw them in research a lot of which stating they are the correctish numbers for streaming platforms. In all honesty, I'm just trying to make sure my music is matching the standard volume of most other music....not trying to obey arbitrary numbers but just looking for something to go off of....or do you think I'm totally good to just follow my ears?
  11. Hi there, I'm trying to balance before bouncing. I've seen that the levels for LUFS should be -12 to -14, and RMS should be anywhere from -7 to -9. However, I am not finding these levels possible at all, despite my best efforts to adjust the gain etc....and yes it could totally be because I did something else wrong. First time really mixing/mastering... Any suggestions?
  12. Hello Everyone, Breezing through the mastering process just for a very small little project. I've seen there are ideal measurements for RMS and LUFS. How do I go about changing them? Brand new to this, so sorry if it's an obvious question. Do I adjust gain, volume etc...? Thanks!
  13. I personally don't subscribe to the whole "-18 dBFS" school of thought. Just stay below 0 dBFS but there's no need to shoot for -18. But other than visually it doesn't truly matter. What you're seeing is not the "white line compressing the gray frequency", what you're seeing is the white line showing you the amount of gain reduction the compressor is producing over time, and the gray displays the level of the incoming audio over the same time. What I'm seeing on your graph is a lot of compression going on (the white line is pretty much below 0 all the time). That's due to your very low threshold setting. It's hard to give advice without hearing what you're doing, what the song is, how the vocals were recorded etc... but it does look like quite a lot of compression. Thanks, I really appreciate the response! I have seen a lot of mixed messages about the -18dB thing. My only question is does just staying below 0 dB like you said lead to problems mastering/later on? Also thanks for the compression advice, I will definitely tinker with it some more...
  14. Hello Everyone, this is my first post in this forum as I am pretty new to using Logic. I'm working on compression, and I've watched a ton of videos and I think I've found a good level for my lead vocals. However, I'm a bit confused. In all of the videos I watched, when the person showed the graph in the compressor, you can see the white line actually compressing the gray frequency, whereas in mine, it is mostly above the gray frequency, which visually leads me to believe it isn't compressing, contrary to what my ears might think they are hearing. If I raise the gain, the gray frequencies get closer to the white line and if I really raise it, the white line can go really far into the gray, just as I am seeing in the videos I have watched. I was originally trying to keep my tracks around 18db/peaking at 12db, but I don't know if I should raise the gain to make things look "right'. I guess I am really not sure what the significance of the graph in the compressor is. Could someone please explain? Thanks!!!! Picture of the graph in my compressor:
×
×
  • Create New...