Jump to content

3ple

Member
  • Posts

    1,721
  • Joined

  • Last visited

2 Followers

Recent Profile Visitors

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

3ple's Achievements

  1. I meant "fixed" as in you can't manually change it with a Knee knob like other models
  2. Thanks for the replies. Yes, I just checked and the Studio FET does indeed have a more pronounced curve compared to the other models and also doesn't have the Knee option so it's a fixed knee. I rarely use the Graph visualizer, to be honest, so I wasn't even considering that. Now looking at the Graph I also noticed that the "average" threshold point at 3:1 is lower than the one at 8:1 (which makes sense since the curve gets smaller the higher the ratio) and that makes the compressor compress more at 3:1 than 8:1, because at 8:1 the line only starts curving at a higher threshold. That was an interesting thing that I've never really noticed, but oh well, we are always learning new things Thanks again for the feedback!
  3. I'm compressing a synth using the Studio FET option and I get 2 weird behaviors. I tried with the other options and they work as expected. If someone can enlighten me... 1 - Even though my threshold is set to 0dB and the input peaks at -3dB (average), the compressor is still working: 2 - When I set the ratio to 3:1 I get more compression than when set to 8:1 or higher.
  4. 3ple

    Apple Loops

    Not sure if you’re aware but Loopcloud receives midi as well so if you have a sequence in Logic, just copy it to the Loopcloud track and now you can listen to it as well. It even lets you transpose the sample depending on the pitch of the midi note. The only advantage for me when it comes to Loopcloud is that you can save patterns, which I wish Logic would have an option for that. I have an idea for a plugin that does that but I need to find a developer that wants to build it with me
  5. 3ple

    Apple Loops

    Another great FREE tool that I would recommend, if you don't know it yet is ADSR Sample Manager. It also works with loops, but there are some features there that I think they still need to work on for it to be as good as Loopcloud for loops. But for samples, it's better than Loopcloud for sure. You can also use custom tags and it works as a plugin, meaning you can have 10 instances of it, unlike Loopcloud which limits you to 1 instance per Logic Project and doesn't save the state (unless you subscribe to a plan that includes that option). But those 2 tools are great time savers
  6. 3ple

    Apple Loops

    You're more than welcome! We are all novice at some point, right? We learn from each other as well so I'm glad I can help. Take time to explore and you will see how great that plugin is. It can literally save you so much time! Also, you can tag the files with custom tags. For example, let's say you have a drum loop that sounds "soft" to you and one that sounds "hard". You can tag them like that "Soft Drums", "Hard Drums". The more you customize your files, the faster you work. When you import a folder, it automatically analyzes and start some automatic tagging, so it saves you some time. It's not 100% accurate when it comes to some tags, but I would say it's 90%, which is great
  7. 3ple

    Apple Loops

    Let's see if I can help and explain everything... Loopcloud is not a plugin that runs inside Logic, per se. You create a new software instrument and then insert as such, but then you have to launch the standalone version (this is actually something I dislike and wish they would come up with something better, but oh well...). Logic then will create a connection between the plugin and the standalone version. It comes with some "welcome" sounds, but then you can import your own folders by just dragging them into the Loopcloud window (standalone version). In this case if you want the Apple Loops, just go here: /Library/Audio/Apple Loops and drag the Apple Loops folder. Loopmasters give you some credits that you can use to buy loops so you will have access to their store and you will for sure be able to find endless options, not just electronic music stuff. They also offer free loops and samples everyday, depending on your subscription (if you decide to buy one, of course, but even with the free version you get a few free loops and samples everyday. You just can't pick which, but... I would suggest that you take some time to read the manual and even watch videos on YouTube so you can get familiar with it, because as I said, it's a great tool. It would be great if it was a real plugin, but overall I rather have it that way than Logic's loop browser. You can edit the loops before importing them, change the starting point, change the pitch, speed, etc, something that you can't with Logic's browser. As with everything else, it takes time to learn all the paths and shortcuts, how it works, but it's not hard once you get familiar with it. They are also very responsive when it comes to bugs and all that, so it's also a plus when you experience some kind of bug. Hope this helps everyone here anything else, let me know
  8. 3ple

    Apple Loops

    I’ve never experienced this, but as I mentioned before, Loopcloud is just a better solution for many different reasons. Logic’s loop browser is just outdated. Maybe one day Apple will decide to update it, but for now I rarely use it. Sometimes for something quick, instead of opening Loopcloud and creating a new track, I just the browser. Other than that, it’s just crap. Loopcloud is free and it gives you so many different options including not having to convert to an Apple Loop. Try it, if you haven’t yet
  9. Well, basically everything inside Logic affects other things, right? That's not what I mean. The mute button does only one thing and doesn't move around when it comes to routing, unlike the Sends. You can have the Sends in 3 different places, depending on the option you pick and it affects the signal in 3 different ways. A mute is a mute. An insert is an insert. You can't have an insert after a pan or the sends. That's what I mean by not interacting with another feature. Also if you think about the flow itself, it doesn't really matter if the Mute is at the bottom or after the sends. It mutes everything. The final result is the same: silence. So regardless of it being at the bottom or not, you get the same result. There's no confusion there. Someone starting out with Logic will not be confused about what the mute button does, either it being at the top of the channel strip before the MIDIFX or at the bottom after the fader So again, if you think it doesn't make sense that the Mute is at the bottom, because that's not how the routing is done behind the scenes, then why is the pan before the volume fader if that's not what's happening behind the scenes? Kinda counterintuitive, don't you think? In this case I don't see it as a matter of personal taste. I see it as it being logical to the majority of people. You shouldn't need to know the internal routing to being able to work with the program. Everything in the channel strip flows from top to bottom, why is it "broken" when it gets to the sends? Then why did they change the instrument from the bottom to the top? It's because of the visual workflow. Again, I'm not saying that the pan should be at the bottom, but I believe that changing the routing internally or changing the names would make much more sense, because people would be able to see it right away, according to the names and the flow top to bottom. I understand the concept in the hardware environment, but when it comes to software, you can change things around so they could easily change the routing to be Inserts > Sends > Pan > Volume. Then the names would make perfect sense. Right now, they don't. If we were to mimic the real world with hardware, then we wouldn't even be allowed to do 90% of the things we do inside a DAW, correct? DAWs were made to make our lives easier and the workflows faster. I don't think they are supposed to mimic the real world all the time. In a console you have a fixed EQ, correct? So you deal with it the way you can. In a DAW you're free to either have an EQ or not and where it goes. That's just an example, for course.
  10. I see what you mean, but all those other options don't directly interact with another feature. What I mean is: since the Sends interact with the Pan and the Fader, then there should be some logic behind it. I'm ok with the other stuff, because they are independent, if you know what I mean. If they changed the names of the 3 options just how I suggested, then the channel strip didn't need to change anything. I don't even see why the route is Sends > Fader > Pan. Can you explain it with an example, because I can't really see the logic behind it, if there's any advantage or something? Also, if companies are trying to mimic the real life environment such as a mixing desk, then the mute and solo should be before the fader: But again, that wouldn't really bother me, because I see those as 100% independent, unlike the Sends where you can move the routing to 3 different positions that, as of now, don't really seem intuitive. Looking at the channel strip, wouldn't we assume that Post Pan and Pre Fader are actually the same? It's quite confusing and even though I know how it works, it always requires me some time to really figure out what I want to do, because I need to think about the whole internal routing instead of just looking at the channel strip and understand it right away, if that makes sense
  11. I think you're missing my point I'm not talking about how things are routed internally, behind the scenes, but how they flow in the channel strip, visually (which should be intuitive) Remember when Logic had the Software Instrument below everything? It didn't make much sense, right? Because it all starts with the instrument and then it flows from top to bottom. Then they changed it to the top, where it makes sense Regardless of the pan (behind the scenes) being before or after the fader, we look at the channel strip and we see MIDIFX > Instrument > Inserts > Sends > Pan > Fader. Even the Output option, according to this logic (no pun intended) should be at the bottom after the fader, not after the Sends. So looking at the channel strip and saying it's "Post Pan", makes me think that the sound is sent after the Pan, but before the Fader. In fact, that's happening after the fader, so it should be called Post Fader. Again, regardless of what's happening behind the scenes. It should be intuitive. So all the other options I presented are according to how things are laid out visually. According to this post (http://www.carneymediagroup.com/musictechhelpguy-videos/2018/12/20/logic-pro-x-effects-sends-post-pan-post-fader-pre-fader-sends-on-faders-independent-pan) here's what he says "These can be a bit confusing because you might think that the pan knob comes before the volume fader, just because of it’s position on the channel visually. The opposite is actually true. The pan knob comes AFTER the volume fader from a signal flow perspective." For me, the moment something can be confusing, it means that it needs to change and become intuitive. That's just my point, otherwise we would all be creating things that work one way behind the scenes, but then visually speaking it would be different. Things shouldn't be built thinking of the "tech/geek" users, but for everyone to easily understand how to
  12. Since I started working with Logic I always found very confusing and not intuitive at all the way the names for the bug routing were picked. For me, based on what they do and where they are located, the names don't really reflect what happens behind the scenes. Example: Post Pan, isn't actually post pan. Is post pan and post fader and since the fader is after the pan, why not call Post Fader? The same for Pre Fader. It's not actually Pre Fader. It's Pre Fader and Pre Pan, and since the pan is before the fader, why not call it Pre Pan? And then there's this other option that's after the fader, but pre pan, so why not just call it Post Fader/Pre Pan? Also the order in the menu, should be reversed to reflect the different point where this happens. Here's my option. Let me know what you think:
  13. Mine is here, for example: /private/var/folders/_n/b_vl0wcx1lsfyw2979zfnt4w0000gn/C/com.apple.MusicApps Have you tried looking inside all folders inside /private/var/folders ? On my post I mentioned a specific folder, but take the time to search inside each one of them. I'm not sure if Apple changed or not, but I would guess that each computer and each installation creates different folders, I don't know. Look at how mine as inside a _n folder and then another folder that had a long name and ended with gn as I mentioned in my post. Maybe on your computer is not the _n folder, I'm not sure how that works...
  14. Thanks. That did the work. I didn't know about that feature. For anyone reading this thread here's an image of what it looks like using shift vs not using it. Top: original Middle: no shift, just drag Bottom: shift+drag (mirrors the original)
  15. Here is a sample project (attached). It is a nonsense collection of notes, but is an example of a new project, not from a template, into which a midi track has been added and the automation won't write. Many thanks! I was able to both write data using a controller and manually moving the knobs. What I meant by "template" was that when you start a new project, Logic shows you the window and when you select the "Empty Project" option, for example, that's a template. There are other templates and it could be the case of one having a problem, but since I record automation, I guess there's something happening with your Logic or maybe something conflicting between Logic and the OS itself. Catalina isn't the most stable OS, from what I heard, so it wouldn't surprise me that it's another conflict. Hope someone here can figure it out for you. Good luck and stay safe!
×
×
  • Create New...