Mediatomb manual refresh




















Post by SolaR » Sat Sep 04, pm. Post by gjc » Mon Sep 06, pm. Post by SolaR » Mon Sep 06, pm. Post by chupacabra » Mon Sep 06, pm. Post by faderus » Tue Sep 07, am. Post by mattman » Thu Sep 09, pm.

Post by SolaR » Thu Sep 09, pm. Post by gjc » Sat Sep 11, pm. Kasper Langmann , Co-founder of Spreadsheeto. Table of Content. Chapter 2: Manual Data Refresh. Chapter 3: Automatic Page Refresh.

Chapter 4: Limitations and Considerations. Chapter 5: Wrapping things up…. To edit or remove media, select "PC Directory" and navigate to the directory containing the media files you want to edit or remove.

Click the X to the right of the file or directory to remove it from MediaTomb's media database. Click the edit icon to the right of a media file to edit the description or mime type used when sharing the media. Click the plus sign surrounded by circular arrows to the right of a directory to change the advanced sharing options.

After edited the configuration file, restart MediaTomb. Then remove the indexed folders and files in web interface. Add them again to show the correct filename. This option may also be safely used on x86 machines - the drawback is poor performance, compared to assembler optimized code. By default this feature is enabled for x86 platforms, but is disabled for others. We discovered that MediaTomb will not cleanly restart on ARM based systems, investigations revealed that this is somehow related to an unclean libupnp shutdown.

This will be fixed in a later release. Default: auto detect 3. If you have a renderer that requires this service, you can safely enable it. It will always return true to IsValidated and IsAuthorized requests. Note: eventhough this service is implemented there is still no Xbox support in MediaTomb, more work needs to be done. Playstation 3 Support --enable-protocolinfo-extension Default: enabled This option allows to send additional information in the protocolInfo attribute, this will enable MP3 and MPEG4 playback for the Playstation 3, but may also be useful to some other renderers.

Note: allthough compiled in, this feature is disabled in configuration by default. Fseeko Check --disable-fseeko-check Default: enabled This is a workaround for a bug in some Debian distributions, disable this check if you know that your system has large file support, but configure fails to detect it.

Largefile Support --disable-largefile Default: auto By default largefile support will be auto detected by configure, however you can disable it if you do not want it or if you experience problems with it on your system.

Since malloc and realloc may behave different on other systems, this gives us the opportunity to write wrapper functions to handle special cases. However, this redefinition may get triggered when cross compiling, even if you are compiling against the GNU C lib.

If this is the case, you can use this option to disable the redefinition. SQLite Support --enable-sqlite3 Default: enabled The SQLite database is very easy in installation and use, you do not have to setup any users, permissions, etc. A database file will be simply created as specified in the MediaTomb configuration. At least SQLite version 3 is required.

We use it to create a nice virtual container layout based on the metadata that is extracted from your media. We also allow the user to create custom import scripts, so everyone has the possibility to adapt the layout to ones personal needs.

Read more about this in the installation section. The main problem with this library is, that it is called differently on various distributions and that it is installed in different locations. For example, it is called js on Fedora, but is available under the name of smjs on Debian.

If configure fails to find your js headers and libraries you can point it to the desired locations see options below. Filemagic Support --enable-libmagic Default: enabled This library determines the file type and provides us with the appropriate mime type information.

It is very important to correctly determine the mime type of your media - this information will be sent to your renderer. If auto detection returns strange mime types, you may want to do a check using the 'file' command the 'file' package must be installed on your system. Assuming that you want to check somefile. You can override auto detection by defining appropriate file extension to mime type mappings in your configuration file. You can also edit the mime type information of an imported object manually via the web UI.

Id3lib Support --enable-id3lib Default: disabled, used if taglib is not available This library will parse id3 tags of your MP3 files, the gathered information will be saved in the database and provided via UPnP. Taglib Support --enable-taglib Default: enabled, preffered over id3lib This library will parse id3 tags of your MP3 files as well as information provided with flac files.

It claims to be faster than id3lib, but it also seems to have some drawbacks. We had some cases where it crashed when trying to parse tags of certain MP3 files on embedded systems, we had reports and observed that it had problems parsing the sample rates. We also did some valgrinding and detected memory leaks. Our feeling is, that you will have more stable results with id3lib, however it is up to you to enable or disable this library.

By default id3lib will be taken if both libraries are present on the system. Libexif Support --enable-libexif Default: enabled The exif library will gather metadata from your photos, it will also find exif thumbnails which are created automatically by most digital camera models. The gathered data will be used by the import script, the thumbnails will be offered as additional resources via UPnP. Inotify Support --enable-inotify Default: auto Inotify is a kernel mechanism that allows monitoring of filesystem events.

You need this if you want to use the Inotify Autoscan mode, contrary to the Timed mode which recsans given directories in specified intervals, Inotify mode will immedeately propagate changes in monitored directories on the filesystem to the database. If you do not specify this option configure will check if inotify works on the build system and compile it in only if the check succeeds.

If you specify this option, the functionality will be compiled in even if the build system does not support inotify - the availability of inotify will then be checked at server runtime. The feature only makes sense in combination with transcoding, since most devices do not support playback of flv files natively. External Transcoding --enable-external-transcoding Default: enabled 3. Sqlite Backup Defaults --enable-sqlite-backup-defaults Default: disabled Enables backup option for sqlite as the default setting, might be useful for NAS builds.

Curl --enable-curl Default: enabled if external transcoding or YouTube features are turned on It only makes sense to enable the curl library if YouTube and External Transcoding are turned on. YouTube requires curl, but it's optional for External Transcoding. Ffmpeg Support --enable-ffmpeg Default: enabled Currently the ffmpeg library is used to extract additional information from audio and video files. It is also capable of reading out the tag information from theora content.

It is not yet used for transcoding, so this feature only gathers additional metadata. Ffmpeg Thumbnailer Support --enable-ffmpegthumbnailer Default: enabled Compiling with ffmpegthumbnailer support is only possible if you also compile with ffmpeg support. The library allows to generate thumbnails for the videos on the fly. MediaTomb Debug Output --enable-tombdebug Default: disabled This option enables debug output, the server will print out a lot of information which is mainly interesting to developers.

Use this if you are trying to trace down a bug or a problem, the additional output may give you some clues. You should not need it under normal circumstances. Log Output --disable-log Default: enabled This option allows you to suppress all log output from the server. Debug Log Output Default: enabled This option allows you to compile the server with debug messages.

If enabled, switching between verbose and normal output during runtime becomes possible. You can also specify the exact location of those programs. The parameters are self explanatory, in case of headers and libraries the DIR parameter is the directory where those headers and libraries are located.

The devconf Script If you are doing some development work and some debugging, you will probably want to compile with the -g flag and also disable optimization. The devconf script does exactly that. In addition, it accepts command line parameters that are passed to the configure script.

Network Setup Some systems require a special setup on the network interface. MediaTomb is running, but your renderer device does not show it you should try the following settings the lines below assume that MediaTomb is running on a Linux machine, on network interface eth1 : route add -net By default MediaTomb will select a free port starting with , however you can specify a port of your choice in the configuration file.

Further, a default server configuration file, called config. Using MySQL Database If MediaTomb was compiled with support for both databases, sqlite will be chosen as default because the initial database can be created and used without any user interaction. MediaTomb has to be able to connect to the MySQL server and at least the empty database has to exist. To create the database and provide MediaTomb with the ability to connect to the MySQL server you need to have the appropriate permissions.

However, this is not recommended. If database auto creation wasn't compiled in configure was run with the "--disable-db-autocreate" or zlib. IP Address --ip or -i The server will bind to the given IP address, currently we can not bind to multiple interfaces so binding to 0. Interface --interface or -e Interface to bind to, for example eth0, this can be specified instead of the ip address. Port --port or -p Specify the server port that will be used for the web user interface, for serving media and for UPnP requests, minimum allowed value is If this option is omitted a default port will be chosen, however, in this case it is possible that the port will change upon server restart.

Configuration File --config or -c By default MediaTomb will search for a file named "config. This option allows you to specify a config file by the name and location of your choice. The file name must be absolute. Home Directory --home or -m Specify an alternative home directory. By default MediaTomb will try to retrieve the users home directory from the environment, then it will look for a. This option is useful in two cases: when the home directory can not be retrieved from the environment in this case you could also use -c to point MediaTomb to your configuration file or when you want to create a new configuration in a non standard location for example, when setting up daemon mode.

In the latter case you can combine this parameter with the parameter described in Section 5. Config Directory --cfgdir or -f The default configuration directory is combined out of the users home and the default that equals to.

This is useful when you want to setup the server in a nonstandard location, but want that the default configuration to be written by the server.

Run Under Different User Name --user or -u Run MediaTomb under the specified user name, this is especially useful in combination with the daemon mode. Run Under Different Group --group or -g Run MediaTomb under the specified group, this is especially useful in combination with the daemon mode. Add Content --add or -a Add the specified directory or file name to the database without UI interaction. The path must be absolute, if path is a directory then it will be added recursively.

If path is a file, then only the given file will be imported. Log To File --logfile or -l Do not output log messages to stdout, but redirect everything to a specified file. Debug Output --debug or -D Enable debug log output.

Compile Info --compile-info Print the configuration summary used libraries and enabled features and exit. Version Information --version Print version information and exit. Display Command Line Summary --help or -h Print a summary about the available command line options.

Configuration File MediaTomb is highly configurable and allows the user to set various options and preferences that define the servers behavior. Rather than enforcing certain features upon the user, we prefer to offer a number of choices where possible. The heart of MediaTomb configuration is the config. If the configuration file is not found in the default location and no configuration was specified on the command line, MediaTomb will generate a default config. Server Settings These settings define the server configuration, this includes UPnP behavior, selection of database, accounts for the UI as well as installation locations of shared data.



0コメント

  • 1000 / 1000