No release tomorrow!

Name
Email
Subject
Comment *
File	Select/drop/paste files here
* = required field	[▶ Show post options & limits] Confused? See the FAQ.

Embed	(replaces files and can be used instead)
Options	Do not bump (you can also write sage in the email field) Spoiler images (this replaces the thumbnails of your images with question marks)
Password	(For file and post deletion.)
Allowed file types:jpg, jpeg, gif, png, webm, mp4, swf, pdf Max filesize is 8 MB. Max image dimensions are 10000 x 10000. You may upload 5 per post.

File: 1453847888809.jpg (190.72 KB, 812x1320, 203:330, ae80b35c00c4f37c484ede65fd….jpg)

No release tomorrow! hydrus_dev ## Board Owner 01/26/16 (Tue) 22:38:08 No.1894

Unfortunately, I had a bad week. I went down with stomach flu on Thursday, so most of my hours disappeared. I eventually managed to catch up with my IRL stuff, and I rebuilt my network and dev computer as I planned, but I have had zero time for hydrus.

I now feel about 8/10 body and 9/10 mind, so I am keen to get back into it. Assuming I still have the energy, I hope to catch up on messages and reports over the next few days. If there is anything very important, please repeat it to my email or the v191 release thread. >>1855

I literally only got hydrus running on my new Win 10 machine in the past half hour, but neither the .py or the .exe have caused the BSOD, so there will be no easy fix there. I will have a think and make a plan.

So, there will be no release tomorrow. I expect to put out the next release on Feb 3rd. It will most likely be some bug fixes.

Anonymous 01/27/16 (Wed) 00:10:40 No.1895

>>1894

Glad to hear you're feeling better!

Anonymous 01/27/16 (Wed) 03:37:04 No.1898

Hi dev, I'm a new hydrus user (been trying it for about a week) and I wasn't really sure where to post this feedback, so I decided here.

First things first, I really like hydrus. And I hope to use it one day to organize my huge collection of pics.

Now the problems. Well, I was actually able to get the same BSOD that others reported (Kernel_Security_Check_Failure) on my laptop running windows 8.1, so it's possible the problem is not related to the windows version. I'll try to explain everything I did the best I can, and maybe this will help you figure out the problem not only for me but for the windows 10 users.

Well, my laptop has an integrated graphics processor (intel HD) and a dedicated GPU (Nvidia) and I notice that hydrus was using the dedicated card even though it had no reason for that. So I decided to mess around and try to fix this by myself before coming here for help. I tried everything I could on Nvidia control panel. I set the hydrus directory (and every .exe) to use only the integrated card but it didn't work. Hydrus seems to open using the integrated card, but as soon as I double-click on system:everything, the dedicated GPU starts to run, right before the thumbnails begin to show, and it never stops until I close hydrus.

Before coming here I decided to try on last thing, and that was updating my GPU driver to the latest version (Geforce Game Ready Driver version 361.43) and that was when I got the BSOD. By the way, the BSOD occurs exactly when hydrus tries to use the dedicated GPU, that is, I can open the program fine, but when I click on system:everything I get a BSOD.

I've since reverted the driver back to the old one I was using and hydrus is working fine now (except that it's still using the wrong graphics card).

This is it, I think. Sorry for the long explanation, I'm not really good at summing things up.

I'm sorry for your bad week, and I hope you soon get to feel 10/10 body and mind again.

BTW, if you need me to run anything, as long as there's a step-by-step, I can do it.

Thanks for this great program.

bob 01/27/16 (Wed) 09:01:42 No.1900

>>1894

Hope you are feeling better. It's heartwarming to see a developer be so committed to his little community.

What issues are going on with Windows 10? I'm running Hydrus on Windows 10x64 on Python 2.7 and I haven't encountered a BSOD or any such errors.

Anonymous 01/27/16 (Wed) 14:53:56 No.1901

>>1898

I actually managed to fix it, and I was supposed to say it here like a week ago, but I forgot. Anyway - the issue is actually with nvidia's drivers! Find the hotfix driver 361.60 and install that. It should fix the BSOD problems. The hotfix issues say that photoshop actually had a very similar problem, with kernel crashes.

Anonymous 01/27/16 (Wed) 17:28:21 No.1903

>>1898

>>1901

Other user here with BSODs, I also use an NVIDIA card on my laptop. I'll check this out, thanks for the idea

>>1894

Glad you're feeling better, I hate the flu. I'll let you know how reverting drivers goes for me

Anonymous 01/27/16 (Wed) 17:33:35 No.1904

>>1903

361.6 wasn't available for my card, trying 361.75 instead

Anonymous 01/27/16 (Wed) 20:08:50 No.1905

>>1904

New drivers fixed my BSODs, and on a side note, no longer try to force Just Cause 2 to melt my GPU

Now that everything is working, I can really see how much the loading system has improved since 188, fantastic work!

Anonymous 01/28/16 (Thu) 00:30:01 No.1906

File: 1453941001707.jpg (334.51 KB, 1280x677, 1280:677, 1425770458747.jpg)

I've been using Windows 10 exclusively with Hydrus through many revisions and have never had any issues with it, just adding an anecdote since I'm sure most people without any issues are less likely to post than those that have issues.

Anonymous 01/28/16 (Thu) 01:11:56 No.1907

>>1906

Yeah for me it was my NVIDIA drivers causing bluescreen, on both Hydrus and Photoshop. AMD and non-GPU users probably don't have an issue.

hydrus_dev ## Board Owner 01/28/16 (Thu) 01:21:49 No.1908

File: 1453944109523.gif (1.19 MB, 690x200, 69:20, 0037c43f2375146e8c999df24f….gif)

>>1906

>>1901

>>1905

Thanks, this is great to hear! I expect a group in Nvidia has had some late nights recently, trying to figure that one out! I bet Adobe kicked up a massive fuss when they discovered Nvidia were crashing their shit.

This also explains why I couldn't figure out what I had changed to cause it. I suppose my spamming of bmp creation when I prepare to fade thumbnails to the screen was being handled by their driver in some way, and their internal double-linked lists were not thread-safe or something.

Let me know, obviously, if anything like it returns.

>>1898

This is interesting and helpful, thank you. I write hydrus in a high-level language, so I don't think I have the explicit power to choose a graphics adapter affinity. I certainly didn't set any 'force max graphics power' flag as far as I can remember. I presume either one of my graphics-related libraries, like OpenCV, Pillow, FFMpeg, or wx, is calling for it through CUDA hooks or something, or Windows in general is forcing it for some reason.

If you can update to the new 361.75 drivers (I just got the popup on my laptop a couple of hours ago), do you experience the same problem?

>>1900

Hydrus was causing BSOD for some Win 10 users when their search results finished, just when thumbnails were about to render to screen. It obviously made the program completely unusable for them. I've been banging my head against the reports for a couple of weeks now. Thankfully, it looks like it is now both not my fault and fixed by Nvidia.

>>1906

I have the bad drivers on my new Win 10 dev machine, and on my Win 8.1 laptop, and don't get it on either, so it must be a combination of things. I even have one of those hybrid integrated/dedicated intel/nvidia systems on my laptop like >>1898 , so I am not sure. Maybe the exact memory speed or chipset, or some power profile that's selectively turning off bits of the PCIE interface or something? Thankfully, this sort of driver fault is way above my pay grade.

Anonymous 01/28/16 (Thu) 12:07:57 No.1910

Are there GET / POST things you can send to the local booru (the one that only accepts requests from 127.0.0.1)?

I think it would be nice to make an addon for my browser that lets you right click and "send to hydrus" or something like that, preferably with the ability to attach a list of tags to the request in the case of browsing a booru.

Anonymous 01/29/16 (Fri) 04:13:47 No.1915

>>1910

to clarify: I'd like to have it be a part of this or hydrus to have the ability to download tags from pages better. Right now it sucks the image up but ignores the tags unless you do a booru search page. Which is long and tedious.

github.com/JetBoom/boorutagparser

Anonymous 01/29/16 (Fri) 23:24:42 No.1920

I've had some very odd issues with Hydrus that persist after reinstalling, after attempting to download and use the tag archive from >>1204.

Immediately after renaming the .db included in the zip "client.db" and dropping it in, attempting to run the client results in a Runtime Error R6034, "An application has attempted to load the CF runtime library incorrectly."

Prior to this, even though I've been running Windows 10 for the past couple of days, Hydrus ran fine (although it never did sync with the tag database, which is why I attempted to download it in the first place.)

Reading through some of the posts here indicate that Windows 10 isn't totally supported yet, and I'm willing to wait, and assist with this bug in any way that I can- luckily I still have the files saved locally.

I'm also desperate for an in-depth guide on how to properly install the tag repository directly, as it took hours to create not a searchable library of 3000+ images, but instead… this error. I tried running test.exe and it failed in two places, but Windows Firewall was blocking it, so…

Anyway, I can give more info on request, probably, and I'm hoping I can get this to work, as it would be a godsend.

Anonymous 01/30/16 (Sat) 04:12:40 No.1921

File: 1454127160978.jpg (91.71 KB, 1000x823, 1000:823, 5d1c7d8150389932353f97fc26….jpg)

>>1920

If you're downloading the tag archive and renaming the db included (as it sounds like you are) to client.db that's not what that file is meant for. That's a tag archive that is meant to go into client_archives and is used to sync the tags within that db with whatever service you choose inside the client. The first link in that post >>1204 is what is meant to be downloaded and dropped into the install_dir/db folder.

Anonymous 01/30/16 (Sat) 16:21:03 No.1924

>>1921

Okay, everything is in the right place now, but a new issue has reared it's ugly head.

The database attempts to update on boot, which is fine, aside from one minor problem…

2016/01/30 11:19:36: updating db to v159

2016/01/30 11:19:36: A serious error occured while trying to start the program. Its traceback will be shown next. It should have also been written to client.log.

2016/01/30 11:19:36: Traceback (most recent call last):

2016/01/30 11:19:36: File "C:\code\Hydrus\include\ClientController.py", line 1011, in THREADBootEverything

2016/01/30 11:19:36: File "C:\code\Hydrus\include\ClientController.py", line 467, in InitModel

2016/01/30 11:19:36: File "C:\code\Hydrus\include\HydrusController.py", line 168, in InitModel

2016/01/30 11:19:36: File "C:\code\Hydrus\include\ClientController.py", line 53, in _InitDB

2016/01/30 11:19:36: File "C:\code\Hydrus\include\HydrusDB.py", line 72, in init

2016/01/30 11:19:36: Exception: Updating the client db to version 159 caused this error:

Traceback (most recent call last):

File "C:\code\Hydrus\include\HydrusDB.py", line 64, in init

File "C:\code\Hydrus\include\ClientDB.py", line 5646, in _UpdateDB

File "C:\code\Hydrus\include\ClientData.py", line 177, in DeletePath

KeyError: 'delete_to_recycle_bin'

2016/01/30 11:19:41: shutting down controller…

2016/01/30 11:19:41: hydrus client shut down

It never manages to actually get past v159.

hydrus_dev ## Board Owner 01/30/16 (Sat) 17:31:30 No.1925

File: 1454175090541.jpg (2.6 MB, 3060x3804, 255:317, 49e2230c16b954ce1bc5a62045….jpg)

>>1910

>>1915

I'd love to eventually support every database 'verb' that the client uses over GET/POST so that people can write their own scripts to do complicated imports/searches like this. At the moment, though, the client only supports GET /file and /thumbnail, really.

>>1920

>>1924

I am sorry for your bad experience. I have written a guide on the program in general here:

http://hydrusnetwork.github.io/hydrus/help/index.html

And in some more detail the tag repositories here:

http://hydrusnetwork.github.io/hydrus/help/getting_started_tags.html

Did you see those? Is there something I did not explain well, or something that did not work for you?

The client is supposed to download and process updates when you are not using it. Most computers process all ~32 million tag mappings after a dozen or so hours of heavy cpu usage, which can ultimately be split up over several weeks. When you tried to sync, what general steps did you go through? Did you put the access key information into services->manage services? Did the tag repository appear in services->review services? Were you getting 'cannot connect' error messages popping up, or was the client never doing any syncing at all?

That v159 db is quite old now. The client is trying to update about six months of updates in v159->v191, which is a lot of steps, and is probably not working due to bit rot. Using these 'jump start' databases is not something I recommend for new users, but if you would still like to try, I have put a new one together for v191, caught up to today, here:

EDIT: The previous link I put here was lacking some folders, here is an updated upload:

http://www.mediafire.com/download/t260gvff3ytp2w2/Hydrus_Network_Client_bare_database_with_PTR_up_to_update_1310.7z

If you drop that into a v191 installation (I suggest clearing everything out and starting again with a fresh install), it should work straight away. Reimport your 3000-odd files, and a decent number of them should have tags. If you find it isn't syncing after a few days, let me know.

Post last edited at 02/03/16 (Wed) 18:29:44

Anonymous 02/02/16 (Tue) 00:15:45 No.1948

>>1925

Oh, my, please don't apologize for my experience. I've dealt with far less useful and far more finicky programs and that was before the leap to Windows 10; my issues stem only from my own impatience, to be perfectly honest. I quite like Hydrus already, if I didn't, I wouldn't be trying so hard to get it to work.

I won't be able to get around to retrying it for a bit, as I'm handling a few difficult issues irl at the moment, but if I have any more problems I'll try to clearly define them in a thread here. Needless to say, you've already been more than helpful.