WOW! ... Thanks for your reply! I was really breaking my head.

I have not cross-imported 3 to 4 or vice-versa, but rather, from the very start, working on a RD4 machine from scratch for the testing... But after patient work on setting marks on 3/4 of my tracks on RD4 RDlibrary, I'm starting to notice that something is wrong.

Have you opened an issue on the Github repo for this? (I guess that this may probably be considered a quite ugly bug!)

Thanks, regards.

On 5/11/22 16:11, Bemis, Andru wrote:
I'm not at my RD4 computer right now, but I have a hunch that the Fade-Up & Fade-Down markers have been accidently switched somewhere in the RD4 programming. I know for a fact that cuts exported from RD4 and imported to RD3 have Fade-Ups where I set Fade--Downs, and vise versa. This leads to very similar results as you're describing. There's definitely a bug of some sort in the way RD4 deals with fade markers.

Andru Bemis

Producer & Host | The Chenango Sessions
Director | Cranberry Coffeehouse
Music Director | WBDY-LP 99.5 FM
Piano Technician | Binghamton Piano Rescue

557 Chenango St, Binghamton, NY 13901, USA
(269) 767-8235
he/him

On Wed, May 11, 2022, 9:35 AM Alejandro olivan Alvarez <alejandro.olivan.alva...@gmail.com> wrote:

    Hi and thanks for your advice!

    From the way you use the 'No fade on segue out' function (or as I
    understand you do), it reassures me I'm using it right: As either
    a way to prevent the cut to be faded down on segue (for instance
    if the cut audio itself fades down nicely) or as a way to take
    control of the actual fading down by means of a fade-down marker.

    Anyways, the fact is that I forgot to mention that I'm beta
    testing RD4 :-P ... so anything could happen!

    But since you mentioned also the fade-up marker, I'm starting to
    feel as if it does nothing (Beta4... probably not the place this
    list to discuss this... but I hate reporting bugs out of my
    incomplete knowledge of features), as most of my tracks do have
    fade up mark for a whole 8 beat bar, and I'm failing to perceive
    nice progressive fade ups, but rather sharp/sudden playback
    starts, resulting in mediocre transitions/segues ... Will have to
    invest time to be sure.

    Anyhow... thank you very much!

    Regards.

    On 5/10/22 22:40, Brandon Anjeleno wrote:
    Hey Alejandro,

    I don't use the fade down markers, but occasionally, I'll use the
    fade up marker to start a song at a specific point giving it a
    clean start point at a specified time. I always use the 'No Fade
    on segue out' function on *all* imaging / sweepers / promos, etc
    so that the next marker doesn't fade out the imaging before the
    end of the sweeper / promo when walking up a song intro.

    Hope that helps!
    Brandon Anjeleno
    Station Manager
    subSTATION.one <https://substation.one/>
    UNITED WE DANCE ®
    +1 (213) 839-7667 <tel:12138397667>
    WhatsApp <https://wa.me/13105986665>


    On Tue, May 10, 2022 at 2:28 AM Alejandro olivan Alvarez
    <alejandro.olivan.alva...@gmail.com> wrote:

        Hi List.

        Not sure whether my list account is ok... hope it is! Here we go

        I'm practicing with my library trying to have all tracks
        properly
        'marked'. So I've quite a lot of fade down and fade up marks.

        The problem I'm facing is that the main log is often
        mutted/faded down
        as two tracks transition/segue, and I'm not finding the logic.

        I'm looking for the cause of this, why do tracks sometimes play
        entirelly with the LogMachine fadded down, with or without
        Fade up
        marks? ... I'm starting to thing I've misunderstood what's
        the bussiness
        logic behind the 'No Fade on segue out' button does... What
        does this
        button do? Does it apply for the track it is defined (as I
        think it
        does) or does it refer to the next track (like the segue mark
        refers to
        where the next track will start)

        I'm not finding this on the manual...

        Thanks!

        _______________________________________________
        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


/Message sent from andrubemis.com <http://www.andrubemis.com>/
_______________________________________________
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Reply via email to