Hi there
I think the file importing from a dropbox is working well now.
I increased the apache time out value from 300 to 3000 and some test
imports have worked well. I presume 300 = 300 seconds = ten minutes
and 3000 = 3000 seconds = 100 minutes and when you consider it only
took about 10 to 15
Jim Hartranft musicmaker10@... writes:
I am still wishing to pitch shift speed
the music, leave ids and spots. This
should be a feature implemented in
RDLibrary. Running a Top 40 station,
it is almost a must have in my market
as the other pop stations speed their
music up. I had
On Saturday 22 November 2014 09:44:52 pm Jim Stewart wrote:
It was all in the ordeal I have to go through to get the Rivendell daemons to
load correctly.
This should not be an issue.
What OS ?
--
Cowboy
http://cowboy.cwf1.com
Some people live life in the fast lane. You're in oncoming
On Sunday 23 November 2014 08:35:13 am Jim Hartranft wrote:
I didn't mean to start an argument but...
*I* can appreciate that.
If we all always agreed on everything all the time, we would have never
advanced beyond the Neanderthal.
While Neanderthal had a 1/2 billion year run, their
Hi,
I fought with this when I started. It seems logical to put a hard
timed midnight in for a new log but all it achieves are the problems
you're experiencing.
What I do instead is put the hard times at the end of the log. For
example:
At 23:59:55 I have a hard timed macro in the aux
On 23.11.2014 17:02, Wayne Merricks wrote:
Hi,
I fought with this when I started. It seems logical to put a hard timed
midnight in for a new log but all it achieves are the problems you're
experiencing.
RD should look at the date, not only the time.? Feature request..?!
What I do instead
what's obvious, is the Fred isn't likely to do it!
that's not saying that someone else might not, and who knows, if it
worked without screwing up something else, who knows...
What worries me was the extra cpu usage, I don't know if anyone noticed,
but since I personally have a bad habit of
Aha, but what happens, when that last track runs into the hst from
the same logs beginning..? At 00:05 a showopener after the news for
example.
Thats why I don't have any hard timed events at the start of a log
until 00:30. By making sure your log make's next at 23:59:55 ish at
best
Sorry, I guess I over-trimmed the thread behind this post. I've been using
Debian Linux (both 32 and 64 bit depending on actual hardware I'm running it
on), the primary on air machine is still running the older Squeeze
distribution, everything else I have Rivendell on runs Wheezy except for a
On Nov 23, 2014, at 11:32 03, John Anderson j...@2601.net wrote:
what's obvious, is the Fred isn't likely to do it!
Bah! Humbug!! :)
What worries me was the extra cpu usage,
That’s certainly a factor, but not the primary one in my view. Unix design
history has a very strong tradition of
actually not, it's the button to disregard the segue marker on the
beginning of the next event...
semantics aside, I don't think a traditional cold start is going to be a
good addition
On Sun, 2014-11-23 at 15:22 -0500, Frederick Gleason wrote:
PS, I am still lobbying for a cold start
agreed
On Sun, 2014-11-23 at 15:22 -0500, Frederick Gleason wrote:
That’s certainly a factor, but not the primary one in my view. Unix design
history has a very strong tradition of building tools that focus on doing one
thing well and then allowing those tools to interoperate, rather
I think the answer in this case is clear: pitch alteration belongs in the
production room, not the air chain.
I tend to agree with this too.
Another option that I could point out - which essentially would be the
same as doing the alteration in production only without the human
element
On 23.11.2014 18:02, Wayne Merricks wrote:
Thats why I don't have any hard timed events at the start of a log until
00:30. By making sure your log make's next at 23:59:55 ish at best
you'll only have a song or advert/stinger left to play so worst case
scenario for a 15 minute song you'll be
Hi,
Beware that if you are applying this to an existing library; there are
cart lengths/average_lengths in the CARTS table and I'm pretty sure cut
lengths in the CUT table.
It would also throw off any segue/talk time/hook/cut start/end markers
you had put in.
Should be possible to script
Hi,
If you run rddbcheck after you change your audio file, it'll go through
and fix the cart/cut lengths in the database, based on the actual
lengths of the audio tracks (I just did a quick test on a test file /
machine I have running an audio file through SOX and speeding it up 5%).
However as
5% is way too high. .5% to about 2% is about the range. 2.5% is really
noticeable.
The point of the technique is to make a competitor playing your music to sound
sluggish to button pushers.
Sent from my iPhone
On Nov 23, 2014, at 9:34 PM, Lorne Tyndale ltynd...@tyndaleweb.com wrote:
Hi,
17 matches
Mail list logo
