Jump to content

ELP71

Member
  • Posts

    26
  • Joined

  • Last visited

ELP71's Achievements

Newbie

Newbie (1/14)

  • Week One Done
  • One Month Later Rare
  • One Year In Rare

Recent Badges

0

Reputation

  1. My guess is the ‘other application’ is Logic.
  2. Yes. I just proceeded with ‘save anyway’. Your results may vary. Hope they addrsss this soon.
  3. Can verify occurrences of this issue as well...it's a nasty one...seems pretty unpredictable and inconsistent. Vicious bug.Can't pull up a crash report because I have to force quit. Haven't experienced the corrupting of sessions I've read about in other threads (fingers crossed). Very weird issue indeed.
  4. I've bounced this question (or a version of it) around a couple times in various forums, etc. It's a noticeable "feature" of Logic, but I think it also has to do with how the OS "handles" RAM usage and how 3rd party software does the same. It's a bummer, especially w/projects that use dozens of streaming-library samples that load a bit of the sample into RAM for 'efficiency' - PLAY comes to mind specifically - but like David says it doesn't hurt workflow too badly to just do the occasional restart.
  5. I'm hearing generally good reports...but like others here I didn't suffer from the issue *fingers crossed* so who knows! I've got a massive project to get through before I go updating anything. Already accidentally "broke" my install of Speakerphone trying to move a couple things around Maybe a by-product will be a resolution of my annoying playhead/visual "issue".
  6. That is an empty region with meta events for stop playback and go to marker. The metronome behaves similarly with no regions in the arrange - I put that meta event in there to replicate a typical performance session I use. Ill try to post a video as requested.
  7. Here's a link to a video of the strange issue on my system: http://youtu.be/Uvt8rxX2Gcw Also tried this w/out the audio interface using Core Audio and internal speaker (Mac Pro) - same behavior. Anyway - there it is!
  8. Thanks. Well I thought they might be related. The OP issue sounded similar (in my opinion) to what I was experiencing. I'll post a video of the phenomenon - probably won't amount to a hill of beans but at least there'll be a visual representation.
  9. Current show up and running - finally a few moments to upload these test projects! These are "empty" versions of live performance sessions I use in theatrical performances on a daily basis. The "buggy" aspect of these Logic sessions behave the same empty or full of audio/plugins/VIs. Both projects have: - two software instrument tracks, one empty, one containing one "empty" MIDI region w/two meta events (stop playback & go to marker 2) - two markers - tempo of 120bpm - created in SL 10.6.8 The project titled "Test" was created in Logic 8, and works as expected. Metronome stops when stop is pressed (either space bar or onscreen in the transport). Markers and meta data behave accordingly. The project titled "Test LP9" was the original "Test" project opened w/Logic 9.1.8 and re-saved/renamed. TO make certain the projects behaved in the same manner I re-created it from scratch in Logic 9.1.8, but it behaved just like the renamed file. Anyway the symptoms are: - metronome has one or two audible "clicks" after stop is pressed (either space bar or onscreen in the transport). - meta commands seem to work now HOWEVER there are audible metronome clicks after the playhead has "stopped" and moved to the next marker. Final comment - FWIW our audio guy opened a similar Logic 9.1.7 session in Mountian Lion and experienced the same issue - upgraded to 9.1.8 and the issue was gone. I'm hoping I have some checkbox unticked! Thanks SFB Test.zip Created in Logic 8 - behaves as expected TestLP9.zip Created in Logic 9.1.8 - does not behave as expected
  10. Sorry bout that - I edited the sig info ages ago but didn't have the default sig display enabled. Appreciate the suggestion, I will do that but I've been responding on mobile (in the middle of a huge project at the moment)
  11. Just an FYI on my observation of the phenomenon - every paramenter mentioned so far (buffer, low latency mode, etc) has been sussed out on my system. Opened empty session in v.8 - no issue. Opened 'offending' v.9 session in v.8 - no issue.
  12. I've experimented in an empty project and experienced the same bug
  13. I've noticed this too. This 'condition' I can't help but think is related to my current inability to use meta commands to any usable extent (stop playback and go to marker). I've posted about it in a couple other spots but it seems like a bug that wouldn't necessarily affect most users. In my system, the metronome keeps clicking for couple beats after I stop it, although the transport 'stops'. It just imprecise.
×
×
  • Create New...