I learned enough CVS to checkout Fred's tag. The Changelog says the bug was confined to rdadmin/edit_station.cpp. Originally I attached the file, but it seems that the mailing list didn't like that, so apologies if this is a repeat post. Anyway, replacing the 2.8.1 version of the file with this one worked to fix the issue. Thanks for the patch Fred.
I'm going to start a new thread on using the macro carts that can play at cue time for GPIO. Thanks, Max Goldstein Operations Director WMFO Medford On Sat, Mar 8, 2014 at 5:13 PM, Max Goldstein, Operations Director < [email protected]> wrote: > I learned enough CSV to checkout Fred's tag. The Changelog says the bug > was confined to rdadmin/edit_station.cpp. I've attached the file here for > anyone who would otherwise have to go hunting for it. Rather than apply > patches, replacing the 2.8.1 version of the file with this one worked to > fix the issue. Thanks for the patch Fred. > > Thanks, > > Max Goldstein > Operations Director > WMFO Medford > > > On Wed, Mar 5, 2014 at 2:21 PM, Max Goldstein, Operations Director < > [email protected]> wrote: > >> I certainly won't deny anything Brian has said re:git and GitHub. For my >> immediate problem of audition controls, (1) thanks for the fix Fred (2) >> since I don't want to dive into cvs, can someone please attach a diff from >> which I can manually patch the 2.8.1 source? Provided it's not too much >> code, or too complicated, I'd like to do that rather than wait for a new >> release (though that's my other option). >> >> Thanks, >> >> Max Goldstein >> Operations Director >> WMFO Medford >> >> >> On Wed, Mar 5, 2014 at 2:14 PM, Brian <[email protected]> wrote: >> >>> Any chance we'll see the Rivendell code base move to Github at some >>> point? CVS is a world of excruciating pain by comparison. Almost nobody >>> uses it anymore, and fewer and fewer people feel comfortable with it as >>> time goes on, so it has the effect of making the source code repository >>> feel a bit more inaccessible and isolated from the world. >>> >>> I had to work with CVS for three years when I worked for Ticketmaster, >>> until they moved to Subversion, which was marginally better. Both are a >>> world of extreme hurt compared to Git, that I wouldn't wish on my worst >>> enemy. I'll never, ever, ever go back. >>> >>> If nothing else, Github makes it extremely easy to browse the code and >>> commit history on the web so it's quick and painless to explore and >>> investigate the code without even having to check out a copy. Further, it >>> makes the process of submitting and merging patches almost criminally >>> simple. >>> >>> I'd be willing to bet that moving to Github would have a noticeable >>> positive impact on the number of useful code contributions and improvements >>> you receive. And the process for reviewing the code, sending notes to the >>> contributor, waiting for them to make the requested improvements, and then >>> merging the new changes into the master branch is brain-dead easy. As >>> opposed to CVS... where branching and merging is so frighteningly complex >>> and difficult and error-prone that it's the stuff of nightmares, and that >>> fear keeps people from even bothering. >>> >>> Brian >>> >>> >>> >>> >>> On Wed, Mar 5, 2014 at 10:03 AM, Fred Gleason >>> <[email protected]>wrote: >>> >>>> >>>> On Mar 5, 2014, at 09:54 51, Max Goldstein, Operations Director < >>>> [email protected]> wrote: >>>> >>>> > Fred, have you been able to reproduce the issue and find a config >>>> solution? >>>> >>>> Confirmed, and fixed in CVS-v2. >>>> >>>> >>>> > Or if this is a bug, can you spot us a point release? >>>> >>>> I've tagged it in CVS as 'cue_assignment_fix'. >>>> >>>> Cheers! >>>> >>>> >>>> >>>> |-------------------------------------------------------------------------| >>>> | Frederick F. Gleason, Jr. | Chief Developer >>>> | >>>> | | Paravel Systems >>>> | >>>> >>>> |-------------------------------------------------------------------------| >>>> | A room without books is like a body without a soul. >>>> | >>>> | -- Cicero >>>> | >>>> >>>> |-------------------------------------------------------------------------| >>>> >>>> _______________________________________________ >>>> Rivendell-dev mailing list >>>> [email protected] >>>> http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev >>>> >>> >>> >>> _______________________________________________ >>> Rivendell-dev mailing list >>> [email protected] >>> http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev >>> >>> >> >
_______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
