Jump to content

Grilled Cheese PhD

Member
  • Posts

    30
  • Joined

  • Last visited

Recent Profile Visitors

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

Grilled Cheese PhD's Achievements

Apprentice

Apprentice (3/14)

  • Reacting Well Rare
  • Dedicated Rare
  • First Post Rare
  • Collaborator Rare
  • Conversation Starter Rare

Recent Badges

3

Reputation

  1. That is so simple and clever! You made my day with that tip!!!!!!!!! 🤓
  2. That might be a nice trick in some situations but to be honest, it's not a technique I would ever use. I think that would just sound like "a giant reverb" and not true to the instrument. 😉
  3. In Sampler, I'd like to be able to set attack, sustain, decay and especially release to values of up to 30 seconds. Currently they are all limited to 10 seconds. Case study in usefulness: I have some playable Tibetan and Crystal Singing Bowl sustains, and some bowed bell sustains too. These instruments sustain for ages after you stop playing them (sometimes up to a minute). Setting them to play "one shot" would not be suitable, and limiting the release to 10 seconds is unnatural for instruments that ring for so long. Seems like an easy update. Just increase the ADSR options from a max of 10 seconds to a new max of 30+ seconds. Cheers! ~Cheesy
  4. Oh dear. Hanging my head in shame. This error has been my fault… I have been using a plug-in that is not Apple Silicon compatible in my project: Native Instruments Transient Master. Exporting Audio regions to new Audio files works just fine if I (a) remove the plug-in or (b) run Logic in Rosetta mode. Sorry about this. I’m fully aware of AS compatibility issues and I should have checked this sooner. The reason I overlooked this is because most of the plugins in my collection are AS compatible, and even though Transient Master isn’t compatible, it works just fine in native mode during playback. Only during audio file exports is it unreliable.
  5. During testing, I just found another glitch. I right clicked on one of these selected regions and selected "Export as audio file(s)". With the regions soloed (which is why they are yellow) all the files exported as silence. Un-soloing the regions and re-bouncing them yielded a correct result. Any way... more testing to do. Just thought I'd share this unexpected result.
  6. Interesting. The regions start at various random places. I could try positioning each one on the start of a bar, but it shouldn't really matter where they are on the timeline. It's just audio data. No normalisation. No snapping. No automation. All files have a fade. I am using plugin processing during exports, so it's possible that they are affecting results in some way. Hunch #348734B: Perhaps plugin delay compensation is messing with the process in some way, given the fact that it's only milliseconds of data that's missing at the start of some files. I'll do a few tests to try and eliminate some variables and narrow down the cause.
  7. Hi Atlas007! Thanks for the suggestion. Unfortunately I'm not a big fan of this method. It's a bit simple and I prefer to use the region export function as it allows me to use Logic's handy file naming protocols. In any case, Logic should be able to export multiple regions without error. I've attached an example to reveal what's happening. Screenshot A shows the original region on top (with a fade out added) and the exported file beneath it. Both are exactly the same length, down to the last sample. Screenshot B zooms in very closely on the start of these regions. As you can see, the initial transient is missing from the exported file. Logic failed to render the file properly during export. WEIRD! Again, the problem is random. When I export a bunch of files, only some of them are affected in this way.
  8. If I select a number of audio regions in the arrange window, and then export them all as audio files, Logic is cutting off the start or end of some of them. The problem seems random. If I export 10 regions, sometimes I will get 10 good files, but other times I might get 8-9 good ones and 1-2 with the start or end trimmed off. It’s usually just a fraction of a second that gets cut off, but that’s enough to ruin the initial transient on a drum hit or guitar pluck for example. I have checked that my region edits are perfect. Logic really is cutting off the heads and tails of some during export. I have some plugins active on the tracks from which I export, both Logic plugins and some third party. This is a problem for me at the moment as I am creating some virtual instruments. This involves recording many individual notes, trimming them carefully to create one-region-per-note, and then exporting all regions to individual audio files. I need Logic to do this properly, otherwise I end up creating a Sampler instrument, start playing it, and then discover that some of the notes are incomplete. I then have to re-export the bad files and reintroduce them into the Sampler instrument. Hassle town. I’m using the latest version of Logic, MBP M1 Max. Cheers! Cheesy.
  9. “Update overview”. Yep - that solved it. Happy dance! Thank you!!! I suspect that the error might be due to RX9 not updating the waveform information after adjustments have been made. RX9 was recently updated for Apple Silicon compatibility so perhaps there are still some bugs that need ironing out.
  10. Correct. There were four peaks originally, then I silenced two. However, I did not silence them in Logic. I opened the original audio file in Izotope RX9, silenced two peaks, then exported that audio from RX9 as a completely new file with a new name. After importing this new audio file into Logic, the waveform is incorrect. I didn’t know about the refresh overview function so I’ll give that a try. Sounds promising.
  11. If a stereo plugin plays a kick that has the exact same information in both the left and right channels, then it’s effectively mono anyway. I don’t think this is something you need to worry about. For peace of mind you could also insert a Logic “gain” plugin on the channel strip and activate “mono” which will force the output to mono, even on a stereo track. Switching the plugin on and off will probably confirm that the kicks are mono either way. 👍🏻
  12. The zoom is the same. You can see the time ruler across the top of both images. They both show the same range of about 1 min 30 sec. More to the point, in the arrange window I can hit ‘play’ and watch the playhead as it passes over the waveform. Two of the visible sound peaks make no sound! Only the second and fourth sounds are heard, because the second and third ones don’t exist (as you can see in the grey waveform editor). Don’t think I’ve seen/heard anything quite like this in 25 years of using Logic.
  13. Here’s an odd glitch… The waveform shown in the attachments is a 90 second audio file. It’s the exact same file, shown in blue in the arrange/main window, and in grey in the audio file editor. The grey one is correct. There are only two sound peaks in the file, and that’s what I hear when I play the file in Logic. However the blue waveform shows two additional sound peaks (that make no sound when played). Originally the audio had 4 sound peaks. I opened the audio file in Izotope RX9 and completely silenced two of them. I then exported the audio to a new file and imported it into Logic. Not sure if the fault lies with Logic or RX9, but I’ve never seen a waveform display incorrectly in Logic before. It’s making it very hard to edit the audio when there are peaks in the waveform that are actually silent. Thoughts? Ideas? Cheers, Cheesy
  14. I agree that the M1 Pro is an awesome choice for Logic. In a MBP it’s silent unless you push it to the limit for an extended period of time. The M1 Pro / Max offer more performance than most people will ever need. The Ultra even more so. Logic can use all 20 cores in an Ultra. In another forum, one user managed to get his Ultra to play back 304 audio tracks each with 15 space designer plugins. That’s 4,560 convolution reverb plugins. Do you need that much power?
  15. I’ve always wondered if track duration has any bearing on the revenue paid to artists by streaming services such as Spotify and Apple Music. For example, does a 2 minute pop song earn the same amount per play as a continuous 60 minute long ambient track???
×
×
  • Create New...