Recherche avancée

Médias (0)

Mot : - Tags -/médias

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (53)

  • Les autorisations surchargées par les plugins

    27 avril 2010, par

    Mediaspip core
    autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs

  • L’utiliser, en parler, le critiquer

    10 avril 2011

    La première attitude à adopter est d’en parler, soit directement avec les personnes impliquées dans son développement, soit autour de vous pour convaincre de nouvelles personnes à l’utiliser.
    Plus la communauté sera nombreuse et plus les évolutions seront rapides ...
    Une liste de discussion est disponible pour tout échange entre utilisateurs.

  • Création définitive du canal

    12 mars 2010, par

    Lorsque votre demande est validée, vous pouvez alors procéder à la création proprement dite du canal. Chaque canal est un site à part entière placé sous votre responsabilité. Les administrateurs de la plateforme n’y ont aucun accès.
    A la validation, vous recevez un email vous invitant donc à créer votre canal.
    Pour ce faire il vous suffit de vous rendre à son adresse, dans notre exemple "http://votre_sous_domaine.mediaspip.net".
    A ce moment là un mot de passe vous est demandé, il vous suffit d’y (...)

Sur d’autres sites (11402)

  • Cannot get JACK Audio/Netjack working over LAN

    23 juin 2020, par James

    I'm trying to stream low latency audio between 2 raspberry pis. Both gstreamer and ffmpeg induce 2+ second delays for me.

    



    I've played around with Jack Audio and locally on a single pi it seems promising. I can route mic input to a speaker locally and it is almost instantaneous.

    



    However, I have been having trouble getting it to route between devices using Netjack.

    



    # ON SERVER
jackd -P70 -p16 -t2000 -dalsa -dhw:1 -p128 -n3 -r44100 -s 

# ON CLIENT
jackd -v -R -P70 -dnetone -i1 -o1 -I0 -O0  -r44100 -p128 -n3

# ON SERVER
jack_netsource -H < ip address of client >
jack_lsp # list availible connection ports

>system:capture_1
>system:playback_1
>system:playback_2
>netjack:capture_1
>netjack:capture_2
>netjack:capture_3
>netjack:playback_1
>netjack:playback_2
>netjack:playback_3

jack_connect system:capture_1 system:playback_1 # this works
jack_connect system:capture_1 netjack:playback_1 # this doesn't work :(


    



    Most of the launch options I pulled from here http://wiki.linuxaudio.org/wiki/raspberrypi#using_jack. I'll be honest I don't really know what they do.

    



    The client jackd output shows messages like

    



    Jack: data not valid
Jack: data not valid
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 6
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
netxruns... duration: 139ms
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 6
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3


    



    And the server jack_netsource output looks like

    



    current latency 114
current latency 20
current latency 27
current latency 29
current latency 48
current latency 23
current latency 33
current latency 28
current latency 41
current latency 84
current latency 44


    



    and the server jackd output looks like

    



    JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = netjack was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = netjack was not finished, state = Triggered
JackEngine::XRun: client = netjack was not finished, state = Triggered


    



    I believe the -dnetone flag indicates to use Netjack2. Netjack 1, which I've tried with the -dnet flag results in a single Not Connected message from jack_netsource and :

    



    Jack: CatchHost fd = 5 err = Resource temporarily unavailable
Jack: CatchHost fd = 5 err = Resource temporarily unavailable
Jack: CatchHost fd = 5 err = Resource temporarily unavailable
Jack: CatchHost fd = 5 err = Resource temporarily unavailable
Jack: CatchHost fd = 5 err = Resource temporarily unavailable
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 6


    



    from the client jackd.

    


  • Cannot get JACK Audio/Netjack working over LAN

    19 septembre 2016, par James

    I’m trying to stream low latency audio between 2 raspberry pis. Both gstreamer and ffmpeg induce 2+ second delays for me.

    I’ve played around with Jack Audio and locally on a single pi it seems promising. I can route mic input to a speaker locally and it is almost instantaneous.

    However, I have been having trouble getting it to route between devices using Netjack.

    # ON SERVER
    
jackd -P70 -p16 -t2000 -dalsa -dhw:1 -p128 -n3 -r44100 -s 
    

    
# ON CLIENT
    
jackd -v -R -P70 -dnetone -i1 -o1 -I0 -O0  -r44100 -p128 -n3
    

    
# ON SERVER
    
jack_netsource -H < ip address of client >
    
jack_lsp # list availible connection ports
    

    
>system:capture_1
    
>system:playback_1
    
>system:playback_2
    
>netjack:capture_1
    
>netjack:capture_2
    
>netjack:capture_3
    
>netjack:playback_1
    
>netjack:playback_2
    
>netjack:playback_3
    

    
jack_connect system:capture_1 system:playback_1 # this works
    
jack_connect system:capture_1 netjack:playback_1 # this doesn't work :(

    Most of the launch options I pulled from here http://wiki.linuxaudio.org/wiki/raspberrypi#using_jack. I’ll be honest I don’t really know what they do.

    The client jackd output shows messages like

    Jack: data not valid
    
Jack: data not valid
    
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 6
    
Jack: JackRequest::Notification
    
Jack: JackEngine::ClientNotify: no callback for notification = 3
    
Jack: JackEngine::ClientNotify: no callback for notification = 3
    
netxruns... duration: 139ms
    
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 6
    
Jack: JackRequest::Notification
    
Jack: JackEngine::ClientNotify: no callback for notification = 3
    
Jack: JackEngine::ClientNotify: no callback for notification = 3

    And the server jack_netsource output looks like

    current latency 114
    
current latency 20
    
current latency 27
    
current latency 29
    
current latency 48
    
current latency 23
    
current latency 33
    
current latency 28
    
current latency 41
    
current latency 84
    
current latency 44

    and the server jackd output looks like

    JackAudioDriver::ProcessGraphAsyncMaster: Process error
    
JackAudioDriver::ProcessGraphAsyncMaster: Process error
    
JackAudioDriver::ProcessGraphAsyncMaster: Process error
    
JackAudioDriver::ProcessGraphAsyncMaster: Process error
    
JackEngine::XRun: client = netjack was not finished, state = Triggered
    
JackAudioDriver::ProcessGraphAsyncMaster: Process error
    
JackAudioDriver::ProcessGraphAsyncMaster: Process error
    
JackEngine::XRun: client = netjack was not finished, state = Triggered
    
JackEngine::XRun: client = netjack was not finished, state = Triggered

    I believe the -dnetone flag indicates to use Netjack2. Netjack 1, which I’ve tried with the -dnet flag results in a single Not Connected message from jack_netsource and :

    Jack: CatchHost fd = 5 err = Resource temporarily unavailable
    
Jack: CatchHost fd = 5 err = Resource temporarily unavailable
    
Jack: CatchHost fd = 5 err = Resource temporarily unavailable
    
Jack: CatchHost fd = 5 err = Resource temporarily unavailable
    
Jack: CatchHost fd = 5 err = Resource temporarily unavailable
    
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 6

    from the client jackd.

  • Compile ffmpeg for armv7s

    14 août 2014, par user3929400

    I am trying to compile ffmpeg on OSX 10.9. I want to use the ffmpeg framework in an iOS testapplication using xCode.

    I want to link the libfaac to ffmpeg and compile it for armv7s. When I follow the compilation guide (https://trac.ffmpeg.org/wiki/CompilationGuide/MacOSX) on the ffmpeg site, it does not work.

    I used the following configuration :

    ./configure  --prefix=/usr/local --enable-gpl --enable-nonfree --enable-libass --enable-libfdk-aac --enable-libfreetype --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libxvid --arch=armv7s

    Another configuration I tried is

    ./configure  --prefix=/usr/local --enable-gpl --enable-nonfree --enable-libass --enable-libfdk-aac --enable-libfreetype --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libxvid --arch=armv7s --enable-cross-compile --target-os=darwin

    The difference between both configuration is the cross compile and target os.

    Both configuration produces the following error message :

    GNU assembler not found, install gas-preprocessor

    Although, I have copied gas-preprocessor.pl into the directories /usr/local/bin and /usr/bin and modified the file read-write props by using chmod +x gas-preprocessor.pl

    Can somebody help me to configure ffmpeg by giving for example an example configuration which does work ?

Navigation