Recherche avancée

Recherche
Choix de la période de publication
Date minimale :

Date maximale :

Type de date :
Choix de la langue
Choix du type de média
Choix de la rubrique
Choix de la licence de publication
Choix de l’auteur

Médias (2)

Mot : - Tags -/media

SPIP - plugins - embed code - Exemple

2 septembre 2013, par kent1

Mis à jour : Septembre 2013

Langue : français

Type : Image

Tags : media, embed, code, intégration

1
2
3
4
5
Publier une image simplement

13 avril 2011, par kent1, Webmaster - Bij de Brest

Mis à jour : Février 2012

Langue : français

Type : Video

Tags : publier, publishing, media, image

1
2
3
4
5

Autres articles (67)

List of compatible distributions

26 avril 2011, par kent1

The table below is the list of Linux distributions compatible with the automated installation script of MediaSPIP. Distribution nameVersion nameVersion number Debian Squeeze 6.x.x Debian Weezy 7.x.x Debian Jessie 8.x.x Ubuntu The Precise Pangolin 12.04 LTS Ubuntu The Trusty Tahr 14.04
If you want to help us improve this list, you can provide us access to a machine whose distribution is not mentioned above or send the necessary fixes to add (...)
Encodage et transformation en formats lisibles sur Internet

10 avril 2011

MediaSPIP transforme et ré-encode les documents mis en ligne afin de les rendre lisibles sur Internet et automatiquement utilisables sans intervention du créateur de contenu.
Les vidéos sont automatiquement encodées dans les formats supportés par HTML5 : MP4, Ogv et WebM. La version "MP4" est également utilisée pour le lecteur flash de secours nécessaire aux anciens navigateurs.
Les documents audios sont également ré-encodés dans les deux formats utilisables par HTML5 :MP3 et Ogg. La version "MP3" (...)
Liste des distributions compatibles

26 avril 2011, par kent1

Le tableau ci-dessous correspond à la liste des distributions Linux compatible avec le script d’installation automatique de MediaSPIP. Nom de la distributionNom de la versionNuméro de version Debian Squeeze 6.x.x Debian Weezy 7.x.x Debian Jessie 8.x.x Ubuntu The Precise Pangolin 12.04 LTS Ubuntu The Trusty Tahr 14.04
Si vous souhaitez nous aider à améliorer cette liste, vous pouvez nous fournir un accès à une machine dont la distribution n’est pas citée ci-dessus ou nous envoyer le (...)

1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | ... | 23

Sur d’autres sites (9626)

Stage-Whisper is not working because of missing files

24 novembre 2023, par Tingtong
I tried to install this here : https://github.com/Stage-Whisper/Stage-Whisper




Once i put the audio file in it, it is still loading and loading but not transcribing it.




So after that i checked the requirements and packages, if there is something missing and there is. I installed those here :



```
Node (required for Electron)&#xA;Yarn (required for Electron)&#xA;Python 3.x (required for backend)&#xA;Rust (required for backend)&#xA;ffmpeg (required for backend)&#xA;Poetry (required for backend)&#xA;
```



I installed them with homebrew. There are some errors showing up, once i launch the electron programm with "yarn dev" : ERROR : "could not locate binding files"




I also tried "poetry run python stagewhisper —input /path/to/audio/file.mp3", but got following message. Poetry could not find a pyproject.toml file in /Users/Administrator/Desktop/Stage-Whisper or its parents.




Where do i have to put the file pyproject.toml and what do i have to write in it ?




So i checked with brew info all tools which i need for Stage-Whisper. Screenshots :enter image description here
[enter image description here](https://i.stack.imgur.com/sirb3.png)




What i tried was to update those packages/requirements which where missing, with "sudo port install requirementPackageName ". But after checking with brew info again, those parts are still missing. So does that actually work or do i have to install those missing stuff with homebrew ? I have Mac Mojave 10.14.6 and Homebrew 4.1.18 Version.




I also got an error, while i installed those tools with homebrew :




ERROR : You are using macOS 10.14.
We (and Apple) do not provide support for this old version. It is expected behaviour that some formulae will fail to build in this old version... etc




Thank you for your help guys.




Edit :






yarn install v1.22.19 warning ../../../package.json : No license field
[1/4] 🔍 Resolving packages... [2/4] 🚚 Fetching packages... [3/4]
🔗 Linking dependencies... warning "@emotion/react >
@emotion/babel-plugin@11.10.2" has unmet peer dependency
"@babel/core@^7.0.0". warning "@emotion/react > @emotion/babel-plugin






@babel/plugin-syntax-jsx@7.18.6" has unmet peer dependency "@babel/core@^7.0.0-0". warning " > autoprefixer@10.4.4" has unmet
peer dependency "postcss@^8.1.0". warning " >
eslint-config-airbnb@19.0.4" has unmet peer dependency
"eslint-plugin-react-hooks@^4.3.0".
[----------------------------------------------------------------------------------------------------------------------------------------------------------------------------] 0/890^[4/4] 🔨 Building fresh packages... [1/7] ⠁ better-sqlite3
[-/7] ⠁ waiting... [3/7] ⠁ sqlite3 [4/7] ⠁ esbuild error
/Users/administrator/Desktop/Stage-Whisper/electron/node_modules/better-sqlite3 :
Command failed. Exit code : 1 Command : prebuild-install || npm run
build-release Arguments : Directory :
/Users/administrator/Desktop/Stage-Whisper/electron/node_modules/better-sqlite3
Output : prebuild-install warn install No prebuilt binaries found
(target=20.9.0 runtime=node arch=x64 libc= platform=darwin)









better-sqlite3@7.6.2 build-release
node-gyp rebuild —release







gyp info it worked if it ends with ok gyp info using node-gyp@9.3.0
gyp info using node@20.9.0 | darwin | x64 gyp info find Python using
Python version 3.9.14 found at "/usr/local/bin/python3" gyp info spawn
/usr/local/bin/python3 gyp info spawn args [ gyp info spawn args

'/Users/administrator/Desktop/Stage-Whisper/electron/node_modules/electron-rebuild/node_modules/node-gyp/gyp/gyp_main.py',
gyp info spawn args 'binding.gyp', gyp info spawn args '-f', gyp
info spawn args 'make', gyp info spawn args '-I', gyp info spawn
args

'/Users/administrator/Desktop/Stage-Whisper/electron/node_modules/better-sqlite3/build/config.gypi',
gyp info spawn args '-I', gyp info spawn args

'/Users/administrator/Desktop/Stage-Whisper/electron/node_modules/electron-rebuild/node_modules/node-gyp/addon.gypi',
gyp info spawn args '-I', gyp info spawn args

'/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/common.gypi',
gyp info spawn args '-Dlibrary=shared_library', gyp info spawn args
'-Dvisibility=default', gyp info spawn args

'-Dnode_root_dir=/Users/administrator/Library/Caches/node-gyp/20.9.0',
gyp info spawn args

'-Dnode_gyp_dir=/Users/administrator/Desktop/Stage-Whisper/electron/node_modules/electron-rebuild/node_modules/node-gyp',
gyp info spawn args

'-Dnode_lib_file=/Users/administrator/Library/Caches/node-gyp/20.9.0/<(target_arch)/node.lib',
gyp info spawn args

'-Dmodule_root_dir=/Users/administrator/Desktop/Stage-Whisper/electron/node_modules/better-sqlite3',
gyp info spawn args '-Dnode_engine=v8', gyp info spawn args

'—depth=.', gyp info spawn args '—no-parallel', gyp info spawn
args '—generator-output', gyp info spawn args 'build', gyp info
spawn args '-Goutput_dir=.' gyp info spawn args ] gyp info spawn
make gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]

TOUCH ba23eeee118cd63e16015df367567cb043fed872.intermediate ACTION
deps_sqlite3_gyp_locate_sqlite3_target_copy_builtin_sqlite3
ba23eeee118cd63e16015df367567cb043fed872.intermediate TOUCH
Release/obj.target/deps/locate_sqlite3.stamp CC(target)
Release/obj.target/sqlite3/gen/sqlite3/sqlite3.o LIBTOOL-STATIC
Release/sqlite3.a CXX(target)
Release/obj.target/better_sqlite3/src/better_sqlite3.o In file
included from ../src/better_sqlite3.cpp:4 : In file included from
./src/better_sqlite3.lzz:11 : In file included from
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/node.h:73 :
In file included from
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8.h:24 :
In file included from
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-array-buffer.h:12 :
In file included from
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-local-handle.h:12 :
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-internal.h:465:30 :
warning : static_assert with no message is a C++17 extension
[-Wc++17-extensions]
SHARED_EXTERNAL_POINTER_TAGS(CHECK_SHARED_EXTERNAL_POINTER_TAGS)
^ /Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-internal.h:465:30 :
warning : static_assert with no message is a C++17 extension
[-Wc++17-extensions]
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-internal.h:465:30 :
warning : static_assert with no message is a C++17 extension
[-Wc++17-extensions]
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-internal.h:465:30 :
warning : static_assert with no message is a C++17 extension
[-Wc++17-extensions]
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-internal.h:465:30 :
warning : static_assert with no message is a C++17 extension
[-Wc++17-extensions]
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-internal.h:466:35 :
warning : static_assert with no message is a C++17 extension
[-Wc++17-extensions]
PER_ISOLATE_EXTERNAL_POINTER_TAGS(CHECK_NON_SHARED_EXTERNAL_POINTER_TAGS)
^ /Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-internal.h:466:35 :
warning : static_assert with no message is a C++17 extension
[-Wc++17-extensions]
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-internal.h:466:35 :
warning : static_assert with no message is a C++17 extension
[-Wc++17-extensions]
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-internal.h:466:35 :
warning : static_assert with no message is a C++17 extension
[-Wc++17-extensions]
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-internal.h:466:35 :
warning : static_assert with no message is a C++17 extension
[-Wc++17-extensions]
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-internal.h:466:35 :
warning : static_assert with no message is a C++17 extension
[-Wc++17-extensions]
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-internal.h:466:35 :
warning : static_assert with no message is a C++17 extension
[-Wc++17-extensions]
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-internal.h:466:35 :
warning : static_assert with no message is a C++17 extension
[-Wc++17-extensions]
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-internal.h:466:35 :
warning : static_assert with no message is a C++17 extension
[-Wc++17-extensions]
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-internal.h:466:35 :
warning : static_assert with no message is a C++17 extension
[-Wc++17-extensions]
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-internal.h:466:35 :
warning : static_assert with no message is a C++17 extension
[-Wc++17-extensions]
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-internal.h:466:35 :
warning : static_assert with no message is a C++17 extension
[-Wc++17-extensions]
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-internal.h:693:61 :
warning : static_assert with no message is a C++17 extension
[-Wc++17-extensions]
static_assert(kJSObjectType + 1 == kFirstJSApiObjectType) ;
^
, "" /Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-internal.h:694:55 :
warning : static_assert with no message is a C++17 extension
[-Wc++17-extensions]
static_assert(kJSObjectType < kLastJSApiObjectType) ;
^
, "" /Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-internal.h:695:63 :
warning : static_assert with no message is a C++17 extension
[-Wc++17-extensions]
static_assert(kFirstJSApiObjectType < kLastJSApiObjectType) ;
^
, "" In file included from ../src/better_sqlite3.cpp:4 : In file included from
./src/better_sqlite3.lzz:11 : In file included from
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/node.h:73 :
In file included from
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8.h:24 :
In file included from
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-array-buffer.h:13 :
In file included from
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-object.h:9 :
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-maybe.h:106:45 :
error : no template named 'is_lvalue_reference_v' in namespace 'std' ;
did you mean 'is_lvalue_reference' ? template >
 ^ 
is_lvalue_reference /Library/Developer/CommandLineTools/usr/include/c++/v1/type_traits:780:50 :
note : 'is_lvalue_reference' declared here template struct
_LIBCPP_TEMPLATE_VIS is_lvalue_reference : public false_type {} ;
^ In file included from ../src/better_sqlite3.cpp:4 : In file included from
./src/better_sqlite3.lzz:11 : In file included from
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/node.h:73 :
In file included from
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8.h:24 :
In file included from
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-array-buffer.h:13 :
In file included from
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-object.h:9 :
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-maybe.h:106:69 :
error : expected '(' for function-style cast or type construction

template >
 ^ /Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-maybe.h:123:43 :
error : no template named 'is_lvalue_reference_v' in namespace 'std' ;
did you mean 'is_lvalue_reference' ? template * = nullptr>
 ^ 
is_lvalue_reference /Library/Developer/CommandLineTools/usr/include/c++/v1/type_traits:780:50 :
note : 'is_lvalue_reference' declared here template struct
_LIBCPP_TEMPLATE_VIS is_lvalue_reference : public false_type {} ;
^ In file included from ../src/better_sqlite3.cpp:4 : In file included from
./src/better_sqlite3.lzz:11 : In file included from
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/node.h:73 :
In file included from
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8.h:24 :
In file included from
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-array-buffer.h:13 :
In file included from
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-object.h:9 :
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-maybe.h:123:67 :
error : expected '(' for function-style cast or type construction
template * =
nullptr>
 ^ In file included from ../src/better_sqlite3.cpp:4 : In file included from
./src/better_sqlite3.lzz:11 : In file included from
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/node.h:73 :
In file included from
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8.h:33 :
In file included from
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-function.h:11 :
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-function-callback.h:151:66 :
warning : static_assert with no message is a C++17 extension
[-Wc++17-extensions]
kReturnValueDefaultValueIndex - kReturnValueIndex) ;
^
, "" /Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-function-callback.h:153:50 :
warning : static_assert with no message is a C++17 extension
[-Wc++17-extensions]
kIsolateIndex - kReturnValueIndex) ;
^
, "" ./src/util/macros.lzz:157:21 : error : no member named
'AccessorSignature' in namespace 'v8'
v8::AccessorSignature::New(isolate, recv)
 ^ ./src/util/binder.lzz:37:51 : error : no member named 'CreationContext' in 'v8::Object'
v8::Local ctx = obj->CreationContext() ;
 ^ 22 warnings and 6 errors generated. make : ***
[Release/obj.target/better_sqlite3/src/better_sqlite3.o] Error 1 rm
ba23eeee118cd63e16015df367567cb043fed872.intermediate gyp ERR ! build
error gyp ERR ! stack Error : make failed with exit code : 2 gyp ERR !
stack at ChildProcess.onExit
(/Users/administrator/Desktop/Stage-Whisper/electron/node_modules/electron-rebuild/node_modules/node-gyp/lib/build.js:203:23)
gyp ERR ! stack at ChildProcess.emit (node:events:514:28) gyp ERR !
stack at ChildProcess._handle.onexit
(node:internal/child_process:294:12) gyp ERR ! System Darwin 18.7.0 gyp
ERR ! command "/usr/local/bin/node"
"/Users/administrator/Desktop/Stage-Whisper/electron/node_modules/.bin/node-gyp"
"rebuild" "—release" gyp ERR ! cwd
/Users/administrator/Desktop/Stage-Whisper/electron/node_modules/better-sqlite3







Same goes for the the "poetry install" command in the backend folder :




8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/build/onig_sys-3a9a2f947b5ad744/outwarning: variable does not need to be mutable --> tokenizers-lib/src/models/unigram/model.rs:265:21 | 265 | let mut target_node = &mut best_path_ends_at[key_pos]; | ----^^^^^^^^^^^ | | | help: remove thismut| = note:#[warn(unused_mut)]` on by default




warning : variable does not need to be mutable
—> tokenizers-lib/src/models/unigram/model.rs:282:21
|
282 | let mut target_node = &mut best_path_ends_at[starts_at + mblen] ;
| ----^^^^^^^^^^^
| |
| help : remove this mut




warning : variable does not need to be mutable
—> tokenizers-lib/src/pre_tokenizers/byte_level.rs:200:59
|
200 | encoding.process_tokens_with_offsets_mut(|(i, (token, mut offsets))| 
| ----^^^^^^^
| |
| help : remove this mut




error : casting &T to &mut T is undefined behavior, even if the reference is unused, consider instead using an UnsafeCell
—> tokenizers-lib/src/models/bpe/trainer.rs:526:47
|
522 | let w = &words[*i] as *const _ as *mut _ ;
| -------------------------------- casting happend here
...
526 | let word : &mut Word = &mut (*w) ;
| ^^^^^^^^^
|
= note : #[deny(invalid_reference_casting)] on by default




warning : tokenizers (lib) generated 3 warnings
error : could not compile tokenizers (lib) due to previous error ; 3 warnings emitted




Caused by :
process didn't exit successfully : /Users/administrator/.rustup/toolchains/stable-x86_64-apple-darwin/bin/rustc --crate-name tokenizers --edition=2018 tokenizers-lib/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no --cfg 'feature="cached-path"' --cfg 'feature="clap"' --cfg 'feature="cli"' --cfg 'feature="default"' --cfg 'feature="http"' --cfg 'feature="indicatif"' --cfg 'feature="progressbar"' --cfg 'feature="reqwest"' -C metadata=cb36f9861d265e60 -C extra-filename=-cb36f9861d265e60 --out-dir /private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps -L dependency=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps --extern aho_corasick=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/libaho_corasick-021885281f13d108.rmeta --extern cached_path=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/libcached_path-767095c4d4a77107.rmeta --extern clap=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/libclap-c92d2593d8a75e62.rmeta --extern derive_builder=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/libderive_builder-833217c2af636976.dylib --extern dirs=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/libdirs-f12e99ecd3a76eae.rmeta --extern esaxx_rs=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/libesaxx_rs-b694f04df571686b.rmeta --extern indicatif=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/libindicatif-39491a3282a24810.rmeta --extern itertools=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/libitertools-b322e49e83853c17.rmeta --extern lazy_static=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/liblazy_static-28a96417d88df3c9.rmeta --extern log=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/liblog-937f94f366843d8a.rmeta --extern macro_rules_attribute=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/libmacro_rules_attribute-d4d77bee9330e675.rmeta --extern onig=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/libonig-7f9dab4334743bdf.rmeta --extern paste=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/libpaste-a36a4a0dbc2ac63f.dylib --extern rand=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/librand-4b1adc86e35ea892.rmeta --extern rayon=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/librayon-d134e48f83d52e6e.rmeta --extern rayon_cond=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/librayon_cond-5715a923c66c54a9.rmeta --extern regex=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/libregex-a5c54f2d0034ab98.rmeta --extern regex_syntax=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/libregex_syntax-58c405f62323b6ed.rmeta --extern reqwest=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/libreqwest-1551c89d20e17f58.rmeta --extern serde=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/libserde-f4748cc953dd1338.rmeta --extern serde_json=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/libserde_json-5fba404e8440399e.rmeta --extern spm_precompiled=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/libspm_precompiled-6bd24072bd3c9d31.rmeta --extern thiserror=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/libthiserror-bcbb2769006ee534.rmeta --extern unicode_normalization_alignments=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/libunicode_normalization_alignments-658520cf6a5461dc.rmeta --extern unicode_segmentation=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/libunicode_segmentation-fffd829ab6256bb0.rmeta --extern unicode_categories=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/libunicode_categories-e3815c3d18c1086b.rmeta -L native=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/build/bzip2-sys-d2cb72d65b178690/out/lib -L native=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/build/zstd-sys-ddff0154a55a136c/out -L native=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/build/esaxx-rs-69d9e34a40d41449/out -L native=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/build/onig_sys-3a9a2f947b5ad744/out (exit status : 1)
error : cargo rustc --lib --message-format=json-render-diagnostics --manifest-path Cargo.toml --release -v --features pyo3/extension-module --crate-type cdylib -- -C 'link-args=-undefined dynamic_lookup -Wl,-install_name,@rpath/tokenizers.cpython-311-darwin.so' failed with code 101




at /usr/local/lib/python3.11/site-packages/poetry/installation/chef.py:166 in _prepare
162│
163│ error = ChefBuildError("\n\n".join(message_parts))
164│
165│ if error is not None :
→ 166│ raise error from None
167│
168│ return path
169│
170│ def _prepare_sdist(self, archive : Path, destination : Path | None = None) -> Path :




Note : This error originates from the build backend, and is likely not a problem with poetry but with tokenizers (0.12.1) not supporting PEP 517 builds. You can verify this by running 'pip wheel —no-cache-dir —use-pep517 "tokenizers (==0.12.1)"'.




UPDATE (SOLVED) :






i found a solution and this worked for me :







"I had the same problem and nothing mentioned here worked for me. Here is what worked for me :




**("Didnt do this Part")"Require all dependencies you need in the main.js file that is run by electron."** 





What i did was :
Run npm i -D electron-rebuild to add the electron-rebuild package
Remove the node-modules folder, as well as the packages-lock.json file.
Run npm i to install all modules.
Run ./node_modules/.bin/electron-rebuild (.\node_modules.bin\electron-rebuild.cmd for Windows) to rebuild everything




It is very important to run ./node_modules/.bin/electron-rebuild directly after npm i otherwise it did not work on my mac."




But now i get following Error, when i upload and transcribe the file :




> [ELECTRON] NewEntry: Creating new entry with UUID: XY...
[ELECTRON] NewEntry: Copying audio file to store...
[ELECTRON] NewEntry: Audio file copied to store.
[ELECTRON] NewEntry: Entry added to database!
[ELECTRON] RunWhisper: Running model with args [
[ELECTRON] '--verbose',
[ELECTRON] 'true',
[ELECTRON] '--output_dir',
[ELECTRON] '/Users/administrator/Library/Application Support/stagewhisper/store/whisper/2a07203b-ad88-438c-babf-b600cb76aa1d',
[ELECTRON] '--task',
[ELECTRON] 'translate',
[ELECTRON] '--model',
[ELECTRON] 'base',
[ELECTRON] '--device',
[ELECTRON] 'cpu',
[ELECTRON] '--input',
[ELECTRON] '/Users/administrator/Library/Application Support/stagewhisper/store/audio/harvard.mp3'
[ELECTRON] ]
[ELECTRON] RunWhisper: Child process closed with code 1
[ELECTRON] RunWhisper: Error running whisper script!
[ELECTRON] Error occurred in handler for 'run-whisper': Error: Error running whisper script!
[ELECTRON] at ChildProcess.<anonymous> (/Users/administrator/Desktop/Stage-Whisper/electron/main/handlers/runWhisper/runWhisper.js:234:31)
[ELECTRON] at ChildProcess.emit (node:events:390:28)
[ELECTRON] at maybeClose (node:internal/child_process:1064:16)
[ELECTRON] at Socket.<anonymous> (node:internal/child_process:450:11)
[ELECTRON] at Socket.emit (node:events:390:28)
[ELECTRON] at Pipe.<anonymous> (node:net:687:12)

 
</anonymous></anonymous></anonymous>

Revision 32595 : avec le numero de version des plugins

1er novembre 2009, par fil@… — Log

avec le numero de version des plugins

How Media Analytics for Piwik gives you the insights you need to measure how effective your video and audio marketing is – Part 2

2 février 2017, par InnoCraft — Community

In Part 1 we have covered some of the Media Analytics features and explained why you cannot afford to not measure the media usage on your website. Chances are, you are wasting or losing money and time by not making the most out of your marketing strategy this very second. In this part, we continue showing you some more insights you can expect to get from Media Analytics and how nicely it is integrated into Piwik.

Video, Audio and Media Player reports

Media Analytics adds several new reports around videos, audios and media players. They are all quite similar and give you similar insights so we will mainly focus on the Video Titles report.

Metrics

The above mentioned reports give you all the same insights and features so we will mainly focus on the “Video Titles” report. When you open such a report for the first time, you will see a report like this with the following metrics :

“Impressions”, the number of times a visitor has viewed a page where this media was included.

“Plays”, the number of times a visitor watched or listened to this media.

“Play rate”, the percentage of visitors that watched or listened to a media after they have visited a page where this media was included.

“Finishes”, the percentage of visitors who played a media and finished it.

“Avg. time spent”, the average amount of time a visitor spent watching or listening to this media.

“Avg. media length” the average length of a video or audio media file. This number may vary for example if the media is a stream.

“Avg completion” the percentage of how much visitors have watched of a video.

If you are not sure what a certain metric means, simply hover the metric title in the UI and you will get a detailed explanation. By changing the visualization to the “All Columns Table” in the bottom of the report, you get to see even more metrics like “Plays by unique visitors”, “Impressions by unique visitors”, “Finish rate”, “Avg. time to play aka hesitation time”, “Fullscreen rate” and we are always adding more metrics.

These metrics are available for the following reports :

“Video / Audio Titles” shows you all metrics aggregated by video or audio title

“Video / Audio Resource URLs” shows you all metrics aggregated by the video or audio resource URL, for example “https://piwik.org/media.mp4”.

“Video / Audio Resource URLs grouped” removes some information from the URLs like subdomain, file extensions and other information to get aggregated metrics when you provide the same media in different formats.

“Videos per hour in website’s timezone” lets you find out how your media content is consumed depending on the hour of the day. You might realize that your media is consumed very differently in the morning vs at night.

“Video Resolutions” lets you discover how your video is consumed depending on the resolution.

“Media players” report is useful if you use different media players on your websites or apps and want to see how engagement with your media compares by media player.

Row evolution

At InnoCraft, we understand that static numbers are not so useful. When you see for example that yesterday 20 visitors played a certain media, would you know whether this is good or bad ? This is why we always give you the possibility to see the data in relation to the recorded data in the past. To see how a specific media performs over time, simply hover a media title or media resource URL and click on the “Row Evolution” icon.

Now you can see whether actually more or less visitors played your chosen video for the selected period. Simply click on any metric name and the chosen metrics will be plotted in the big evolution graph.

This feature is similar to the Media Overall evolution graph introduced in Part 1, but shows you a detailed evolution for an individual media title or resource.

Media details

Now that you know some of the most important media metrics, you might want to look a bit deeper into the user behaviour. For example we mentioned before the “Avg time spent on media” metric. Such an average number doesn’t let you know whether most visitors spent about the same time watching the video, or whether there were many more visitors that watched it only for a few seconds and a few that watched it for very long.

One of the ways to get this insight is by again hovering any media title or resource URL and clicking on the “Media details” icon. It will open a new popup showing you a new set of reports like these :

The “Time spent watching” and “How far visitors reached in the media” bar charts show you on the X-Axis how much time each visitor spent on watching a video and how far in the video they reached. On the Y-Axis you see the number of visitors. This lets you discover whether your users for example jump often to the middle or end of the video and which parts of your video was seen most often.

The “How often the media was watched in a certain hour” and “Which resolutions the media was watched” is similar to the reports introduced in Part 1 of the blog post. However, this time instead of showing aggregated video or audio content data, they display data for a specific media title or media resource URL.

Segmented audience log

In Part 1 we have already introduced the Audience Log and explained that it is useful to better understand the user behaviour. Just a quick recap : The Audience Log shows you chronologically every action a specific visitor has performed on your website : Which pages they viewed, how they interacted with your media, when they clicked somewhere, and much more.

By hovering a media title or a media resource and then selecting “Segmented audience log” you get to see the same log, but this time it will show only visitors that have interacted with the selected media. This will be useful for you for example when you notice an unusual value for a metric and then want to better understand why a metric is like that.

Applying segments

Media Analytics lets you apply any Piwik segment to the media reports allowing you to dice your visitors or personas multiplying the value that you get out of Media Analytics. For example you may want to apply a segment and analyze the media usage for visitors that have visited your website or mobile app for the first time vs. recurring visitors. Sometimes it may be interesting how visitors that converted a specific goal or purchased something consume your media, the possibilities are endless. We really recommend to take advantage of segments to understand your different target groups even better.

The plugin also adds a lot of new segments to your Piwik letting you segment any Piwik report by visitors that have viewed or interacted with your media. For example you could go to the “Visitors => Devices” report and apply a media segment to see which devices were used the most to view your media. You can also combine segments to see for example how often your goals were converted when a visitor viewed media for longer than 10 seconds after waiting for at least 20 seconds before playing your media and when they played at least 3 videos during their visit.

Widgets, Scheduled Reports, and more.

This is not where the fun ends. Media Analytics defines more than 15 new widgets that you can add to your dashboard or export it into a third party website. You can set up Scheduled Reports to receive the Media reports automatically via email or sms or download the report to share it with your colleagues. It works also very well with Custom Alerts and you can view the Media reports in the Piwik Mobile app for Android and iOS. Via the HTTP Reporting API you can fetch any report in various formats. The plugin is really nicely integrated into Piwik we would need some more blog posts to fully cover all the ways Media Analytics advances your Piwik experience and how you can use and dig into all the data to increase your conversions and sales.

How to get Media Analytics and related features

You can get Media Analytics on the Piwik Marketplace. If you want to learn more about this feature, you might be also interested in the Media Analytics User Guide and the Media Analytics FAQ.

1 | ... | 2087 | 2088 | 2089 | 2090 | 2091 | 2092 | 2093 | 2094 | 2095 | ... | 3209

Recherche avancée

Médias (2)

SPIP - plugins - embed code - Exemple

Publier une image simplement

Autres articles (67)

List of compatible distributions

Encodage et transformation en formats lisibles sur Internet

Liste des distributions compatibles

Sur d’autres sites (9626)

Stage-Whisper is not working because of missing files

Revision 32595 : avec le numero de version des plugins

How Media Analytics for Piwik gives you the insights you need to measure how effective your video and audio marketing is – Part 2

Video, Audio and Media Player reports

Metrics

Row evolution

Media details

Segmented audience log

Applying segments

Widgets, Scheduled Reports, and more.

How to get Media Analytics and related features

Se connecter

Navigation

Syndication

Boussole SPIP