Recherche avancée

Médias (0)

Mot : - Tags -/protocoles

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

Autres articles (54)

  • 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

  • Support audio et vidéo HTML5

    10 avril 2011

    MediaSPIP utilise les balises HTML5 video et audio pour la lecture de documents multimedia en profitant des dernières innovations du W3C supportées par les navigateurs modernes.
    Pour les navigateurs plus anciens, le lecteur flash Flowplayer est utilisé.
    Le lecteur HTML5 utilisé a été spécifiquement créé pour MediaSPIP : il est complètement modifiable graphiquement pour correspondre à un thème choisi.
    Ces technologies permettent de distribuer vidéo et son à la fois sur des ordinateurs conventionnels (...)

  • HTML5 audio and video support

    13 avril 2011, par

    MediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
    The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
    For older browsers the Flowplayer flash fallback is used.
    MediaSPIP allows for media playback on major mobile platforms with the above (...)

Sur d’autres sites (6450)

  • 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.

  • Revision 62042 : Premier gros commit... Les doc2img passent en documents de SPIP, plus ...

    3 juin 2012, par kent1@… — Log

    Premier gros commit...
    Les doc2img passent en documents de SPIP, plus de table dédiée mais un mode de document différent

  • Revision 37686 : Un premier essai (absolument pas parfait) pour ne pas planter l’ajax ...

    26 avril 2010, par kent1@… — Log

    Un premier essai (absolument pas parfait) pour ne pas planter l’ajax sur le formulaire d’installation lorsque les plugins ont des fonctions d’installation

Navigation