• 2 Posts
  • 84 Comments
Joined 11 months ago
cake
Cake day: August 15th, 2023

help-circle
  • remotelove@lemmy.caMto196@lemmy.blahaj.zoneWendy Carlos rule
    link
    fedilink
    arrow-up
    13
    ·
    edit-2
    1 hour ago

    Synth sims are the cheap way to go. Cardinal is an open source fork of VCV Rack. It can be used standalone or as a plugin with your favorite DAW.

    https://cardinal.kx.studio/

    All the concepts are the same as modular “euro rack” synths. Voltage lines, oscillators, the works. You even use “wires” to connect everything.

    All YouTube tutorials for VCV are generally applicable to Cardinal, btw.

    If you want to go the DAW route, it should work with the free version of FL Studio. It’s just much easier to do full tracks that way. However: FL Studio is not easy to learn and even less so when you are integrating something like Cardinal.

    Edit: I apologize in advance if this post is the reason you fall into the money pit that is digital music.






  • I can’t find a source personally but there seems to be a bit of internet controversy on the subject.

    A clip from TikTok said it was a secret signal for having syphilis. We can discount that just because of the source.

    It could be from Rome or Europe, for reasons ranging from cleanliness to small hot cups.

    Eesh. The Internet is useless these days.



  • It was on old 3.5" drives a long time ago, before anything fancy was ever built into the drives. It was in a seriously rough working environment anyway, so we saw a lot of failed drives. If strange experiments didn’t work to get the things working, mainly for lulz, the next option was to see if a sledge hammer would fix the problem. Funny thing… that never worked either.




  • Maybe? Bad cables are a thing, so it’s something to be aware of. USB latency, in rare cases, can cause problems but not so much in this application.

    I haven’t looked into the exact ways that bad sectors are detected, but it probably hasn’t changed too much over the years. Needless to say, info here is just approximate.

    However, marking a sector as bad generally happens at the firmware/controller level. I am guessing that a write is quickly followed by a verification, and if the controller sees an error, it will just remap that particular sector. If HDDs use any kind of parity checks per sector, a write test may not be needed.

    Tools like CHKDSK likely step through each sector manually and perform read tests, or just tells the controller to perform whatever test it does on each sector.

    OS level interference or bad cables are unlikely to cause the controller to mark a sector as bad, is my point. Now, if bad data gets written to disk because of a bad cable, the controller shouldn’t care. It just sees data and writes data. (That would be rare as well, but possible.)

    What you will see is latency. USB can be magnitudes slower than SATA. Buffers and wait states are causing this because of the speed differences. This latency isn’t going to cause physical problems though.

    My overall point is that there are several independent software and firmware layers that need to be completely broken for a SATA drive to erroneously mark a sector as bad due to a slow conversion cable. Sure, it could happen and that is why we have software that can attempt to repair bad sectors.










  • HE SAID: OK, TEAM UP AGIANST LEMMYSHITPOSTS?

    (i do not condone or endorse said suggestion. only healthy and productive behavior is encouraged on this community. do not participate in lemmy brigading if you are between the ages of 0 and 165. brigading may cause herpes, aids, anal leakage and hair loss. moderators of 196 are not designed to diagnose or treat or provide care for anything. please talk to your medical care provider if you have additional questions.)