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
I finally found time to update from 2.18.2 to 2.19.2. Is there a way to
disabled this new feature? It makes it difficult to set the position of
voice tracks over the song intros if there is a music import tag in the log.
"Log Importation Changes. Changed music and traffic importation so that
