Closed (won't fix)
Project:
Embedded Media Field
Version:
6.x-1.x-dev
Component:
Providers
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
25 Jun 2009 at 12:16 UTC
Updated:
4 Aug 2009 at 19:15 UTC
Jump to comment: Most recent file
Comments
Comment #1
jspayne commentedI guess it shouldn't be assigned to me if I want someone else to review it...
Comment #2
winston commentedjspayne,
This is so weird. I was just working on creating a provider for archive audio tonight when I bumped in to this issue! I was submitting a bug report against the base emfield.module as I was trying to improve the way the provider gets the xml files (taking out the screen scraping code).
Anyway, I'll probably be done with mine tomorrow. There are a few differences between mine and yours. For example I'm planning to provide a richer set of data for theming purposes, and also provide some alternate theming functions to demonstrate how to use a couple of commonly used audio players (1pixelout, etc.). Also, taking out the above mentioned screen scraping code in favor of something more direct.
That said, I'd be happy to collaborate on it with you. I would point out that the emfield maintainers are no longer adding new providers to the base emfield module. Instead they are creating them as new projects with the intent that when media module comes online they will be upgraded to that (which I'm sure will take some effort).
Here are a couple of examples...
http://drupal.org/project/media_viddler
http://drupal.org/project/media_flickr
In the flickr case you'll notice ONLY the photoset functionality was added (basically treated like video) since flickr image is already supported in emfield. There are a few others including one I did a couple of months ago (all of which start with media_ in the name)
Anyway, if you want to help me maintain this (or take ownership) you'll need CVS access. Go here for how to do that - http://drupal.org/cvs-application/requirements.
Let me know. I'm probably going to do the CVS commit tomorrow as I've had it on my to do list for some time now (been using archive.org for its audio hosting for a long time).
Peter
Comment #3
jspayne commentedYou can have it - I wasn't really interested in maintaining it, I just didn't want to have to fiddle around every time I upgrade the module.
Jeff
Comment #4
winston commentedFair enough. I did find it strange that there wasn't an audio provider created previously. Archive.org is very good for audio.
- Peter
Comment #5
robloachWould the Archive.org video provider work for these?
Comment #6
jspayne commentedI tried using the video provider, but it doesn't work out of the box. It needs to search for the right media file types & set up the player correctly, so it was just easier for me to clone the provider and fix it, rather than put a bunch of conditional code in.
Comment #7
winston commentedRob, jspayne,
I did create a project for this (as it appears that this is the direction the maintainers prefer when adding new providers - see media_flickr for example.
The project is at media_archive
There are a couple of differences between archive.org and some of the other audio providers. For example, archive.org allows multiple tracks in a single item. I'm working for support on that right now, but having problems related to this issue - emfield_request_xml xml parsing routine problem.
You can check the issue queue for media_archive to see the additional enhancements in progress.
Comment #8
winston commentedQuick update.
Just committed the multi-track support.
Ended up having to fork the emfield_request_xml function, but will be revisiting that in the emfield issue queue.
Does the emfield provider perhaps want to set this to "won't fix"?
Comment #9
aaron commentedyep; thanks for taking that on winston & jspayne!
the version 2 of emfield, and media in d7, will remove all provider files entirely, leaving them up to individual modules (and stream wrappers for d7). i'll update the project page to point to the new media archive module, and v2 would need to include video & audio (though i'll coordinate that with you, as i suspect there will be big changes to the structure at that point, hopefully for the better).