Hi all!
The manual just shows the following unhelpful information regarding generating
reports...
https://ibb.co/H29K3Z2
What should be included is on the RivendellAudio.org site
https://ibb.co/mzBfsL7
I would think there should be some mention in the opsmanual pdf about the
format of the Admin:Manage Reports: Export Path requirements. I didn't expect
a path to include a filename template to be required because that isn't
mentioned in the opsmanual.pdf file.
Just a suggestion to make adoption easier for others.
On another note: if I am editing an event and moving an item in pre-import
tracks, and I click a little too fast it crashes RDLogManager.
That's no fun.
This is all Rivendell 3.6.1 under the so-called stable CentOS version.
I will agree the RDAirPlay is awesomely stable, but the Log Manager is quite
touchy about how fast you operate it. I would think a quad core 3.8Ghz system
wouldn't require deliberate pauses between moving an item up or down a queue
list.
For now the solution is clear, but painful for a fresh install where I will
have to import thousands of songs and liners and ads and then build clocks and
schedules.
I can live with it, but it is disappointing.
I am getting close to having to figure out the macro conventions and scripting.
I am confident that it will work, but there have been some unexpected issues
even after reading the opsmanual cover to cover, as it lacks details found only
online.
Thanks to everyone involved in making Rivendell better and better.
Best regards,
Aaron
___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
