A conference before NAB might be an issue for Fred and Scott. Not to speak for them but Saturday and Sunday are busy as they set up for the show. Then there are various other user groups both days such as Nautel, Gates Air, BE etc. I get there the previous Tues because of the Public Radio Engineers Conference(PREC). If it happened at NAB one of the evenings may be best. IMHO.
Darrell McCalla WBHM FM 90.3 205-440-0977 Cell 205-934-WBHM Office www.wbhm.org > On Nov 6, 2014, at 8:04 PM, "[email protected]" > <[email protected]> wrote: > > Send Rivendell-dev mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Rivendell-dev digest..." > > > Today's Topics: > > 1. Re: Conference? (Cowboy) > 2. Re: Conference? (Brian McKelvey) > 3. Re: Conference? (Cowboy) > 4. Re: Conference? (Brandon Sossamon) > 5. Re: Conference? (Brian McKelvey) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 6 Nov 2014 13:19:46 -0400 > From: Cowboy <[email protected]> > To: [email protected] > Subject: Re: [RDD] Conference? > Message-ID: <[email protected]> > Content-Type: text/plain; charset="iso-8859-1" > >> On Thursday 06 November 2014 11:08:59 am you wrote: >> ?The NAB >> is great but you won't get the much needed, thorough, explanation of >> Rivendell. > > I disagree ! > We can make it happen. > I will agree it's not going to happen standing at the booth *during* > the show, but that's not all that's available. > > Moreso, schedule your flight a day early, and you might be surprised > at how much can be had in that "before the show" period. > A day after might also be possible. ( as well as easing flight arrangements ) > If you bought a support agreement, possibly both ! ;) > > -- > Cowboy > > http://cowboy.cwf1.com > > The opposite of a profound truth may well be another profound truth. > -- Bohr > > > ------------------------------ > > Message: 2 > Date: Thu, 6 Nov 2014 10:23:06 -0800 > From: Brian McKelvey <[email protected]> > To: Jim Stewart <[email protected]> > Cc: "[email protected]" > <[email protected]> > Subject: Re: [RDD] Conference? > Message-ID: <[email protected]> > Content-Type: text/plain; charset="us-ascii" > > I second the move to documentation. I honestly don't have nearly as much the > Rivendell experience as many others here. I have it installed on a machine > in my office but am not using it for anything still, despite interest, > because the task of learning how to use to its full potential is daunting. > For me, however, it's not daunting from a technical perspective: I'm totally > confident in my ability to get up and running on whatever kind of setup I > would want to build. I'm a software engineer who has been working deeply and > daily with Linux since 1999. The part that's difficult for me is all the > legacy and industry-specific concepts, terminology, and jargon from the radio > industry. > > I started playing with Rivendell in about 2003 when I was going to school at > Biola University, studying film audio engineering. There was a > basically-dead on-campus radio station that had been running a Winamp > playlist on repeat, and the studio was full of old and broken gear and badly > needed a new paint job, console repairs, new (non-fluorescent) lighting, > etc., and also needed an actual radio automation system. My friend and I > were the only ones who had any interest, so we went in and re-did everything > ourselves on a shoestring budget. > > Because of my Linux experience, I was able to set it up with an NFS server to > host the audio files and act as Windows domain controller with roaming > profiles for the students to have their own accounts on the production > machines and be able to add content to watch folders from their dorm rooms, > etc. I even wrote custom content ingestion and processing scripts. > > What was missing for me, and still is to this day, is understanding what a > lot of the radio-specific terminology even means. The jargon used in radio > is so unique and distinct from other areas of broadcast and especially > different what I was most involved in, film production. The radio industry > seems to have different or special names for things things oftentimes that > are different from how everyone else refers to them, and there are a lot of > radio specific concepts or legacy concepts or metaphors that are long-since > obsolete and probably should be done away with but we keep around because > their usage is so entrenched amongst industry veterans. Referring to "carts" > and "cuts" for example. Someone coming into this arena who's never worked > with magnetic tape before and lived in the digital realm their entire lives > wouldn't have the slightest idea what a "cart" was. > > I guess my overly long-winded point is, I agree there is a very real need for > documentation. And not specifically technical documentation, but information > about what radio automation even is, a complete rundown of exactly what it > is, and what all the other parts that go with it are (3rd party traffic > scheduling software, for example.) > > I had to figure those terms and concepts out on my own, with little help or > guidance, mostly by trial and error, pushing buttons and entering data to see > what happened. There's still a good easily 50% of the concepts and UI in > Rivendell that I still have absolutely no idea whatsoever what it might be > used for. "Clocks," "dayparts", "scheduler codes", I have only a > surface-level idea about those things, but not enough to really understand > how to use the music scheduler, so I've always been stuck with manually > created logs. For years, up until recently, I had absolutely no idea what on > earth was meant by "traffic." The only thing I could imagine was that it had > something to do with reporters talking about morning-drive freeway > congestion. I understand now that it has to do with scheduling and tracking > ads, PSAs, promos, etc., but only a surface level understanding... There's > probably more that's encompassed? (And "traffic?" Really? What on earth do > ads and promos have t > o do with "traffic?" I'm sure there's a totally logical and historical > explanation for why it's called traffic, but given that I can't imagine what > it might be, that's a clear indication that we ought to start migrating > towards a more modern and clear term....) > > Mind you, I'm extremely adept at using Google to find answers. I rarely post > asking for help, especially when I feel like I should be able to find the > answers on my own. But Google isn't always terribly helpful at finding > information about concepts and terminology that are uniquely used by > radio-industry professionals. It's almost like the lexicon of knowledge is > only picked up through on-the-job involvement and exposure to it, and then > when people do post or discuss things online, there's a base assumption that > everyone already knows the concepts. I've seen relatively few resources > geared toward someone from the outside trying to learn the language. > > The concepts & terminology around music and traffic scheduling, for example, > are so daunting that on multiple occasions I'd almost considered diving into > the MySQL schema and just writing my own music scheduling system. While that > would be a reasonably serious undertaking, it's often felt more approachable > to me than trying to figure out the utilities that are already built in. > > Short version is, I'd love resources to help me understand the depth of what > Rivendell can do and how to use it, written with the assumption that the > reader may be technically proficient, but has absolutely zero exposure to the > language and metaphors of the radio industry. (Technical documentation would > be a separate document.) > > I guess my main point is that for me, the approachability issues I experience > with Rivendell aren't about technical issues, they're about old radio > industry jargon terms and concepts, knowledge of which seems to be taken for > granted in most of the documentation that is already written. > > Brian > > Sent from my iPhone > >> On Nov 6, 2014, at 7:48 AM, Jim Stewart <[email protected]> wrote: >> >> I agree that a traditional conference might be a bit ambitious. For >> example, I live "only" 700 miles (1000 KM) away and probably wouldn't even >> make it. >> >> >> What I think would benefit Rivendell the most is a push to update the Wiki >> so that it is: >> >> >> 1) More up to date >> >> a) A more complete and updated users guide (Existing is very good, but need >> updating) >> b) A useful administrators guide (Existing is only a template, and even >> that needs work) >> >> 2) Contains more "step-by-steps" for newbies (Including some "quick-starts" >> to handle getting most people up and going). I'm thinking it is difficult >> for newbies to even figure out where to start! >> >> 3) Contains a LOT more details on administration and initial setup (see >> admin guide above) >> >> 4) Then more examples of peoples' "unusual" setups. >> >> >> 5) Contains lots of troubleshooting sections so fewer are simply lost when >> something goes wrong. >> >> >> I for one am guilty of not participating in this yet as I think I have >> several unusual things I've gotten Rivendell/LInux to do on our station that >> others might be interested in (and that I brag about to those running many >> of those "other" commercial systems). >> >> >> A single conference tends to only benefit those who attend at the time, >> where as fixing up the Wiki will provide a lasting benefit for all of us and >> many new users. It took me quite awhile to get things working for us, and I >> had a pretty good Linux background, but had never used Jack audio before >> which in itself had a steep learning curve. I currently struggle with many >> aspects of MySQL which I previously had little experience with. >> >> >> >> _______________________________________________ >> Rivendell-dev mailing list >> [email protected] >> http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > <http://caspian.paravelsystems.com/pipermail/rivendell-dev/attachments/20141106/dd48f695/attachment-0001.html> > > ------------------------------ > > Message: 3 > Date: Thu, 6 Nov 2014 15:13:24 -0400 > From: Cowboy <[email protected]> > To: [email protected] > Subject: Re: [RDD] Conference? > Message-ID: <[email protected]> > Content-Type: text/plain; charset="iso-8859-1" > >> On Thursday 06 November 2014 01:23:06 pm Brian McKelvey wrote: >> ?It's almost like the lexicon of knowledge is only picked up through >> on-the-job involvement and exposure to it, > > We call it "job security." :) > > Truth be told, you are right ! > Like many fields, the terms and jargon *as used* are often picked up > only through association with the field. > As an apprentice, if you will. > > -- > Cowboy > > http://cowboy.cwf1.com > > The opposite of a profound truth may well be another profound truth. > -- Bohr > > > ------------------------------ > > Message: 4 > Date: Thu, 6 Nov 2014 13:45:55 -0600 > From: Brandon Sossamon <[email protected]> > To: [email protected] > Subject: Re: [RDD] Conference? > Message-ID: > <cahochroit_rxp-ngyu13w32f-4nk1sdp-tsggeu-6dqeqek...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > I'd support a conference but it may make more sense to host a webinar for > those too far away or without time to dedicate to the travel. At minimum, > a YouTube channel for how-to's. Perhaps folks could submit suggestions for > content and a topic (or a topic suggested by more than one individual) is > chosen each week and a video is produced. I've found some Linux YouTube > channels are helpful just to understand it in a general sense which has > helped me grasp the inner workings of RD a little better/faster. > > brandon sossamon > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > <http://caspian.paravelsystems.com/pipermail/rivendell-dev/attachments/20141106/9aee2042/attachment-0001.html> > > ------------------------------ > > Message: 5 > Date: Thu, 6 Nov 2014 18:03:46 -0800 > From: Brian McKelvey <[email protected]> > To: Brandon Sossamon <[email protected]> > Cc: "[email protected]" > <[email protected]> > Subject: Re: [RDD] Conference? > Message-ID: <[email protected]> > Content-Type: text/plain; charset="us-ascii" > > This is a great idea! YouTube is awesome for this kind of thing. I use it > constantly to learn about other things, particularly hobbyist electronics > (Arduono, raspberry Pi, etc.), and the maker movement. I'd offer to work on > making a few videos but I'm afraid I wouldn't be best suited to it because of > the aforementioned issues. > > Anyone know of good screencast-oriented video capture software for Linux? > > Brian > > Sent from my iPhone > >> On Nov 6, 2014, at 11:45 AM, Brandon Sossamon <[email protected]> >> wrote: >> >> I'd support a conference but it may make more sense to host a webinar for >> those too far away or without time to dedicate to the travel. At minimum, a >> YouTube channel for how-to's. Perhaps folks could submit suggestions for >> content and a topic (or a topic suggested by more than one individual) is >> chosen each week and a video is produced. I've found some Linux YouTube >> channels are helpful just to understand it in a general sense which has >> helped me grasp the inner workings of RD a little better/faster. >> >> brandon sossamon >> >> _______________________________________________ >> Rivendell-dev mailing list >> [email protected] >> http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > <http://caspian.paravelsystems.com/pipermail/rivendell-dev/attachments/20141106/8009d69f/attachment.html> > > ------------------------------ > > _______________________________________________ > Rivendell-dev mailing list > [email protected] > http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev > > > End of Rivendell-dev Digest, Vol 19, Issue 11 > ********************************************* _______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
