Bug 14037 - avidemux not compiled with libsamplerate support
Summary: avidemux not compiled with libsamplerate support
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal minor
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-02 20:22 CEST by Johnny Accot
Modified: 2014-09-03 00:41 CEST (History)
1 user (show)

See Also:
Source RPM: avidemux-2.6.8-3.mga5.tainted.src.rpm
CVE:
Status comment:


Attachments

Description Johnny Accot 2014-09-02 20:22:09 CEST
Description of problem:

In the current configuration, if one chooses the jack audio server as the audio output in avidemux, the audio track of a movie cannot be played at all unless the audio sample rate matches exactly the sample rate of the jack server.  The application log says this can be fixed by compiling avidemux with libsamplerate support.  I suggest adding that compiling option to the avidemux source package.

Version-Release number of selected component (if applicable):


How reproducible:
Always (as soon as the server and movie sample rates are different)

Steps to Reproduce:
1. Start an instance of jackd with a 48kHz sample rate
2. Enable jack output in avidemux and load a movie with, e.g., a 44.1kHz sample rate
3. Try to play the movie and see in the log:

DeviceStopped -> DeviceStopped
[JACK] audio stream sample rate: 44100
[JACK] jack server sample rate: 48000
[JACK] For play this, you need avidemux compiled with libsamplerate support
[JACK] Stop
 [stop]  [audioDevice]Stopping device... DeviceStopped -> DeviceStopped


Reproducible: 

Steps to Reproduce:
Comment 1 David Walser 2014-09-03 00:41:17 CEST
Thanks for the report.  Given the number of things that already depend on libsamplerate, there's really no reason not to build this with support for it.

Fixed in avidemux-2.6.8-4.mga5 (building now).

Status: NEW => RESOLVED
CC: (none) => luigiwalser
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.