(If you're going to mumble about "why would you want to disable it?", etc., just close the tab.)

Ideally, I want to strictly disable the reasoning (on the models that allow it).
> "reasoning": {"enabled": false}
> "thinking": {"type": "disabled"}
Both of these official parameters kinda work, but it still triggers reasoning sometimes.

Now, is there a way to manually strip it out in the SillyTavern?
So far, I have tried:
- adding ["<think>", "</think>"] in the Custom Stopping Strings. Didn't work.
- adding <think>, </think> in the Auto-swipe. Didn't work.

Ok. Here's the full context:

[1] I've been using the same PC for more than 5 years without any problem.
Previous spec:
-CPU: AMD Ryzen 7 3700X 8-Core
-Motherboard: ASUS TUF Gaming B450M-PRO S STCOM
-RAM: Samsumg DDR4-3200 (16GB) x2
-Drive: Samsung 860 EVO (500GB) + HDD
-GPU: GTX 1060 6G
-Monitor: DELL UltraSharp U2719DC (QHD/60Hz)
-Case: be quiet PURE BASE 500 WINDOW (WHITE)
-Power: Micronics CASLON M 700W 80PLUS 230V EU

[2] Recently, I decided to upgrade it.
-I changed my motherboard to ASUS TUF Gaming B550M-PLUS.
-I reinstalled Windows 10 from scratch on my SSD (860 EVO).

[3] Everything works properly, except that I start to get random bluescreens and forced shutdowns.
I ran WinDbg on the generated memory.dmp files. Here are the logs if anyone wants to take a look. It seems to point to the same kernel failure during the context switch:
https://pastebin.com/5CBBCJ4t
https://pastebin.com/e3S0aASc
https://pastebin.com/evAxhsdC

---
This is the situation so far.

Any insight/advice/help to solve the issue?

For context: I'm using it via OpenRouter, and I disabled reasoning.

When it generates a response, it repeats the same response twice, verbatim.

Anybody having the same problem and have solved it?

Edit: Solved. It was a provider issue.
Also, reasoning is a cancer.

https://github.com/acc4github/kdenlive-omnifade

This is my 4th plugin, following Camera Shake Organic, OmniSlide, and OmniWipe.

This is a relatively simple crossfade transition plugin with zoom/speed control.

https://preview.redd.it/pxtnniubl58h1.jpg?width=416&format=pjpg&auto=webp&s=7957d0d7c01b8b1d77622c31a00c69c58adb3160

Features

- Fade Progress (position) – standard transition progress, animated from 0 to 1.
- Speed Curve (%) – applies a power‑law easing curve to the fade timing. Higher values create stronger acceleration/deceleration.
- Gentle Arrival (%) – adds a smooth slowdown at the end of the transition.
-> When Speed Curve is 0%, it acts as a reverse ease‑out (fast start, slow end).
-> When Speed Curve is used, it creates a deceleration zone near the end – the fade eases into the final frame.
- Independent Zoom per Clip – choose separate behaviours for the outgoing and incoming clips:
-> Expand – clip grows larger over the transition.
-> Static – no zoom (scale = 1).
-> Shrink – clip shrinks over the transition.
-> Zoom Strength (%) – controls how intense the zoom effect is.
- Blur Strength – radial blur that automatically adjusts its amount based on speed.
- Fill Background (average) – fills the empty background with the average colour of each clip.
- Invert – swaps the incoming and outgoing clips.

Demo

https://reddit.com/link/1u9qao5/video/797eqiodl58h1/player

Limitations

1. When the Fill Background is off and the clip is blurring, the black/dark edges appear.

As I explained in my other plugin posts, this is seemingly due to the limitations in Kdenlive/frei0r framework. The incoming clip data from Kdenlive includes an invisible black padding in the buffer. This padding leaks in when the plugin does a fuzzy pixel sampling.

2. It's a bit heavier than other effects.

Turns out, cross-fading is far more expensive than simple moving... I optimized as much as I could, and it should be ok with casual usage, but I recommend not stacking it up.

License

This project is licensed under the GNU General Public License v3.0 (GPL-3.0).

---

Disclaimer: it works well on my PC, but I cannot guarantee that it will for you. Use it at your own risk, and it'd be appreciated if anyone reviewed the code in my GitHub.

I'm coding with Grok, and it was amazing until like a week ago. But it became extremely mistake-prone, context-blind, and just dumb in general.

I can tangibly feel the quality difference. The same design/debug now literally takes 20 more requests to get a semi-correct result.

I generally love Grok and I'm continuing to use it. I'm just wondering if I'm hallucinating on this.

https://github.com/acc4github/kdenlive-omniwipe

This is my third plugin after I made Camera Shake Organic and OmniSlide(renamed from OmniSwipe).

Learning from making the previous 2 plugins, I was able to make this one relatively smoothly.

This one is designed to cover wipe transitions.

Features

https://preview.redd.it/wgsf3s5jig7h1.jpg?width=447&format=pjpg&auto=webp&s=5093d8a871b69889e6a572c73d4ab361e5acad94

- Limit Range to Clips: Content-aware toggle
-> ON: Detects non-transparent areas in both clips and restricts the wipe area to their bounding rectangle.
-> OFF: Wipes the entire frame.

- Direction Axis + Wheel: Base axis (0°, 90°, 180°) combined with wheel offset for wipes in any angle.

- Speed Curve (%): Controls acceleration/deceleration using power-law easing. Higher values create stronger non-linear timing.

- Gentle Arrival (%): Adds smooth slowdown at the end. It switches between 2 mechanisms depending on the Speed Curve's state.
-> When Speed Curve is 0%: Acts as reverse curve for fast start + deceleration.
-> When Speed Curve is used: Expands a 'deceleration zone' from the clip's end. The wipe will start to slow down as the playback enters this zone. At 100%, the entire clip is under Gentle Arrival's control.

- Border Type: None (simple wipe) or Bar (traveling colored bar with width and HSV color controls).

- Border Blur: Blurs the border (including the bar).

- Invert: Swap incoming and outgoing clips.

Demo

https://reddit.com/link/1u6j24g/video/qq10jkt1jg7h1/player

Limitations

1. The Bar color controls are separated.

I wanted to use Kdenlive's native color picker, but for some reason, it's not well-supported in the transition plugins. I had to break it into individual Hue/Saturation/Value/Opacity sliders.

2. When using Blur, black edges will appear outside the clip area.

This is due to the same annoying limitations in Kdenlive that I explained here. The incoming clip data from Kdenlive includes an invisible black padding in the buffer. This padding leaks in when the plugin does a fuzzy pixel sampling. Unfortunately, this seems to be really hard to avoid under the current Kdenlive plugin architecture.

https://preview.redd.it/9td22fnlmg7h1.jpg?width=766&format=pjpg&auto=webp&s=39750cffcb746d818ba4281bcaad4d6df0795f70

License

This project is licensed under the GNU General Public License v3.0 (GPL-3.0).

---
As a disclaimer, it works well on my PC, but I cannot guarantee that it will for you. Use it at your own risk, and it'd be appreciated if anyone reviewed the code in my GitHub.

+
On a sidenote, I refactored and heavily optimized my other plugins. I'm also planning to make a Fade transition plugin next(OmniFade).

https://github.com/acc4github/kdenlive-omniswipe

This is my second custom plugin, after making Camera Shake Organic.

I wanted to make a custom transition plugin that can handle pretty much any swipe/slide transition, without having to load or tweak multiple plugins.

I used Grok(AI) in actual coding (since I have literally zero background knowledge in programming), but I spent a lot of time trying to understand and design the abstract-level architecture and data flow myself.

I also ran into a lot of technical API limitations in Kdenlive / frei0r that made me seethe and pull my hair out. (There seems to be many weird things going on there...) But in the end, I managed to solve or work around them all eventually.

I'm happy about how it came out.

Features

https://preview.redd.it/wcpzb6336v6h1.jpg?width=447&format=pjpg&auto=webp&s=68e305d453c06ac5c3853a8870f2363ddce44dc8

- Arrival Direction Axis / Wheel: Controls the angles at which the incoming clip enters.
- Departure Direction Axis / Wheel: Controls the angles at which the outgoing clip disappears (when moving).
- Outgoing Behavior: Static / Move / Fade.
- Speed Curve (%): Higher % = stronger acceleration.
- Gentle Arrival (%): Add smooth slowdown to the clip's movement. It switches between 2 mechanisms depending on the Speed Curve's state.
-> When Speed Curve is at 0%: Gentle Arrival acts like a reverse Speed Curve, adding a negative logarithmic curve to the speed. As you dial up Gentle Arrival, the curve will become stronger, and clips will start fast and decelerate towards the end.
-> When Speed Curve is used: Gentle Arrival's intensity will symmetrically mirror Speed Curve's logarithmic curve. And as you dial up Gentle Arrival, it will expand the 'effective zone' from the clip's end. The clips will start to slow down as the playback enters this zone. At 100%, the entire clip is under Gentle Arrival's control.
- Motion Blur (%): Add directional blur to the moving clips.
- Edge Smoothing:
-> ON: Smoothing out the clip's edge pixels.
-> OFF: The clip's boundaries are exactly snapped to its actual content.
- Invert: Invert the effect.

Demo

https://reddit.com/link/1u4233v/video/5523jhltvw6h1/player

Limitations

1. The current motion blur is very low-res to prioritize performance.

I'm not sure why, but blurring or anything that involves higher sampling seems extremely costly in Kdenlive plugins. (I cross-checked it by adding bilinear sampling to other official plugins.)
I didn't add controls for blur quality since I thought it was not that important, but if anyone requests, I might later.

2. 'Edge Smoothing' introduces dark edges on blurred clips.

(I almost puked while dealing with this issue.) This is seemingly due to Kdenlive's limitations. When the plugin receives the clip data from Kdenlive, it seems to come with an invisible padding around the actual content clip, matching the project's entire resolution. This invisible area lives in the buffer, though it's typically invisible in the output/preview.

Pardon the image. Art credit: @QupoStuv35

As you can see in this debug image I used, what the plugin recognizes as 'a clip' is actually this entire area that includes this buffer. (The magenta part in the picture is what the plugin thinks is the 'outside area'.)
This becomes problematic when you try to add blur or any feature that involves fuzzy pixel sampling. The fuzziness pulls this black area into the visible area at the clip's edges, and 'black edges' appear out of nowhere.

https://preview.redd.it/f795exuovv6h1.jpg?width=728&format=pjpg&auto=webp&s=4ea372d2ac0a1a45872be00fe4465f0453039a06

From the plugin's perspective, this padding seems to be literally merged with the clip's content and is inseparable.
To solve this problem, I added a 'content detection' in the code. It scans the image to detect where the black/transparent area ends, and strictly crops the processing area to the actual content.
However, this approach makes the edge sharp or jaggy in some cases, because the cropping is extremely strict to prevent the black from leaking in. That's why I made it an option to give users more control.
- When 'Edge Smoothing' is on: This content detection mechanism is disabled, and the plugin samples the entire area with the invisible black padding. (That being said, the black edge will appear with this option, especially if the clip is blurred.)
- When 'Edge Smoothing' is off: The content detection is enabled, snapping the processing area to the clip's actual content.
(In Camera Shake Organic, I additionally implemented additional padding to smooth out all 4 edges.)

3. Minor issues

- It doesn't support keyframes.
- The thumbnail is not generated in the docker.
I couldn't figure out how to do these. I'm not sure if Kdenlive supports them or not with the custom plugins in the first place, tho.

License

This project is licensed under the GNU General Public License v3.0 (GPL-3.0).

---

It's been a long, hard journey.

As a disclaimer, it works well on my PC, but I cannot guarantee that it will for you. Use it at your own risk, and it'd be appreciated if anyone reviewed the code in my GitHub.

It's a small, heavily modified c++ plugin for a video editor I use. I had no background knowledge in programming (aside from the HTML/CSS and simple gamemaker engines), and I can't believe I made it work!

I asked Grok to implement features one by one, analyze code lines for a normie, checking each step carefully to not mess it up.

It now works smoothly without bugs. I'm very happy. :>

+
I tried other AIs too (-which are supposed to be good at coding), but weirdly enough, Grok was the best to work with.

Other AIs tend to be nitpicky and rigid, whereas Grok was very flexible and straightforwardly gave what I asked for within its capacity without snobbily filtering my intent.

https://github.com/acc4github/kdenlive-camerashake-organic

This is a modified version of Camera Shake Ultimate by PakeMPC.

The original effect is too repetitive and static to my taste, and since nobody really gives a shit about such a niche effect, I made a fork myself. It should provide much more random, organic 'hand-held' movements.

This is the first time I've ever done anything remotely coding-adjacent. I used Grok with literally zero background knowledge.

Use it at your own risk, and it'd be appreciated if anyone reviewed the code.

https://preview.redd.it/2q495fukht5h1.jpg?width=444&format=pjpg&auto=webp&s=b0bacc3bc6074a5aabac758d640a48d0509d8414

Comparison:

original

modified

I tried making a custom profile with CBR and high bitrates (e.g., 384kbps, 512kbps, etc), but the audio in the actual output file is always 247kbps or lower. It seems the aac bitrate is capped.

How can I achieve a higher audio bitrate with aac format?

(As for why I need this, it's for technical reasons. Just close this post if you're going to say things like "why would you need this?", "there won't be audible differences", etc.)