Recherche avancée

Médias (0)

Mot : - Tags -/upload

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

Autres articles (104)

  • XMP PHP

    13 mai 2011, par

    Dixit Wikipedia, XMP signifie :
    Extensible Metadata Platform ou XMP est un format de métadonnées basé sur XML utilisé dans les applications PDF, de photographie et de graphisme. Il a été lancé par Adobe Systems en avril 2001 en étant intégré à la version 5.0 d’Adobe Acrobat.
    Étant basé sur XML, il gère un ensemble de tags dynamiques pour l’utilisation dans le cadre du Web sémantique.
    XMP permet d’enregistrer sous forme d’un document XML des informations relatives à un fichier : titre, auteur, historique (...)

  • Use, discuss, criticize

    13 avril 2011, par

    Talk to people directly involved in MediaSPIP’s development, or to people around you who could use MediaSPIP to share, enhance or develop their creative projects.
    The bigger the community, the more MediaSPIP’s potential will be explored and the faster the software will evolve.
    A discussion list is available for all exchanges between users.

  • Installation en mode ferme

    4 février 2011, par

    Le mode ferme permet d’héberger plusieurs sites de type MediaSPIP en n’installant qu’une seule fois son noyau fonctionnel.
    C’est la méthode que nous utilisons sur cette même plateforme.
    L’utilisation en mode ferme nécessite de connaïtre un peu le mécanisme de SPIP contrairement à la version standalone qui ne nécessite pas réellement de connaissances spécifique puisque l’espace privé habituel de SPIP n’est plus utilisé.
    Dans un premier temps, vous devez avoir installé les mêmes fichiers que l’installation (...)

Sur d’autres sites (7778)

  • lavfi : properly signal out-of-memory error in ff_filter_samples

    4 août 2012, par Reinhard Tartler

    lavfi : properly signal out-of-memory error in ff_filter_samples

  • azap from LinuxTV dvb-apps strange signal behavior with Hauppauge WinTV-HVR 950Q [migrated]

    27 février 2012, par mmoment

    What I want to do

    I have a Hauppauge WinTV-HVR 950Q USB-TV-Stick. I want to use this stick to successively tune to and read in a certain live TV stream.

    What I do

    I trigger a scan and save the scan results in a file. I call it channels.conf, like the v4l documentary proposes.

    scan /home/username/Documents/dvb/atsc/us-CA-SF-Bay-Area > /home/username/Documents/dvb/atsc/conf/home_channels.conf

    Everything works fine, the scan returns something like this(A correct channel file) :

    [0003]:503000000:8VSB:49:52:3
    
[0005]:503000000:8VSB:81:84:5
    
[0006]:503000000:8VSB:97:100:6
    
26 San Francisco, CA:551000000:8VSB:49:52:3
    
26 San Francisco, CA:551000000:8VSB:65:68:4
    
KTSF-D3:551000000:8VSB:81:84:5
    
KTSF-D4:551000000:8VSB:97:100:6
    
KTSF-D5:551000000:8VSB:113:116:7
    
KTSF-D6:551000000:8VSB:129:132:8
    
KPIX-DT:563000000:8VSB:49:52:1
    
KKPX ION:635000000:8VSB:49:52:3
    
KKPX qubo:635000000:8VSB:65:68:4
    
IONLife:635000000:8VSB:81:84:5
    
100:635000000:8VSB:487:488:100
    
200:635000000:8VSB:417:418:200
    
201:635000000:8VSB:422:423:201
    
202:635000000:8VSB:427:428:202
    
203:635000000:8VSB:432:433:203
    
204:635000000:8VSB:412:413:204
    
300:635000000:8VSB:442:443:300
    
400:635000000:8VSB:457:458:400
    
KSTS-HD:683000000:8VSB:49:52:3
    
Telemundo Exitos TV:683000000:8VSB:65:68:4
    
CNL-SOI:683000000:8VSB:81:84:5
    
KQEH:689000000:8VSB:49:52:1
    
KQED:689000000:8VSB:65:68:2
    
LIFE:689000000:8VSB:81:84:3
    
KIDS:689000000:8VSB:97:100:4
    
V-me:689000000:8VSB:113:116:5

    Then I tune to a channel from the scan results. KIDS for example :

    azap -r -c Documents/dvb/atsc/conf/channels.conf KIDS

    What I expect the program to do :

    I expect the program to be tuned and to deliver results similar to this :

    username@username:~$ azap -r -c Documents/dvb/atsc/conf/channels.conf KIDS
    
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
    
tuning to 689000000 Hz
    
video pid 0x0061, audio pid 0x0064
    

    
status 1f | signal 00e6 | snr 00e6 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
    
status 1f | signal 00e6 | snr 00e6 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
    
status 1f | signal 00e6 | snr 00e6 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
    
status 1f | signal 00dc | snr 00e6 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
    
status 1f | signal 00e6 | snr 00e6 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
    
status 1f | signal 00e6 | snr 00e6 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
    
...

    What it does :

    In 2 out of 5 tries the azap just doesn't work at all.

    username@username:~$ azap -r -c Documents/dvb/atsc/conf/channels.conf KIDS
    
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
    
tuning to 689000000 Hz
    
video pid 0x0061, audio pid 0x0064
    

    
status 00 | signal 0000 | snr 00e6 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
    
status 00 | signal 0000 | snr 00e4 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
    
status 00 | signal 0000 | snr 00e6 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
    
status 00 | signal 0000 | snr 00c2 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
    
status 00 | signal 0000 | snr 00e6 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
    
...

    The rest of the time it generally works initially, then switches the status to 00 and can not be used any more, even if there is incoming signal.

    status 1f | signal 00dc | snr 00dc | ber 00000000 | unc 00000000 | FE_HAS_LOCK
    
status 1f | signal 00d2 | snr 00dc | ber 00000000 | unc 00000000 | FE_HAS_LOCK
    
status 1f | signal 00dc | snr 00dc | ber 00000000 | unc 00000000 | FE_HAS_LOCK
    
status 1f | signal 00dc | snr 00dc | ber 00000000 | unc 00000000 | FE_HAS_LOCK
    
status 1f | signal 00d2 | snr 00d2 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
    
status 1f | signal 00c8 | snr 00d2 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
    
status 1f | signal 00d2 | snr 00d2 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
    
status 00 | signal 00d2 | snr 00d2 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
    
status 00 | signal 00d2 | snr 00d2 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
    
status 00 | signal 00d2 | snr 00d2 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
    
status 00 | signal 00dc | snr 00dc | ber 00000000 | unc 00000000 | FE_HAS_LOCK
    
status 00 | signal 00e6 | snr 00e6 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
    
status 00 | signal 00dc | snr 00dc | ber 00000000 | unc 00000000 | FE_HAS_LOCK
    
status 00 | signal 00e6 | snr 00e6 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
    
status 00 | signal 00e6 | snr 00e6 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
    
status 00 | signal 00e6 | snr 00dc | ber 00000000 | unc 00000000 | FE_HAS_LOCK
    
...

    The output even shows that there is high signal to noise ratio, low or rather no block errors or uncorrected errors at all at first, then it
    This keeps me wondering since I see no reason for the program to switch. After double checking with a real TV I am very sure that I always have an incoming signal and that there should not be any reasons for a behavior like this.

    Question

    Can any of you guys see a reason for this behavior, could it be a problem with the Hardware that I'm using or rather a Software issue ? Did anybody experience the same issues, how did you fix it ? Any help is greatly appreciated !

  • Process terminates by signal calling ffmpeg part in Android NDK project

    29 août 2013, par Álvaro

    According to this blog post I've build my Android ffmpeg project. I've written the native code from my Java code with the static library and the jni functions.
    When I run this part of code I obtain the next logcat, any idea of why my process terminates by signal ?

    03-14 11:16:06.488: I/DEBUG(31): *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
    03-14 11:16:06.488: I/DEBUG(31): Build fingerprint: generic/google_sdk/generic:2.3.4/GINGERBREAD/123630:eng/test-keys'
    03-14 11:16:06.488: I/DEBUG(31): pid: 377, tid: 377  >>> com.testffmpeg <<<
    03-14 11:16:06.488: I/DEBUG(31): signal 4 (SIGILL), code 1 (ILL_ILLOPC), fault addr 80a98f10
    03-14 11:16:06.488: I/DEBUG(31):  r0 002b0030  r1 80b1c410  r2 00030d40  r3 00000000
    03-14 11:16:06.488: I/DEBUG(31):  r4 00000000  r5 002b0030  r6 00000010  r7 00000010
    03-14 11:16:06.488: I/DEBUG(31):  r8 be877308  r9 7fffffff  10 80b1bea0  fp 00000000
    03-14 11:16:06.488: I/DEBUG(31):  ip be8772f0  sp be8772d0  lr 80a99d64  pc 80a98f10  cpsr 60000010
    03-14 11:16:06.568: I/DEBUG(31):          #00  pc 00298f10  /data/data/com.testffmpeg/lib/libffmpeg.so
    03-14 11:16:06.568: I/DEBUG(31):          #01  lr 80a99d64  /data/data/com.testffmpeg/lib/libffmpeg.so
    03-14 11:16:06.568: I/DEBUG(31): code around pc:
    03-14 11:16:06.568: I/DEBUG(31): 80a98ef0 eaffff9e 0009304c fffeffe4 e92d4010
    03-14 11:16:06.568: I/DEBUG(31): 80a98f00 e24dd020 e28dc020 e3a04000 e1cd20f8
    03-14 11:16:06.568: I/DEBUG(31): 80a98f10 e3003000 e52c4004 e3a02000 e3433ff0
    03-14 11:16:06.568: I/DEBUG(31): 80a98f20 e58dc010 e3a0c001 e58dc000 ebffff77
    03-14 11:16:06.568: I/DEBUG(31): 80a98f30 e1500004 b1a00004 a59d001c e28dd020
    03-14 11:16:06.568: I/DEBUG(31): code around lr:
    03-14 11:16:06.568: I/DEBUG(31): 80a99d44 ed947b04 e1a00005 e5941000 eefd7bc7
    03-14 11:16:06.568: I/DEBUG(31): 80a99d54 ee17ca90 e1a0200c e1a03fc2 ebfffc65
    03-14 11:16:06.568: I/DEBUG(31): 80a99d64 eaffffb8 e1c421d0 e1a00008 e58d9000
    03-14 11:16:06.568: I/DEBUG(31): 80a99d74 eb0008cc e1a00005 e5941000 e898000c
    03-14 11:16:06.568: I/DEBUG(31): 80a99d84 ebfffc6e eaffffaf e1a00005 e3a01030
    03-14 11:16:06.568: I/DEBUG(31): stack:
    03-14 11:16:06.568: I/DEBUG(31):     be877290  001f9a98  [heap]
    03-14 11:16:06.568: I/DEBUG(31):     be877294  0008ced8  [heap]
    03-14 11:16:06.568: I/DEBUG(31):     be877298  00000005<br />
    03-14 11:16:06.578: I/DEBUG(31):     be87729c  a8114ca9  /system/lib/libutils.so
    03-14 11:16:06.578: I/DEBUG(31):     be8772a0  001f9a48  [heap]
    03-14 11:16:06.578: I/DEBUG(31):     be8772a4  be8772cc<br />
    03-14 11:16:06.578: I/DEBUG(31):     be8772a8  fffffffc<br />
    03-14 11:16:06.578: I/DEBUG(31):     be8772ac  00000000<br />
    03-14 11:16:06.578: I/DEBUG(31):     be8772b0  be8772cc<br />
    03-14 11:16:06.578: I/DEBUG(31):     be8772b4  a821a33d  /system/lib/libbinder.so
    03-14 11:16:06.578: I/DEBUG(31):     be8772b8  00271270  [heap]
    03-14 11:16:06.578: I/DEBUG(31):     be8772bc  a821a9d5  /system/lib/libbinder.so
    03-14 11:16:06.578: I/DEBUG(31):     be8772c0  00000030<br />
    03-14 11:16:06.578: I/DEBUG(31):     be8772c4  00000000<br />
    03-14 11:16:06.578: I/DEBUG(31):     be8772c8  df002777<br />
    03-14 11:16:06.578: I/DEBUG(31):     be8772cc  e3a070ad<br />
    03-14 11:16:06.578: I/DEBUG(31): #00 be8772d0  00000000<br />
    03-14 11:16:06.578: I/DEBUG(31):     be8772d4  afd10f08  /system/lib/libc.so
    03-14 11:16:06.578: I/DEBUG(31):     be8772d8  00030d40  [heap]
    03-14 11:16:06.578: I/DEBUG(31):     be8772dc  00000000<br />
    03-14 11:16:06.578: I/DEBUG(31):     be8772e0  000000da<br />
    03-14 11:16:06.578: I/DEBUG(31):     be8772e4  00000008<br />
    03-14 11:16:06.578: I/DEBUG(31):     be8772e8  000001b4<br />
    03-14 11:16:06.578: I/DEBUG(31):     be8772ec  c0000000<br />
    03-14 11:16:06.578: I/DEBUG(31):     be8772f0  80b24938  /data/data/com.testffmpeg/lib/libffmpeg.so
    03-14 11:16:06.578: I/DEBUG(31):     be8772f4  80a99d64  /data/data/com.testffmpeg/lib/libffmpeg.so
    03-14 11:16:06.578: I/DEBUG(31):     be8772f8  00000000<br />
    03-14 11:16:06.578: I/DEBUG(31):     be8772fc  afd1386d  /system/lib/libc.so
    03-14 11:16:06.578: I/DEBUG(31):     be877300  00000000<br />
    03-14 11:16:06.578: I/DEBUG(31):     be877304  80b1be7c  /data/data/com.testffmpeg/lib/libffmpeg.so
    03-14 11:16:06.578: I/DEBUG(31):     be877308  002b0028  [heap]
    03-14 11:16:06.578: I/DEBUG(31):     be87730c  00000000<br />
    03-14 11:16:06.578: I/DEBUG(31):     be877310  00000003<br />
    03-14 11:16:06.578: I/DEBUG(31):     be877314  00000000<br />
    03-14 11:16:07.118: D/Zygote(33): Process 377 terminated by signal (4)

Navigation