Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Audio pauses introduced in ouput video file. #14

Open
gtsop opened this issue Jun 19, 2018 · 4 comments
Open

Audio pauses introduced in ouput video file. #14

gtsop opened this issue Jun 19, 2018 · 4 comments

Comments

@gtsop
Copy link

gtsop commented Jun 19, 2018

Very short audio pauses (we're talking about miliseconds) are introduced into the output file every 1-2 seconds in a 17sec rendered video.

Pulverize was set up as instructed in the README file (using the php version). The following command was used:

pulverize spot.blend 8

System info

OS     : Manjaro Linux
Kernel : 4.17
CPU    : i7-4790K
RAM    : 16GB
GPU    : Nvidia GTX 770

Blender info

Blender  : 2.79 (sub 4)
Output   : FFmpeg video | RGB
Encoding :
    Contain        : MPEG-4
    Video Coded    : H.264
    Output quality : Lowest quality
    Encoding speed : Realtime
    Audio Codec    : MP3
    Bitrate        : 192

Is there anything I can change to make this work?

@FraYoshi
Copy link

actually, the pauses occur where the split takes place. I see you have an i7. 17/8 = 2.125.

I solved this by exporting the audio separately and then joining it with FFmpeg. It is actually just a workaround.

@gtsop
Copy link
Author

gtsop commented Jun 25, 2018

actually, the pauses occur where the split takes place. I see you have an i7. 17/8 = 2.125.

Exactly my initial thoughts, but wouldn't everyone have the same problem?
Anyway, if your fix is working we could automate it by providing an extra option into the parameter JSON

@hperrin
Copy link
Member

hperrin commented Jun 26, 2018

Hmm. That's a smart workaround. Maybe pulverize should be doing that. Are you rendering audio directly from blender? And is it fast?

@hperrin
Copy link
Member

hperrin commented Jun 26, 2018

Btw, this problem only happens on certain codecs. I've never had this problem on the recommended codecs (in the readme).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants