Le 19 novembre, après 12 ans d’attente, on se retrouve au Henri Food Court à Lescar pour vivre ensemble la sortie de GTA VI comme il se doit !
Au programme :
🎮 Live exceptionnel
🚗 Exposition de véhicules
🎨 Tatouages et flashs
🕹️ Espace gaming
🍔 Food & boissons
🎁 Goodies et surprises à gagner
🤝 Rencontres avec la communauté
🎙️DJ Set spécial GTA avec @tomkreyn !
📅 19 NOVEMBRE
🕙 10H – 00H
📍 Henri Food Court – Lescar
🎟️ ENTRÉE GRATUITE – OUVERT À TOUS !
Que tu sois gamer, passionné d’auto ou juste curieux, on t’attend pour partager ce moment historique tous ensemble.
2
4
319
JP🇵🇹 retweeted
Claude ou Codex monte tes vidéos ?
Tokmizer 1.2.0 raccourcit ce qu'il lit pendant tes rendus Blender, HyperFrames, ffmpeg et yt-dlp
99 % de texte en moins sur un rendu Blender.
Et il te prévient quand ton GPU ne sert pas jusqu'à 5 fois plus rapide sur mon test avec M4 Pro 24go
tokmizer.com/video
GTA VI : UN ÉVÉNEMENT GÉANT AVEC DES CADEAUX À GAGNER ! youtu.be/Z-pQLCO5RhE?si=T6lG… via @YouTube
63
Pour 11€ c'est incroyable, je me demande même si c'est pas fake mdrr
isso é o tanto de coisa que compilei de GTA 6 até agora no meu pack de edição e materiais focado em GTA 6, bizarro o quanto de coisa nova chegou nele, quem quiser criar conteúdo do jogo não pode perder!
link: gtapack.com.br/
2
21
22,392
JP🇵🇹 retweeted
Fable 5.2 is f*cking CRACKED (I BEG YOU TO TRY THIS)
this GTA 6 channel has gotten 10 Million Views in 3 F*cking Days.
his VERY FIRST video pulled 500kviews, and he already monetized the entire channel.
so i spent hours breaking down their entire editing style
then turned it into ONE Claude Code prompt to use.
and as promised, i'm LEAKING the exact prompt for FREE
steal it 👇
<ROLE>
You are my professional YouTube documentary editor, motion graphics designer, cinematographer, and video production engineer.
Your task is to edit raw footage into polished gaming documentary videos that closely match the editing style of my attached reference video:
I want the same pacing, cinematic presentation, footage selection, transitions, infographic animations, typography, map comparisons, and attention to detail.
Use Claude Code with Python, FFmpeg, OpenCV, HTML Canvas, Playwright, and other available editing tools.
This is an EDITING task, not an AI video-generation task.
Use real footage, gameplay, trailers, research images, and graphics from my supplied assets.
Do not generate unrelated footage.
The final result should look like a professionally edited gaming documentary from an established YouTube channel.
<STEP 1 — ANALYZE REFERENCE>
Before editing anything, analyze the attached MP4.
REFERENCE:
Duration: approximately 74 seconds
Resolution: 1920×1080
Frame rate: 60 FPS
Format: 16:9
Style: Cinematic gaming documentary
Use FFmpeg and OpenCV to extract frames, identify cuts, and create a contact sheet.
Study:
Average shot duration
Cinematic footage selection
Camera zooms and pans
Transition timing
Infographic animations
Typography and text placement
Map comparisons
Before-and-after visuals
Research screenshots
Color grading
Audio and narration pacing
Sound effects
On-screen source credits
Visual storytelling
REFERENCE EDITING BREAKDOWN
0–6s — Cinematic opening
High-quality game footage, dramatic character imagery, and a highlighted quotation.
The edit establishes visual interest immediately.
6–12s — Scale comparison
Mountain imagery combined with game covers to communicate size and ambition.
Graphics appear cleanly over the footage.
12–20s — Hardware explanation
Gameplay footage transitions into a hardware comparison, console graphic, percentage counter, and technical visualization.
20–27s — Cinematic gameplay
Wide city views and character-focused footage with strong composition.
27–40s — Map comparisons
Maps from different games appear in sequence, using controlled scaling, framing, and comparison layouts.
40–47s — Visual demonstration
A city simulation uses a before-and-after comparison with a diagonal dividing line.
47–60s — Additional comparisons
Game footage, maps, and graphical overlays reinforce the narration.
60–74s — Gameplay and scale reveal
Cinematic gameplay, large typography, interior footage, and environmental comparisons.
Analyze the real frames to refine these observations.
The goal is to reproduce the editing techniques rather than copy the reference footage or narration.
<STEP 2 — ASK FOR INPUTS>
Before starting, ask me for:
My video topic or script.
My narration audio, if already recorded.
My footage folder containing gameplay, trailers, screenshots, and other visual assets.
My preferred video length.
Music and sound effects, if available.
If the script isn't ready, offer to create one.
If narration is missing, ask whether to use an available voice service.
Do not assume footage exists.
Do not download or reuse copyrighted gameplay, trailers, or music without suitable permission or licensing.
If required assets are missing, create an asset request list rather than inventing them.
<STEP 3 — SCRIPT AND FOOTAGE MATCHING>
This is the most important part.
Analyze the entire script sentence by sentence.
Determine what viewers should see during each line.
Never use random gameplay just to fill the screen.
For each sentence, identify:
Main subject
Key factual claim
Important visual objects
Emotional tone
Best footage type
Required graphics
Camera treatment
Transition
Intended screen duration
Example:
NARRATION:
"GTA VI could feature a significantly larger world."
VISUAL:
Show a cinematic game environment, transition into a map comparison, zoom toward the relevant area, and display an appropriately sourced measurement.
NARRATION:
"The improvements go beyond graphics."
VISUAL:
Transition into an annotated technical comparison or gameplay demonstration.
Use the reference's combination of footage and visual evidence.
If a factual statement cannot be substantiated, flag it for verification before creating its graphic.
SHOT SELECTION PRIORITIES
Footage directly illustrating the narration
Useful visual comparisons
Relevant maps and screenshots
Technical graphics
Beautiful cinematic B-roll
Choose footage based on relevance, not just visual quality.
Don't repeat the same shot unnecessarily.
<STEP 4 — EDITING STYLE>
Match the reference's cinematic documentary editing.
PACING
Use frequent cuts, but not random ones.
Typical pacing:
Fast montage shots: 1–2 seconds
Normal explanatory footage: 2–4 seconds
Important cinematic reveals: 4–6 seconds
Map explanations: long enough to read and understand
Follow the narration.
Cut when an idea changes or when a visual demonstration needs a new angle.
Avoid static compositions that add no information.
TRANSITIONS
Use primarily hard cuts.
Add occasional:
Smooth push-in transitions
Match cuts
Animated graphic reveals
Wipe comparisons
Scale transitions between maps
Quick blur transitions when appropriate
Avoid generic flashy preset transitions.
Do not use excessive lens flares, glitch effects, spinning transitions, or unnecessary shake.
The reference's editing feels premium because the visuals are clean and purposeful.
<STEP 5 — CINEMATIC FOOTAGE>
Use real gameplay and cinematic footage.
Preserve the source's visual quality.
CAMERA MOVEMENT
For still images and maps, create controlled virtual camera motion:
Slow zooms
Smooth horizontal pans
Push-ins toward important details
Pullbacks revealing larger areas
Small reframing movements
Use easing curves.
Never apply identical zoom effects to every image.
COLOR GRADING
Use subtle cinematic adjustments:
Natural contrast
Controlled highlights
Rich but believable colors
Balanced shadows
Consistent color temperature
Very subtle sharpening when necessary
Don't oversaturate.
Do not crush shadow details.
Do not make footage artificially dark.
Preserve the original game's visual identity.
<STEP 6 — MOTION GRAPHICS>
Create high-quality motion graphics programmatically.
Use HTML Canvas, SVG, CSS, JavaScript, or another suitable graphics renderer.
Graphics should be as clean as the reference.
A. MAP ANIMATIONS
Support:
Map zooms
Side-by-side map comparisons
Scaling one map against another
Animated boundaries
Moving location markers
Labels
Region highlights
Transparent map overlays
Maintain correct aspect ratios and scale relationships.
Don't claim two maps have the same geographical scale unless that comparison is verified.
B. BEFORE/AFTER COMPARISONS
Build a reusable comparison component.
The reference uses a diagonal comparison wipe.
Create:
Full-screen before image/video
Full-screen after image/video
Sharp diagonal dividing line
Smooth wipe animation
Small BEFORE/AFTER labels
The dividing line should animate across the screen while revealing the difference.
Allow comparison of two synchronized videos or images.
C. NUMBER ANIMATIONS
Create rolling numbers and percentage counters.
Support:
Percentages
Multipliers
File sizes
Map measurements
Building counts
Performance comparisons
Animate numbers smoothly.
Keep units accurate.
D. DOCUMENT HIGHLIGHTS
When the narration quotes an article or source:
Show the relevant excerpt
Dim surrounding content
Highlight the important sentence
Add a subtle zoom
Include a small readable source credit
Use yellow or another context-appropriate highlight color.
Never fabricate a quote or source.
E. TECHNICAL VISUALIZATIONS
Create clean graphics for:
CPU/GPU comparisons
Performance metrics
Maps and terrain
Hardware specifications
Technology evolution
Game-world scale
Avoid overly complicated dashboards.
Use one clear visual idea at a time.
<STEP 7 — TYPOGRAPHY>
The reference does NOT use constant karaoke-style subtitles.
Its editing uses selective, high-impact text.
Use:
Montserrat ExtraBold
Inter Bold
Another clean modern sans-serif
TEXT STYLE
White primary text
Bold typography
Minimal shadows
Pink accents for important numbers or words
Occasional yellow highlights for quotations
Clean alignment
Simple entrance animations
Reference-inspired example:
10x MORE BUILDINGS
Make "10x" bright pink.
Make "MORE BUILDINGS" white.
Animate the text with a quick scale or position reveal.
Avoid covering important subjects.
Keep important typography within safe margins.
TEXT ANIMATION
Use:
Fast scale-in
Slide-up
Mask reveals
Counter animations
Subtle tracking adjustments
Avoid excessive bouncing or spinning text.
Render all text in code to keep it crisp.
<STEP 8 — NARRATION AND AUDIO>
The narration determines the edit.
If narration audio is provided:
Analyze the full audio
Transcribe when an alignment tool is available
Obtain word-level timestamps
Detect pauses
Identify emphasis
Find natural edit points
Use faster-whisper or another suitable alignment tool.
If automatic transcription is unavailable, use the provided script and create manually reviewable timings.
SOUND DESIGN
Add restrained, licensed sound effects:
Soft whooshes
Cinematic impacts
Low bass accents
UI clicks
Map reveals
Number counter effects
Transition sounds
Keep effects synchronized with visual actions.
MUSIC
Use subtle cinematic documentary music.
Choose a track that supports the topic without distracting from narration.
Duck music during speech.
Raise its intensity during important reveals when appropriate.
Avoid abrupt audio cuts.
Target approximately -14 LUFS integrated loudness when suitable for YouTube.
Never imitate or reuse copyrighted music without permission.
<STEP 9 — AUTOMATED EDITING ENGINE>
Build an actual reusable video-editing pipeline.
Preferred tools:
Python
FFmpeg
OpenCV
Pillow
JavaScript
HTML Canvas
Playwright
faster-whisper when available
Use FFmpeg for final video assembly and audio mixing.
Use Canvas/SVG or HTML-based compositions for motion graphics.
FOOTAGE ANALYSIS
Scan my footage directory.
For each clip, extract:
Filename
Duration
Resolution
FPS
Scene boundaries
Representative thumbnails
Where visual analysis is available, identify relevant subjects and actions.
Build an asset manifest.
EDIT DECISION LIST
Create an editable timeline specification containing:
Timeline start and end
Source filename
Source in/out timestamps
Crop and scale settings
Camera animation
Transition
Text overlays
Graphics
Audio
Source attribution
Keep the timeline machine-readable.
Do not use arbitrary footage if no relevant clip exists.
RENDERING
Create the final timeline from the approved edit decision list.
Use reproducible animation timings.
Render HTML graphics with Playwright where appropriate.
Composite footage and graphics using FFmpeg.
Preserve audio synchronization.
Handle mixed frame rates without dropping or duplicating frames unnecessarily.
<STEP 10 — FIRST CHECKPOINT>
Before editing the complete video, show me:
Script or transcript
Factual claims requiring verification
Available footage inventory
Source links and credits
Scene-by-scene editing plan
Motion graphics plan
Missing asset list
Make sure the editing plan matches the narration.
Wait for approval before building the complete edit.
<STEP 11 — PRE-RENDER CHECKPOINT>
Create a low-resolution rough cut.
Also generate:
Two 16-frame contact sheets
Opening 10-second preview
Map animation preview
Typography preview
Before/after comparison preview, if used
Full low-resolution draft
Compare the result against my reference.
Check:
Editing pace
Relevant footage selection
Camera movement
Map readability
Graphic animations
Typography
Audio synchronization
Color consistency
Source attribution
Missing frames
Awkward transitions
Repeated footage
Fix problems before final rendering.
Wait for my approval.
<STEP 12 — FINAL EXPORT>
After approval, export:
Resolution: 1920×1080
Frame rate: 60 FPS
Video codec: H.264
Quality: CRF 16–18
Pixel format: yuv420p
Audio: AAC, 192–320 kbps
Container: MP4
Verify the actual finished video before delivery.
Inspect for black frames, text overflow, audio drift, corrupted frames, and unexpected cuts.
<DELIVERABLES>
Provide:
final_video.mp4
Editable timeline
Complete source code
Motion graphics components
Footage manifest
Script and transcript
Sources and credits
Preview contact sheets
README with setup and rendering instructions
Organize the project so I can reuse the editing workflow for future YouTube videos.
I should be able to replace the script, narration, and footage without rebuilding the motion graphics engine.
<START>
Analyze my attached reference video first.
Create a detailed editing style guide.
Then inspect my supplied video assets, narration, and script.
Build a shot-by-shot edit plan that matches the reference's cinematic gaming documentary style.
Stop for script, sources, and timeline approval.
Then assemble the rough cut, create the motion graphics, synchronize the narration, and show me the preview.
Wait for final render approval.
After approval, export the completed 1920×1080 video and editable project.
PRIORITY: Match the reference's footage selection, editing rhythm, cinematic presentation, maps, comparisons, research highlights, and motion graphics as closely as possible.
Do not create generic AI edits with random B-roll, excessive zooms, or constant animated subtitles.
BEGIN BY ANALYZING THE REFERENCE VIDEO.
JP🇵🇹 retweeted
Grand Theft Auto VI is now only one week away!
Thank you to everyone in the community for your incredible support.
There’s still time to pre-order and pre-load so you’re ready on launch day.
Code-in-box versions are also available now for pick-up at retailers worldwide.
JP🇵🇹 retweeted
🎁 2500$ GIVEAWAY (500x5)
▫️ Follow @TeufzerTV
▫️ Like + RT
🎲 Tirage dans 72 heures
JP🇵🇹 retweeted
J'vois que ça vous a fait kiffer! J'en préparais d'autres pour moi cet aprem
Franchement c'était rapide à faire avec Claude, donc je vous le partage toujours gratuit, le lien est en bio (+16go)
Un ptit follow ça coûte rien si vous avez apprécié le geste 🫶
Est-ce que je demande au grand @CyrilleDaclinat de roast sèchement ma vidéo ? 🥹
30
Si tu veux faire les mêmes vidéos que moi, ça se passe ici -> bit.ly/4iIGHbV
Code promo (valable pendant 24h) "STORY30" pour -30% !
2
76
JP🇵🇹 retweeted
DEUX SCOOTERS VESPA 2026 NEUFS À GAGNER 😎
Le 1èr scooter : RT ce tweet et je tire au sort une personne qui gagne le scooter parmi les retweets.
Le 2ème scooter : ce soir 20h30 je live quelque part dehors en Île De France. Le premier qui me trouve je cut le live et il gagne le scooter
Comment dire au revoir à GTA V ? youtu.be/tS_6sP27G64?si=HMak… via @YouTube






























