Portrait Presentations

the information below applies to presentations created in brightauthor\ connected and brightauthor classic content created in a partner cms may behave differently as the cms may handle rotation in a different manner landscape brightsign players natively output video in the landscape (horizontal) orientation, just like blu ray/dvd players and most media players like amazon fire stick, google chromecast, roku media players, and tivo stream while newer players and os versions do support custom resolutions which can potentially output true portrait video, this is not yet natively supported in either brightauthor\ connected or brightauthor classic landscape on portrait displays displaying a landscape presentation on most displays that are rotated to the portrait (vertical) orientation results in the video appearing sideways, unless the display itself is doing some internal rotation for portrait presentations, the player must internally rotate the content to output a rotated landscape display that would appear sideways if displayed on a landscape oriented display rotating displays some newer displays (e g , samsung frame models), have orientation sensors and the display will rotate the input based on the display's physical orientation this results in landscape presentations appearing in the correct orientation, either letter boxed (bars at top and bottom) or stretched out of aspect depending on the display setting portrait presentations, on the other hand, are pre rotated by the player, then rotated again by the display resulting in the image being sideways and letter boxed or stretched out of aspect depending on the display setting automatic input rotation should be disabled on displays like this to avoid the double rotation for samsung displays, the source content orientation setting needs to be changed to force it to landscape while the hdmi input is selected series 4 vs series 5 & 6 portrait content is displayed differently on series 5 and 6 players than older series 4 players series 5 and 6 players these players do not rotate the individual widgets portrait rotations take place on the rovideomode docid\ qq734nqz0hcwni0unsdmp object within the autorun brs (for example, the transform() = “90” call after getscreenmodes() ) example this example uses rovideomode to rotate the display vidmode = createobject("rovideomode") width = vidmode getresx() height = vidmode getresy() sm = vidmode getscreenmodes() videomode$ = mid(str(width),2) + "x" + mid(str(height),2) + "x60p" sm\[0] video mode = videomode$ sm\[0] transform = "90" sm\[0] display x = 0 sm\[0] display y = 0 sm\[0] enabled = true vidmode setscreenmodes(sm) r = createobject("rorectangle",0,0,width,height) series 4 players portrait rotations must take place on the individual widgets used by your application (for example, “rot90” in the config for rohtmlwidget docid\ xljq5 yhdma2ssmpzimtk ) when using rotouchscreen docid\ wydfi oewp1uofqjvyhhu , the touch screen must also be rotated when using touch events example this example uses rohtmlwidget to rotate the display config = { url "//filepath for index html//", transform "rot90", nodejs enabled true, mouse enabled true, inspector server { port 2999 }, port msgport, } rect = createobject("rorectangle", 0, 0, width, height) htmlwidget = createobject("rohtmlwidget", rect, config)