![]() Could you download the latest nightly (which is ready in a few minutes), copy over your /data folder from the 4.1.2 version and re-try to write the NFO. You can create a new shortcut to your tinyMediaManager.exe (right click the tinyMediaManager.exe and choose “New - Shortcut”) and add the start parameter ntentfolder='' to the shortcut (right click, choose “Properties” and enter the parameter after the executable). But what about using only one tinyMediaManager instance with multiple profiles Especially for macOS this is needed since there is no more a portable version for macOS. But I've just started a new nightly build with enhanced logging in the NFO writing. TinyMediaManager v5 offers now a new start parameter for setting the profile path, which needs to be set while starting tinyMediaManager: Windows MacOS: ~/Library/Application Support/tinyMediaManagerīut what about using only one tinyMediaManager instance with multiple “profiles”? Especially for macOS this is needed since there is no more a portable version for macOS. If you get some access/permission errors, you have to look at file system level - there is nothing special with Java. Windows: C:\Users\username\AppData\Roaming In this case Kodi just reads your local NFO/artwork files. If you don’t want Kodi also to contact external sites for meta data, you should set the Information provider to Local information only. TinyMediaManager v5 will be able to write your data into the systems default locations if you don’t use the portable version: Kodi natively supports NFO files - all you have to do is to prepare them with tinyMediaManager and set your data source as source in Kodi.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |