• 0 Posts
  • 46 Comments
Joined 10 months ago
cake
Cake day: December 29th, 2023

help-circle
  • I feel (and I’m no doctor) was that it was already too late by visit 3.

    perhaps, but even the other visits it seems the doctors were cagey around pregnancy - that’s what this kind of law does - it dissuades doctors from considering things because they’re worried about repercussions

    if the first 2 doctors had come to the conclusion that it was pregnancy related sepsis and that abortion is the only option, well now they’re in a real hard position - to let the patient get worse and worse in front of them and then likely take all the blame when things go downhill FAST? or “misdiagnose” and send her on her way for someone else to deal with?

    the first is a lot of personal risk; the 2nd is minimal risk… is it selfish? absolutely! but humans act selfishly - thats just how we’re wired, and laws can’t just decide to make people act differently



  • Though he had already performed an ultrasound, he was asking for a second.

    The first hadn’t preserved an image of Crain’s womb in the medical record. …

    The state’s laws banning abortion require that doctors record the absence of a fetal heartbeat before intervening with a procedure that could end a pregnancy. Exceptions for medical emergencies demand physicians document their reasoning. “Pretty consistently, people say, ‘Until we can be absolutely certain this isn’t a normal pregnancy, we can’t do anything, because it could be alleged that we were doing an abortion,’” said Dr. Tony Ogburn, an OB-GYN in San Antonio.

    the delays at the 3rd hospital were almost entirely attributable to Texas abortion law.

    the problem with blaming doctors for fobbing off “hard cases that they simply don’t want to deal with” as you put it, is that they shouldn’t be hard cases - they have to think about more than what’s good for the patient, and that’s kinda ridiculous



  • 2 pass will encode a file once, and store a log of information about what it did… then on the 2nd pass it’ll use that information to better know when it should use more or less bitrate/keyframes - honestly i’m not too sure of the specifics here

    now, it’s most often used to keep a file to a particular file size rather than increasing quality per se, but id say keeping a file to a particular size means you’re using the space that you have effectively

    looks like with ffmpeg you do need to run it twice - there’s a log option

    i mostly export from davinci resolve so i’m not too well versed in ffmpeg flags etc

    doing a little more reading it seems the consensus is that spending more time on encoding (ie a higher preset) will likely give a better outcome than 2 pass unless you REALLY care about file size (like the file MUST be less than, but as close to 100mb)


  • if you’re planning on editing it, you can record in a very high bitrate and re-encode after the fact… yes, re-encoding looses some quality, however you’re likely to end up with a far better video if you record and 2x the h264 bitrate and then re-encode to your final h265 (or av1) bitrate than if you just record straight to h264 at your final bitrate

    another note on this: lots of streaming stuff will say to use CBR (constant bitrate), which is true for streaming, however i think probably for re-encode VBR (variable bitrate) with multi-pass encode will give a good trade-off - CBR for live because the encoding software can’t predict what’s coming up, but when you have a known video it can change bitrate up and down because it knows when it’ll need higher bitrate