Re: [RDD] 3.x and asi cards.
On 28-Feb-20 10:36, Timothy Elwell wrote: you do still need the ASI for MP3 as it's a licensing issue with software MP3 due to patents. I notice from https://en.wikipedia.org/wiki/MP3#Licensing,_ownership_and_legislation : "... patents required to implement MP3 expired in most countries by December 2012, 21 years after the publication of ISO CD 11172..." and "An exception is the United States... If only the known MP3 patents filed by December 1992 are considered, then MP3 decoding has been patent-free in the US since 22 September 2015, when U.S. Patent 5,812,672, which had a PCT filing in October 1992, expired. If the longest-running patent mentioned in the aforementioned references is taken as a measure, then the MP3 technology became patent-free in the United States on 16 April 2017, when U.S. Patent 6,009,399, held and administered by Technicolor, expired. As a result, many free and open-source software projects, such as the Fedora operating system, have decided to start shipping MP3 support by default, and users will no longer have to resort to installing unofficial packages maintained by third party software repositories for MP3 playback or encoding." (Wikipedia is not necessarily an accurate reference and I am not a lawyer.) R ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Passing ATH value to Statury Licence Report in command line
Just out of interest, those of you who are reporting to SoundExchange, how do you derive the required ISRC or Label for your reporting? Automated RepMatch lookup? ACR? Some other method? Or do your music sources include ISRC on import? Thanks! --R On 20-Jan-20 00:25, Rob Landry wrote: What SoundExchange requires of us is a list of all the songs we play in a month, and the number of "performances" for each, that is, the number of listeners who heard each song. This is produced by a script that accepts as input a) the Icecast server log for the month, and b) the station's playlist for the month. Rob ___ 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] rdimport - Suggested ingestion parameters?
Excellent! Thanks very much for the detailed response, a great help! -R On 16-Nov-18 19:48, Fred Gleason wrote: The usage is very similar to that of rdimport(1)... ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] rdimport - Suggested ingestion parameters?
Fred, As I am a novice here, I would be most grateful if you could do me the favour of providing an example usage of nested-import.pl, just so that I get it right first time. The command-line invocation I am using currently would be: rdimport --verbose --segue-level=-10 --autotrim-level=-30 --normalization-level=-10 MUSIC * How would I call the Perl script with these parameters? Many thanks --Richard E On 16-Nov-18 17:17, Fred Gleason wrote: * How do I make it recurse so it crawls the source library and grabs the content of all my album folders and sub-folders? Only a few files are in the root: most are in album folders and sometimes deeper. rdimport(1) doesn’t do recursion by itself, but can be made to do so with a little scripting. See: https://github.com/ElvishArtisan/rivendell-importers and take a look at the ‘nested-import.pl’ script. ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] rdimport - Suggested ingestion parameters?
Thanks for this! Is there a solution to my other query? --Richard E * How do I import all audio file types in one go, or at least *.mp3 and *.flac for starters?; * How do I make it recurse so it crawls the source library and grabs the content of all my album folders and sub-folders? Only a few files are in the root: most are in album folders and sometimes deeper. rdimport(1) doesn’t do recursion by itself, but can be made to do so with a little scripting. See: https://github.com/ElvishArtisan/rivendell-importers and take a look at the ‘nested-import.pl’ script. ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] rdimport - Suggested ingestion parameters?
Hi... I now have a 2TB drive mounted at /var that can hopefully contain the RD music library in WAV format and I'm beginning to import files. As a result I have a couple of queries. I am navigating to the source music library root directory, which is a read-only-mounted NTFS partition, and issuing the command: rdimport --verbose --segue-level=-10 --autotrim-level=-30 --normalization-level=-10 MUSIC *.mp3 The first thing I see is the message: "Session management: None of the authentication protocols specified are supported". What is this telling me? Meanwhile, the files appear successfully ingested from the root of the source library. However: * How do I import all audio file types in one go, or at least *.mp3 and *.flac for starters?; * How do I make it recurse so it crawls the source library and grabs the content of all my album folders and sub-folders? Only a few files are in the root: most are in album folders and sometimes deeper. MTIA for any observations. Best, --Richard E ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] rdimport - audio file location and ingestion
IIRC, you can store a full complement of metadata in a WAV file and there is a standard for it, it's just not commonly done. I must admit that the one thing that has concerned me slightly is the fact that the ingested files are completely unidentifiable - the idea of writing out and maintaining the metadata in the ingested files in case of a need for database reconstruction sounds like a neat idea on the face of it. On Mon, 5 Nov 2018, Fred Gleason wrote: ...This was one of the fundamental design principles laid down at the very inception of the project: the audio store contains *only* audio; all other metadata goes in the SQL database. What was the rationale behind this decision, incidentally? Given the amount of thought that has gone into the project as a whole, I imagine there is a very good reason for it. -_R On 06-Nov-18 16:50, Rob Landry wrote: Of course, one consequence of this approach is that if you lose the MySQL database, the audio files will be more or less useless. If each audio file had headers carrying copies of the metadata, it would be possible to reconstruct the database fromt hem in the event of a disaster. ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] rdimport - audio file location and ingestion
Hi, Robert... It's heading that way. I indeed picked up a used machine for the current experiments and it should be fine for the application. Thankfully storage is cheap too: I have a 2TB drive on its way. I'll let rdimport ingest from the existing NTFS copy of the library and save its version on the new drive. --Richard E On 05-Nov-18 21:59, Robert Jeffares wrote: I would heartily recommend you build a Rivendell system on a dedicated computer. You can source 2nd hand 64 bit machines relatively inexpensively and they work quite well. You may need to install a bigger drive for /var/snd depending on the music library size, but you can run with almost anything to see how it works. ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] rdimport - audio file location and ingestion
Hi, Fred... Many thanks for these helpful comments, much appreciated. --Richard E On 05-Nov-18 21:39, Fred Gleason wrote: ...the audio store contains *only* audio; all other metadata goes in the SQL database. ...The European Broadcasting Union has codified the standard audio storage format for use in professional broadcast storage and play-out systems. Rivendell (as well as many proprietary systems) adhere to these standards ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] rdimport - audio file location and ingestion
Observations based on your comments - for which thank you again! On 05-Nov-18 20:58, drew Roberts wrote: What does the windows system do with the audio that it cannot work with the Riv files? The Windows playout system reads the metadata from the audio files and stores it in a database that points at the original files. While you can have it make a copy of the library on ingestion it doesn't have to. So the original files are played out, from their original formats. While the Windows system could no doubt /play/ the WAV files produced by Rivendell, they may not contain any metadata, so it wouldn't know what they were. I know that WAV /can /contain metadata but very few applications do that. Does RD keep metadata in the WAV file or simply store it in the database? If you are going to all that trouble the latter would seem to be the way to go. ...If you use that, you use the compressed format you will: 1. lose quality wrt your flac files. 2. incur re-encoding losses from your mp3s. I wouldn't dream of using a lossy compression scheme on the library. I just find it interesting that RD would turn an mp3 file into a WAV file (or a FLAC file into a WAV file for that matter), neither of which confer any sonic benefit. Presumably what this /does /do is to ensure that the system only ever has to play out WAV files and that files ingested will never be stored at /lower/ quality than they come in. If you have room in the box, it is likely more than worth it to put in a drive for /var/snd.. It's not difficult OS-wise to add another drive and move /var on to it, so that's what I'm looking at. I can pull the DVD drive (I have an external USB one somewhere) and put a drive in there instead. Many thanks once again, --Richard E ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] rdimport - audio file location and ingestion
Hi, Drew... This is exceptionally useful information, and thank you. OK, so the current setup won't work. Not only that, my entire installation won't work - if the library needs to be stored in /var/snd/ then it DOES require its own partition - indeed, its own drive. In addition, if I want to run both a Windows system and Rivendell on the same machine as dual-boot I will indeed need two libraries, one in native format (mainly FLAC plus some mp3s) under NTFS and one generated by Rivendell under xfs, probably on its own drive mounted at /var. You note that Rivendell will convert all files to .WAV (even if they are lossy compressed, interestingly) so I need to allow a seriously larger space for the library. I'm very glad I learned this now when I'll only have wasted a day or so building the system, and not some way further down the line, so I am very grateful for the comments. Many thanks! --Richard E ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
