I would like an option where decks correspond one-to-one to presets that only include the cards directly within the deck and not any subdecks.
This feature would greatly enhance the FSRS experience for those that want content-aware scheduling, as creating and tracking a preset for each deck can become quite tedious.
You can create n presets and assign them one-to-one to your decks. That functionality exists already, though setup might take a few minutes if you have a lot of decks.
Also see the chapters in Deck Options - Anki Manual for more info about presets and subdecks.
As mentioned above, I am aware of that solution, I would just prefer not maintaining many presets as doing a collection-wide change becomes quite combersome when it has to be repeated for each one.
So what exactly do you propose? How would that feature look like?
A simple FSRS toggle which gives each deck their own preset automatically.
You’re asking for:
But also for:
If you give every deck its own preset, then you’ll have to manage a preset for every deck. I don’t know how you envison having one without the other.
I meant in terms of its internal implementation, each deck will act as if it had its own FSRS preset associated with it by default.
Simply put I want a toggle that completely dissasociates deck presets from fsrs, decks are the unit of optimization for their directly contained cards.
Since FSRS works better with more review history, and presets make it easier to manage multiple decks that have the same settings – it makes sense for FSRS to be managed by preset as well.
It sounds like you’re envisioning that just FSRS parameters and DR will be set deck-by-deck, while everything else in Options will remain set preset-by-preset – is that right?
It’s hard to imagine the decks that vary so starkly in their scheduling needs that they each need different FSRS parameters – but they are similar enough that all the rest of their settings would be the same. Even if you had a couple decks that fit that bill, it seems unlikely it would be necessary for every deck. Given how few users would ever need to manage their collections at that level of detail, so this would be a pretty niche use-case.