There are different file formats but the one to go for is GPX format.PSU can take the file generated by the tracker application and uses the time a picture was taken to match it to the location you - and the camera - were at that time then it writes that information to the PSU catalog and the image file (if you have PSU set to write metadata).There are many such tracker applications / devices available, both free and paid for.A GPS “tracker” application on a smartphone or dedicated GPS device can record your location and movements over a period (based on signals received from GPS satellites).The majority of “normal” cameras don’t have this capability but using PSU and a tracking app you can still geo-tag. If the picture was taken with a smartphone or GPS-enabled camera then the data will already include the latitude and longitude (subject to your settings and to the device picking up strong enough satellite signals).Whilst this can be done manually, here I am really talking about using a GPX file from a tracking app to apply a location. This location (normally) denotes where the image was taken. Geo-tagging is the process of assigning a geographical location to an image.Then in the next post I shall explain in detail how to geotag in PSU. But if you are having issues, these posts may help.įor those who may be new to this, in the first post I will describe what geo-tagging is and why you may want it. If you are not having issues then that’s great - your apps are probably better than mine and you don’t need to read this. This should be viewed as complimentary to the PSU help document Help>quick manual – Geotagging (PDF). Having got a little way in understanding the issues I am sharing in case it is useful to others. Some of these are caused by my cameras and my tracking app, but some of it is PSU and a combination of these issues makes confusing scenarios. This is for a variety of reasons, as will become clear (I hope). MediaElement.Geotagging in PSU has always caused me a lot of problems. mediaElement.SetPlaybackSource(MediaSource.CreateFromAdaptiveMediaSource(result.MediaSource)) Var source = MediaSource.CreateFromAdaptiveMediaSource(adaptiveMediaSource) RegisterForAdaptiveMediaSourceEvents(adaptiveMediaSource) Var adaptiveMediaSource = result.MediaSource If (result.Status = AdaptiveMediaSourceCreationStatus.Success)

Result = await AdaptiveMediaSource.CreateFromUriAsync(uri) Result = await AdaptiveMediaSource.CreateFromUriAsync(uri, httpClient) = new HttpCredentialsHeaderValue('Bearer', MainPage.bearerToken) ĪdaptiveMediaSourceCreationResult result = null HttpClientFilter.AuthorizationHeader = new HttpCredentialsHeaderValue('Bearer', MainPage.bearerToken) HttpClientFilter = new AddAuthorizationHeaderFilter(baseProtocolFilter) Since it is in MPEG-DASH protected format, the movie path uses var baseProtocolFilter = new HttpBaseProtocolFilter() ī = HttpCacheWriteBehavior.NoCache // Always set WriteBehavior = NoCache I receive the 'Video could not be decoded' error in video player and 'MF_MEDIA_ENGINE_ERR_DECODE : HRESULT - 0x8004110E' exception in MediaFailed event handler. In this case the mediaĬontent gets downloaded however it does not play in the media player. Therefore I use AdaptiveMediaSource to send the JWT authorization token in the HTTP header. The video file is in MPEG-DASH protected and it requires JWT token, uses Software DRM. I have a video file placed in azure media server.

Decoded error gps4cam