My bad. Cut start was badly set on the second track. I'm keeping an ear on our stream.
Le 27/06/2014 15:08, Hoggins! a écrit : > Hello Pedro, > > I think I just heard the same phenomenon on our station. Also running > 2.9.0. There was no overlapping between songs, the first one having a > segue out set. > The first song faded out, and the second one only started when the fade > out was complete. > > I'm not 100% sure, but your messages definitely ring a bell with what I > just heard. > > Hoggins! > > > Le 27/06/2014 11:36, Pedro Picoto a écrit : >> To put things clear I've made a raw graphic. >> >> http://postimg.org/image/t9crd6l09/ >> >> 1 - is what is set to do (overlaping from segue start point) >> 2 - is what is randomly happening (check the gap between the jingle >> end the start of song b) >> >> When I mean gao I mean the amount of time between the segue start of >> jingle and the end of the jingle >> defined on auto-trimming, perceived as silence. >> >> >> On Fri, Jun 27, 2014 at 2:35 AM, John Anderson >> <[email protected] <mailto:[email protected]>> wrote: >> >> I guess what i am having difficulty with the delay start times on >> cart...why would you want/need to do this.. as a general rule, you >> would expect the carts to start at once, once you asked for a >> start..so i see no point in pre-recording a delay. >> >> then the silence at the end of the cart...for what >> purpose...again, all that is likely to do is give you dead air at >> the end of the cart in certain modes...if you put a segue start in >> the proper place, and if the system in in segue, you should get >> identical playback every time.. >> >> i really don't get the intentional silence? >> >> >> On Thursday, June 26, 2014 7:39 PM, Pedro Picoto >> <[email protected] <mailto:[email protected]>> wrote: >> >> >> I'm just want that the segues respect the Segue Start mark I set >> for each and every file. >> This database/snd files ALREADY WORKED FINE. It's having this >> behaviour since yesterday. It's happening mainly with jingles. >> Jingles that used to run consistent >> regarding the Segue start point. When I ear a messy segue I check >> the library and confirm that the segue start mark >> is well defined. I put that same jingle on the log and listen to >> it again. It plays fine. Will it play fine a next time? I dont >> know. It's random. >> >> >> On Thu, Jun 26, 2014 at 11:21 PM, John Anderson >> <[email protected] <mailto:[email protected]>> wrote: >> >> I don't understand this at all... >> >> exactly what are you trying to accomplish... >> >> more so why... >> >> >> >> On Thursday, June 26, 2014 3:13 PM, Thomas Churchill >> <[email protected] <mailto:[email protected]>> >> wrote: >> >> >> I haven’t gotten to this yet in setup and testing. Mostly >> whatever I try sounds horrible and I have left the segue’s >> alone for another day. Also I am having trouble saving edits >> to the markers. >> But perhaps this applies: >> http://www.wave1049online.net/Rivendell/He says: >> >> * Each song must have a second or so of silence at the start >> * Each song must have about 4 seconds of silence at the end >> * Each seque must be at least 1.5 seconds in duration or it >> won't "hit" correctly >> * Each song must end at least 1.5 seconds after the end of >> its seque >> >> ·The silence at the beginning and end of each track >> is/very/important. When it comes time to trim the events, >> you'll be glad you did that because, although the songs will >> look good in Rivendell's library manager, the won't seque >> correctly unless there is adequate space, especially at the >> end of the track, to ensure that segues are a minumum of 1.5 >> seconds in duration, and the defined end of the track is at >> least 1.5 seconds away from the end of the segue. If these >> conditions are not met, the segues won't hit correctly on the >> air. We wasted an extra 2 weeks learning that lesson the hard way. >> ·Even if you have a piece of imaging or a sound effect or >> something whose duration is less than a second, you're still >> going to need that second of silence in front and that 4 >> seconds of silence in back, or its segue will be nasty. You >> won't like it. >> TC >> *From:*[email protected] >> <mailto:[email protected]> >> [mailto:[email protected] >> <mailto:[email protected]>] *On >> Behalf Of *Pedro Picoto >> *Sent:* Thursday, June 26, 2014 1:39 PM >> *To:* [email protected] >> <mailto:[email protected]> >> *Subject:* [RDD] Segue start failing >> I've noticed that randomly the segue start point isn't >> respected. Each time I listen to one failing I check it on the >> RDLibrary and it's correctly marked. >> Running version 2.8.1. and never had this problem before. I've >> been using/testing/learning this >> version for quite a while. >> >> _______________________________________________ >> Rivendell-dev mailing list >> [email protected] >> <mailto:[email protected]> >> http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev >> >> >> >> >> >> >> >> >> _______________________________________________ >> Rivendell-dev mailing list >> [email protected] >> http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev > _______________________________________________ > Rivendell-dev mailing list > [email protected] > http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev > _______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
