Jump to content

dead_beat

Member
  • Posts

    33
  • Joined

  • Last visited

dead_beat's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Hi David, Just following up on this: - The file was created in the current Logic version, 10.6 . - Yes, I can scroll up, and it looks like this: - Yes, I can open a new mixer window, and it looks normal: This has been a constant bug since installing 10.6; it's easy to make it go away (just select another view, single/tracks/all, then go back to the original view), but thought it would be worth reporting. Many thanks
  2. Hi all, Since installing 10.6, I've been sporadically getting this when I open the mixer window (maybe 50-70% of the time): Anyone else seeing this? Many thanks!
  3. I forgot, sorry, I made a little sketch too: However, again, the problem won't be completely apparent without looking at the project file. Many thanks!
  4. HI all, I've been noticing a number of bus/aux/send routing issues in 10.6.1 . I was able to isolate one issue, and I will attach the file. However, there have been many, and I'll add more to this thread as they appear. In the attached project, the routing is as follows: There is a vocal source, in a stack. The stack header has 2 sends: let's call them 'Aux A' and 'Aux B'. The stack sends a fixed value to 'Aux A'. The stack's send to 'Aux B' is automated. 'Aux B', in turn, sends some of its signal to 'Aux A'. Here's the behaviour I'd expect: If you solo 'Aux B', you should only hear those signals that pass through 'Aux B'. So, if no signal is being passed to 'Aux B', you should hear nothing. However, here's the behaviour I'm getting: 'Aux B' is soloed, and no signal is currently being passed to it. However, I still hear a signal, being passed through 'Aux A'. The question is: why am I hearing signal from 'Aux A', when no signal should currently be passing to Aux A? This might not make much sense in the abstract (it's not as simple as it sounds). So I'm attaching a very simple project file here: example 9 2 21.zip Many thanks in advance for your insights!
  5. Just following up on this thread, now that I've moved all assets onto my new internal SSD. Now, all data is on the internal SSD (no other drive is connected). However, Logic still creates new overviews for all audio each time I reopen the project. The SSD is formatted with a GUID partition map, as required for a Mac internal drive. Any ideas why this might be happening? (Attaching images from Disk Utility below, showing all of the specs of the new drive and the container which holds the 2 volumes 'Mac HD' and 'Mac HD - Data')
  6. Ah, well spotted JakobP! Many thanks for working that one out. It's possible this happens when I use the marquee tool to split longer looped sections into smaller groupings, and the original audio region isn't a perfect number of bars. Occasionally, depending on the tempo and settings, regions end up being just a sample short of a bar. Agreed it still doesn't explain the behaviour, but at least (hopefully) resolves it! Thanks again
  7. Also want to add a +1 to lovenest's point: this audio initially looped fine, and at some point it inexplicably stopped looping. The same thing has happened in several projects.
  8. Hi forum, Just wanted to add a +1 here: I've been experiencing the same issue. It's been happening in multiple projects, but with most of these I've replaced the loops with copies of the regions (obviously not ideal). However, I'm attaching the most recent project file where the issue has come up. (I've deleted all data except the track with the audio looping error). Thanks! audio looping error - example a.zip
  9. Thank you David, and sorry for delay - it currently appears this is an issue only with packages received from a particular client. I reproduced the scenario by uploading logic files saved as 'packages' then downloading them, but couldn't reproduce the problem. I'll check in with the client to see whether he's updated to 10.6, or whether there's any other dodgy stuff going on there. Thanks for your help!
  10. Hi all, I've encountered an error immediately after updating to 10.6: I often use the media browser to import channel strips from one project into another. The projects I'm importing from tend to be sent to me by a third party (and saved as 'packages' rather than 'folders'), so they'll be downloaded into my 'Downloads' folder. I'll subsequently move these client project files into a folder where I keep all of the assets for that particular project. Here is my example project: In the image, 'client's project file' is the project file I received (into the Downloads folder) from the client. 'project file' is where I keep my own logic project file/folder for that particular project. Now the strange part: since updating to 10.6, whenever I attempt to import data from the client's project file, it looks for the audio in the location where the project was originally downloaded to, ie the 'Downloads' folder, rather than looking for the audio in the directory where the client's project file is now stored: As you can see, it's looking for the audio in the 'downloads' folder, as if the project file is still there. However, 'downloads' is empty! So of course it won't find anything there. I've experienced something similar before, so I thought to try saving the project as a 'folder' rather than a 'package' (as I know 'package' contents are sometimes not searchable). Voila - Logic now rightly sees the project's assets where they are. So it's clear this is a problem strictly with project files saved as a 'package'. This is easy enough to solve once, but i receive dozens of these 'package'-style files from clients who are not advanced users every week, so I'd rather not have to save them as a folder each and every time. Can you explain why, for project files saved as a 'package', Logic is looking for a project's assets in the folder it was originally downloaded to, rather than its actual location? Many thanks!
  11. Excellent, that's worked perfectly! Thank you both for your help - absolutely love this forum.
  12. Sorry, forgot to mention that - yes, auto-assign is already disabled for the APRO under Logic > Control Surfaces > Preferences > MIDI controllers. But unfortunately the problem remains. Regarding the control surface plugin - sorry for not mentioning this either! Roland supplied a control surface plugin which I installed and cannot uninstall (the uninstaller is defunct, and so far Roland's tech support haven't been able to tell me how I can uninstall the plugin manually). I wasn't sure if it could easily be solved within Logic itself, so wanted to check!
  13. True, I use the EastWest steinway piano regularly, which is much heavier, and have never experienced timing issues - Sampler's Yamaha Grand was just going absolutely loopy. Will investigate further and post back here.
  14. Will do, thank you David - I'll be returning to the affected project shortly, and I'll double-check to see if the problem still occurs. I'm suspecting that it has something to do with the fact that the Yamaha Grand is so much 'heavier' data-wise than the other Sampler pianos; just confused as to why the timing errors were so bad but the CPU/HD meters were comfortably near zero. Will upload project once I've double-checked.
×
×
  • Create New...