Re: [RDD] Important details missing from the OpsManual PDF

[Fred Gleason]

On Jun 29, 2021, at 16:45, Aaron M <99.5engin...@gmail.com> wrote:

> The manual just shows the following unhelpful information regarding 
> generating reports...
> 
> 
> https://ibb.co/H29K3Z2 
> 
> 
> What should be included is on the RivendellAudio.org  RivendellAudio.org> site
> 
> 
> https://ibb.co/mzBfsL7 

You’re confusing two different types of reports. The passage you cite in the 
Operations Guide refers to the ‘built-in’ reports that are included in 
rdlogedit(1). The design pattern for those types of reports (several other 
modules have them is well) is simply to operate on the current context of the 
module and display its results using the selected report viewer (as specified 
in the ‘Report Editor’ field RDAdmin->ManageHosts->[hostname]. OTOH, the Wiki 
page entry is referring to ‘as played’ reports, which are designed to be highly 
configurable and can configured to automatically generate on a set schedule.


> 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.

Agreed that some overarching discussion about reports in general, including the 
fact that there are two different basic types, would be a Good Thing. A section 
in the ‘Rivendell Administration’ section that discusses configuring (as 
opposed to merely using) such would good too.

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
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

[RDD] Important details missing from the OpsManual PDF

[Aaron M]

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