Opened 11 years ago

Closed 4 years ago

#11491 closed Developer Task (Unverified)

Patch to service api (content endpoint) allowing querying of recorded markup data

Reported by: dev-team@… Owned by: stuartm
Priority: minor Milestone: unknown
Component: MythTV - Services API - Backend Version: 0.26-fixes
Severity: medium Keywords: services-api commskip
Cc: Ticket locked: no

Description

This is a patch to allow the querying of RecordedMarkup? data via services api for third party player commskip.

Attachments (6)

mythtv-0.26-serviceapi-recorded-markup.patch (16.3 KB) - added by dev-team@… 11 years ago.
adds methods to query recordedmarkup data to services-api content endpoint
mythtv-0.27-serviceapi-recorded-markup.patch (15.2 KB) - added by dev-team@… 11 years ago.
adds methods to query recordedmarkup data to services-api content endpoint for 0.27
mythtv-0.27-serviceapi-recorded-markup.2.patch (16.4 KB) - added by dev-team@… 11 years ago.
Previous version of this patch did not contain the .pro file
mythtv-0.26-serviceapi-recorded-markup.2.patch (16.3 KB) - added by dev-team@… 11 years ago.
Updated initialization of Markup Type
mythtv-0.27-serviceapi-recorded-markup.3.patch (16.4 KB) - added by dev-team@… 11 years ago.
Updated initialization of Markup Type
mythtv-0.27-serviceapi-recorded-markup.4.patch (13.4 KB) - added by dev-team@… 11 years ago.
new patch with no concept of mark type id coming from the db

Download all attachments as: .zip

Change History (16)

Changed 11 years ago by dev-team@…

adds methods to query recordedmarkup data to services-api content endpoint

Changed 11 years ago by dev-team@…

adds methods to query recordedmarkup data to services-api content endpoint for 0.27

Changed 11 years ago by dev-team@…

Previous version of this patch did not contain the .pro file

Changed 11 years ago by dev-team@…

Updated initialization of Markup Type

Changed 11 years ago by dev-team@…

Updated initialization of Markup Type

Changed 11 years ago by dev-team@…

new patch with no concept of mark type id coming from the db

comment:1 Changed 11 years ago by sphery

Owner: changed from dblain to sphery
Status: newaccepted

comment:2 Changed 11 years ago by sastie@…

will this be included in 0.27 ?

comment:3 Changed 11 years ago by Raymond Wagner

If it hasn't been committed yet, 0.27 has been in feature freeze for over a month, and this cannot be added.

comment:4 Changed 10 years ago by Karl Egly

Component: Bindings - XML/JSONMythTV - Services API - Backend

comment:5 Changed 10 years ago by sphery

Overlaps with/partial duplicate of #12090.

comment:6 Changed 9 years ago by doug@…

Although I'm not the original author, I'd love to see this functionality added. I created a pull request with the above patch modified to work with current Master. I also added "Bookmark" as a property since that's useful to me.

https://github.com/MythTV/mythtv/pull/93

Thanks!

comment:7 Changed 9 years ago by Frank Phillips <fphillips81@…>

This functionality was merged from #12090, so I think this ticket and pull/93 can be closed.

comment:8 Changed 9 years ago by stuartm

Although there were overlaps, some of the functionality provided by this patch is not provided by the patches in #12090.

This patch allows pulling the bookmark information and information about resolution, bitrate and aspect ratio.

Which isn't to say that this patch will be merged, it won't, but I'm leaving it open as a reminder to add the equivalent functionality to the services API. Namely the ability to pull recording file metadata - resolution, bitrate, codec etc from the new recordedfile table.

comment:9 Changed 8 years ago by Karl Egly

Owner: changed from sphery to stuartm
Status: acceptedassigned
Type: Patch - FeatureDeveloper Task

Stuart, I'm closing the PR as per your last comment and moving this over to your reminders.

comment:10 Changed 4 years ago by Stuart Auchterlonie

Resolution: Unverified
Status: assignedclosed

Closing all old tickets in trac.

If your issue still persists, please open an issue in Github https://github.com/MythTV/mythtv/issues

and reference the existing trac ticket.

Note: See TracTickets for help on using tickets.