Unshackle - Modular Movie, TV, and Music Archival Software

[sipho]

You don't have to use uv. Lots of cats to skin.

[deccavox]

This is the advise I got for uv (I've read it or seen it a few times elsewhere in the past).
If you're aiming for smooth, hassle-free upgrades of `uv`. Here's the rundown on each option:

### Using `pipx`
**Pros:**
- Installs `uv` in an isolated virtual environment, so it won’t interfere with your system or global Python packages.
- Upgrading is a breeze with `pipx upgrade uv`.
- Keeps your Python environment cleaner and avoids version conflicts.
- Ideal for command-line tools that aren’t meant to be part of a larger Python project.

**Cons:**
- You need to have `pipx` installed and properly set up beforehand (though that's usually a one-time thing).

### Using `pip`
**Pros:**
- Simple and direct if you're comfortable with managing Python packages manually.
- Easily scriptable if you're installing as part of a larger setup.

**Cons:**
- Installing globally can lead to dependency clashes or permission issues.
- Managing upgrades might require manual steps like `pip install --upgrade uv`, and sometimes dealing with `sudo`.

### Verdict
For your goal—*easy and reliable upgrades*—`pipx` is the way to go. It treats `uv` as a standalone tool and makes updating as simple as typing one command. Think of it as the best of both worlds: flexibility without the fuss.

In other words. If you use `pip` to initially install 'uv' you are installing it globally (which you want, you want to be able to use uv anywhere on your system). When you update uv, at some time in the future the update could add extra dependencies and those dependencies could be used by other Python packages you have already installed globally some time ago. Then you could end up with 'dependency hell' where different packages rely on different versions of dependencies, you've now got the wrong versions and so you can 'break' your system.

By installing uv via pipx, it lives in its own mini environment, with its dependencies contained and isolated. That means:

Upgrading uv only affects uv and its dependencies.
uv still appears to be being used globally which is good, but it's actually being routed through pipx environment.
It makes it nice and neat and secure.
I've been using uv for some time now for all my projects, not just unshackle, so I'm happy with my setup.

But, it's your choice.

[phased]

Thanks. But really do we need another way? To avoid confusion for everyone it is far simpler to do as the unshackle maintainer suggests.
And if anyone wants to run things in an environment with uv, the command 'uv venv' will create it, and it will tell you how to start it too - 'source .venv/bin/activate' .
From there on it is sp4k.y's instructions. Simple - no confusion.

Once voice, one way. Do your thing if you want but probably best not to over-complicate it for others. Just look at the mess in the devine thread.

[deccavox]

Thanks. But really do we need another way? To avoid confusion for everyone it is far simpler to do as the unshackle maintainer suggests.
And if anyone wants to run things in an environment with uv, the command 'uv venv' will create it, and it will tell you how to start it too - 'source .venv/bin/activate' .
From there on it is sp4k.y's instructions. Simple - no confusion.

Once voice, one way. Do your thing if you want but probably best not to over-complicate it for others.

Fair enough. The thread is really about using unshackle anyway and not about using uv. The github assumes that you have uv installed already. It makes no mention as to how to install uv.

[mickmars]

Thanks Deccavox

I now have the
Error: There are no Services added yet


My yaml says

services:
- /path/to/services C:\unshackle\unshackle\services
- /other/path/to/services C:\unshackle\unshackle\services

What am I doing wrong?

Cheers

[WhiskeyJack]

Thanks Deccavox

I now have the
Error: There are no Services added yet


My yaml says

services:
- /path/to/services C:\unshackle/unshackle/services
- /other/path/to/services C:\unshackle/unshackle/services

What am I doing wrong?

You've entered the weirdest file path and unshackle can't find what you've pointed it to. fix it with

services:
    -  C:\unshackle\unshackle\services
    -  C:\unshackle\unshackle\services

If you have only one service file list that, and delete the details to the other one. I've absolutely no idea why this was added, it should have remained as a single line under directories.

services: C:\unshackle/unshackle/services

[mickmars]

Hi

It now says on yaml line #28

services: C:\unshackle\unshackle\services

and I'm still getting the No Services error

Just so I am clear, I got my services from

https://forum.videohelp.com/threads/414154-Devine-Modular-Movie-TV-and-Music-Archival-...60#post2778797

I unzipped them and placed them in the Unshackle services folder in my C drive

[deccavox]

try

uv run unshackle env info

that lists where it thinks all your paths are.

[iamghost]

directories:
  services: ./unshackle/services

[mickmars]

try

uv run unshackle env info

that lists where it thinks all your paths are.

No config file found, you can use any of the following locations:
├── 1.
│ C:\Users\palmer\AppData\Roaming\uv\tools\unshackle \Lib\site-packag
│ es\unshackle\unshackle.yaml
├── 2.
│ C:\Users\palmer\AppData\Roaming\uv\tools\unshackle \Lib\site-packag
│ es\unshackle.yaml
└── 3.
C:\Users\palmer\AppData\Roaming\uv\tools\unshackle \Lib\site-packag
es\unshackle\unshackle.yaml

[WhiskeyJack]

try

uv run unshackle env info

that lists where it thinks all your paths are.

No config file found, you can use any of the following locations:
├── 1.
│ C:\Users\palmer\AppData\Roaming\uv\tools\unshackle \Lib\site-packag
│ es\unshackle\unshackle.yaml
├── 2.
│ C:\Users\palmer\AppData\Roaming\uv\tools\unshackle \Lib\site-packag
│ es\unshackle.yaml
└── 3.
C:\Users\palmer\AppData\Roaming\uv\tools\unshackle \Lib\site-packag
es\unshackle\unshackle.yaml

I'm on a *nix set, installed using

uv tool install git+https://github.com/unshackle-dl/unshackle.git

unshackle env info points to

unshackle env info
                                                                                
                ▄• ▄▌ ▐ ▄ .▄▄ ·  ▄ .▄ ▄▄▄·  ▄▄· ▄ •▄ ▄▄▌  ▄▄▄ .                 
                █▪██▌•█▌▐█▐█ ▀. ██▪▐█▐█ ▀█ ▐█ ▌▪█▌▄▌▪██•  ▀▄.▀·                 
                █▌▐█▌▐█▐▐▌▄▀▀▀█▄██▀▐█▄█▀▀█ ██ ▄▄▐▀▀▄·██▪  ▐▀▀▪▄                 
                ▐█▄█▌██▐█▌▐█▄▪▐███▌▐▀▐█ ▪▐▌▐███▌▐█.█▌▐█▌▐▌▐█▄▄▌                 
                 ▀▀▀ ▀▀ █▪ ▀▀▀▀ ▀▀▀ · ▀  ▀ ·▀▀▀ ·▀  ▀.▀▀▀  ▀▀▀                  
                   v 3.3.3 Copyright © 2019-2025 rlaphoenix                     
                              v 1.0.1 - unshackle                               
                                                                                
     Config loaded from                                                         
     /home/WhiskeyJack/.local/share/uv/tools/unshackle/lib/python3.12/site-package     
     s/unshackle/unshackle.yaml

it is part of the installation, when freshly installed, the unshackle.yaml will have cursory info that you need to edit for yuor system. It will be likewise if you just downloaded the zip archive from github, or git cloned. Location according to github of the freshly installed unshackle.yaml is

unshackle/unshackle.yaml

[iamghost]

all I did was add new folder under unshackle and add it unshackle.yaml

[Attachment 87927 - Click to enlarge]
no problem so far

[mickmars]

I know where my yaml file is - I just dont know what i need to enter or where I need to enter it to get the env info right and make the services work

my installation method was using the guide in post#6 on this thread

[iamghost]

thats my yaml. all folder is under unshackle folder

[Attachment 87928 - Click to enlarge]

[Attachment 87929 - Click to enlarge]

[deccavox]

My yaml is more or less the same as iamghosts (apart from my services and WVDs are in .\unshackle\unshackle), except I've used absolute paths instead of relative paths

directories:
  services: D:\unshackle\unshackle\services
  cache: D:\unshackle\cache
  cookies: D:\unshackle\cookies
#  dcsl: DCSL # Device Certificate Status List
  downloads: D:\unshackle\Downloads
  logs: D:\unshackle\Logs
  temp: D:\unshackle\temp
  WVDs: D:\unshackle\unshackle\WVDs

Relative is a much better idea since I can then have multiple installations of unshackle installed on my system (if I wanted) even deep within multiple folder paths and use the same yaml file. So thanks iamghost, an excellent idea. I will change mine

All changed and working fine

[WhiskeyJack]

Hi

It now says on yaml line #28

services: C:\unshackle\unshackle\services

and I'm still getting the No Services error

Just so I am clear, I got my services from

https://forum.videohelp.com/threads/414154-Devine-Modular-Movie-TV-and-Music-Archival-...60#post2778797

I unzipped them and placed them in the Unshackle services folder in my C drive

I unzipped them and placed them in the Unshackle services folder in my C drive

and are you correctly pointing to the services folder?
Can you show the full path on your PC to us, and show us the yaml?

The issue here, unfortunately, is yourself. This is a problem you have caused.
So, be patient as people here try to offer advise based on how they interpret how you state the issue you are facing.

[F1sav28]

I have the same issue as mickmars, I posted this also at #26 but it understandably got lost amongst a bit of chatter. I'm sure it's related to those odd indents under the services line in the default yaml. I finally deleted them entirely after fiddling with "no services added yet" reports, and it all worked (I downloaded a test season and assumed I'd fixed it), but the very next day, despite me not touching it unshackle had fallen apart and just wouldn't reopen. Through tweaking and rolling my yaml back it was definetly breaking down with those indents, for me it seems it will only operate whilst they are present in the original state.

Every time I try and remove or alter these lines, the whole unshackle fails. I can append to them, but nothing happens in terms of it finding a service if I do.

    - /path/to/services
    - /other/path/to/services

It might be useful just to see how other yaml look for the entire section between # override... down to #pre-define...
Have you guys deleted the indent section?

I also tried the uv run unshackle env info command to check myself, but that doesn't work, even on the fresh step by step install that command just errors.

│   193 │   main_globals = sys.modules["__main__"].__dict__                    │
│   194 │   if alter_argv:                                                     │
│   195 │   │   sys.argv[0] = mod_spec.origin                                  │
│ ❱ 196 │   return _run_code(code, main_globals, None,                         │
│   197 │   │   │   │   │    "__main__", mod_spec)                             │
│   198                                                                        │
│   199 def run_module(mod_name, init_globals=None,    

│    84 │   │   │   │   │      __package__ = pkg_name,                         │
│    85 │   │   │   │   │      __spec__ = mod_spec)                            │
│ ❱  86 │   exec(code, run_globals)                                            │
│    87 │   return run_globals                                                 │
│    88                                                                        │
│    89 def _run_module_code(code, init_globals=None,       

│    92 │   for name in sorted(dir(config.directories)):                       │
│    93 │   │   if name.startswith("__") or name == "app_dirs":                │
│    94 │   │   │   continue                                                   │
│ ❱  95 │   │   path = getattr(config.directories, name).resolve()             │
│    96 │   │   for var, var_path in path_vars.items():                        │
│    98 │   │   │   │   path = rf"%{var}%\{path.relative_to(var_path)}"   

AttributeError: 'list' object has no attribute 'resolve'

As I mentioned in first post, the install went fine, added wvd etc and nothing suggested an issue, I just can't point it to a service folder again. The command uv run unshackle env check works out fine, that's all ticked off.

I'll try yet another clean install (alhtough it does install fine), but I suspect it will not open that info command or find services. It's likely something simple, at least it seems it's not just me at the moment though.

Thanks all.

[WhiskeyJack]

I have the same issue as mickmars, I posted this also at #26 but it understandably got lost amongst a bit of chatter. I'm sure it's related to those odd indents under the services line in the default yaml. I finally deleted them entirely after fiddling with "no services added yet" reports, and it all worked (I downloaded a test season and assumed I'd fixed it), but the very next day, despite me not touching it unshackle had fallen apart and just wouldn't reopen. Through tweaking and rolling my yaml back it was definetly breaking down with those indents, for me it seems it will only operate whilst they are present in the original state.

Every time I try and remove or alter these lines, the whole unshackle fails. I can append to them, but nothing happens in terms of it finding a service if I do.

    - /path/to/services
    - /other/path/to/services

It might be useful just to see how other yaml look for the entire section between # override... down to #pre-define...
Have you guys deleted the indent section?

I also tried the uv run unshackle env info command to check myself, but that doesn't work, even on the fresh step by step install that command just errors.

│   193 │   main_globals = sys.modules["__main__"].__dict__                    │
│   194 │   if alter_argv:                                                     │
│   195 │   │   sys.argv[0] = mod_spec.origin                                  │
│ ❱ 196 │   return _run_code(code, main_globals, None,                         │
│   197 │   │   │   │   │    "__main__", mod_spec)                             │
│   198                                                                        │
│   199 def run_module(mod_name, init_globals=None,    

│    84 │   │   │   │   │      __package__ = pkg_name,                         │
│    85 │   │   │   │   │      __spec__ = mod_spec)                            │
│ ❱  86 │   exec(code, run_globals)                                            │
│    87 │   return run_globals                                                 │
│    88                                                                        │
│    89 def _run_module_code(code, init_globals=None,       

│    92 │   for name in sorted(dir(config.directories)):                       │
│    93 │   │   if name.startswith("__") or name == "app_dirs":                │
│    94 │   │   │   continue                                                   │
│ ❱  95 │   │   path = getattr(config.directories, name).resolve()             │
│    96 │   │   for var, var_path in path_vars.items():                        │
│    98 │   │   │   │   path = rf"%{var}%\{path.relative_to(var_path)}"   

AttributeError: 'list' object has no attribute 'resolve'

As I mentioned in first post, the install went fine, added wvd etc and nothing suggested an issue, I just can't point it to a service folder again. The command uv run unshackle env check works out fine, that's all ticked off.

I'll try yet another clean install (alhtough it does install fine), but I suspect it will not open that info command or find services. It's likely something simple, at least it seems it's not just me at the moment though.

Thanks all.

do you have only one services folder?
If so, only point to that one, and delete the second line. I've no idea why that layout causes such errors, it's a bloody pain to pin down, but that second line in services is most likely causing it. so
instead of

services:
    - /path/to/services
    - /other/path/to/services

use, and seriously use this

 services: /path/to/services

[deccavox]

This is the beginning part of my unshackle.yaml (up to # Use pywidevine Serve-compliant Remote CDMs) which seems to work fine. Obviously the directory paths reflect my setup. The creds I've made up and the cmd wvd. But you get the idea. I've kept the 2 space indent that Sp5rky adopted. I've used backslashes since I'm Windows based (although forward slashes should still work in Windows when using Python).

# Group or Username to postfix to the end of all download filenames following a dash
tag: user_tag

# Set terminal background color (custom option not in CONFIG.md)
set_terminal_bg: false

# Muxing configuration
muxing:
  set_title: false

# Login credentials for each Service
credentials: 
  ALL4: me@gmail.com:buggeroff
  DSCP: me@gmail.com:buggeroff
  TVNZ: me@gmail.com:buggeroff
#  ROKU: email:password

# Override default directories used across unshackle
directories:
  services: .\unshackle\services
  cache: .\cache
  cookies: .\cookies
#  dcsl: DCSL # Device Certificate Status List
  downloads: .\Downloads
  logs: .\Logs
  temp: .\temp
  WVDs: .\unshackle\WVDs
#  prds: PRDs
  # Additional directories that can be configured:
  # commands: Commands
  # vaults: Vaults
  # fonts: Fonts

# Pre-define which Widevine or PlayReady device to use for each Service
cdm:
  default: ANDROID_2222_l3
  EXAMPLE: PRD_1

# Configuration data for each Service
services:
  iP:
    cert: .\certs\bbciplayer.pem

[iamghost]

here, everything should be ready for you, add folders, wvd, prd, services, unshackle.yaml already sort out.
just install uv then your good
https://gofile.io/d/WWR5tO
https://files.videohelp.com/u/301156/unshackle.rar

[F1sav28]

Thanks, I've played around got it working. The annoyance is, it's the same edit that I made two days ago, so why it works now and not in earlier attempts today, I've no idea.

Anyhow, this is my current test yaml below which I've just downloaded an episode without any issue.

I have also closed the terminal window and run it again, it still worked. I'm a tad stumped why this itteration was a success, it's genuinely the same as the one that stopped working, but hey ho. All I can think of at the moment I've done differently, is start fresh but thus far I've only added the ITV service instead of the full volume. I might do that piece by piece to see if it's something within the services folder itself the installation doesn't like...

The default yaml has all the proxy nonsense, which I haven't edited yet which by default forces an error. Bypassing it with --no-proxy for testing did work. Is there a steer on what rows are safe to jettison with all the proxy stuff?


[Attachment 87939 - Click to enlarge]

[deccavox]

The default yaml has all the proxy nonsense, which I haven't edited yet which by default forces an error. Bypassing it with --no-proxy for testing did work. Is there a steer on what rows are safe to jettison with all the proxy stuff?

Everything from '# Legacy NordVPN configuration (use proxy_providers instead)' onwards (including '# External proxy provider services' I deleted. They're of no interest to me. If I want to connect to NZ or Aus I do so through my VPN (SurfShark) and it works OK. I'm just testing out TVNZ now and it's fine.

What's been nice about this thread is the way everybody has been willing to help one another. Excellent team work folks.

[mickmars]

i entered uv run unshackle env check
and found it says
Shaka-Packager │ ❌ │ Not Found

How do i add shaka packager to my installation, please ?

[iamghost]

i entered uv run unshackle env check
and found it says
Shaka-Packager │ ❌ │ Not Found

How do i add shaka packager to my installation, please ?

add it in unshackle folder

https://files.videohelp.com/u/301156/packager-win-x64.exe

[mickmars]

i entered uv run unshackle env check
and found it says
Shaka-Packager │ ❌ │ Not Found

How do i add shaka packager to my installation, please ?

add it in unshackle folder

https://files.videohelp.com/u/301156/packager-win-x64.exe

I added it to unshackle folder and then unshackle\unshackle folder - Still same error ?

[iamghost]

1st I remove packager-win-x64.exe from unshackle folder (not ./unshackle/unshackle/packager-win-x64.exe)
its show red X
then put it back ./unshackle/packager-win-x64.exe
it work fine

[Attachment 87940 - Click to enlarge]