In addition to further adaptions for macOS 11 (Big Sur) and minor improvements, the data rate and FPS (Frames Per Seconds) can now explicitly be specified when exporting movies in MPEG-4 format.

So far, the various standard export settings (presets) from Apple have been used both for saving and for exporting movies. This makes it easy to save movies in HD or SD format or for AppleTV / iPad / iPhone, WiFi and Cellular.
However, these standard export settings also have a disadvantage: neither the data rate nor the FPS can be specified explicitly, which means that the movies sometimes have a very large file size, especially in the HD format. In addition, 30 FPS is used by default – even if the original only has 25 FPS.
Especially after changing the video size (e.g. to crop the top and bottom edges), the standard export settings mean that the movies are sometimes 2-4 times as large as the original after saving. In addition to the 30 FPS, this is due to a high data rate, e.g. 7500 instead of 4500 kBits / second.

In this version, after selecting the MPEG-4 format, the data rate and FPS can now be specified explicitly.

nessViewer movie export

The default values ​​are the values ​​of the original – but it is worthwhile to reduce the data rate, especially for longer movies. E.g. for a merged 30 minutes iPhone recording, the file size can be reduced from 2 GB to 800 MB. However, it is advisable to check the export afterwards and, if necessary, to try different data rates in order to obtain an optimal relationship between quality and file size.

We have made a video showing the editing of movies with the 64 bit version containing: rotate & save, join, delete & save, export.

Keywords: 64 bit, data rate, edit, editing, fps, movie, mpeg-4, nessViewer


After the DLNA bug fix for the support of miniDLNA (middle of December) we continued to work on the improvements in this version to extend the access to miniDLNA and to use nessViewer as an iCloud alternative in better way.

In addition to minor improvements in accessing miniDLNA (date and duration of videos in a more readable form, preview of movies), the access of DLNA media servers outside the local network is now also possible via VPN.

Normally this access via VPN is not possible because the DLNA media server is not found even with the VPN connection. Therefore, in addition to the TCP/IP address (and port), the name of the info file can now be specified in the nessViewer App settings – with these two details, direct access is also possible via VPN.

These two details are filled in automatically by nessViewer App – it is sufficient to enter a unique part of the TCP/IP address (e.g. “.20:”) at “DLNA” in the settings and then to access with the MediaCenter the DLNA media server in the local network.

The FTP client of the nessViewer App can of course not only access the nessViewer media server but also a DLNA media server. The only prerequisite for this is the input of the FTP user and password in the settings.

When transferring files, not only the selected file can now be transferred, but also all files in a folder.

In addition, all files in a folder can now be deleted (via the action menu) after “Open File” has been selected.

With these improvements, it is now easier to transfer many photos and movies (possibly even from the “Photos App”) to the media server (or vice versa):
1.) If necessary import photos and movies from the “Photos App” into nessViewer App (via the action menu at “Open File”).
2.) Transfer this media from the nessViewer App to the media server (via FTP client).
3.) If necessary delete these media in the nessViewer App (via the action menu at “Open File”).

There is a PDF document describing nessViewer as an iCloud alternative in German from 2012. Except for the improvements described here (and of course minor visual changes), it is still up to date.

Keywords: alternative, DLNA, FTP, iCloud, iOS, movie, nessViewer, photo, Photos App, VPN


After we intensively tested miniDLNA, installed on the Raspberry Pi, we noticed a few things that were not so optimally.

On one hand, the date of videos was displayed in an illegible form and the duration directly behind it. Now the date is displayed localized and the duration in the 2nd line.

In addition, a preview is now displayed for videos. We have read the opportunity to create a cover for each video and to change the miniDLNA configuration. But that is too complex for us with so many videos.
However, the video preview may take 1-3 seconds to display – depending on the video.

And in general, the automatic selection did not work correctly with DLNA (both after selecting a menu entry and after returning to a higher level) – which has now been corrected.

Keywords: Apple, AppStore, DLNA, MediaCenter, Media Server, miniDLNA, TV, tvOS


nessMediaCenter App for AppleTV now supports miniDLNA too.

We have been informed by Dennis that nessMediaCenter App for AppleTV can not access miniDLNA installed on the Raspberry Pi. So far, miniDLNA has not been specified as supported DLNA / UPnP media server, but Raspberry Pi is an interesting solution because of the low price.

After a loan was unfortunately too old to install OpenMediaVault 4 on it, we invested in Raspberry Pi – and unfortunately we had to find out during tests that miniDLNA can be accessed with the MediaCenter of nessMediaCenter / nessViewer for macOS but not with nessMediaCenter for AppleTV or nessViewer for iOS.

While the DLNA media server information is loaded synchronously on macOS, it is loaded asynchronously on iOS and tvOS. While this is not a problem with other DLNA media servers, the information was loaded too slowly with miniDLNA – and as a result the process no longer worked correctly.

We have therefore extended the code so that it is now checked again in the asynchronous call whether media can be accessed. With this extension the media of miniDLNA can now be accessed.

Keywords: Apple, AppStore, DLNA, MediaCenter, Media Server, miniDLNA, TV, tvOS


After the adaptions for iOS 13 (nessViewer, finessTV) and tvOS 13 (nessMediaCenter, finessTV), the adaptions for macOS 15 (Catalina) are now available.

So far, we had been waiting with the updates for macOS 15, because unfortunately (again this time) Apple has not reacted to our bug report. And through this bug, the access to the media of the Photos App fails with macOS 15. Unfortunately, this bug was not fixed even with macOS 15.1, but since Apple made this update now generally available, we have no other choice. As with macOS 14, we hope that Apple will find time as soon as possible – and will not need 1/2 year as last time.

Addendum from 18.12: meanwhile we were able to clarify the problem with Apple. Fortunately it is not a bug, but just a setting: the selected photo library must be set as a system photo library so that the photos app media can be accessed.

The most important adaptation is the playback of the music and protected movies through the MediaCenter. While macOS 10.14 or earlier uses iTunes for this playback, macOS 10.15 uses the Music App for music playback (Music App Control) and the TV app for playing protected movies.

In addition, we have newly developed the access to the media of the Photos App. Previously, these media and their structure were read directly from the database – but since this is no longer possible under macOS 10.15, the system framework “MLMediaLibrary” is now used instead.
This works very well for macOS 14 or older, but unfortunately, as already said, not yet on macOS 15.

Keywords: 64 bit, Music App, nessMediaCenter, nessViewer, Photos App, TV App

← Older Newer →