• 1 Post
  • 138 Comments
Joined 3 years ago
cake
Cake day: June 8th, 2023

help-circle


  • Interesting thoughts. Thanks for sharing them. I assumed that you would want to have file versioning out of the way and focus on the writing. What about keeping a sort of change log (diary, if you want) as part of the document itself, like an appendix? That way you could maybe separate raw document history from the creative process.

    Git is a technical tool intended for versioning sharing, manipulating and comparing pieces of code. I’m not sure that you need all those aspects for literary work. I imagine that writing a poem is more linear in the sense that you won’t merge a poem branch back to the “main” version of the poem. At least not in the way you would do it with code. You will also probably not submit or accept patches to the poem. So maybe the commit messages are not necessarily the best place to keep “creative metadata” about the content.

    Just some random thoughts. I guess that you’ll have to try and see what method fits your creative process best (the natural trend you mentioned). Good luck!





  • Picard uses audio fingerprinting and the musicbrainz DB to match the items. If the items are in the DB, then it will find them. If they aren’t, then they can be added.

    There are other similar tools (although they might not have graphical UIs) which also use additional metadata backends and allow complex manipulation of audio files. I personally use beets which can be configured to use Musicbrainz, Spotify, Deezer, Discogs and Bandcamp for metadata (it will also help with file manipulation, audio normalization, fetch cover art and many other things). It seems that there is a plugin called ‘ytimport’ which integrates with SoundCloud and YouTube. That might help with your specific question, though I did not test it.

    Beware that the latest release of beets (2.5.x at the time of writing) is quite fresh and might break some plugins. I personally will stick with 2.4.x for a while.












  • sfera@beehaw.orgtoLinux@lemmy.mlswap SSD to test run Linux?
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    9 months ago

    Testing a normal Linux installation sounds like a good idea. In my opinion it’s better to transition to Linux than switch. That way you can go back to your previous system setup and see what you are missing or need without having to open your computer and swap hardware. If you can add the old or new SSD as an external drive and so that you can can boot then your plan might work out.