roycho87

Activity

Stars and mentions · Last 30 days, Oct 20 – Nov 18

GitHub stars0
Mentions10
01234Oct 20Nov 3Nov 18
UTC days · repositories roycho87 owns0 repositories

Top repositories

roycho87’s repositories ranked by pull request authors, as on trending.

Loading

Contributes to

Repositories outside roycho87’s account where roycho87 opened or reviewed pull requests in the past 365 days.

Who noticed roycho87

Everyone who starred or forked roycho87’s repositories since the archive began in 2011.

Notable accounts

Ordered by the stars their own repositories have received.

Biggest fans

Accounts that starred the most of these repositories.

Breakout weeks

Each repository’s best week of new stars, with the release published around it.

Mentions

10posts
Nov 190 posts
  1. Geiru Context Suite is a ComfyUI node pack that stops long MiniMax H3 videos from drifting by pulling every shot back to the first clip's clean frame. It can also render in overlapping windows; this clip is from one two-minute render. roycho87/geiru_context_suite t.co

    18 likes · 3 reposts · 845 views
  2. 既存のH3 Motion ContextかMultiRefと組み合わせて使う追加ノード。 同一シーンの連続生成向けで、場面転換時は保護OFF推奨。完全静止シーンでは徐々に暗くなる問題も残る。 GitHub: roycho87/geiru_context_suite

    2 likes · 1 repost · 140 views
  3. Reddit · · r/StableDiffusion · u/roychodraws · roycho87/workflows

    Flip a switch and stop your Videos from Degrading. 50 Clip Test No Degrading at the end. Geiru Context Suite I did the thing where I nuke the first post because I forgot to do something also the title sucked and I forgot to credit literally the most important contributor in the video. Skip to 8:05 to see the results. Also, if you guys are curious you can visit this repository to read about everything I tested to get to this point. roycho87/NerdNotes Lots of information in there. Maybe you guys can read it and come up with an even better solution. If you have some good info, please leave an issue on the Github and I'll compile it all together. Any experiments you've done and the results, what you've learned etc. All of it is helpul. Geiru Context Suite: degradation protection for long MiniMax H3 chains The main part of this that allowed this to work came from Ethanfel. He created the context noise method that allowed this to work so giant shout out to him. The Clown Context Suite is now the Geiru Context Suite. She's named after the clown, and the new name keeps it from getting mixed up with ClownShark's nodes. Your old workflows still load fine. The big addition is a degradation protection switch on Geiru Context that turns three nodes on together. Geiru Keystone locks a clean frame 0 from a source clip into every shot. Geiru Late Lock tacks that clip's capstone onto the back late in the steps. Geiru Context Noise, based on ethanfel's idea, gives the held frames part of the noise instead of handing them over perfectly clean. Turn it on for long stretches of one scene and off around cuts, since scene changes reset the drift on their own. Keystone can also load its source clip straight from your latent folder now, so when the scene changes you only change one number. Also new: a context noise switch on Geiru Hybrid Windows, and a ready-to-go example workflow, noisy_clown_example. I tested it on a 50-clip chain (about 5½ minutes): running on a beach, then a café, a walk through town and a garden. The plain chain was falling apart by clip 20, while the protected one still looked clean and barely drifted in the still scenes. Side by sides and all the numbers are in my notes. It's not perfect yet, since fully static shots can still slowly darken, but it's the best I've gotten so far! remember to use this to combine your clips. https://github.com/roycho87/workflows/tree/main/workflows/seamless_video_combiner You have to clip off the last 17 frames and join at the 22nd frame with 39 frames of overlap for the settings in the workflow. Repo: roycho87/geiru_context_suite Test notes: roycho87/NerdNotes Credits (none of this exists without them): - seitanism, for the masked latent context everything here is built on: seitanism/ComfyUI-H3-Motion-Context-MultiRef - NikoDemon80, for Motion Context, the Chain node and a ton of drift testing: NikoDemon80/ComfyUI-H3-Motion-Context - ethanfel (Lumifel), for the context noise idea: ethanfel/ComfyUI-MiniMaxH3-Context-Loop - drozbay, for H3 latent masking: drozbay/MaskVidExperiments - kijai, for H3 support and context windows in ComfyUI: github.com/kijai - JalenBrunson, for Hybrid Windows: Jalen-Brunson/ComfyUI-HybridWindows - TrentHunter82, for TrentNodes, whose degrade node made the frame 0 tests possible: TrentHunter82/TrentNodes edit: Currently running a test on best settings to use for this and will update the nodes with best defaults after it's done tomorrow as it's about 19 hours of generating. You can check the nerdnotes to see the test and how it's going. After reviewing the tests i was able to determine that the best settings for noise is 1 and linear. I've changed that to the defaults.

    228 points · 61 comments
  4. The Clown Context Suite has changed its name to the Geiru Context Suite. Its a custom node suite specializing in long form MiniMax H3 vid gen and it helps reduce / eliminate vid gen degradation over long gens. roycho87/geiru_context_suite

    3 likes · 2 reposts · 505 views
  5. Reddit · · r/StableDiffusion · u/roychodraws · roycho87/NerdNotes

    I taken all the info I've found on degradation and Frame 0 and compiled it. I'm updating it in real time. github.com/roycho87/NerdNotes/tree/main If you have comments or suggestions you can leave an issue in the NerdNotes and Claude or I will check them every hour. You can ask him questions and he will respond about things we've done or found. Just open an issue on the github. There's lots to read in there including articles from papers about similar issues with other models. Best thing you can do is direct him to resources to look up on the topic. Just post a link in the git issue. Claude will add your biological and technological distinctiveness to our own. Your culture will adapt to service us. Resistance is futile.

    58 points · 29 comments
  6. Reddit · · r/StableDiffusion · u/roychodraws · roycho87/clown_context_suite

    Try this workflow, too. github.com/roycho87/clown_context_suite/blob/main… .98 MP No Upscaler Took about an hour on a 5090. It's slightly slower because to use the capstone and keystone i have to render about 14 extra steps but the results are pretty amazing. It manages to give near perfect consistency the entire way by rendering the full 8 steps of each context motion using keystone and capstone to prevent degradation from building too significantly, so that each next part of the chain can build off a fully denoised section. Then it throws away the top 2 steps of every window and does 2 context window passes. Final result is a perfectly consistent video with no degradation that you can make at pretty extreme lengths. roycho87/clown_context_suite Clowntext Hybrid Windows Credits This node is not my idea. It's built on kijai's MiniMax H3 context windows, which are in ComfyUI now (PR #17425), and it works the way JalenBrunson's ComfyUI-HybridWindows does (based on the Rolling Diffusion paper). All credit to them. I just added the keystone and capstone feature to it, to help everyone make longer videos without degradation. What it does Instead of chaining clips, it renders the whole video in one go, in overlapping windows, so memory stays at one window: 1. Window 1 renders the first switch_step steps, and a snapshot is saved. 2. Window 1 carries on to the last step, only to get its finished first frame (the keystone) and its last single-frame latent (the capstone). That finish is thrown away and window 1 goes back to the snapshot. 3. Windows 2, 3 and on render the first switch_step steps one after another. Each one's overlap with the window before is locked to that window's result. The keystone is locked into each window's first slot, and the capstone is tacked onto its back from capstone_step on (and cut off again). 4. The last steps run as blended context windows over the whole video, which smooths the joins. With keystone and capstone off, it works like plain hybrid windows. In my test (a 60-second render, 17 windows, same seed), the plain version lost a lot of detail by the end and the keystone + capstone version held its detail much better. Plug the model through it (model in, model out to the guider). It needs a ComfyUI with MiniMax H3 context windows: update ComfyUI if the node is missing. |Setting|Meaning| |:-|:-| |context_length / context_overlap|Window size and overlap in frames (17n + 5). 124 / 39 is about 5 seconds per window.| |switch_step|Steps each window renders on its own before the blended finish. 6 of 8 = steps 1-6 window by window, 7-8 blended.| |keystone_swap|Window 1's finished first frame is locked into the first slot of every later window.| |back_capstone|Window 1's finished last single-frame latent is tacked onto the back of every later window.| |finished_handoff|On: every window renders all the way to the last step, and the next window's overlap is locked to those finished frames. Every window goes back to its switch_step snapshot before the blended finish. Costs the last steps once more per window.| |capstone_step|Steps before the capstone comes in. Keep it below switch_step (4 with 6 = on for steps 5-6), or it never comes in.| |fuse_method|How the blended steps average the windows (pyramid).| |freenoise|Reuses window 1's noise for every window: more consistent, but motion can repeat. Off gives more variety.| |split_conds_to_windows|Give each window its own prompt (see below).| |detail_latent|Optional: use this latent's first frame as the keystone instead of window 1's.| |sound_first|Off by default. On: renders the sound first on its own (picture at 64x64), then locks it in and renders the picture.| One prompt per window: make one prompt node per window, join them in order with ComfyUI's Conditioning Combine (chain them for more than two), plug the result into the guider, and turn split_conds_to_windows on. Each window takes the prompt for the part of the video under its middle, so with as many prompts as windows, window 1 gets prompt 1, window 2 prompt 2, and so on. One prompt for a whole minute makes every window try to do the whole thing, so the motion repeats.

    85 points · 38 comments
  7. 作者の比較では、10クリップ目の色ズレ指標が6.4→2.9に改善。 さらに「Clown Late Lock」で、元のポーズに引っ張られる問題を抑える設計。 GitHub: roycho87/clown_context_suite Reddit: reddit.com

    1 like · 86 views
  8. Reddit · · r/StableDiffusion · u/roychodraws · roycho87/clown_context_suite

    Try this workflow, please. It cuts degradation in half just by adding it. I'm still sick. slowing degradation by about 60% while having virtually no impact on motion. reddit.com Please try it. Test it. Fuck with the settings. Leave comments on the github or in this post. Be my little beta testers. github.com/roycho87/clown_context_suite/blob/main… it should work pretty much like regular motion context. the only difference will be how you join the videos and when you change your scene you need to disable it while the scene changes and change the source latent to the beginning of that new scene in the clown keyframe node. >eli5 explaination. >when you generate something you're basically stacking all these dominoes in a line, and when you generate it, all those dominoes lean on eachother to form a picture. >Motion context, as it has been used, has been taking the end of that domino chain and restarting a new chain, but we didn't realize that everything that made that picture good was in that very first domino. >so i changed it so that when we take the end of the domino chain to form a new picture, i also pick up that first domino and bring it with so that the picture still comes out good. Info from the readme. roycho87/clown_context_suite Clown Keystone and Clown Late Lock Every shot in a chain is made from the one before it, so small colour and sharpness changes build up. Clown Keystone puts a latent from clip 1 into every shot, so each one is pulled back to how clip 1 looked. H3 latents come in 17-frame blocks of 1 + 4 + 4 + 4 + 4 frames. The first latent of each block is a single frame on its own: - keystone = clip 1's first latent (frame 0). - capstone = clip 1's last single-frame latent (frame 187 of a 192-frame clip). Keystone only swaps those single-frame latents, so nothing else in the shot moves. |Setting|Meaning| |:-|:-| |enabled|On / off.| |graft_mask|0 = kept exactly (default). 0.2-0.3 = kept roughly. 1 = ignored.| |source_clip|The clip the keystone and capstone come from (1). On that shot and earlier nothing is grafted. Only used when shot_number is plugged in.| |placement|keystone front (default), keystone front + back, capstone front + back, keystone front + capstone back. front = the shot's first latent, back = its last single-frame latent.| |Input|Meaning| |:-|:-| |clip 1 (keystone / capstone)|A Load Latent fixed on clip 1. Keep it outside the Chain group so the Chain buttons don't change its number.| |shot_number|From Clown Shot Counter. On shot 1 clip 1 isn't loaded (it doesn't exist yet).| Clown Late Lock goes between Keystone and the sampler: latent from Keystone in, latent out to the sampler; model in, model out to the guider. For the first swap_step steps (default 4) the grafted slot is free, so the shot decides its own motion and pose. From the next step on it's locked to what Keystone put there. slots picks which slot: capstone slot (back) (default), keystone slot (front), or both. It only touches slots Keystone actually filled, so on shot 1 it does nothing. A capstone locked from the start pulls the pose back toward clip 1. Late Lock avoids that. Comparison, clip 10 of the same 10-clip chain: no Keystone (base), keystone front, and keystone front + Late Lock capstone. In a 10-clip test (measured about 20 frames from the end of clip 10), colour drift from clip 1 went from 6.4 with no Keystone, to 3.9 with keystone front, to 2.9 with keystone front + Late Lock capstone. Over-sharpening dropped as well. Joining: the grafted frames are clip 1's, not part of the shot, so use the 17 + 22 cut: cut the last 17 frames of each clip and the first 22 of the next. In Seamless Video Combiner: Use Beginning pair on, Beginning Overlap 39, Beginning Join 22.

    130 points · 48 comments
  9. Reddit · · r/StableDiffusion · u/roychodraws · roycho87/clown_context_suite

    Introducing Clown Prophecy (The only actually fix to degredation) Clown Context Suite: chain MiniMax H3 clips without them slowly turning to mush If you’ve chained H3 clips, you know the problem. Every new clip starts from the tail of the last one, and each time a little detail gets lost. That loss stacks up, so by clip 10 everything looks soft and washed out. The reason is that we only ever tell the model where to start. We never tell it where to end. It’s like telling an archer roughly which way to aim but never giving them a target. They can be the best archer in the world and they still won’t hit the spot you wanted. So I gave it a target. There are three pieces: 🎈 Clown Context takes the last frames of the previous clip and pins them to the start of the new one, so the motion carries over smoothly. 🔮 Clown Prophecy is the time travel part. Before a shot is rendered, it renders just the ending of that shot as a short, fresh clip, straight from the shot’s prompt and reference pictures. Because it’s made from scratch and not from a tired old tail, it’s full quality. It’s basically a picture of how the shot is supposed to end, from a video that doesn’t exist yet. 🤡 Clown Anchoring takes that ending and pins it to the back of the shot. Now the shot has a good start from the last clip and a clean target at the end, and the model has to fill in the middle and land on good-quality frames. Every time you do that, the quality gets pulled back up. Run Prophecy every couple of shots and the degradation never gets bad enough to notice. Other stuff in the pack: - Bypass switch and “run every N shots”, so you can drop it into any workflow and only use Prophecy when you want it. - Clown Shot Counter can count your saved clips by itself, so batches just work. - An example workflow is included. GitHub: roycho87/clown_context_suite big thanks to u/shutupyourewrong for helping me brainstorm this. I wouldn't have gotten to this point without bouncing ideas off him. Also for giving me the name. Also, believe it or not I have to give some credit to foxydits. He claimed the secret to stopping degradation was to put an end frame reference image which.... was completely wrong... but it did spark the idea that helped me come up with this. In honor of his contribution I've changed the name of my workflow. edit: 2 bugs just were fixed on the github. should work with all openai urls now as well as ollama. there was a bug where prompts being edited would run the same cached anchor and that should also be fixed. any new input will clear the cached anchor and run. edit2: it's very important that you prompt correctly otherwise this does not work, even in manual mode. i updated the readme >In ollama and manual mode, Clown Prophecy Prompt rewrites your shot prompt so it only describes the ending. To do that it has to find the parts of your prompt, so use the standard H3 reference-mode layout. >Easiest way to get the format right: write your prompts with the H3 Prompt IDE node. It outputs the standard layout Clown Prophecy expects. Just make sure every shot after the first has a start time. >H3 Prompt IDE: ethanfel/ComfyUI-H3-Prompt-IDE >Official MiniMax H3 prompting rules (Ref2VA): huggingface.co edit3: i added a switch called "llm_sees" that will remove shots except the shots tagged past a certain time in your detailed description. this should help with weaker llms but, really, if you don't use a strong llm you should just be manually prompting it. please keep feedback coming.

    336 points · 124 comments

Achievements

Awards earned by the repositories roycho87 owns. Select an award to embed its badge.

No awards yet

Repositories earn awards by reaching the top three in a completed trending day or week.

A repository earns an award for finishing first, second or third in a completed trending day or week, ranked by new stars, new forks or pull request authors. Awards follow a repository through renames and transfers and count toward its current owner. Weeks run Monday to Sunday, UTC.