
Recherche avancée
Autres articles (112)
-
Personnaliser en ajoutant son logo, sa bannière ou son image de fond
5 septembre 2013, parCertains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;
-
Ecrire une actualité
21 juin 2013, parPrésentez les changements dans votre MédiaSPIP ou les actualités de vos projets sur votre MédiaSPIP grâce à la rubrique actualités.
Dans le thème par défaut spipeo de MédiaSPIP, les actualités sont affichées en bas de la page principale sous les éditoriaux.
Vous pouvez personnaliser le formulaire de création d’une actualité.
Formulaire de création d’une actualité Dans le cas d’un document de type actualité, les champs proposés par défaut sont : Date de publication ( personnaliser la date de publication ) (...) -
Publier sur MédiaSpip
13 juin 2013Puis-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 (12802)
-
I want to be able to view the CCTV screen on the web
12 mars 2019, par 윤성호I want to be able to view the CCTV screen on the web.
I have been working on a project that allows the ip camera to be viewed on the web.
Then I was asked to make Coaxial camera visible on the web.
So I decided to use DVR.
First, I connected the DVR to the router.
Then the input of the coaxial camera is received by the DVR and the DVR transmits the information through the router.
Through this process, i confirmed that rtsp works normally.
But it didn’t work on the web.I am currently using the nginx web server.
and use ffmpeg to send rtsp information to rtmp on my nginx web server.
The web server will then transform it into an hls (index.m3u8) file.
I think something went wrong during this process.Nginx RTMP Config
# RTMP Config
rtmp {
server {
listen 1935; # Listen on standard RTMP port
chunk_size 4000;
application live{
live on;
deny play all;
push rtmp://localhost/play;
on_publish http://localhost:3001/api/on-live-auth;
on_publish_done http://localhost:3001/api/on-live-done;
}
application play {
live on;
# Turn on HLS
hls on;
hls_nested on;
hls_fragment_naming system;
hls_path /home/banana/nginx/live;
hls_fragment 3;
hls_playlist_length 60;
# disable consuming the stream from nginx as rtmp
#deny play all;
}
}
}
# End RTMP ConfigFFMPEG command
ffmpeg -i rtsp://<cameraip> -c:v copy -rtsp_transport tcp -preset veryfast -c:a copy -fflags +igndts+genpts -f flv rtmp://localhost/live/<cameraid>
</cameraid></cameraip>Test results
IP Camera RTSP address = admin:qwerty1.@ssnet4.iptime.org:555/trackID=3
DVR RTSP address = admin:hrd-442s@hwakptz.iptime.org:4524/1
Run the above rtsp addresses in vlc player respectively
Success : IP Camera RTSP address , DVR RTSP address
IP camera HLS address = http://168.131.150.80:4567/live/5c28ae28c6cd0c6c329e1ebc/index.m3u8
DVR HLS address = http://168.131.150.80:4567/live/5c8746c9d7d74a600edf2460/index.m3u8
Run the above rtsp addresses in vlc player respectively
Sucess : IP Camera HLS address
Fail : DVR HLS address
This is the same result on the react player.
const streamUrl = `http://168.131.150.80:4567/live/<cameraid>/index.m3u8`;
<reactplayer width="{"100%"}" height="{"100%"}" url="{streamUrl}" playing="{true}" controls="{false}" muted="{true}"></reactplayer>
</cameraid>Question
- Is there a way to see rtsp directly on the web ?
- What’s the problem and what’s the other way ?
-
rtpproto : Check the source IP if one single source has been specified
18 juillet 2013, par Martin Storsjörtpproto : Check the source IP if one single source has been specified
If another peer is sending unicast packets to the same port that
we are listening on, those packets can end up being received despite
using source specific multicast. For those cases, manually check the
source address of received packets against the intended source address.This only handles the case when the source list is one single IP
address for now, which probably is the most common case.Based on a patch by Ed Torbett.
Signed-off-by : Martin Storsjö <martin@martin.st>
-
Python UnicodeEncodeError : 'charmap' codec can't encode when using GEOPY
23 février 2021, par Tony RoczzI have been fiddling with python geopy and I tried the basic commands given in the documentation. But I am getting the UnicodeEncodeError when trying the
raw
command(to geolocate a query to an address and coordinates)


print(location.raw)




Error
UnicodeEncodeError: 'charmap' codec can't encode character '\xa9' in position 83: character maps to <undefined></undefined>



Then I tried the other way around (To find the address corresponding to a set of coordinates)



print(location.address) 




I am getting the same error
UnicodeEncodeError: 'charmap' codec can't encode character '\u0101' in position 10: character maps to <undefined></undefined>



I tried
print((location.address).encode("utf-8"))
, now am not getting any error but the output printed is like thisb'NH39, Mirz\xc4\x81pur



and when using
print((location.raw).encode("utf-8"))
I am getting error


AttributeError: 'dict' object has no attribute 'encode'




Can anyone tell me what is going on here and what I should do to get a proper output ?



Edit :(After being marked as duplicate)



Based on the solution given in this problem I am reporting on how it does not solve my problem



What I wanted to know is why do I get the UnicodeEncodeError when trying out the basic sample codings given in the documentation and it did answer for that.



If I want to use it an application how do I solve the error and I cannot have the application running on separate IDE or send the output to a external file since my application will function based on the output from geopy, I want the application to run in the terminal as my other applications do.