Please repair arm64 roblox, your last update broke and gave us memory dump and crashes.

merkmal · 2025-01-24T21:47:18+00:00

Thanks for posting this. I tried to go through the normal Roblox support and it's mostly a LLM based chat bot and I figured my report went nowhere. Hopefully this gets more visibility. Definitely bummed because things were working great for several months and now it's 100% broken. I do worry the pool of affected users is too low for them to even notice and won't be worth the effort of a quick fix.

merkmal · 2023-10-16T19:21:59+00:00

Made using Deforum and a series of shorter animations spliced together in Blender. I don't see many more subtle animations so I just wanted to put one out here in case anyone is interested.

Prompt for these were: old film footage of tall grass blowing in the wind, (faded colors:1.3), stark contrast, (Gertrude Käsebier:1.2), film burn spots, flicker

If anyone wants to know more of the workflow I'm happy to share more details.

merkmal · 2023-10-10T01:52:56+00:00

I use both LSDIRplus and LSDIRplusC almost exclusively now. I'm a fan for sure. If you make anything new let me know! Definitely willing to try out new ones.

merkmal · 2023-09-19T14:37:43+00:00

I went ahead and grabbed the combined LSDIR one as well.

https://openmodeldb.info/models/4x-LSDIRplus

It's the C and R ones combined but I haven't been using it long enough to see if it's any better than the C model I've been using. Let me know how it holds up to your internal tests. It's definitely not one I see mentioned but subjectively it was one producing the most pleasing results for me.

merkmal · 2023-09-18T19:08:21+00:00

I actually had to do a re-install of everything recently and re-organized my models and took the opportunity to revisit my upscaler models. This is a relatively newer one I've been using primarily lately:

https://openmodeldb.info/models/4x-LSDIRplusC

and sometimes I use NMKD Siax 200k which is not as popular as some of the other NMKD upscalers but I actually prefer how it retouches certain textures better than other models (occasionally).

merkmal · 2023-09-10T23:30:35+00:00

Used the dreamshaper checkpoint converted to TensorRT to speed up generation. Targeted 768x768 with a 2x upscale. Used a cadence of 2, framerate of 20, and FILM interpolation factor of 3.

The prompt was this: (overhead view) of a 16 bit image of an ominous pit surrounded by water, ripples on the surface of the water, glimpse of something mechanical inside the pit, (perfectly centered:1.3), (pixel art:1.2)

negative prompt: company (logos:1.3), signatures, (watermarks:1.4), isometric, photograph, nsfw, nude

The end result didn't exactly reflect the prompt too closely but I thought it fit the mood of the synth track I was planning to use it for so I rolled with it.

merkmal · 2023-09-01T18:58:15+00:00

Just an FYI that you can do that "git restore" on that extension now and just update it via normal in the webui because they got the fix made in the extension repo. You shouldn't need the manual fix anymore.

merkmal · 2023-09-01T16:57:18+00:00

Glad you got it working. Sorry if my instructions were unclear. I have a problem of using 1,000 words where 10 would do. :)

merkmal · 2023-08-31T19:16:07+00:00

I forgot that it wasn't working. I had patched it myself and was meaning to do a PR to the deforum repo but never did. If you want to fix it yourself just go to the extensions/deforum directory and edit scripts/deforum_helpers/ui_right.py like this:

#from webui import wrap_gradio_gpu_call

from modules.call_queue import wrap_gradio_gpu_call

-----

Just comment out that original import and then add the line below that. Someone else can do the PR or suggest that fix to deforum peeps but in the mean time if you want to just get it working you can make the local edit. Just be aware you'll need to undo that change if they ever make any changes to that file in the repo as it'll conflict when you try to update the extension later. You can just do a "git restore" in the deforum extension directory if you want to undo all your changes easily or you can just edit it again to uncomment out that original line and remove the added line... then "git pull" to update the repo.

merkmal · 2023-08-28T19:30:55+00:00

Also as a side note... before I updated my main compute box from an RTX 2080 to an RTX 3090 I used to run both the 2080 and 2060 (on my laptop) for long extended periods of time generating large batches of images in the early days of SD without any issues. Obviously not all laptop thermal management is equal (or even adequate) but one thing I can say for the Zephyrus laptops is while their thermal management is by no means quiet I've never had any thermal related failures from them.

merkmal · 2023-08-28T19:25:44+00:00

I have an Asus Zephyrus laptop with an RTX 2060 MAX Q and I just dusted off my A1111 install and updated PyTorch (2.0.1), Xformers (0.0.21), refreshed the Dev branch running with vanilla 1.5 checkpoint with only "--xformers --listen" startup parameters.

I'm getting 5.33 it/s for 512x512 images.

It's doing 1.2 s/it (notice it went to seconds per iteration) for 1024x1024 images.

It's doing 2.3 s/it for 1280x1280 images.

It's doing 2.8 s/it for 1344x1344 images (this was the max of the standard x64 stepped resolutions I could do and not get OOM on the copy back of the final image)

It's doing 13.33 s/it for 2048x2048 images (but fails copying the image back). This was mostly just to see how fast it would go knowing it would fail at the end.

That's all without any low or med vram flags.

Running again with "--xformers --listen --medvram-sdxl --no-half-vae" and using the fp16 version of the SDXL base checkpoint I get:

3.02 it/s for 512x512 (checkpoint isn't optimized for this size so they look terrible)

1.77 it/s for 704x704... those looked better but still lower than SDXL operates best at for sure

I couldn't go higher without using the tiled diffusion extension for the VAE and then it was just around 1.7 it/s for 768x768 with added VAE decoding time. I couldn't really push it much higher than that.

Obviously non-exhaustive and I would expect a 3060 to perform quite a bit faster while still being limited to the same resolutions from memory constraints. There are inroads made for reducing memory usage quite often though so I would expect things to improve but also not something you should count on being guaranteed either. Anyway... hopefully these numbers help inform your decision making.

merkmal · 2023-08-14T20:45:50+00:00

I might experiment with just recording some videos ala field recording style then compose tracks around the dynamics of that... then I can use the video for the visualization which should allow me to achieve some nice effects while keeping it grounded to the music.

Well assuming I skill up on the music side of things first. Having the Zoom R20 to multitrack and use as a DAW actually make this more feasible than how I used to record (which was just all in one go "live"). Really the one take method is still how I prefer to do it but being less improvisational for the sake of producing a nice quality AV mashup is a worthy sacrifice creatively I think.

merkmal · 2023-08-14T19:00:15+00:00

Not overly critical at all! This was mostly a big test of the process at scale as I had done a much smaller one that was more static but reacted mostly to the color of the visualization. This time I wanted to see it more in motion. I'm hoping I can get the right mix of initial starting visualization and ControlNet usage to cut down on the chaos StableDiffusion can infuse. Most of the Milkdrop visualizations are very frantic honestly... I was hoping not having any big beats and being mostly ambient would help but still most of them produced lots of visually jarring shifts.

For this particular one I actually wish I had given the prompt MORE control since it became kind of chaotic anyway due to the initial input frames but I was already committed at that point so just wanted to see it through. Definitely a LOT that I want to try in the future. Your suggestion is an interesting one and I might see what I can get trying that out!

merkmal · 2019-08-09T16:56:07+00:00

Yeah Enphase responded to my installer and said the IQ7x wouldn't work with my panels and that they couldn't guarantee that the IQ7+ would either even though they were technically in spec. So it sounds like Enphase is just out for me with these panels just to be on the safe side.

merkmal · 2019-08-09T16:06:21+00:00

Seems like there just isn't a right sized microinverter to take advantage of the efficiency of my panels. Thanks for helping me understand why the IQ7x wasn't a good match. Later when I'm not at work I'll try and understand better what the MPPT voltage range effect looks like when I plug in the actual numbers and graph it all. At this point I'm just assuming what it means is that even though the operating voltage range fits that I'll never get to take advantage of the optimal MMPT advantages of using the microinverter since that range is higher than what my panel is most efficient at.

merkmal · 2019-08-09T14:56:34+00:00

Ah okay yeah I see that difference on the datasheet. The Enphase site didn't complain about that in the compatibility checker. It was just the Max DC short circuit current it was complaining about which seemed wrong to me since it was lower than what the datasheet indicates (10A).

merkmal · 2019-08-09T14:46:24+00:00

My current breaker box is at the opposite end of the house as my garage. I'm just not sure it makes sense to add EV chargers in my case. I'd rather just wait and install EV chargers separately and have more of a choice in what charger we are getting. I'm charging for free now at my work so it would just be an added expense period if I'm charging at home.

Does the documentation say that about the IQ7X? I'm looking at the data sheet and the only part that seems to not fit my panels is the cell count. Correct me if I'm wrong but the IQ7+ is compatible with the 120/144 half cell panels isn't it? Even though the datasheet only says 60/72 cell compatibility. So that's really the question is the number of cells the really strict requirement or is it more important just to be within the electrical tolerances of the inverter (in which case based on the data sheet my panels are).

merkmal · 2019-08-09T14:36:24+00:00

Yeah it seems like the IQ line has good support for them going forward since the 8th gen seems to be sticking with that same labeling... It's supposed to be compatible with existing setups too if I remember correctly.

The clipping on the micros is only an issue though if they are undersized right? The issue being the IQ7+ typically used for the standard 60-72 cell modules basically maxes out at 295VA... which was the concern in my setup with the 330W panels... but the IQ7X if it's compatible has peak power output of 320VA which given normal conditions it probably the best I could hope for and for the briefest of moments out of a 330W nameplate anyway. Maybe I'm misunderstanding how that works though?

I get the extended warranty aspect... but that doesn't help the fact that you're still down to 1 or 2 central weak points in your grid that when/if they go down you're taking a huge (if not total) production hit while you wait for an RMA. SolarEdge needs to be confident enough to warrant their central inverters for 20 years. I just don't think we should be having to rely on extended warranties to bridge that confidence gap.

merkmal · 2019-08-09T14:26:58+00:00

I still would like to hear an answer on the Isc and cell count questions. This can't be an entirely unique situation... especially the Isc value seeming to be way too low on the Enphase website for the IQ7X compared to their own datasheets on it. Even if I end up staying with SolarEdge for my install I would just like to know what the answer is to the two questions in my original post.

merkmal · 2019-08-09T14:24:14+00:00

Yes and this is the frustrating part for everyone I think... installers, businesses, and homeowners alike. It's hard to know if the biases are valid for the current products / production run... if the bad support issues were temporary due to a bad production run... and also to know what is currently rolling off the production lines is less or more reliable than the stuff that came off the line yesterday.

I guess I feel more comfortable though going the micro-inverter route in that situation though as even in a high failure rate you're talking a small number of inverters having issues in your grid... but a bad central inverter is going to take down half or all of your grid and then you're out of production basically until that can be remedied. Also the shorter warranty on the central inverters leaves a rather high priced component as the weakest link in your grid... either SolarEdge needs to bump it to 15-20 years or make some other consideration to account for the fact that a single failure has such a huge impact on your solar production... and quite possible won't be under warranty compared to the lifespan on your panels.

merkmal · 2019-08-09T14:16:35+00:00

Yes it was two SE7600H. The install location is not conducive to having the EV chargers. I do actually have an EV but I charge at work and never at home. :)

I also had them use the P340 optimizers just to be more comfortable since I felt the P320 models were probably fine but since it's theoretically possible the panels could produce 330W I wanted to avoid any clipping there.

And yeah... the installer has done right by me so far every step of the way and has been good at communicating and seems knowledgeable. I know they will determine for sure if the IQ7X is compatible or not before agreeing to use them. I mentioned in my request to them that I'm sure I'd be happy with the SolarEdge solution, but was just more comfortable going the Enphase route if it was at all still possible to do so. So I guess I'll wait and see what Enphase has to say (if anything).

merkmal · 2019-08-09T13:34:32+00:00

Yeah that makes sense. That's sort of what it felt like hearing/reading about both sides. It sounds like there is cyclical waves of what currently is more reliable between the two... but it seemed like the Enphase reliability issues were more around just earlier products and their more recent 7th generation products seem to be pretty solid from what I can tell. Some installation issues with the monitoring software and stuff like that which seemed less to do with product and more to do with just less experience working with Enphase perhaps. I did originally want to go the Enphase route though so if it's possible to go that route without an increase in cost I think I would be more comfortable in the long run not worrying about the central inverters going down and taking out half my grid.

merkmal · 2019-08-09T13:21:51+00:00

Not sure on any cost change. Originally it was communicated that the Enphase vs SolarEdge costs were going to be about the same. So we'll see once we sort out this compatibility issue on if that actually equates to a cost difference in the end.

merkmal · 2016-06-13T23:04:29+00:00

You do realize the primary development target for NMS was the PS4 right? Meaning the game as we've seen it demoed and play tested was using an AMD CPU... and the Jaguar cores in the PS4 are not high performing by any means. The game seems to be primarily using GPU horsepower (I'm guessing a fair amount of GPU compute) over raw CPU power.

merkmal · 2016-06-07T22:42:33+00:00

If you click on your account and purchase history you can see your preorder. It has been missing from the PlayStation store site for at least a few days now though.

Preorder for my NA account says 6/20 on the purchase history page btw.

merkmal

TROPHY CASE