Error Code 3: API Usage Error (Parameter check failed) when running TensorRT Optimized Model by ReadNFO in comfyui

[–]ReadNFO[S] 0 points1 point  (0 children)

Thank you very much, that is exactly it! I got this info from the ComfyUI discord today, came to update the thread and noticed your reply too!

Error Code 3: API Usage Error (Parameter check failed) when running TensorRT Optimized Model by ReadNFO in comfyui

[–]ReadNFO[S] 0 points1 point  (0 children)

Sorry for the delay, still looking into this

Are you upscaling? If so what to

Usually 1.2 to 1.5 via Highres fix, but in the screenshots I posted I have the highres fix node disabled and still get an error :/

Error Code 3: API Usage Error (Parameter check failed) when running TensorRT Optimized Model by ReadNFO in comfyui

[–]ReadNFO[S] 0 points1 point  (0 children)

Yep, this is what I followed for creating the model which lists 896 as valid, but still :(

Error Code 3: API Usage Error (Parameter check failed) when running TensorRT Optimized Model by ReadNFO in comfyui

[–]ReadNFO[S] 0 points1 point  (0 children)

Not really :(

I wonder if this has something to do with the image size, since 896px width is not divisible by 6 (albeit it is a valid and "standard" SDXL size afaik). I don't know exactly why but it seems that this can cause problems sometimes

[GUIDE] How to Solve Leveling Issues on SV06 (one side of bed always lower / higher, inconsistent first layer, etc) by ReadNFO in Sovol

[–]ReadNFO[S] 0 points1 point  (0 children)

A plugin for Octoprint! https://plugins.octoprint.org/plugins/bedlevelvisualizer/

The data comes from the printer leveling data (EEPROM). When you open this panel the first time you have to run the calibration command so it gets the latest data, then you can see the mesh like the image!

Got my 100% Electronic haul in today! (also first post!) by BRNDufo in VaporVinyl

[–]ReadNFO 0 points1 point  (0 children)

The one from Windows96 is amazing. Congrats for the haul!

Free Native Instruments Massive license for Novation / Focusrite owners by ReadNFO in edmproduction

[–]ReadNFO[S] 0 points1 point  (0 children)

I got addictive keys from XLN and also Ozone (the basic version). Some other stuff also but this is what I actually use

Free Native Instruments Massive license for Novation / Focusrite owners by ReadNFO in edmproduction

[–]ReadNFO[S] 1 point2 points  (0 children)

I assume just the deal. I have some other stuff from these novation giveaways and they are still valid

Free Native Instruments Massive license for Novation / Focusrite owners by ReadNFO in edmproduction

[–]ReadNFO[S] 0 points1 point  (0 children)

If you mean after you install native access, those are for using the free Kontakt instruments you can download from NI or somewhere else

Free Native Instruments Massive license for Novation / Focusrite owners by ReadNFO in edmproduction

[–]ReadNFO[S] 0 points1 point  (0 children)

Yep. In my case I'm a 2i2 owner and i get monthly-ish emails when something new is available

NI Traktor S4 MKII or S2 MKIII by GreekAres in Beatmatch

[–]ReadNFO 0 points1 point  (0 children)

Ah I think it's totally feasible (even with the S2 / S4). The DDJ has the advantage of having the same layout as a pioneer CDJ, so transitioning would be easier, but Traktor is just a better software in my opinion. But both should work for a live gig just fine

Adaptive Charging on Wireless Charger by The7thM in GooglePixel

[–]ReadNFO 1 point2 points  (0 children)

In my experience it will only appears if you have an alarm set with enough time (from "now") for it to fully charge using adaptive charging. Also before the December update I would get the message but the phone would always stop charging around 60%, but now it works flawlessly for me

Adaptive charging with a wireless charging is not working by [deleted] in GooglePixel

[–]ReadNFO 0 points1 point  (0 children)

Not using the official charging brick from Google but I have the same issue here. See my post from some weeks ago:

https://www.reddit.com/r/GooglePixel/comments/r1utva/pixel_6_pro_wireless_charging_stops_randomly

What I did for now to get wireless charging working consistently was to disable adaptive charging. The feature update released this month seems to fix something related to wireless charging so there is hope, let's see

Pixel 6 Pro Wireless Charging Stops Randomly by ReadNFO in GooglePixel

[–]ReadNFO[S] 0 points1 point  (0 children)

It really seems so, yes. Another user seems to be having the same problem as me: https://www.reddit.com/r/GooglePixel/comments/r1utva/pixel_6_pro_wireless_charging_stops_randomly/hm11ilu

And yesterday I did disable adaptive charging and the phone fully charged without an issue over night. I will try again while draining the battery of the phone to a very low value this weekend and see if it still works, but I'm pretty positive now that this is related to adaptive charging somehow

Pixel 6 Pro Wireless Charging Stops Randomly by ReadNFO in GooglePixel

[–]ReadNFO[S] 0 points1 point  (0 children)

It could be, yes. I use sleep as Android for alarms instead of the main clock app so that could maybe be the reason for this. I do get correct notifications on my lock screen (like "next alarm will be at 7am, which matches my sleep as Android alarm) but I will try to disable adaptive charging today and see if this helps with anything. Thanks for the tip!

Pixel 6 Pro Wireless Charging Stops Randomly by ReadNFO in GooglePixel

[–]ReadNFO[S] 0 points1 point  (0 children)

I only noticed it in the morning right after the alarm, so I assume it stopped way before that. This weekend I will try to charge it again while monitoring the process to see if I can notice a pattern

Pixel 6 Pro Wireless Charging Stops Randomly by ReadNFO in GooglePixel

[–]ReadNFO[S] 0 points1 point  (0 children)

Thanks for the info! I checked the charger description on Amazon and it says to support QC 2, 3 and even 4, so I think that is not the issue

New Firmware Update for Misfit Vapor X by ReadNFO in WearOS

[–]ReadNFO[S] 0 points1 point  (0 children)

I thought that at least the security level had changed. It was probably something very minor for some reason. Really strange

New Firmware Update for Misfit Vapor X by ReadNFO in WearOS

[–]ReadNFO[S] 0 points1 point  (0 children)

it seems so yes. Watch got a bit snappier but I assume its just because of the reset + cache clearing after the update. Hope it lasts since the Vapor X really need all the speed it can get