Hi there. Due to the lack of one of my favorite Plugins, i choose to implement it by myself. It should take a http_stream and write it to the Disk. Before i start and spend my time, ive a simple question: Is it possible with the actual V0.9 SDK? For better understanding ive drawed a little Picture which explains, what i want to do:

Click here...

The Second is: I need some tips about the preferences Dialog and whats the best way to create a subpage for it. Do u use the Form-Designer for it? Its not described in the tutorials

No Idea?! A simple yes its possible, or no it isnt would be enough for me...

Havent thought that no one wants a Streamripper... :/

Ok i give up
Ive found nothing in the SDK what i could use to "grab" the http-stream on his way from "input" to the "decoder". Since i got no help, the only way is to write a replacement for the build-in http-reader i think. Future Answers are welcome, but for now i stop to spend my time.

You are right, you cannot intercept data from an arbitrary file/stream. You also cannot replace a filesystem handler like the built-in HTTP handler; you could use a handler for a different scheme that wraps an existing handler, for example by internally redirecting operations on "http+grab://" URLs to operations on"http://" URLs.

Ok. Let me Summarize this:

- I cant "override" the internal http-reader
- I cant get the Pointer from the audio-Stream (on his way to the Decoder)
- But i can write my own Input-Plugin to handle URIs like this: ""httpgrab://xxxx.com"

If this is all correct, i must say that the v0.9 SDK has more limitations than 0.8.3
Damn... i need the Source-code of "foo_input_std.dll" Is it closed ?

No, those were all present in 0.8.3 as well.The only difference regarding the issue at hand is that, for technical reasons, the HTTP handler is now implemented in the core/foo_input_std (not sure which), while it was separate component for 0.8.3.

It is.

Ok. The last question i have for now is:

If i write an alternative http_reader, the internal one will steal my stream, because its from "http://xxx", so i must define an alternative Handler to deal with something like this: "httpgrab://" etc. right ?

You should only need to implement a minimum workalike of the http filesystem service, as well as a wrapper file service for that to open. It will also modify the link to http://, open that file, then create the file wrapper around it.

The wrapper should be aware of seeking, and optionally watch for on_playback_dynamic_info_track for track cutting.