If that doesn't suit you, our users have ranked 31 alternatives to MiniDLNA and 17 are available for Mac so hopefully you can find a suitable replacement. Other interesting Mac alternatives to MiniDLNA are Universal Media Server (Free, Open Source), Serviio (Freemium), PS3 Media Server (Free, Open Source) and MediaTomb (Free, Open Source). FREE Shipping on orders over $25 shipped by Amazon. YEHUA Wireless Display Receiver Miracast WiFi Display Adapter Screen Mirroring Dongle Compatible Airplay Miracast DLNA for iOS Devices Android Smartphone Mac Windows8.1/10.
Latest Version: 1.26
Rated 3/5 By 29 People
What does FireStream - UPnP/DLNA media server do? Introducing FireStream: the most advanced UPnP/DLNA media server for the Mac platform. FireStream is written for the Mac from scratch with an 'it just works' philosophy, so that you can be sure it provides a true, seamless Mac experience. Enjoy all of your media, including videos, photos and music on all of your DLNA devices. FireStream natively supports music and videos from iTunes and the new Photos app as well as any user specified folders. The media is organized just like it is on your Mac and includes thumbnails and rich metadata. Its a snap to locate and stream your favorite content from the comfort of your couch.Transcoding allows you to play media files that would normally not be supported by a device by converting them on the fly. You can specify connection speed and quality settings to fit your network and device capabilities with ease or enable subtitles with a single click.With automatic device detection and automatic transcoding configuration, FireStream makes streaming your media as easy as can be. Just power on your UPnP/DLNA media device and FireStream will instantly locate it. Using the Devices tab you can adjust advanced per-device transcoding, network and quality settings giving you fine-grained control of each device. FireStream also has a built in authorization system that allows you to limit access to specific devices.Unique just-in-time indexing technology allows FireStream to instantly share your media without having to index your entire Mac first! Changes to your media libraries or folders are instantly reflected in the FIreStream content index.FireStream works great with Xbox One, PlayStation 4, PlayStation 3, Sony Bravia TVs, Sony Blu-ray Players, LG Smart TVs, LG Blu-ray Players, Roku, Harman/Kardon receivers, Naim Uniti, Oppo Blu-ray players, Kodi, MediaMonkey, VLC for iOS/tvOS and many, many other devices.Get FireStream and enjoy the best Mac media streaming experience today!Note: Xbox 360 is not currently supported.Note: Users with iTunes or Photos libraries stored on an external drive or network share may need to add that drive/share to Content > Folders in FireStream and Stop, Quit and restart FireStream to ensure the content is accessible.Download for MacOS - server 1 --> $14.99
Looking for a simple DLNA server that I could just fire up in some directory, watch some files on my TV and then be done with it, I came up empty. There are some decent servers out there, like Serviio and friends, but none that fit my requirements. Also there wasn't really a decent enough and uncomplicated enough open source implementation that I could borrow. The Coherence python project seemed to be a good starting point, but was already to complex for what I was trying to achieve. Also, python dealing with Unicode paths on Windows pretty much sucks. Then there is Mono.UPnP, which didn't really work, and the Intel(?) Developer Tools for UPnP, which seemed kinda nice at first, but turned out to be coming straight out of over-engineering hell, in my humble opinion.
And so I decided to write my own server, borrowing some ideas from Coherence, reading some of the UPnP specs and reverse engineering the various protocols involved (yuck, SOAP :p) by watching my TV interact with Coherence and Serviio under Wireshark.
And since I was at it and this is supposed to be an educational and 'fun' project, I decided to do what you shouldn't normally do: Re-invent the wheel by writing my own small http server implementation insead of using the framework one.
Serve videos from current directory and subdirectories
sdlna.exe -t image -t audio -v bytitle
Serve images and audio files from the current directory and subdirectories, organizing files by title.
sdlna.exe -c cache.sqlite dir1 dir2
Serve videos from dir1 and dir2 (and subdirectories), storing meta data and thumbnails in the persistent cache store
Display usage help.
Or just use the WinForms GUI. (This probably won't work too well on non-Windows platforms ;)
Your front-end hereFeel free to contribute something that works better for your preferred platform.
Also, you'll want to have a working
ffmpeg binary somewhere within your
$PATH, so that video thumbnailing and information gathering works.
- Zero-config DLNA Server without persistent state (optional cache)
- Written in C# (See FAQ)
- Thumbnailing support for images and videos - if ffmpeg is found in the search path -, using any stream as input.
- Meta data as provided by TagLib#
- Serving of any and all file-system addressable files, incl. some views (transformations)
- Should be relatively easy to code up additional media sources, like podcasts
Non-Features, maybe TODO
- Media transcoding
- Although it should be easy enough to come up with something based on ffmpeg and the various freely available image libraries
- Full DLNA support - only browsing/playing supported at the moment
- Complete SSDP support. Because SSDP makes me cringe, I stopped after getting the basics working
- No Unit testing or test suite.. Yeah, laziness is your enemy
- Some .Net 4 Client Profile compatible implementation to run the app
- Tested on .Net 4 and Fedora17 + mono, OSX Lion + mono
- File system and networking :p
- Some DLNA renderer (e.g. TV) to actually display the served media.
- Tested with: Samsung C-Series TV, Kinsky
The external dependencies are nuget managed and can be auto-restored (except for Sqlite maybe.. Just reinstall it using nuget into the fsserver project).
The thing wasn't formally designed, but more written as I went along. However, the individual components are only loosely coupled and interact through some real, generic interfaces that allow for extensibility.
Most of the IO is asynchronous, as per .Net
Stream.BeginRead/.BeginWrite. No forking (D'OH), no explicit thread management.
The structure is as follows:
Best Dlna Server Windows 10
serverclass library - The actual core that implements an SSDP and HTTP server
SSDPServerimplementing the important bits of the SSDP-based multicast protocol as used by UPnP/DLNA
HttpClient- Custom, stripped down HTTP/1.0 implementation
Handlers- Request processing and response composition
Responses- Implementing an interface the HttpClient knows how to ship over the net.
Views- Transformations of media trees
- Some interfaces, types, enums, etc. to bring things together
fsserverclass library - Serving stuff from a file sytem. To be 'mounted' by the
- Virtual folder/file trees the HTTPServer MediaMount will understand
thumbsclass library - Generating thumbnail pictures from arbriary stream sources
- Image thumbnailer, using .Net System.Drawing
- Video thumbnailer, using ffmpeg via async pipes and the .Net Process API
sdlnaCLI application - Bringing the various pieces together
SimpleDLNAGUI application - Alternative to the CLI and with persistent configuration. This thing is especially rough, as im not an UX guy.
utilVarious low-level utility stuff
Feel free to drop me pull requests. If you plan to implement something more than a few lines, then open the pull request early so that there aren't any nasty surprises later. Please try not to introduce too many new FXCop warnings. ;)
Acdsee for mac os x torrent. It's 100% Cocoa and uses the latest technologies in Mac OS X. Xtorrent is powered by a download engine written from the ground up exclusively for Mac OS X. The result is a lightweight, stable experience that's optimized for the Mac.Xcore implements a fully modern torrent engine featuring support for all relevant torrent protocols (such as peer exchange and message stream encryption).
If you want to add something that will require some for of persistence incl. persistent configuration or API keys, etc., then open a pull request/issue especially early!
- Q: Does it work in my network/with my TV?
- A: At the moment, if you got a somewhat recent Samsung TV, then probably yes. Otherwise probably not. Why don't you just try?
- Q: This thing does not work with my setup?!
- A: Either provide me with the setup (i.e. buy me that TV) or whip out your debugger and Wireshark and read Contributing ;)
- Q: Are you planning to support Podcasts, RTMP streaming, insert name here?
- A: Maybe, but probably not. See Contributing
- Q: Why .Net and C#? I'm on Linux and/or Mac!
- A: Yeah, well.. Other languages have their own set of problems. C# is reasonably portable, managed and garbage collected, statically typed and comes with a huge stdlib. And actually quite nice to use. If only it wasn't for Microsoft having invented this stuff and holding various patents..
Dlna For Mac Free Music
To Microsoft, the UPnP(-AV) folks and Samsung and DLNA gurus for designing such a set of specs and protocols, that includes HTTP-alike over multicast UDP sockets, SOAP and XML, dozens of poorly documented namespaces used in SOAP responses, the contentFeatures.dlna.org HTTP header and other fancy tech. Also a big kudos to software engineers for messing up even the most basic things like http header field names are usually case insensitive or the Reason-Phrase of http status lines is purely informal.