Get Started. It's Free
or sign up with your email address
ON Future Tools by Mind Map: ON Future Tools

1. processes

2. Douglas Arellanes -- http://camp.org

2.1. radio moderator

2.2. art degree

2.3. digital art

2.4. pirate radio

2.5. in prague since 1992

2.6. radio one

2.7. New node

3. tools

3.1. campsite

3.1.1. CMS

3.1.2. timeline based publishing

3.1.3. workflow

3.1.4. why not a radio version?

3.1.4.1. b92

3.1.4.1.1. robert klein

3.1.4.1.2. sennding a stream in amsterdam

3.1.4.1.3. sending back to serbia

3.1.4.1.4. timbuktu remotely radio control

3.1.4.1.5. if police come can you continue to send

3.1.4.1.6. crisis situation

3.1.4.1.7. camcaster

3.2. search for consesus for other stations

3.2.1. orange talk radio

3.2.1.1. program scheme

3.2.1.2. using jarm

3.2.1.3. live station switchover to preprogrammed

3.2.1.4. upload interface

3.2.1.5. jam is controling a audio switch

3.2.1.6. teams have te right to fill a slot

3.2.1.7. live sessions

3.2.1.8. upload playlists

3.2.1.9. live broadcast via live streams

3.2.1.10. 3 iterations for user interface

3.2.1.11. fading times are general fixed

3.2.2. live broadcast with streams

3.2.2.1. latency issue

3.2.2.2. ommiting time reference

3.2.2.3. reboot.fm - is allways streaming

3.2.2.4. time reference

3.2.2.4.1. tricks ...

3.2.2.5. radioX live shows

3.2.2.5.1. from studio

3.2.2.5.2. rest preprogrammed

3.2.2.6. New node

3.2.3. reboot.fm

3.2.3.1. no playlists on the central service

3.2.3.2. workflow is organised around shows

3.2.3.3. jingles where played on the full hour

3.2.3.4. permiisons for scheduler

3.2.3.5. publishing as posdcasts

3.2.3.6. google calendar for organizing

3.2.3.7. people want to use their tools

3.2.3.8. use cases of private and community radio are different

3.2.4. thomas b. disigner

3.2.4.1. question how to organise workflows

3.2.5. problems to face

3.2.5.1. range of softskills

3.2.5.2. diffrent use of existing tools

3.2.5.3. standars

3.2.5.4. creating playlists for royalties

3.2.5.5. metadata leads to hard work

3.2.5.6. shazam - fragmentation of song information

3.2.5.6.1. echonet

3.2.5.6.2. shazaam

3.2.5.6.3. gracenote

3.2.5.6.4. musicbrainz fingerprinting

3.2.5.7. "home grown" character of existing archive and software

3.2.5.8. duties

3.2.5.9. station has a broader concern about listners then the single partizipating listener

3.2.5.10. stream ripping

3.2.5.11. public archive contains copyrighted material

3.2.5.12. radio specific playout

3.2.5.13. audioprocessing for finaliseing playout (comprassor/limiter)

3.2.5.14. bunch of hardware involved

3.2.5.15. audio routing to integrate VOIP / SKYPE

3.2.6. OPEN RADIO CONFERENCE

3.2.6.1. upcoming in 17t October in Berlinh October in Berlin

3.2.6.2. flossmanuals booksprint

3.2.6.3. alot of HOWTOS

4. Herman Huber

4.1. radiofabric

4.2. own software

4.3. developed 2004

4.4. studied computer sience

5. Norbert Gnauer

5.1. Orange radio

5.2. vienna

5.3. involved in IT

5.4. involved as moderator

6. Paul baranowsky

6.1. founder of campcaster

6.2. had founding

6.3. planning a successor of campcaster

6.4. take what is out there

6.5. building tools

6.6. best practise

6.7. programming since 8

7. Nick von Frankenberg

7.1. radioX

7.2. musc content

7.3. more user side

7.4. need tools with wide range

8. artist

8.1. New node

9. jonas Oohrstrom

9.1. programmed the medialibary

9.2. background services

9.3. for metadata services

10. chris weaver

10.1. resonance.fm

10.2. small station

10.3. small budget

10.4. experimental broadcasting

10.5. how to do that

10.6. how for free

11. pit schulz

11.1. netculture

11.2. 2000 radio

11.3. rebbot.fm

11.4. haus der ulturen der welt

11.5. berlin based

12. wishlist

12.1. interfaces

12.1.1. software

12.1.1.1. build modules for other CMSs

12.1.1.1.1. now playing

12.1.1.1.2. commenting

12.1.1.1.3. calendar / schedule

12.1.1.2. automated reporting

12.1.1.2.1. royalty holders

12.1.1.2.2. ads buyers

12.1.1.2.3. feedback for content providers

12.1.2. user interface

12.1.2.1. interaction design

12.1.2.1.1. see what you can change

12.1.2.1.2. simple first

12.1.2.1.3. grained access

12.1.2.2. card player - jingle bank

12.1.2.3. "five years of country interupted by ads" - button

12.1.3. different views on the same data

12.1.4. open hirarchy of container formats

12.1.5. "making the invisible visable"

12.1.5.1. make the interface simpler

12.2. standards

12.2.1. meta data convention

12.2.2. workflow

12.2.3. iptc - sports ML news ML

12.2.4. ical - program exchange

12.3. archive

12.3.1. easy accessible

12.3.2. archiving of broadcast

12.3.3. interconnectivity

12.3.4. automations

12.3.4.1. broadcast archive

12.3.4.2. live tagging / recognition

12.3.4.3. live updates

12.3.5. user tagging of tracks

12.4. playout

12.4.1. programmable playout (card master)

12.4.1.1. myriad

12.4.1.2. mair list

12.4.2. music discovery

12.4.3. transitions

12.4.4. prelisten

12.4.5. live sessions

12.4.6. integrate IRC/Skype back channel

12.4.7. control over crossfades

12.4.8. logging

12.5. core components

12.5.1. automatic tagging services

12.5.2. extensible RESTful API

12.5.3. scheduler

12.5.4. player

12.5.5. medialibary

12.5.5.1. track metadata

12.5.6. linking services

12.5.7. community based interactions

12.5.8. fine grained access control

12.5.9. playlists

12.6. abstract playout system

12.6.1. liquidsoap

12.6.2. mpd

12.6.3. streaming integrated

12.6.4. integrated audio processing

12.7. sustainabilty

12.7.1. $$$

12.7.1.1. ads schedule and proof

12.7.1.2. premium SMS dedications

12.7.1.3. club membership

12.7.1.4. donations

12.7.1.5. workshops

12.7.1.6. paid access

12.7.1.7. public founding criteria

12.7.1.7.1. overwievs of activity

12.7.1.7.2. statistics of listeners

12.7.1.7.3. spending reports

12.7.1.7.4. the whole workflow reflects also reporting

12.7.2. staff training

12.7.3. documentation

13. New node

14. afternoon session

14.1. archive

14.1.1. usage?

14.1.1.1. used only for prescheduled playout

14.1.1.2. ... not used for radio DJ

14.1.1.3. ...

14.1.2. ... metadata make the value

14.2. standards

14.2.1. dublin core

14.2.2. smil

14.3. New node