Jump to content

Dnonkong

Member
  • Posts

    35
  • Joined

  • Last visited

Recent Profile Visitors

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

Dnonkong's Achievements

Newbie

Newbie (1/14)

  • First Post Rare
  • Collaborator Rare
  • Week One Done
  • One Month Later Rare
  • One Year In Rare

Recent Badges

0

Reputation

  1. I'm seeing this behavior now in a film scoring template. Loads of VI's powered off, samples purged etc. File sizes ballooning up to 2-3gb. I took a peak inside and it seems Logic is duplicating the movie file split audio files (Dx, Tmp) inside the media files folder, which added with project file backups accounts for the huge size. These are all saved as folders, and reference the audio within the audio files folder. If I delete the content from the media folder, Logic will repopulate it when re-saving. Any ideas? Using 10.7.3 on a new M1 MBP.
  2. LPX Colorizer is indeed the culprit. I reverted to the standard Logic theme (ie. uninstalled LPX Colorizer's changes) and the problem went away. The latest versions do away with the plug-in, but apparently at the cost of potential crashing. Thanks for your input @Des99.
  3. Yes, no luck in either place. I'm starting to suspect it has something to do with LPX Colorizer. Going to try and uninstall that and see what happens next.
  4. @Des99 No sign of a Strip Control plug-in in either locale.
  5. I'll try that @Atlas007 and report back! @Des99 I'm not exactly sure, I've never seen it before. Pretty sure it's not a third party plug in? At least not one I was aware of installing.
  6. I have indeed, everything is re-scanned and validated.
  7. Greetings all! Crash report reads, "Logic Pro quit unexpectedly while using the StripControlPI_VST_AU Protect plug-in." The behavior occurs when clicking on or engaging tracks/buses that were previously created in a separate writing template I created for a scoring project. This project is then duplicated and used as a starting point for the various music cues. It doesn't seem to happen with new tracks I make within the duplicated template file, unless I close the session and re-open it. Basically, selecting any track that exists within a given session is fair game for a crash, though the crashing behavior is not always consistent. These tracks are almost always embedded in track stacks, and clicking the top level of the track stack can cause the issue. Doesn't matter if it's an instrument track or an audio track. One guess is that it could be related to the plugins instantiated on the template file? Perhaps a setting got corrupted? I am also using LPX Colorizer, and recently upgraded to the latest version which allows for custom coloring of the channel strips within the mixer. This never happened before the latest update. I have since deselected the custom coloring option, but the crashing behavior remains. Another possible 3rd party culprit is Speakerfood's Plug Search tool. I am using the latest version of this as well. Any ideas? It's quite frustrating, especially when you start to get in a flow state. Many thanks for your input!
  8. Temporary workaround: route the offending audio channels to busses and use the controller assignments to control the newly created Aux sends. Bit clunky but will do for now. I will be curious to hear if anyone else has seen the above mentioned behavior as well.
  9. Greetings David, how curious! I am testing it by bouncing midi regions from software instrument tracks (nested within stacks) and it's not porting over the original track's groups selections.
  10. Is there a way to bounce a track in place and have the newly created BIP track retain the same group settings as the original track?
  11. Having some more unexpected behavior - I've got all my controllers dialed in now, but the assignments set to specific audio tracks are pointing to the wrong tracks for some reason. Assignments to Aux channels and VCA groups all work fine. It seems anything assigned to an Audio track is treated similar to index mode. Logic looks at all Audio tracks from left to right (in the mixer) and bases the numbers from the order of that list. I can set the controllers to find the right tracks (ie. changing "Audio 12" to Audio 8 based on the index list) but this breaks as soon as a new audio track is added to the list. Any thoughts? Bug?
×
×
  • Create New...