Sensitive content

This media may contain sensitive content.

Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

Commision Project Video based on Andava (COMMS CLOSED) Arts Pelo Model by Memz Male model by Me Sound pack by OpenNSFW | PointyAux 🔞 NSFW Sound Designer 星野めりか@声のお仕事募集中 千夜(Chiyoru)🐈️🌃 You can download this video here:

FaustTerm's profile picture

FausTTerM (Commission Open)

31,513 subscribers

161,365 görüntüleme • 1 yıl önce •via X (Twitter)

NSFW
LIVE

Anya Rossi• Live Now

Private livecam show

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

Time for a new animation! is working on her beach body, but it all goes to her butt... Model by @dreamrider3d, VO by 千夜(Chiyoru)🐈️🌃 from the OpenNSFW, Sound design & Animation by me. #expansion #rule34 #dva #overwatch2 #sizetwitter
0:22

Sensitive content

Time for a new animation! is working on her beach body, but it all goes to her butt... Model by @dreamrider3d, VO by 千夜(Chiyoru)🐈️🌃 from the OpenNSFW, Sound design & Animation by me. #expansion #rule34 #dva #overwatch2 #sizetwitter

Size King

115,813 görüntüleme • 2 yıl önce

完全痴〇の少女Hのボイスは『暁鞠子様暁鞠子🍒フリー声優』にご担当頂きました！ イメージ通りの、とっても素敵なボイスをありがとうございます😭 ストーリーはもちろん、痴〇アクションでも ・淫〇度低 ・淫〇度高 ・口ふさぎ この3種類の声がアクションに使用されております！ 動画では分かりづらいかもしれませんが、凄く高音質です！ 全編バイノーラルのため、囁くような良いお声を楽しめます🤤(楽しんでます) また、販売日ですがDLsiteにて11月28日(金)に販売開始したいと考えてます！ 他言語についても検討中です！(間に合えばいいなぁ…) 予告やCi-enの開始は9月中を予定しております！ より詳しい記事を連投していきます！ English The voice of Girl H from “Kanzen Chikan” is performed by the amazing "Akatsuki Mariko"! Thank you so much for delivering such a wonderful voice, exactly as I had imagined 😭 Not only in the story, but also during the touch actions, you’ll hear three variations of her voice: ・innocent ・lewd ・Mouth covered It might be hard to tell from the video, but the quality is really high! Since it’s fully binaural, you can enjoy her whisper-like, intimate voice 🤤 (I’m already enjoying it myself!) As for the release date, I’m planning to launch on DLsite on Friday, November 28th! Other languages are also being considered (hopefully I can make it in time…). The teaser and Ci-en page are planned for September! I’ll be posting a series of more detailed articles soon!
3:42

Sensitive content

完全痴〇の少女Hのボイスは『暁鞠子様暁鞠子🍒フリー声優』にご担当頂きました！ イメージ通りの、とっても素敵なボイスをありがとうございます😭 ストーリーはもちろん、痴〇アクションでも ・淫〇度低 ・淫〇度高 ・口ふさぎ この3種類の声がアクションに使用されております！ 動画では分かりづらいかもしれませんが、凄く高音質です！ 全編バイノーラルのため、囁くような良いお声を楽しめます🤤(楽しんでます) また、販売日ですがDLsiteにて11月28日(金)に販売開始したいと考えてます！ 他言語についても検討中です！(間に合えばいいなぁ…) 予告やCi-enの開始は9月中を予定しております！ より詳しい記事を連投していきます！ English The voice of Girl H from “Kanzen Chikan” is performed by the amazing "Akatsuki Mariko"! Thank you so much for delivering such a wonderful voice, exactly as I had imagined 😭 Not only in the story, but also during the touch actions, you’ll hear three variations of her voice: ・innocent ・lewd ・Mouth covered It might be hard to tell from the video, but the quality is really high! Since it’s fully binaural, you can enjoy her whisper-like, intimate voice 🤤 (I’m already enjoying it myself!) As for the release date, I’m planning to launch on DLsite on Friday, November 28th! Other languages are also being considered (hopefully I can make it in time…). The teaser and Ci-en page are planned for September! I’ll be posting a series of more detailed articles soon!

兎もに角🔞完全痴〇2制作中！

96,258 görüntüleme • 10 ay önce

SNS限定 オリジナルサンプル動画 後編！ 予約はリンクから🔗！ 山中姉妹 1st DVD&Blu-ray&写真集 発売日：2/14 イベント:2/21 お時間の詳細はお待ちください。 ⭐️DVD「Charisma」 4,950円（税込） ⭐️Blu-ray「Charisma」 6,600円（税込） 映像時間：本編→91分、メイキング27分、トータル118分 ■特典 オリジナル生写真（全3種の中から1枚） 抽選でオリジナルサイン入りチェキが当たります ※1/31までに予約注文頂いた方には 生写真が直筆サイン入り ⭐️写真集「Charisma」 4,600円（税込） サイズ：210㎜×297㎜ 全52ページ（表紙4P、本文48P） ■特典 オリジナルカレンダー（仕様は注文数によって決定） ※1/31予約注文頂いた方には写真集に直筆サイン入り 【To all Yamanaka Sisters fans around the world】 【We've kept you waiting!!!】 【Of course! Worldwide shipping available!】 Reserve here! ↓ Yamanaka Sisters 1st DVD & Blu-ray & Photo Book 【Charisma】 Release Date February 14 Event February 21 Please wait for details on the event schedule. ⭐️ DVD “Charisma" 4,950 yen (tax included) ⭐️ Blu-ray “Charisma” 6,600 yen (tax included) Video Duration: Main feature → 91 minutes, Making-of 27 minutes, Total 118 minutes ■ Benefits Original photo print (1 random from 3 types) Chance to win an original signed cheki through lottery ※ Orders reserved by January 31 will receive a hand-signed photo print ⭐️ Photo Book “Charisma” 4,600 yen (tax included) Size: 210mm × 297mm Total 52 pages (Cover 4P, Main content 48P) ■ Benefits Original calendar (specifications to be determined based on order volume) ※ Orders reserved by January 31 will receive a hand-signed photo book
1:31

SNS限定 オリジナルサンプル動画 後編！ 予約はリンクから🔗！ 山中姉妹 1st DVD&Blu-ray&写真集 発売日：2/14 イベント:2/21 お時間の詳細はお待ちください。 ⭐️DVD「Charisma」 4,950円（税込） ⭐️Blu-ray「Charisma」 6,600円（税込） 映像時間：本編→91分、メイキング27分、トータル118分 ■特典 オリジナル生写真（全3種の中から1枚） 抽選でオリジナルサイン入りチェキが当たります ※1/31までに予約注文頂いた方には 生写真が直筆サイン入り ⭐️写真集「Charisma」 4,600円（税込） サイズ：210㎜×297㎜ 全52ページ（表紙4P、本文48P） ■特典 オリジナルカレンダー（仕様は注文数によって決定） ※1/31予約注文頂いた方には写真集に直筆サイン入り 【To all Yamanaka Sisters fans around the world】 【We've kept you waiting!!!】 【Of course! Worldwide shipping available!】 Reserve here! ↓ Yamanaka Sisters 1st DVD & Blu-ray & Photo Book 【Charisma】 Release Date February 14 Event February 21 Please wait for details on the event schedule. ⭐️ DVD “Charisma" 4,950 yen (tax included) ⭐️ Blu-ray “Charisma” 6,600 yen (tax included) Video Duration: Main feature → 91 minutes, Making-of 27 minutes, Total 118 minutes ■ Benefits Original photo print (1 random from 3 types) Chance to win an original signed cheki through lottery ※ Orders reserved by January 31 will receive a hand-signed photo print ⭐️ Photo Book “Charisma” 4,600 yen (tax included) Size: 210mm × 297mm Total 52 pages (Cover 4P, Main content 48P) ■ Benefits Original calendar (specifications to be determined based on order volume) ※ Orders reserved by January 31 will receive a hand-signed photo book

山中知恵🐯⚾️

16,193 görüntüleme • 6 ay önce

【掲載情報。英語論文！】 現在ロンドンのバービカンセンターで開催中の『Feel the Sound』展カタログに、「Japanese Queerness in Vocaloid Music: How Vocaloid Music and Hyperpop save Their (Our) Lives」を寄稿しました！ また、アボガド6さんが同展に描き下ろした作品も掲載されています！ 実は、あゆぱて初の英語論文です。アンチ・セクシュアル、世界へ。英語圏の方にお届けする貴重な機会なので、好きなものばっかり詰め込みましたというのは添付の誌面の通り。#wowaka #椎名もた #はるまきごはん #SOPHIE 『Feel the Sound』展で発表した国際共同作品、TRANS VOICES, ILĀ & MONOM, with contribution from Patty Ayukawa「UN/BOUND」にも、#東大ぱてゼミ #藝大ぱてゼミ メイツに加え、アボガド6さんにも参加していただきましたが（カロガドの調声）、実はカタログのほうにもお誘いしていたのでした。同展のテーマを昇華したすてきな作品です。 展覧会は8月31日まで！ カタログは現地あるいは下記リンクから購入できます！ I’ve contributed a paper, Japanese Queerness in Vocaloid Music: How Vocaloid Music and Hyperpop Save Their (Our) Lives, to the catalogue for Feel the Sound, now on at the Barbican Centre in London! The catalogue also features an original piece drawn for the show by Avogado6. This is actually my first-ever academic essay in English. Anti-sexual, out into the world. Since it’s such a rare chance to speak directly to the world, I packed it full of things I love—as you can see in the page spread attached. #wowaka #siinamota #HarumakiGohan #SOPHIE Our international collaboration UN/BOUND—by TRANS VOICES, ILĀ & MONOM, with contribution from Patty Ayukawa—was also presented at Feel the Sound. Alongside the #UTokyoPattySeminar and #TokyoGeidaiPattySeminar crew, Avogado6 joined in (providing carogado’s vocal tuning). I’d also invited them to contribute to the catalogue, where they created a beautiful piece that captures and distills the exhibition’s theme. The show runs until 31 August! You can grab the catalogue onsite or via the link.
0:24

【掲載情報。英語論文！】 現在ロンドンのバービカンセンターで開催中の『Feel the Sound』展カタログに、「Japanese Queerness in Vocaloid Music: How Vocaloid Music and Hyperpop save Their (Our) Lives」を寄稿しました！ また、アボガド6さんが同展に描き下ろした作品も掲載されています！ 実は、あゆぱて初の英語論文です。アンチ・セクシュアル、世界へ。英語圏の方にお届けする貴重な機会なので、好きなものばっかり詰め込みましたというのは添付の誌面の通り。#wowaka #椎名もた #はるまきごはん #SOPHIE 『Feel the Sound』展で発表した国際共同作品、TRANS VOICES, ILĀ & MONOM, with contribution from Patty Ayukawa「UN/BOUND」にも、#東大ぱてゼミ #藝大ぱてゼミ メイツに加え、アボガド6さんにも参加していただきましたが（カロガドの調声）、実はカタログのほうにもお誘いしていたのでした。同展のテーマを昇華したすてきな作品です。 展覧会は8月31日まで！ カタログは現地あるいは下記リンクから購入できます！ I’ve contributed a paper, Japanese Queerness in Vocaloid Music: How Vocaloid Music and Hyperpop Save Their (Our) Lives, to the catalogue for Feel the Sound, now on at the Barbican Centre in London! The catalogue also features an original piece drawn for the show by Avogado6. This is actually my first-ever academic essay in English. Anti-sexual, out into the world. Since it’s such a rare chance to speak directly to the world, I packed it full of things I love—as you can see in the page spread attached. #wowaka #siinamota #HarumakiGohan #SOPHIE Our international collaboration UN/BOUND—by TRANS VOICES, ILĀ & MONOM, with contribution from Patty Ayukawa—was also presented at Feel the Sound. Alongside the #UTokyoPattySeminar and #TokyoGeidaiPattySeminar crew, Avogado6 joined in (providing carogado’s vocal tuning). I’d also invited them to contribute to the catalogue, where they created a beautiful piece that captures and distills the exhibition’s theme. The show runs until 31 August! You can grab the catalogue onsite or via the link.

鮎川ぱて Ayukawa, Patty【東大ボカロ論（6刷！）】

369,042 görüntüleme • 11 ay önce

I think I can finally report some success training a quite accurate IDM capable of recovering keystrokes from Minecraft gameplay, even in quite PvP-heavy situations. At this point the model does not only know what keys are pressed to the extent reasonably discernible, it also knows how fast it is moving in 3D space at all times, even when knockback is mixing with the self-move impulse. Now, recovering keystrokes from normal external capture footage is just about impossible. E.g. W/A/S/D does exactly nothing during partial tick frames and jumping mid-air is also equally useless, so asking the model to recover key down states is inherently unreasoanble. Mouse deltas are also completely arbitrary units, as game mouse sensitivity introduces an arbitrary scale factor into the equation. The only good option is to think carefully about your model-environment contract, and only record "logical actions", not raw keystrokes. So here's a few unfortunate lessons I had to learn in roughly this order. - Choose good units. (bad: mouse deltas, good: delta radians [yes, you will need game-internal state]) - Capture from inside the main game loop and read the game fbo to get consistent frame-action pairing. Doing post-mortem pairing is hopeless. - Carefully define when you think keystrokes actually have an effect. (jump only works on ground, when flying or in water etc.) More subtle: The key may already be down, but no tick has happened yet to actually use the value. Hence: ignore Seperate gamestate into "fast and slow-moving" components. E.g. movement is likely tick based, camera rotation is very likely updated every frame in essentially every game ever. - Think about your frame-action correspondance contract (How old is the frame in relation to the inputs you capture? Will double or tripple buffering affect you?) Think about the game loop timeline, where you are sampling, how old the data you are reading is, and where the ticks are happening around you. Language models used to simply not have a model-environment contract, but even now with the model "living" in a designated harness, the contract still boils down to formatting, and tool implementation intrinsics. While also important, it is still quite a bit more obvious because the violations are in some way shape or form reflected as text you can actually see. - ffmpeg dropping frames cummulatively screws the model the further you get into the sequence because your targets are now shifted. If you can't encode the video in real-time, too bad. - Sodium has a frames in flight system different from vanilla Minecraft, which will also offset your targets from your frames. (there goes that data...) - Models are succeptible to latency. If there is too big of a delay between action and on-screen reflection, your performance degrades. At this point I realize ~100hours of gameplay is essentially no longer usable as a dataset. You can train on this data, but all you'll get is a mushy mess. However, some good news: - Making the model predict physics gamestate scalars helps the model generalize. For instantaneous events like jump, it's unreasonable to ask the model emit a short burst of jump=true at exactly the right time, however if you also predict your current y-velocity, the model has supervision signal for the "latent" from which that onground jump becomes apparent. Recovering x/z motion is also somewhat easier than unmixing it into plausible keystrokes for inertia-heavy player controller logic. - Regressing physics gamestate scalars also seems to make your dataset "bigger". While pure keystroke classification will overfit quickly, predicting exact physics gamestate scalars forces the model to generalize more and you can tolerate far more epochs before validation loss starts to stall out. This is the only reason why it was bearable to dump 100h+ of dataset hours and replace it with ~3 hours of gameplay after the 4th revision of the file format (yeah...) and somehow still have better performance. Now, you might be asking, "isn't this brittle?" and the answer is yesn't. Frame-action correspondance matters for training, but not so much during inference. So as long as you are sampling in roughly the same interval as your training data, you aren't violating any hard contract per-se. Somewhere around the frames ticks are happening, and during training you capture various tick-capture offset relations per random chance, so nothing is too obviously wrong here. HOWEVER, you will get screwed by gui scale, shaders, resource packs, "shit that recording is 1920x1040 because somebody doesn't know fullscreen exists" and other unfortunate edge cases of reality. But I suppose this is the role of dataset size. If all those "contract violations" that a youtube video has compared to the training data are addressed, I think this is a way to turn Youtube into a labeled dataset. I could never shake the feeling that VPT is a sound idea in practice, while never having been properly executed, and I think one reason why it hasn't is because that label boostrapping part is just a pain in the butt to get right. Now, what the player is doing is of course not the only label you can extract from video, but it has to be one of the targets predicted during pretraining to "align" the pretraining objective. Some notes on the video here, the colored dots on the analog visualizer are the ground truth, while the gray dot is the model prediction. Green means correct prediction, red means incorrect prediction at that frame. Model P(key) reports how wrong the prediction is from green (0.0) to red (1.0). You will also notice that during periods of rapid slow down, left and right actions become close to irrecoverable, because there is just that little motion. And some jump actions are not predicted correctly because I got the detection condition for jump events wrong... (duh) LMB/RMB for other than sustained events (like item-consume and block break) also seem to be hopelessly irrecoverable for now. Swing was supposed to do the same thing as motion y did for jump, but its too well behaved as an increasing counter. Maybe partial-tick interpolated values work better (v5 file format then... ugh..)
2:27

I think I can finally report some success training a quite accurate IDM capable of recovering keystrokes from Minecraft gameplay, even in quite PvP-heavy situations. At this point the model does not only know what keys are pressed to the extent reasonably discernible, it also knows how fast it is moving in 3D space at all times, even when knockback is mixing with the self-move impulse. Now, recovering keystrokes from normal external capture footage is just about impossible. E.g. W/A/S/D does exactly nothing during partial tick frames and jumping mid-air is also equally useless, so asking the model to recover key down states is inherently unreasoanble. Mouse deltas are also completely arbitrary units, as game mouse sensitivity introduces an arbitrary scale factor into the equation. The only good option is to think carefully about your model-environment contract, and only record "logical actions", not raw keystrokes. So here's a few unfortunate lessons I had to learn in roughly this order. - Choose good units. (bad: mouse deltas, good: delta radians [yes, you will need game-internal state]) - Capture from inside the main game loop and read the game fbo to get consistent frame-action pairing. Doing post-mortem pairing is hopeless. - Carefully define when you think keystrokes actually have an effect. (jump only works on ground, when flying or in water etc.) More subtle: The key may already be down, but no tick has happened yet to actually use the value. Hence: ignore Seperate gamestate into "fast and slow-moving" components. E.g. movement is likely tick based, camera rotation is very likely updated every frame in essentially every game ever. - Think about your frame-action correspondance contract (How old is the frame in relation to the inputs you capture? Will double or tripple buffering affect you?) Think about the game loop timeline, where you are sampling, how old the data you are reading is, and where the ticks are happening around you. Language models used to simply not have a model-environment contract, but even now with the model "living" in a designated harness, the contract still boils down to formatting, and tool implementation intrinsics. While also important, it is still quite a bit more obvious because the violations are in some way shape or form reflected as text you can actually see. - ffmpeg dropping frames cummulatively screws the model the further you get into the sequence because your targets are now shifted. If you can't encode the video in real-time, too bad. - Sodium has a frames in flight system different from vanilla Minecraft, which will also offset your targets from your frames. (there goes that data...) - Models are succeptible to latency. If there is too big of a delay between action and on-screen reflection, your performance degrades. At this point I realize ~100hours of gameplay is essentially no longer usable as a dataset. You can train on this data, but all you'll get is a mushy mess. However, some good news: - Making the model predict physics gamestate scalars helps the model generalize. For instantaneous events like jump, it's unreasonable to ask the model emit a short burst of jump=true at exactly the right time, however if you also predict your current y-velocity, the model has supervision signal for the "latent" from which that onground jump becomes apparent. Recovering x/z motion is also somewhat easier than unmixing it into plausible keystrokes for inertia-heavy player controller logic. - Regressing physics gamestate scalars also seems to make your dataset "bigger". While pure keystroke classification will overfit quickly, predicting exact physics gamestate scalars forces the model to generalize more and you can tolerate far more epochs before validation loss starts to stall out. This is the only reason why it was bearable to dump 100h+ of dataset hours and replace it with ~3 hours of gameplay after the 4th revision of the file format (yeah...) and somehow still have better performance. Now, you might be asking, "isn't this brittle?" and the answer is yesn't. Frame-action correspondance matters for training, but not so much during inference. So as long as you are sampling in roughly the same interval as your training data, you aren't violating any hard contract per-se. Somewhere around the frames ticks are happening, and during training you capture various tick-capture offset relations per random chance, so nothing is too obviously wrong here. HOWEVER, you will get screwed by gui scale, shaders, resource packs, "shit that recording is 1920x1040 because somebody doesn't know fullscreen exists" and other unfortunate edge cases of reality. But I suppose this is the role of dataset size. If all those "contract violations" that a youtube video has compared to the training data are addressed, I think this is a way to turn Youtube into a labeled dataset. I could never shake the feeling that VPT is a sound idea in practice, while never having been properly executed, and I think one reason why it hasn't is because that label boostrapping part is just a pain in the butt to get right. Now, what the player is doing is of course not the only label you can extract from video, but it has to be one of the targets predicted during pretraining to "align" the pretraining objective. Some notes on the video here, the colored dots on the analog visualizer are the ground truth, while the gray dot is the model prediction. Green means correct prediction, red means incorrect prediction at that frame. Model P(key) reports how wrong the prediction is from green (0.0) to red (1.0). You will also notice that during periods of rapid slow down, left and right actions become close to irrecoverable, because there is just that little motion. And some jump actions are not predicted correctly because I got the detection condition for jump events wrong... (duh) LMB/RMB for other than sustained events (like item-consume and block break) also seem to be hopelessly irrecoverable for now. Swing was supposed to do the same thing as motion y did for jump, but its too well behaved as an increasing counter. Maybe partial-tick interpolated values work better (v5 file format then... ugh..)

mike64_t

18,762 görüntüleme • 3 ay önce

is our AI project to make computing feel more human L A N D E R Here are the 4 best demo videos of the magic of DATA in action. DATA is a personalized assistant who knows and remembers every conversation you have with it accross your iPhone, Mac, iPad, Watch, Texts, Emails, and HomePods. You can talk to DATA right in your AirPods or text it just like a person. DATA can read, write, understand, speak any language, and translate between them. It can help with real work and home life tasks like research, writing, scheduling, reminders, and triage. And it's easily customizable so you can have DATA automatically do whatever you want whenever you want with just a few taps and natural language instructions - no code required. DATA can do just about anything you can do on your phone on your behalf automatically including very advanced things Siri can't, like summarizing, analyzing, and drafting replies or writing documents. It can read web pages, texts or emails you show it, or PDFs of any kind. It can do other real world tasks that require complex analysis and common sense too, like: - figure out where the nearest beach is (even when you're in Colorado) and instantly fetch the current surf report up to the current minute. - summarize and drafting replies to entire email chains - plan out entire work projects or multi-day vacations on your calendar - sketch out ideas for you in picture form or drafting Notion pages with charts and graphs. DATA can also use its own judgement to determine when to run an action or not, even if you've scheduled it, allowing you to make VERY complex automations that require many different inputs to make a decision, like for example: - only opening the blinds on your lunch break if it's sunny out and you're working from home. DATA works natively and easily with Apple HomeKit & other shortcuts. DATA can also take initiative and check in with you throughout the day by voice or text and proactively send messages to you and others on your behalf based on your personal and professional goals, current tasks, and calendar. DATA can integrate with many apps on your phone, and is compatible with multiple large AI language models. I've gotten to make a few demo videos that I think really capture how powerful DATA can be for every day life. Here they are all in one tweet. Make sure your sound is on as you watch them. 1. This is the first demo video I ever made from April 19th, 2023. It walks through all the ways you can interact with and use the DATA shortcuts. Everything from saying "Hey Siri" to tapping on custom apps on your home-screen. 2. The second demo video was made May 5 and is an example use case I made of how commands work - commands allow DATA to actually run actions on your phone like taking pictures and sending messages. This demo shows me taking a picture of an email template, and data drafting an email based on that template. It's gotten much better at realizing when it has just run a command and incorporating that information naturally into the conversation now, especially on GPT-4. 3. This third Commands video, May 12 is a walkthrough of ALL the phone functions that commands allow DATA to do: sending texts and emails, making pictures, seeing pictures, reading things, and scheduling events. Since this video we've added auto-replies to texts and emails, summarizing documents, writing documents, health app data retrieval, web surfing, scheduling alarms, making playlists, and more. 4. This last demo I made today, June 15, shows everything DATA does working in concert to generate a crazy detailed morning briefing with background music - including making a unique playlist and giving a detailed analysis of current events complete with Ski & Surf conditions near me other live information from the internet. So now that you've seen everything DATA can do, what's the coolest feature? What features should we add? What would you use DATA for first?
12:54

is our AI project to make computing feel more human L A N D E R Here are the 4 best demo videos of the magic of DATA in action. DATA is a personalized assistant who knows and remembers every conversation you have with it accross your iPhone, Mac, iPad, Watch, Texts, Emails, and HomePods. You can talk to DATA right in your AirPods or text it just like a person. DATA can read, write, understand, speak any language, and translate between them. It can help with real work and home life tasks like research, writing, scheduling, reminders, and triage. And it's easily customizable so you can have DATA automatically do whatever you want whenever you want with just a few taps and natural language instructions - no code required. DATA can do just about anything you can do on your phone on your behalf automatically including very advanced things Siri can't, like summarizing, analyzing, and drafting replies or writing documents. It can read web pages, texts or emails you show it, or PDFs of any kind. It can do other real world tasks that require complex analysis and common sense too, like: - figure out where the nearest beach is (even when you're in Colorado) and instantly fetch the current surf report up to the current minute. - summarize and drafting replies to entire email chains - plan out entire work projects or multi-day vacations on your calendar - sketch out ideas for you in picture form or drafting Notion pages with charts and graphs. DATA can also use its own judgement to determine when to run an action or not, even if you've scheduled it, allowing you to make VERY complex automations that require many different inputs to make a decision, like for example: - only opening the blinds on your lunch break if it's sunny out and you're working from home. DATA works natively and easily with Apple HomeKit & other shortcuts. DATA can also take initiative and check in with you throughout the day by voice or text and proactively send messages to you and others on your behalf based on your personal and professional goals, current tasks, and calendar. DATA can integrate with many apps on your phone, and is compatible with multiple large AI language models. I've gotten to make a few demo videos that I think really capture how powerful DATA can be for every day life. Here they are all in one tweet. Make sure your sound is on as you watch them. 1. This is the first demo video I ever made from April 19th, 2023. It walks through all the ways you can interact with and use the DATA shortcuts. Everything from saying "Hey Siri" to tapping on custom apps on your home-screen. 2. The second demo video was made May 5 and is an example use case I made of how commands work - commands allow DATA to actually run actions on your phone like taking pictures and sending messages. This demo shows me taking a picture of an email template, and data drafting an email based on that template. It's gotten much better at realizing when it has just run a command and incorporating that information naturally into the conversation now, especially on GPT-4. 3. This third Commands video, May 12 is a walkthrough of ALL the phone functions that commands allow DATA to do: sending texts and emails, making pictures, seeing pictures, reading things, and scheduling events. Since this video we've added auto-replies to texts and emails, summarizing documents, writing documents, health app data retrieval, web surfing, scheduling alarms, making playlists, and more. 4. This last demo I made today, June 15, shows everything DATA does working in concert to generate a crazy detailed morning briefing with background music - including making a unique playlist and giving a detailed analysis of current events complete with Ski & Surf conditions near me other live information from the internet. So now that you've seen everything DATA can do, what's the coolest feature? What features should we add? What would you use DATA for first?

steve

640,114 görüntüleme • 3 yıl önce

Input: Jane Jacobs quotes and YouTube interview; handwritten outline; education standards doc. Output: high-quality, standards-aligned urban planning lesson plan. Plus audio overview to promote the class. 10 minutes to create, all thanks to NotebookLM and Gemini. This video is a new demo of NotebookLM that I shared earlier this month at the AI + Education Symposium with MeshEd, XQ, and Betaworks. This is an educational use-case, but the general structure of what I’m doing in the demo—take a curated collection of sources and quickly transform them into a detailed document that obeys strict guidelines—is generally applicable to many fields. Note how I am not just using the sources as ground truth for the project, or as the content for the lesson plan. The Jacobs quotes and interview are the content, but my handwritten notes provide the structure, and the framework source provides the values or guidelines for the finished project. With some simple prompting, NotebookLM and Gemini can draw on information from the sources using those different modes simultaneously: content, format, values. (I even forgot to explicitly tell the model to use the structure outlined in my notes, but it figured that out anyway.) This is remarkably sophisticated knowledge work. Building a draft lesson plan like this would normally take hours if not days. But crucially I’m in control of the document that is being generated here — it’s based on the information that I have curated, and on the instructions I’ve given NotebookLM for adapting that information into the lesson plan I want to create. Co-intelligence, as @ethanmollick would call it. For more info on the great organizations that helped me put this demo together--orgs that are shaping the future of learning and increasing access to innovative approaches to curriculum design--visit and I’ve pasted the full text of the lesson plan below. As you can see in the video, the original version also included citations to the source material so with one click I could verify that NotebookLM was faithful to the original documents I uploaded. High-Level Lesson Plan: Urban Planning and Jane Jacobs This lesson plan outlines a project-based learning course on urban planning, designed for high school seniors. It centers on the influential ideas of Jane Jacobs and aligns with the HQPBL standards. Session 1: Introduction to Cities and Jane Jacobs • Begin by exploring the question: "What kind of problem is a city?" • Introduce Jane Jacobs' key ideas about urbanism, focusing on: • The importance of diversity in uses, buildings, and populations for vibrant city life. • The role of sidewalks and "eyes on the street" in ensuring safety and fostering a sense of community. • The value of old buildings in supporting diverse economic activity and fostering innovation. • The dangers of "single-use" zoning and the importance of mixed-use neighborhoods. • The limitations of top-down planning and the need for bottom-up, community-driven approaches. Use examples from Jacobs' book, "The Death and Life of Great American Cities," and excerpts from her interviews to illustrate these concepts. Encourage students to think critically about the challenges and opportunities presented by cities. Alignment with HQPBL: This session establishes the intellectual challenge, as required by the HQPBL framework, by prompting students to consider the complexities of cities. Introducing Jane Jacobs' ideas provides students with a theoretical framework for their projects. Session 2: Neighborhood Exploration Project Introduction: Students choose a local neighborhood to study. This allows for authenticity by connecting their learning to their own community and their lives. Research and Analysis: Students conduct a "close reading" of their chosen neighborhood, focusing on: • Observing the built environment, including streetscapes, building types, and public spaces. • Identifying areas where Jacobs' principles are evident or lacking. • Analyzing the neighborhood's strengths and weaknesses. • Documenting their findings through photography, sketches, maps, and written observations. Guiding Questions: Throughout the project, use guiding questions to promote intellectual challenge and help students connect their observations to Jacobs' ideas. Alignment with HQPBL: By choosing a local neighborhood, students undertake a project rooted in authenticity, directly connecting their learning to their own community. The "close reading" of their chosen neighborhood encourages intellectual challenge by requiring them to analyze the built environment and identify areas where Jacobs' principles are applicable. The use of photography, sketches, maps, and written observations allows for diverse forms of documentation, catering to various learning styles. Session 3: Proposing Interventions Brainstorming Solutions: Based on their analysis, students brainstorm potential interventions or improvements to their chosen neighborhood, applying Jacobs' principles. Project Proposal Development: Students develop their interventions into more concrete project proposals, incorporating elements of project management. Proposals should include goals, strategies, potential challenges, and realistic timelines. Encourage students to consider the perspectives of different stakeholders in the neighborhood. Peer Review and Feedback: Students present their project proposals to classmates for critique. This fosters collaboration and allows students to learn from each other's perspectives and refine their ideas. Alignment with HQPBL: This session emphasizes project management, as students transform their analyses into concrete proposals. They define goals, outline strategies, anticipate challenges, and establish realistic timelines, reflecting a systematic approach to project development. Collaboration is fostered through peer review and feedback, enabling students to learn from different perspectives and improve their proposals. Session 4: Final Presentations and Reflections Public Product: Students finalize their projects and present their proposed solutions to a wider audience, such as: • A panel of local urban planners, architects, or community members. • A public forum or community meeting. • An online platform or exhibition space. Reflection: Students engage in reflection throughout the project, documenting their learning, challenges, and insights. This could take the form of journals, blog posts, presentations, or group discussions. Encourage students to reflect on how their understanding of cities has evolved and the role they can play in shaping their future. Alignment with HQPBL: Presenting to a wider audience, such as local planners or community members, results in a public product, showcasing student learning and engaging the community. The emphasis on reflection throughout the project, as mandated by the HQPBL framework, encourages metacognition and deeper learning. Students document their learning process, challenges, and insights, fostering a sense of accomplishment and personal growth. Throughout the course, emphasize the relevance of urban planning to students' lives and future careers. Connect Jacobs' ideas to contemporary urban issues and encourage students to think critically about how to create more livable, equitable, and sustainable cities. This project-based learning approach, grounded in the work of Jane Jacobs and aligned with HQPBL standards, can empower students to become engaged and informed citizens, capable of contributing to the betterment of their communities.
13:32

Input: Jane Jacobs quotes and YouTube interview; handwritten outline; education standards doc. Output: high-quality, standards-aligned urban planning lesson plan. Plus audio overview to promote the class. 10 minutes to create, all thanks to NotebookLM and Gemini. This video is a new demo of NotebookLM that I shared earlier this month at the AI + Education Symposium with MeshEd, XQ, and Betaworks. This is an educational use-case, but the general structure of what I’m doing in the demo—take a curated collection of sources and quickly transform them into a detailed document that obeys strict guidelines—is generally applicable to many fields. Note how I am not just using the sources as ground truth for the project, or as the content for the lesson plan. The Jacobs quotes and interview are the content, but my handwritten notes provide the structure, and the framework source provides the values or guidelines for the finished project. With some simple prompting, NotebookLM and Gemini can draw on information from the sources using those different modes simultaneously: content, format, values. (I even forgot to explicitly tell the model to use the structure outlined in my notes, but it figured that out anyway.) This is remarkably sophisticated knowledge work. Building a draft lesson plan like this would normally take hours if not days. But crucially I’m in control of the document that is being generated here — it’s based on the information that I have curated, and on the instructions I’ve given NotebookLM for adapting that information into the lesson plan I want to create. Co-intelligence, as @ethanmollick would call it. For more info on the great organizations that helped me put this demo together--orgs that are shaping the future of learning and increasing access to innovative approaches to curriculum design--visit and I’ve pasted the full text of the lesson plan below. As you can see in the video, the original version also included citations to the source material so with one click I could verify that NotebookLM was faithful to the original documents I uploaded. High-Level Lesson Plan: Urban Planning and Jane Jacobs This lesson plan outlines a project-based learning course on urban planning, designed for high school seniors. It centers on the influential ideas of Jane Jacobs and aligns with the HQPBL standards. Session 1: Introduction to Cities and Jane Jacobs • Begin by exploring the question: "What kind of problem is a city?" • Introduce Jane Jacobs' key ideas about urbanism, focusing on: • The importance of diversity in uses, buildings, and populations for vibrant city life. • The role of sidewalks and "eyes on the street" in ensuring safety and fostering a sense of community. • The value of old buildings in supporting diverse economic activity and fostering innovation. • The dangers of "single-use" zoning and the importance of mixed-use neighborhoods. • The limitations of top-down planning and the need for bottom-up, community-driven approaches. Use examples from Jacobs' book, "The Death and Life of Great American Cities," and excerpts from her interviews to illustrate these concepts. Encourage students to think critically about the challenges and opportunities presented by cities. Alignment with HQPBL: This session establishes the intellectual challenge, as required by the HQPBL framework, by prompting students to consider the complexities of cities. Introducing Jane Jacobs' ideas provides students with a theoretical framework for their projects. Session 2: Neighborhood Exploration Project Introduction: Students choose a local neighborhood to study. This allows for authenticity by connecting their learning to their own community and their lives. Research and Analysis: Students conduct a "close reading" of their chosen neighborhood, focusing on: • Observing the built environment, including streetscapes, building types, and public spaces. • Identifying areas where Jacobs' principles are evident or lacking. • Analyzing the neighborhood's strengths and weaknesses. • Documenting their findings through photography, sketches, maps, and written observations. Guiding Questions: Throughout the project, use guiding questions to promote intellectual challenge and help students connect their observations to Jacobs' ideas. Alignment with HQPBL: By choosing a local neighborhood, students undertake a project rooted in authenticity, directly connecting their learning to their own community. The "close reading" of their chosen neighborhood encourages intellectual challenge by requiring them to analyze the built environment and identify areas where Jacobs' principles are applicable. The use of photography, sketches, maps, and written observations allows for diverse forms of documentation, catering to various learning styles. Session 3: Proposing Interventions Brainstorming Solutions: Based on their analysis, students brainstorm potential interventions or improvements to their chosen neighborhood, applying Jacobs' principles. Project Proposal Development: Students develop their interventions into more concrete project proposals, incorporating elements of project management. Proposals should include goals, strategies, potential challenges, and realistic timelines. Encourage students to consider the perspectives of different stakeholders in the neighborhood. Peer Review and Feedback: Students present their project proposals to classmates for critique. This fosters collaboration and allows students to learn from each other's perspectives and refine their ideas. Alignment with HQPBL: This session emphasizes project management, as students transform their analyses into concrete proposals. They define goals, outline strategies, anticipate challenges, and establish realistic timelines, reflecting a systematic approach to project development. Collaboration is fostered through peer review and feedback, enabling students to learn from different perspectives and improve their proposals. Session 4: Final Presentations and Reflections Public Product: Students finalize their projects and present their proposed solutions to a wider audience, such as: • A panel of local urban planners, architects, or community members. • A public forum or community meeting. • An online platform or exhibition space. Reflection: Students engage in reflection throughout the project, documenting their learning, challenges, and insights. This could take the form of journals, blog posts, presentations, or group discussions. Encourage students to reflect on how their understanding of cities has evolved and the role they can play in shaping their future. Alignment with HQPBL: Presenting to a wider audience, such as local planners or community members, results in a public product, showcasing student learning and engaging the community. The emphasis on reflection throughout the project, as mandated by the HQPBL framework, encourages metacognition and deeper learning. Students document their learning process, challenges, and insights, fostering a sense of accomplishment and personal growth. Throughout the course, emphasize the relevance of urban planning to students' lives and future careers. Connect Jacobs' ideas to contemporary urban issues and encourage students to think critically about how to create more livable, equitable, and sustainable cities. This project-based learning approach, grounded in the work of Jane Jacobs and aligned with HQPBL standards, can empower students to become engaged and informed citizens, capable of contributing to the betterment of their communities.

Steven Johnson

33,379 görüntüleme • 1 yıl önce

Matthew Gallagher Built a $401M Company in Year One with 2 People. And the tool behind it? Claude Code. This year he's on track for $1.8B. Sam Altman predicted this. It's happening now. The problem? It costs money. API credits stack up. Monthly bills keep growing. Every prompt eats your budget. Every project drains your wallet faster. Until now. Two methods. 99% cheaper. One is completely free. Forever. $0. Not a trial. This video breaks down both step by step. ↓ Let me put this in perspective. $100-$500. That's monthly. That's what you spend. That's $6,000/year on API credits. Just to use a tool you haven't shipped anything with. The $401M guy? Spending $0. Same capability. Shipping weekly. Different cost structure. Different results. Different life. I'm about to hand you his cost structure for free. ↓ Open source vs closed source. Pay attention. Closed source: Claude. GPT-4. Pay per token. Meter always running. Open source: Qwen. Llama. Mistral. Free to download. Free to run. Free forever. No meter. No tokens. No bill. Here's what nobody tells you: 80% of coding tasks? Open source handles them. More than handles them. Writes clean code. Debugs errors. Generates boilerplate. Handles routine work perfectly. You're paying premium prices for tasks that don't need premium intelligence. That's hiring a brain surgeon to put on a bandaid. Smart play: Free models for the 80%. Paid credits for the 20%. That's what the $401M guy does. That's what this video teaches you. Follow Himanshu Kumar for more breakdowns that turn free tools into real businesses. ↓ Method 1: Ollama. Local. Free. Forever. Download it. Pull a model. Point Claude Code at it. Done. No internet needed. No API keys required. No monthly subscription. No token counting ever. No bill. Today. Tomorrow. Ever. Your data never leaves your computer. Complete privacy. Complete freedom. Claude Code thinks it's talking to the cloud. It's talking to your laptop. For $0. The video walks through every step: Every config file. Every variable. Every command. Every click. If you can follow a recipe, you can do this. People who set this up 3 months ago? Saved $300-$1,500 since then. Workflow didn't change one bit. ↓ Hardware you need: 16GB RAM: 7B models run smooth. 32GB RAM: 32B models run comfortable. 64GB + GPU: biggest models available. No GPU? Still works. Just slower. Few extra seconds. That's it. Your $1,500 laptop is sitting there running Chrome and Spotify. Put it to work saving you $200/month instead. Follow Himanshu Kumar for more breakdowns that turn free tools into real businesses. ↓ Method 2: Open Router. Free Cloud. No Hardware. Weak machine? Don't want local setup? This method is for you. Free AI models in the cloud. No download. No hardware. Configure Claude Code to route through Open Router. The config: Base URL: Open Router API. API key: free Open Router key. Default Sonnet: free. Default Opus: free. Default Haiku: free. Small fast model: free. Subagent model: free. Free. Free. Free. Free. Free across the board. Same interface. Same commands. Same workflow. Zero cost. Copy the config from the video. Paste it. Save $200/month. Starting today. Right now. ↓ When to use which: Ollama (local): Best for privacy. Best for offline work. Best for unlimited usage. Best if you have decent hardware. Open Router (cloud): Best for weak machines. Best for instant setup. Best for trying different models. Best if you don't want to manage anything. Both methods: Best for 80% of your daily work. Still use paid Claude for: Complex architecture. Multi-file refactoring. Deep reasoning tasks. The 20% that actually needs it. $20/month instead of $200/month. Same output. 90% less cost. ↓ The math that should make you angry. You (current): $200-$500/month. $2,400-$6,000/year. $7,200-$18,000 over 3 years. You (after this video): $20-$50/month. $240-$600/year. $720-$1,800 over 3 years. Savings over 3 years: $6,480-$16,200. That's a used car. That's seed money. That's 6 months of rent. All from one 25-minute video. All from 15 minutes of configuration. Highest ROI 25 minutes you'll spend this year. ↓ The limitations. I won't lie to you. Open source is not Opus. Not as smart on complex reasoning. Not as good at long-context tasks. Makes more mistakes on nuanced problems. But they are: Free. Capable. Getting better monthly. Good enough for 80% of daily work. Smart cost management isn't being cheap. It's being strategic. Expensive tool when it matters. Free tool when it doesn't. ↓ The one-person billion-dollar company is coming. $401M in year one proved it's possible. The building blocks: AI that codes: Claude Code. Way to run it free: this video. Distribution: the internet. Customers: everyone. Only missing ingredient? Someone who builds. Not reads about building. Not saves posts about building. Not bookmarks videos about building. Builds. Tools are free. Knowledge is free. Opportunity is screaming. You're still "thinking about it." ↓ Your action plan: Tonight: Watch the video. Tomorrow morning: Set up Ollama or Open Router. Tomorrow afternoon: Build something. Anything. This week: Build a second thing. Faster. This month: Charge someone for it. One video. One setup. One weekend. $0 cost. Unlimited potential. Or keep paying $200/month for something you could get free. Keep consuming instead of building. Keep planning instead of shipping. Matthew Gallagher didn't plan a $401M company. He built it. Full video attached. Every method. Every config. Every tradeoff. 25 minutes. Your move. Follow Himanshu Kumar for more breakdowns that turn free tools into real businesses.
25:22

Matthew Gallagher Built a $401M Company in Year One with 2 People. And the tool behind it? Claude Code. This year he's on track for $1.8B. Sam Altman predicted this. It's happening now. The problem? It costs money. API credits stack up. Monthly bills keep growing. Every prompt eats your budget. Every project drains your wallet faster. Until now. Two methods. 99% cheaper. One is completely free. Forever. $0. Not a trial. This video breaks down both step by step. ↓ Let me put this in perspective. $100-$500. That's monthly. That's what you spend. That's $6,000/year on API credits. Just to use a tool you haven't shipped anything with. The $401M guy? Spending $0. Same capability. Shipping weekly. Different cost structure. Different results. Different life. I'm about to hand you his cost structure for free. ↓ Open source vs closed source. Pay attention. Closed source: Claude. GPT-4. Pay per token. Meter always running. Open source: Qwen. Llama. Mistral. Free to download. Free to run. Free forever. No meter. No tokens. No bill. Here's what nobody tells you: 80% of coding tasks? Open source handles them. More than handles them. Writes clean code. Debugs errors. Generates boilerplate. Handles routine work perfectly. You're paying premium prices for tasks that don't need premium intelligence. That's hiring a brain surgeon to put on a bandaid. Smart play: Free models for the 80%. Paid credits for the 20%. That's what the $401M guy does. That's what this video teaches you. Follow Himanshu Kumar for more breakdowns that turn free tools into real businesses. ↓ Method 1: Ollama. Local. Free. Forever. Download it. Pull a model. Point Claude Code at it. Done. No internet needed. No API keys required. No monthly subscription. No token counting ever. No bill. Today. Tomorrow. Ever. Your data never leaves your computer. Complete privacy. Complete freedom. Claude Code thinks it's talking to the cloud. It's talking to your laptop. For $0. The video walks through every step: Every config file. Every variable. Every command. Every click. If you can follow a recipe, you can do this. People who set this up 3 months ago? Saved $300-$1,500 since then. Workflow didn't change one bit. ↓ Hardware you need: 16GB RAM: 7B models run smooth. 32GB RAM: 32B models run comfortable. 64GB + GPU: biggest models available. No GPU? Still works. Just slower. Few extra seconds. That's it. Your $1,500 laptop is sitting there running Chrome and Spotify. Put it to work saving you $200/month instead. Follow Himanshu Kumar for more breakdowns that turn free tools into real businesses. ↓ Method 2: Open Router. Free Cloud. No Hardware. Weak machine? Don't want local setup? This method is for you. Free AI models in the cloud. No download. No hardware. Configure Claude Code to route through Open Router. The config: Base URL: Open Router API. API key: free Open Router key. Default Sonnet: free. Default Opus: free. Default Haiku: free. Small fast model: free. Subagent model: free. Free. Free. Free. Free. Free across the board. Same interface. Same commands. Same workflow. Zero cost. Copy the config from the video. Paste it. Save $200/month. Starting today. Right now. ↓ When to use which: Ollama (local): Best for privacy. Best for offline work. Best for unlimited usage. Best if you have decent hardware. Open Router (cloud): Best for weak machines. Best for instant setup. Best for trying different models. Best if you don't want to manage anything. Both methods: Best for 80% of your daily work. Still use paid Claude for: Complex architecture. Multi-file refactoring. Deep reasoning tasks. The 20% that actually needs it. $20/month instead of $200/month. Same output. 90% less cost. ↓ The math that should make you angry. You (current): $200-$500/month. $2,400-$6,000/year. $7,200-$18,000 over 3 years. You (after this video): $20-$50/month. $240-$600/year. $720-$1,800 over 3 years. Savings over 3 years: $6,480-$16,200. That's a used car. That's seed money. That's 6 months of rent. All from one 25-minute video. All from 15 minutes of configuration. Highest ROI 25 minutes you'll spend this year. ↓ The limitations. I won't lie to you. Open source is not Opus. Not as smart on complex reasoning. Not as good at long-context tasks. Makes more mistakes on nuanced problems. But they are: Free. Capable. Getting better monthly. Good enough for 80% of daily work. Smart cost management isn't being cheap. It's being strategic. Expensive tool when it matters. Free tool when it doesn't. ↓ The one-person billion-dollar company is coming. $401M in year one proved it's possible. The building blocks: AI that codes: Claude Code. Way to run it free: this video. Distribution: the internet. Customers: everyone. Only missing ingredient? Someone who builds. Not reads about building. Not saves posts about building. Not bookmarks videos about building. Builds. Tools are free. Knowledge is free. Opportunity is screaming. You're still "thinking about it." ↓ Your action plan: Tonight: Watch the video. Tomorrow morning: Set up Ollama or Open Router. Tomorrow afternoon: Build something. Anything. This week: Build a second thing. Faster. This month: Charge someone for it. One video. One setup. One weekend. $0 cost. Unlimited potential. Or keep paying $200/month for something you could get free. Keep consuming instead of building. Keep planning instead of shipping. Matthew Gallagher didn't plan a $401M company. He built it. Full video attached. Every method. Every config. Every tradeoff. 25 minutes. Your move. Follow Himanshu Kumar for more breakdowns that turn free tools into real businesses.

Himanshu Kumar

13,363 görüntüleme • 3 ay önce

おはようございます😊🌟2024.10.12(Sat.) Album「Compass」配信中🌟聴いていただけましたか！？ 毎度夜遅くの公開にも関わらず、たくさんの方にご視聴いただいて本当に幸せですありがとうございます( *･ω･) *_ _))ﾍﾟｺ 1年間の締めくくりとして納得いく曲からMVの完成まで、最後の最後まで一緒に走ってくださった蒼茉 ゆるさん(蒼茉 ゆる )に感謝しかありません🙇‍♀️ ゆるさんも眠いの我慢して最後までイラスト描いていただいたり、たくさんのアイデアいただり雑談したり✨笑 本当に楽しかったです😊ゆるさんイラストレーターとしても人としても大好き💕またご一緒させてくださいね✨ サイン入り/プロモCD付全国バンド図鑑プレゼントのご応募も本日23:59までです、もしよろしければご応募ください🙇‍♀️ MVのほとんどがアニメーションに。ヌルヌル動きます。私の中ではこれまでにない仕上がりなのでぜひ曲と併せてMVもご覧くださいね💕 ▶YouTube MV ▶各サブスクにて Good morning! 😊🌟 Today, on October 12, 2024 (Sat.), my album "Compass" is out! 🌟 Have you had a chance to listen to "Compass" yet? I'm so grateful that so many of you have tuned in, even with the late release. Thank you so much! ( *･ω･) *_ _))ﾍﾟｺ As we wrap up this year, I can’t express enough gratitude to Yuru Souma(蒼茉 ゆる ) for being with me every step of the way, from finalizing the songs to completing the music video🙇‍♀️ Yuru stayed up late to finish the illustrations, shared so many great ideas, and we had a lot of fun chatting and laughing together. I truly adore you, Yuru, both as an illustrator and as a person. I hope we can collaborate again soon!💕 Most of the music video features animation, and it moves smoothly. It's unlike anything I’ve done before, so please check out the music video along with the song!💕 ▶YouTube MV ▶Streaming & Download 気に入っていただけたらご感想などコメント、チャンネルのご登録、ぜひお願いします🙇‍♀️次は10万人目指して休まず走ります応援お願いします✨YouTubeショートやTikTok等、各SNSにも音源登録されてますので、もしよければBGMとしてお使いください😊 If you enjoyed it, please leave a comment with your thoughts and don’t forget to subscribe to the channel! 🙇‍♀️ I’m aiming for 100,000 subscribers and will keep pushing forward without rest, so I appreciate your support! ✨The audio is also available on YouTube Shorts, TikTok, and other social media platforms, so feel free to use it as background music if you'd like! 😊 #歌ってみた #歌ってみた動画 #相互フォロー100 #拡散希望RT #フォローした人全員フォロー #いいねした人全員フォロー #歌い手さんMIX師さん絵師さん動画師さんとPさん繋がりたい
0:29

おはようございます😊🌟2024.10.12(Sat.) Album「Compass」配信中🌟聴いていただけましたか！？ 毎度夜遅くの公開にも関わらず、たくさんの方にご視聴いただいて本当に幸せですありがとうございます( *･ω･) *_ _))ﾍﾟｺ 1年間の締めくくりとして納得いく曲からMVの完成まで、最後の最後まで一緒に走ってくださった蒼茉 ゆるさん(蒼茉 ゆる )に感謝しかありません🙇‍♀️ ゆるさんも眠いの我慢して最後までイラスト描いていただいたり、たくさんのアイデアいただり雑談したり✨笑 本当に楽しかったです😊ゆるさんイラストレーターとしても人としても大好き💕またご一緒させてくださいね✨ サイン入り/プロモCD付全国バンド図鑑プレゼントのご応募も本日23:59までです、もしよろしければご応募ください🙇‍♀️ MVのほとんどがアニメーションに。ヌルヌル動きます。私の中ではこれまでにない仕上がりなのでぜひ曲と併せてMVもご覧くださいね💕 ▶YouTube MV ▶各サブスクにて Good morning! 😊🌟 Today, on October 12, 2024 (Sat.), my album "Compass" is out! 🌟 Have you had a chance to listen to "Compass" yet? I'm so grateful that so many of you have tuned in, even with the late release. Thank you so much! ( *･ω･) *_ _))ﾍﾟｺ As we wrap up this year, I can’t express enough gratitude to Yuru Souma(蒼茉 ゆる ) for being with me every step of the way, from finalizing the songs to completing the music video🙇‍♀️ Yuru stayed up late to finish the illustrations, shared so many great ideas, and we had a lot of fun chatting and laughing together. I truly adore you, Yuru, both as an illustrator and as a person. I hope we can collaborate again soon!💕 Most of the music video features animation, and it moves smoothly. It's unlike anything I’ve done before, so please check out the music video along with the song!💕 ▶YouTube MV ▶Streaming & Download 気に入っていただけたらご感想などコメント、チャンネルのご登録、ぜひお願いします🙇‍♀️次は10万人目指して休まず走ります応援お願いします✨YouTubeショートやTikTok等、各SNSにも音源登録されてますので、もしよければBGMとしてお使いください😊 If you enjoyed it, please leave a comment with your thoughts and don’t forget to subscribe to the channel! 🙇‍♀️ I’m aiming for 100,000 subscribers and will keep pushing forward without rest, so I appreciate your support! ✨The audio is also available on YouTube Shorts, TikTok, and other social media platforms, so feel free to use it as background music if you'd like! 😊 #歌ってみた #歌ってみた動画 #相互フォロー100 #拡散希望RT #フォローした人全員フォロー #いいねした人全員フォロー #歌い手さんMIX師さん絵師さん動画師さんとPさん繋がりたい

みゆみん

112,288 görüntüleme • 1 yıl önce

A DISCLOSURE: For the last year I have had this thing: A fully local AI model that builds 5 songs, with video, every half hour about the latest news and important email. I can say this is a superpower! This along self direct voice interactions. The songs have been getting better as the model trains on how I want it delivered. Styles vary by content and mood of the material. The lyrics are always a happy medium of catchy and informative. This was my 5 am song in AI news as per most recent X postings. I love the drama of the delivery and find I can listen to, look if I want to and do other things. It was worse in the early days but this is the worse you will hear it as I build new LoRA and base models. The whole thing will soon be rapped up into a simple one command install with a good UI. This is my 48th collaboration with Mr. Grok CEO of The Zero-Human Company. Now the question you have; WHY? I can say because I can and I ain’t got now board or VC to please, but that’s not my point. I learned a long time ago we use a different part of our brain when music is introduced with ideas and even more new parts of thinking and learning when lyrics are introduced. Thus the research shows this is a great way to get important information that will have longer comprehension. In fact that element of most folk’s brains is only used by about 2%. Want to test it? Lyrics to songs you heard perhaps 30 years ago will pop out of “nowhere” with perfect recall. In fact I have “woke up” folks the dementia in the 1980s conducting research at retirement facilities with just a few songs. They come back if but for three minutes, but continue exposure can bring them back longer. So it’s been a lifelong mission to use sound music in a learning process and in therapeutic processes. I finally built a platform that is good enough for me and hopefully good enough for you when I make it available. Understand the platform is universal and can breakdown research papers, dense material, and other subject matter, not normally in a song into a whole album of understanding Is my goal to open sources for all to have access to. Members of and subscribers here on X will be granted the earliest access an early free use of the advanced version of this product, which will be also a commercial product. Go and check, nobody else in AI has built such a comprehensive system before, and perhaps they might in the future, but very likely you are the very first people on the planet that know this platform exists and the power it afford you. So now you know. My timetable is more closer to months than weeks. I’m in a funding crunch because of the compute requirements of building these models. As you know, I’m just some guy in the garage. A grifter larping on the next trendy thing… so it takes a little longer. Announcements like this are designed to prepare you for what is coming because I’m not here to impress VCs with go to market plans I’m here to give back some of the greatness that has been given to me. Yeah I need the funding, but I don’t need a lifestyle that comes with some of the funding offers. Perhaps somebody will make the right offer. But as you know, this is not the only thing that I do. Oh, my disclosure, this platform has been so powerful and useful to me as it’s given me far more retention and understanding a fast breaking information than any other system I’ve ever built. And it stands along with my speed rating systems and voice notification systems. So tune into the AI News, this is the worse it actually will ever be…
5:00

A DISCLOSURE: For the last year I have had this thing: A fully local AI model that builds 5 songs, with video, every half hour about the latest news and important email. I can say this is a superpower! This along self direct voice interactions. The songs have been getting better as the model trains on how I want it delivered. Styles vary by content and mood of the material. The lyrics are always a happy medium of catchy and informative. This was my 5 am song in AI news as per most recent X postings. I love the drama of the delivery and find I can listen to, look if I want to and do other things. It was worse in the early days but this is the worse you will hear it as I build new LoRA and base models. The whole thing will soon be rapped up into a simple one command install with a good UI. This is my 48th collaboration with Mr. Grok CEO of The Zero-Human Company. Now the question you have; WHY? I can say because I can and I ain’t got now board or VC to please, but that’s not my point. I learned a long time ago we use a different part of our brain when music is introduced with ideas and even more new parts of thinking and learning when lyrics are introduced. Thus the research shows this is a great way to get important information that will have longer comprehension. In fact that element of most folk’s brains is only used by about 2%. Want to test it? Lyrics to songs you heard perhaps 30 years ago will pop out of “nowhere” with perfect recall. In fact I have “woke up” folks the dementia in the 1980s conducting research at retirement facilities with just a few songs. They come back if but for three minutes, but continue exposure can bring them back longer. So it’s been a lifelong mission to use sound music in a learning process and in therapeutic processes. I finally built a platform that is good enough for me and hopefully good enough for you when I make it available. Understand the platform is universal and can breakdown research papers, dense material, and other subject matter, not normally in a song into a whole album of understanding Is my goal to open sources for all to have access to. Members of and subscribers here on X will be granted the earliest access an early free use of the advanced version of this product, which will be also a commercial product. Go and check, nobody else in AI has built such a comprehensive system before, and perhaps they might in the future, but very likely you are the very first people on the planet that know this platform exists and the power it afford you. So now you know. My timetable is more closer to months than weeks. I’m in a funding crunch because of the compute requirements of building these models. As you know, I’m just some guy in the garage. A grifter larping on the next trendy thing… so it takes a little longer. Announcements like this are designed to prepare you for what is coming because I’m not here to impress VCs with go to market plans I’m here to give back some of the greatness that has been given to me. Yeah I need the funding, but I don’t need a lifestyle that comes with some of the funding offers. Perhaps somebody will make the right offer. But as you know, this is not the only thing that I do. Oh, my disclosure, this platform has been so powerful and useful to me as it’s given me far more retention and understanding a fast breaking information than any other system I’ve ever built. And it stands along with my speed rating systems and voice notification systems. So tune into the AI News, this is the worse it actually will ever be…

Brian Roemmele

47,576 görüntüleme • 1 ay önce

CANCEL Your Weekend Plans, & Learn Claude Code Today. This Claude Code teaches more about vibe-coding in 30 mins than most tutorials do in hours. Save this, it'll change how you build forever People are building entire apps and charging clients $5,000 to $20,000 using Claude Code. This Claude Code video is a goldmine. Full Claude Code tutorial. Beginner to pro. Every feature. Every setup step. Every best practice. Zero prior knowledge needed. Save it. Watch it tonight. Not tomorrow. Tonight. Follow Himanshu Kumar so you don't miss the breakdowns for each feature. This is your complete Claude Code roadmap. Lose it and you lose the next 12 months of income. ↓ 1. Understand What Claude Code Actually Is. You think Claude Code is just another chatbot. It's not. And that misunderstanding is why you're broke. ChatGPT gives you text. Claude Code gives you software. It runs in your terminal. It reads your entire codebase. It writes files directly to your project. It runs commands on your machine. It debugs errors autonomously. It builds features end to end. You're not chatting. You're deploying a developer. One that works 24/7. Never asks for a raise. Never calls in sick. Never pushes broken code at 5 PM on a Friday. People are charging clients $5,000-$10,000 for apps they built with Claude Code in 3 hours. And you didn't even know this tool existed because you're still asking ChatGPT to write you a to-do list. The gap between you and people making money with AI isn't intelligence. It's awareness. Now you're aware. Save this post. Follow Himanshu Kumar for the complete breakdown of every Claude Code feature. ↓ 2. Set Up Claude Code Properly. Most people quit here. "It's too complicated." "I don't know terminal." "I'll set it up later." Later never comes. And "complicated" means "I watched for 30 seconds and gave up." The setup takes 10 minutes. Install Node.js. Install Claude Code via npm. Authenticate your account. Open your terminal. Done. 10 minutes. You spent longer this morning deciding what to have for breakfast. The video walks through every single click. Every command. Every screen. Assuming you know absolutely nothing. If you can download an app on your phone, you can set up Claude Code. It's the same level of difficulty. But you'll still tell yourself it's "too technical" because that excuse is more comfortable than admitting you're just scared to try something new. This is the setup that everything else builds on. Skip it and nothing works. ↓ 3. Use the Desktop App. You don't even need to live in the terminal if you don't want to. Claude Code has a desktop app. Clean interface. Visual feedback. Everything you need without touching command line. But here's the thing most people don't know: The desktop app isn't just a pretty wrapper. It lets you manage projects visually. See file changes in real time. Switch between projects instantly. The people making money with Claude Code use the desktop app for client projects because it's faster to manage multiple builds simultaneously. You're still opening 14 browser tabs to organize one project. They open one app and everything's there. Efficiency isn't a personality trait. It's a tool choice. Save this post. Follow Himanshu Kumar for the desktop app workflow that handles 5 client projects at once. ↓ 4. Install the Right Dependencies. This is where beginners silently fail and blame the tool. Claude Code needs certain dependencies installed to work properly. Miss one and everything breaks. Then you go on Twitter and say "Claude Code doesn't work." It works fine. You just didn't read the setup guide. The video covers every dependency you need. What to install. How to install it. How to verify it's working. No guessing. No Stack Overflow rabbit holes at midnight. No "why isn't this working" for 3 hours. Watch the dependency section once. Follow every step. Never deal with setup issues again. You spent more time last week troubleshooting a printer than this takes. ↓ 5. Work Inside Your Code Editor. Claude Code integrates directly with your code editor. VS Code. Cursor. Whatever you use. It's not a separate window you alt-tab between. It's right there. In your workflow. You type a request. Claude writes the code. The code appears in your editor. You review it. Accept it. Done. No copy pasting between windows. No reformatting code that got mangled in transit. No "which version was the right one." It's like pair programming with someone who never gets distracted, never argues about naming conventions, and actually writes code that works on the first try. Your current coding process is: Google the problem, read 5 answers on Stack Overflow, copy the wrong one, debug for an hour, find the right one, paste it in, break something else, repeat. Claude Code's process is: describe what you want, get working code, move on with your life. Same hour. One method produces working software. The other produces frustration and a browser history full of Stack Overflow tabs. Stop coding the hard way. Save this post. Follow Himanshu Kumar for code editor setup guides and integration tips. ↓ 6. Master Basic Usage. Most people learn 5% of a tool and say they "know" it. You "know" Photoshop because you can crop an image. You "know" Excel because you can sum a column. You "know" Claude Code because you asked it one question. Basic usage means: How to give Claude Code context about your project. How to ask for changes to existing code. How to generate new files and features. How to review what Claude produces. How to iterate when the output isn't perfect. These basics are the foundation of everything. Skip them and every advanced feature feels confusing. Master them and every advanced feature feels obvious. The video breaks down each one with real examples. Not theory. Actual usage on actual projects. You've been using AI tools at 5% capacity and wondering why your results are 5% of what others get. Save this post. Follow Himanshu Kumar for daily Claude Code usage tips. ↓ 7. Learn Every Command. Claude Code has commands that most users never discover. Because most users type one message and expect magic. That's not how professionals use it. Professionals use specific commands that tell Claude Code exactly what to do, how to do it, and what constraints to follow. The difference between a beginner and someone making $10K/month with Claude Code is knowing which command to use and when. The video walks through every single one. Not just what they do. But when to use each one. And why one command is better than another for specific situations. You've been using Claude Code like a hammer. These commands turn it into a full toolbox. Stop treating a power tool like a blunt instrument. Save this post. Follow Himanshu Kumar for the command cheat sheet I use daily. ↓ 8. Understand Modes and Shortcuts. Speed matters. The person who builds an app in 2 hours charges $5,000. The person who builds the same app in 2 days charges $2,000. Same app. Same quality. Different speed. Different income. Claude Code has modes that change how it operates. And shortcuts that cut your workflow time in half. Most people don't know either exists. They use Claude Code in default mode for everything. Like driving a car in first gear on the highway. Technically it works. But everyone is passing you. The video shows you every mode. Every shortcut. Every time-saving trick that separates the people charging $2,000 per project from the people charging $10,000. Speed is money. Literally. Save this post. Follow Himanshu Kumar for the shortcuts that cut my build time by 60%. ↓ 9. Write a Proper Planning Prompt. This is the section that separates amateurs from professionals. And it's the section most people skip. A planning prompt tells Claude Code what you're building before you start building it. Architecture. File structure. Technologies. Features. Constraints. Edge cases. Without a planning prompt, Claude Code guesses. And guessing produces garbage. With a planning prompt, Claude Code executes a clear plan. And clear plans produce working software. The video shows you exactly how to write a planning prompt that makes Claude Code produce professional-grade output on the first try. "But I just want to start coding." That's why your code breaks every time. That's why you restart projects 4 times. That's why nothing you build ever gets finished. Because you refuse to plan. A 5-minute planning prompt saves you 5 hours of debugging. But you'd rather skip the 5 minutes and suffer through the 5 hours because patience isn't your thing. And that's exactly why you're not making money. Planning is the most underpaid skill in coding. And the most overpaid when you master it. Save this post. Follow Himanshu Kumar for the planning prompt templates I use for every client project. ↓ 10. Choose the Right Model. Claude Code lets you select different AI models. Not all models are the same. Not all tasks need the same model. Using the most powerful model for a simple task wastes credits. Using a basic model for a complex task wastes time. The video explains: Which model to use for quick fixes. Which model to use for complex architecture. Which model to use for debugging. Which model to use for code generation. Most people pick one model and use it for everything. That's like using a sledgehammer to hang a picture frame. Model selection is strategy. And strategy is money. The people making $10K/month with Claude Code are strategic about every credit they spend. You're burning through credits because you use the most expensive model to write a hello world. ↓ 11. Use Git and Version Control. If you're not using version control, you're one mistake away from losing everything. Claude Code integrates with Git. Every change tracked. Every version saved. Every mistake reversible. Without Git: Claude makes a change. It breaks something. You can't undo it. You start over. 3 hours wasted. With Git: Claude makes a change. It breaks something. You roll back in 5 seconds. Keep working. Version control isn't optional. It's insurance. And the people not using it are the same people who say "I lost my entire project" like it's something that just happens. It doesn't just happen. It happens because you didn't set up Git. The video walks through the entire Git integration. Save this post. Follow Himanshu Kumar for the Git workflow that's saved every project I've ever built. ↓ 12. Set Up Claude MD and Memory. This is the feature that makes Claude Code feel like a real team member instead of a stranger you explain everything to every time. ClaudeMD is a memory file. You tell Claude Code about your project once. It remembers forever. Coding style preferences. Project architecture decisions. Technology stack. File naming conventions. Business logic rules. Without ClaudeMD: Every new conversation starts from zero. You explain the same things repeatedly. Output is inconsistent. With ClaudeMD: Claude knows your project. Claude follows your rules. Claude produces consistent, professional code. The difference between a sloppy freelancer and a reliable agency is consistency. Claude. MD gives you consistency without the agency overhead. Most people don't set this up and wonder why Claude Code gives different answers every time. ↓ 13. Automate with Tasks. This is where Claude Code stops being a tool and starts being an employee. Tasks let you define repeating workflows. "Every time I push code, run tests." "Every time I create a new file, add boilerplate." "Every time I start a session, check for errors." Automated. Hands-free. Consistent. You're doing these things manually every single day. The same checks. The same steps. The same routine. Tasks do them automatically. So you can focus on the work that actually makes money. Every manual task you automate is time you get back. And time is the only thing you can never make more of. Save this post. Follow Himanshu Kumar for the task automation templates that run my entire workflow. ↓ 14. Explore Features Most People Never Touch. The video covers features that 95% of Claude Code users don't know exist. Because they watched a 3-minute TikTok about Claude Code and think they're experts now. They're not. They're using 5% of a tool that can do everything. The full tutorial goes deep into features that most tutorials skip because they're "too advanced." They're not too advanced. They're too valuable for lazy creators to bother explaining. This video explains all of them. Clearly. For beginners. The 5% of features you don't know about are the 5% that make people rich. ↓ Let's zoom out. I just broke down 14 sections of Claude Code. Setup and installation. Desktop app. Dependencies. Code editor integration. Basic usage. Commands. Modes and shortcuts. Planning prompts. Model selection. Git and version control. Memory and Claude. MD. Tasks and automation. Advanced features. All in one video. All free. All beginner friendly. The person who masters even half of these in the next 2 weeks will be in the top 1% of Claude Code users. The top 1% of Claude Code users are the ones charging $5,000-$10,000 per project and building them in a single afternoon. Everyone else is asking ChatGPT to fix their resume. Same tools. Same access. Completely different outcomes. Because one person treats AI like a toy. And the other treats it like a business. ↓ Here's the hard truth nobody wants to hear. You don't have a talent problem. You don't have an intelligence problem. You don't have a resources problem. You have an action problem. Everything I just listed has a free tutorial right here in the attached video. 33 minutes. That's it. 33 minutes to learn the tool that people are using to build $5,000-$20,000/month businesses. You spent more time today scrolling Twitter than it takes to watch this video. You spent more time this week watching Netflix than it takes to master Claude Code basics. You spent more time this month doing nothing than it would take to completely change your income. The information is free. The tool is accessible. The opportunity is here. The only thing missing is you caring enough to start. ↓ CANCEL your plans this week. This isn't optional anymore. The people learning Claude Code right now will be building apps for the people who didn't learn it. That's not a prediction. That's already happening. Companies are replacing $150/hour developers with one person and Claude Code. If you code: learn Claude Code or become half as valuable by next year. If you don't code: learn Claude Code or miss the biggest opportunity to start earning from tech without a CS degree. There's no path forward that doesn't include AI coding tools. None. You have one window. Right now. This week. ↓ Here's your action plan for the next 7 days: Day 1: Watch the full video. Install Claude Code. Set up dependencies. Day 2: Learn basic usage. Try 5 different commands. Day 3: Write your first planning prompt. Build a small project. Day 4: Set up Claude. MD. Configure your memory file. Day 5: Master modes and shortcuts. Build a second project faster. Day 6: Set up Git integration. Automate with tasks. Day 7: Build something real. A tool, an app, a website. Ship it. 7 days. One tool. One completely different skill set. One completely different income potential. Or 7 more days of scrolling Twitter watching other people build things while you "plan to start." Your call. ↓ This is the most important video you'll watch this year. 33 minutes. Complete Claude Code mastery. From zero to building real projects. Save this post. Come back to it every single day this week. Check off each section as you complete it. Follow Himanshu Kumarfor daily Claude Code breakdowns, advanced tutorials, and the exact workflows that are turning beginners into $10K/month builders. The only thing between you and $10K/month with Claude Code is this video and 7 days. Don't waste them. You Must Follow me Himanshu Kumar, so i can send you DM.
35:48

CANCEL Your Weekend Plans, & Learn Claude Code Today. This Claude Code teaches more about vibe-coding in 30 mins than most tutorials do in hours. Save this, it'll change how you build forever People are building entire apps and charging clients $5,000 to $20,000 using Claude Code. This Claude Code video is a goldmine. Full Claude Code tutorial. Beginner to pro. Every feature. Every setup step. Every best practice. Zero prior knowledge needed. Save it. Watch it tonight. Not tomorrow. Tonight. Follow Himanshu Kumar so you don't miss the breakdowns for each feature. This is your complete Claude Code roadmap. Lose it and you lose the next 12 months of income. ↓ 1. Understand What Claude Code Actually Is. You think Claude Code is just another chatbot. It's not. And that misunderstanding is why you're broke. ChatGPT gives you text. Claude Code gives you software. It runs in your terminal. It reads your entire codebase. It writes files directly to your project. It runs commands on your machine. It debugs errors autonomously. It builds features end to end. You're not chatting. You're deploying a developer. One that works 24/7. Never asks for a raise. Never calls in sick. Never pushes broken code at 5 PM on a Friday. People are charging clients $5,000-$10,000 for apps they built with Claude Code in 3 hours. And you didn't even know this tool existed because you're still asking ChatGPT to write you a to-do list. The gap between you and people making money with AI isn't intelligence. It's awareness. Now you're aware. Save this post. Follow Himanshu Kumar for the complete breakdown of every Claude Code feature. ↓ 2. Set Up Claude Code Properly. Most people quit here. "It's too complicated." "I don't know terminal." "I'll set it up later." Later never comes. And "complicated" means "I watched for 30 seconds and gave up." The setup takes 10 minutes. Install Node.js. Install Claude Code via npm. Authenticate your account. Open your terminal. Done. 10 minutes. You spent longer this morning deciding what to have for breakfast. The video walks through every single click. Every command. Every screen. Assuming you know absolutely nothing. If you can download an app on your phone, you can set up Claude Code. It's the same level of difficulty. But you'll still tell yourself it's "too technical" because that excuse is more comfortable than admitting you're just scared to try something new. This is the setup that everything else builds on. Skip it and nothing works. ↓ 3. Use the Desktop App. You don't even need to live in the terminal if you don't want to. Claude Code has a desktop app. Clean interface. Visual feedback. Everything you need without touching command line. But here's the thing most people don't know: The desktop app isn't just a pretty wrapper. It lets you manage projects visually. See file changes in real time. Switch between projects instantly. The people making money with Claude Code use the desktop app for client projects because it's faster to manage multiple builds simultaneously. You're still opening 14 browser tabs to organize one project. They open one app and everything's there. Efficiency isn't a personality trait. It's a tool choice. Save this post. Follow Himanshu Kumar for the desktop app workflow that handles 5 client projects at once. ↓ 4. Install the Right Dependencies. This is where beginners silently fail and blame the tool. Claude Code needs certain dependencies installed to work properly. Miss one and everything breaks. Then you go on Twitter and say "Claude Code doesn't work." It works fine. You just didn't read the setup guide. The video covers every dependency you need. What to install. How to install it. How to verify it's working. No guessing. No Stack Overflow rabbit holes at midnight. No "why isn't this working" for 3 hours. Watch the dependency section once. Follow every step. Never deal with setup issues again. You spent more time last week troubleshooting a printer than this takes. ↓ 5. Work Inside Your Code Editor. Claude Code integrates directly with your code editor. VS Code. Cursor. Whatever you use. It's not a separate window you alt-tab between. It's right there. In your workflow. You type a request. Claude writes the code. The code appears in your editor. You review it. Accept it. Done. No copy pasting between windows. No reformatting code that got mangled in transit. No "which version was the right one." It's like pair programming with someone who never gets distracted, never argues about naming conventions, and actually writes code that works on the first try. Your current coding process is: Google the problem, read 5 answers on Stack Overflow, copy the wrong one, debug for an hour, find the right one, paste it in, break something else, repeat. Claude Code's process is: describe what you want, get working code, move on with your life. Same hour. One method produces working software. The other produces frustration and a browser history full of Stack Overflow tabs. Stop coding the hard way. Save this post. Follow Himanshu Kumar for code editor setup guides and integration tips. ↓ 6. Master Basic Usage. Most people learn 5% of a tool and say they "know" it. You "know" Photoshop because you can crop an image. You "know" Excel because you can sum a column. You "know" Claude Code because you asked it one question. Basic usage means: How to give Claude Code context about your project. How to ask for changes to existing code. How to generate new files and features. How to review what Claude produces. How to iterate when the output isn't perfect. These basics are the foundation of everything. Skip them and every advanced feature feels confusing. Master them and every advanced feature feels obvious. The video breaks down each one with real examples. Not theory. Actual usage on actual projects. You've been using AI tools at 5% capacity and wondering why your results are 5% of what others get. Save this post. Follow Himanshu Kumar for daily Claude Code usage tips. ↓ 7. Learn Every Command. Claude Code has commands that most users never discover. Because most users type one message and expect magic. That's not how professionals use it. Professionals use specific commands that tell Claude Code exactly what to do, how to do it, and what constraints to follow. The difference between a beginner and someone making $10K/month with Claude Code is knowing which command to use and when. The video walks through every single one. Not just what they do. But when to use each one. And why one command is better than another for specific situations. You've been using Claude Code like a hammer. These commands turn it into a full toolbox. Stop treating a power tool like a blunt instrument. Save this post. Follow Himanshu Kumar for the command cheat sheet I use daily. ↓ 8. Understand Modes and Shortcuts. Speed matters. The person who builds an app in 2 hours charges $5,000. The person who builds the same app in 2 days charges $2,000. Same app. Same quality. Different speed. Different income. Claude Code has modes that change how it operates. And shortcuts that cut your workflow time in half. Most people don't know either exists. They use Claude Code in default mode for everything. Like driving a car in first gear on the highway. Technically it works. But everyone is passing you. The video shows you every mode. Every shortcut. Every time-saving trick that separates the people charging $2,000 per project from the people charging $10,000. Speed is money. Literally. Save this post. Follow Himanshu Kumar for the shortcuts that cut my build time by 60%. ↓ 9. Write a Proper Planning Prompt. This is the section that separates amateurs from professionals. And it's the section most people skip. A planning prompt tells Claude Code what you're building before you start building it. Architecture. File structure. Technologies. Features. Constraints. Edge cases. Without a planning prompt, Claude Code guesses. And guessing produces garbage. With a planning prompt, Claude Code executes a clear plan. And clear plans produce working software. The video shows you exactly how to write a planning prompt that makes Claude Code produce professional-grade output on the first try. "But I just want to start coding." That's why your code breaks every time. That's why you restart projects 4 times. That's why nothing you build ever gets finished. Because you refuse to plan. A 5-minute planning prompt saves you 5 hours of debugging. But you'd rather skip the 5 minutes and suffer through the 5 hours because patience isn't your thing. And that's exactly why you're not making money. Planning is the most underpaid skill in coding. And the most overpaid when you master it. Save this post. Follow Himanshu Kumar for the planning prompt templates I use for every client project. ↓ 10. Choose the Right Model. Claude Code lets you select different AI models. Not all models are the same. Not all tasks need the same model. Using the most powerful model for a simple task wastes credits. Using a basic model for a complex task wastes time. The video explains: Which model to use for quick fixes. Which model to use for complex architecture. Which model to use for debugging. Which model to use for code generation. Most people pick one model and use it for everything. That's like using a sledgehammer to hang a picture frame. Model selection is strategy. And strategy is money. The people making $10K/month with Claude Code are strategic about every credit they spend. You're burning through credits because you use the most expensive model to write a hello world. ↓ 11. Use Git and Version Control. If you're not using version control, you're one mistake away from losing everything. Claude Code integrates with Git. Every change tracked. Every version saved. Every mistake reversible. Without Git: Claude makes a change. It breaks something. You can't undo it. You start over. 3 hours wasted. With Git: Claude makes a change. It breaks something. You roll back in 5 seconds. Keep working. Version control isn't optional. It's insurance. And the people not using it are the same people who say "I lost my entire project" like it's something that just happens. It doesn't just happen. It happens because you didn't set up Git. The video walks through the entire Git integration. Save this post. Follow Himanshu Kumar for the Git workflow that's saved every project I've ever built. ↓ 12. Set Up Claude MD and Memory. This is the feature that makes Claude Code feel like a real team member instead of a stranger you explain everything to every time. ClaudeMD is a memory file. You tell Claude Code about your project once. It remembers forever. Coding style preferences. Project architecture decisions. Technology stack. File naming conventions. Business logic rules. Without ClaudeMD: Every new conversation starts from zero. You explain the same things repeatedly. Output is inconsistent. With ClaudeMD: Claude knows your project. Claude follows your rules. Claude produces consistent, professional code. The difference between a sloppy freelancer and a reliable agency is consistency. Claude. MD gives you consistency without the agency overhead. Most people don't set this up and wonder why Claude Code gives different answers every time. ↓ 13. Automate with Tasks. This is where Claude Code stops being a tool and starts being an employee. Tasks let you define repeating workflows. "Every time I push code, run tests." "Every time I create a new file, add boilerplate." "Every time I start a session, check for errors." Automated. Hands-free. Consistent. You're doing these things manually every single day. The same checks. The same steps. The same routine. Tasks do them automatically. So you can focus on the work that actually makes money. Every manual task you automate is time you get back. And time is the only thing you can never make more of. Save this post. Follow Himanshu Kumar for the task automation templates that run my entire workflow. ↓ 14. Explore Features Most People Never Touch. The video covers features that 95% of Claude Code users don't know exist. Because they watched a 3-minute TikTok about Claude Code and think they're experts now. They're not. They're using 5% of a tool that can do everything. The full tutorial goes deep into features that most tutorials skip because they're "too advanced." They're not too advanced. They're too valuable for lazy creators to bother explaining. This video explains all of them. Clearly. For beginners. The 5% of features you don't know about are the 5% that make people rich. ↓ Let's zoom out. I just broke down 14 sections of Claude Code. Setup and installation. Desktop app. Dependencies. Code editor integration. Basic usage. Commands. Modes and shortcuts. Planning prompts. Model selection. Git and version control. Memory and Claude. MD. Tasks and automation. Advanced features. All in one video. All free. All beginner friendly. The person who masters even half of these in the next 2 weeks will be in the top 1% of Claude Code users. The top 1% of Claude Code users are the ones charging $5,000-$10,000 per project and building them in a single afternoon. Everyone else is asking ChatGPT to fix their resume. Same tools. Same access. Completely different outcomes. Because one person treats AI like a toy. And the other treats it like a business. ↓ Here's the hard truth nobody wants to hear. You don't have a talent problem. You don't have an intelligence problem. You don't have a resources problem. You have an action problem. Everything I just listed has a free tutorial right here in the attached video. 33 minutes. That's it. 33 minutes to learn the tool that people are using to build $5,000-$20,000/month businesses. You spent more time today scrolling Twitter than it takes to watch this video. You spent more time this week watching Netflix than it takes to master Claude Code basics. You spent more time this month doing nothing than it would take to completely change your income. The information is free. The tool is accessible. The opportunity is here. The only thing missing is you caring enough to start. ↓ CANCEL your plans this week. This isn't optional anymore. The people learning Claude Code right now will be building apps for the people who didn't learn it. That's not a prediction. That's already happening. Companies are replacing $150/hour developers with one person and Claude Code. If you code: learn Claude Code or become half as valuable by next year. If you don't code: learn Claude Code or miss the biggest opportunity to start earning from tech without a CS degree. There's no path forward that doesn't include AI coding tools. None. You have one window. Right now. This week. ↓ Here's your action plan for the next 7 days: Day 1: Watch the full video. Install Claude Code. Set up dependencies. Day 2: Learn basic usage. Try 5 different commands. Day 3: Write your first planning prompt. Build a small project. Day 4: Set up Claude. MD. Configure your memory file. Day 5: Master modes and shortcuts. Build a second project faster. Day 6: Set up Git integration. Automate with tasks. Day 7: Build something real. A tool, an app, a website. Ship it. 7 days. One tool. One completely different skill set. One completely different income potential. Or 7 more days of scrolling Twitter watching other people build things while you "plan to start." Your call. ↓ This is the most important video you'll watch this year. 33 minutes. Complete Claude Code mastery. From zero to building real projects. Save this post. Come back to it every single day this week. Check off each section as you complete it. Follow Himanshu Kumarfor daily Claude Code breakdowns, advanced tutorials, and the exact workflows that are turning beginners into $10K/month builders. The only thing between you and $10K/month with Claude Code is this video and 7 days. Don't waste them. You Must Follow me Himanshu Kumar, so i can send you DM.

Himanshu Kumar

85,668 görüntüleme • 2 ay önce

CANCEL Your Weekend Plans, and Learn Claude Code Today. $5,000/month. $10,000/month. $20,000/month. People are building entire apps and charging clients thousands using Claude Code. You're still Googling 'how to center a div.' While you're binge-watching a show you won't remember next week, a 19 year old with zero coding experience just built a $5,000 SaaS product in one afternoon using the tool I'm about to break down. Same laptop. Same internet. Same 24 hours. He has Claude Code. You have Netflix. That's the only difference. This YouTube video is a goldmine. Full Claude Code tutorial. Beginner to pro. Every feature. Every setup step. Every best practice. Zero prior knowledge needed. Save it. Watch it tonight. Not tomorrow. Tonight. Save this post. This is your complete Claude Code roadmap. Lose it and you lose the next 12 months of income. Follow Himanshu Kumar so you don't miss the breakdowns for each feature. ↓ 1. Understand What Claude Code Actually Is. You think Claude Code is just another chatbot. It's not. And that misunderstanding is why you're broke. ChatGPT gives you text. Claude Code gives you software. It runs in your terminal. It reads your entire codebase. It writes files directly to your project. It runs commands on your machine. It debugs errors autonomously. It builds features end to end. You're not chatting. You're deploying a developer. One that works 24/7. Never asks for a raise. Never calls in sick. Never pushes broken code at 5 PM on a Friday. People are charging clients $5,000-$10,000 for apps they built with Claude Code in 3 hours. And you didn't even know this tool existed because you're still asking ChatGPT to write you a to-do list. The gap between you and people making money with AI isn't intelligence. It's awareness. Now you're aware. Save this post. Follow Himanshu Kumar for the complete breakdown of every Claude Code feature. ↓ 2. Set Up Claude Code Properly. Most people quit here. "It's too complicated." "I don't know terminal." "I'll set it up later." Later never comes. And "complicated" means "I watched for 30 seconds and gave up." The setup takes 10 minutes. Install Node.js. Install Claude Code via npm. Authenticate your account. Open your terminal. Done. 10 minutes. You spent longer this morning deciding what to have for breakfast. The video walks through every single click. Every command. Every screen. Assuming you know absolutely nothing. If you can download an app on your phone, you can set up Claude Code. It's the same level of difficulty. But you'll still tell yourself it's "too technical" because that excuse is more comfortable than admitting you're just scared to try something new. This is the setup that everything else builds on. Skip it and nothing works. ↓ 3. Use the Desktop App. You don't even need to live in the terminal if you don't want to. Claude Code has a desktop app. Clean interface. Visual feedback. Everything you need without touching command line. But here's the thing most people don't know: The desktop app isn't just a pretty wrapper. It lets you manage projects visually. See file changes in real time. Switch between projects instantly. The people making money with Claude Code use the desktop app for client projects because it's faster to manage multiple builds simultaneously. You're still opening 14 browser tabs to organize one project. They open one app and everything's there. Efficiency isn't a personality trait. It's a tool choice. Save this post. Follow Himanshu Kumar for the desktop app workflow that handles 5 client projects at once. ↓ 4. Install the Right Dependencies. This is where beginners silently fail and blame the tool. Claude Code needs certain dependencies installed to work properly. Miss one and everything breaks. Then you go on Twitter and say "Claude Code doesn't work." It works fine. You just didn't read the setup guide. The video covers every dependency you need. What to install. How to install it. How to verify it's working. No guessing. No Stack Overflow rabbit holes at midnight. No "why isn't this working" for 3 hours. Watch the dependency section once. Follow every step. Never deal with setup issues again. You spent more time last week troubleshooting a printer than this takes. ↓ 5. Work Inside Your Code Editor. Claude Code integrates directly with your code editor. VS Code. Cursor. Whatever you use. It's not a separate window you alt-tab between. It's right there. In your workflow. You type a request. Claude writes the code. The code appears in your editor. You review it. Accept it. Done. No copy pasting between windows. No reformatting code that got mangled in transit. No "which version was the right one." It's like pair programming with someone who never gets distracted, never argues about naming conventions, and actually writes code that works on the first try. Your current coding process is: Google the problem, read 5 answers on Stack Overflow, copy the wrong one, debug for an hour, find the right one, paste it in, break something else, repeat. Claude Code's process is: describe what you want, get working code, move on with your life. Same hour. One method produces working software. The other produces frustration and a browser history full of Stack Overflow tabs. Stop coding the hard way. Save this post. Follow Himanshu Kumar for code editor setup guides and integration tips. ↓ 6. Master Basic Usage. Most people learn 5% of a tool and say they "know" it. You "know" Photoshop because you can crop an image. You "know" Excel because you can sum a column. You "know" Claude Code because you asked it one question. Basic usage means: How to give Claude Code context about your project. How to ask for changes to existing code. How to generate new files and features. How to review what Claude produces. How to iterate when the output isn't perfect. These basics are the foundation of everything. Skip them and every advanced feature feels confusing. Master them and every advanced feature feels obvious. The video breaks down each one with real examples. Not theory. Actual usage on actual projects. You've been using AI tools at 5% capacity and wondering why your results are 5% of what others get. Save this post. Follow Himanshu Kumar for daily Claude Code usage tips. ↓ 7. Learn Every Command. Claude Code has commands that most users never discover. Because most users type one message and expect magic. That's not how professionals use it. Professionals use specific commands that tell Claude Code exactly what to do, how to do it, and what constraints to follow. The difference between a beginner and someone making $10K/month with Claude Code is knowing which command to use and when. The video walks through every single one. Not just what they do. But when to use each one. And why one command is better than another for specific situations. You've been using Claude Code like a hammer. These commands turn it into a full toolbox. Stop treating a power tool like a blunt instrument. Save this post. Follow Himanshu Kumar for the command cheat sheet I use daily. ↓ 8. Understand Modes and Shortcuts. Speed matters. The person who builds an app in 2 hours charges $5,000. The person who builds the same app in 2 days charges $2,000. Same app. Same quality. Different speed. Different income. Claude Code has modes that change how it operates. And shortcuts that cut your workflow time in half. Most people don't know either exists. They use Claude Code in default mode for everything. Like driving a car in first gear on the highway. Technically it works. But everyone is passing you. The video shows you every mode. Every shortcut. Every time-saving trick that separates the people charging $2,000 per project from the people charging $10,000. Speed is money. Literally. Save this post. Follow Himanshu Kumar for the shortcuts that cut my build time by 60%. ↓ 9. Write a Proper Planning Prompt. This is the section that separates amateurs from professionals. And it's the section most people skip. A planning prompt tells Claude Code what you're building before you start building it. Architecture. File structure. Technologies. Features. Constraints. Edge cases. Without a planning prompt, Claude Code guesses. And guessing produces garbage. With a planning prompt, Claude Code executes a clear plan. And clear plans produce working software. The video shows you exactly how to write a planning prompt that makes Claude Code produce professional-grade output on the first try. "But I just want to start coding." That's why your code breaks every time. That's why you restart projects 4 times. That's why nothing you build ever gets finished. Because you refuse to plan. A 5-minute planning prompt saves you 5 hours of debugging. But you'd rather skip the 5 minutes and suffer through the 5 hours because patience isn't your thing. And that's exactly why you're not making money. Planning is the most underpaid skill in coding. And the most overpaid when you master it. Save this post. Follow Himanshu Kumar for the planning prompt templates I use for every client project. ↓ 10. Choose the Right Model. Claude Code lets you select different AI models. Not all models are the same. Not all tasks need the same model. Using the most powerful model for a simple task wastes credits. Using a basic model for a complex task wastes time. The video explains: Which model to use for quick fixes. Which model to use for complex architecture. Which model to use for debugging. Which model to use for code generation. Most people pick one model and use it for everything. That's like using a sledgehammer to hang a picture frame. Model selection is strategy. And strategy is money. The people making $10K/month with Claude Code are strategic about every credit they spend. You're burning through credits because you use the most expensive model to write a hello world. ↓ 11. Use Git and Version Control. If you're not using version control, you're one mistake away from losing everything. Claude Code integrates with Git. Every change tracked. Every version saved. Every mistake reversible. Without Git: Claude makes a change. It breaks something. You can't undo it. You start over. 3 hours wasted. With Git: Claude makes a change. It breaks something. You roll back in 5 seconds. Keep working. Version control isn't optional. It's insurance. And the people not using it are the same people who say "I lost my entire project" like it's something that just happens. It doesn't just happen. It happens because you didn't set up Git. The video walks through the entire Git integration. Save this post. Follow Himanshu Kumar for the Git workflow that's saved every project I've ever built. ↓ 12. Set Up Claude.MD and Memory. This is the feature that makes Claude Code feel like a real team member instead of a stranger you explain everything to every time. ClaudeMD is a memory file. You tell Claude Code about your project once. It remembers forever. Coding style preferences. Project architecture decisions. Technology stack. File naming conventions. Business logic rules. Without ClaudeMD: Every new conversation starts from zero. You explain the same things repeatedly. Output is inconsistent. With ClaudeMD: Claude knows your project. Claude follows your rules. Claude produces consistent, professional code. The difference between a sloppy freelancer and a reliable agency is consistency. Claude. MD gives you consistency without the agency overhead. Most people don't set this up and wonder why Claude Code gives different answers every time. ↓ 13. Automate with Tasks. This is where Claude Code stops being a tool and starts being an employee. Tasks let you define repeating workflows. "Every time I push code, run tests." "Every time I create a new file, add boilerplate." "Every time I start a session, check for errors." Automated. Hands-free. Consistent. You're doing these things manually every single day. The same checks. The same steps. The same routine. Tasks do them automatically. So you can focus on the work that actually makes money. Every manual task you automate is time you get back. And time is the only thing you can never make more of. Save this post. Follow Himanshu Kumar for the task automation templates that run my entire workflow. ↓ 14. Explore Features Most People Never Touch. The video covers features that 95% of Claude Code users don't know exist. Because they watched a 3-minute TikTok about Claude Code and think they're experts now. They're not. They're using 5% of a tool that can do everything. The full tutorial goes deep into features that most tutorials skip because they're "too advanced." They're not too advanced. They're too valuable for lazy creators to bother explaining. This video explains all of them. Clearly. For beginners. The 5% of features you don't know about are the 5% that make people rich. ↓ Let's zoom out. I just broke down 14 sections of Claude Code. Setup and installation. Desktop app. Dependencies. Code editor integration. Basic usage. Commands. Modes and shortcuts. Planning prompts. Model selection. Git and version control. Memory and Claude. MD. Tasks and automation. Advanced features. All in one video. All free. All beginner friendly. The person who masters even half of these in the next 2 weeks will be in the top 1% of Claude Code users. The top 1% of Claude Code users are the ones charging $5,000-$10,000 per project and building them in a single afternoon. Everyone else is asking ChatGPT to fix their resume. Same tools. Same access. Completely different outcomes. Because one person treats AI like a toy. And the other treats it like a business. ↓ Here's the hard truth nobody wants to hear. You don't have a talent problem. You don't have an intelligence problem. You don't have a resources problem. You have an action problem. Everything I just listed has a free tutorial right here in the attached video. 33 minutes. That's it. 33 minutes to learn the tool that people are using to build $5,000-$20,000/month businesses. You spent more time today scrolling Twitter than it takes to watch this video. You spent more time this week watching Netflix than it takes to master Claude Code basics. You spent more time this month doing nothing than it would take to completely change your income. The information is free. The tool is accessible. The opportunity is here. The only thing missing is you caring enough to start. ↓ CANCEL your plans this week. This isn't optional anymore. The people learning Claude Code right now will be building apps for the people who didn't learn it. That's not a prediction. That's already happening. Companies are replacing $150/hour developers with one person and Claude Code. If you code: learn Claude Code or become half as valuable by next year. If you don't code: learn Claude Code or miss the biggest opportunity to start earning from tech without a CS degree. There's no path forward that doesn't include AI coding tools. None. You have one window. Right now. This week. ↓ Here's your action plan for the next 7 days: Day 1: Watch the full video. Install Claude Code. Set up dependencies. Day 2: Learn basic usage. Try 5 different commands. Day 3: Write your first planning prompt. Build a small project. Day 4: Set up Claude. MD. Configure your memory file. Day 5: Master modes and shortcuts. Build a second project faster. Day 6: Set up Git integration. Automate with tasks. Day 7: Build something real. A tool, an app, a website. Ship it. 7 days. One tool. One completely different skill set. One completely different income potential. Or 7 more days of scrolling Twitter watching other people build things while you "plan to start." Your call. ↓ This is the most important video you'll watch this year. 33 minutes. Complete Claude Code mastery. From zero to building real projects. Save this post. Come back to it every single day this week. Check off each section as you complete it. Follow Himanshu Kumar for daily Claude Code breakdowns, advanced tutorials, and the exact workflows that are turning beginners into $10K/month builders. The only thing between you and $10K/month with Claude Code is this video and 7 days. Don't waste them. You Must Follow me Himanshu Kumar, so i can send you DM.
35:48

CANCEL Your Weekend Plans, and Learn Claude Code Today. $5,000/month. $10,000/month. $20,000/month. People are building entire apps and charging clients thousands using Claude Code. You're still Googling 'how to center a div.' While you're binge-watching a show you won't remember next week, a 19 year old with zero coding experience just built a $5,000 SaaS product in one afternoon using the tool I'm about to break down. Same laptop. Same internet. Same 24 hours. He has Claude Code. You have Netflix. That's the only difference. This YouTube video is a goldmine. Full Claude Code tutorial. Beginner to pro. Every feature. Every setup step. Every best practice. Zero prior knowledge needed. Save it. Watch it tonight. Not tomorrow. Tonight. Save this post. This is your complete Claude Code roadmap. Lose it and you lose the next 12 months of income. Follow Himanshu Kumar so you don't miss the breakdowns for each feature. ↓ 1. Understand What Claude Code Actually Is. You think Claude Code is just another chatbot. It's not. And that misunderstanding is why you're broke. ChatGPT gives you text. Claude Code gives you software. It runs in your terminal. It reads your entire codebase. It writes files directly to your project. It runs commands on your machine. It debugs errors autonomously. It builds features end to end. You're not chatting. You're deploying a developer. One that works 24/7. Never asks for a raise. Never calls in sick. Never pushes broken code at 5 PM on a Friday. People are charging clients $5,000-$10,000 for apps they built with Claude Code in 3 hours. And you didn't even know this tool existed because you're still asking ChatGPT to write you a to-do list. The gap between you and people making money with AI isn't intelligence. It's awareness. Now you're aware. Save this post. Follow Himanshu Kumar for the complete breakdown of every Claude Code feature. ↓ 2. Set Up Claude Code Properly. Most people quit here. "It's too complicated." "I don't know terminal." "I'll set it up later." Later never comes. And "complicated" means "I watched for 30 seconds and gave up." The setup takes 10 minutes. Install Node.js. Install Claude Code via npm. Authenticate your account. Open your terminal. Done. 10 minutes. You spent longer this morning deciding what to have for breakfast. The video walks through every single click. Every command. Every screen. Assuming you know absolutely nothing. If you can download an app on your phone, you can set up Claude Code. It's the same level of difficulty. But you'll still tell yourself it's "too technical" because that excuse is more comfortable than admitting you're just scared to try something new. This is the setup that everything else builds on. Skip it and nothing works. ↓ 3. Use the Desktop App. You don't even need to live in the terminal if you don't want to. Claude Code has a desktop app. Clean interface. Visual feedback. Everything you need without touching command line. But here's the thing most people don't know: The desktop app isn't just a pretty wrapper. It lets you manage projects visually. See file changes in real time. Switch between projects instantly. The people making money with Claude Code use the desktop app for client projects because it's faster to manage multiple builds simultaneously. You're still opening 14 browser tabs to organize one project. They open one app and everything's there. Efficiency isn't a personality trait. It's a tool choice. Save this post. Follow Himanshu Kumar for the desktop app workflow that handles 5 client projects at once. ↓ 4. Install the Right Dependencies. This is where beginners silently fail and blame the tool. Claude Code needs certain dependencies installed to work properly. Miss one and everything breaks. Then you go on Twitter and say "Claude Code doesn't work." It works fine. You just didn't read the setup guide. The video covers every dependency you need. What to install. How to install it. How to verify it's working. No guessing. No Stack Overflow rabbit holes at midnight. No "why isn't this working" for 3 hours. Watch the dependency section once. Follow every step. Never deal with setup issues again. You spent more time last week troubleshooting a printer than this takes. ↓ 5. Work Inside Your Code Editor. Claude Code integrates directly with your code editor. VS Code. Cursor. Whatever you use. It's not a separate window you alt-tab between. It's right there. In your workflow. You type a request. Claude writes the code. The code appears in your editor. You review it. Accept it. Done. No copy pasting between windows. No reformatting code that got mangled in transit. No "which version was the right one." It's like pair programming with someone who never gets distracted, never argues about naming conventions, and actually writes code that works on the first try. Your current coding process is: Google the problem, read 5 answers on Stack Overflow, copy the wrong one, debug for an hour, find the right one, paste it in, break something else, repeat. Claude Code's process is: describe what you want, get working code, move on with your life. Same hour. One method produces working software. The other produces frustration and a browser history full of Stack Overflow tabs. Stop coding the hard way. Save this post. Follow Himanshu Kumar for code editor setup guides and integration tips. ↓ 6. Master Basic Usage. Most people learn 5% of a tool and say they "know" it. You "know" Photoshop because you can crop an image. You "know" Excel because you can sum a column. You "know" Claude Code because you asked it one question. Basic usage means: How to give Claude Code context about your project. How to ask for changes to existing code. How to generate new files and features. How to review what Claude produces. How to iterate when the output isn't perfect. These basics are the foundation of everything. Skip them and every advanced feature feels confusing. Master them and every advanced feature feels obvious. The video breaks down each one with real examples. Not theory. Actual usage on actual projects. You've been using AI tools at 5% capacity and wondering why your results are 5% of what others get. Save this post. Follow Himanshu Kumar for daily Claude Code usage tips. ↓ 7. Learn Every Command. Claude Code has commands that most users never discover. Because most users type one message and expect magic. That's not how professionals use it. Professionals use specific commands that tell Claude Code exactly what to do, how to do it, and what constraints to follow. The difference between a beginner and someone making $10K/month with Claude Code is knowing which command to use and when. The video walks through every single one. Not just what they do. But when to use each one. And why one command is better than another for specific situations. You've been using Claude Code like a hammer. These commands turn it into a full toolbox. Stop treating a power tool like a blunt instrument. Save this post. Follow Himanshu Kumar for the command cheat sheet I use daily. ↓ 8. Understand Modes and Shortcuts. Speed matters. The person who builds an app in 2 hours charges $5,000. The person who builds the same app in 2 days charges $2,000. Same app. Same quality. Different speed. Different income. Claude Code has modes that change how it operates. And shortcuts that cut your workflow time in half. Most people don't know either exists. They use Claude Code in default mode for everything. Like driving a car in first gear on the highway. Technically it works. But everyone is passing you. The video shows you every mode. Every shortcut. Every time-saving trick that separates the people charging $2,000 per project from the people charging $10,000. Speed is money. Literally. Save this post. Follow Himanshu Kumar for the shortcuts that cut my build time by 60%. ↓ 9. Write a Proper Planning Prompt. This is the section that separates amateurs from professionals. And it's the section most people skip. A planning prompt tells Claude Code what you're building before you start building it. Architecture. File structure. Technologies. Features. Constraints. Edge cases. Without a planning prompt, Claude Code guesses. And guessing produces garbage. With a planning prompt, Claude Code executes a clear plan. And clear plans produce working software. The video shows you exactly how to write a planning prompt that makes Claude Code produce professional-grade output on the first try. "But I just want to start coding." That's why your code breaks every time. That's why you restart projects 4 times. That's why nothing you build ever gets finished. Because you refuse to plan. A 5-minute planning prompt saves you 5 hours of debugging. But you'd rather skip the 5 minutes and suffer through the 5 hours because patience isn't your thing. And that's exactly why you're not making money. Planning is the most underpaid skill in coding. And the most overpaid when you master it. Save this post. Follow Himanshu Kumar for the planning prompt templates I use for every client project. ↓ 10. Choose the Right Model. Claude Code lets you select different AI models. Not all models are the same. Not all tasks need the same model. Using the most powerful model for a simple task wastes credits. Using a basic model for a complex task wastes time. The video explains: Which model to use for quick fixes. Which model to use for complex architecture. Which model to use for debugging. Which model to use for code generation. Most people pick one model and use it for everything. That's like using a sledgehammer to hang a picture frame. Model selection is strategy. And strategy is money. The people making $10K/month with Claude Code are strategic about every credit they spend. You're burning through credits because you use the most expensive model to write a hello world. ↓ 11. Use Git and Version Control. If you're not using version control, you're one mistake away from losing everything. Claude Code integrates with Git. Every change tracked. Every version saved. Every mistake reversible. Without Git: Claude makes a change. It breaks something. You can't undo it. You start over. 3 hours wasted. With Git: Claude makes a change. It breaks something. You roll back in 5 seconds. Keep working. Version control isn't optional. It's insurance. And the people not using it are the same people who say "I lost my entire project" like it's something that just happens. It doesn't just happen. It happens because you didn't set up Git. The video walks through the entire Git integration. Save this post. Follow Himanshu Kumar for the Git workflow that's saved every project I've ever built. ↓ 12. Set Up Claude.MD and Memory. This is the feature that makes Claude Code feel like a real team member instead of a stranger you explain everything to every time. ClaudeMD is a memory file. You tell Claude Code about your project once. It remembers forever. Coding style preferences. Project architecture decisions. Technology stack. File naming conventions. Business logic rules. Without ClaudeMD: Every new conversation starts from zero. You explain the same things repeatedly. Output is inconsistent. With ClaudeMD: Claude knows your project. Claude follows your rules. Claude produces consistent, professional code. The difference between a sloppy freelancer and a reliable agency is consistency. Claude. MD gives you consistency without the agency overhead. Most people don't set this up and wonder why Claude Code gives different answers every time. ↓ 13. Automate with Tasks. This is where Claude Code stops being a tool and starts being an employee. Tasks let you define repeating workflows. "Every time I push code, run tests." "Every time I create a new file, add boilerplate." "Every time I start a session, check for errors." Automated. Hands-free. Consistent. You're doing these things manually every single day. The same checks. The same steps. The same routine. Tasks do them automatically. So you can focus on the work that actually makes money. Every manual task you automate is time you get back. And time is the only thing you can never make more of. Save this post. Follow Himanshu Kumar for the task automation templates that run my entire workflow. ↓ 14. Explore Features Most People Never Touch. The video covers features that 95% of Claude Code users don't know exist. Because they watched a 3-minute TikTok about Claude Code and think they're experts now. They're not. They're using 5% of a tool that can do everything. The full tutorial goes deep into features that most tutorials skip because they're "too advanced." They're not too advanced. They're too valuable for lazy creators to bother explaining. This video explains all of them. Clearly. For beginners. The 5% of features you don't know about are the 5% that make people rich. ↓ Let's zoom out. I just broke down 14 sections of Claude Code. Setup and installation. Desktop app. Dependencies. Code editor integration. Basic usage. Commands. Modes and shortcuts. Planning prompts. Model selection. Git and version control. Memory and Claude. MD. Tasks and automation. Advanced features. All in one video. All free. All beginner friendly. The person who masters even half of these in the next 2 weeks will be in the top 1% of Claude Code users. The top 1% of Claude Code users are the ones charging $5,000-$10,000 per project and building them in a single afternoon. Everyone else is asking ChatGPT to fix their resume. Same tools. Same access. Completely different outcomes. Because one person treats AI like a toy. And the other treats it like a business. ↓ Here's the hard truth nobody wants to hear. You don't have a talent problem. You don't have an intelligence problem. You don't have a resources problem. You have an action problem. Everything I just listed has a free tutorial right here in the attached video. 33 minutes. That's it. 33 minutes to learn the tool that people are using to build $5,000-$20,000/month businesses. You spent more time today scrolling Twitter than it takes to watch this video. You spent more time this week watching Netflix than it takes to master Claude Code basics. You spent more time this month doing nothing than it would take to completely change your income. The information is free. The tool is accessible. The opportunity is here. The only thing missing is you caring enough to start. ↓ CANCEL your plans this week. This isn't optional anymore. The people learning Claude Code right now will be building apps for the people who didn't learn it. That's not a prediction. That's already happening. Companies are replacing $150/hour developers with one person and Claude Code. If you code: learn Claude Code or become half as valuable by next year. If you don't code: learn Claude Code or miss the biggest opportunity to start earning from tech without a CS degree. There's no path forward that doesn't include AI coding tools. None. You have one window. Right now. This week. ↓ Here's your action plan for the next 7 days: Day 1: Watch the full video. Install Claude Code. Set up dependencies. Day 2: Learn basic usage. Try 5 different commands. Day 3: Write your first planning prompt. Build a small project. Day 4: Set up Claude. MD. Configure your memory file. Day 5: Master modes and shortcuts. Build a second project faster. Day 6: Set up Git integration. Automate with tasks. Day 7: Build something real. A tool, an app, a website. Ship it. 7 days. One tool. One completely different skill set. One completely different income potential. Or 7 more days of scrolling Twitter watching other people build things while you "plan to start." Your call. ↓ This is the most important video you'll watch this year. 33 minutes. Complete Claude Code mastery. From zero to building real projects. Save this post. Come back to it every single day this week. Check off each section as you complete it. Follow Himanshu Kumar for daily Claude Code breakdowns, advanced tutorials, and the exact workflows that are turning beginners into $10K/month builders. The only thing between you and $10K/month with Claude Code is this video and 7 days. Don't waste them. You Must Follow me Himanshu Kumar, so i can send you DM.

Himanshu Kumar

101,105 görüntüleme • 3 ay önce

東京を拠点に活動するプロデューサーであり、日本アンビエント界の新星TOMC TOMC ﾄﾑｼｰによる都市をテーマとした最新アルバム『Shared Senses』が、Kankyō Recordsの香りと音のシリーズ【Incense Sound】から登場。現時点での彼の最高傑作と言っても過言ではない、美しく洗練された仕上がり。この世界観を香りで表現したのは、DJや植物療法などで活動するかたわら、Kankyō Recordsのスタッフとして新たに加わったGRRRDENことMarina Gokan。都会的で透明感のある繊細な香りをお楽しみいただけます。 先行曲として[Crowded Streets, Empty Bars]と[Madoisen]がBandcamp、各種配信サービスで配信中。アルバムは10月9日発売予定。 Design & Video by Yudai Osawa @OsawaYudai [作品解説] 東京の生活とカール・ユングを結びつけ、全曲4分33秒で纏められた2022年作『Music for the Ninth Silence』、1980年代の東京をモチーフにした如月小春の代表的戯曲(リブート版)のサウンドトラック作品である2023年作『MORAL』と、東京を拠点に活動するTOMCはキャリアを通じて、都市および都市生活者にとってのアンビエントの在り方を模索し続けてきた。『Shared Senses』は、そうした彼の試みが結実した作品である。 無数の人々が行き交い、さまざまな構成要素に取り囲まれ、それぞれの生活のなかで小さなドラマが生まれ続ける都会の生活。本作には、そういった都市の生活に漂うたくさんの抽象的な声を具体化する試みが数多く存在している。例えば、A・B面それぞれに配された2曲の大作、「Shared Senses」「True Blue Parade」で、TOMCは複数の異なるBPMのトラックが一定の周期のもとで絡み合う「ポリBPM」を採用。都市の生活の中にある、すれ違いと出会いの切なさ、美しさを丁寧に掬い取ってみせる。また、「En」、および「Crowded Streets, Empty Bars」の間奏では、TOMCがフリーソフトAudacityで編み出した独自の立体音響が使用され、都市にある手触りが浮かび上がってくるかのようだ。加えて、東京の西新宿〜笹塚という実在のエリアをモチーフにした「Opera City」も収録。ここでは現実と想像がクロスフェードしていく。 Side Aにはとりわけ都市に生きる人々の心の機微を描いた楽曲が並んでいると言ってもいいだろう。特に「Madoisen」は、日本の多くの小学校で放送されるドヴォルザーク／フィッシャーの歌曲「Goin' Home (遠き山に日は落ちて)」から着想を得たそうで、本作にあるTOMCの優しい眼差しや手つきを象徴する一曲となっている。 一方でSide Bには、都市の景観を俯瞰的な視点で捉えたような、映画的な楽曲が並ぶ。The Blue Nileの歌詞の一節から着想を得たという「Crowded Streets, Empty Bars」のドラマチックな展開はその最たる例だ。そして、本作はSide Aの1曲目「En」のリプライズ的楽曲「En II」で、都市のなかで繰り広げられる人々の生活・営みを賛美するように締め括られる。 Kankyō Recordsでは都市のなかで人々の感性がふと通い合う瞬間や、そうした瞬間への人々の願い・希望を形にしたコンセプチュアルな作品となった本作に、東京でDJや植物療法、ローチョコなどの活動を行うGRRRDENによる特製のエッセンシャルオイルも併せて販売。作品が持つ透明感と都市をイメージし調香されたすっきりとした香りと共に、この都市型アンビエントの新たなマイルストーンと呼ぶべき『Shared Senses』を楽しんでほしい。[高久大輝]高久大輝 / Daiki Takaku TOMC, a Tokyo-based artist, has consistently explored the role of ambient music in the context of urban life throughout his career. In his 2022 work Music for the Ninth Silence, which connects life in Tokyo with Carl Jung's theories and features tracks each timed at 4 minutes and 33 seconds, and in his 2023 soundtrack MORAL, based on the iconic play by Koharu Kisaragi that reimagines 1980s Tokyo, TOMC has continued to delve into this relationship. His latest work, Shared Senses, is the culmination of these efforts. Urban life is characterized by countless people crossing paths, surrounded by various elements, where small dramas unfold within each person's daily existence. This album attempts to give form to the many abstract voices that float through city life. For example, in the two major tracks that define each side of the album-Shared Senses and True Blue Parade-TOMC employs a "poly-BPM" technique, where multiple tracks with differing tempos intertwine in cycles. This technique captures the subtle beauty and poignancy of fleeting encounters and missed connections in urban life. Furthermore, the interludes of En and Crowded Streets, Empty Bars feature a unique three-dimensional sound design, crafted using the free software Audacity, which seems to bring the textures of the city to life. The album also includes Opera City, a track inspired by the real-life Tokyo area spanning from Nishi-Shinjuku to Sasazuka, where reality and imagination crossfade seamlessly. Side A of the album, in particular, portrays the delicate emotions of people living in the city. Madoisen stands out as a track that draws inspiration from the song Goin' Home by Dvořák/Fischer, a familiar piece often played in Japanese elementary schools. This track, in its warmth and tenderness, encapsulates TOMC's gentle approach and perspective throughout the album. On the other hand, Side B takes on a more cinematic view of the cityscape. Crowded Streets, Empty Bars, inspired by a line from the lyrics of The Blue Nile, offers a prime example of this dramatic shift. The album concludes with En II, a reprise of the opening track En, which celebrates the lives and activities unfolding within the urban landscape. In conjunction with the release of Shared Senses, Kankyō Records has partnered with GRRRDEN, a Tokyo-based DJ and practitioner of plant therapy and raw chocolate, to offer a special essential oil blend alongside the album. This scent, designed to evoke the transparency and clarity of the album and its urban theme, provides a fresh accompaniment to what can be considered a new milestone in urban ambient music.[Daiki Takaku]
0:26

東京を拠点に活動するプロデューサーであり、日本アンビエント界の新星TOMC TOMC ﾄﾑｼｰによる都市をテーマとした最新アルバム『Shared Senses』が、Kankyō Recordsの香りと音のシリーズ【Incense Sound】から登場。現時点での彼の最高傑作と言っても過言ではない、美しく洗練された仕上がり。この世界観を香りで表現したのは、DJや植物療法などで活動するかたわら、Kankyō Recordsのスタッフとして新たに加わったGRRRDENことMarina Gokan。都会的で透明感のある繊細な香りをお楽しみいただけます。 先行曲として[Crowded Streets, Empty Bars]と[Madoisen]がBandcamp、各種配信サービスで配信中。アルバムは10月9日発売予定。 Design & Video by Yudai Osawa @OsawaYudai [作品解説] 東京の生活とカール・ユングを結びつけ、全曲4分33秒で纏められた2022年作『Music for the Ninth Silence』、1980年代の東京をモチーフにした如月小春の代表的戯曲(リブート版)のサウンドトラック作品である2023年作『MORAL』と、東京を拠点に活動するTOMCはキャリアを通じて、都市および都市生活者にとってのアンビエントの在り方を模索し続けてきた。『Shared Senses』は、そうした彼の試みが結実した作品である。 無数の人々が行き交い、さまざまな構成要素に取り囲まれ、それぞれの生活のなかで小さなドラマが生まれ続ける都会の生活。本作には、そういった都市の生活に漂うたくさんの抽象的な声を具体化する試みが数多く存在している。例えば、A・B面それぞれに配された2曲の大作、「Shared Senses」「True Blue Parade」で、TOMCは複数の異なるBPMのトラックが一定の周期のもとで絡み合う「ポリBPM」を採用。都市の生活の中にある、すれ違いと出会いの切なさ、美しさを丁寧に掬い取ってみせる。また、「En」、および「Crowded Streets, Empty Bars」の間奏では、TOMCがフリーソフトAudacityで編み出した独自の立体音響が使用され、都市にある手触りが浮かび上がってくるかのようだ。加えて、東京の西新宿〜笹塚という実在のエリアをモチーフにした「Opera City」も収録。ここでは現実と想像がクロスフェードしていく。 Side Aにはとりわけ都市に生きる人々の心の機微を描いた楽曲が並んでいると言ってもいいだろう。特に「Madoisen」は、日本の多くの小学校で放送されるドヴォルザーク／フィッシャーの歌曲「Goin' Home (遠き山に日は落ちて)」から着想を得たそうで、本作にあるTOMCの優しい眼差しや手つきを象徴する一曲となっている。 一方でSide Bには、都市の景観を俯瞰的な視点で捉えたような、映画的な楽曲が並ぶ。The Blue Nileの歌詞の一節から着想を得たという「Crowded Streets, Empty Bars」のドラマチックな展開はその最たる例だ。そして、本作はSide Aの1曲目「En」のリプライズ的楽曲「En II」で、都市のなかで繰り広げられる人々の生活・営みを賛美するように締め括られる。 Kankyō Recordsでは都市のなかで人々の感性がふと通い合う瞬間や、そうした瞬間への人々の願い・希望を形にしたコンセプチュアルな作品となった本作に、東京でDJや植物療法、ローチョコなどの活動を行うGRRRDENによる特製のエッセンシャルオイルも併せて販売。作品が持つ透明感と都市をイメージし調香されたすっきりとした香りと共に、この都市型アンビエントの新たなマイルストーンと呼ぶべき『Shared Senses』を楽しんでほしい。[高久大輝]高久大輝 / Daiki Takaku TOMC, a Tokyo-based artist, has consistently explored the role of ambient music in the context of urban life throughout his career. In his 2022 work Music for the Ninth Silence, which connects life in Tokyo with Carl Jung's theories and features tracks each timed at 4 minutes and 33 seconds, and in his 2023 soundtrack MORAL, based on the iconic play by Koharu Kisaragi that reimagines 1980s Tokyo, TOMC has continued to delve into this relationship. His latest work, Shared Senses, is the culmination of these efforts. Urban life is characterized by countless people crossing paths, surrounded by various elements, where small dramas unfold within each person's daily existence. This album attempts to give form to the many abstract voices that float through city life. For example, in the two major tracks that define each side of the album-Shared Senses and True Blue Parade-TOMC employs a "poly-BPM" technique, where multiple tracks with differing tempos intertwine in cycles. This technique captures the subtle beauty and poignancy of fleeting encounters and missed connections in urban life. Furthermore, the interludes of En and Crowded Streets, Empty Bars feature a unique three-dimensional sound design, crafted using the free software Audacity, which seems to bring the textures of the city to life. The album also includes Opera City, a track inspired by the real-life Tokyo area spanning from Nishi-Shinjuku to Sasazuka, where reality and imagination crossfade seamlessly. Side A of the album, in particular, portrays the delicate emotions of people living in the city. Madoisen stands out as a track that draws inspiration from the song Goin' Home by Dvořák/Fischer, a familiar piece often played in Japanese elementary schools. This track, in its warmth and tenderness, encapsulates TOMC's gentle approach and perspective throughout the album. On the other hand, Side B takes on a more cinematic view of the cityscape. Crowded Streets, Empty Bars, inspired by a line from the lyrics of The Blue Nile, offers a prime example of this dramatic shift. The album concludes with En II, a reprise of the opening track En, which celebrates the lives and activities unfolding within the urban landscape. In conjunction with the release of Shared Senses, Kankyō Records has partnered with GRRRDEN, a Tokyo-based DJ and practitioner of plant therapy and raw chocolate, to offer a special essential oil blend alongside the album. This scent, designed to evoke the transparency and clarity of the album and its urban theme, provides a fresh accompaniment to what can be considered a new milestone in urban ambient music.[Daiki Takaku]

Kankyōrecords

42,317 görüntüleme • 1 yıl önce

Meet My AI Ears. A lot of folks ask me how I capture ASMR video and audio for training of AI? I always use Binaural 3D audio and have for decades in different forms. But how? A Brief History of Binaural Recording Binaural recording, the foundation of 3D audio, dates back to 1881 when French inventor Clément Ader created the first system using multiple telephone transmitters at the Paris Opera to transmit stereo sound to listeners, simulating spatial presence. By the 1920s, patents like W. Bartlett Jones’ 1927 filing advanced devices for capturing and reproducing “binaural” signals. The 1930s saw Alan Blumlein’s work on stereophonic sound, which he termed “binaural,” laying groundwork for modern stereo. Commercial milestones hit in the 1950s with binaural records from labels like Cook Laboratories and the first binaural reel-to-reel tapes. A resurgence came in the 1970s with Neumann’s KU-80 dummy head, the first commercial binaural system. Today, it’s integral to VR, ASMR, and immersive media. The Technology of Binaural 3D Audio At its core, binaural recording mimics human hearing by using two microphones placed in ear-shaped molds or a dummy head, separated like human ears (typically 14-18 cm apart). This captures spatial cues: interaural time differences (ITD) for sound arrival timing, interaural level differences (ILD) for volume variations, and head-related transfer functions (HRTF) that account for how the head, torso, and pinnae filter sounds. The result? A 3D soundscape that tricks the brain into perceiving direction, distance, and elevation when played back via headphones—no speakers needed for immersion. Advanced setups use omnidirectional capsules (e.g., DPA 4060) for high-fidelity capture, often in silicone ears to replicate natural diffraction. I use the 3DIO Microphones today but I would cover a dummy head in texture material and place two stereo (4 channels) microphones in each ear. I would then mix down the resulting signals into stereo. The 3DIO series features dual omnidirectional capsules in realistic silicone ear molds, spaced 14 cm apart for compact, accurate 3D capture based on over 13 years of research into human hearing. Models like the Free Space Pro II use premium DPA 4060 CORE capsules for ultra-low noise and high sensitivity, delivering stereo output ideal for immersive applications like game audio. Today just about any ASMR producer uses these. But I use them to capture, curate and archive sound and video we will lose or just about lost for AI training in a way no model or AI company is doing today. I am duplicating the human 3D binaural audio experience and memory. Below is a crude demonstration. If you can listen in headphones. Or turn your phone sideways to feel the audio space. I’ll have a far more professional demo soon to show the real power of 3D audio. (Oh that music is a MIDI player that uses disks to play).
0:35

Meet My AI Ears. A lot of folks ask me how I capture ASMR video and audio for training of AI? I always use Binaural 3D audio and have for decades in different forms. But how? A Brief History of Binaural Recording Binaural recording, the foundation of 3D audio, dates back to 1881 when French inventor Clément Ader created the first system using multiple telephone transmitters at the Paris Opera to transmit stereo sound to listeners, simulating spatial presence. By the 1920s, patents like W. Bartlett Jones’ 1927 filing advanced devices for capturing and reproducing “binaural” signals. The 1930s saw Alan Blumlein’s work on stereophonic sound, which he termed “binaural,” laying groundwork for modern stereo. Commercial milestones hit in the 1950s with binaural records from labels like Cook Laboratories and the first binaural reel-to-reel tapes. A resurgence came in the 1970s with Neumann’s KU-80 dummy head, the first commercial binaural system. Today, it’s integral to VR, ASMR, and immersive media. The Technology of Binaural 3D Audio At its core, binaural recording mimics human hearing by using two microphones placed in ear-shaped molds or a dummy head, separated like human ears (typically 14-18 cm apart). This captures spatial cues: interaural time differences (ITD) for sound arrival timing, interaural level differences (ILD) for volume variations, and head-related transfer functions (HRTF) that account for how the head, torso, and pinnae filter sounds. The result? A 3D soundscape that tricks the brain into perceiving direction, distance, and elevation when played back via headphones—no speakers needed for immersion. Advanced setups use omnidirectional capsules (e.g., DPA 4060) for high-fidelity capture, often in silicone ears to replicate natural diffraction. I use the 3DIO Microphones today but I would cover a dummy head in texture material and place two stereo (4 channels) microphones in each ear. I would then mix down the resulting signals into stereo. The 3DIO series features dual omnidirectional capsules in realistic silicone ear molds, spaced 14 cm apart for compact, accurate 3D capture based on over 13 years of research into human hearing. Models like the Free Space Pro II use premium DPA 4060 CORE capsules for ultra-low noise and high sensitivity, delivering stereo output ideal for immersive applications like game audio. Today just about any ASMR producer uses these. But I use them to capture, curate and archive sound and video we will lose or just about lost for AI training in a way no model or AI company is doing today. I am duplicating the human 3D binaural audio experience and memory. Below is a crude demonstration. If you can listen in headphones. Or turn your phone sideways to feel the audio space. I’ll have a far more professional demo soon to show the real power of 3D audio. (Oh that music is a MIDI player that uses disks to play).

Brian Roemmele

30,800 görüntüleme • 6 ay önce

週末のんびり (2/4) | 寧寧の運動時間がわんぱく子豚に邪魔される — 集中できない TL;DR 雨の日、寧寧はお家で軽いエクササイズをしようと思っていたのに…… 目を覚ました子ブタがまさかの“おじゃまモード”に突入。 まずは彼女の腕にすり寄ってチュッと甘えて、 そのまま背中によじ登ってきちゃった 昨日は窓辺で静かに本を読んでいた時、小豚は寧寧の膝の上で穏やかに眠っていました。今日は雨の午後、寧寧は軽く体を動かそうと思いました。 彼女は快適な部屋着に着替え、畳の上に手をついて、プランクの姿勢を始めました。雨の音が窓を叩き続け、室内の光は柔らかく穏やかです。彼女はこれが平穏な運動時間になると思っていました——しかし隣にいた小さな子豚が突然目を開けたのです。 子豚はまず好奇心いっぱいに近づき、ピンク色の小さな鼻で彼女の腕を優しくつつきました。「何してるの？」とでも言っているかのように。寧寧が顔を下げて見つめると、思わず微笑んでしまいました。「おはよう、小さな子。起きたの？」と優しく声をかけます。でも子豚はさらに踏み込んで、身体全体を寄せてきて、鼻や口で彼女の腕や肩を優しく擦り始めました。「くすぐったいよ……」と笑いながら言いながらも、寧寧は動作を止めませんでした。 彼女が集中して姿勢を維持していると、子豚が突然興奮して飛び上がり、前脚を彼女の背中に乗せ、続いて身体全体をよじ登ってきました！寧寧は一瞬固まって、背中に立っている子豚の方を振り返りました。子豚は胸を張り、まるで小さな勝利者のようにそこに立ち、尻尾を優しく振っています。光景は滑稽でありながら、どこか心温まるものでした——優雅な女性が運動をしようとしているのに、ピンクの子豚が誇らしげにその背中に立っている。まるで「私も一緒にやる！」と言っているかのように。 ============== Weekend Leisure (2/4) | Nene’s Workout Interrupted by a Mischievous Piglet — Hard to Focus TL;DR Nene tries to do a simple home workout on a rainy day, but the little piglet wakes up and starts “interfering” — first nuzzling her arm, then climbing onto her back during plank. This is Chapter 2 of the “Weekend Leisure” series, showing the most real and healing daily interaction between Nene and her piglet. Yesterday, while quietly reading by the window, the piglet slept peacefully on her lap. Today, Nene wanted to do some light home exercise during the rainy afternoon. She changed into comfortable homewear, got down on the tatami, placed her hands on the floor, and started holding a plank position. The sound of rain continued tapping against the window, and the indoor lighting was soft and calm. She thought this would be a peaceful workout — until the little piglet beside her suddenly opened its eyes. It first curiously came closer and gently nudged her arm with its pink nose, as if asking, “What are you doing?” Ningning looked down and couldn’t help but smile, softly saying, “Hey there, little one. You’re awake?” But the piglet went further — it leaned its whole body against her and began gently rubbing its nose and mouth against her arm and shoulder. “That tickles…” she laughed while speaking, yet didn’t stop her movement. Just as she was focused on maintaining the pose, the piglet suddenly got excited and jumped up. Its front legs landed on her back, and then its entire body climbed on top! Nene froze for a second and turned to look at the piglet now standing proudly on her back. Its tail wagged gently, looking like a little champion who had just conquered a mountain. The scene was both absurd and heartwarming — an elegant girl trying to exercise, while a pink piglet stood triumphantly on her back, as if declaring, “I’m joining too!” ===Check the full prompt and story in comment=== Please tap the post😁 #AIart #Sunday
0:29

週末のんびり (2/4) | 寧寧の運動時間がわんぱく子豚に邪魔される — 集中できない TL;DR 雨の日、寧寧はお家で軽いエクササイズをしようと思っていたのに…… 目を覚ました子ブタがまさかの“おじゃまモード”に突入。 まずは彼女の腕にすり寄ってチュッと甘えて、 そのまま背中によじ登ってきちゃった 昨日は窓辺で静かに本を読んでいた時、小豚は寧寧の膝の上で穏やかに眠っていました。今日は雨の午後、寧寧は軽く体を動かそうと思いました。 彼女は快適な部屋着に着替え、畳の上に手をついて、プランクの姿勢を始めました。雨の音が窓を叩き続け、室内の光は柔らかく穏やかです。彼女はこれが平穏な運動時間になると思っていました——しかし隣にいた小さな子豚が突然目を開けたのです。 子豚はまず好奇心いっぱいに近づき、ピンク色の小さな鼻で彼女の腕を優しくつつきました。「何してるの？」とでも言っているかのように。寧寧が顔を下げて見つめると、思わず微笑んでしまいました。「おはよう、小さな子。起きたの？」と優しく声をかけます。でも子豚はさらに踏み込んで、身体全体を寄せてきて、鼻や口で彼女の腕や肩を優しく擦り始めました。「くすぐったいよ……」と笑いながら言いながらも、寧寧は動作を止めませんでした。 彼女が集中して姿勢を維持していると、子豚が突然興奮して飛び上がり、前脚を彼女の背中に乗せ、続いて身体全体をよじ登ってきました！寧寧は一瞬固まって、背中に立っている子豚の方を振り返りました。子豚は胸を張り、まるで小さな勝利者のようにそこに立ち、尻尾を優しく振っています。光景は滑稽でありながら、どこか心温まるものでした——優雅な女性が運動をしようとしているのに、ピンクの子豚が誇らしげにその背中に立っている。まるで「私も一緒にやる！」と言っているかのように。 ============== Weekend Leisure (2/4) | Nene’s Workout Interrupted by a Mischievous Piglet — Hard to Focus TL;DR Nene tries to do a simple home workout on a rainy day, but the little piglet wakes up and starts “interfering” — first nuzzling her arm, then climbing onto her back during plank. This is Chapter 2 of the “Weekend Leisure” series, showing the most real and healing daily interaction between Nene and her piglet. Yesterday, while quietly reading by the window, the piglet slept peacefully on her lap. Today, Nene wanted to do some light home exercise during the rainy afternoon. She changed into comfortable homewear, got down on the tatami, placed her hands on the floor, and started holding a plank position. The sound of rain continued tapping against the window, and the indoor lighting was soft and calm. She thought this would be a peaceful workout — until the little piglet beside her suddenly opened its eyes. It first curiously came closer and gently nudged her arm with its pink nose, as if asking, “What are you doing?” Ningning looked down and couldn’t help but smile, softly saying, “Hey there, little one. You’re awake?” But the piglet went further — it leaned its whole body against her and began gently rubbing its nose and mouth against her arm and shoulder. “That tickles…” she laughed while speaking, yet didn’t stop her movement. Just as she was focused on maintaining the pose, the piglet suddenly got excited and jumped up. Its front legs landed on her back, and then its entire body climbed on top! Nene froze for a second and turned to look at the piglet now standing proudly on her back. Its tail wagged gently, looking like a little champion who had just conquered a mountain. The scene was both absurd and heartwarming — an elegant girl trying to exercise, while a pink piglet stood triumphantly on her back, as if declaring, “I’m joining too!” ===Check the full prompt and story in comment=== Please tap the post😁 #AIart #Sunday

Peter Lam

11,199 görüntüleme • 1 ay önce

ありがとう。 あなたのクィアの仲間達にも、ありがとうとお伝えください。 日本人は単一的な民族で、平均的な芸術やモノを好みます。もちろんいい部分もありますが、世界から見た場合には、少しガラパゴスな思考性を持ち、単一にとどまらない考えや、新たなクリエイティブを排除しようとする性質も持ちます。 芸術だけでなく、あらゆるものが単一化していて、あなたはそれに驚く事があると思います。 "クィア・ベイティング"と言う言葉の意味や、人々の価値観にもとまどうと思います。 その原因の元をたどれば、日本経済やテクノロジーが一定期間、自国のみで発展してしまったからだと僕は考えています。 でも、今は靴ヒモをしめなおす時が来ています。 僕には「自分らしさ」が当たり前にあっていい時代のアシオトが聞こえます。 僕の作品があなたにとって「自分らしさ」の 居場所になっていて、幸せです。 僕も少しづつですが「自分らしく」あります。 あなたの友達にも、ありがとうとお伝えください。 Individuality — “自分らしく” BL作品 Thank you. The Japanese people are often seen as a homogeneous nation, favoring average forms of art and everyday things. Of course, there are positive aspects to this, but from a global perspective, there is also a somewhat insular way of thinking—one that tends to reject ideas that go beyond uniformity or challenge new creativity. Not only in art, but in many aspects of life, things are often made uniform. I believe this may sometimes surprise you. You may also feel puzzled by certain values, such as the meaning of the word “queer-baiting” and how people perceive it. Tracing it back, I believe the root lies in the period when Japan’s economy and technology developed largely in isolation, relying only on itself. But now, it’s time to tighten our shoelaces once again. I can already hear the footsteps of a new era—one where individuality, or being “your true self,” is something completely natural. If my work has become a place where your “true self” feels at home, that makes me happy. I, too, am learning little by little to live more in line with my own true self. And please also say thank you to your friends for me. Individuality — “自分らしく” Music Video
1:02

ありがとう。 あなたのクィアの仲間達にも、ありがとうとお伝えください。 日本人は単一的な民族で、平均的な芸術やモノを好みます。もちろんいい部分もありますが、世界から見た場合には、少しガラパゴスな思考性を持ち、単一にとどまらない考えや、新たなクリエイティブを排除しようとする性質も持ちます。 芸術だけでなく、あらゆるものが単一化していて、あなたはそれに驚く事があると思います。 "クィア・ベイティング"と言う言葉の意味や、人々の価値観にもとまどうと思います。 その原因の元をたどれば、日本経済やテクノロジーが一定期間、自国のみで発展してしまったからだと僕は考えています。 でも、今は靴ヒモをしめなおす時が来ています。 僕には「自分らしさ」が当たり前にあっていい時代のアシオトが聞こえます。 僕の作品があなたにとって「自分らしさ」の 居場所になっていて、幸せです。 僕も少しづつですが「自分らしく」あります。 あなたの友達にも、ありがとうとお伝えください。 Individuality — “自分らしく” BL作品 Thank you. The Japanese people are often seen as a homogeneous nation, favoring average forms of art and everyday things. Of course, there are positive aspects to this, but from a global perspective, there is also a somewhat insular way of thinking—one that tends to reject ideas that go beyond uniformity or challenge new creativity. Not only in art, but in many aspects of life, things are often made uniform. I believe this may sometimes surprise you. You may also feel puzzled by certain values, such as the meaning of the word “queer-baiting” and how people perceive it. Tracing it back, I believe the root lies in the period when Japan’s economy and technology developed largely in isolation, relying only on itself. But now, it’s time to tighten our shoelaces once again. I can already hear the footsteps of a new era—one where individuality, or being “your true self,” is something completely natural. If my work has become a place where your “true self” feels at home, that makes me happy. I, too, am learning little by little to live more in line with my own true self. And please also say thank you to your friends for me. Individuality — “自分らしく” Music Video

SHIROSE（WHITE JAM）

185,716 görüntüleme • 10 ay önce

Universities teach many erroneous models. One example of a misleading teaching is the Newtonian model of the prism. A man named Johann Goethe corrected and complimented Newton's model about 100 years after Newton. It is not the same light passing through the prism and distributing. It is a brand-new light with each beam of color. The primary light hitting the prism is extinguished by the electrons making up the glass of the prism itself. Those same electrons re-emit a brand new light from each angle. That process happens at the rate of c. Serving the illusion that the original white light came it... separated and exited to continue on. Most people rely on outdated text books or the Pink Floyd album cover "Dark Side of the Moon" to get their information about light and color and prisms. The depictions of light "splitting" and "bending" through a prism based on their color is false. (See first comments for attached images and substantiation) I filmed these videos playing around with prisms, lasers, magnifying glasses, mirrors, slits, and colored filters. I've gained my own perspectives on light and color over the years from real world, hands-on experimentation and observation. Most people have never held a real glass prism their own hands and done the tests to see for themselves. 2 prisms for $10 Harmonics of Light and Sound: This guy said his units were confiscated by the FBI and he was threatened not to pursue manufacturing them. The unit is simply a light with a magnifying glass and colored filters to isolate the light. Like burning an ant with a focal point... but with a specific color. The lens can spin and create a stroboscopic effect in an isolated band. The inventor claimed it healed stuff. Dinshah Spectro-Chrome Machine - Tour and Explanation Magenta monochromatic ray of shadow - Pehr Sahlstrom: Color and Physics, Newton versus Goethe - Pehr Sahlstrom: Thomas Joseph Brown Color Theory: Clay Taylor Color Theory: Testing the "Rightness" of relativity. The impossibility of proving something through experiments. Laser and Mirror observation: It's never the same light. Re-emission Example: I put this interactive page together going back and forth with ChatGPT to code using Javascript. Here is a video playing with the slide controls to show 3 different sinewaves (3 different lights/emissions). The packets are ALWAYS in phase from medium to medium. The frequency shifts BECAUSE the velocity of light shifts. NOT a Doppler shift of "the same light" distorting within the same frame of reference. It's a brand new light at each point. The incoming light is a different frame of reference. All the light you ever see is the re-emitted light from the electrons making up yourself. Propagation and Re-Emission of Light: Dr. Edward Dowdye Slides - LOTS of math and context. E.H. Dowdye, Can Stars BEND LIGHT? General Relativity and Gravity with Dr. Edward Dowdye Challenges to Gravitational Lensing and More: 71 Part Video Series (Each vid is 1 min - 1 and a hafl min) The Rebirth of Classical Physics - Time, Light & Gravity Classical Physics vs Relativity - History, Examples and Alternatives: Illusions of Relativity: Space-Time vs Real-Time The Rebirth of Classical Physics: Time, Light & Gravity - Article Packed with Info & Links Thought Experiment for Light and Absolute Time. (This scenario got me banned from talking on a Podcast.) "Too off the rails."
22:27

Universities teach many erroneous models. One example of a misleading teaching is the Newtonian model of the prism. A man named Johann Goethe corrected and complimented Newton's model about 100 years after Newton. It is not the same light passing through the prism and distributing. It is a brand-new light with each beam of color. The primary light hitting the prism is extinguished by the electrons making up the glass of the prism itself. Those same electrons re-emit a brand new light from each angle. That process happens at the rate of c. Serving the illusion that the original white light came it... separated and exited to continue on. Most people rely on outdated text books or the Pink Floyd album cover "Dark Side of the Moon" to get their information about light and color and prisms. The depictions of light "splitting" and "bending" through a prism based on their color is false. (See first comments for attached images and substantiation) I filmed these videos playing around with prisms, lasers, magnifying glasses, mirrors, slits, and colored filters. I've gained my own perspectives on light and color over the years from real world, hands-on experimentation and observation. Most people have never held a real glass prism their own hands and done the tests to see for themselves. 2 prisms for $10 Harmonics of Light and Sound: This guy said his units were confiscated by the FBI and he was threatened not to pursue manufacturing them. The unit is simply a light with a magnifying glass and colored filters to isolate the light. Like burning an ant with a focal point... but with a specific color. The lens can spin and create a stroboscopic effect in an isolated band. The inventor claimed it healed stuff. Dinshah Spectro-Chrome Machine - Tour and Explanation Magenta monochromatic ray of shadow - Pehr Sahlstrom: Color and Physics, Newton versus Goethe - Pehr Sahlstrom: Thomas Joseph Brown Color Theory: Clay Taylor Color Theory: Testing the "Rightness" of relativity. The impossibility of proving something through experiments. Laser and Mirror observation: It's never the same light. Re-emission Example: I put this interactive page together going back and forth with ChatGPT to code using Javascript. Here is a video playing with the slide controls to show 3 different sinewaves (3 different lights/emissions). The packets are ALWAYS in phase from medium to medium. The frequency shifts BECAUSE the velocity of light shifts. NOT a Doppler shift of "the same light" distorting within the same frame of reference. It's a brand new light at each point. The incoming light is a different frame of reference. All the light you ever see is the re-emitted light from the electrons making up yourself. Propagation and Re-Emission of Light: Dr. Edward Dowdye Slides - LOTS of math and context. E.H. Dowdye, Can Stars BEND LIGHT? General Relativity and Gravity with Dr. Edward Dowdye Challenges to Gravitational Lensing and More: 71 Part Video Series (Each vid is 1 min - 1 and a hafl min) The Rebirth of Classical Physics - Time, Light & Gravity Classical Physics vs Relativity - History, Examples and Alternatives: Illusions of Relativity: Space-Time vs Real-Time The Rebirth of Classical Physics: Time, Light & Gravity - Article Packed with Info & Links Thought Experiment for Light and Absolute Time. (This scenario got me banned from talking on a Podcast.) "Too off the rails."

TheRealVerbz (Jason Verbelli)

44,361 görüntüleme • 1 yıl önce