preiswerte Schmerzmittel ohne Rezept HCG-Injektionen Online-Apotheke

Stability on Windows – and an upcoming Release

A lot of interesting work has been done behind the scenes since the last blog post. Even though we’re still low on developers (are you a dev? we’re still searching!), ilikenwf and Mook made many steps in the direction of building with a more current, vanilla XULrunner. Non-technically speaking, that means making Nightingale much faster and more reliable, with more addons and support for newer web services. I (rjtdrjgfuzkfg) just finished working on the fix for the only blocker issue we had with 1.11.

We finally have working Windows builds using a recent version of taglib (read: builds without the annoying crash issue) and that means that the basic porting for using a newer, vanilla taglib is done. Now we need your support – please download the testing build and try it out to see if everything works as expected. A huge part of the metadata handling code was rewritten, so we need to test it thoroughly. Please report any issues and all the successes you run into in the forums or at the github issue tracker, so we can fix them in preparation for releasing the next version!

We will also be working on using system taglib support on Linux, which would reduce the number of bundled dependencies, making Nightingale even more lightweight. Linux builds of the current taglib changes are not yet available due to the required dependency rebuild, but they should be rolling out very soon!

Speaking of 1.11.1, we’re moving in the direction of releasing the second and probably last release from the current code branch. There are many bugs fixed already, and we’re looking forward to publishing them in a stable build soon. Again, we need your help testing, so make sure and let us know if you see something that is not ready yet or broken.


Thanks for your interest into the Project!

– rsjtdrjgfuzkfg and the Nightingale Community

6 Responses to “Stability on Windows – and an upcoming Release”

  • Great news!

    Small problem – can’t install it ! I had installed and uninstalled a couple of previous versions (on Windows) and now this install is getting stuck with ‘an older version is installed … do you want to uninstall it ..?’ message. I click yes but its just looping round to the same message.

    I’ve cleaned out my registry and everything else Nightingale related, I can think of, but no luck!

    Looking forward to getting it going…

  • But some good news too! I did get the new test release running on another machine (XP) and all (2907 media items) imported OK.

    Well done!

    There’s 2 items fewer than loaded into songbird – I’ll try to identify them. I’m eager to get it installed it on my Windows 7 PC and port my Songbird extensions over…

  • From what I see in the installer’s source code (read: I have no idea of the current installer), it looks for me like the key HKLM\Software\Nightingale is responsible for version detection. Did you remove that specific one?

    You can try to open the installer in 7-zip and copy the files and all elements within the $_OUTDIR folder into any folder, then start nightingale.exe. We have some plans for switching the installer system anyway, but not sure how far we’ll get that for 1.11.1.

  • Good news and bad.

    Found a registry entry under wow6432Node hich needed to be removed. Ng installed Ok but crashes when importing – no metadata at all but some media items. Maybe something to do with running on 64 bit machine? (I imported those media items onto my XP machine with no problems)

    Can’t find a crash report anywhere!

  • Error console

    Error: SQLite compile step:
    select property_id, property_name from properties
    caused the error
    no such table: properties

  • The error console looks normal. I personally run Win7x64, and that works for me. Did you try with a fresh profile?

    Also, maybe not only the registry had issues with the last uninstallation. Maybe uninstalling and reinstalling helps? If not, could you verify the md5 of components/sbMetadataHandlerTaglib.dll is 7320458539efeaadb02a33d52ca085bc, just to ensure there were no copying issues?

Comments are currently closed.