Recherche avancée

Médias (91)

Autres articles (58)

  • D’autres logiciels intéressants

    12 avril 2011, par

    On ne revendique pas d’être les seuls à faire ce que l’on fait ... et on ne revendique surtout pas d’être les meilleurs non plus ... Ce que l’on fait, on essaie juste de le faire bien, et de mieux en mieux...
    La liste suivante correspond à des logiciels qui tendent peu ou prou à faire comme MediaSPIP ou que MediaSPIP tente peu ou prou à faire pareil, peu importe ...
    On ne les connais pas, on ne les a pas essayé, mais vous pouvez peut être y jeter un coup d’oeil.
    Videopress
    Site Internet : (...)

  • 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

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-je poster des contenus à partir d’une tablette Ipad ?
    Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir

Sur d’autres sites (9478)

  • aacenc : coding style changes

    21 août 2015, par Rostislav Pehlivanov
    aacenc : coding style changes
    

    This commit only changes the coding style to a saner way
    of accessing coefficients (makes more sense to get the
    memory address of a coefficients and start from there
    rather than adding arbitrary numbers to offset a pointer).
    Some compilers might detect an out of bounds access easier.

    Also the way M/S and IS coefficients are calculated has been
    changed, but should still have the same result (with the exception
    that IS now applies from the normal coefficients rather than the
    pristine ones, this is needed for upcoming commits).

    Signed-off-by : Rostislav Pehlivanov <atomnuker@gmail.com>

    • [DH] libavcodec/aaccoder.c
    • [DH] libavcodec/aacenc.c
  • Returned non-zero exit status 1 / error code 1 : b''

    26 août 2015, par pufAmuf

    I’m trying to extract the video height via ffprobe into python, however I am having issues (with some videos).

    Here is my ffprobe command : ffprobe -v quiet -print_format compact=print_section=0:nokey=1:escape=csv -show_entries stream=height "some video here(bla)_25.mp4"

    It returns something like this

    720
    (empty-line)
    N/A

    Here is the code I used to extract the output for later processing :

    executecommand = 'ffprobe -v quiet -print_format compact=print_section=0:nokey=1:escape=csv -show_entries stream=height "' + CurrentVideoToBeProcessed + '"'

    VideoHeight = subprocess.check_output(executecommand)

    This is the error that came about :

    subprocess.CalledProcessError : Command ’...’ returned non-zero exit
    status 1

    So when I modified the code to this :

    try:
       VideoHeight = subprocess.check_output(executecommand,shell=True,stderr=subprocess.STDOUT)
    except subprocess.CalledProcessError as e:
       raise RuntimeError("command '{}' return with error (code {}): {}".format(e.cmd, e.returncode, e.output))

    This is the error I get :

    RuntimeError : command ’...’ return with error (code 1) : b’’

    I assumed at first the issue was with the file names, but certain videos work and certain don’t, irregardless of the file name.
    This is the output I get in python for videos that work :

    b’360\r\n\r\n’

    Any idea what’s going on ? Thanks !

    Edit
    It turns out the problem is in the file names after all. From what I gather so far at least, numbers in file-names seem to be causing the error.
    Edit2
    I re-ran the code after I closed several cmd instances and I am not getting the error anymore. I don’t know why. I am sure, however that if I were to convert hundreds of videos again I’ll get the error eventually as it has always happened eventually.

  • How to keep personally identifiable information safe

    23 janvier 2020, par Joselyn Khor

    The protection of personally identifiable information (PII) is important both for individuals, whose privacy may be compromised, and for businesses that may have their reputation ruined or be liable if PII is wrongly accessed, used, or shared.

    Curious about what PII is ? Here’s your introduction to personally identifiable information.

    Due to hacking, data leaks or data thievery, PII acquired can be combined with other pieces of information to form a more complete picture of you. On an individual level, this puts you at risk of identity theft, credit card theft or other harm caused by the fraudulent use of your personal information.

    On a business level, for companies who breach data privacy laws – like Cambridge Analytica’s harvesting of millions of FB profiles – the action leads to an erosion of trust. It can also impact your financial position as heavy fines can be imposed for the illegal use and processing of personally identifiable information.

    So what can you do to ensure PII compliance ?

    On an individual level :

    1. Don’t give your data away so easily. Although long, it’s worthwhile to read through privacy policies to make sure you know what you’re getting yourself into.
    2. Don’t just click ‘agree’ when faced with consent screens, as consent screens are majorly flawed. Users mostly always opt in without reading and without being properly informed what they opt in to.
    3. Did you know you’re most likely being tracked from website to website ? For example, Google can identify you across visits and websites. One of the things you can do is to disable third party cookies by default. Businesses can also use privacy friendly analytics which halt such tracking. 
    4. Use strong passwords.
    5. Be wary of public wifi – hackers can easily access your PII or sensitive data. Use a VPN (virtual private network), which lets you create a secure connection to a server of your choosing. This allows you to browse the internet in a safe manner.

    A PII compliance checklist for businesses/organisations :

    1. Identify where all PII exists and is stored – review and make sure this is in a safe environment.
    2. Identify laws that apply to you (GDPR, California privacy law, HIPAA) and follow your legal obligations.
    3. Create operational safeguards – policies and procedures for handling PII at an organisation level ; and building awareness to focus on the protection of PII.
    4. Encrypt databases and repositories where such info is kept.
    5. Create privacy-specific safeguards in the way your organisation collects, maintains, uses, and disseminates data so you protect the confidentiality of the data.
    6. Minimise the use, collection, and retention of PII – only collect and keep PII if it’s necessary for you to perform your legal business function.
    7. Conduct privacy impact assessments (PIA) to find and prevent privacy risks (identify what and why it’s to be collected ; how the information will be secured etc.).
    8. De-identify within the scope of your data collection and analytics tools.
    9. Anonymise data.
    10. Keep your privacy policy updated.
    11. Pseudonymisation.
    12. A more comprehensive guide for businesses can be found here : https://iapp.org/media/pdf/knowledge_center/NIST_Protecting_PII.pdf