[Logo] Jaikoz- Discussion Forum
  [Search] Search   [Recent Topics] Recent Topics   [Members]  Member Listing   [Groups] Back to home page 
[Register] Register / 
[Login] Login 
Messages posted by: netphreak  XML
Profile for netphreak -> Messages posted by netphreak [42] Go to Page: 1, 2, 3 Next 
Author Message
Almost 8 months now... I get a feeling this is not a priority task?

So - do you accept any help on this issue? I can donate money, code or try to get a legal agreement for you (based on your terms) - if it helps speeding up things here...
There's only one way of making it "100% legal" (if at all possible) - and that's to pay good money for it.

I would easily go for a (rather expensive) payable plugin, and I bet there's a few more of us.
Sorry to bring this up again, but still nothing? I have had my Jaikoz work on hold since this feature disappeared, since we don't know if it will be back...

I know there are probably more exciting or needed things to do with Jaikoz first, and I totally respect that - but the "fix" seems fairly easy - can you enlighten us on what's holding you back on deciding if this feature will or won't be back?
Any progress on this? lyrdb.com should be fairly easy to use as replacement, right? The administrator of the database have even given permission to use it with Jaikoz...

I just want to know if there's any point in waiting for this or look for alternatives when it comes to lyric tagging - pointless to do some tagging now, if a solution comes up some day, and I'll have to tag the same tracks all over again...
Voted
Oh, I thought this limitation were restricted to the restful API only, not SOAP... Who on earth wants to use SOAP to receive a simple URL??? But I think you are right anyway.

I'll send you a mail with other alternatives, they may not belong here.
I see (and should have seen) - thank you for clearing that up.
Paul:
I really use this feature (bonus or not), and can provide some help if wanted.

This is only a guess, but from your post about LyricWiki_API it seems like Jaikoz currently can not use SOAP, and the restful API from LyricWiki isn't working the way it should...

I can make a web application with a restful API as frontend, and SOAP as backend. Then all you would need to do is changing the URL for lyrics in Jaikoz...

Or maybe... make an option in Jaikoz for users to choose URL for lyrics? Then at least this can be solved temporarily...

Just some thoughts
Sorry if this is a "known issue", but since I upgraded to 4.40 NGS Jaikoz no longer display's PUID's??? Even though Jaikoz tell me acoustic fingerprints are received successfully...
Thank you for your prompt answer. Didn't think of the possibility of users editing the exports, and import it again - yes, this will clearly confuse users.

I will base my exports from Squeezeserver mysql database instead, which is a better idea in many ways.

Btw, great work on the latest stable release! A long step in the right direction
I love the export feature to *.xls, but I wonder if it's possible to export file information like: filetype, bitrate and size?
Fantastic, will give it a go later tonight ;)
I noticed that when using the Original release date plugin with Picard to populate the TDOR ID3 frame - it will display properly in Jaikoz. But when altering/saving the file with Jaikoz, the frame get "corrupted", and will not display again in Jaikoz ("TDORata="X bytes;").

Funny part is that it still shows the correct value in Picard!

So my guess is that Jaikoz add something "extra" to the frame when saving, which Jaikoz itself is not expecting when opening the file again...
When saving a value (say 1979) in the ID3v2 field "Original release time" - it fails, and populate the "Unknown list" field with "TDORata="5 bytes;" instead!

Tried it with Jaikoz 3.4.2, 3.8.2 and 3.8.3.

Is it a bug?
 
Profile for netphreak -> Messages posted by netphreak [42] Go to Page: 1, 2, 3 Next 
Go to:   
Powered by JForum 2.1.6 © JForum Team