Using Windows 7 Ultimate x64 and latest Opus.
I created a file collection of files on the network and now when I try and open it Opus pretty much just hangs up.
I have one older file collection also and it does the same thing there.
Not sure if this is a Windows 7 problem or a problem with Opus.
The networked files are on a mix of computers running Windows 7 and Vista.
Been playing some more with it and it's not hanging. It's just painfully slow. Even trying to scroll through the list of files takes minutes.
Is it a really slow (e.g. far away) network drive?
Which columns are shown when viewing the collection?
Which types of files are in the collection?
All the network drives are on a wired gigabit network. All the computers have gigabit connections.
Columns are Name, Ext, Size, Modified, Attr
Files are mostly music and video files.
Does it happen without video files? If not it might be caused by some codecs (I would recommend K-Lite Codec Pack then).
Is it painfully slow 'some' times or 'all' the time?
Once it finishes and you can see the files, what happens if you copy all file paths to the clipboard and stick them into a batch file with each file following an explicit dir command? Does the batch file take as long as Opus to list the files - or is it faster?
It's slow all the time. You literally can't do anything with that lister.
What happens if you turn on Prefs - Folders - Options: Display generic icons for: All folders?
If that improves things then it could be something like a shell extension which provides icon overlays for music/video files and is reading large amounts of the file to work out what to display. It could also be an anti-virus scaner that's scanning the entire file whenever it is opened to get that information.
Though if it was either of those things, or anything similar, then browsing similar network folders would also be slow. Is that the case, or is it only slow when using collections?
Yeah, despite Opus' multi-threaded-ness... slow and hangy lister response while accessing network resources is one thing that often plagues me in Opus. I have to imagine it's the same in Explorer - though I've never checked or compared since I just assumed it's not Opus...
Even so, it's irritating enough that I wonder if GPSoft could make any improvements in this area. I'm diverging a bit off topic from your "specific" slowness with your file collections, and referring to the effect that slowness has on being able to use the lister while you're otherwise waiting for whatever is happening to "finish". I'd have hoped that in Opus, I could still do "other" things in the lister while one display is choking on a network resource... Instead, I can't access other open (local) folder tabs in that lister until the network access attempt has completed sorting itself out. And if I've mistakenly clicked on a network resource and try to just close the hangy lister, I get the "Program is not responding / End Now / Cancel" dialog from WinXP... I have similar hanginess while waiting for access to other things like external USB drives that have spun down and gone to "sleep" - while waiting for them to wake up.
Anyhow, back to whether or not your inherent slow access time is some issue in Opus or not (despite the effect it has on the lister) I'm still curious what happens if you do a batch file listing of all files at the root of one of these collections. If that is still unusably slow, then it's not anything at all to do with Opus obviously - codecs, shell extensions, or otherwise... though I think those are all still useful valid testing points.
Very strange.
Just created a new collection using all the same files as the old collection and it is pretty speedy.
Network browsing has never been a problem with speed.
But there's that one collection.......
Try comparing the /dopusdata\Collections .COL files for each of the collections... Are there any items in the OLD collection that just plain ol' don't exist anymore, and weren't added to the 'new' collection? Any other oddities different between the two .COL files?
I am having the same sorts of issues,
Windows 7 x64, the network is a slow network but my problem is that DOpus is 'not responding' during the entire operation which is taking 30+ seconds...
Making DOpus rather useless when it comes to any network drive at the moment.
I only have Name and Size displayed, I will give that the network is painfully slow at times, but isn't DOpus supposed to be threaded so that it doesn't lock up while retrieving network information?