Jump to content

Danny Wyatt

Moderator
  • Posts

    803
  • Joined

  • Last visited

Converted

Recent Profile Visitors

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

Danny Wyatt's Achievements

  1. But as you can see, you won't input the BPM, because that's exactly what you are trying to find and if "rounding" would be a problem, then Logic would be worse than my "app", because as you can see, my "app" gives you more decimals compared to Logic The main idea of this "app" is that you don't focus on a grid, because as I mentioned, this is primarily a tool for everyone to use it, with or without DAW. For example, if someone sends you an audio file and you don't know the BPM, but while playing it, you can clearly see that it has 8 beats / 2 bars. Ok if you see that the audio file has 3.29 seconds, those are the only 2 details that you need in order to find the correct BPM of that audio file. If the audio has some extra silence and it's not a perfect loop, neither my "app" or Logic will help you with that, because it will always focus on the full length of the audio, including the silence. You won't be saved there, regardless of the tool. You will always have an out of sync loop there. The issue will be the audio file, not the tool used to find the BPM. It depends... sometimes FLEX sucks and using an external tool can be your best option. Also, working on loop files is not always only when working on a project. Maybe someone is working on their loop library, so having access to a calculator that is super accurate, will help them find the exact BPM of a loop, but more importantly, if they have to create a PERFECT loop, they will be able to do that as well, because using the option on the right, you will have the most accurate length of that file if you want a loop that syncs 100% Anyway, I'm happy to know that people are using this tool and you find it useful. In the end, tools are just tools and whenever you find this to be useful, go for it! Eventually one day I would like to create an app for mobile to make it even better, but that's expensive...
  2. The goal of this "app" is that people without Logic or any DAW are still able to find these calculations. Sometimes I'm just working on loop files and I don't want to open Logic for that, as I'm using another audio editor. Also, using Logic, you need to open it, create a new project, save that new project. That itself, just to find the right ms of a file or the bpm, seems a bit too much work. Then if you are working with 100 files, are you going to import one file at a time and go through all those steps you mentioned? A lot of work, in my opinion. :) With this "app" you just need to see the length of the audio file, understand how many beats and bars and that's it. Pretty fast. Sure, you can still use that method for specific scenarios. It's a matter of evaluating what needs to be done at a particular time.
  3. So you're saying "some projects" behave like that and some don't? To be honest, I'm not familiar with M1 or Rosetta, so I can't comment on that, but if only some projects get affected, maybe that's an issue with some plugin(s) you have on those projects... but it's hard to know which, if everything is transparent... What you can do is try to import one of those projects into a new project and start by only importing some channel strips until you see the channel strip with the issue (if indeed the issue is with one or more plugins). Does it make sense?
  4. That make sense!I think it would be even better if that sort of implementation would also permit to stack 3rd party plugins as well... Yes, I was not expecting this feature to just allow stock plugins. I mentioned stock plugins on my previous reply, just because any 3rd party plugin I found would not allow stock plugins, such as the one you suggested, Plogue Bidule, etc. For now, the only workaround is to send the channel strip's output to a bus (that would act like the wrapper) then the wrapper's output to another bus, and that would be going to the main output. Then you could create a stack out of those 3 channel strips and save patches/channel strip settings for the 2nd channel strip. But it's a waste of time and resources every time you want to apply this kind of workflow. A separate feature would be awesome.
  5. I've used that in the past, but it doesn't allow stock plugins, which is 99% of what I use :/ My idea with this thread was more about something native to Logic, which would be way more interesting (and less prone to error in the future when Apple decides to make radical changes and all companies have to update their own products).
  6. Note that there are two freeze methods in Logic - green snowflake, and blue snowflake. The regular freeze freezes the entire channel strip in the method you describe - the instrument, and all plugins, get rendered to audio, and you can't change those plugins. Source-only freeze freezes just the instrument, but leaves the plugins on that channel live - good for for example, a heavy CPU synth part, rendering that (in a similar manner as bouncing pre-plugins to audio), but leaving the plugins live for mixing/tweaking etc. Yeah, that's really not a feature I'm familiar with so I didn't know you could just freeze the instrument itself. One thing I also pointed out on my previous reply, is that freezing ends up locking the regions, unlike BIP where you can manipulate the new regions without the issue of overloading the CPU, so that's a benefit of BIP, in my opinion. I guess both can be useful depending on each scenario. Maybe I will explore that in the future with the option to just freeze the instrument. Thanks for clarifying.
  7. Yeah, as I mentioned, I don't remember the last time I used the feature so I'm not super familiar with it. One thing I want to point out though is that the argument that "both take the same amount of time to apply" is subjective, because the freeze applies to the whole track while you can bounce in place just a small part of the song, depending on your needs. Let's say you have a small region that's a 1 bar long right at the beginning of the song and the same one at the end, so they have a 3 min empty space between them. Freezing the track will create a 3+ min long file, while with BIP you can just focus on those 2 sections, with the advantage that you can then move, delete, loop, etc, those audio regions for experimentation.
  8. Yes, the general idea would be similar to the pedal board, but for plugins. I mean, even if they just created a single plugin slot (without the extra feature to expand it in the channel strip), that would already be an awesome improvement. It's something I would be using over and over again, to be honest. I've never used the I/O plugin, but reading about it, it seems it wouldn't do anything about this particular situation. The selection based processing isn't an option either, because it's not something you can save for other projects and the idea here is that you are also able to move that group of plugins to a different position in the channel strip. And of course, if we are working with MIDI, how would selection based processing work? But I guess your idea of the pedal board could be the beginning of something if they could somehow reuse that plugin, duplicate the code and transform it.
  9. Note that it's not a Logic user account. It's a new macOS user account and then opening Logic to figure out if the issue is with your current user account or global.
  10. I don't remember the last time that I had to freeze tracks, but I believe once you do it, you can't mess with the inserts or sends, right? Something like that, I guess. The advantage of BIP is that you can just bounce the MIDI to audio (if you choose not to include the inserts), but still mess with the inserts and sends. That would be my workflow
  11. I had to do this in the past and what I did was I reconnected the missing samples and then saved it again, maybe with a slightly different name. When you replace the samples, do you usually hit the Save inside Alchemy to save/overwrite the preset?
  12. Can you delete all audio and midi regions and share the project so we can test it here? Create a copy of the folder on a different location (so you can mess with it without screwing the original one), delete all audio from the Project window on the right, then make sure you go to File > Project Management > Clean Up to completely remove all files from the project, before you ZIP it. Then upload it here. I will be happy to test it.
  13. Please share a screenshot of the Mixer view so we can see how things are routed. Also, if you press the i icon next to the R, you will be able to audition without recording. This also depends on your settings here: Preferences > Audio > General You have 3 options for the monitoring. Play with them and see what suits your needs.
×
×
  • Create New...