obplayer icon indicating copy to clipboard operation
obplayer copied to clipboard

LA not switching to Fall Back Media

Open radiorob opened this issue 8 years ago • 7 comments

When LA gets to the end of a scheduled LA show and there is nothing else scheduled, it should sense it is stuck playing nothing and should kick into a DPL (if there is one) and if no DPL start playing local Fall Back Media. Presently at end of LA, it gets stuck, screen blinks\refreshes, dead air. When LA is stuck, pressing > PLAY starts the fall back media.

radiorob avatar Jun 30 '16 03:06 radiorob

Hi, again. Thanks for the fast support, and sorry for my english, (Hola from Valencia, ES) I think I found a clue where this issue begins. If in a the middle of a schedulled playlist I break Ctr-C *2 the obplayer and restart it, the show continues, but at the end if nothing its programmed this bug shows up, and no fall back , no, nada.

Silly patch, not a real solution: Put in the beggining of the function play_next in scheduler.py line 173. self.ctrl.stop_requests() self.ctrl.add_request(media_type='break', end_time=self.end_time(), title = "break (filling spaces)")

UPDATE!: Just only one case, this case breaking in he middle of a show...the player fail me again after several shows...argh.

iesfausti avatar Jul 20 '16 09:07 iesfausti

Hello from Vancouver, Canada =)

The problem here is moreso one of user interaction. The existing behaviour is actually how we designed it at the time as a compromise, and a proper fix requires some major work on the LiveAssist.

The problem is that once the LA show has ended and the fallback player or default playlist takes over to fill the air, there's no way for the radio host to interrupt that and go back to their show. The show has ended and the scheduler has moved on to the next show. There's also no reliable way for the LA to detect that the show has ended and the radio host has walked away (and thus it is safe to switch). It's possible for the radio host to let the playlist finish and then talk a bit more before ending the show, or they could accidentally click on the last item causing the show to end, thus locking them out. So the decision was made to not lock out the host, even if that means playing dead air for the remainder of the slot.

Perhaps a better way of doing this would be to add a button to the LA to go live vs playing the DPL, and the host will have to click the button when they're ready. If they fail to show up to do their show, it would play fallback or DPL content for the whole slot. This would require some major work though, given how the live assist and schedule system is currently written. The LA was originally made on a very small budget, and the rest of the player code has been rewritten since then. The LA could do with a lot of work really. Currently it's not a high priority on my to do list, but I will get to it eventually.

transistorfet avatar Jul 21 '16 03:07 transistorfet

How much closer are you after cery nearly 5 years?

I really like the way LA works for doing remotes around town live.

Would be nice if we could end any time we wanted without someone having to make sure there is not dead air.

BD-Engineering avatar Jul 01 '21 22:07 BD-Engineering

Issue Status: 1. Open 2. Started 3. Submitted 4. Done


This issue now has a funding of 100.03 USD (99.99 USD @ $1.0/USD) attached to it.

gitcoinbot avatar Oct 29 '21 17:10 gitcoinbot

Issue Status: 1. Open 2. Started 3. Submitted 4. Done


Workers have applied to start work.

These users each claimed they can complete the work by 1 month, 4 weeks from now. Please review their action plans below:

1) dan-giddins has applied to start work (Funders only: approve worker | reject worker).

This app looks like its mostly written in python. Does it run okay on Windows?

If so, I will try and get the app up and running, then investigate the issue in the code.

Learn more on the Gitcoin Issue Details page.

gitcoinbot avatar Nov 01 '21 15:11 gitcoinbot

@boolinn523 Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

  • [x] reminder (3 days)
  • [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

gitcoinbot avatar Nov 12 '21 17:11 gitcoinbot

@boolinn523 Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

  • [x] reminder (3 days)
  • [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

gitcoinbot avatar Nov 12 '21 17:11 gitcoinbot

@boolinn523 Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

  • [x] reminder (3 days)
  • [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

gitcoinbot avatar Nov 15 '21 17:11 gitcoinbot

@boolinn523 Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

  • [x] reminder (3 days)
  • [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

gitcoinbot avatar Nov 15 '21 17:11 gitcoinbot

@boolinn523 Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

  • [x] reminder (3 days)
  • [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

gitcoinbot avatar Nov 18 '21 17:11 gitcoinbot

@boolinn523 Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

  • [x] reminder (3 days)
  • [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

gitcoinbot avatar Nov 18 '21 17:11 gitcoinbot

@boolinn523 Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

  • [x] reminder (3 days)
  • [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

gitcoinbot avatar Nov 21 '21 17:11 gitcoinbot

@boolinn523 Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

  • [x] reminder (3 days)
  • [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

gitcoinbot avatar Nov 21 '21 17:11 gitcoinbot

@boolinn523 Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

  • [x] reminder (3 days)
  • [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

gitcoinbot avatar Nov 24 '21 17:11 gitcoinbot