you need to have different clocks for 6:00, 12:00, 18:00 and 00:00 from all other hours, and all clocks need to have LOTS of music scheduled in them. HINT Schedule songs as 1 Minute Duration and schedule at least 30 in each hour. The actual times a re longer, but the clock is not for accurate times but for the sequence of events. Put a timed event at the start of each clock which bounces songs not needed from the previous hour. Your report looks like you have short scheduled hours. which brings the 12noon event up to 10am and the 1800 to 1530... unless you have a rogue or no clock in the grid somewhere.
Robert Jeffares Big Valley Radio 2011/10/17 Mágica FM Comunitaria <[email protected]> > ** > We use 1.7 + Rivendell Jack, running on Canaima GNU / Linux 3.0 a distro > based on Debian Squeeze. > > We have problems with scheduled events (timed events) by rdlogmanager > create a series of events that some legal requirements of our country should > sound at a specific time several times a day (national anthem), we mark this > event in "Timed Start "and" Use hard start time "and then hopped on a" > clock "where we carry all the cartridges that will sound then programmed > in the grid and send them to generate the log by date. The problem is that > the same event should be run at 6:00, 12:00, 18:00 and 00:00 but usually > active at 10:00 and 15:30 so incomprehensible to us. > > All the "clocks" we have armed with a total of 59:59:9. > > Someone has any idea may be happening? > > Jaime Mora > Amazonas - Venezuela > > > //////////////////////////////////////////////////////////////////////////////////////////// > > Usamos Rivendell 1.7 + Jack, corriendo sobre Canaima GNU/Linux 3.0 una > distro basada en Debian Squeeze. > > Tenemos problemas con los eventos programados (timed events), mediante > rdlogmanager creamos una serie de eventos algunos de ellos que por > exigencias legales de nuestro país deben sonar a una hora específica varias > veces al día (himno nacional), ese evento lo marcamos en "Timed Start" como > "Use hard start time" y luego lo montamos en un"clock" dónde cargamos todos > los cartuchos que sonarán luego, lo programamos en el grid y mandamos a > generar el log por fechas. El problema está en que el mismo evento debe > ejecutarse a las 6:00, 12:00, 18:00 y 00:00 pero por lo general se activa a > las 10:00 y a las 15:30 de manera incomprensible para nosotros. > > Todos los "clocks" los hemos armado con un total de 59:59:9. > > Alguién tiene idea de que puede estar sucediendo? > > Jaime Mora > Amazonas - Venezuela > -- > *Mágica 106.3 FM Comunitaria* > Usando 100% Software Libre - Canaima GNU/Linux 3.0 y Rivendell 1.7.x > Usuario Canaima GNU/Linux ** No: 542009 > Audio: http://magicafm.enamazonas.com / Noticias: > http://magicaradio.wordpress.com > Twitter: @magica_fm Identica: @magicafm > Coogle Talk: [email protected] > Tlf. (0058) 0248 6868084 > "Quien es miembro de una organización revolucionaria no ha adquirido > ninguna clase de derecho extra, lo que ha adquirido son deberes que tiene > que cumplir. "CHE" ** > > > _______________________________________________ > Rivendell-dev mailing list > [email protected] > http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev > >
_______________________________________________ Rivendell-dev mailing list [email protected] http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
