#qsv — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #qsv, aggregated by home.social.
-
Wrote my first :rust: #Rust program today. A small utility to grab the last value of a matching column in a matching csv file. I had hacked something together with #qsv, #nushell and #python, but those were all too slow for fast repeated calls. This Rust version executes 10-100x faster: a few ms on a :raspberrypi: #RaspberryPi 4, neat! 👌
Rust and :nixos: #nix is also a match made in heaven, omg is the experience better than Python 🫠
$ csvget scd30 co2
940.66 -
Comment on this video (which us not shown on my Fedi instance, yay federation!)
https://tube.kockatoo.org/w/63cGWTvhzqu2bwMGsh3QcF
I cannot believe that that GPU is not usable for video work. That is what GPUs are made for!
Poorly, there are a few caveats:
- there are always more DEcoders supported than ENcoders. I guess not being able to play a video (it would play but be less efficiently decoded on the CPU) is worse than being bound to #h265 instead of #av1 for recording.
- thus it makes sense that GPUs generally work flawlessly for gaming, as that is just displaying videos (or rendering content, which is kinda different, no idea why video codecs are more difficult than rendering methods)
- for every video format out there exists an encoder. If you use software rendering (on the CPU), you can use ANYTHING. Like encode to modern (and free!) AV1 using #svtav1 on any old CPU.
- if you want to encode videos on a GPU, you need drivers, but also a different encoder. On #NVIDIA you use #NVENC (NVidia ENCoder), for example nvenc_x265 for h265/HEVC videos. On #IntelArc (and afaik AMD GPUs), you use the #QSV (quick sync video) library which builds on top of #VAAPI, which is open source. So you can encode to AV1 using qsv_av1 for example.What encoders are supported depends on the GPU a lot. Intel Arc seems to have supported the free, efficient and future-proof AV1 codec the earliest, but also the older free codecs VP9 and VP8 (also used in webm), like in a GPU I recently bought used. My older NVIDIA GPU only supports H265, which is proprietary and often less efficient than AV1 (not always, video codecs are black magic).
As OBS can use your GPU for video capture (encoding), the issue is purely in software support.
I only have experience with #ffmpeg for re-encoding videos, but that is also in many video editing tools. Try if you can get them somehow.
For NVIDIA I needed the latest proprietary drivers (#NixOS makes this extremely easy, can recommend) and ffmpeg, nvenc worked out of the box.
For intel Arc I used the regular drivers included in the kernel, but after adding the QSV runtime to my "hardware.graphics.extraPackages" I needed to recompile the entire kernel. Using a #longterm kernel (currently 6.18) makes this more viable... longterm XD.
-
Comment on this video (which us not shown on my Fedi instance, yay federation!)
https://tube.kockatoo.org/w/63cGWTvhzqu2bwMGsh3QcF
I cannot believe that that GPU is not usable for video work. That is what GPUs are made for!
Poorly, there are a few caveats:
- there are always more DEcoders supported than ENcoders. I guess not being able to play a video (it would play but be less efficiently decoded on the CPU) is worse than being bound to #h265 instead of #av1 for recording.
- thus it makes sense that GPUs generally work flawlessly for gaming, as that is just displaying videos (or rendering content, which is kinda different, no idea why video codecs are more difficult than rendering methods)
- for every video format out there exists an encoder. If you use software rendering (on the CPU), you can use ANYTHING. Like encode to modern (and free!) AV1 using #svtav1 on any old CPU.
- if you want to encode videos on a GPU, you need drivers, but also a different encoder. On #NVIDIA you use #NVENC (NVidia ENCoder), for example nvenc_x265 for h265/HEVC videos. On #IntelArc (and afaik AMD GPUs), you use the #QSV (quick sync video) library which builds on top of #VAAPI, which is open source. So you can encode to AV1 using qsv_av1 for example.What encoders are supported depends on the GPU a lot. Intel Arc seems to have supported the free, efficient and future-proof AV1 codec the earliest, but also the older free codecs VP9 and VP8 (also used in webm), like in a GPU I recently bought used. My older NVIDIA GPU only supports H265, which is proprietary and often less efficient than AV1 (not always, video codecs are black magic).
As OBS can use your GPU for video capture (encoding), the issue is purely in software support.
I only have experience with #ffmpeg for re-encoding videos, but that is also in many video editing tools. Try if you can get them somehow.
For NVIDIA I needed the latest proprietary drivers (#NixOS makes this extremely easy, can recommend) and ffmpeg, nvenc worked out of the box.
For intel Arc I used the regular drivers included in the kernel, but after adding the QSV runtime to my "hardware.graphics.extraPackages" I needed to recompile the entire kernel. Using a #longterm kernel (currently 6.18) makes this more viable... longterm XD.
-
Comment on this video (which us not shown on my Fedi instance, yay federation!)
https://tube.kockatoo.org/w/63cGWTvhzqu2bwMGsh3QcF
I cannot believe that that GPU is not usable for video work. That is what GPUs are made for!
Poorly, there are a few caveats:
- there are always more DEcoders supported than ENcoders. I guess not being able to play a video (it would play but be less efficiently decoded on the CPU) is worse than being bound to #h265 instead of #av1 for recording.
- thus it makes sense that GPUs generally work flawlessly for gaming, as that is just displaying videos (or rendering content, which is kinda different, no idea why video codecs are more difficult than rendering methods)
- for every video format out there exists an encoder. If you use software rendering (on the CPU), you can use ANYTHING. Like encode to modern (and free!) AV1 using #svtav1 on any old CPU.
- if you want to encode videos on a GPU, you need drivers, but also a different encoder. On #NVIDIA you use #NVENC (NVidia ENCoder), for example nvenc_x265 for h265/HEVC videos. On #IntelArc (and afaik AMD GPUs), you use the #QSV (quick sync video) library which builds on top of #VAAPI, which is open source. So you can encode to AV1 using qsv_av1 for example.What encoders are supported depends on the GPU a lot. Intel Arc seems to have supported the free, efficient and future-proof AV1 codec the earliest, but also the older free codecs VP9 and VP8 (also used in webm), like in a GPU I recently bought used. My older NVIDIA GPU only supports H265, which is proprietary and often less efficient than AV1 (not always, video codecs are black magic).
As OBS can use your GPU for video capture (encoding), the issue is purely in software support.
I only have experience with #ffmpeg for re-encoding videos, but that is also in many video editing tools. Try if you can get them somehow.
For NVIDIA I needed the latest proprietary drivers (#NixOS makes this extremely easy, can recommend) and ffmpeg, nvenc worked out of the box.
For intel Arc I used the regular drivers included in the kernel, but after adding the QSV runtime to my "hardware.graphics.extraPackages" I needed to recompile the entire kernel. Using a #longterm kernel (currently 6.18) makes this more viable... longterm XD.
-
Comment on this video (which us not shown on my Fedi instance, yay federation!)
https://tube.kockatoo.org/w/63cGWTvhzqu2bwMGsh3QcF
I cannot believe that that GPU is not usable for video work. That is what GPUs are made for!
Poorly, there are a few caveats:
- there are always more DEcoders supported than ENcoders. I guess not being able to play a video (it would play but be less efficiently decoded on the CPU) is worse than being bound to #h265 instead of #av1 for recording.
- thus it makes sense that GPUs generally work flawlessly for gaming, as that is just displaying videos (or rendering content, which is kinda different, no idea why video codecs are more difficult than rendering methods)
- for every video format out there exists an encoder. If you use software rendering (on the CPU), you can use ANYTHING. Like encode to modern (and free!) AV1 using #svtav1 on any old CPU.
- if you want to encode videos on a GPU, you need drivers, but also a different encoder. On #NVIDIA you use #NVENC (NVidia ENCoder), for example nvenc_x265 for h265/HEVC videos. On #IntelArc (and afaik AMD GPUs), you use the #QSV (quick sync video) library which builds on top of #VAAPI, which is open source. So you can encode to AV1 using qsv_av1 for example.What encoders are supported depends on the GPU a lot. Intel Arc seems to have supported the free, efficient and future-proof AV1 codec the earliest, but also the older free codecs VP9 and VP8 (also used in webm), like in a GPU I recently bought used. My older NVIDIA GPU only supports H265, which is proprietary and often less efficient than AV1 (not always, video codecs are black magic).
As OBS can use your GPU for video capture (encoding), the issue is purely in software support.
I only have experience with #ffmpeg for re-encoding videos, but that is also in many video editing tools. Try if you can get them somehow.
For NVIDIA I needed the latest proprietary drivers (#NixOS makes this extremely easy, can recommend) and ffmpeg, nvenc worked out of the box.
For intel Arc I used the regular drivers included in the kernel, but after adding the QSV runtime to my "hardware.graphics.extraPackages" I needed to recompile the entire kernel. Using a #longterm kernel (currently 6.18) makes this more viable... longterm XD.
-
Die falschen Registry Einträge habe ich mit #regedit korrigiert:
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Intel\MediaSDK\Dispatch\iKBL_5916]
"DeviceID"=dword:00005916
"VendorID"=dword:00008086
"APIVersion"=dword:00000108
"Merit"=dword:08000015
"Path"="C:\\Program Files\\Intel\\Media SDK\\libmfxhw32.dll"und analog mit 64. Die #libmfxhw werden so verwendet, wie Intel sich das mit #QSV damals vorgestellt hat. Verifiziert mit #ffmpeg 4.Aug.2021 von ottverse. Für moderne Zwecke ist das irrelevant
-
Wir haben heute Nachmittag einige Domains und E-Mail Adressen, welche in den letzten Wochen negativ durch Spam und Phishing aufgefallen sind, Serverweit gesperrt. Darunter sind auch ein gutes Dutzend E-Mail Adressen unserer Lieblings-Spamers Gmail.
Wir wünschen ein gutes Wochenende! -
Done this with the #AMD 5600G's iGPU, now testing #Jellyfin hardware transcoding with my #Intel #ArcA380 GPU - one question though, is it normal for CPU usage to be rather high at least in the early parts of streaming (while transcoding), even with hardware transcoding?
I'm just trying to figure out if it is actually hardware transcoding - I'm assuming it is, bcos on the admin dashboard I'm seeing that it's transcoding as AV1 and I'm sure my Ryzen 7 1700 would not be able to do/handle that, esp considering that I'm testing with 4 streams playing concurrently? but the CPU usage is rather high the first minute or two or more from when the stream starts, it does lower down afterwards - the video playback is perfectly fine, no stuttering or anything like that.
My method of passthrough is the same as I did with the 5600G, that is a simple passthrough to the #LXC container, then to the #Docker container running Jellyfin. I don't think I noticed this high CPU usage when testing the 5600G, and the only minor configuration difference between the two was I'd used #VAAPI with the 5600G and disabled #AV1 encoding (since idt it supports it), while on the Arc A380 GPU I'm using Intel's #QSV and have enabled AV1 encoding.
Am I correct to assume that hardware transcoding is indeed working? Cos again, I'm quite certain my Ryzen 7 1700 would definitely NOT be able to handle this lol esp since I only give the LXC container 2 cores. -
Just published a new version of csv-diff (v0.1.1) 🚀
https://lib.rs/crates/csv-diff
This fixes a nasty bug regarding sort order of modified csv records. 😖
Details in the MR/PR:
https://gitlab.com/janriemer/csv-diff/-/merge_requests/31Also, two new incoming PRs for #qsv, the #CSV toolkit:
The first updates to the latest csv-diff, fixing aforementioned bug:
https://github.com/dathere/qsv/pull/2456The second fixes a bug regarding conversion from column names to indices:
https://github.com/dathere/qsv/pull/2457 -
Just published a new version of csv-diff (v0.1.1) 🚀
https://lib.rs/crates/csv-diff
This fixes a nasty bug regarding sort order of modified csv records. 😖
Details in the MR/PR:
https://gitlab.com/janriemer/csv-diff/-/merge_requests/31Also, two new incoming PRs for #qsv, the #CSV toolkit:
The first updates to the latest csv-diff, fixing aforementioned bug:
https://github.com/dathere/qsv/pull/2456The second fixes a bug regarding conversion from column names to indices:
https://github.com/dathere/qsv/pull/2457 -
Just published a new version of csv-diff (v0.1.1) 🚀
https://lib.rs/crates/csv-diff
This fixes a nasty bug regarding sort order of modified csv records. 😖
Details in the MR/PR:
https://gitlab.com/janriemer/csv-diff/-/merge_requests/31Also, two new incoming PRs for #qsv, the #CSV toolkit:
The first updates to the latest csv-diff, fixing aforementioned bug:
https://github.com/dathere/qsv/pull/2456The second fixes a bug regarding conversion from column names to indices:
https://github.com/dathere/qsv/pull/2457 -
Just published a new version of csv-diff (v0.1.1) 🚀
https://lib.rs/crates/csv-diff
This fixes a nasty bug regarding sort order of modified csv records. 😖
Details in the MR/PR:
https://gitlab.com/janriemer/csv-diff/-/merge_requests/31Also, two new incoming PRs for #qsv, the #CSV toolkit:
The first updates to the latest csv-diff, fixing aforementioned bug:
https://github.com/dathere/qsv/pull/2456The second fixes a bug regarding conversion from column names to indices:
https://github.com/dathere/qsv/pull/2457 -
Just published a new version of csv-diff (v0.1.1) 🚀
https://lib.rs/crates/csv-diff
This fixes a nasty bug regarding sort order of modified csv records. 😖
Details in the MR/PR:
https://gitlab.com/janriemer/csv-diff/-/merge_requests/31Also, two new incoming PRs for #qsv, the #CSV toolkit:
The first updates to the latest csv-diff, fixing aforementioned bug:
https://github.com/dathere/qsv/pull/2456The second fixes a bug regarding conversion from column names to indices:
https://github.com/dathere/qsv/pull/2457 -
Bah. Looks like have hit the limits of the P400’s NVENC transcoder; hit rates below 1.00x for first time... it's put in a few years.
The P400 RAM usage is about 1 gb with 4 streams, but 100% on encode/decode. The P400 has 1 Pascal (6th gen) nvenc block and 2gb RAM.
Have an Arc A380 coming in now.
A380 should be able to handle quite a bit more, has two MFX engines (quicksync) & 6gb RAM.
Time will tell.
-
Ouch, there is another bug and this time it is actually _in #CSVDiff itself_!
It happens with sorting the results of modified rows (urgh, I'm also not happy with the sorting code).😨
Thankfully, datatraveller1 already has found a reproducible example - thank you so much! ❤️
Bug:
https://github.com/dathere/qsv/issues/2443#issuecomment-2598987465I think I already found a solution, but needs rigorous testing first!
Potential solution:
https://github.com/dathere/qsv/issues/2443#issuecomment-2599681431 -
Ouch, there is another bug and this time it is actually _in #CSVDiff itself_!
It happens with sorting the results of modified rows (urgh, I'm also not happy with the sorting code).😨
Thankfully, datatraveller1 already has found a reproducible example - thank you so much! ❤️
Bug:
https://github.com/dathere/qsv/issues/2443#issuecomment-2598987465I think I already found a solution, but needs rigorous testing first!
Potential solution:
https://github.com/dathere/qsv/issues/2443#issuecomment-2599681431 -
Ouch, there is another bug and this time it is actually _in #CSVDiff itself_!
It happens with sorting the results of modified rows (urgh, I'm also not happy with the sorting code).😨
Thankfully, datatraveller1 already has found a reproducible example - thank you so much! ❤️
Bug:
https://github.com/dathere/qsv/issues/2443#issuecomment-2598987465I think I already found a solution, but needs rigorous testing first!
Potential solution:
https://github.com/dathere/qsv/issues/2443#issuecomment-2599681431 -
Ouch, there is another bug and this time it is actually _in #CSVDiff itself_!
It happens with sorting the results of modified rows (urgh, I'm also not happy with the sorting code).😨
Thankfully, datatraveller1 already has found a reproducible example - thank you so much! ❤️
Bug:
https://github.com/dathere/qsv/issues/2443#issuecomment-2598987465I think I already found a solution, but needs rigorous testing first!
Potential solution:
https://github.com/dathere/qsv/issues/2443#issuecomment-2599681431 -
Ouch, there is another bug and this time it is actually _in #CSVDiff itself_!
It happens with sorting the results of modified rows (urgh, I'm also not happy with the sorting code).😨
Thankfully, datatraveller1 already has found a reproducible example - thank you so much! ❤️
Bug:
https://github.com/dathere/qsv/issues/2443#issuecomment-2598987465I think I already found a solution, but needs rigorous testing first!
Potential solution:
https://github.com/dathere/qsv/issues/2443#issuecomment-2599681431 -
Nice, I think I found the bug! 🐛
See all the explanation and possible solution here:
=> https://github.com/dathere/qsv/issues/2443#issuecomment-2597097311
Workaround is also present and explained, so should be no blocker for people.
Will prob provide a fix on the weekend. 🤞
-
Nice, I think I found the bug! 🐛
See all the explanation and possible solution here:
=> https://github.com/dathere/qsv/issues/2443#issuecomment-2597097311
Workaround is also present and explained, so should be no blocker for people.
Will prob provide a fix on the weekend. 🤞
-
Nice, I think I found the bug! 🐛
See all the explanation and possible solution here:
=> https://github.com/dathere/qsv/issues/2443#issuecomment-2597097311
Workaround is also present and explained, so should be no blocker for people.
Will prob provide a fix on the weekend. 🤞
-
Nice, I think I found the bug! 🐛
See all the explanation and possible solution here:
=> https://github.com/dathere/qsv/issues/2443#issuecomment-2597097311
Workaround is also present and explained, so should be no blocker for people.
Will prob provide a fix on the weekend. 🤞
-
Nice, I think I found the bug! 🐛
See all the explanation and possible solution here:
=> https://github.com/dathere/qsv/issues/2443#issuecomment-2597097311
Workaround is also present and explained, so should be no blocker for people.
Will prob provide a fix on the weekend. 🤞
-
Uh ohhhh, someone reported a bug in qsv's `diff` command.😮 🙈
https://github.com/dathere/qsv/issues/2443
Hopefully, we can resolve this soon! 🤞🥺
I have a strong suspicion, but let's see... I need more info first from the OP.
-
Uh ohhhh, someone reported a bug in qsv's `diff` command.😮 🙈
https://github.com/dathere/qsv/issues/2443
Hopefully, we can resolve this soon! 🤞🥺
I have a strong suspicion, but let's see... I need more info first from the OP.
-
Uh ohhhh, someone reported a bug in qsv's `diff` command.😮 🙈
https://github.com/dathere/qsv/issues/2443
Hopefully, we can resolve this soon! 🤞🥺
I have a strong suspicion, but let's see... I need more info first from the OP.
-
Uh ohhhh, someone reported a bug in qsv's `diff` command.😮 🙈
https://github.com/dathere/qsv/issues/2443
Hopefully, we can resolve this soon! 🤞🥺
I have a strong suspicion, but let's see... I need more info first from the OP.
-
Uh ohhhh, someone reported a bug in qsv's `diff` command.😮 🙈
https://github.com/dathere/qsv/issues/2443
Hopefully, we can resolve this soon! 🤞🥺
I have a strong suspicion, but let's see... I need more info first from the OP.
-
Der Jahresausklang ist eine spannende Zeit: Das Vergangene Revue passieren lassen und mit Neugier auf das Kommende blicken.
-
#CsvDiff has finally reached v0.1.0, it's first ever non-alpha/-beta release! 🎉
New features like getting at the headers from the diffresult have been needed for the following PR in qsv (which is in final review):
https://github.com/jqnatividad/qsv/pull/1395When merged, you'll be able to decide, whether the diffresult should output headers or not (see examples in the PR). :awesome:
Check out csv-diff's Changelog for the full details:
https://gitlab.com/janriemer/csv-diff/-/blob/main/CHANGELOG.md?ref_type=heads#010-30-october-2023 -
#CsvDiff has finally reached v0.1.0, it's first ever non-alpha/-beta release! 🎉
New features like getting at the headers from the diffresult have been needed for the following PR in qsv (which is in final review):
https://github.com/jqnatividad/qsv/pull/1395When merged, you'll be able to decide, whether the diffresult should output headers or not (see examples in the PR). :awesome:
Check out csv-diff's Changelog for the full details:
https://gitlab.com/janriemer/csv-diff/-/blob/main/CHANGELOG.md?ref_type=heads#010-30-october-2023 -
#CsvDiff has finally reached v0.1.0, it's first ever non-alpha/-beta release! 🎉
New features like getting at the headers from the diffresult have been needed for the following PR in qsv (which is in final review):
https://github.com/jqnatividad/qsv/pull/1395When merged, you'll be able to decide, whether the diffresult should output headers or not (see examples in the PR). :awesome:
Check out csv-diff's Changelog for the full details:
https://gitlab.com/janriemer/csv-diff/-/blob/main/CHANGELOG.md?ref_type=heads#010-30-october-2023 -
#CsvDiff has finally reached v0.1.0, it's first ever non-alpha/-beta release! 🎉
New features like getting at the headers from the diffresult have been needed for the following PR in qsv (which is in final review):
https://github.com/jqnatividad/qsv/pull/1395When merged, you'll be able to decide, whether the diffresult should output headers or not (see examples in the PR). :awesome:
Check out csv-diff's Changelog for the full details:
https://gitlab.com/janriemer/csv-diff/-/blob/main/CHANGELOG.md?ref_type=heads#010-30-october-2023 -
#CsvDiff has finally reached v0.1.0, it's first ever non-alpha/-beta release! 🎉
New features like getting at the headers from the diffresult have been needed for the following PR in qsv (which is in final review):
https://github.com/jqnatividad/qsv/pull/1395When merged, you'll be able to decide, whether the diffresult should output headers or not (see examples in the PR). :awesome:
Check out csv-diff's Changelog for the full details:
https://gitlab.com/janriemer/csv-diff/-/blob/main/CHANGELOG.md?ref_type=heads#010-30-october-2023 -
I can't reproduce the bug. ¯\_(ツ)_/¯
Neither in #CsvDiff ...
https://gitlab.com/janriemer/csv-diff/-/commit/0ac6ba724656dbcc620eefda3f8ec5d8064134d6...nor in #qsv
https://github.com/jqnatividad/qsv/pull/1297My assumption is that they have forgotten to specify the option --right-delimiter (or --left-delimiter, respectively), when executing `qsv diff`:
https://github.com/jqnatividad/qsv/issues/1258#issuecomment-1712842883Anyway, we now have additional tests in csv-diff and qsv, so definitely a win, regardless of the outcome! 🎉
@floriann FYI
-
I can't reproduce the bug. ¯\_(ツ)_/¯
Neither in #CsvDiff ...
https://gitlab.com/janriemer/csv-diff/-/commit/0ac6ba724656dbcc620eefda3f8ec5d8064134d6...nor in #qsv
https://github.com/jqnatividad/qsv/pull/1297My assumption is that they have forgotten to specify the option --right-delimiter (or --left-delimiter, respectively), when executing `qsv diff`:
https://github.com/jqnatividad/qsv/issues/1258#issuecomment-1712842883Anyway, we now have additional tests in csv-diff and qsv, so definitely a win, regardless of the outcome! 🎉
@floriann FYI
-
I can't reproduce the bug. ¯\_(ツ)_/¯
Neither in #CsvDiff ...
https://gitlab.com/janriemer/csv-diff/-/commit/0ac6ba724656dbcc620eefda3f8ec5d8064134d6...nor in #qsv
https://github.com/jqnatividad/qsv/pull/1297My assumption is that they have forgotten to specify the option --right-delimiter (or --left-delimiter, respectively), when executing `qsv diff`:
https://github.com/jqnatividad/qsv/issues/1258#issuecomment-1712842883Anyway, we now have additional tests in csv-diff and qsv, so definitely a win, regardless of the outcome! 🎉
@floriann FYI
-
I can't reproduce the bug. ¯\_(ツ)_/¯
Neither in #CsvDiff ...
https://gitlab.com/janriemer/csv-diff/-/commit/0ac6ba724656dbcc620eefda3f8ec5d8064134d6...nor in #qsv
https://github.com/jqnatividad/qsv/pull/1297My assumption is that they have forgotten to specify the option --right-delimiter (or --left-delimiter, respectively), when executing `qsv diff`:
https://github.com/jqnatividad/qsv/issues/1258#issuecomment-1712842883Anyway, we now have additional tests in csv-diff and qsv, so definitely a win, regardless of the outcome! 🎉
@floriann FYI
-
I can't reproduce the bug. ¯\_(ツ)_/¯
Neither in #CsvDiff ...
https://gitlab.com/janriemer/csv-diff/-/commit/0ac6ba724656dbcc620eefda3f8ec5d8064134d6...nor in #qsv
https://github.com/jqnatividad/qsv/pull/1297My assumption is that they have forgotten to specify the option --right-delimiter (or --left-delimiter, respectively), when executing `qsv diff`:
https://github.com/jqnatividad/qsv/issues/1258#issuecomment-1712842883Anyway, we now have additional tests in csv-diff and qsv, so definitely a win, regardless of the outcome! 🎉
@floriann FYI
-
::: OBS Studio | Streamers open source dream software - OBS 30 gets Intel Quick Sync Video on Linux :linux: 🎞️
#1 screen casting app's next release is in BETA still - so please help testing it!
All intricacies => https://github.com/obsproject/obs-studio/releases/tag/30.0.0-beta1
#OBS #Linux #QSV #WHIP #WebRTC #screencasting #streaming #desktop #Intel #development #testing #help
-
Souvent, les enseignantes et enseignants ne se sentent pas compétents, (in)formés, ou en sécurité pour aborder en classe les controverses de l’actualité: vaccination, climat et transitions énergétiques, identité sexuelle, consommation de viande, etc. Ces questions divisent et mobilisent. Comment faire, sans se mettre en danger ni délaisser les apprentissages disciplinaires?
#débat #vaccins #SVT #QSV #histoiregeographie #controverses
⏬
https://www.cahiers-pedagogiques.com/former-aux-controverses-et-a-les-resoudre/ -
Yay! Sorting the #csv diff result by columns has just been merged into #qsv! 🥳
-
New release of #qsv, the CSV toolkit, is out! 🎉
The `diff` command now sorts by line when no other sort option is given (before, order of diffresult was not stable across runs). 🧮 📃
This release also introduces a new command `joinp` - the first command that is powered by pola.rs! 🚀
Check the full release notes here:
https://github.com/jqnatividad/qsv/releases/tag/0.90.0#CSV #CLI #Terminal #Rust #RustLang #OpenSource #Data #DataScience #Polars
-
A new version of csv-diff is out (v0.1.0-beta.2) 🎉
https://lib.rs/crates/csv-diff
This version adds a method, which allows you to sort your diff result by columns (it was already possible to sort by lines).
See the changelog for an example:
https://gitlab.com/janriemer/csv-diff/-/blob/8642a8a7ba14e22d076cee8c3f690c17f41d7528/CHANGELOG.md#010-beta2-19-february-2023Sorting by columns will soon be integrated into qsv, the #CSV toolkit:
https://github.com/jqnatividad/qsv/issues/714Thank you @jqnatividad for the idea of this feature! 💚
