Download & Extend

Station Port to D7

Project:Station
Version:6.x-2.x-dev
Component:Programs
Category:feature request
Priority:normal
Assigned:Unassigned
Status:active

Issue Summary

Any plan ? pot

Comments

#1

Title:D7?» Station Port to D7

Changed title to be more descriptive.

Subscribing to port module owners comments on possible port.

#2

I'm guessing work on a 6.x-2.0 stable release will come before any port to D7.

#3

subscribe

#4

A comment from the maintainers would be appreciated, even if it's just a request for someone else to do the work ;)

#5

Based on a brief conversation with drewish, we should just tag 6.x-2.0 and move on.

I've been working on fullcalendar and field_collection as replacements for the custom station_schedule and station_playlist code. The station_program and station_catalog should be relatively easy to port. I've literally never used station_archive, but based on the fate of audio, it looks like that's a non-starter.

#6

In the years I have been thinking about this, I think a fresh start may call for a fresh take on what is needed. My goal is to provide a real-time API for the live audio stream, and I am turning back to Drupal to be the solution to do this.

Drewish, I know we have had a conversation in the past, but I have been giving this a lot of thought. I really believe that the host information begs to be entered real-time when the host is actually playing a track. If this can become the focus of playlist, count me in.

What I propose is a host entry form to be open in front of a live host, whether that host is presenting music or topical matter. From this form, I would like to assemble the needed data to feed stream encoders, RDS encoders, hd encoders, etc. Here is a sample entry form in it's most simple form: http://streameta.org/content/host-user-control.

Also, I have mocked up a demo that does refer to MusicBrainz for field data. Try typing in a song title here: http://rock.vu.wsum.wisc.edu/ and then selecting a title that pops up.

I have had a lot of contact with a lot of stations that do live audio, and it's pretty unanimous that we can do a better job of aggregating our host's metadata and making it available to all. "Content without metadata is just bits."

#7

Subscribing! We looked at "updating" the station module to D7 for our stations but abandoned the idea. We wanted it mainly for the scheduler for programs, but ended up gong a different route. I'll be keeping a close eye on this thread.

#8

Subscribing - This is really important that this update happens imho. I rely heavily on this module for my radio station and I cant update to D7, if only I have the cash to invest in dev work id pay for it!

#9

What do stations and users need most from a D7 station module? Here is my 2¢:

  1. Metadata API: What song is playing right now, and by whom? Is it being played live or is it from automation? If not a song, what is the topic of discussion? This information is never more relevant than right now.
  2. Metadata Logging: Who played what when? What was that talk show about?
  3. Scheduling: What's coming up? Is there a sub on? What are the details for a program.
  4. Archiving: Can the audio be fed or skimmed? Can start and stop be controlled by Metadata API for show starts and ends?
  5. Stream Linking and Statistics: Load balancing, HTML5 players, streaming server metadata, graphing.

These are the components required to semantically convey a live audio stream. This data, aggregated with a well designed "host entry" page will provide the data needed to socially graph our most precious resource, live hosts. It could also give them a place to get the information needed to put out over
I think modeling and creating a host entry form could be a great place to start a D7 station module.

#10

Has anyone tried running this through the Coder module to produce a basic patch that addresses some of the essential elements that have changed? There's certainly work that will need to be done with upgrading it to support Views 3 & Fields. It's quite likely that there won't be a clean upgrade path. However, there are lots of good reasons for there to be a D7 version of this module.

#11

I think mattrock has hit the nail on the head here, this is exactly what I have been craving from this module for a long time. If I had the skills to develop it myself I would. I think a simple D7 port would be ok for now with a major rewrite

#12

Greetings all. This issue remains in need. I'm guessing many of you, like myself, do not possess the skills to code yourselves. Yet, a live stream metadata handler remains a critically missing tool for broadcasters and your here because of the belief that Drupal 7 gorks for you.

I suggest the following:

  1. Move the discussion. I think the discussion which must be had can best fit at http://groups.drupal.org/radio
  2. Prioritize coveted features. In my case, a real-time webform for play entry in front of the host.
  3. Build a model. We will be able to convey our mission to those who do know how to code if we know exactly what to ask for.

If nobody objects, I will find or open a discussion at Google Groups and post a link in this thread. If you have objections, now is the time to reply.

#13

Please come to Drupalcon Denver 2012 and join our BOF to help direct this module's future: http://denver2012.drupal.org/content/drupal-managing-radio-stations

#14

Hi, any update from the Denver? What happened?