|
42594
|
CMHP (Clean Minimalistic Home Page) by @Tuguldur | CMHP (Clean Minimalistic Home Page) by @Tuguldur | Stardance...
|
Tuguldur
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: CMHP (Clean Minimalistic Home Page) by @Tug Title: CMHP (Clean Minimalistic Home Page) by @Tuguldur | Stardance...
|
1793865345.5174341
|
1794729345.5174341
|
|
56011
|
asd by @RespectableDot | Stardance
|
RespectableDot
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: asd by @RespectableDot | Stardance
|
1793865346.359065
|
1794729346.359065
|
|
56018
|
bob by @Bobfish6598 | Stardance
|
Bobfish6598
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: bob by @Bobfish6598 | Stardance
|
1793865350.7103517
|
1794729350.7103517
|
|
56019
|
bob by @Bobfish6598 | Stardance
|
Bobfish6598
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: bob by @Bobfish6598 | Stardance
|
1793865352.5179374
|
1794729352.5179374
|
|
39943
|
COSMOCRYPT VT-80 by @NITHIN | Stardance
|
NITHIN
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: COSMOCRYPT VT-80 by @NITHIN | Stardance
|
1793865355.4333534
|
1794729355.4333534
|
|
56027
|
Clock by @EhtishamCodes | Stardance
|
EhtishamCodes
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Clock by @EhtishamCodes | Stardance
|
1793865357.1489527
|
1794729357.1489527
|
|
56030
|
My own site! by @imraghav012 | Stardance
|
imraghav012
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @imraghav012 | Stardance
|
1793865360.131312
|
1794729360.131312
|
|
35563
|
PLEASE DELETE by @Lokpriyanth | Stardance
|
Lokpriyanth
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: PLEASE DELETE by @Lokpriyanth | Stardance
|
1793865363.0304294
|
1794729363.0304294
|
|
56036
|
Anims-simulation by @Freaked | Stardance
|
Freaked
|
0
|
2.71
|
0
|
[]
|
[{"post_id": 59105, "ts": "202 [{"post_id": 59105, "ts": "2026-08-31T18:51:10Z", "hours": 2.7089, "text": "#Devlog 1 : I am working of a cool 3D black hole simulator , it was really time taking but i finally got how my simulator will look and i am thinking of first making a net (space fabric) to show accuracy of black hole and its massive gravity i think i should use some cool animation to make it more attractive. what you guys think what will be best."}]...
|
Title: Anims-simulation by @Freaked | Stardance
D Title: Anims-simulation by @Freaked | Stardance
Devlogs:
#Devlog 1 : I am working of a cool 3D black hole simulator , it was really time taking but i finally got how my simulator will look and i am thinking of first making a net (space fabric) to show accuracy of black hole and its massive gravity i think i should use some cool animation to make it more attractive. what you guys think what will be best....
|
1793865364.7556484
|
1794729364.7556484
|
|
39060
|
PomodBros by @belbel | Stardance
|
belbel
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: PomodBros by @belbel | Stardance
|
1793865366.4671743
|
1794729366.4671743
|
|
4707
|
Ai by @AnantPrakash | Stardance
|
AnantPrakash
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Ai by @AnantPrakash | Stardance
|
1793865368.5492213
|
1794729368.5492213
|
|
36726
|
Demo#1 by @ritam | Stardance
|
ritam
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Demo#1 by @ritam | Stardance
|
1793865370.28479
|
1794729370.28479
|
|
44103
|
A website š¤©š by @nourzain160 | Stardance
|
nourzain160
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: A website š¤©š by @nourzain160 | Stardance
|
1793865371.9929492
|
1794729371.9929492
|
|
38690
|
Pipasso | An Auto Drawing Bot by @Dragon | Stardan Pipasso | An Auto Drawing Bot by @Dragon | Stardance...
|
Dragon
|
0
|
40.9
|
0
|
[]
|
[{"post_id": 48266, "ts": "202 [{"post_id": 48266, "ts": "2026-08-16T15:55:07Z", "hours": 1.8519, "text": "Devlog 23 The new paths looked good in code, but moving a real mouse along pixel steps can still look rough. I spent time checking that the automation engine could follow those close-together points safely. What I did Updated the mouse engine to expand longer point-to-point moves into safe drag steps. Checked pause, stop, and mouse-button release behaviour with continuous paths. Updated the draw-style controls and help text so Continuous is clearly the normal choice. Kept the live preview and placement ghost matched to the same processed mask. Current result Continuous paths are ready for real cursor automation. The output stays faithful to the source mask instead of drawing through empty areas."}, {"post_id": 48178, "ts": "2026-08-16T13:59:46Z", "hours": 2.0469, "text": "Devlog 22 So I was thinking: if every dark pixel is part of a little map, the cursor should be able to walk through that map without taking shortcuts through the white background. That became the new continuous drawing style. What I did Added a Continuous draw pattern and made it the default. Grouped ink pixels into connected regions. Used a depth-first walk to make long, pixel-adjacent pen paths. Let paths backtrack over already-drawn pixels instead of lifting the pen or crossing blank space. Kept larger connected shapes first so the drawing starts with the main details. Current result The bot can draw connected regions as unbroken, human-like strokes. There are no skipped scan lines in Continuous mode. The original fill patterns are still available for shading-style drawings."}, {"post_id": 46942, "ts": "2026-08-14T14:43:47Z", "hours": 1.6844, "text": "Devlog 21 I watched the bot draw and finally noticed why it looked a bit like a printer instead of a person: it was doing separate scan lines with spaces between them. It was technically drawing the right shapes, but the movement did not feel right. What I did Looked at how the fill paths were being created. Kept the older horizontal, vertical, and random scanline styles as optional faster modes. Planned a new default that would stay on real image pixels instead of jumping between rows. Current result I understood that the problem was the path algorithm, not the mouse speed. The next task was to make a proper continuous tracer."}, {"post_id": 46421, "ts": "2026-08-13T16:45:27Z", "hours": 1.9192, "text": "Devlog 20 The final part was testing with different pictures and fixing the little problems that only show up when you actually use the program. Then I wrote the README so future-me knows what all of this does. What I did Tested line-art, threshold, and colour-group paths with sample images. Checked placement, cancellation, stop behaviour, and cursor release. Added installation, usage, safety, and limitation notes to the README. Listed dependencies in requirements.txt . Current result A working AutoDraw desktop project with documented setup and safety guidance. Plenty of future ideas, but a complete usable version now."}, {"post_id": 45167, "ts": "2026-08-11T14:14:03Z", "hours": 1.5628, "text": "Devlog 19 I realised most people would double-click the app, not run commands. A console window popping up behind it made it feel unfinished. What I did Added main.pyw for no-console Windows launching. Guarded console output for environments without stdout/stderr. Checked the project can also be packaged with PyInstaller. Current result The project is closer to something a normal user can open directly."}, {"post_id": 44683, "ts": "2026-08-10T16:40:31Z", "hours": 1.7878, "text": "Devlog 18 By now it worked, but the controls felt scattered. I spent this session making it feel more like a small Windows utility than a school experiment. What I did Organised controls into Settings, Thresholding, and Action sections. Added labels for interval, click delay, luminance, and draw pattern. Improved the image and threshold previews. Current result The main workflow is easier to understand at a glance."}, {"post_id": 42588, "ts": "2026-08-07T12:32:51Z", "hours": 2.4092, "text": "Devlog 17 The bot canāt magically swap the pen colour in every app, so I made the program honest about that limitation instead of pretending it was solved. What I did Added automatic pauses between colour groups. Made an always-on-top colour notice with an RGB swatch. Added continue and stop controls for each layer. Current result Multi-colour mode guides the user through manual pen changes."}, {"post_id": 41977, "ts": "2026-08-06T14:48:48Z", "hours": 1.7783, "text": "Devlog 16 Then I wondered if it could do more than black lines. I experimented with grouping similar colours, even though it makes the workflow more complicated. What I did Added k-means colour clustering. Ordered groups from dark to light. Generated fill paths for each colour group. Current result The processing engine can split an image into separate colour layers."}, {"post_id": 41194, "ts": "2026-08-05T08:08:30Z", "hours": 1.5864, "text": "Devlog 15 I noticed some images looked better depending on how they were filled. That became a good excuse to add different drawing patterns. What I did Added horizontal scanline filling. Reused the same logic for vertical strokes. Added a random mode that shuffles and sometimes reverses strokes. Current result The user can choose how the drawing progresses without changing the final ink mask."}, {"post_id": 41172, "ts": "2026-08-05T06:32:42Z", "hours": 1.8778, "text": "Devlog 14 Drawing individual pixels was obviously not going to be practical. I changed the mask into longer strokes, one run of pixels at a time. What I did Found continuous runs of ink pixels in each scanline. Converted each run into one two-point stroke. Used zig-zag ordering on alternate rows to reduce travel. Added a fill-spacing setting. Current result Threshold drawings are much faster and smoother than pixel-by-pixel drawing. [!NOTE] The image shows how it used to draw and now how it draws, the drawing is still kind of wobbly, will keep adjusting till its flawless"}, {"post_id": 40841, "ts": "2026-08-04T16:59:46Z", "hours": 2.3481, "text": "Devlog 13 Edge detection looked cool, but it sometimes missed things or made weird extra details. I tried a simpler idea: draw only pixels within a brightness range. What I did Added min/max luminance settings. Created a black-and-white ink mask from the selected range. Made a live threshold preview in the GUI. Current result Users can choose which brightness levels become ink. The result is easier to tune for simple images."}, {"post_id": 39993, "ts": "2026-08-03T10:48:42Z", "hours": 1.81, "text": "Devlog 12 I wanted a way to know whether the drawing would land in the right place before the mouse started moving. So I made a little ghost version follow the cursor. What I did Captured a screenshot behind the placement overlay. Displayed a transparent processed-image preview under the cursor. Added an outlined bounding box to make the size easier to notice. Current result Placement is visual instead of a blind click."}, {"post_id": 38252, "ts": "2026-07-31T15:34:48Z", "hours": 1.7439, "text": "Devlog 11 At first I was typing coordinates, which was annoying and easy to get wrong. A click-to-place workflow felt much more natural. What I did Added a full-screen crosshair positioning window. Captured the next left-click as the drawingās top-left origin. Added Escape cancellation before drawing begins. Current result The user can point at a canvas and place the drawing directly."}, {"post_id": 37767, "ts": "2026-07-30T18:01:59Z", "hours": 1.6058, "text": "Devlog 10 I really did not want a bug to leave the mouse holding down forever. This session was mostly about making failure less stressful. What I did Added stop, pause, and resume state handling. Ensured the mouse button is released on completion, stop, or error. Enabled PyAutoGUIās corner fail-safe. Started wiring an Esc-key emergency stop. Current result The bot has multiple ways to stop safely. Pausing mid-stroke no longer risks a stuck drag."}, {"post_id": 37157, "ts": "2026-07-29T17:33:23Z", "hours": 3.7783, "text": "Devlog 08 and 09 Devlog 08 This was the slightly scary part: allowing the project to control the real cursor. I tested on a safe blank drawing area, with my hand ready to stop it. What I did Added PyAutoGUI mouse movement and mouse-down/mouse-up actions. Translated local canvas points into screen coordinates. Added adjustable movement, click, and gap delays. Current result A simple path can be drawn using real mouse input. Timing is configurable instead of hard-coded. Devlog 09 I clicked draw and the whole window froze while the mouse worked. It wasnāt technically broken, but it felt broken. That sent me down the threading rabbit hole. What I did Moved drawing work to a background thread. Added start, progress, and finished callbacks. Kept GUI actions on the interface side of the program. Current result The interface stays responsive while automation is running."}, {"post_id": 36845, "ts": "2026-07-29T05:06:14Z", "hours": 1.7694, "text": "Devlog 07 My first path order was basically random, and the cursor would bounce around like it had too much coffee. I made a simple nearest-neighbour ordering system to calm it down. What I did Measured distance between path ends. Ordered contours by the closest next path. Reversed paths when approaching their end was shorter. Current result The cursor should spend less time travelling between separate strokes. Line drawings feel more intentional."}, {"post_id": 35858, "ts": "2026-07-27T15:50:26Z", "hours": 1.9178, "text": "Devlog 06 Edges are still just pixels, though. I had to figure out how to make them into actual strokes that a mouse could follow without constantly clicking every single point. What I did Found contours from the edge image. Converted contours into lists of (x, y) points. Simplified overly detailed paths and ignored tiny unusable contours. Added PathGroup so related strokes can travel together. Patched some parts of image rendering issue mentioned in the 5th devlog , so it at least works. Current result The processor now produces drawable paths, not only a black-and-white image."}, {"post_id": 35536, "ts": "2026-07-27T01:16:32Z", "hours": 2.2169, "text": "Devlog 04 and 05 Devlog 04 I added an image preview, then noticed a problem: the original picture and the drawing area could have different shapes. A wide image was getting squished, which looked terrible. What I did Added a preview area to the interface. Resized images while keeping their aspect ratio. Letterboxed them on a white canvas so the processing area stays consistent. Current result Images fit the drawing canvas without stretching. The preview is much closer to what the bot will use. Devlog 05 So I was thinking that drawing every pixel would take forever. I tried edge detection instead, because an outline is often enough to recognise a picture. What I did Added OpenCV and converted images to grayscale. Used blur plus Canny edge detection to find visible outlines. Saved the generated edge image for previewing and debugging. Had a lot of problems with the back end when converting PNG / SVG Current result The app can turn an image into line-art data. Some rendering issues when using a PNG or a SVG I can see why some pictures work better than others. (1st Image is the gray scale version of , the 2nd image)"}, {"post_id": 34685, "ts": "2026-07-25T16:29:03Z", "hours": 1.9825, "text": "Devlog 03 The next question was, āCan it even open the kind of images I use?ā I used Pillow because it made loading and converting images much less scary. What I did Added a file picker for image files. Loaded images with Pillow and converted them to RGB. Put the image-loading work into image_processor.py instead of mixing it into the GUI. Current result Users can choose an image from their computer. The program has a separate place for image-related code."}, {"post_id": 34055, "ts": "2026-07-24T14:45:34Z", "hours": 1.7711, "text": "Devlog 02 I started with the least exciting but most reassuring thing: making an actual window appear. Seeing a blank app on screen made the project feel real. What I did Set up main.py to start the program. Created a basic Tkinter app shell. Added a title, a simple layout, and a place for image controls. Current result The app launches without needing a terminal-focused workflow. There is a foundation to build the interface onto."}, {"post_id": 33523, "ts": "2026-07-23T15:29:11Z", "hours": 1.4511, "text": "Devlog 01 ā The idea So I was thinking: what if I could give a program a picture and have it draw it with my mouse? It sounded simple at first, but then I realised the computer needs a list of tiny movements, not just an image. What I did Defined the goal: load an image, turn it into strokes, and reproduce them on screen. Chose Python because I already knew enough to experiment quickly. Picked Tkinter for the desktop window and wrote down the main parts the project would need. Current result A clear plan instead of just āmake a drawing bot.ā The first rough project folder and entry-point idea."}]...
|
Title: Pipasso | An Auto Drawing Bot by @Dragon | Title: Pipasso | An Auto Drawing Bot by @Dragon | Stardance
Devlogs:
Devlog 01 ā The idea So I was thinking: what if I could give a program a picture and have it draw it with my mouse? It sounded simple at first, but then I realised the computer needs a list of tiny movements, not just an image. What I did Defined the goal: load an image, turn it into strokes, and reproduce them on screen. Chose Python because I already knew enough to experiment quickly. Picked Tkinter for the desktop window and wrote down the main parts the project would need. Current result A clear plan instead of just āmake a drawing bot.ā The first rough project folder and entry-point idea.
Devlog 02 I started with the least exciting but most reassuring thing: making an actual window appear. Seeing a blank app on screen made the project feel real. What I did Set up main.py to start the program. Created a basic Tkinter app shell. Added a title, a simple layout, and a place for image controls. Current result The app launches without needing a terminal-focused workflow. There is a foundation to build the interface onto.
Devlog 03 The next question was, āCan it even open the kind of images I use?ā I used Pillow because it made loading and converting images much less scary. What I did Added a file picker for image files. Loaded images with Pillow and converted them to RGB. Put the image-loading work into image_processor.py instead of mixing it into the GUI. Current result Users can choose an image from their computer. The program has a separate place for image-related code.
Devlog 04 and 05 Devlog 04 I added an image preview, then noticed a problem: the original picture and the drawing area could have different shapes. A wide image was getting squished, which looked terrible. What I did Added a preview area to the interface. Resized images while keeping their aspect ratio. Letterboxed them on a white canvas so the processing area stays consistent. Current result Images fit the drawing canvas without stretching. The preview is much closer to what the bot will use. Devlog 05 So I was thinking that drawing every pixel would take forever. I tried edge detection instead, because an outline is often enough to recognise a picture. What I did Added OpenCV and converted images to grayscale. Used blur plus Canny edge detection to find visible outlines. Saved the generated edge image for previewing and debugging. Had a lot of problems with the back end when converting PNG / SVG Current result The app can turn an image into line-art data. Some rendering issues when using a PNG or a SVG I can see why some pictures work better than others. (1st Image is the gray scale version of , the 2nd image)
Devlog 06 Edges are still just pixels, though. I had to figure out how to make them into actual strokes that a mouse could follow without constantly clicking every single point. What I did Found contours from the edge image. Converted contours into lists of (x, y) points. Simplified overly detailed paths and ignored tiny unusable contours. Added PathGroup so related strokes can travel together. Patched some parts of image rendering issue mentioned in the 5th devlog , so it at least works. Current result The processor now produces drawable paths, not only a black-and-white image.
Devlog 07 My first path order was basically random, and the cursor would bounce around like it had too much coffee. I made a simple nearest-neighbour ordering system to calm it down. What I did Measured distance between path ends. Ordered contours by the closest next path. Reversed paths when approaching their end was shorter. Current result The cursor should spend less time travelling between separate strokes. Line drawings feel more intentional.
Devlog 08 and 09 Devlog 08 This was the slightly scary part: allowing the project to control the real cursor. I tested on a safe blank drawing area, with my hand ready to stop it. What I did Added PyAutoGUI mouse movement and mouse-down/mouse-up actions. Translated local canvas points into screen coordinates. Added adjustable movement, click, and gap delays. Current result A simple path can be drawn using real mouse input. Timing is configurable instead of hard-coded. Devlog 09 I clicked draw and the whole window froze while the mouse worked. It wasnāt technically broken, but it felt broken. That sent me down the threading rabbit hole. What I did Moved drawing work to a background thread. Added start, progress, and finished callbacks. Kept GUI actions on the interface side of the program. Current result The interface stays responsive while automation is running.
Devlog 10 I really did not want a bug to leave the mouse holding down forever. This session was mostly about making failure less stressful. What I did Added stop, pause, and resume state handling. Ensured the mouse button is released on completion, stop, or error. Enabled PyAutoGUIās corner fail-safe. Started wiring an Esc-key emergency stop. Current result The bot has multiple ways to stop safely. Pausing mid-stroke no longer risks a stuck drag.
Devlog 11 At first I was typing coordinates, which was annoying and easy to get wrong. A click-to-place workflow felt much more natural. What I did Added a full-screen crosshair positioning window. Captured the next left-click as the drawingās top-left origin. Added Escape cancellation before drawing begins. Current result The user can point at a canvas and place the drawing directly.
Devlog 12 I wanted a way to know whether the drawing would land in the right place before the mouse started moving. So I made a little ghost version follow the cursor. What I did Captured a screenshot behind the placement overlay. Displayed a transparent processed-image preview under the cursor. Added an outlined bounding box to make the size easier to notice. Current result Placement is visual instead of a blind click.
Devlog 13 Edge detection looked cool, but it sometimes missed things or made weird extra details. I tried a simpler idea: draw only pixels within a brightness range. What I did Added min/max luminance settings. Created a black-and-white ink mask from the selected range. Made a live threshold preview in the GUI. Current result Users can choose which brightness levels become ink. The result is easier to tune for simple images.
Devlog 14 Drawing individual pixels was obviously not going to be practical. I changed the mask into longer strokes, one run of pixels at a time. What I did Found continuous runs of ink pixels in each scanline. Converted each run into one two-point stroke. Used zig-zag ordering on alternate rows to reduce travel. Added a fill-spacing setting. Current result Threshold drawings are much faster and smoother than pixel-by-pixel drawing. [!NOTE] The image shows how it used to draw and now how it draws, the drawing is still kind of wobbly, will keep adjusting till its flawless
Devlog 15 I noticed some images looked better depending on how they were filled. That became a good excuse to add different drawing patterns. What I did Added horizontal scanline filling. Reused the same logic for vertical strokes. Added a random mode that shuffles and sometimes reverses strokes. Current result The user can choose how the drawing progresses without changing the final ink mask.
Devlog 16 Then I wondered if it could do more than black lines. I experimented with grouping similar colours, even though it makes the workflow more complicated. What I did Added k-means colour clustering. Ordered groups from dark to light. Generated fill paths for each colour group. Current result The processing engine can split an image into separate colour layers.
Devlog 17 The bot canāt magically swap the pen colour in every app, so I made the program honest about that limitation instead of pretending it was solved. What I did Added automatic pauses between colour groups. Made an always-on-top colour notice with an RGB swatch. Added continue and stop controls for each layer. Current result Multi-colour mode guides the user through manual pen changes.
Devlog 18 By now it worked, but the controls felt scattered. I spent this session making it feel more like a small Windows utility than a school experiment. What I did Organised controls into Settings, Thresholding, and Action sections. Added labels for interval, click delay, luminance, and draw pattern. Improved the image and threshold previews. Current result The main workflow is easier to understand at a glance.
Devlog 19 I realised most people would double-click the app, not run commands. A console window popping up behind it made it feel unfinished. What I did Added main.pyw for no-console Windows launching. Guarded console output for environments without stdout/stderr. Checked the project can also be packaged with PyInstaller. Current result The project is closer to something a normal user can open directly.
Devlog 20 The final part was testing with different pictures and fixing the little problems that only show up when you actually use the program. Then I wrote the README so future-me knows what all of this does. What I did Tested line-art, threshold, and colour-group paths with sample images. Checked placement, cancellation, stop behaviour, and cursor release. Added installation, usage, safety, and limitation notes to the README. Listed dependencies in requirements.txt . Current result A working AutoDraw desktop project with documented setup and safety guidance. Plenty of future ideas, but a complete usable version now.
Devlog 21 I watched the bot draw and finally noticed why it looked a bit like a printer instead of a person: it was doing separate scan lines with spaces between them. It was technically drawing the right shapes, but the movement did not feel right. What I did Looked at how the fill paths were being created. Kept the older horizontal, vertical, and random scanline styles as optional faster modes. Planned a new default that would stay on real image pixels instead of jumping between rows. Current result I understood that the problem was the path algorithm, not the mouse speed. The next task was to make a proper continuous tracer.
Devlog 22 So I was thinking: if every dark pixel is part of a little map, the cursor should be able to walk through that map without taking shortcuts through the white background. That became the new continuous drawing style. What I did Added a Continuous draw pattern and made it the default. Grouped ink pixels into connected regions. Used a depth-first walk to make long, pixel-adjacent pen paths. Let paths backtrack over already-drawn pixels instead of lifting the pen or crossing blank space. Kept larger connected shapes first so the drawing starts with the main details. Current result The bot can draw connected regions as unbroken, human-like strokes. There are no skipped scan lines in Continuous mode. The original fill patterns are still available for shading-style drawings.
Devlog 23 The new paths looked good in code, but moving a real mouse along pixel steps can still look rough. I spent time checking that the automation engine could follow those close-together points safely. What I did Updated the mouse engine to expand longer point-to-point moves into safe drag steps. Checked pause, stop, and mouse-button release behaviour with continuous paths. Updated the draw-style controls and help text so Continuous is clearly the normal choice. Kept the live preview and placement ghost matched to the same processed mask. Current result Continuous paths are ready for real cursor automation. The output stays faithful to the source mask instead of drawing through empty areas....
|
1793865374.8985126
|
1794729374.8985126
|
|
52550
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1793865383.5249379
|
1794729383.5249379
|
|
35025
|
OSLFFB by @kolon3d | Stardance
|
kolon3d
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: OSLFFB by @kolon3d | Stardance
|
1793865385.2466125
|
1794729385.2466125
|
|
52553
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1793865386.1024115
|
1794729386.1024115
|
|
52557
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1793865390.415612
|
1794729390.415612
|
|
52566
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1793868423.8895576
|
1794732423.8895576
|
|
52574
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1793868425.6489716
|
1794732425.6489716
|
|
52579
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1793868429.1932557
|
1794732429.1932557
|
|
52582
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1793868430.0554109
|
1794732430.0554109
|
|
52585
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1793868431.8071737
|
1794732431.8071737
|
|
2062
|
FOLIO by @harshithkarthikeyan21 | Stardance
|
harshithkarthikeyan21
|
0
|
0.43
|
0
|
[]
|
[{"post_id": 1655, "ts": "2026 [{"post_id": 1655, "ts": "2026-06-03T19:46:50Z", "hours": 0.4342, "text": "FOLIO DEVLOG #1 Project overview: Folio is the unified, AI-driven portfolio advisor app that connects your fragmented investments and transforms complex market data into instant, plain-English risk analysis Created Github repo finished getting live stock data from yahoo finance started working on getting live Crypto prices"}]...
|
Title: FOLIO by @harshithkarthikeyan21 | Stardance Title: FOLIO by @harshithkarthikeyan21 | Stardance
Devlogs:
FOLIO DEVLOG #1 Project overview: Folio is the unified, AI-driven portfolio advisor app that connects your fragmented investments and transforms complex market data into instant, plain-English risk analysis Created Github repo finished getting live stock data from yahoo finance started working on getting live Crypto prices...
|
1793868434.7022743
|
1794732434.7022743
|
|
45953
|
School Website by @Anshhh | Stardance
|
Anshhh
|
0
|
5.02
|
0
|
[]
|
[{"post_id": 45233, "ts": "202 [{"post_id": 45233, "ts": "2026-08-11T16:01:01Z", "hours": 1.6383, "text": "I added a page for the faculty and a separate page for each teacher(that is not designed yet) For this I have made cards for each teacher, with their respective dataā¦ I will add all the teachersā info after finalizing the structure. Now I am planning to add a notice page and an admin page through which I could update all the notices easily."}, {"post_id": 44071, "ts": "2026-08-09T16:15:26Z", "hours": 1.3153, "text": "Hero section DONEEE!!! Dayum, that was fun, I am done with the hero section, added a desc, some CTA buttons, some stats and allā¦ I love the structure and the look of itā¦ WOW Next I will be adding a faculty page, with separate cards for each teacherā¦ less gooo"}, {"post_id": 43943, "ts": "2026-08-09T12:14:06Z", "hours": 2.0711, "text": "I am making a website for my schoolā¦ I have created a base for the hero section, a simple navbar and a slideshow for some images of the school to showcaseā¦ I will finish the hero section soon and move to the facilitatorās page, I am planning to make separate cards for all the teachers and add their description on itā¦"}]...
|
Title: School Website by @Anshhh | Stardance
Devl Title: School Website by @Anshhh | Stardance
Devlogs:
I am making a website for my schoolā¦ I have created a base for the hero section, a simple navbar and a slideshow for some images of the school to showcaseā¦ I will finish the hero section soon and move to the facilitatorās page, I am planning to make separate cards for all the teachers and add their description on itā¦
Hero section DONEEE!!! Dayum, that was fun, I am done with the hero section, added a desc, some CTA buttons, some stats and allā¦ I love the structure and the look of itā¦ WOW Next I will be adding a faculty page, with separate cards for each teacherā¦ less gooo
I added a page for the faculty and a separate page for each teacher(that is not designed yet) For this I have made cards for each teacher, with their respective dataā¦ I will add all the teachersā info after finalizing the structure. Now I am planning to add a notice page and an admin page through which I could update all the notices easily....
|
1793868436.9691303
|
1794732436.9691303
|
|
45960
|
CIE Computer Science DBML Playground by @hackyc | CIE Computer Science DBML Playground by @hackyc | Stardance...
|
hackyc
|
0
|
36.52
|
0
|
[]
|
[{"post_id": 63928, "ts": "202 [{"post_id": 63928, "ts": "2026-09-08T00:02:18Z", "hours": 1.5114, "text": "Local Flask Server FULLY DONE The project is under active development for an online version accessible to the public. It will be in the next ship. 2026-08-15 - v0.4.1 Summary Refined repository hygiene after the static migration planning work. Changed Updated root ignore rules to exclude macOS .DS_Store metadata from version control. 2026-07-22 - v0.4.0 Summary Documented the static GitHub Pages migration strategy before implementation began. Added Added github-static/implementation_plan.md describing the browser SQLite architecture, static deployment model, client-owned database persistence, API replacement map, test plan, security considerations, and GitHub Pages deployment options. 2026-07-18 - v0.3.1 Summary Adjusted the Flask development server documentation and runtime configuration for local network access. changed Updated the Flask server port configuration. Updated README run instructions to match the locally accessible development server."}, {"post_id": 50647, "ts": "2026-08-19T22:13:58Z", "hours": 10.0631, "text": "Added DML syntax for CIE. Started backend re-write for the github static page."}, {"post_id": 48507, "ts": "2026-08-16T21:42:50Z", "hours": 12.7036, "text": "Working on the github static page. This is somewhat much harder than I think, 3 hours went into relearning jsā¦ Also need the fix the UI bug where the selected category in dark mode is still black text."}, {"post_id": 47855, "ts": "2026-08-16T02:42:23Z", "hours": 5.0339, "text": "Plan written for Github Static Page. Itās so hard that I need to re-write nearly all backend logic as the processing part has to be on client-end as github pages are static only."}, {"post_id": 47331, "ts": "2026-08-15T06:39:37Z", "hours": 5.6633, "text": "Wooooooo light mode! Imported more syntax rules :P"}, {"post_id": 47154, "ts": "2026-08-14T20:45:31Z", "hours": 1.54, "text": "Base UI is working finallyā¦ SQL syntax still need to be checked to strictly only allow CIE syntax! Need to get a āLight Modeā for UI."}]...
|
Title: CIE Computer Science DBML Playground by @ha Title: CIE Computer Science DBML Playground by @hackyc | Stardance
Devlogs:
Base UI is working finallyā¦ SQL syntax still need to be checked to strictly only allow CIE syntax! Need to get a āLight Modeā for UI.
Wooooooo light mode! Imported more syntax rules :P
Plan written for Github Static Page. Itās so hard that I need to re-write nearly all backend logic as the processing part has to be on client-end as github pages are static only.
Working on the github static page. This is somewhat much harder than I think, 3 hours went into relearning jsā¦ Also need the fix the UI bug where the selected category in dark mode is still black text.
Added DML syntax for CIE. Started backend re-write for the github static page.
Local Flask Server FULLY DONE The project is under active development for an online version accessible to the public. It will be in the next ship. 2026-08-15 - v0.4.1 Summary Refined repository hygiene after the static migration planning work. Changed Updated root ignore rules to exclude macOS .DS_Store metadata from version control. 2026-07-22 - v0.4.0 Summary Documented the static GitHub Pages migration strategy before implementation began. Added Added github-static/implementation_plan.md describing the browser SQLite architecture, static deployment model, client-owned database persistence, API replacement map, test plan, security considerations, and GitHub Pages deployment options. 2026-07-18 - v0.3.1 Summary Adjusted the Flask development server documentation and runtime configuration for local network access. changed Updated the Flask server port configuration. Updated README run instructions to match the locally accessible development server....
|
1793868438.7571871
|
1794732438.7571871
|
|
45977
|
AURA by @luciaa | Stardance
|
luciaa
|
0
|
0.97
|
0
|
[]
|
[{"post_id": 58370, "ts": "202 [{"post_id": 58370, "ts": "2026-08-30T19:33:37Z", "hours": 0.9739, "text": "Aura ā Day 1 (kind of) Not actually day one ā I started this project back in early August but had to put it on hold, didnāt have the time for it. Picking it back up now. The idea: move your hand in front of the camera and it makes music. First hurdle was just getting the camera to show up on screen. PowerShell had script execution disabled by default, so that took a bit of troubleshooting before I could even test anything. Once that was fixed, the camera worked right away. From there I added hand detection with MediaPipe and connected it to sound: hand height controls the pitch, an open hand vs. a closed fist changes the tone, and the left and right hand play in different note ranges. With both hands up, you can already play something like a rough melody ā a gesture-controlled theremin, basically. Right now the sound is still pretty rough ā the pitch jumps around more than Iād like, and the tone itself needs work. Thatās next."}]...
|
Title: AURA by @luciaa | Stardance
Devlogs:
Aura Title: AURA by @luciaa | Stardance
Devlogs:
Aura ā Day 1 (kind of) Not actually day one ā I started this project back in early August but had to put it on hold, didnāt have the time for it. Picking it back up now. The idea: move your hand in front of the camera and it makes music. First hurdle was just getting the camera to show up on screen. PowerShell had script execution disabled by default, so that took a bit of troubleshooting before I could even test anything. Once that was fixed, the camera worked right away. From there I added hand detection with MediaPipe and connected it to sound: hand height controls the pitch, an open hand vs. a closed fist changes the tone, and the left and right hand play in different note ranges. With both hands up, you can already play something like a rough melody ā a gesture-controlled theremin, basically. Right now the sound is still pretty rough ā the pitch jumps around more than Iād like, and the tone itself needs work. Thatās next....
|
1793868440.7622128
|
1794732440.7622128
|
|
45991
|
Cosmicshell by @Prokshith | Stardance
|
Prokshith
|
0
|
2.86
|
0
|
[]
|
[{"post_id": 47016, "ts": "202 [{"post_id": 47016, "ts": "2026-08-14T16:29:51Z", "hours": 1.6461, "text": "Change design on th lock and started working on home screen (taskbar)"}, {"post_id": 45238, "ts": "2026-08-11T16:09:21Z", "hours": 0.6586, "text": "Just finished the booting and the lock screen . Isnāt it is cool.(Donāt forget leave any feedback)"}, {"post_id": 44532, "ts": "2026-08-10T11:08:33Z", "hours": 0.5564, "text": "stared working on lock screen,initial degsin below ."}]...
|
Title: Cosmicshell by @Prokshith | Stardance
Devl Title: Cosmicshell by @Prokshith | Stardance
Devlogs:
stared working on lock screen,initial degsin below .
Just finished the booting and the lock screen . Isnāt it is cool.(Donāt forget leave any feedback)
Change design on th lock and started working on home screen (taskbar)...
|
1793868442.5249846
|
1794732442.5249846
|
|
50820
|
PocketPlayer by @nameer | Stardance
|
nameer
|
0
|
5.74
|
0
|
[]
|
[{"post_id": 54398, "ts": "202 [{"post_id": 54398, "ts": "2026-08-25T12:11:04Z", "hours": 1.2414, "text": "Audio Output Architecture: I researched the audio output stage for PocketPlayer and decided on a provisional architecture using the PCM5102A stereo DAC followed by the TPA6133A2 stereo headphone amplifier. The ESP32 sends digital audio to the DAC over IĀ²S, the DAC converts it to analog stereo audio, and the headphone amplifier drives the final 3.5 mm stereo headphone output. I also documented the complete signal path in architecture.md."}, {"post_id": 53569, "ts": "2026-08-24T05:04:12Z", "hours": 0.7294, "text": "Microphone Comparison & Selection: I compared the INMP441 with alternative IĀ²S MEMS microphones, including the ICS-43434 and SPH0645LM4H-B. I evaluated factors such as IĀ²S compatibility, SNR, frequency response, power consumption, size, and availability. I decided to keep the INMP441 as a provisional candidate while continuing to verify availability before the final purchase. I also updated the PocketPlayer component documentation with the comparison and selection reasoning."}, {"post_id": 52232, "ts": "2026-08-22T10:20:17Z", "hours": 1.7178, "text": "INMP441 Microphone Research: Researched the INMP441 digital MEMS microphone and documented its IĀ²S interface, voltage requirements, audio specifications, ESP32 compatibility, and recording architecture. I also noted that the INMP441 is currently listed as NRND, so its availability and possible alternatives will be checked before final purchase."}, {"post_id": 51540, "ts": "2026-08-21T09:32:56Z", "hours": 0.9681, "text": "Session 3 ā Hardware Research: I continued PocketPlayerās hardware research by verifying the SSD1306 128Ć64 OLED and EC11 rotary encoder. I documented their relevant specifications, interfaces, compatibility with the ESP32, and physical dimensions that still need to be verified from the exact parts before CAD. I also added the rotary encoderās user-input architecture to the project documentation. Next, I will research the microSD storage system and continue verifying the remaining hardware."}, {"post_id": 50939, "ts": "2026-08-20T12:31:35Z", "hours": 1.0808, "text": "Session 1 + Session 2 ā PocketPlayer: I set up the PocketPlayer project, created and connected the GitHub repository and Hackatime tracking, and established the initial project structure. I then began hardware research and verified the ESP32-DevKitC V4 using Espressifās official documentation, documenting its relevant interfaces, power options, and GPIO considerations. The next step is to research and verify the remaining components before finalizing the hardware desinging"}]...
|
Title: PocketPlayer by @nameer | Stardance
Devlog Title: PocketPlayer by @nameer | Stardance
Devlogs:
Session 1 + Session 2 ā PocketPlayer: I set up the PocketPlayer project, created and connected the GitHub repository and Hackatime tracking, and established the initial project structure. I then began hardware research and verified the ESP32-DevKitC V4 using Espressifās official documentation, documenting its relevant interfaces, power options, and GPIO considerations. The next step is to research and verify the remaining components before finalizing the hardware desinging
Session 3 ā Hardware Research: I continued PocketPlayerās hardware research by verifying the SSD1306 128Ć64 OLED and EC11 rotary encoder. I documented their relevant specifications, interfaces, compatibility with the ESP32, and physical dimensions that still need to be verified from the exact parts before CAD. I also added the rotary encoderās user-input architecture to the project documentation. Next, I will research the microSD storage system and continue verifying the remaining hardware.
INMP441 Microphone Research: Researched the INMP441 digital MEMS microphone and documented its IĀ²S interface, voltage requirements, audio specifications, ESP32 compatibility, and recording architecture. I also noted that the INMP441 is currently listed as NRND, so its availability and possible alternatives will be checked before final purchase.
Microphone Comparison & Selection: I compared the INMP441 with alternative IĀ²S MEMS microphones, including the ICS-43434 and SPH0645LM4H-B. I evaluated factors such as IĀ²S compatibility, SNR, frequency response, power consumption, size, and availability. I decided to keep the INMP441 as a provisional candidate while continuing to verify availability before the final purchase. I also updated the PocketPlayer component documentation with the comparison and selection reasoning.
Audio Output Architecture: I researched the audio output stage for PocketPlayer and decided on a provisional architecture using the PCM5102A stereo DAC followed by the TPA6133A2 stereo headphone amplifier. The ESP32 sends digital audio to the DAC over IĀ²S, the DAC converts it to analog stereo audio, and the headphone amplifier drives the final 3.5 mm stereo headphone output. I also documented the complete signal path in architecture.md....
|
1793868443.4098961
|
1794732443.4098961
|
|
50828
|
my things by @Saurabhnarale | Stardance
|
Saurabhnarale
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: my things by @Saurabhnarale | Stardance
|
1793868446.6030426
|
1794732446.6030426
|
|
50842
|
tek by @shailesh | Stardance
|
|
0
|
1.53
|
0
|
[]
|
[{"post_id": 49557, "ts": "202 [{"post_id": 49557, "ts": "2026-08-18T13:11:03Z", "hours": 0.2836, "text": "added the hip connector and the electronics moutnign plate, exported duplicate items to make it easier for print legion"}, {"post_id": 49525, "ts": "2026-08-18T12:13:55Z", "hours": 1.2506, "text": "I made the first leg of the biped, need to mirror to make another and make a mounting plate for the electronics"}]...
|
Title: tek by @shailesh | Stardance
Devlogs:
I ma Title: tek by @shailesh | Stardance
Devlogs:
I made the first leg of the biped, need to mirror to make another and make a mounting plate for the electronics
added the hip connector and the electronics moutnign plate, exported duplicate items to make it easier for print legion...
|
1793868449.7734172
|
1794732449.7734172
|
|
7134
|
All-In-One Downloader by @joshualom8 | Stardance
|
joshualom8
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: All-In-One Downloader by @joshualom8 | Star Title: All-In-One Downloader by @joshualom8 | Stardance...
|
1793868451.5011451
|
1794732451.5011451
|
|
18236
|
My very own WebOS by @heian | Stardance
|
heian
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @heian | Stardance
|
1793868453.2674754
|
1794732453.2674754
|
|
15593
|
My first slack bot! by @sadhana_g | Stardance
|
sadhana_g
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @sadhana_g | Stardan Title: My first slack bot! by @sadhana_g | Stardance...
|
1793868456.8341374
|
1794732456.8341374
|
|
38299
|
Untitled by @Yoruu | Stardance
|
Yoruu
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @Yoruu | Stardance
|
1793868459.8297405
|
1794732459.8297405
|
|
9198
|
My awesome macropad! by @AP | Stardance
|
AP
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @AP | Stardance
|
1793868461.5632832
|
1794732461.5632832
|
|
8556
|
THE ULTIMATE JARVIS by @Mokxsh_ | Stardance
|
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: THE ULTIMATE JARVIS by @Mokxsh_ | Stardance
|
1793868463.297625
|
1794732463.297625
|
|
54596
|
PianoOS by @niejestemprawdziwyy | Stardance
|
niejestemprawdziwyy
|
1
|
40.64
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-09-03T08:54:23Z", "hours": 14.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "WebOS BUT you can play piano. PianoOS also allows you to run a metronome as an app and make some hehe notes The most challenging thing was definitely the animation in the beggining, like hell nah, i must have spent like 6h just on a 5 second cutscene. Still tho, Iām happy with how it looks, and even happier how it can look in the future.", "repo": "https://github.com/Korsor2137/PianoOS", "demo": "https://raw.githack.com/Korsor2137/PianoOS/main/index.html"}]...
|
[{"post_id": 85968, "ts": "202 [{"post_id": 85968, "ts": "2026-10-31T23:02:49Z", "hours": 2.5367, "text": "I finished the next update of PianoOS. Named it 2.2 , because yes. So yeah, from previous devlog the only things that changed are: record and play finally work, after fixing some, wouldnāt call it bugs, but rather stupid misspells and writing a new function. I also changed settings saving, now it saves both audio and one and only visual setting. Cool. I changed the base color of nutkis (flying notes) to cyan, because my friend said he liked it. And i guess itās everything. Iāll see if it gets accepted, hope so. Oh, and a video proving that this works with midi piano, i think i didnāt do one yet, yeah that laptop is as olf as it looks, so it doesnāt work the best on it, but on any other normal device it should work just fine, and that meow was in the video, not from your cat. Below is a short story of my halloween, cause today was great. I was at my local gallery, because there was a little anime/game event happenning. I went there with 2 other friends, one was that cyan guy from earlier, and weāve had fun there. Bought some merch, silksong shirt, some genshin and jojo pins. But on the way home, there was one thing still on my mind, i donāt have any costume or mask to scare the people coming. Then, as if a lightbulb appeared over my head. I got my dressing-gown, an empty bottle of nonalcoholic drink called āleszek freeā and a baseball bat. And when they came to knock on my door, i turned off all lights, and slowly opened the door, so i was still standing in the shadows, made a drinking gesture with that bottle, and after a moment fake rushed towards them with that bat, shouting out loud āget out of my land!!ā in polish of course. Then smiled and gave them candies. Gave them a scare of the night. And i must have became quite the attraction, because the same few people kept telling and bringing more to my door. At one moment it must have been like 15 people at once. Proud of myself, best act of my life."}, {"post_id": 85184, "ts": "2026-10-30T22:31:23Z", "hours": 3.385, "text": "Made the flying notes. They are red because it was all my blood, sweat and tears. Well, actually because red is very easy to see, still iāll make the colors customizable, and make the record and play options fully work. Then itāll be work done. Nice. Also, recorded myself coding, cause i really want to have this project accepted. Ima go to sleep, itās late in the night."}, {"post_id": 84526, "ts": "2026-10-29T20:21:06Z", "hours": 3.6144, "text": "I made a clock and a help button, so some people donāt get lost in my webOS. Thatās kinda it, it took long all because i couldnāt see a little misspell. Also made the flying notes checkbox, but well, it doesnāt do anything yet of course. Iāll try finishing in next 2 days and ship it as fast as possible. Also recording myself doing it, because i got āyou have overused aiā copy paste āfeedbackā 3 times already, even tho i did what i was told. So, adding new things that it. And a question, does time alone look good, or should i add also the date?"}, {"post_id": 75696, "ts": "2026-09-30T19:34:29Z", "hours": 7.9089, "text": "Heck yeah! Finished all the rewriting, added a few new things blah blah blah Nobody cares! The important thing is that iāve rewritten all css and most js, fixed many if not all bugs, so itās foolproof. Yet another alt settings to play (in config). Metronome also sound more realistic. The whole thing should, and i mean should work better and faster. It looks better, sustain pedal fully works etc. etc. ANYWAY TEST IT HERE: https://raw.githack.com/Korsor2137/PianoOS/main/index.html"}, {"post_id": 69175, "ts": "2026-09-16T15:12:47Z", "hours": 0.5994, "text": "Made new controls for piano, so itās possible to play more sounds with keyboard itself left-new, right-old However iām still leaving them in the comments if for some reason someone wanted to use them I suppose i should make these devlogs a bit more often, the previous one was like 8h gap lol (q: 45 means that q is A4, i: 57 is A5, the rest most people can figure out themselves)"}, {"post_id": 68766, "ts": "2026-09-15T18:32:55Z", "hours": 8.6006, "text": "Made a new, better banner and rewriting a lot of things I was told that there was too much ai used, so i marked clearly at what part ai was used and rewritten the other parts. Added settings saving and reading it, made the samples load faster and added a loading percentage, deleted a particle animation so it doesnāt lag that much on mobiles, made the piano look cleaner (deleted some nametags), added sustain on spacebar, added config section in the code, readded old and added new unneccesary comments, fixed a bug with music either glitching out or playing after refreshing and fixed a few esthetic choices, probably unnoticable, but color changes and alsoā¦. plaing still dre is way easier now, as B3 can now be played with q, sooooo you just go āadhā a few times, then another few of āqdhā and some āqsgā. use spacebar for sustain and mouse for bass notes and voila! also i made it possible to name the workspace in the web itself still, i have to rewrite most of css, as some parts are unneccesary or ai and some are well, lacking. also, fixed the piano sample loading, just too lazy to make a new screenshot also, i overuse the word āalsoā"}, {"post_id": 60719, "ts": "2026-09-03T08:45:08Z", "hours": 5.8211, "text": "Finally, I finished my WebOS, or did I? I want to continue working on it as WebOS 2. Iām quite proud of how it looks now. But anyway, hereās the Readme: PianoOSA WebOS, which has notepad and metronome apps and fully playable 88 key piano. Try it here : https://raw.githack.com/Korsor2137/PianoOS/main/index.html Note: it may take a few seconds to prepare all the piano sounds How to run: Yeah, just click the link. Or download it and then run index.html Features: -Full 88 key virtual piano, which you can play using mouse, with your pc keyboard (-a- to -ā- keys, press capslock to change octaves to lower) or by connecting your own MIDI piano; -Keys glow when you play the piano; -A simple notepad and a metronome which when you minimalize will remember their location adn when theyāre closed, their position resets; -A button to hide the piano interface; -Volume settings which you can change to your liking. Authorās notes: And why did I decide to make this? Well, I saw how on the WebOS missions there was a lot of awesome stuff, the same main concept and yet they were all so different. So, since I like piano, decided to implement it :D I plan on making it more customizable in the future, such as changing the background color, or maybe the whole stylistic, making the top right buttons actually work instead of just being a decoration, adding maybe a few piano sounds, and of course more apps so it actually feels like an actual OS. Also, notice a little reference at the title screen? Full copyright of the sound samples I used: MIT LicenseCopyright (c) 2020 Liam LeePermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the āSoftwareā), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED āAS ISā, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."}, {"post_id": 59229, "ts": "2026-08-31T22:01:49Z", "hours": 3.7533, "text": "I made the background and keyboard for my WebOS. Not gonna lie, used AI here with canvas, also found nice tutorial so i might do these particles that fly above when playing piano. iām quite proud of making these glowing keys, well those are actually shadows but doesnāt matter. Also: made these names for keys, i intend for them to be toggable tho; made a button to hide/show piano, i think it looks good when its fully hidden and only the lights remain; and itās now possible to control the piano with a pc keyboard, using ā a ā to ā ā ā keys, black keys are the keys above like ā w ā and ā e ā, and to change the octave with capslock; itās also possible to control them with mouse For my plans, i next intend to make some actual apps, of course including notebook, but also metronome and midi recording. From other things i want to implement shortcuts, so when you press A0 and C4, for example, virtual keyboard hides or shows. Last thing is to make a mouse setting so when a note is pressed, until you stop pressing it you can move it to any position, while still playing that note (Toggable, so that itās also possible to scale the whole piano really fast). I donāt intend to implement everything now, maybe after i make the first few apps and working piano iāll ship it as WebOS 1, and then continue as WebOS 2 Oh, and should i name the keys that are possible to play with pc keyboard or maybe should i simply add a short guide of how it works and also maybe it would make sense to add actual sounds lol Anyways, feedback and critique is welcome, encouraged even, so i know what would actually be a good feature"}, {"post_id": 56764, "ts": "2026-08-28T17:34:02Z", "hours": 4.6208, "text": "Since this is my first post iāll explain what my project even is about. My goal is to create a WebOS that you can control with a midi piano, where i want to then implement some usefull functions for pianists, weāll see how far can i go with my amateur skills. Iāve coded bigger part of html already. Currently though im having some problems with how it looks and the whole animation. I seriously need to optimize it because daamnn its laggy now. Also, what a coincidence with the colors of those seven sou- i mean balls of light."}]...
|
Title: PianoOS by @niejestemprawdziwyy | Stardance Title: PianoOS by @niejestemprawdziwyy | Stardance
Devlogs:
Since this is my first post iāll explain what my project even is about. My goal is to create a WebOS that you can control with a midi piano, where i want to then implement some usefull functions for pianists, weāll see how far can i go with my amateur skills. Iāve coded bigger part of html already. Currently though im having some problems with how it looks and the whole animation. I seriously need to optimize it because daamnn its laggy now. Also, what a coincidence with the colors of those seven sou- i mean balls of light.
I made the background and keyboard for my WebOS. Not gonna lie, used AI here with canvas, also found nice tutorial so i might do these particles that fly above when playing piano. iām quite proud of making these glowing keys, well those are actually shadows but doesnāt matter. Also: made these names for keys, i intend for them to be toggable tho; made a button to hide/show piano, i think it looks good when its fully hidden and only the lights remain; and itās now possible to control the piano with a pc keyboard, using ā a ā to ā ā ā keys, black keys are the keys above like ā w ā and ā e ā, and to change the octave with capslock; itās also possible to control them with mouse For my plans, i next intend to make some actual apps, of course including notebook, but also metronome and midi recording. From other things i want to implement shortcuts, so when you press A0 and C4, for example, virtual keyboard hides or shows. Last thing is to make a mouse setting so when a note is pressed, until you stop pressing it you can move it to any position, while still playing that note (Toggable, so that itās also possible to scale the whole piano really fast). I donāt intend to implement everything now, maybe after i make the first few apps and working piano iāll ship it as WebOS 1, and then continue as WebOS 2 Oh, and should i name the keys that are possible to play with pc keyboard or maybe should i simply add a short guide of how it works and also maybe it would make sense to add actual sounds lol Anyways, feedback and critique is welcome, encouraged even, so i know what would actually be a good feature
Finally, I finished my WebOS, or did I? I want to continue working on it as WebOS 2. Iām quite proud of how it looks now. But anyway, hereās the Readme: PianoOSA WebOS, which has notepad and metronome apps and fully playable 88 key piano. Try it here : https://raw.githack.com/Korsor2137/PianoOS/main/index.html Note: it may take a few seconds to prepare all the piano sounds How to run: Yeah, just click the link. Or download it and then run index.html Features: -Full 88 key virtual piano, which you can play using mouse, with your pc keyboard (-a- to -ā- keys, press capslock to change octaves to lower) or by connecting your own MIDI piano; -Keys glow when you play the piano; -A simple notepad and a metronome which when you minimalize will remember their location adn when theyāre closed, their position resets; -A button to hide the piano interface; -Volume settings which you can change to your liking. Authorās notes: And why did I decide to make this? Well, I saw how on the WebOS missions there was a lot of awesome stuff, the same main concept and yet they were all so different. So, since I like piano, decided to implement it :D I plan on making it more customizable in the future, such as changing the background color, or maybe the whole stylistic, making the top right buttons actually work instead of just being a decoration, adding maybe a few piano sounds, and of course more apps so it actually feels like an actual OS. Also, notice a little reference at the title screen? Full copyright of the sound samples I used: MIT LicenseCopyright (c) 2020 Liam LeePermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the āSoftwareā), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED āAS ISā, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Made a new, better banner and rewriting a lot of things I was told that there was too much ai used, so i marked clearly at what part ai was used and rewritten the other parts. Added settings saving and reading it, made the samples load faster and added a loading percentage, deleted a particle animation so it doesnāt lag that much on mobiles, made the piano look cleaner (deleted some nametags), added sustain on spacebar, added config section in the code, readded old and added new unneccesary comments, fixed a bug with music either glitching out or playing after refreshing and fixed a few esthetic choices, probably unnoticable, but color changes and alsoā¦. plaing still dre is way easier now, as B3 can now be played with q, sooooo you just go āadhā a few times, then another few of āqdhā and some āqsgā. use spacebar for sustain and mouse for bass notes and voila! also i made it possible to name the workspace in the web itself still, i have to rewrite most of css, as some parts are unneccesary or ai and some are well, lacking. also, fixed the piano sample loading, just too lazy to make a new screenshot also, i overuse the word āalsoā
Made new controls for piano, so itās possible to play more sounds with keyboard itself left-new, right-old However iām still leaving them in the comments if for some reason someone wanted to use them I suppose i should make these devlogs a bit more often, the previous one was like 8h gap lol (q: 45 means that q is A4, i: 57 is A5, the rest most people can figure out themselves)
Heck yeah! Finished all the rewriting, added a few new things blah blah blah Nobody cares! The important thing is that iāve rewritten all css and most js, fixed many if not all bugs, so itās foolproof. Yet another alt settings to play (in config). Metronome also sound more realistic. The whole thing should, and i mean should work better and faster. It looks better, sustain pedal fully works etc. etc. ANYWAY TEST IT HERE: https://raw.githack.com/Korsor2137/PianoOS/main/index.html
I made a clock and a help button, so some people donāt get lost in my webOS. Thatās kinda it, it took long all because i couldnāt see a little misspell. Also made the flying notes checkbox, but well, it doesnāt do anything yet of course. Iāll try finishing in next 2 days and ship it as fast as possible. Also recording myself doing it, because i got āyou have overused aiā copy paste āfeedbackā 3 times already, even tho i did what i was told. So, adding new things that it. And a question, does time alone look good, or should i add also the date?
Made the flying notes. They are red because it was all my blood, sweat and tears. Well, actually because red is very easy to see, still iāll make the colors customizable, and make the record and play options fully work. Then itāll be work done. Nice. Also, recorded myself coding, cause i really want to have this project accepted. Ima go to sleep, itās late in the night.
I finished the next update of PianoOS. Named it 2.2 , because yes. So yeah, from previous devlog the only things that changed are: record and play finally work, after fixing some, wouldnāt call it bugs, but rather stupid misspells and writing a new function. I also changed settings saving, now it saves both audio and one and only visual setting. Cool. I changed the base color of nutkis (flying notes) to cyan, because my friend said he liked it. And i guess itās everything. Iāll see if it gets accepted, hope so. Oh, and a video proving that this works with midi piano, i think i didnāt do one yet, yeah that laptop is as olf as it looks, so it doesnāt work the best on it, but on any other normal device it should work just fine, and that meow was in the video, not from your cat. Below is a short story of my halloween, cause today was great. I was at my local gallery, because there was a little anime/game event happenning. I went there with 2 other friends, one was that cyan guy from earlier, and weāve had fun there. Bought some merch, silksong shirt, some genshin and jojo pins. But on the way home, there was one thing still on my mind, i donāt have any costume or mask to scare the people coming. Then, as if a lightbulb appeared over my head. I got my dressing-gown, an empty bottle of nonalcoholic drink called āleszek freeā and a baseball bat. And when they came to knock on my door, i turned off all lights, and slowly opened the door, so i was still standing in the shadows, made a drinking gesture with that bottle, and after a moment fake rushed towards them with that bat, shouting out loud āget out of my land!!ā in polish of course. Then smiled and gave them candies. Gave them a scare of the night. And i must have became quite the attraction, because the same few people kept telling and bringing more to my door. At one moment it must have been like 15 people at once. Proud of myself, best act of my life.
Ships:
WebOS BUT you can play piano. PianoOS also allows you to run a metronome as an app and make some hehe notes The most challenging thing was definitely the animation in the beggining, like hell nah, i must have spent like 6h just on a 5 second cutscene. Still tho, Iām happy with how it looks, and even happier how it can look in the future....
|
1793868464.1426504
|
1794732464.1426504
|
|
26290
|
Untitled by @roberto | Stardance
|
roberto
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @roberto | Stardance
|
1793868464.9804785
|
1794732464.9804785
|
|
52613
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1793868466.7946827
|
1794732466.7946827
|
|
52634
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1793868468.807374
|
1794732468.807374
|
|
52647
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1793868470.5734715
|
1794732470.5734715
|
|
52649
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1793868472.3442638
|
1794732472.3442638
|
|
34003
|
Untitled by @mani | Stardance
|
mani
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @mani | Stardance
|
1793868474.3803496
|
1794732474.3803496
|
|
56091
|
boom boom game by @hann | Stardance
|
hann
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: boom boom game by @hann | Stardance
|
1793868476.6906586
|
1794732476.6906586
|
|
47509
|
causal-interp by @ranveergill | Stardance
|
ranveergill
|
0
|
5.82
|
0
|
[]
|
[{"post_id": 53532, "ts": "202 [{"post_id": 53532, "ts": "2026-08-24T03:44:48Z", "hours": 5.8208, "text": "Devlog 1: Ten phases in, and the honest answer is half yes This project set out to build a system that can discover and causally validate the mechanisms behind a neural networkās behavior, aimed eventually at models too capable for a human to check by hand. Since no answer key exists for that eventual target, the whole approach only means anything if itās validated against models where the answer key does exist and is publicly known. So thatās what the first ten phases did. I ran activation patching and path patching against GPT-2 smallās IOI circuit, a published, head-by-head known structure, and compared the results against the paper directly. Phase 1 recovered 20 of 26 heads. Phase 2 tested whether path patching would fix the misses. It didnāt, and I reported that as a negative result rather than reframing it. Phase 3 fixed 2 more heads using a threshold that was locked in before seeing any scores, specifically to avoid the trap of picking a number because it looks good after the fact. Phase 4 was the real turning point. Every phase up to that point told the system exactly where to look, which position, which part of the head, because the paper says so. Phase 4 made it search for that instead, with zero access to the answer key, and it converged on the right positions anyway. Thatās the first real evidence this can do more than rediscover what itās told. Phases 5 through 7 tested how far that holds up. The pipeline transferred to a second published circuit (greater than comparisons) with almost no code changes, and then to a third circuit on a completely different, smaller model architecture. Recovery dropped hard on that third one, from about 69 percent to 50 percent, and the cause turned out to be structural: the metric being used is blind to a whole class of heads by design, not by mistake. Thatās a real limitation, not a bug, and it only became visible because the system was tested somewhere it hadnāt been tuned. Phases 8 through 10 tried to close that gap and the gaps around it. A system for flagging disagreement between different experimental setups caught the blind spot from phase 7 with no advance warning, which was genuinely exciting, but it also flagged plenty of things that turned out to be nothing, and nothing in the system could yet tell the two apart on its own. A separate attempt to have the system generate its own experiment setups from a one line description worked well at generating candidates, but the system still couldnāt reliably judge which candidate to trust without a human checking the answer. Writing the synthesis after all ten phases made the pattern obvious. Anything that comes down to measuring a number has been mechanized successfully. Anything that comes down to judging whether that number means something real still needs a person. Thatās not a small gap. Itās arguably the one piece the entire project exists to eventually replace, since a model too capable to check by hand is exactly the situation where no one will be available to make that judgment call. A quick follow up check on old data confirmed this isnāt just a vague impression. Itās measurable, and it came back inconclusive on 13 data points, which is itself the honest answer at that sample size rather than something to round up into a finding. Next up is figuring out whether that judgment gap is solvable with a different kind of signal entirely, or whether itās a genuine ceiling on this approach. Either answer would be useful to know for sure."}]...
|
Title: causal-interp by @ranveergill | Stardance
Title: causal-interp by @ranveergill | Stardance
Devlogs:
Devlog 1: Ten phases in, and the honest answer is half yes This project set out to build a system that can discover and causally validate the mechanisms behind a neural networkās behavior, aimed eventually at models too capable for a human to check by hand. Since no answer key exists for that eventual target, the whole approach only means anything if itās validated against models where the answer key does exist and is publicly known. So thatās what the first ten phases did. I ran activation patching and path patching against GPT-2 smallās IOI circuit, a published, head-by-head known structure, and compared the results against the paper directly. Phase 1 recovered 20 of 26 heads. Phase 2 tested whether path patching would fix the misses. It didnāt, and I reported that as a negative result rather than reframing it. Phase 3 fixed 2 more heads using a threshold that was locked in before seeing any scores, specifically to avoid the trap of picking a number because it looks good after the fact. Phase 4 was the real turning point. Every phase up to that point told the system exactly where to look, which position, which part of the head, because the paper says so. Phase 4 made it search for that instead, with zero access to the answer key, and it converged on the right positions anyway. Thatās the first real evidence this can do more than rediscover what itās told. Phases 5 through 7 tested how far that holds up. The pipeline transferred to a second published circuit (greater than comparisons) with almost no code changes, and then to a third circuit on a completely different, smaller model architecture. Recovery dropped hard on that third one, from about 69 percent to 50 percent, and the cause turned out to be structural: the metric being used is blind to a whole class of heads by design, not by mistake. Thatās a real limitation, not a bug, and it only became visible because the system was tested somewhere it hadnāt been tuned. Phases 8 through 10 tried to close that gap and the gaps around it. A system for flagging disagreement between different experimental setups caught the blind spot from phase 7 with no advance warning, which was genuinely exciting, but it also flagged plenty of things that turned out to be nothing, and nothing in the system could yet tell the two apart on its own. A separate attempt to have the system generate its own experiment setups from a one line description worked well at generating candidates, but the system still couldnāt reliably judge which candidate to trust without a human checking the answer. Writing the synthesis after all ten phases made the pattern obvious. Anything that comes down to measuring a number has been mechanized successfully. Anything that comes down to judging whether that number means something real still needs a person. Thatās not a small gap. Itās arguably the one piece the entire project exists to eventually replace, since a model too capable to check by hand is exactly the situation where no one will be available to make that judgment call. A quick follow up check on old data confirmed this isnāt just a vague impression. Itās measurable, and it came back inconclusive on 13 data points, which is itself the honest answer at that sample size rather than something to round up into a finding. Next up is figuring out whether that judgment gap is solvable with a different kind of signal entirely, or whether itās a genuine ceiling on this approach. Either answer would be useful to know for sure....
|
1793868481.7764602
|
1794732481.7764602
|
|
34065
|
Trading Bot by @HenryTierney | Stardance
|
HenryTierney
|
0
|
0.0
|
0
|
[]
|
[{"post_id": 27327, "ts": "202 [{"post_id": 27327, "ts": "2026-07-12T20:14:38Z", "hours": 0.0, "text": "Devlog #1 Welcome to the development log! This project tracks our engineering journey from a flawed, overfitted stock picker into an adaptive, blind multi-asset allocation system. Think of it like building a self-driving car , but for managing money. The Development Journey Step 1: The āGuessingā Car (Overfitting) We started by creating a basic computer rule: āBuy stocks when they drop a bit, and sell them when they jump.ā We let the computer guess the absolute best numbers for this rule using past stock market data. The computer came back with perfect numbers that looked like a jackpot, but there was a catch: it only worked perfectly on the past data because it memorized the answers . If we tried to use this exact code in the real world, it would crash instantly. So I had to: Identify initial strategy flaws Diagnose curve-fitting problems Step 2: The āAdaptiveā Car (Walk-Forward Analysis) To fix the guessing problem, we forced the computer to study history in small chunks. The bot looks at a 10-year window of data to learn basic market behaviors. It tests its rules on the next 5-year window to prove it can adapt to unseen data. This forced the computer to dynamically adjust its style. It learned to be careful and safe during bad economic times (like the high-inflation 1970s) and more aggressive when the economy was booming (like the 1990s). Step 3: Changing the Terrain (Multi-Asset Allocation) Next, we realized that only investing in the US stock market is like driving a sports car on a muddy mountain roadāsometimes you get stuck. We upgraded the system by giving the computer a garage full of different vehicles: US Stocks ( SPY ) Tech Stocks ( QQQ ) Gold ( GLD ) Bonds ( TLT ) Real Estate ( VNQ ) We proved that when the stock market enters a major crash, the bot should pivot capital into hard assets or safety nets to keep compounding value. Step 4: The Blind Talent Scout (Momentum Ranking) To make this fully realistic, we stripped away the computerās ability to ālook aheadā into the future. We built a system that looks back at the past 12 months to see which assets are moving with the fastest upward velocity (momentum). The Rule: Every year, it checks the scoreboard, automatically kicks out the losers, and splits your money 50/50 into the top two winning assets. Step 5: Future Updates While the baseline system is highly capable, the upcoming roadmap includes several key structural upgrades to prepare it for advanced market environments: Dynamic Position Sizing Instead of a rigid 50/50 split, the system will allocate more money to the asset with the smoothest trend and less to the highly volatile one. Alternative Macro Filters We will test replacing the basic stock market filter ( RSI / EMA ) with real-world economic indicators, like inflation tracking and interest rate moves, to predict market crashes earlier. Expanded Asset Pool To capture even more diverse trends, we plan to add international stocks, emerging markets, and broad commodities (like oil and agriculture) to the selection pool."}]...
|
Title: Trading Bot by @HenryTierney | Stardance
D Title: Trading Bot by @HenryTierney | Stardance
Devlogs:
Devlog #1 Welcome to the development log! This project tracks our engineering journey from a flawed, overfitted stock picker into an adaptive, blind multi-asset allocation system. Think of it like building a self-driving car , but for managing money. The Development Journey Step 1: The āGuessingā Car (Overfitting) We started by creating a basic computer rule: āBuy stocks when they drop a bit, and sell them when they jump.ā We let the computer guess the absolute best numbers for this rule using past stock market data. The computer came back with perfect numbers that looked like a jackpot, but there was a catch: it only worked perfectly on the past data because it memorized the answers . If we tried to use this exact code in the real world, it would crash instantly. So I had to: Identify initial strategy flaws Diagnose curve-fitting problems Step 2: The āAdaptiveā Car (Walk-Forward Analysis) To fix the guessing problem, we forced the computer to study history in small chunks. The bot looks at a 10-year window of data to learn basic market behaviors. It tests its rules on the next 5-year window to prove it can adapt to unseen data. This forced the computer to dynamically adjust its style. It learned to be careful and safe during bad economic times (like the high-inflation 1970s) and more aggressive when the economy was booming (like the 1990s). Step 3: Changing the Terrain (Multi-Asset Allocation) Next, we realized that only investing in the US stock market is like driving a sports car on a muddy mountain roadāsometimes you get stuck. We upgraded the system by giving the computer a garage full of different vehicles: US Stocks ( SPY ) Tech Stocks ( QQQ ) Gold ( GLD ) Bonds ( TLT ) Real Estate ( VNQ ) We proved that when the stock market enters a major crash, the bot should pivot capital into hard assets or safety nets to keep compounding value. Step 4: The Blind Talent Scout (Momentum Ranking) To make this fully realistic, we stripped away the computerās ability to ālook aheadā into the future. We built a system that looks back at the past 12 months to see which assets are moving with the fastest upward velocity (momentum). The Rule: Every year, it checks the scoreboard, automatically kicks out the losers, and splits your money 50/50 into the top two winning assets. Step 5: Future Updates While the baseline system is highly capable, the upcoming roadmap includes several key structural upgrades to prepare it for advanced market environments: Dynamic Position Sizing Instead of a rigid 50/50 split, the system will allocate more money to the asset with the smoothest trend and less to the highly volatile one. Alternative Macro Filters We will test replacing the basic stock market filter ( RSI / EMA ) with real-world economic indicators, like inflation tracking and interest rate moves, to predict market crashes earlier. Expanded Asset Pool To capture even more diverse trends, we plan to add international stocks, emerging markets, and broad commodities (like oil and agriculture) to the selection pool....
|
1793868483.500003
|
1794732483.500003
|
|
20132
|
My first slack bot! by @sjpark01 | Stardance
|
sjpark01
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @sjpark01 | Stardanc Title: My first slack bot! by @sjpark01 | Stardance...
|
1793868486.489035
|
1794732486.489035
|
|
50858
|
OpenDAW by @saisrihari | Stardance
|
saisrihari
|
0
|
128.54
|
0
|
[]
|
[{"post_id": 63592, "ts": "202 [{"post_id": 63592, "ts": "2026-09-07T14:48:48Z", "hours": 7.7333, "text": "IāVE ADDED TWO HUGE FEATURES!!!: 1)Full Mixer- So now weāve got a dedicated mixer screen with volume faders, pan, mute/solo and a master channel. The colour of the tracks correspond with the mixer track colours. 2)Fixed Timeline Zoom- The zoom is now visible on the left panel. It changes the timeline width. The zoom is also saved with projects."}, {"post_id": 62627, "ts": "2026-09-06T02:58:38Z", "hours": 8.6619, "text": "Iāve fixed some major bugs with the drum machine. I added a startup window which appears when the application is opened. It appears with entries where you can set your project name, BPM, Make a new project, Open an existing project or even settings. I made a new logo which is displayed at the top. Iāve also added a zoom in timeline feature for better viewing in the timeline."}, {"post_id": 62171, "ts": "2026-09-05T13:08:13Z", "hours": 6.3, "text": "Iāve added a settings window. You can now select your preferred microphone, MIDI and you can refresh devices if youāve connected a new one. Also the keyboard shortcut list is displayed here. Settings is accessible from both the toolbar or the File dropdown"}, {"post_id": 61937, "ts": "2026-09-05T03:36:26Z", "hours": 5.3333, "text": "I removed the fullscreen arrangement feature cause it kept bugging out and I wasnāt able to fix it. Iāll probably add it back on a future date. I also improved the vocals. You can now select your microphone from the input dropdown. You can record vocals when the instrument is playing. Iāve also added a vocal preset to the fx rack. The project is near completion (Iāll say around 3/4th way through)."}, {"post_id": 60964, "ts": "2026-09-03T17:23:11Z", "hours": 5.7111, "text": "I added a fullscreen arangement view. When you click f11 or the arrangement button in the top the daw expands into the timeline. Itās not perfect yet and itās very buggy so I might remove it later (or fix it). The feature is inspired from ableton live."}, {"post_id": 59690, "ts": "2026-09-01T16:44:27Z", "hours": 8.5333, "text": "I added markers (they get placed at your playheads position). I added Auto-save which is togglable currently but Iāll probably change that soon. I added clip fades which can be set after clicking the fade in or fade out button. A dialogue box appears asking you at what time you need the track to fade in and out. I also expanded the undo/redo to 100 states which now includes fades and the markers. The project is close to completion!"}, {"post_id": 59000, "ts": "2026-08-31T16:06:50Z", "hours": 8.3353, "text": "I added a drum beat maker ! (It shows up with an error tho whenever I try to play more than two drum tracks). It has a 16 step sequencer, A kick, snare, Hi-hats, clap. You can add cells by clicking them (theyāre togglable). It uses your current BPM and is added to the timeline using the āAdd to timelineā button. The code works by having separate parts for the tracks, audio engine, and GUI, which work together to load."}, {"post_id": 57853, "ts": "2026-08-30T05:04:15Z", "hours": 7.1, "text": "So I added undo and redo buttons (finally) in the top toolbar you can use ctrl+z and ctrl+y as shortcut keys. Iāve also added a looping feature. You can now enable the loop from the on/off button on the transport bar. Set A sets the loop start at current playhead. Set B sets the loop end at current playhead. āLā toggles looping and playback cycles continuously between Set A and Set B."}, {"post_id": 56752, "ts": "2026-08-28T17:15:33Z", "hours": 8.2692, "text": "I finally added an effects rack. The effects I included were: Gain, Delay, Delay Time, Reverb, Distortion, Compressor, High-pass and low-pass filters. Each track now has an āfxā button or you can use the open effects rack on the left panel. The effects are added both to playback and export and you can use the āfā key to open the rack."}, {"post_id": 55580, "ts": "2026-08-27T15:04:58Z", "hours": 8.3667, "text": "I finally found a purpose for the panel on the left. You can now see the current bpm, track count, track length, selected track, position and length. You can also rename your track, change its colour or split the track here. You can also split a track by moving the playhead and clicking āDā or split at a particular section of the track."}, {"post_id": 55109, "ts": "2026-08-26T15:55:11Z", "hours": 5.6667, "text": "Ok! I added some core features that I was supposed to add before. You can now move your tracks in the timeline. Your supposed to click and drag the waveforms horizontally. I also added settable BPM. Now your BPM is visible in the top toolbar and I set the range from 40bpm to 240 (By default itās 120). Also your bpm is saved and loaded with projects."}, {"post_id": 54901, "ts": "2026-08-26T03:51:31Z", "hours": 3.4381, "text": "I finally added another instrument in the piano roll. You can now select between an acoustic guitar and a piano. Iāll add more in the coming days."}, {"post_id": 54612, "ts": "2026-08-25T17:09:21Z", "hours": 6.9333, "text": "You can now rename and recolor all your tracks! I also fixed the importing from the piano roll to the timeline. When you click the recolour button it randomly picks a colour. Iāll add particular colour pickers in the near future."}, {"post_id": 53907, "ts": "2026-08-24T16:44:13Z", "hours": 1.2, "text": "Added these keyboard commands"}, {"post_id": 53836, "ts": "2026-08-24T15:09:08Z", "hours": 8.3119, "text": "-I FINALLY FIXED THE RECORD BUTTON. -I added a piano roll which can be switched to using the button on the top left (Probably might switch itās location later). -Itās a 4 octave piano you can left-click cells to add notes and click them again to remove. -For now thereās only one instrument (Rhodes Piano). Iāll add more soon!"}, {"post_id": 53055, "ts": "2026-08-23T13:31:43Z", "hours": 2.4144, "text": "Tried to fix the record button cus it kept bugging out for some reason and I screwed everything up. I GIVE UP FOR TODAY. Iāll think abt this tmrw."}, {"post_id": 52840, "ts": "2026-08-23T06:13:19Z", "hours": 9.7575, "text": "Had a bit of a longer session this time. The last 3 days have been highly productive for me but now my holidays are over :( . Iāve made some big changes: -Added a record button. (Took me wayyy to long to make) -Added partitions so now all the sections are clearly divided. -Added a timeline. -Added a panel on the left (Still donāt know what Iām gonna do with it) -Added Save, Load, Export and Import features -Now you can trim your audio clips -Moved the add track button to the top left"}, {"post_id": 52371, "ts": "2026-08-22T14:14:53Z", "hours": 8.0044, "text": "Okā¦ Iāve got some huge changes. The DAW is starting to take shape now. You can now see the waveform of your audio track. I improved the audio quality drastically. I formatted so now everything is centered. I implemented a dark grey theme with neon blue accents. Iāve come up with the nameā¦ I think Iāll call it OpenDAW. I still donāt know what Iāll do with the space on the left but I know Iāll come up with something. My passion for this project is increasing every second I work on it."}, {"post_id": 51720, "ts": "2026-08-21T15:35:14Z", "hours": 8.4694, "text": "FINALLYā¦After 8 hrs smth mins of scripting and debugging I have thisā¦.You can add many tracks, change their individual volumes and play it as a whole. My plan is to make an opensource DAW which can easily be modded. I have holidays where I live so Iāll try putting atleast 8hrs a day. I need to format it because it feels pretty barebones rn AND I NEED THAT LAPTOP (i have a 4gb ram rn). Ty all!!"}]...
|
Title: OpenDAW by @saisrihari | Stardance
Devlogs Title: OpenDAW by @saisrihari | Stardance
Devlogs:
FINALLYā¦After 8 hrs smth mins of scripting and debugging I have thisā¦.You can add many tracks, change their individual volumes and play it as a whole. My plan is to make an opensource DAW which can easily be modded. I have holidays where I live so Iāll try putting atleast 8hrs a day. I need to format it because it feels pretty barebones rn AND I NEED THAT LAPTOP (i have a 4gb ram rn). Ty all!!
Okā¦ Iāve got some huge changes. The DAW is starting to take shape now. You can now see the waveform of your audio track. I improved the audio quality drastically. I formatted so now everything is centered. I implemented a dark grey theme with neon blue accents. Iāve come up with the nameā¦ I think Iāll call it OpenDAW. I still donāt know what Iāll do with the space on the left but I know Iāll come up with something. My passion for this project is increasing every second I work on it.
Had a bit of a longer session this time. The last 3 days have been highly productive for me but now my holidays are over :( . Iāve made some big changes: -Added a record button. (Took me wayyy to long to make) -Added partitions so now all the sections are clearly divided. -Added a timeline. -Added a panel on the left (Still donāt know what Iām gonna do with it) -Added Save, Load, Export and Import features -Now you can trim your audio clips -Moved the add track button to the top left
Tried to fix the record button cus it kept bugging out for some reason and I screwed everything up. I GIVE UP FOR TODAY. Iāll think abt this tmrw.
-I FINALLY FIXED THE RECORD BUTTON. -I added a piano roll which can be switched to using the button on the top left (Probably might switch itās location later). -Itās a 4 octave piano you can left-click cells to add notes and click them again to remove. -For now thereās only one instrument (Rhodes Piano). Iāll add more soon!
Added these keyboard commands
You can now rename and recolor all your tracks! I also fixed the importing from the piano roll to the timeline. When you click the recolour button it randomly picks a colour. Iāll add particular colour pickers in the near future.
I finally added another instrument in the piano roll. You can now select between an acoustic guitar and a piano. Iāll add more in the coming days.
Ok! I added some core features that I was supposed to add before. You can now move your tracks in the timeline. Your supposed to click and drag the waveforms horizontally. I also added settable BPM. Now your BPM is visible in the top toolbar and I set the range from 40bpm to 240 (By default itās 120). Also your bpm is saved and loaded with projects.
I finally found a purpose for the panel on the left. You can now see the current bpm, track count, track length, selected track, position and length. You can also rename your track, change its colour or split the track here. You can also split a track by moving the playhead and clicking āDā or split at a particular section of the track.
I finally added an effects rack. The effects I included were: Gain, Delay, Delay Time, Reverb, Distortion, Compressor, High-pass and low-pass filters. Each track now has an āfxā button or you can use the open effects rack on the left panel. The effects are added both to playback and export and you can use the āfā key to open the rack.
So I added undo and redo buttons (finally) in the top toolbar you can use ctrl+z and ctrl+y as shortcut keys. Iāve also added a looping feature. You can now enable the loop from the on/off button on the transport bar. Set A sets the loop start at current playhead. Set B sets the loop end at current playhead. āLā toggles looping and playback cycles continuously between Set A and Set B.
I added a drum beat maker ! (It shows up with an error tho whenever I try to play more than two drum tracks). It has a 16 step sequencer, A kick, snare, Hi-hats, clap. You can add cells by clicking them (theyāre togglable). It uses your current BPM and is added to the timeline using the āAdd to timelineā button. The code works by having separate parts for the tracks, audio engine, and GUI, which work together to load.
I added markers (they get placed at your playheads position). I added Auto-save which is togglable currently but Iāll probably change that soon. I added clip fades which can be set after clicking the fade in or fade out button. A dialogue box appears asking you at what time you need the track to fade in and out. I also expanded the undo/redo to 100 states which now includes fades and the markers. The project is close to completion!
I added a fullscreen arangement view. When you click f11 or the arrangement button in the top the daw expands into the timeline. Itās not perfect yet and itās very buggy so I might remove it later (or fix it). The feature is inspired from ableton live.
I removed the fullscreen arrangement feature cause it kept bugging out and I wasnāt able to fix it. Iāll probably add it back on a future date. I also improved the vocals. You can now select your microphone from the input dropdown. You can record vocals when the instrument is playing. Iāve also added a vocal preset to the fx rack. The project is near completion (Iāll say around 3/4th way through).
Iāve added a settings window. You can now select your preferred microphone, MIDI and you can refresh devices if youāve connected a new one. Also the keyboard shortcut list is displayed here. Settings is accessible from both the toolbar or the File dropdown
Iāve fixed some major bugs with the drum machine. I added a startup window which appears when the application is opened. It appears with entries where you can set your project name, BPM, Make a new project, Open an existing project or even settings. I made a new logo which is displayed at the top. Iāve also added a zoom in timeline feature for better viewing in the timeline.
IāVE ADDED TWO HUGE FEATURES!!!: 1)Full Mixer- So now weāve got a dedicated mixer screen with volume faders, pan, mute/solo and a master channel. The colour of the tracks correspond with the mixer track colours. 2)Fixed Timeline Zoom- The zoom is now visible on the left panel. It changes the timeline width. The zoom is also saved with projects....
|
1793868491.2053394
|
1794732491.2053394
|
|
11575
|
Who wants to go 3 billion dollars in debt?!! by @k Who wants to go 3 billion dollars in debt?!! by @kelp | Stardance...
|
kelp
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Who wants to go 3 billion dollars in debt?! Title: Who wants to go 3 billion dollars in debt?!! by @kelp | Stardance...
|
1793868494.095072
|
1794732494.095072
|