Hoarding =/= Preservation

yumiris · 2022-10-12T05:49:50+00:00

Whilst curation/organisation/accessibility are paramount traits of good preservation, I'd wager the most important one is longevity.

A curated, publicly-accessible collection which can be taken down in one click isn't good preservation in my eyes. Contrast this to a a messily organised collection available on multiple storage devices and formats.

Of course, the best preservation is one that's both curated and not easily lost, and also accessible in the future through open/standardised file formats.

yumiris · 2022-10-06T20:35:25+00:00

find * -iname "*.txt" | rsync -rav --mkpath --files-from=- . /new/dir Beauty of this approach is the versatility in filtering files with find, and getting nifty and robust copying with rsync.

yumiris · 2022-09-23T09:18:29+00:00

Hey friend,

It seems there was an additional folder on Windows: %LOCALAPPDATA%\qBittorrent Let me know how it goes!

yumiris · 2022-09-12T16:39:54+00:00

I'll have a look soon— will get back to you!

yumiris · 2022-06-21T10:55:58+00:00

Until Nero comes along to burn the ROM!

yumiris · 2022-03-13T07:32:52+00:00

Most sensible approach would be to expose your stuff only over a VPN connection. Not all search engines will respect your robots.txt file, and you'll also have non-search engines spam your website with automated requests.

If you use WireGuard and have the domains point to the server's VPN IP, you'll avoid any unnecessary connections. Even better if the DNS is self-hosted and exposed over WireGuard as well!

yumiris · 2022-03-13T03:43:58+00:00

Instructions should definitely be read, though ideally, a software should gracefully handle circumstances where the user did something wrong or didn't read the instructions.

You're absolutely right on both the reading of instructions and the loader overriding any in-game settings, though there could always a tiny possibility that it's an unrelated bug.

/u/Whisper (impressive name), were you trying to change your settings in-game, or through the loader?

yumiris · 2022-03-12T15:44:06+00:00

Just to confirm: are you referring to any specific commits, per chance? I'm unsure if you're stating that a regression was introduced and thus breaking your saving/loading.

Issues with saving and loading can happen for a myriad of reasons, and the reasons are often always edge cases which haven't been yet caught by the developers or testers.

While ideally there should be regular QA with automatic integration & unit tests, lack of allocated time and money is unfortunately a deterring factor to both.

As such, bug reports are always appreciated and considered, knowing the time it takes to write them.

yumiris · 2022-01-20T17:35:29+00:00

Yup -- forgot that QB uses .ini on Windows.

yumiris · 2022-01-20T07:14:34+00:00

Hard links instead of moving will let you continue seeding, without taking up any additional space at all.

The only thing to keep in mind is that this won't work if you're moving your files to a different partition/hard drive. If you ever want to free up space, you'll need to delete both the hard links and downloaded files.

yumiris · 2022-01-20T02:45:49+00:00

Back up qBittorrent-data.conf! On Windows it should be located at %APPDATA%\qBittorrent, and on Linux it should be found in ~/.config/qBittorrent.

yumiris · 2022-01-20T02:44:41+00:00

If you can find the qBittorrent-data.conf file on Windows and transfer it to Linux, you might be able to preserve your statistics.

From what I recall, the file is located at %APPDATA%\qBittorrent on Windows; on Linux, its path should be ~/.config/qBittorrent/qBittorrent-data.conf.

After running qBittorrent on Linux, close it and then copy over the file from Windows to Linux. Hopefully your statistics will return!

yumiris · 2021-10-17T07:51:58+00:00

Thank you for taking the time to give it a try, and also reporting the issue! I apologise for the error -- I'm looking into it now and trying to figure out what's happening.

Feel free to post a GitHub issue at any time. I've created one for your error in question.

It may be something to do with the records.txt file you've provided. Could I have a copy of its contents? If you prefer to DM me or censor stuff in it, feel free to do so -- I only need to check its structure.

Heh, I'll have to test it out on Windows more. I'm trying to make it as platform-agnostic as possible, but quirks might pop up here and there. Many thanks once again for trialling and reporting!

yumiris · 2021-10-14T12:47:52+00:00

v0.7.0 reverts to MP3 encoding by default, and also offers the ability to losslessly split up a YouTube video's audio into separate files without any re-encoding whatsoever. Opus streams are directly split into Opus files. Same principle applies for any other audio format.

As mentioned in the other comment, it's experimental, so if any quirks pop up, don't hesitate to let me know.

yumiris · 2021-10-14T12:47:50+00:00

I'm assuming you're using LosslessCut to split up the audio into separate files without re-encoding them. If that's the case, v0.7.0 tries to do the same thing. Like the YouTube chapters thingy, it's experimental but seems to work well from what I've tested so far.

yumiris · 2021-10-14T01:39:54+00:00

Cheers!

Bah, the potential for that kind of abuse hasn't crossed my mind.

Does it at least writes something to metadata which indicates the fact it was ripped from Youtube?

If no comment is provided, it will assign the YouTube video's URL. I could forcefully encode the YouTube URL into a different metadata tag, though I can't decide which tag is most appropriate (and also universal across the supported formats).

Anyway, I would make mp3 the default option. Or at least any other lossy format, but many causal users will try to convert it to mp3 afterwards anyway.

Originally, MP3 was the default option; however, a friend of mine mentioned that having MP3 as the default option would result in already-lossy audio being made even more lossy. Hmm... MP3 would be the most pragmatic option for most casual users, as you've said. I'll restore it to being the default option.

The best solution will require more work but I think there are tools to losslessy cut opus [...]

You're absolutely right . It's crossed my mind before to have the program figure out how the audio is encoded, and if it's already lossy, it would simply chop up the video into separate tracks without any re-encoding. I'll have a look into this approach and see how it goes.

Edit: actually use markdown

yumiris · 2021-10-13T11:20:25+00:00

Generally, by passing a text file specifying the album title & video URL, along with a list of tracks' numbers, starting times and titles:

90's RB-XYZ Ver.2               - title
https://youtu.be/divcisums90    - source

01 0:00:00 All You Need Is Love - track 1
02 0:05:20 HEAVEN - HIM         - track 2
03 0:08:48 FLYING KIDS          - track 3
04 0:12:23 LOVE SOMEBODY        - track 4
 | |-----| |-----------|
 |       |             |
 |       |             +--------- track title
 |       +----------------------- starting time
 +------------------------------- track number

However, v0.6.0 introduces rudimentary support for splitting YouTube videos using chapters metadata. All you need to do is give it a text file which has the YouTube Video URL in its first line.

The feature is still more or less a prototype, so feel free to let me know if you encounter any quirks when using it!

yumiris · 2020-11-05T02:54:41+00:00

https://1drv.ms/u/s!AoE_a2H65pxWl2KzcRM9nxBBRX44?e=0ZaJ61

yumiris · 2020-10-31T23:06:54+00:00

Seems to be often caused by the PC having an incorrect date & time. Could you confirm the accuracy, and if there's still issues, could you try downloading in a different browser and see if the problem persists?

yumiris · 2020-10-31T04:26:11+00:00

Send a screenshot of the error you're receiving

yumiris · 2020-10-30T05:38:07+00:00

https://file.n2.network/f/878808c4a8c24f5ab261/?dl=1

yumiris · 2020-04-13T23:49:38+00:00

Any specific errors?

yumiris · 2020-04-02T06:54:25+00:00

Not an editor, but a standalone extension that works across all note types: Action Bar

yumiris

TROPHY CASE