352x288

0 views
Skip to first unread message

Dinah Lianes

unread,
Aug 3, 2024, 1:14:45 PM8/3/24
to fortcomrole

When I do this I get two spatial layers, based on the first two of my three constraints. For the higher resolution spatial layer he decoded / displayed videoWidth and videoHeight (on the element) are 352x288, the scaleResolutionDownBy=2 value. This works this way on iOS Safari and on Windows Chrome, Edgium, and Firefox.

If you pass low resolution constraints to gUM then the libwebrtc encoder will just generate low resolution simulcast streams. Anyway, this is how libwebrtc/Chrome/Firefox works. mediasoup does not and cannot change their behavior.

When exporting media in Premiere Pro under the MPEG-4 format, I only have two (3GPP) presets for exporting and both are 352x288 or smaller. If I choose one and try to change the video options below an error pops up that says that resolution is not supported. With that said...

How would I export a file with the following specs:

Yeah, I have tried multiple other things, but still I am unable to export a H264 MP4 with embedded captions. It works with mxf files but I am being asked for MP4 files with the embedded captions? I much apprciate all the help here and hope maybe there is an answer as to why that option is not available for H264 files?

When you perform the calibration of the stereo camera on images with a resolution less than 640x480, large errors are obtained. For example, using images with a resolution of 352x288 p. the errors are:

I don't know what requirements you need to meet for error and depth, but you need to budget your accuracy through each step of your application's image pipeline. Here's what I do: I calibrate my cameras at the maximum resolution they will support. When I run an application which needs to use the calibration/depth map, I pyramid down (linear interpolate) the left and right images to the lowest resolution which will meet my application's requirements, to reduce the processing time and latency.

Another observation, the interesting scene should fill our field of view. You're using a very small portion of your image as a region of interest. Can you use longer focal length lenses, or move your cameras physically closer to the objects of interest? You will get much higher accuracy that way.

@opalmirror, this means you can calibrate on resolutions with large sizes, and in the future work use a lower resolution? Does this mean that the calibration matrices do not depend on the original image resolution?

Since I'm usually using ROS as a library level above opencv, it's only a general approach. I can in this way use camera information from calibration from one imager resolution, at a different imager resolution.

I'm experimenting with using the Pi for web cam streaming and motion detection, with the motion app. Trying a few different web cameras and combinations with other hardware, I've found one combination that is perfectly stable (see below). However, I'm only getting it to work with a resolution of 352x288. I would like to utilize more of the resolution that the 720p web cam is capable of. I've tried 640x480, 640x360 and 1280x720, but they don't work (motion is unable to initialize the camera). The Pi has 256MB of memory, which should be plenty to support the high resolutions. For instance, motion lists memory usage at 1.8MB for the 1280x720 resolution.

Edit: I have since found that the setup I'm currently using with MJPG-streamer is not completely stable, so there's a chance that the setup described above is not completely stable but just more stable as it uses a lower resolution.

Edit 2 (4/21/13): It has been known for a while that USB is not stable on the Raspberry Pi, causing trouble with many web cameras and wifi dongles. The foundation is actively working on this, and good progress has been made lately. There is an update available via rpi-update that fixes many issues. See the USB Redux thread on the Raspberry Pi forum.

The limit on resolution went away when I switched from motion to MJPG-streamer. MJPG-streamer streams 1280x720 at 5FPS. With 3 computers connected to the stream, the CPU usage is only around 10%. The disadvantage with MJPG-streamer is that it does not have motion detection.

I believe it is very tricky to find the right resolution I had been stuck with 352x288 for quite some time until I discovered that I can also use a 960 x 720 resolution. With this kind of resolution I get about 2 fps. (keeps the need for storage low ;-)).

Huge catalog of beautiful wallpapers 352x288 in high quality. All pictures are sorted by popularity. A handy search by colors and tags will help you find the perfect covers for your phone. The catalog contains the most popular vertical wallpapers with a resolution of 352x288 on a variety of topics, from beautiful girls, anime, flowers and landscapes, to dark (black) pictures, photos of cars, space and various backgrounds. You can download them directly to your phone or computer and then download them to your Android or iPhone. Attention! All new screensavers 352 on 288 on the site were uploaded by our users or found freely distributed on the Internet and are presented for informational purposes only. By downloading free wallpapers 352x288 you assume responsibility for their use.

TEMIC stands for TEleMaintenance Industrielle Cooperative which means Industrial Co-operative Remote Maintenance.TEMIC is a French national project with several academic (LIFC, INRIA, GRTC) andindustrial (SWI)partners.

TEMIC proposes a hardware and software platform of collaborative remotemaintenance : maintenance staff may work remotely and in collaborationwith other experts. The integration of innovative solutions in terms ofnetworks and mobility leads to competitive maintenance solutions, based on the connection (nearby or remote) of multimedia computer data with adapted human skills.
The TEMIC platform integrates various technologies:

  • Networks: they may be wire (LAN, WAN) or wireless (GPRS, WiFi, Bluetooth).They present different characteristics (rate...).
  • Terminals: PC, laptop, PDA, mobile phone.Resources, display capacity, communication protocol, are different.
  • Multimedia applications: VOD, videoconference, file download.They run with specific protocols and video/audio formats.
This heterogeneity needs adaptive solutions for an efficient streams transmissionon the platform networks.

To respond to these various constraints, active services have to adapt and optimizethe content of streams passing through the active network node.Multimedia data streams adaptation is performed dynamically in order to improve industrial maintenance solutions.The challenge is to provide an architecture running in a client/serverenvironment, but involving no modification on the applications installed on the end-machines like web servers, video players,...

For the Temic project, our team has worked on the design and adaptation of an industrial autonomic network node, whichis derived from the Tamanoir environment. This Industrial Autonomic Network Node is designed to be deployed on limited resources based network boxes, and so to be integrated into industrial platforms.

We developed and tested active adaptation network services, specially written for the Tamanoir Execution Environment in Java.Active services applying on multimedia streams crossing the network node may realise data compression, format transcoding, frame resizing... This kind of adaptation contributes to the saving of network bandwidth (by decreasing the output data rate) and to thereduction of the resources used on the client terminal playing the multimedia data (by reducing the framerate and the frame size). The adaptation is thereby transparent for the applications.

We present two industrial maintenance scenarios on which we baseour experimentations. These scenarios were planned by the TEMICproject team to be used by a company through a maintenance contracton a restricted industrial area.

This scenario (Fig. 1) adds multimedia sensors (microphone + video camera) to industrial classical sensors (temperature sensor, contact sensor ...). In the Temic project, the video camera is directed towards a strategic area inside a pump house whereas the microphone is used to locate unusual engines sounds. They can be combined together, and in this case the data flow will contain both audio and video streams. This scenario remains opened to all kinds of survey data. New sensors providing several data streams may beadded.

Terminals may be laptop, PDA, in fact every mobile device able to communicate with at least the HTTP protocol and to play multimedia data. The access server is used both to grant access to the system from mobile clients and to transmit survey data coming from industrials sensors to the active network node. The active network node hosts active adaptation network services which analyse clients requests and transmit them the adapted data. All collected data (provided by sensors) are managed by the active network node. It means that data are stored, deleted if not necessary anymore or transmitted to users who ask for them.

In this scenario, all communications occur on wireless network, and the end users are located outside the restricted area. End users (maintenance staff), if they are authorized to connect to the system, have the possibility to get data stored on the active network node (still images for instance) and to visualise in real-time the video/audio streams coming from the video camera/micro.

Active adaptation network services deployed for this scenarioprovide the following tasks :

  • adaptation of transmited multimedia streams, on the fly, to mobile devices. Streams are adapted to network conditions, processing and display capacities of the receiving terminal with modifications of frame size, quality factor, encoding format. Audio and video streams are transmitted with a streaming protocol like RTP, which stands upon UDP.
  • adaptation of some data, such as still images, with the same modification as above. The adapted data are then transmitted, possibly contained into a file, to mobile devices. The difference with the case presented above is that data are not sent with a streaming protocol. They may be contained into a file (a jpeg image) and transmitted with HTTP. Players on mobile devices are not the same for both cases.
  • storage on the active network node of some sensors data and multimedia data, and management of the storage unit by regular cleanings.

c80f0f1006
Reply all
Reply to author
Forward
0 new messages