AspectHD faulty playback quirk?
 

Hey,
Just an odd tidbit that's been annoying the heck out of me as I've been editing--

it seems that sometimes when I press spacebar to start to playback my edited footage, it won't play. The "play" turns to the "stop" icon as it should, but nothing happens. I've learned to press the spacebar twice in rapid succession after that initial pause to get it to play, but this is very bothersome. Sometimes it won't play at all and I have to move the play line (i guess that's what one would call it?) over another clip in the timeline before it will play.

In addition, the audio jumps slightly a second or two into playback. "Go put that bu-bucket over there" type of jump. This happens every time. It's bothersome because when I'm editing the soundtrack I have to rewind the footage to a good distance before what I'm listening to so the jump doesn't occur on it.

Anyone else had these issues and can comment?

Spacebar thing isn't normal, but it was an older fault so we will look it see if it is back for any reason. Audio startup varies from computer to computer, as Premiere is slaving audio to our video playback, when often it is the other way around.

I very seldom get that sort of false-start playback (although I do get it). I tend to blame Premiere as one of the short list of flaky behaviours it regularly exhibits (for me).

I do get the audio glitch you're talking about on playback, every time. And yeah, it's sort of irritating, but I've gotten into the habit of just giving it a few seconds of run-up in order for both audio and video to settle down.

Audio glitch
 

I get the same audio glitch, like someone above said, bu-bucket. It's every time, but I've learned to give it a bit of pre-roll and no prob. It would be a good bug fix though.

Tip

Just updated to the new version and I'm observing the same lack of playback from the spacebar.

I experienced the same. I solved it on my system to also remove the premiere presets and playback decoder while the unstaller asks a yes or no confirmation.
After removing it, and installing the latest build the problem was gone.