Re: [RDD] Virtual Logs

[Lorne Tyndale]

Hi,

Figured it out. For some reason my rdvairplayd had not started properly.
 After I restarted my services the virtual logs and macros below started
working.

Lorne Tyndale


> 
> Hi,
>  
> I'm trying to figure out how virtual logs work, and running into some issues.
>  
> I've set up a macro that is:
>  
> LL 101 W_11_22_2020 -2!
>  
>  
> I'd thought this would load a log into the virtual log 101 and start to play 
> the first entry, but it doesn't seem to do anything, I don't get any audio.
>  
> The same exact macro replacing the "101" with "1", "2", or "3" works - loads 
> that log into the main or aux log in rdairplay and starts the playout.
>  
> I tried doing a:
> PN 101!
>  
> macro after the LL command above and that did not work either.
>  
> I also tried other virtual log machines, 102 and 103, but those did not work
>  
> What am I missing?
>  
> Lorne Tyndale
___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Touchscreen Monitor

[David Klann]

On 11/22/20 6:18 PM, Emir Yapıcı wrote:
> I have used Waveshare’s 10 inch hdmi touchscreen monitor with Rivendell. 
> It was pretty well but right click was not supported.
> 
> “Display” connected via HDMI and “touch” connected via USB, like a mouse.
> 
> 23 Kas 2020 Pzt, saat 02:49 tarihinde wa7skg  > şunu yazdı:
> 
> Is anybody using touchscreens with Rivendell? Does it work well? Are
> there any economical touchscreens available these days? Is it really
> worth the extra expense? How is the touchscreen connection handled?
> They
> used to be via VGA and a serial port, but nothing has serial ports
> anymore. Is it via HDMI and USB?
> 
> Thanks

And I have a Rivendell system with an Acer 22" HDMI touchscreen display. 
USB for the "mouse". Though the display can do 1920x1080, I like to set 
it to a lower resolution so the RDAirplay window isn't so tiny.

With that caveat, it works fine.

   ~David Klann

> 
> 
> -- 
> 73,
> Michael WA7SKG
> 
> "Any day you do not learn one new thing is a wasted day."
> ___
> Rivendell-dev mailing list
> Rivendell-dev@lists.rivendellaudio.org
> 
> http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
> 
> -- 
> *
> *
> *Emir YAPICI*
> 

___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Avoiding Use of ASI Audio Device

[David Klann]

Hi Fred,

Thanks for your thoughts on this issue I'm having.

On 11/22/20 12:38 PM, you wrote:
> On Nov 20, 2020, at 15:47, David Klann  > wrote:
> 
>> I have an old ASI 5020 card installed in a system running Rivendell
>> 3.4.1. I would like to use this card via audio routing with JACK, and
>> not directly in Rivendell.
>>
>> I can't seem to convince Rivendell to disregard its existence in the
>> system -- even by NOT loading the asihpi driver. Rivendell seems to be
>> aware of it without that driver loaded.
>>
>> Can someone help me understand how to prevent Rivendell from directly
>> using an ASI card?
> 
> There are at least two possible ways:
> 
> 1) Compile Rivendell with HPI support disabled, by adding the 
> ‘--disable-hpi’ switch to the ‘./configure’ invocation. This of course 
> means that you cannot use the stock RPMs.
> 

Although on my "lab" system I'm compiling current "development" versions 
of Rivendell, my goal is to make this (somewhat academic) experiment 
work with stock RPMs.

> 2) Load a version of the AudioScience HPI driver that lacks support for 
> that model. Since the ASI5020 was end-of-lifed some time ago by ASI, 
> chances are good that simply updating the ‘hpklinux’ package to the 
> latest version (available at 
> http://static.paravelsystems.com/audioscience/centos/7/).
> 

This *seems* like a reasonable approach! But ... the hitch is that the 
ALSA driver also uses the Audio Science firmware blobs. The snd-asihpi 
driver expects firmware files to be in /lib/firmware/asihpi. And as soon 
as I drop the file "dsp5000.bin" (the firmware for the 5020 card) into 
that directory Rivendell seems to "see" it and RDAdmin->Manage 
Hosts->[hostname]->Audio Resources reports that the Audio Science driver 
is loaded (even though I've explicitly blacklisted the asihpi driver):

 SUPPORTED AUDIO DRIVERS
   AudioScience HPI [4.14.03]
   JACK Audio Connection Kit [Generic]
   Advanced Linux Sound Architecture (ALSA) [1.1.8]

Note that even though I have the latest hpklinux driver package loaded 
(4.20.10-1.el7.centos from the Paravel repo), it appears to be picking 
up the version info from the firmware blob.

I realize that I can move the firmware blob out of /lib/firmware/asihpi 
and load the snd-asihpi driver *after* Rivendell has started. That *kind 
of* works.

Do you have any other thoughts on my understanding about what's 
happening with the firmware blob?

Thanks Fred!

   ~David

> 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

Re: [RDD] Touchscreen Monitor

[Emir Yapıcı]

I have used Waveshare’s 10 inch hdmi touchscreen monitor with Rivendell. It
was pretty well but right click was not supported.

“Display” connected via HDMI and “touch” connected via USB, like a mouse.

23 Kas 2020 Pzt, saat 02:49 tarihinde wa7skg  şunu yazdı:

> Is anybody using touchscreens with Rivendell? Does it work well? Are
> there any economical touchscreens available these days? Is it really
> worth the extra expense? How is the touchscreen connection handled? They
> used to be via VGA and a serial port, but nothing has serial ports
> anymore. Is it via HDMI and USB?
>
> Thanks
>
>
> --
> 73,
> Michael WA7SKG
>
> "Any day you do not learn one new thing is a wasted day."
> ___
> Rivendell-dev mailing list
> Rivendell-dev@lists.rivendellaudio.org
> http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
>
-- 

*Emir YAPICI*
___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

[RDD] Touchscreen Monitor

[wa7skg]

Is anybody using touchscreens with Rivendell? Does it work well? Are 
there any economical touchscreens available these days? Is it really 
worth the extra expense? How is the touchscreen connection handled? They 
used to be via VGA and a serial port, but nothing has serial ports 
anymore. Is it via HDMI and USB?


Thanks


--
73,
Michael WA7SKG

"Any day you do not learn one new thing is a wasted day."
___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

[RDD] Virtual Logs

[Lorne Tyndale]

Hi,
 
I'm trying to figure out how virtual logs work, and running into some issues.
 
I've set up a macro that is:
 
LL 101 W_11_22_2020 -2!
 
 
I'd thought this would load a log into the virtual log 101 and start to play 
the first entry, but it doesn't seem to do anything, I don't get any audio.
 
The same exact macro replacing the "101" with "1", "2", or "3" works - loads 
that log into the main or aux log in rdairplay and starts the playout.
 
I tried doing a:
PN 101!
 
macro after the LL command above and that did not work either.
 
I also tried other virtual log machines, 102 and 103, but those did not work
 
What am I missing?
 
Lorne Tyndale
___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Avoiding Use of ASI Audio Device

[Fred Gleason]

On Nov 20, 2020, at 15:47, David Klann  wrote:

> I have an old ASI 5020 card installed in a system running Rivendell 
> 3.4.1. I would like to use this card via audio routing with JACK, and 
> not directly in Rivendell.
> 
> I can't seem to convince Rivendell to disregard its existence in the 
> system -- even by NOT loading the asihpi driver. Rivendell seems to be 
> aware of it without that driver loaded.
> 
> Can someone help me understand how to prevent Rivendell from directly 
> using an ASI card?

There are at least two possible ways:

1) Compile Rivendell with HPI support disabled, by adding the ‘--disable-hpi’ 
switch to the ‘./configure’ invocation. This of course means that you cannot 
use the stock RPMs.

2) Load a version of the AudioScience HPI driver that lacks support for that 
model. Since the ASI5020 was end-of-lifed some time ago by ASI, chances are 
good that simply updating the ‘hpklinux’ package to the latest version 
(available at http://static.paravelsystems.com/audioscience/centos/7/ 
).

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