This discussion is locked
SusNuts

Q: Waveburner editing sluggish

I master my clients projects in Logic and bounce out the mastered file as a whole album in one file ready to go to Waveburner to compile as a cd. When I cut up and top and tail the individual tracks from the imported file I find the track start and end editing extremely sluggish and very delayed as to what my cursor is doing. The spinning wheel comes up and I wait when I'm doing what you'd think would be the most basic editing. When you edit the start and end points of an audio region in Logic it's completely responsive to your mouse cursor. Why in Waveburner would this seemingly simple editing have such a sluggish and delayed response. I find it increasingly annoying and pretty much unusable. I have an older generation Macbook 2.2gHz intel running 10.6.4 and it's exactly the same (sluggish).
Also I find the scrolling in Waveburner with both the magic / mighty mouse way too fast and if your finger moves up or down while you're scrolling, your zoom changes... annoying you can't turn this off.

Anybody else have these problems? I'm running a completely up to date OS and Waveburner software.

Just to clarify this happens on my Imac 27" i7 8GB and my 2.2 gHz 4GB macbook both running 10.6.4

Imac i7, Mac OS X (10.6.4), 8GB Ram

Posted on Oct 5, 2010 2:00 AM

Close

Q: Waveburner editing sluggish

  • All replies
  • Helpful answers

  • by vikst,

    vikst vikst Oct 6, 2010 1:00 AM in response to SusNuts
    Level 1 (0 points)
    Oct 6, 2010 1:00 AM in response to SusNuts
    Absolutely same thing here.
    All the basic editing and volume curve movements take 15-20 seconds with the pizza wheel of death.
    I work for Metropolia Music University in Helsinki. We updated all computers to SL, Logic 9.1.1 and WB 1.6.1 in the beginning of this semester. I run a music mastering course and we´ve been using WB to practice CD assembly and editing techniques. We´re all Mac here and everything´s been running smoothly so far (with WB 1.5.2). This latest "update" has been a disaster, at the moment I can´t use WB for teaching.
    Quick 1.6.2 (preferably 1.7....) update would be appreciated. Thanks!
  • by vikst,

    vikst vikst Oct 12, 2010 3:28 AM in response to vikst
    Level 1 (0 points)
    Oct 12, 2010 3:28 AM in response to vikst
    I trashed all Waveburner and Logic prefs, including LSSsharedFile ones.

    All the basic functions are back to normal.
  • by Miles Fender,

    Miles Fender Miles Fender Oct 19, 2010 7:20 AM in response to vikst
    Level 3 (780 points)
    Oct 19, 2010 7:20 AM in response to vikst
    I tried trashing prefs but it didn't help me.

    I may have to put WaveBurner in the "completely unusable" category at this point. It performs reasonably until I try to put a plugin (any plugin) on a region, at which point performance takes a dive and any operation results in the spinning wheel of death:

    - starting and stopping takes 5-10 seconds
    - editing fades or trimming takes 10+ seconds

    Attempting either of the above during playback results in an unrecoverable lock-up.

    Additionally, I get random pops and glitches during playback; they don't transfer when burning so I've learned to ignore them, but it's very distracting.

    Logic performs beautifully on my system though - no problems at all.

    Since no-one else seems to be reporting quite such awful WaveBurner issues, I'm inclined to think it's just me, or that no-one is using this thing. I'm hopeful there's some setting or something I can tweak to make it work... anyone else seen this sort of thing and been able to resolve it? I don't think I have the patience to do another master like this, and I have deadlines so may otherwise have to find an alternative.
  • by vikst,

    vikst vikst Oct 22, 2010 3:02 AM in response to Miles Fender
    Level 1 (0 points)
    Oct 22, 2010 3:02 AM in response to Miles Fender
    Trashing prefs helped but now the pizza wheel of death is back. Very annoying
  • by vikst,

    vikst vikst Nov 15, 2010 5:07 AM in response to vikst
    Level 1 (0 points)
    Nov 15, 2010 5:07 AM in response to vikst
    Things seem to be fixed in the latest updates (ProKit or Logic). Works fine again. Thanks, Apple!