In this version we have improved the media server, the MediaCenter and the media presentation in addition to some internal routines.

New for the media server for macOS 10.15 and newer is the integrated movie segmenter (MPEG4AppleHLS), which breaks down movies into M3U8 segments and streams them to the media client (available in the MediaCenter). Previously only available as an extra installation through the mediafilesegmenter, Apple has now also integrated this function as a system routine.
After initial enthusiasm – after all, this could make both VLC 2.2.8 and ffmpeg superfluous – the disillusionment quickly followed: contrary to the usual M3U8, which also enables streaming if the entire movie is not yet available as segments, Apple has chossen a format in which the entire movie must be segmented. This is okay for short videos (e.g. iPhone recordings), but e.g. cinema movies would always have to be completely segmented beforehand. With a large movie collection of e.g. 8 TB, this would not only take time but also require another 8 TB of hard drive space. Since the media server segments movies ad hoc and then deletes the segments again, this solution can only be used for short movies (because these are segmented quickly enough and the segments can be deleted again after streaming).

If the size of a movie was changed during movie editing (e.g. to remove annoying black bars at the top and bottom), then this movie could only be streamed if the width / height is an even number. This incompatibility is now recognized and corrected accordingly.

Movies streamed to another Mac through the media server are presented there through the WebKit (HTML). Unfortunately, unlike the AppleTV and iPhone, the Mac system routines (AVFoundation) can not play M3U8 movies.
The WebKit used so far has been marked as “deprecated” by Apple – so we have integrated the new WebKit.
In addition, we have improved the display, integrated zooming and the preservation of the playback speed (slow motion or faster playback). The display duration for images etc. is also retained.

Unfortunately, while one might expect newer systems to be faster, the exact opposite is the case. Unfortunately, we already noticed this when accessing the Music App (instead of iTunes) – and this also applies to the creation of the preview images and meta information.
As a result, scrolling in the MediaCenter was sometimes “suboptimal” – only with the new asynchronous creation of this information (right side in the MediaCenter) is it somewhat smooth again for macOS 10.15 and newer.

Keywords: 64 bit, MediaCenter, Media Presentation, Media Server, nessMediaCenter, nessViewer


Although we actually have enough Apple hardware, we have now bought a new Apple computer in order to be able to test the new Apple processor Silicon M1 with our products. Actually, we would have preferred to wait until a 27-inch iMac with this processor is available, but well … a new Mac Mini is okay too.

The biggest surprise with the Mac Mini was that the MAC address changed – already known from iPhones, but not yet for us with Macs. Especially since no info was displayed even when starting the Mac Mini – and also the deactivation as with the iPhone is missing?
The point and purpose is actually that privacy is better protected if the device tries to log into different WLANs – this makes sense with iPhone and MacBooks, but who goes for a walk with a Mac Mini? And: only the last 2 characters are (so far?) exchanged … well, okay.
Since the MAC address is part of the registration key with nessViewer, the last 2 digits of random MAC addresses are now replaced by “XX”.

We have also improved video editing at nessViewer – tests with other different video sizes had shown that the merging of movies did not always work optimally.

Oh, yes: although all of our products also work optimally with Rosetta, nessMediaCenter and nessViewer now run natively on Apple Silicon M1 processors.

And not to forget: Apple has requested an update of “NV Remote II” because the iOS app has not been updated for a long time.

Keywords: 64 bit, edit, editing, M1, movie, nessMediaCenter, nessViewer, Silicon


As with nessMediaCenter, we have now fixed a bug in nessViewer caused by macOS 11 (Big Sur) and macOS 10.15 (Catalina) so that longer titles and descriptions are displayed correctly again in the MediaCenter.

In addition, we have improved the movie editing so that movies with different orientations (portrait, landscape) can now be joined together in a better way.
The system routines (AVFoundation) unfortunately place the individual tracks at the top or left. When joining, the offset is now calculated in order to place these tracks centered.

The prerequisite for this was maintaining the orientation. Up to now, a movie was displayed correctly after opening, even if recorded in portrait mode, but after the first editing (e.g. to delete a section) the movie was displayed horizontally. And then had to be rotated to the right once.

Now this orientation is retained even after editing. The changes required for this should also be achieved with less code at the same time, which was not easy and took several attempts. We are all the more pleased that it has now worked.

Keywords: 64 bit, edit, editing, MediaCenter, movie, nessViewer


With this version, a bug in macOS 11 (Big Sur) and partly also macOS 10.15 (Catalina) is “bypassed” – unfortunately there is no other way of saying it.

If a media title or description in the MediaCenter is longer than the available space, the rest of the text will be displayed automatically after a short time. Means scrolled, so to speak.
So that this is displayed smoothly even on very large screens with high resolution, only the affected area is scrolled. The rest of the content is not displayed again during this time.

To make this work, macOS provides routines for this – and has been doing this since the 1st day of macOS. That is basically fundamental.
Unfortunately, since Catalina, Apple has started to change the functions for this only partially and since Big Sur completely. The result: the text is scrolled, but the rest of the display … is deleted.

Actually this is a bug. Apple was also notified over 6 months ago. Unfortunately, Apple interprets this bug differently – according to Apple, it is not a bug, but “correct behavior”. With the additional hint that the developers may develop their own routines for a correct and optimized display.

Fortunately, we managed to turn this “correct behavior” off.

The AppStore version is in review by Apple since midday yesterday – we hope that this version will be available soon as well.

After 2.5 days, this version is now available in the Mac App Store as well.

This adjustment of the MediaCenter has already been implemented for nessViewer for Mac, but we are currently working on further improvements in movie editing.

Keywords: 64 bit, nessMediaCenter


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

← Older Newer →