That would actually be handy, because I'm personally sick of all the ~2KB ini files that "portable" programs* leave all over the place. It would be awesome if they instead came with a few KB internal padding that was used to store the config (so the filesize doesn't change, to not affect simplistic sync/backup routines), and then silently updated their config on-the-fly.
* ini spawning programs include CPU-Z, HWMon, HWiNFO, BulkRenameUtility, HxD (newer versions spawn a settings folder), seemingly every NirSoft + O&O tool - and the master of all spawners: explorer.exe dropping desktop.ini's.
Thinking more, Microsoft should definitely implement this as a standard feature. They should be able to implement it quite quickly, and then promote it as a win for Windows AND dotnet - and they need some wins!
So there would need to be standard defined, whereby the exe would basically embed a "protobuf" definition in it's header area, and then a maximally sized "message" could be tacked on to the end of the exe. In the Explorer>file-Properties screen, there could be a config tab that shows the current config (and maybe allows direct editing), plus buttons for import/export/clear config. And as part of the standard, options could be defined as public/shared or private, and thus private fields would get encrypted by the OS/TPM, which means sharing an exe with sensitive info embedded would "not be a risk". The config tab could even have a "meta" option for things like "config changes update this executables modified date" (again for the sync/backup aspect).
# make a 6 second long video that alternates from green to red every second.
ffmpeg -f lavfi -i "color=red[a];color=green[b];[a][b]overlay='mod(floor(t)\,2)*w'" -t 6 master.mp4; # creates 150 frames @ 25fps.
# try make a 1 second clip starting at 0sec. it should be all green.
ffmpeg -ss 0 -i "master.mp4" -t 1 -c copy "clip1.mp4"; # exports 27 frames. you see some red.
ffmpeg -ss 0 -t 1 -i "master.mp4" -c copy "clip2.mp4"; # exports 27 frames. you see some red.
ffmpeg -ss 0 -to 1 -i "master.mp4" -c copy "clip3.mp4"; # exports 27 frames. you see some red.
# -t and -to stop after the limit, so subtract a frame. but that leaves 26...
# so perhaps offset the start time so that frame#0 is at 0.04 (ie, list starts at 1)?
ffmpeg -itsoffset 0.04 -ss 0 -i "master.mp4" -t 0.96 -c copy "clip4.mp4"; # exports 25 frames, all green, time = 1.00. success.
# try make another 1 second clip starting at 2sec. it should be all green.
ffmpeg -itsoffset 0.04 -ss 2 -i "master.mp4" -t 0.96 -c copy "clip5.mp4"; # exports 75 frames, time = 1.08, and you see red-green-red.
# maybe don't offset the start, and drop 2 at the end?
ffmpeg -ss 2 -i "master.mp4" -t 0.92 -c copy "clip6.mp4"; # exports 75 frames, time = 1.08, and you see green-red.
ffmpeg -ss 2 -t 0.92 -i "master.mp4" -c copy "clip7.mp4"; # exports 75 frames, time = 0.92, and you see green-red.
# try something different...
ffmpeg -ss 2 -i "master.mp4" -c copy -frames 25 "clip8.mp4"; # video is broken.
ffmpeg -ss 2 -i "master.mp4" -c copy -frames 25 -avoid_negative_ts make_zero "clip9.mp4"; # exports 25 frames, all green, time = 1.00. success?
# try export a red video the same way.
ffmpeg -ss 3 -i "master.mp4" -c copy -frames 25 -avoid_negative_ts make_zero "clip10.mp4"; # oh no, it's all green!
I've never tried doing frame perfect clips like that, that does sound annoying. But from a cursory read of the source, I don't think this program will solve that issue either? Because the time stamps in your examples are all correct, and the TUI is using ffmpeg with -ss and -t as well.
I think the best way of getting frame accurate clips like that is putting the starting time after the input (or rather before the output), which decodes the video up to that time, and reencode it instead of copying. Both of these commands gives the expected output:
Yer, I noticed that this tool was just doing `-ss -i -t` from its demo gif, which is what prompted me to reply. I'm sure people will discover that all sorts of problems will manifest if they don't start a lossless clip on a keyframe. One such scenario is when you make a clip that plays perfect on your PC, but then you send it someone over FB Messenger, and all of a sudden there's a few seconds of extra video at the start!
Can't make frame perfect cuts without re-encoding, unless your cut points just so happen to be keyframe aligned.
There are incantations that can dump for you metadata about the individual packets a given video stream is made up of, ordered by timecode. That way you can sanity check things.
This is terribly frustrating. The paths of least resistance either lead to improper cuts or wasteful re-encoding. Re-encoding just until the nearest keyframe I'm sure is also possible, but yeah, this does suck, and the tool above doesn't seem to make this any more accessible either according to the sibling comment.
> Re-encoding just until the nearest keyframe I'm sure is also possible
Yer, I've done that, and it's a pain to do "manually" (ie, without having a script ready to do it for you). I've also manually sliced the bitstream to re-insert the keyframe, which if applied to my clip5.mp4 example, could potentially reduce the 50* negative ts frames to maybe 2 or 3. It would be easier if there were tools that could "unpack" and "repack" the frames within the bitstream, and allow you to modify "pointers"/etc in the process - but I don't know of any such thing.
For frame perfect cuts you need to re-encode. You can use lossless H264 encoding for intermediary cuts before the final one so that you don't unnecessarily degrade quality.
I wonder if there is a solution which would just copy the pieces in between the starting and ending points while only re-encoding the first and last piece as required.
> On December 15, 2025 Canada enacted "Bill C-3", granting citizenship to people born before Dec. 15, 2025 with ANY level of Canadian ancestry they can document. (It used to be a "first generation limit")
> ancestors domiciled in the former colony of Newfoundland are still considered as Canadian born or naturalized for the purpose of citizenship by descent.
> December 15, 2025 Canada enacted "Bill C-3", granting citizenship to people born before Dec. 15, 2025 with ANY level of Canadian ancestry they can document. (It used to be a "first generation limit")
This is misleading.
Outside the first generation, the Canadian parent must have spent 3 years cumulatively in Canada prior to the birth, otherwise the child will not be a citizen. That's not a threshold you're likely to meet with a few holiday trips here and there.
I’m not sure Canada is doing well right now. Young people are really struggling and we are dealing with housing crisis. There is also trade conflicts with the United States.
An anti immigration sentiment has also taken over half the country due to rising costs and shortages, which is trickling down to various aspects of the life here.
The harsh weather is not pleasant either. Ironically, young Canadians are looking to move elsewhere.
> - Configuring the python client with a json string that did not seem to have a documented schema
I'm far from an expert, yet I came to believe that what you've described is basically "code smell". And the smell probably comes from seemingly innocuous things like enum's.
And you wondered if the solution was using Go, but no, it isn't. I was actually Go at the time myself (this was a few years ago, and I used Twirp instead of Protobuf) - but I realised that RDBMS > "Server(Go)" layer had quirks, and then the "Server(Go)" > "API(JS)" had other quirks -- and so I realised that you may as well "splat" out every attribute/relationship. Because ultimately, that's the problem...
Eg: is it a null field, or undefined, or empty, or false, or [], or {}? ...
The first link makes the problem sound like it can happen to anyone, but then when you tease out the details;
* Toxicity resulting from lack of monitoring is frequently seen in patients requiring high doses to treat ailments like osteoporosis, renal osteodystrophy, psoriasis, gastric bypass surgery, celiac, or inflammatory bowel disease.
* Patients who are on high doses of Vitamin D and taking inadvertently increased amounts of highly fortified milk are also at increased risk for vitamin D toxicity.
* According to the latest report from America's Poison Centers (APC), there were 11,718 cases of vitamin D exposure recorded in the National Poison Data System. More than half of these cases were in children younger than 5 years.
* The clinical signs and symptoms of vitamin D toxicity manifest from hypercalcemia's effects.
* Clinical management of vitamin D toxicity is mainly supportive and focuses on lowering calcium levels.
* Isotonic saline should be used to correct dehydration and increase renal calcium clearance.
A lot of those point to people drinking too much milk! (enriched milk)
* People with osteoporosis thinking "I better drink more milk for strong bones" when they are already on supplements/medicine.
* Kids drinking lots of milk and presumably not drinking any water - hence the dehydration.
PS: There are a lot of people out there that don't drink any water, and stick to juice or milk or soda, etc. They are not always fat, but that doesn't mean they don't have issues.
I've read the article by now and I like it. It's balanced, more so than the comment section made me think.
And my takeaway is not that everyone should be taking 10k IE, but it's a great reminder to be more consistent in taking my Vitamin capsules in winter.
I'm still standing by my point that it's "easy" to overdose on Vitamin D. Like the article already mentions, one should remember possible kidney issues and not take insane doses of it.
What the recommended daily intake should be, I don't know.
The whole reason I'm commenting on this is I used to take one of the "top" antidepressants on this list.
And I am a skeptic of antidepressants, that doesn't mean I deny all positive effects in people who are prescribed them, of course.
For what it's worth, it's also easy to overdose on Venlafaxine. It's still considered safe.
Just an example to make clear that my comment was not a critique of taking Vitamin D in general.
I don't find the article's main point surprising though. That's the reason I'm taking Vitamin D, too. Doesn't mean that it's impossible to overdose, and this point is also important, because many people still think that it would be impossible to take too much of an vitamin or mineral. Thankfully, high-dose Vitamin A / retinol supplements are not as widespread.
> A statistical error in the estimation of the recommended dietary allowance (RDA) for vitamin D was recently discovered; in a correct analysis of the data used by the Institute of Medicine, it was found that 8895 IU/d was needed for 97.5% of individuals to achieve values ≥50 nmol/L. Another study confirmed that 6201 IU/d was needed to achieve 75 nmol/L and 9122 IU/d was needed to reach 100 nmol/L.
> This could lead to a recommendation of 1000 IU for children <1 year on enriched formula and 1500 IU for breastfed children older than 6 months, 3000 IU for children >1 year of age, and around 8000 IU for young adults and thereafter. Actions are urgently needed to protect the global population from vitamin D deficiency.
> ...
> Since 10 000 IU/d is needed to achieve 100 nmol/L [9], except for individuals with vitamin D hypersensitivity, and since there is no evidence of adverse effects associated with serum 25(OH)D levels <140 nmol/L, leaving a considerable margin of safety for efforts to raise the population-wide concentration to around 100 nmol/L, the doses we propose could be used to reach the level of 75 nmol/L or preferably 100 nmol/L.
About 2 years ago I was using Whisper AI locally to translate some videos, and "hallucinations" is definitely the right phrase for some of its output! So just like you might expect from a stereotypical schizo: it would stay on-task for a while, but then start ranting about random things, or "hearing things", etc.
reply