Jump to content
Search In
  • More options...
Find results that contain...
Find results in...


  • Content Count

  • Joined

  • Last visited


This user doesn't have any awards

1 Follower

About imbrock

  • Title

Profile Information

  • Gender
  • Location
    Kelowna BC
  • Interests
    Games and tech stuff obviously.
  • Occupation
    Graphic designer - Tombstones.

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. imbrock

    which keyboard should I get?

    I think that depends entirely on how much you use the G keys. From a technical standpoint, yes absolutely. But if you use those keys in every game you play, you might find the ducky a bit lacking.
  2. imbrock

    which keyboard should I get?

    Duckies are godly. I've got a shine 6 and I've been super happy. I've dumped a full glass of water on it, took it apart and blow dried it, worked fine. Dumped tea on it, took apart cleaned with cuetips and some rubbing alcohol and water blow dried it works great. Only complaint is that the switches are soldered in place. Had to RMA the first one I had because some lights werent working, RMA was quick and painless.
  3. I could see occasional pothole slamming eventually damaging parts like the gpu. I feel like mounting it in a way where there was a bit of flex or foam of some sort to allow the case to slow instead of just slamming would be your best bet. Aside from not having things slamming out of their hole I'm not sure about orientation being a problem
  4. imbrock

    Wireless Gaming

    I think your best bet for wireless gaming would be to use one of the streaming setups like steam in home streaming, nvidia game streaming, whatever microsofts baked in thing is. Find a small computer like a raspberry pi or something and mount it on the back of your monitor and set the whole thing up like that. Would be a bit more work but would work pretty seamlessly.
  5. My only complaint is that some of the coolest stuff has already been done. Multi gamers 1 cpu, so many mini pc's and pc's in consoles, all of which are my favourite types of videos, get harder and harder to do since they'res only so much you can escalate the situation.
  6. Yeah its a heck of a time to wait to see if the changes fixed anything. I think it may be combining the loading times and the processing times, though there is a chance the github user content media bits are accessed a bit slower than most things we're used to. Yeah the cu100 just bumped the version up to the newer one with support for newer gpus, apparently the older ones don't support tensor cores or something. So glad we got that working for you. Its been a fun project. Cool i'll shoot you the link
  7. Thats really strange, I wonder why its running out on yours but not on mine, they should more or less be the same... I assume your Runtime > Change runtime type > is set to GPU. Are you running the script fresh after it fails or closing out the tab and reopening it to try again? I noticed that during the first run it updates # Work around with Pillow being preinstalled on these Colab VMs, causing conflicts otherwise. !pip install Pillow==4.1.1 # Work around with Pillow being preinstalled on these Colab VMs, causing conflicts otherwise. !pip install Pillow==4.1.1 to the 4.1.1 version from 4.0.0, could be related to that. Other than that I'm not sure, I really didn't like how my photos came out of the 42 anyway and am running it at 30 like the dorothy photo. It really shouldn't be running out of memory anyway, maybe try with just 1 for sure small picture to see how it goes first
  8. Thats weird, this is my top cell with the modifications in it from os import path from wheel.pep425tags import get_abbr_impl, get_impl_ver, get_abi_tag platform = '{}{}-{}'.format(get_abbr_impl(), get_impl_ver(), get_abi_tag()) accelerator = 'cu100' if path.exists('/opt/bin/nvidia-smi') else 'cpu' !pip install -q http://download.pytorch.org/whl/{accelerator}/torch-1.0.0-{platform}-linux_x86_64.whl torchvision import torch print(torch.__version__) print(torch.cuda.is_available()) when it runs it returns 1.0.0 True everything else just ran through clean for me for the first time.
  9. Thats for the your own photos coming through google drive right? What resolution and dpi are your photos there? If they're quite large I could see that affecting things. I've got one 2000x3000(ish) 96 dpi photo going through that now at 42 and it seems alright. Though I'm still waiting on it to finish the current process.
  10. I put it through with 32 and it went through fine but had the same system call error. Which means its fine at factor 42 and cu90 apparently theres something weird with cu80 and 90 and newer gpus. I'm trying cu100 now which should apparently work better, fingers crossed.
  11. Looks like it crashes out trying to do a colourize with version 90 of cuda, I think they changed a call name or something. I'm testing it out back at cu80 with fewer passes first then I'm going to look into bumping up the cu version
  12. imbrock

    Run MacOS Vm without Dedicated Graphics

    You would probably need graphics for setup but could possibly disable them afterwards. Not 100% sure how macOS would respond to that though, might be fussy, I'm sure theres a way you could pass it a dummy gpu entry or something if it chose not to boot.
  13. Youre welcome, its fun I havent coded in a while and I've been trying to ease my way back in this year.