
Recherche avancée
Médias (1)
-
1 000 000 (wav version)
26 septembre 2011, par
Mis à jour : Avril 2013
Langue : English
Type : Audio
Autres articles (88)
-
Taille des images et des logos définissables
9 février 2011, parDans beaucoup d’endroits du site, logos et images sont redimensionnées pour correspondre aux emplacements définis par les thèmes. L’ensemble des ces tailles pouvant changer d’un thème à un autre peuvent être définies directement dans le thème et éviter ainsi à l’utilisateur de devoir les configurer manuellement après avoir changé l’apparence de son site.
Ces tailles d’images sont également disponibles dans la configuration spécifique de MediaSPIP Core. La taille maximale du logo du site en pixels, on permet (...) -
Supporting all media types
13 avril 2011, parUnlike most software and media-sharing platforms, MediaSPIP aims to manage as many different media types as possible. The following are just a few examples from an ever-expanding list of supported formats : images : png, gif, jpg, bmp and more audio : MP3, Ogg, Wav and more video : AVI, MP4, OGV, mpg, mov, wmv and more text, code and other data : OpenOffice, Microsoft Office (Word, PowerPoint, Excel), web (html, CSS), LaTeX, Google Earth and (...)
-
Pas question de marché, de cloud etc...
10 avril 2011Le vocabulaire utilisé sur ce site essaie d’éviter toute référence à la mode qui fleurit allègrement
sur le web 2.0 et dans les entreprises qui en vivent.
Vous êtes donc invité à bannir l’utilisation des termes "Brand", "Cloud", "Marché" etc...
Notre motivation est avant tout de créer un outil simple, accessible à pour tout le monde, favorisant
le partage de créations sur Internet et permettant aux auteurs de garder une autonomie optimale.
Aucun "contrat Gold ou Premium" n’est donc prévu, aucun (...)
Sur d’autres sites (10626)
-
Swift A script of macOS is not running on the M2 chip ?
15 avril 2024, par Muhammad Danish QureshiI am making a macOS app using SwiftUI, app is working fine on mac Intel chip, mac Apple M1 chip but not working on the mac M2 chip.
Below is the following code which is crashing on M2 chip for force unwrapping the
data
inString(data: data!, encoding: .utf8)
.

I know that force unwrap is not suitable, but for testing purpose I am doing force unwrap.


When I run the
which ffmpeg
in terminal it provides the path in result, no matter which mac terminal is (it always return actual path of ffmpeg), but when run this command from the swift Program it does not found anything and got crashed on apple M2 chip.

My actual scenario (or requirement) is I need to get the path using the command
which ffmpeg
and write that path in the file on macOS app.

Kindly guide me why the code is crashing or not providing the actual path.


func findFFmpegPath() -> String? {
 let task = Process()
 task.launchPath = "/bin/bash" // Path to bash shell
 task.arguments = ["-l", "-c", "which ffmpeg"] // Execute "which ffmpeg" command
 let pipe = Pipe()
 task.standardOutput = pipe
 task.standardError = pipe // Capture any errors as well

 do {
 try task.run()
 let data = try pipe.fileHandleForReading.readToEnd()
 let output = String(data: data!, encoding: .utf8)
 print("data:\(data)\n\(output)\n\(output?.trimmingCharacters(in: .whitespacesAndNewlines))")
 return output?.trimmingCharacters(in: .whitespacesAndNewlines)
 } catch {
 print("Error running task: \(error)")
 return nil
 }
}



When I run
which ffmpeg
in the terminal it gives me path correctly, See the screenshot bleow.



When I run the
/bin/bash -l -c "which ffmpeg"
in the M2 than I got this result.



When I run the
/bin/bash -l -c "which ffmpeg"
in the Apple M1 than I got this result.



Getting desired result in the terminal, but not getting result from the Swift Program.


-
Ffmeg to convert images to video
30 octobre 2022, par WILT -
Unable to manually parse the HEVC video with alpha [closed]
17 novembre 2023, par leoI'm trying to parse the bitstream of HEVC video with alpha on linux(specific video format reference WWDC2019 : https://developer.apple.com/videos/play/wwdc2019/506).


Taking the 'puppets_with_alpha_hevc.mov' file from 'Using HEVC Video with Alpha' as an example, I would first extract the HEVC bitstream, then parse its fields. When it comes to the VPS field, as I reach the vps_extension, I find that the bitstream in 'puppets_with_alpha_hevc.mov' does not conform to the HEVC standard document, preventing further parsing.


The extracted HEVC bitstream binary is shown in the following image.


I analyzed the VPS part of the bitstream, and the vps_extension field should start from 0x3F. However, I encountered an issue when parsing up to 0xA4, as shown in the picture, and could not continue with the parsing.



I'm not sure at which step the error occurred, but it should be somewhere between the 0x3F on line 28 and 0xA4 on line 34. Is anyone familiar with HEVC with alpha ? Could you provide some insights or tips for analysis ?