Error when scheduler stoped
  • In the console I get this error when the scheduled playlist is finished:

    PlaylistEvent::stop error:
    GstreamerPlayer not opened yet


    What this mean? I read inside the cxx code and say that this is not an error if the user was stoped the playlist, but this is no my case:

    void
    PlaylistEvent :: stop(void)                        throw ()
    {
        DEBUG_BLOCK
    
        try {
            audioPlayer->stop();
            audioPlayer->close();
        } catch (std::logic_error &e) {
            // TODO: handle error
            // NOTE: this may not be an error, because the user may have stopped
            // the playback manually (see Scheduler::StopCurrentlyPlayingMethod)
            std::cerr << "PlaylistEvent::stop error: " << std::endl;
            std::cerr << e.what() << std::endl;
        }
        state = stopped;
    }
    


  • 3 Comments sorted by
  • Hi Normando,

    Could you please provide more information how to reproduce this issue? and which version you are using?

    Does CC-studio crash or can you simply resume playback after that?

    Cheers!
    robin
  • Hi Robin

    Right now I am not using CC, but I remember this issue.

    CC version is 1.4 I have download from source forge, and compiled under centos 5.5 32bit.

    I was get this error in the console exactly when the playlist reach the end. Any way this not disturb the normal operation of the playlist. I think this is only noise.

    Thanks Robin
  • On 10/13/10 16:50, Normando Hall wrote:
    > Hi Robin
    >
    > Right now I am not using CC, but I remember this issue.
    >
    > CC version is 1.4 I have download from source forge, and compiled under
    > centos 5.5 32bit.
    >
    > I was get this error in the console exactly when the playlist reach the
    > end.
    > Any way this not disturb the normal operation of the playlist. I
    > think this is only noise.

    Do you mean by this that it is not a blocking or critical issue?
    IOW: You think it is not important to fix this, right?

    While it may be annoying it does not have influence on the general
    usability of CC-1.4.
    That at least is my POV - the only thing I could reproduce is the
    warning on the console. Users who don't read the console will not even
    notice.

    Campcaster-1.4 is in feature-freeze; bug-fix-only mode until 1.6 comes
    out. Campcaster-1.6 (only a few weeks away) will render the studio-GUI
    completely obsolete. We'll be fixing critical bugs in 1.4 until 1.6 is
    stable; but non-critical issues in 1.4 will likely remain unaddressed.

    > Thanks Robin
    you're welcome.

    Cheers!
    robin