Re: [RDD] Remote Voicetracking Via Web Interface
Keith, Thanks for checking this out. I developed this for a very specific need and wanted to put it out into the wild to see if anyone with more PHP skills would take this and develop it further. It meets our needs right now for several DJ's to track from live remotes on their iPhones and to contribute shows - so there are no immediate plans to develop more functionality. To get this to mimic what is in the Voicetracker application (where you can set segue points), there is an enormous amount of work to be done. You would need to write a WebRTC interface into CAED to get precise timing and to hear to the segue. In looking at a design for our needs, we decided that this was not necessary or even desired. If the talking points are set on the library, this actually will allow the radio host to sound optimal. Rivendell does a really good job of mixing and we don't want to overburden the hosts or want them messing with the points. This uses the Rivendell API to ingest the audio object from the browser. You could create a custom ingest script that takes the audio and uses SOX to compress the audio to make it louder, trim the edges, etc.. This may be an enhancement I would add. What might be an enhancement would be to create a shadow library of MP3's to hear the intro/outro. This would be necessary for an implementation of RDLibrary on the web. This would also require a daemon to continuously update the library - or an implementation of CAED that speaks WebRTC (as mentioned above). I think it's a very good direction to go for Rivendell to support remote users, although it is nontrivial. Brian *--* *Brian P. McGlynn* bmcgl...@geneseemedia.net ᐧ On Tue, Aug 6, 2019 at 2:25 PM Keith Thelen wrote: > Was excited to see this a few days ago. Finally got a chance to test it > this afternoon… so far it seems to work nicely! > > My question is, do you - or anyone else - have plans to develop this > further? > > I have only vague notions of what it’d take to achieve similar > functionality to the local voicetracker (ie. rendering starts/ends of > adjacent cart/s to create temporary, low-bitrate intro/outro “previews” to > play in the browser; creating something that can provide provide graphical > segue adjustment in the browser, etc). > > But if/when that happens, it’ll be a great day for Rivendell - and indeed, > the world! > > > > - > Keith Thelen > ___ > Rivendell-dev mailing list > Rivendell-dev@lists.rivendellaudio.org > http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev > ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Remote Voicetracking Via Web Interface
Was excited to see this a few days ago. Finally got a chance to test it this afternoon… so far it seems to work nicely! My question is, do you - or anyone else - have plans to develop this further? I have only vague notions of what it’d take to achieve similar functionality to the local voicetracker (ie. rendering starts/ends of adjacent cart/s to create temporary, low-bitrate intro/outro “previews” to play in the browser; creating something that can provide provide graphical segue adjustment in the browser, etc). But if/when that happens, it’ll be a great day for Rivendell - and indeed, the world! - Keith Thelen ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Remote Voicetracking Via Web Interface
Here is the latest version of the Remote Voicetracker based on the latest Rivendell (3.0). https://github.com/bpm1992/rivendell/tree/rdweb/web/rdphp The changes are visible here: https://github.com/bpm1992/rivendell/pull/new/rdweb To get this to work, you will need to do the following: 1. Install PHP and HTTPS for Apache. HTTPS is mandatory to get the Audio libraries to work in HTML5 2. Clone my repository into /usr/local/src/rivendell 3. Create a directory called /usr/local/rdweb 4. Copy the contents of /usr/local/src/rivendell/web/rdphp into /usr/local/rdweb 5. Copy /usr/local/src/rivendell/conf/rdweb.conf.in to /etc/httpd/conf.d/rdweb.conf 6. Edit /etc/httpd/conf.d/rdweb.conf and change the directories to point to /usr/local/rdweb 7. Restart HTTPD 8. Login to the Voicetracker with https://[IP_address]/rdweb 9. User a Rivendell user that has Web API rights 10. Try out remote voicetracking *Note: * This is meant for developer-level people familiar with PHP coding. This is only tested on Centos 7 and has a dependency on its native PHP version. Later versions of PHP (v7) have not been tested and will likely have issues. Please take a look at this and please make changes and enhancement to it. Rivendell is an excellent Automation system - and I believe the one thing lacking from Rivendell compared to the other commercial systems is the ability to remote voicetrack -- and this can be the start of getting it to work. This works with Chrome, my iPad (using Safari) and my iPhone. I have not tested on Android and do not plan to. If you are a developer, please play around with this, make changes, enhancements and send me some pull requests. I would be delighted to make a pull request to put this into the main code repository so it can evolve with Rivendell. If you are not a developer, this could be very difficult to set up and I'm unfortunately not in a position to be able to support this due to time restrictions. Future Enhancements: 1. Group-level permissions 2. General Clean-Up 3. RDLibrary Interface to upload/manage the music library 4. RDLogmanager Interface to generate/review logs *--* *Brian P. McGlynn* bmcgl...@geneseemedia.net On Sat, Aug 3, 2019 at 10:56 AM Fred Gleason wrote: > On Aug 3, 2019, at 10:24, Brian McGlynn wrote: > > Where should I base it in the source tree? I call it "RDWeb" and could > put it into a directory with that name. It installs the Javascript and PHP > code into /usr/local/share/rdweb and there are configuration files for > Apache that need to be installed. Right now, it is all manual to install. > In contributing it to the community, I am hoping to get some help in > cleaning it up a bit. > > > In the Rivendell build system, there are two arguments to ‘configure’ that > control this sort of thing: > > --libexecdirdir= > The location to install web content (both static and scripts) > Value on CentOS 7: ‘/var/www/rd-bin’ > > --sysconfdir= > The location to install httpd configuration snippets > Value on CentOS 7: ‘/etc/httpd/conf.d’ > > (Note that the ‘Value on CentOS 7’ fields are merely examples; on other > distros these paths can be and are different!) > > If you’re using Autoconf for your build system, then just use the > @libexecdir@ and @sysconfdir@ variables to get the target paths. If > you’re just using a flat Makefile, then provide some variables with > reasonable defaults and some directions to the user to set these to the > desired locations. > > > This uses a mix of the Web API and direct access to the database. At > present, it needs to run on a machine with Rivendell installed since it > pulls database configuration from /etc/rd.conf. That could easily be > modified. > > > Ouch! Why the DB access? Are we missing something from the Web API that > you need? > > 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 > ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Remote Voicetracking Via Web Interface
On Aug 3, 2019, at 10:24, Brian McGlynn wrote: > Where should I base it in the source tree? I call it "RDWeb" and could put > it into a directory with that name. It installs the Javascript and PHP code > into /usr/local/share/rdweb and there are configuration files for Apache that > need to be installed. Right now, it is all manual to install. In > contributing it to the community, I am hoping to get some help in cleaning it > up a bit. In the Rivendell build system, there are two arguments to ‘configure’ that control this sort of thing: --libexecdirdir= The location to install web content (both static and scripts) Value on CentOS 7: ‘/var/www/rd-bin’ --sysconfdir= The location to install httpd configuration snippets Value on CentOS 7: ‘/etc/httpd/conf.d’ (Note that the ‘Value on CentOS 7’ fields are merely examples; on other distros these paths can be and are different!) If you’re using Autoconf for your build system, then just use the @libexecdir@ and @sysconfdir@ variables to get the target paths. If you’re just using a flat Makefile, then provide some variables with reasonable defaults and some directions to the user to set these to the desired locations. > This uses a mix of the Web API and direct access to the database. At > present, it needs to run on a machine with Rivendell installed since it pulls > database configuration from /etc/rd.conf. That could easily be modified. Ouch! Why the DB access? Are we missing something from the Web API that you need? 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
