On Jun 11, 2018, at 07:52, Rob Landry <41001...@interpring.com> wrote:
> How does rddbcheck see the files?
It just does an open(). Nothing fancy.
> Is there something I need to use beyond ls -al to verify that it can see them?
That should be all that’s needed.
Cheers!
On Sat, 9 Jun 2018, Cowboy wrote:
It's so easy to make a backup immediately before doing anything
like that, I can't even begin to tell you how incompetent I felt at
that moment, but it does happen even to the best of us.
Now that the horse is more or less back in the barn, I've set them up
On Sat, 9 Jun 2018, Fred Gleason wrote:
On Jun 9, 2018, at 11:28, Rob Landry <41001...@interpring.com> wrote:
I suggested they might have a database problem and suggested
running rddbcheck. That proved to be a spectacularly bad
suggestion, as it adjusted the length of every
On Jun 9, 2018, at 11:28, Rob Landry <41001...@interpring.com> wrote:
> I suggested they might have a database problem and suggested running
> rddbcheck. That proved to be a spectacularly bad suggestion, as it adjusted
> the length of every audio cut to zero!
Not a bad suggestion _per se_,
On Saturday 09 June 2018 11:28:35 am Rob Landry wrote:
> That proved to be a spectacularly bad suggestion, as it
> adjusted the length of every audio cut to zero!
>
> They didn't have a recent database backup,
That part, I can relate to, unfortunately.
( yeah, the data recovery guy without a
On Jun 9, 2018, at 11:28, Rob Landry <41001...@interpring.com> wrote:
> I suggested they might have a database problem and suggested running
> rddbcheck. That proved to be a spectacularly bad suggestion, as it adjusted
> the length of every audio cut to zero!
That tells me that the audio store
A client of mine has been running RD 2.15 for a while on Debian 6.
On Thursday, they called me to say they were getting an error when trying
to edit markers on audio cuts.
I suggested they might have a database problem and suggested running
rddbcheck. That proved to be a spectacularly bad
