Jump to content

depthofallthings

Member
  • Posts

    24
  • Joined

  • Last visited

depthofallthings's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Tried that too, even tried selecting the 4 tracks, copied, then selected another 4 in a row and hit paste… then it only pasted automation— no regions. So weird!
  2. Hello! I'm currently trying to copy a few regions from 4 tracks in a row, trying to paste over to another set of tracks. But for some reason, whenever I paste, it's pasting only on the original tracks not the new ones. My default Command+V for paste is now pasting like "Paste at original position". I'm not sure what I pressed to change this, but before it used to paste copied regions on any tracks regardless. Any help would be appreciated. Thank you!
  3. Thanks David, unfortunately if I add automation points in my slope, it will not add the point directly to it. It will force the new point all the way to -inf and I have to bring it back up and eyeball it, won't be 100% linear where it left off (another bug). I was able to add a slight curve and that worked as well, I suppose having it more rough either with curve or extra points will be the only solution. Any other ideas?
  4. Hello, I upgraded to 10.7 recently, and today I noticed a huge bug with automation. Apple was able to replicate the issue and after a few hours determined that everyone on their team has the same bug (even users with Monterey). Now my case is with the engineering team. Here's the issue. If you have any gradual automation change set over 50 seconds, it will drop out down to the lowest or highest value if it's a gradual increase or decrease. You can test this out by creating any new track and setting a volume automation of -inf at the beginning of your project, then 0 dB about 4 minutes in. Scrub your playhead from start to finish but watch the automation value readout on the left panel. You'll see it dropping out incrementally. Some is more noticeable than others, depending on how drastic the change in value is. Please note that this affects ANY type of automation. Bear this in mind if your projects have been sounding a little strange lately or if you're hearing things change quickly where it shouldn't. Here is a gif video: If you are also experiencing this problem, I recommend reporting to Apple so they are able to gauge the impact. I can see this being a big issue for a lot of us being how common and simple this type of editing is. Please let me know if you find any good workarounds other than rolling back the Time Machine. Thank you! EDIT: I have found a slight workaround, still not great. The issue seems to happen between two single points of automation set over 50 seconds. You will have to place automation waypoints along the slope within 50 seconds and it will not drop out. Unfortunately, it will drop your automation to the lowest point, so you'll have to eyeball where it needs to go back up to. There seems to be yet another bug. If you click on the middle between two points, it doesn't just simply add a point. Best regards, Mickey
  5. Not sure if anyone was aware of this (I just learned the hard way) but our beloved "Snap to Zero Crossing" does not work properly for stereo files. I found out because I was noticing clicks/pops on only one channel at times, and when I zoomed in, it didn't look like the right channel was snapped to a zero crossing, only the left side. So, I split the stereo file to a left and right mono track, highlighted both tracks, split once, and voila. Two completely different zero crossings and NO POPS on either side. This is good knowledge for those of us who are working in videogame music. (not sure how this is going to work with exported looping tracks because one side will always be hanging off, but odds are the few samples difference will be fine as long as there's a zero point on both L & R, then the interleaved track should sound perfect once looped) Just wanted to let y'all know. If I'm wrong here in some way, please let me know. But after hours upon hours of testing many different methods, this solved my issue. It would be great if Logic found a common zero crossing for L & R in interleaved stereo files, but it doesn't appear to be the case. Maybe it's a rare chance both would have a zero crossing at the same exact sample? Please see the correct split zero crossing in my attachment.
  6. Just to touch on what David mentioned, there needs to be a blend and proper usage of both mono/stereo in a mix. Your bass frequencies should typically be narrower in the mix, but you don't usually want to just pan to the left or the right because you could be losing signal that was on the opposite side. You'd be better off using a Direction Mixer and try to merge the stereo more towards the center to taste. Again typically bass frequencies sound better as mono, especially a bass line or kick, but some synth bass notes can sound really cool if they are in stereo. The big issue why most engineers say that mixing stereo is so tough, is because there needs to be a balance. You have to keep monitoring your Gonioscope and that way you can see what individual mono tracks, and the entire mix is doing. If it's starting to go out of phase, or too stereo, then that means that your mix is too wide and will sound bad if played as mono, like through a bluetooth speaker that could be in mono. Mono compatibility should always be taken into consideration when mixing, and mastering. With headphones, your mixes may sound really awesome if they're "too wide" but this is dangerous. The meter will help guide you, and you should be creating mixes to where they will be compatible on multiple setups, including mono/stereo. Again, it should all be in taste. The real magic comes down to the mix and where the individual instruments and tracks lie. You want to make sure that everything has it's own room to breathe, so you can hear all the instruments in all their glory. Imagine an orchestra. Now imagine if you had every instrument in an orchestra hall, panned to the center. Every instrument would be fighting for each others spaces. Now think about how a real orchestra hall is set up, (they can be set up multiple ways). For example, furthest from left to right could be, Basses, Violas, then Violins, then Flutes, then the right side could be Oboes, French Horns, Cellos, and Clarinets. This is just an example, but this should help you imagine in a real depth of field. You want to think about physically where your instruments would be if you were to have them in a live setting, and USE YOUR EARS! Play around with the panning and Direction Mixer to put the instruments where they best sound for you. Happy listening!
  7. No problem! To start with, I'd say check out this Apple Support link. Let the Mac itself determine if there are any issues with the cpu. If one of your cores is shot, then this should detect that. Apple Support If you want to see core performance and try something after the Apple Support link, then try Geekbench. Geekbench Let us know how it goes! I'm actually rather curious to find out of one of your cores is bad or not. Please do reply and let us know the outcome of these stress test programs! Best Regards,
  8. Does it stay idle consistently? It could be an issue with one of the cores on your processor actually. I would recommend getting some sort of CPU tester for Mac that can stress test each core in multithreading mode and see what the results are. If a diagnostic program comes back okay, then there would have to be an issue with Logic, if so and you're on the latest version then I'd recommend a complete re-install of Logic Pro X, save your prefs just in case if that happens.
  9. I reset the audio engine and surprisingly it seems to bounce okay after that (unless I got lucky). I hadn't reset the audio engine for a few months prior to bouncing and normally I do from switching things around etc... I'm fairly positive this was the issue, either resetting or changing it to built-in audio while bouncing. I honestly wouldn't be surprised if it was the audio engine because I was having massive cpu overloads while mixing the last few months, I'd imagine with how many I was having without resetting the engine would probably make it act a little funky somewhere down the line. Thanks again! I'll post if it happens again however for now it seems to be okay.
  10. Hey David! Thanks for the post, yeah I usually leave plugin latency set to All, however I have never tried changing to built in audio! I'll give that a shot.
  11. I haven't tried those, would it be a good idea to turn these features on/off upon bounce when I'm bouncing a split master stem then change back afterwards?
  12. I do have additional plugins but not on the master stem that I'm bouncing. The other tracks in the project that were used to make the master stem are in the same project but are muted and all plugins turned off.
  13. I do have a few plugins on them, however I have them turned off and the power off on the tracks using the power on/off button in the hidden track options. Could they still cause issues even if they're turned off? Is it because they're loaded into the memory and can still cause trouble?
  14. Hey everyone, I'm having a strange issue I don't recall ever having before. This time I'm having an issue where if I export a track, there's a chance that the bounced track will have a click/pop and makes a split second of dead silence somewhere in the track. Just to give some more information, these are tracks that already bounced previously as a rendered export from a master stem file from a soundtrack I made. The 24bit master stem has no issues, I import the master stem then split the tracks to make individual tracks then bounce again. These individual tracks are the ones that have the issue once bounced, now not all of them do this but some do and it's completely random. I kept them in the same 24bit wav format. Is this something do to with resetting the audio engine or buffer range size? I thought all the buffer settings were for playback only, not upon bounce. If anyone has any ideas please let me know. It seems since the file is already rendered, it bounces them really fast like in 1-2 seconds, maybe it's bouncing them too fast? Thanks! Mickey
×
×
  • Create New...