latimagine.blogg.se - How to add a new song to media shout 4

#How to add a new song to media shout 4 code
#How to add a new song to media shout 4 windows 8

This is not "commercial-ready" code, but it does show the basic concepts. Net 4.5.2 included in the ShoutCast-2015 sample. There is a pre-built version of the library using. It requires a beta version of MediaFoundation.

#How to add a new song to media shout 4 windows 8

While the sample still works on Windows 7, the new Scheme handler that supports 200 OK only works on Windows 8 and (presumably) later.

So (nearly) the same player app works for both W7 & W8. And, it supports (just) enough seeking to work with W8's SourceResolver. In addition to handling streams that use ICY 200 OK, this one also handles just 200 OK (as well as a few other features). So I created my own Scheme handler (also written in c#). It bothered me that this didn't work on Windows 8. There may be some new approach that MS expects people to use, but I don't know what it might be. This seems weird, since such streams weren't seekable in W7 either, but apparently now that is a fatal error. The same program (above) that works fine on W7 now gives MF_E_BYTESTREAM_NOT_SEEKABLE errors on W8. They have completely broken the ability to stream mpeg audio using MF. Instead of 'fixing' MF to allow for any stream that specifies icy-metaint to provide song titles (a seemingly minor fix), MS went a different way.

I thought about trying to create such an MFT, but then I realized that: These beeps/buzzes can be very annoying (except with disco music since how could you tell?).

In fact, if a server sends song titles after having responded with 200 OK, MF will try to 'play' the titles. Note: If the server cannot be convinced to respond with ICY 200 OK (for example if it just uses 200 OK), there is no way to convince MF to automatically parse titles for you (although it may be possible to do the parsing yourself - maybe an MFT?).

If the server you are connecting to can be coaxed into responding with ICY 200 OK by sending an Icy-Metadata: 1, then explicitly using the UrlMonSchemePlugin instead of allowing the SourceResolver to resolve the URL can help.

Adding support for song titles is a fairly trivial change to the existing samples.

#How to add a new song to media shout 4 code

If the server you are connecting to uses ICY 200 OK to identify itself as an ICY server, you can use c# code like the shoutcast.zip code here.

There are several answers to this question, depending on your circumstances. Thank you in advance for your time and benevolence. NET, what I need to implement to trigger the above events? The question is: how could I get the updates from the shoutcast with Media Foundation. Which returns only these: "Bitrate" : 128 Hr = metadataProvider.GetMFMetadata(descriptor, 0, 0, out metadata) Īnd somewhere in the app I call: Display(stream.Metadata) Hr = mediaSource.CreatePresentationDescriptor(out descriptor) IMFMetadataProvider metadataProvider = obj as IMFMetadataProvider MediaSource, MFServices.MF_METADATA_PROVIDER_SERVICE, typeof(IMFMetadataProvider).GUID, out obj MediaStream, mediaURL, MFResolution.MediaSource, properties, out objectType, out mediaSourceĪnd this is how I get metadata: hr = MFExtern.MFGetService( Hr = sourceResolver.CreateObjectFromByteStream( MediaURL, MFResolution.ByteStream, properties, out mediaStream This is how I create media source: hr = sourceResolver.CreateObjectFromURL( I try to get song title from shoutcast stream, but the events: MENewStream, MEEndOfStream, MESourceMetadataChanged are never triggered, nothing is updated.