Re: [RDD] Library Editor--or perhaps a Database--Problem
compare the permissions on the original and the edited file ls -l /var/snd/[cartnum]* will give you both They should be the same. Permissions seem to be the problem better then 90% of the time. regards Robert On 08/03/17 15:06, Chuck wrote: I'm on RD v2.10.3 from Tryphon running Linux Mint 17 (no .x update) on my personal Asus Zen notebook with /var/snd on an external USB drive. This has been running for nearly 3 years with no problems until today. My /var/snd and database is the master for our station as I do all the production work, and another computer is used for actual playout, which is a clone of my /var/snd and RD database. One of the things I do is edit fade-out levels and make adjustments to music tracks in the library. My usual method is to copy the originally imported track and paste it to a new cut (Cut 002) and mark that as the untouched original in the "Cut Info". Then I weight it "0" so it never plays, but is available if there ever should be a reason to return to the original, untouched track. Today, however, when I pasted the copied track to the new cut, it did not seem to paste. Track length was "00.0" and when I clicked on "Edit Markers", a dialog appeared that says, "No audio present in the cut." This problem is repeatable with other carts, but no problems importing new tracks to carts--just this copy and paste problem. There IS audio, as it plays in the preview player in the "Cut Info" button. And a file manager shows cut 002 with a file size identical to cut 001 in /var/snd. Cut 002 also imports and plays in Audacity. It will NOT play in RDAirplay, which also sees it as a 'no audio present' track, and skips it. Anybody have any clues as to what the problem might be? This isn't exactly an on-air machine and is on the Internet, so I do Mint updates, but the problem has appeared suddenly when I have not done a Mint update for weeks. I did have a power failure a few days ago, and the /var/snd USB drive is not on a UPS (the notebook is), but such outages have not caused problems in the past. The power outage occurred while a log was being generated, however, so /var/snd was not available and the log generation seemed to stop. After power resumed, I started the log generation over, and that log seems fine. Any ideas appreciated. --Chuck W. ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev -- *Communication Consultants* 64 Warner Park Avenue Laingholm Auckland 0604 09 8176358 0221693124 06 650 6087 ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Library Editor--or perhaps a Database--Problem
On Wednesday 08 March 2017 03:07:28 pm Chuck wrote: > I have been using this method for > over 2 years on the same installation on the same computer with no > problems. There's the key ! What changed ? ( something definitely did ) Maybe something as seemingly innocuous as an auto-update of something or another seemingly totally unrelated... Restored known good backup, maybe ? Something changed, and at the same time this started happening. -- Cowboy http://cowboy.cwf1.com Is it possible that software is not like anything else, that it is meant to be discarded: that the whole point is to always see it as a soap bubble? ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Rivendell and Broadcast Tools switcher.
Hi,
I'm not sure if this is a broadcast appliance install or something else,
but one thing that I've run into on Ubuntu based distributions is the
user ID that you're running Rivendell as needs to be a member of the
dialout group in order to access the serial port.
Especially if you're running the daemons under a different user ID from
the ID you're running the GUI under, you'll need to add the user ID's
that runs the daemons to dialout or else it won't be able to access the
serial port.
I don't know if this is the problem, but it is something to look at.
>
> If you get correct results in Minicom but not in Rivendell, the problem
> might be Rivendell-related.
>
> But if you never get correct results even in Minicom, then you've got a
> hardware problem (bad serial port? bad cable? incorrect pinout?) or a
> configuation problem.
>
>
> Rob
>
> --
> Я там, где ребята толковые,
> Я там, где плакаты "Вперёд",
> Где песни рабочие новые
> Страна трудовая поёт.
>
> On Mon, 6 Mar 2017, James Greenlee wrote:
>
> >
> > As far as producing the "correct" result...That would be a negative.
> >
> > No matter what the macro says, Rivendell always puts the switch into mute.
> >
> > Executing a *140 directly into the switcher via minicom doesn't do anything.
> >
> > So Rivendell is logging in to Linux as user "rd." I just added the user rd
> > to the group dialout (which has access to the serial port). Now rd can run
> > minicom and execute switches via commands punched into minicom (*11, *81,
> > *62, etc). Rivendell macros fail though.
> >
> > I'm obviously missing something.
> >
> > In my mind, this should be really easy:
> >
> > 1. Install standard Rivendell per the instructions provided:
> > http://static.paravelsystems.com/rivendell-install/rivendell-install-rhel7.html
> > 2. Configure host, setup serial port, add matrix as Broadcast Tools 8x2.
> > 3. Fire up RDLibrary, create a macro, ST 0 1 1!
> > 4. Run macro, watch the switch assign input 1 to output 1.
> >
> > Sadly it doesn't work. The Macro puts the switcher into "mute" state.
> > Minicom allows me to switch inputs just fine though and it's using the same
> > configuration as Rivendell for the serial port.
> >
> > James
> >
> >
> > - Original Message -
> > From: "Rob Landry" <41001...@interpring.com>
> > To: "James Greenlee"
> > Cc: "Wayne Merricks" , "User discussion
> > about the Rivendell Radio Automation System"
> >
> > Sent: Monday, March 6, 2017 3:42:46 PM
> > Subject: Re: [RDD] Rivendell and Broadcast Tools switcher.
> >
> > On Mon, 6 Mar 2017, James Greenlee wrote:
> >
> >> Using screen, and executing a ST macro from Rivendell, I see an output of
> >> *140 and the switcher goes to mute. Executing a *140 in minicom does not
> >> produce the same result.
> >
> > Does it produce the correct result, though?
> >
> >> It would appear then that the Rivendell "driver"
> >> for the Broadcast Tools 8x2 speaks a slightly different language than
> >> what my 8x2 actually understands.
> >
> > As far as I know, 8x2s have always understood the same language.
> >
> > Is Rivendell defining the serial port with different parameters than
> > minicom? Is Rivendell running as a different user than minicom? If so,
> > does that user have sufficient privileges to use the serial port?
> >
> >> In Wayne's documentation, you can execute commands to the serial port via
> >> rmlsend with some shell scripts with screen commands. I'm sure I can make
> >> that work, but is there a way to make a "driver" for Rivendell like the
> >> existing Broadcast Tools 8x2 switcher one?
> >
> > UTSL ("Use the source, Luke").
> >
> > Personally, I wouldn't bother, though; I'd have Rivendell run a
> > constellation of shell commands containing whatever language you need to
> > make the switcher work.
> >
> >
> > 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] Library Editor--or perhaps a Database--Problem
On Wed, 8 Mar 2017 07:36:15 -0500 Cowboy wrote: > On Tue, 07 Mar 2017 21:06:33 -0500 > Chuck wrote: > > > My usual method is to copy the originally > > imported track and paste it to a new cut (Cut 002) and mark that as > > the untouched original in the "Cut Info". Then I weight it "0" so it > > never plays, but is available if there ever should be a reason to > > return to the original, untouched track. > > Should I assume you know that Library markers are non-destructive ? > > Rivendell makes NO changes to the audio. None. > All markers, fades, etc. are strictly in the database. > > Therefore, the original, or marked, file is always "untouched." < Right. But it *is* the audio tracks I am altering. Aside from bringing audio up to constant until nearer the end on songs where the audio fades over 30 to 45 seconds, I am also adding back-announcements to songs, à la WBEB/Philly, so I am definitely destructing the audio files. If we ever drop that back-announce format, I want to be able to return to the original tracks without having to reimport the tracks all over again from scratch. At this point, I have no clue why the library editor and airplay do not see the copy and pasted files as containing bonafide audio, when it appears those files do have audio. I have been using this method for over 2 years on the same installation on the same computer with no problems. --Chuck W. ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Rivendell and Broadcast Tools switcher.
If you get correct results in Minicom but not in Rivendell, the problem
might be Rivendell-related.
But if you never get correct results even in Minicom, then you've got a
hardware problem (bad serial port? bad cable? incorrect pinout?) or a
configuation problem.
Rob
--
Я там, где ребята толковые,
Я там, где плакаты "Вперёд",
Где песни рабочие новые
Страна трудовая поёт.
On Mon, 6 Mar 2017, James Greenlee wrote:
As far as producing the "correct" result...That would be a negative.
No matter what the macro says, Rivendell always puts the switch into mute.
Executing a *140 directly into the switcher via minicom doesn't do anything.
So Rivendell is logging in to Linux as user "rd." I just added the user rd to
the group dialout (which has access to the serial port). Now rd can run minicom and
execute switches via commands punched into minicom (*11, *81, *62, etc). Rivendell
macros fail though.
I'm obviously missing something.
In my mind, this should be really easy:
1. Install standard Rivendell per the instructions provided:
http://static.paravelsystems.com/rivendell-install/rivendell-install-rhel7.html
2. Configure host, setup serial port, add matrix as Broadcast Tools 8x2.
3. Fire up RDLibrary, create a macro, ST 0 1 1!
4. Run macro, watch the switch assign input 1 to output 1.
Sadly it doesn't work. The Macro puts the switcher into "mute" state. Minicom
allows me to switch inputs just fine though and it's using the same configuration as
Rivendell for the serial port.
James
- Original Message -
From: "Rob Landry" <41001...@interpring.com>
To: "James Greenlee"
Cc: "Wayne Merricks" , "User discussion about the Rivendell
Radio Automation System"
Sent: Monday, March 6, 2017 3:42:46 PM
Subject: Re: [RDD] Rivendell and Broadcast Tools switcher.
On Mon, 6 Mar 2017, James Greenlee wrote:
Using screen, and executing a ST macro from Rivendell, I see an output of
*140 and the switcher goes to mute. Executing a *140 in minicom does not
produce the same result.
Does it produce the correct result, though?
It would appear then that the Rivendell "driver"
for the Broadcast Tools 8x2 speaks a slightly different language than
what my 8x2 actually understands.
As far as I know, 8x2s have always understood the same language.
Is Rivendell defining the serial port with different parameters than
minicom? Is Rivendell running as a different user than minicom? If so,
does that user have sufficient privileges to use the serial port?
In Wayne's documentation, you can execute commands to the serial port via
rmlsend with some shell scripts with screen commands. I'm sure I can make
that work, but is there a way to make a "driver" for Rivendell like the
existing Broadcast Tools 8x2 switcher one?
UTSL ("Use the source, Luke").
Personally, I wouldn't bother, though; I'd have Rivendell run a
constellation of shell commands containing whatever language you need to
make the switcher work.
Rob
___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Library Editor--or perhaps a Database--Problem
On Tue, 07 Mar 2017 21:06:33 -0500 Chuck wrote: > My usual method is to copy the originally > imported track and paste it to a new cut (Cut 002) and mark that as > the untouched original in the "Cut Info". Then I weight it "0" so it > never plays, but is available if there ever should be a reason to > return to the original, untouched track. Should I assume you know that Library markers are non-destructive ? Rivendell makes NO changes to the audio. None. All markers, fades, etc. are strictly in the database. Therefore, the original, or marked, file is always "untouched." -- Cowboy http://cowboy.cwf1.com The trouble with heart disease is that the first symptom is often hard to deal with: death. -- Michael Phelps ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
