Page MenuHome
Create Task
Maniphest T45650

Audio playback position not reset after Alt+A, ESC
Closed, ArchivedPublic
Actions

Description

System Information
Win7/64, GTX 750 Ti

Blender Version
2.75a (official)
Can't say about latest build Blender-2.75.0-git.d894fcb-AMD64 as it crashes during testing.

Short description of error
In the given situation, the audio playback position is not reset by pressing ESC when playing back using Alt+A.

Exact steps for others to reproduce the error

  1. Add two MP4 Videos (here: H.264 + AAC) to the VSE
  2. First video starts at frame 0, second at frame 660.
  3. Set current frame = 660
  4. Press Alt+A -> playback starts, play few seconds, press ESC
  5. Problem: If you press Alt+A again, audio playback should start at frame 660 again, but it does not.

Related Objects

Event Timeline

Willi (willi) created this task.Aug 1 2015, 10:36 PM
Willi (willi) raised the priority of this task from to 90.
Willi (willi) updated the task description. (Show Details)
Willi (willi) added projects: BF Blender, Video Sequencer.
Willi (willi) edited a custom field.
Willi (willi) added a subscriber: Willi (willi).
Willi (willi) added a comment.EditedAug 1 2015, 11:23 PM

Tested back to Blender 2.57b. All versions have that problem.

I've just toggled the console, and it says
"AL lib: (EE) UpdateDeviceParams: Failed to set 44100hz, got 48000hz instead"
and during playback "seeking failed!". EDIT: This message is output whenever Alt+A is pressed, not when ESC is pressed.

I've switched to SDL, 48 kHz, 16 bits signed. The original problem is still there. Audio position is not reset. Well, I didn't expect a low level change would solve this kind of problem that seems to be a simple application level positioning issue.

Julian Eisel (Severin) lowered the priority of this task from 90 to 30.Aug 2 2015, 12:27 AM
Julian Eisel (Severin) added a subscriber: Julian Eisel (Severin).

Fixed a bug here which caused the crash (rB2ec0d53034aff), chances are that this also fixed the audio bug. Could you test again tomorrow with latest buildbot build when the builds from today are up?

Btw, the AL lib error is just a warning, it appears on many machines but is nothing really bad.

Julian Eisel (Severin) added a comment.Aug 2 2015, 1:04 AM

Oh, you should've reported the crash too, reproducible crashes in common scenarios should always be fixed asap.

Julian Eisel (Severin) changed the task status from Unknown Status to Unknown Status.Aug 9 2015, 5:45 PM
Julian Eisel (Severin) claimed this task.

No answer for one week -> closed! Sorry, but we have to be very strict in order to keep our bug tracker organized. We can consider reopening after we've got the requested information.