Same here, if I’m not using the legacy driver, all hell breaks loose.

Honestly, I would bet that it’s (through no fault of the author’s) the video feed just blowing everything up. Are you using RTSP with OMXPlayer?

I ended up going back to the legacy driver for video, using MMFPEG, and restarting MM every 2 hours to get it stable.

Yep.

			dateFormat: "M/D h:mm a",

That’ll fix it.

odd… Here’s how I have mine configured, and it clearly changes things

{
			module: "calendar",
			position: "top_right",
			config: {
				maximumEntries: 15,
				maximumNumberOfDays: 90,
				displaySymbol: false,
				maxTitleLength: 30,
				wrapEvents: true,
				fetchInterval: 120000,
				fade: false,
				dateFormat: "M/D h:mm a",
				fullDateEventDateFormat: "M/D",
				timeFormat: "absolute",
				getRelative: 0,
				urgency: 0,
				broadcastEvents: false,
				hideOngoing: true,
				excludedEvents: ["InOffice"],
				dateEndFormat: "h:mm a",
				calendars: [
					{
						symbol: "calendar",
						url: "https://url", 
					}
					],
				}
		},

I’d use this in my config.js for the calendar module’s config:

dateFormat: "h:mm a", //  This sets the string to time only
timeFormat: "absolute", // only shows times normally. 
getRelative: 0, // lowers the limit for absolute time to zero - no relative. 
urgency: 0, // makes sure it stays absolute.

I do believe that changing the dateFormat to “H:mm” will go 24 hour.

Most of the location numbers for major cities are actually in the source code for the webpage, just an FYI. Point people to the webpage for closer details.

What’s your CSS look like to make the grey background, shouldn’t be anything more than this:

.module {
background-color:rgba(0,0,0,0.5);
border-radius: 5px;
padding:5px;
}

More info needed - what modules are you running?

Is there any modules configured to “fullscreen_above” or “fullscreen_below”?

@costascontis said in [MMM-RTSPStream] - Video Streaming from Live Feeds & Security Cameras:

can someone use vlc instead of omxplayer with your module?If yes whats the pro and con on that?

I know on the develop branch you can.

Pro: it kept the original aspect ratio.
con: it didn’t work more than once.

I’m unable to get this module to load and run with FFMPeg anymore - as of 3PM 1/4/19 (Pacific Time (Seattle))

Update was applied as of that time.

I don’t know how to retrieve logs.

– Bug filed on github - https://github.com/shbatm/MMM-RTSPStream/issues/34

Does the config.js file pass the internal config check? This will help you determine that:

Run:
cd ~\MagicMirror
npm run config:check

@michael5r - Actually, I don’t get scrollbars at all. If I don’t subtract back from the 100vh/100vw or 100% - It’ll just run off the edge of the screen as if the system is seeing the screen (In this case, the RasPi’s 7" touchscreen) bigger than it is. With it set the way I have it, everything is dead on edge, giving the maximum use of the screen.

I’d support trying VLC over OMXPlayer - OMXPlayer barely works - and crashes so much, I had to switch to FFMpeg(?) – and even that crashes on my Pi 3+

@sdetweil so, then because I have to use the following:

body {
margin: 0px;
height: calc(100vh - 10px);
width: calc(100vw - 5px);
}

am I correct in assuming that magicmirror sees the screen a few pixels bigger than it really is - and that’s being expressed by running off the right and bottom of the screen when I don’t have the 10px subtract from height, and the 5px subtract from width?

This is the part that’s getting me…

width: calc(100vh - var(–body-margin) * 2);
height: calc(100vw - var(–body-margin) * 2);

If I’m reading this correctly - it’s taking the calculation of 100% of the viewpoint(direction) - the margin defined in the varible multiplied by 2?

100% of the viewport height minus 40 pixels in your example?

@sean Can you explain your body code a bit? I’m not quite following it.

@michael5r Actually, if I don’t subtract, the margins run clear off the right side and bottom of the screen, using the official 7" touchscreen, those subtractions bring it back to 100%

God, what an annoying video. Echo and loudness had me turning it off in 30 seconds or less.

Yeah, just something I can’t figure out for now. Thanks anyway. I’ll disable it and put it on my “maybe to do later” list.

It’s showing for me, @j-e-f-f