Recherche avancée

Médias (0)

Mot : - Tags -/clipboard

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

Autres articles (48)

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

  • MediaSPIP v0.2

    21 juin 2013, par

    MediaSPIP 0.2 is the first MediaSPIP stable release.
    Its official release date is June 21, 2013 and is announced here.
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

  • Des sites réalisés avec MediaSPIP

    2 mai 2011, par

    Cette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
    Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page.

Sur d’autres sites (6520)

  • OpenCV Reporting TBR instead of FPS when using capture.get(CV_CAP_PROP_FPS)

    22 février 2012, par Malife

    I have several videos that I am trying to process using OpenCV and Qt 4.7.4 on Mac OS 10.6.8 (Snow Leopard). If I create a cv::VideoCapture object and then query for the frame rate related to such video, what I get back is the TBR and not FPS.

    For instance if use ffprobe Video1.mp4 what I get is :

    >> ffprobe Video1.mp4      
    
ffprobe version 0.7.8, Copyright (c) 2007-2011 the FFmpeg developers
    
built on Nov 24 2011 14:31:00 with gcc 4.2.1 (Apple Inc. build 5666) (dot 3)
    
configuration: --prefix=/opt/local --enable-gpl --enable-postproc --enable-swscale --   
    
enable-avfilter --enable-libmp3lame --enable-libvorbis --enable-libtheora --enable-
    
libdirac --enable-libschroedinger --enable-libopenjpeg --enable-libxvid --enable-libx264 
    
--enable-libvpx --enable-libspeex --mandir=/opt/local/share/man --enable-shared --
    
enable-pthreads --cc=/usr/bin/gcc-4.2 --arch=x86_64 --enable-yasm
    
libavutil    50. 43. 0 / 50. 43. 0
    
libavcodec   52.123. 0 / 52.123. 0
    
libavformat  52.111. 0 / 52.111. 0
    
libavdevice  52.  5. 0 / 52.  5. 0
    
libavfilter   1. 80. 0 /  1. 80. 0
    
libswscale    0. 14. 1 /  0. 14. 1
    
libpostproc  51.  2. 0 / 51.  2. 0
    

    
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'Video1.mp4':
    
Metadata:
    
major_brand     : isom
    
minor_version   : 0
    
compatible_brands: mp41avc1qt  
    
creation_time   : 2012-01-09 23:09:43
    
encoder         : vlc 1.1.3 stream output
    
encoder-eng     : vlc 1.1.3 stream output
    
Duration: 00:10:10.22, start: 0.000000, bitrate: 800 kb/s
    
Stream #0.0(eng): Video: h264 (Baseline), yuvj420p, 704x480 [PAR 10:11 DAR 4:3], 798 
    
kb/s, 27.71 fps, 1001 tbr, 1001 tbn, 2002 tbc
    
Metadata:
    
  creation_time   : 2012-01-09 23:09:43

    Which correctly reports FPS = 27.71 and TBR = 1001. Nevertheless if I use the following OpenCV code to query for the FPS :

    QString filename = QFileDialog::getOpenFileName(this,
    
                                        "Open Video",
    
                                        "Video Files (*.mp4, *.mpg)");
    

    
capture.release();
    
capture.open(filename.toAscii().data());
    

    
if (!capture.isOpened()){
    
    qDebug() <<"Error when opening the video!";
    
    return;
    
}
    

    

    
qDebug() << "Frame Rate:" << capture.get(CV_CAP_PROP_FPS);
    
qDebug() << "Num of Frames:" << capture.get(CV_CAP_PROP_FRAME_COUNT);
    
qDebug() << "OpenCV Version" << CV_VERSION;

    The output I get is :

    Frame Rate: 1001 
    
Num of Frames: 610832 
    
OpenCV Version 2.3.1

    Which reports the TBR instead of the FPS. This behavior is consistent when I try to open different videos.

    I checked OpenCV's bug tracker and I also found this stack overflow question to be a similar but not quite the same problem, so I am at a loss to what to do next. Any hint or idea is most welcome since I've tried lots of things and seem to be getting nowhere.

  • How to record audio in android ?

    28 mars 2012, par newentry

    I am doing a loopback test in android, which record's audio using AudioRecorder then encode the uncompressed pcm into speex after that i decode speex back to pcm and given to AudioPlayer for playing .Later case i will test between two devices P2P . I am trying to record audio , similar to call recording in which save both sender and receiver voide into a single file mp4 format .Can anybody suggest me a good direction to proceed and also is it possible to achieve this through ffmpeg ported for android ?

    thanks,

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

Navigation