Release 1.6.4 with Python selection upon install

Sorry, no further changes 😐

1.6.3 Release with python2->python->python3 execution order

Push version to 1.6.2

DSM7 release for cphub.net (1.6.2)

Release notes

This is a release for a coming DSM7 version and cphub.net repository.
Please read following notes carefully or you'll ask questions afterwards 🙂

General information and major changes

• Fixed password input
• This release no longer supports DSM6. If you're still on DSM6, please check previous releases.

Installation

• Upon installation/upgrade you'll now be asked for a share name for output files. Default share tvstreamrecord is recommended. If already exists, this share will be reused. No data will be deleted or lost upon installation, deinstallation or upgrade of this package. If you wish to uninstall the package, you will have to delete the new share from Control Panel manually
• If you've upgraded from DSM6, please change your output path accordingly (e.g. /volume1/tvstreamrecord)
• The database (tvstreamrecord.db) will now be created in the new share thus allowing for its backup and better migration. You can even open it with an SQLite tool of your choice (e.g. SQuirreL)

Migrating from DSM6

Clean installation is recommended but migration / repair should be possible. Your database should be preserved and copied to the new share.
To be sure, you can save your old database using terminal prior to updating, for example (check paths):

cp /var/packages/tvstreamrecord/target/settings.db /volume1/tvstreamrecord/tvstreamrecord.db

ffmpeg related notes

• This release is now fully dependent on ffmpeg, all protocols will now be forwarded to it, "supported protocols" configuration entry is thus removed

• Instead, there is a new switch for using the old legacy recording on http streams only (for older devices such as NetStream)

• As of now, the community version of ffmpeg is not available, so the built-in ffmpeg is used. This version however have some restrictions (for example, no support for https protocol). If required (or just to use the latest and fullest version), you must download it manually:

  • check ffmpeg.org for a compatible release for your architecture (for newer x64 CPUs it would be ffmpeg-release-amd64-static.tar.xz from https://johnvansickle.com/ffmpeg/) and download it
  • extract the subfolder's contents of the archive to /volume1/tvstreamrecord/ffmpeg (or \\myNAS\tvstreamrecord\ffmpeg on Windows)

(example using 7-Zip for Windows)

• open TSR configuration and change ffmpeg path to /volume1/tvstreamrecord/ffmpeg/ffmpeg
• voilà

If you didn't do it, please don't ask me why it's not working.

---

Feedback appreciated!

DSM7 release for cphub.net

Release notes

This is a release for a coming DSM7 version and cphub.net repository.
Please read following notes carefully or you'll ask questions afterwards 🙂

General information and major changes

• This release no longer supports DSM6. If you're still on DSM6, please check previous releases.

Installation

• Upon installation/upgrade you'll now be asked for a share name for output files. Default share tvstreamrecord is recommended. If already exists, this share will be reused. No data will be deleted or lost upon installation, deinstallation or upgrade of this package. If you wish to uninstall the package, you will have to delete the new share from Control Panel manually
• If you've upgraded from DSM6, please change your output path accordingly (e.g. /volume1/tvstreamrecord)
• The database (tvstreamrecord.db) will now be created in the new share thus allowing for its backup and better migration. You can even open it with an SQLite tool of your choice (e.g. SQuirreL)

Migrating from DSM6

Clean installation is recommended but migration / repair should be possible. Your database should be preserved and copied to the new share.
To be sure, you can save your old database using terminal prior to updating, for example (check paths):

cp /var/packages/tvstreamrecord/target/settings.db /volume1/tvstreamrecord/tvstreamrecord.db

ffmpeg related notes

• This release is now fully dependent on ffmpeg, all protocols will now be forwarded to it, "supported protocols" configuration entry is thus removed

• Instead, there is a new switch for using the old legacy recording on http streams only (for older devices such as NetStream)

• As of now, the community version of ffmpeg is not available, so the built-in ffmpeg is used. This version however have some restrictions (for example, no support for https protocol). If required (or just to use the latest and fullest version), you must download it manually:

  • check ffmpeg.org for a compatible release for your architecture (for newer x64 CPUs it would be ffmpeg-release-amd64-static.tar.xz from https://johnvansickle.com/ffmpeg/) and download it
  • extract the subfolder's contents of the archive to /volume1/tvstreamrecord/ffmpeg (or \\myNAS\tvstreamrecord\ffmpeg on Windows)

(example using 7-Zip for Windows)

• open TSR configuration and change ffmpeg path to /volume1/tvstreamrecord/ffmpeg/ffmpeg
• voilà

If you didn't do it, please don't ask me why it's not working.

---

Feedback appreciated!

DSM7 Preview release

Release notes

This is a preview release for a coming DSM7 version. Please read following notes carefully or you'll ask questions afterwards 🙂

General information and major changes

• This release no longer supports DSM6. If you're still on DSM6, please check previous releases.

Installation

• Upon clean install you'll now be asked for a share name for output files. Default share is recommended. If already exists, this share will be reused. No data will be deleted or lost upon installation, deinstallation or upgrade of this package. If you wish to uninstall the package, you will have to delete the new share from Control Panel manually.
• Because of new rights management, this share can not be changed from inside the package anymore, corresponding configuration entry is now disabled.
• The database (tvstreamrecord.db) will now be created in the new share thus allowing for its backup and better migration. You can even open it with an SQLite tool of your choice (e.g. SQuirreL). Its path is also not changeable anymore.

Migrating from DSM6

No automatic migration or repair is possible. Clean installation should be used instead.

• if you're still using DSM6, you can install the previous release 1.5.1 first, which allows you to move and save the database.
• if you're on DSM7 and TSR is in "Repair" state, you can probably save your database using terminal, for example (check paths):

cp /var/packages/tvstreamrecord/target/settings.db /volume1/tvstreamrecord/tvstreamrecord.db

• if you're on DSM7 and removed TSR already, sorry, your database is lost forever.

After removing and reinstalling TSR, stop it again, overwrite the new created database with saved one and start it anew.

ffmpeg related notes

• This release is now fully dependent on ffmpeg, all protocols will now be forwarded to it, "supported protocols" configuration entry is thus removed

• Instead, there is a new switch for using the old legacy recording on http streams only (for older devices such as NetStream)

• As of now, the community version of ffmpeg is not available, so the built-in ffmpeg is used. This version however have some restrictions (for example, no support for https protocol). If required (or just to use the latest and fullest version), you must download it manually:

  • check ffmpeg.org for a compatible release for your architecture (for newer x64 CPUs it would be ffmpeg-release-amd64-static.tar.xz from https://johnvansickle.com/ffmpeg/) and download it
  • extract the subfolder's contents of the archive to /volume1/tvstreamrecord/ffmpeg (or \\myNAS\tvstreamrecord\ffmpeg on Windows)

(example using 7-Zip for Windows)

• open TSR configuration and change ffmpeg path to /volume1/tvstreamrecord/ffmpeg/ffmpeg
• voilà

If you didn't do it, please don't ask me why it's not working.

Known issues

• Multiple volumes are probably not supported correctly, your new share is assumed to be located on volume1, e.g. /volume1/tvstreamrecord, which is where your database and records are looked for.
• Port changing is possible but this change will not be reflected in Package Center (for now always showing 8030).

---

Feedback appreciated!
addressing #47, confirmation pending

Last DSM6 build

This is a latest Synology SPK release for DSM6

With DSM7 a new rights management is introduced.
I'm aware that some devices running DSM7 don't have Docker (e.g. DS415play).
I'll check whether tvstreamrecord can further provide a native release after an official DSM7 release.
In the meanwhile this tool goes for Docker and already got some long pending issues cleared.

General

• Configuration location can now be changed for better portability in advanced settings tab
• Update jQuery, jQueryUI, jQuery Mobile and their themes (if updating, you must reselect your favorite theme ignoring broken GUI 😛)

Docker

• Official repository and readme at:
  https://hub.docker.com/repository/docker/pavion/tvstreamrecord
• for proper updating tvstreamrecord configuration is stored in /volume1/common/tvstreamrecord.db, path /volume1/common should be linked or changed!

Synology

• Local libraries are not committed anymore but provided for portability inside spk
• You might want to set the database portable for a later Docker migration, saving all your data

Disclaimer

• This is a pre-release, not all features were tested properly.
• Python 2 should still be supported, Python 3 is recommended

Feedback appreciated.

Use python3 if available

• Use python3 if available
• Fix passing negative value to time.sleep()

Avoid using datetime.min

Using strftime on datetime.min on Python 2.7 throws an Exception:
year=1 is before 1900; the datetime strftime() methods require year >= 1900
This should not happen, could have an other root cause and is OK with Python 3

Target issue:
https://www.synology-forum.de/showthread.html?37898-tvstreamrecord-Aufzeichnen-von-HTTP-Streams&p=866321&viewfull=1#post866321

Fix fail-safe delta

Fix fail-safe delta, which never worked as intended 😞

Edit: using fail-safe delta no longer marks a record as invalid

EPG import fix

Fixed / updated EPG data import from https://xmltv.se (Import URL: http://xmltv.xmltv.se)

Please note: thanks and any credit for using this or any other EPG source must be given solely to their respective maintainers.

Addressing issue #37