June 20, 2019, 11:00:38 AM
Welcome, Guest. Please login or register
News: Stay up to date with everything that's happening at http://plus.digitalsignage.com

MediaSignage support forum

Recent Posts

Pages: 1 [2] 3 4 ... 10
Open source Digital Signage / Re: Install issue with StudioLite on Centos
« Last post by admin on June 11, 2019, 09:02:51 AM »
for distribution, run either:
- npm run release_aot
- npm run release_aot_no_sync
- npm run release_jit

either of the 3 will generate the the distribution folder ./dist where all the files you need for distribution will be placed.

note that the script assumes you are running this in unix/linux therefore are using unix commands.  if you are running this in windows, you may need to convert the script to use DOS commands

best regards

Open source Digital Signage / Re: Install issue with StudioLite on Centos
« Last post by tomislavl on June 11, 2019, 07:07:40 AM »
Thank you very much , that sorted my problem.

I just have one more q...

How to deploy edited studio-lite... i know that npm-install create instance for editing, and he is running in dev mode...
"dev": "npm run x_cssDev && ng serve --port 4208 --aot false"

is there any command for npm run prod or similiar?

Hi everyone,

When taking a picture with a digital camera, the orientation is saved as part of the metadata (EXIF). Since Windows 10 takes this tag into account, even pictures taken sideways or upside down appear correctly in Windows 10.

However, uploading pictures as resources to Studio-Pro doesn't take the tag into account. This can be very problematic for those who don't use software to correct the orientation of pictures before uploading to Studio-Pro. Suddenly pictures that look normal on your computer look sideways or upside down under Resources.  Using Scenes to rotate pictures is obviously a very limited workaround since no one wants to assign Scenes based on the orientation of the original photo!

Expected behaviour:  When uploading a picture as a resource, take into account the orientation so that it will always appear correctly.
Hi, thanks for the quick reply.

I'm using both Android 6 and Android 8. I installed the beta client you provided, it didn't resolve the issue. In fact there are some objects that appear in the stable release that don't work in the beta client, i.e. a .png resource.

Edit:  The issue is resolved thanks to the support staff's help, and the solution consists of two parts:  Installing the beta client, and also ensuring you have the hardware resources on the Android box for the graphical changes on the timeline. The beta client performed as expected on the stronger Android box, but gave a worse experience on the lower end box. Apparently S905 chipsets aren't heavy lifters! 
Open source Digital Signage / Re: Install issue with StudioLite on Centos
« Last post by admin on June 10, 2019, 07:09:42 AM »
if you are getting the error

            if (!require.extensions.hasOwnProperty(ext)) {

the above error message usually appears on nodejs version 8 or later.  you can modify the file:

and replace the line: if (!require.extensions.hasOwnProperty(ext)) {
with: if (!Object.prototype.hasOwnProperty.call(require.extensions, ext)) {

best regards

as i understand, you are using Android OS version 6 - what is the player software version used?

can you try this beta version of the android player: http://galaxy.signage.me/Code/Install/apk/6.3/CloudSignagePlayer.apk

Open source Digital Signage / Re: Install issue with StudioLite on Centos
« Last post by tomislavl on June 10, 2019, 06:38:33 AM »
i also have the same problem, and i try to remove CSS from gulp but i still have the same problem.
Any other suggestions?

My OS is Ubuntu 16.04
Hi everyone,

I've seen the following bug occur across different Android boxes (6.0 and above are in use):

1) Create a catalog item which is a picture resource (either jpg or png). Assign this item to a category.
2) Create a new scene (Catalog MIME). Add a "catalog item" component and assign it the "resource" item.
3) Within one of the channels in a timeline, add a "catalog player" component and assign the previous scene. Assign the catalog player to work with the catalog.

So far this is standard. Expected behaviour would be that every "time interval" the catalog player would show a different picture. However the picture doesn't show at all. What is shown on the Android box are fields like "name", "info0" etc. but no picture resources.

The timeline preview shows that the catalog player plays the picture resource correctly.

Things I've tried to resolve this:

1) Resize the picture (resource) to be the same size as the screen divison for the timeline.
2) Resize picture (resource), screen division AND scene to be the same size.
3) Played with background/appearance settings for catalog player, catalog item (under the scene) and the scene itself.
4) Resetting and clearing the cache for the Android players.

Any ideas what could be causing this and how to resolve it?

General discussion on the mediaSERVER / USB Administrator Issues
« Last post by Jennytrike on June 04, 2019, 10:15:33 PM »
I wonder why the hidden administrator is not included in advertisements for example. Or even in the Help window F1.
General discussion on the mediaCLOUD / Video On Demand Interactive list
« Last post by EdwardSek on June 04, 2019, 10:07:17 PM »
Im looking at putting a video capture card in my PC has anyone have any good ideas on what is the best one to use?
Pages: 1 [2] 3 4 ... 10
Carbonate design by Bloc
variant: carbon
SMF 2.0.12 | SMF © 2016, Simple Machines