Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - chriss

Pages: 1 2 3 [4] 5 6 ... 10
Developers / Re: Annoucement: Getting cover art and attributes from IMDB
« on: January 26, 2009, 07:14:55 am »

But I did get this error on the second media I tried adding after pressing the "Get Coverart" button:
Code: [Select]
Fatal error: mysql error: [1062: Duplicate entry '168-78-0-0' for key 1] in EXECUTE("INSERT INTO File_Attribute (FK_File,FK_Attribute) VALUES ('168','78')") in /var/www/pluto-admin/include/adodb/ on line 77
The strange thing is, if I enter the same media again, now it has coverart and all the attributes.

I've seen this error happen to my system several times... no only with the IMDB patch but also with the older amazon attribute fetching. I haven't looked into this yet, but if you just do a reload the error does not occur again and the data is stored as expected.

I did have problems patching it...
I had to manually edit the following files:

Hmm, would have to check the patch again. If I remember correctly, there was a problem when adding the stuff to SVN, too, but the problem was fixed. I think it was my fault because I somehow mixed up different branches (0710, 0810 and trunk).

I also found 2 bugs, the first is just a a text that is not translated.
The option to include attributes is called "Include Amazon attributes" and should be IMDB.

Ok, this is a simple one. I attached it to the original ticket and will fix it. (#53)

The other is Genres. If a Genre does not exist, it gets added as a Title or a Album.
For example I have never used the Genre "Drama", all movies get a second Title called "Drama".
After adding the Genre "Drama" manually to one movie, it gets added correctly as a Genre.

I think this is not related to the IMDB patch which only fetches the attributes. Under some circumstances you should see that behavior with amazon, too. Please try to apply the patch from ticket #52 ( and report back if the problem stays.

One other thing. It's slow (and worth it). Sometimes the search is fast, and whenever I see a difference in the speed the list is shorter. When It's slow, I get a duplicate list of selectable movies. When It's fast I get only the movie I'm after.

Yeah, I know that it is slow. Unfortunately you have to do several queries to IMDB to fetch all the information and the more movies you find with the search, the slower it gets...

Anyway, thanks for the feedback!


Developers / Re: Coding an Automatic Lighting controller in GSD
« on: January 17, 2009, 08:55:46 pm »
But also remember, that we have UpdateEntArea, which does all calculation of scenario and event generation any time the router is reloaded. This is the application that makes all the automatic events, and it makes all the scenarios in response to certain devices being available, etc. Add anything pertaining to this here, and only here.

agreed, but my point is, that all these calculations and rules are hard coded in there. They should not be replaced with another hard coded implementation but with a system being able to interpret some form of external rules, i.e., it should not be necessary to recompile this plugin everytime the rules are changed. please correct me, if this isn't necessary right now or if i'm wrong.

Developers / Re: Coding an Automatic Lighting controller in GSD
« on: January 17, 2009, 03:14:30 pm »
thanks for the info, hari.

i just digged through the GSD pages. Seems GSD is a bit more than the name suggests, but still not meeting the requirements - at least not in its current state.

Developers / Re: Coding an Automatic Lighting controller in GSD
« on: January 17, 2009, 02:38:33 pm »
Hi bulek,

- we currently have plugins that are coded in C++ and do whatever they do. Their behavour is hardcoded and barely settable by any settings. And also, it's quite hard to change their behavour, cause you have to be experienced C++ and LMCE programmer to do anything with it...

- on the other hand majority of us need somekind of custom determined behaviour and a lot of users probably feel quite incompetent to do anything useful (including my self from time to time).


What we would need to have is basically remove that behaviours from hardcoded plugins (except maybe those that are really needed)
still with you here...

and then try to prepare everything in GSD and Ruby way (so user could write minimal code with easy access to objects, data, events , etc...).

but  this is the point I don't really get. Again this plugin would be "hardcoded in Ruby" instead of "hardcoded in C++" and in some months somebody will start to do it again as "hardcoded in Java" because he doesn't like Ruby and C++? Or am I missing something?
I think, we should have some sort of "macro language" to define automation behavior on an abstract level, i.e. without having to think of DCE connectors, messages or whatever. This macro language would be interpreted by some plugin. I know, this is similar to responding to events, but it should be more powerful, i.e. allow to leave the lights off when starting a movie while the sun is shining brightly (and maybe activate your blinds instead). BTW, having some concept of inheritance would be great, e.g., define a movie scenario for the whole house but only modify some things in you bedroom and still be able to benefit from improvements done to the main scenario automagically...

Is this what you are thinking of? Haven't looked into GSD yet so maybe this is basically the same  :P


Users / Re: Auto tagging folder - just a thought
« on: January 15, 2009, 10:59:56 pm »
Hi guys,

I've been thinking about starting to redo the media management part in JavaEE, e.g., using the Seam framework for a web application. This would give us the opportunity to have a nicer GUI while sticking to the approach of being able to access your system via a simple web browser.

What do you think?


ps I implemented a grabber for IMDB attributes for the current web-admin, check the svn...

Developers / Re: Backup System Improvements (0810 Critical)
« on: January 14, 2009, 12:35:09 pm »
I would suggest to log all bugs in Trac and give a description as detailed as possible... this way the bugs won't get lost.

yeah, sure. But it has been done quite some time ago and therefore was copied to the 0810 branch... it found that particular changeset when following the history of the current branch.

Developers / Cleaning of duplicate attributes removed from UpdateMedia
« on: January 13, 2009, 09:38:57 am »
In changeset 20523 ( cmiron removed the code to remove duplicate attributes from UpdateMedia.

Does anybody know why this happened? Any problems with the code? BTW, who is cmiron, maybe a pluto guy?

I started looking at the code because UpdateMedia is occasionally putting duplicated attributes into my database.


Developers / Re: Backup System Improvements (0810 Critical)
« on: January 13, 2009, 05:20:00 am »
I already thought about extending UpdateMedia based on Jon's code to automatically sync playlists to a directory, e.g., /home/public/data/playlists/. As a side effect, this would allow to keep the playlists over new installs and db failures like the metadata for media files is kept right now.
Maybe this approach can be used for other data, too, since I think it is quite nice... (had metadata wiped twice within the last few weeks... luckly I didn't lose any information because of UpdateMedia :))

just my 2c

Users / Re: Media Pc with front touch panel
« on: January 10, 2009, 04:05:04 pm »
I think some members have reported to have a second x-screen with a UI1-orbiter running on a second screen. This scenario would be perfect for your use-case but needs some hacking because it is not supported out of the box.

Regarding your GPU: go for nvidia since ATI is not supported yet.

Users / Re: Unravelling of datagrid entries in Album sort mode...
« on: January 10, 2009, 09:02:31 am »
You are right - this patch does not fix the issue but merely cleans up the symptoms. I think, this is why I haven't submitted it to Trac yet.

Unfortunately I didn't have the time to set up a full blown dev environment to try to fix this issue in UpdateMedia or even track it down to a code segment. I appreciate if one of the devs would comment on this, too.

Users / Re: Unravelling of datagrid entries in Album sort mode...
« on: January 10, 2009, 02:05:29 am »
then that would seem to imply that UpdateMedia rather than the Orbiter code is at fault.
that's what I was talking about  8)

The thing that confuses me is that when this subject has been discussed before (and solved!) one of the devs described this as a grouping issue in the SQL queries.... perhaps I misunderstood?
Well, after all it is just a conclusion of mine after seeing the behavior I described above - I haven't looked at the actual db queries.
An example why grouping the album title is no good idea might be the following scenario: imagine having a couple of albums called 'greatest hits' by different performers. If you would group this on the title you would have all those albums merged under a single button 'greatest hits'. This is not what I am expecting when browsing my albums...

So my question to you is, if I need to roll up these rows in the Attribute table of the Media database, how do I do that and also correct the files and any other relations so that they all use the same FK pointing to the one remaining, unique Attribute entry? I note that this folder/album has over 1000 audio tracks in it, many by the same artist, so when I look in the Attribute table for the Album name I get 583 instances of the same album!!

Well, either by updating the album title 538 times like described above or by applying the attached patch.

Regarding the attached patch
Beware: I created this patch, it worked for me but it is not excessively tested. I recommend to make a backup of pluto_media first.
After applying the patch, go to web admin -> media browser, activate the album checkbox and then hit the button "merge all attributes of same name and type". Note: this will merge all album titles of the same name! If you have something like in my greatest-hits-example, be sure to rename those album before (maybe something like "greatest hits (performer)") to not have them merged.


Users / Re: Unravelling of datagrid entries in Album sort mode...
« on: January 09, 2009, 08:23:28 pm »
collinjones, maybe you don't see the point I want to make ;) please don't take this post as an offense, I'm just trying to understand...

First let me tell you again... I'm having tenth of compilations (one album with several performers) which are tagged correctly. All files of an album share the same attribute, i.e., not just attributes with the same title but the same db record. These albums are shown correctly in the datagrids: there is just one entry and if I select one of them, I get a new screen with all tracks belonging to that compilation, where each track has a different title and performer.
To me, this looks like the DB queries, especially the group operation (something like group by PK_Attribute) is working fine.

Now back to my first posting. Some weeks ago it seemed I had the same problem you are having right now. Albums showed up multiple times in the orbiter and every album contained only one title of the whole compilation. Is this the same behavior you are seeing?
I tracked this down to having multiple entries for the same album (compilation) in my media database. The album title was always the same but there where several rows of data. Once I corrected this, the orbiter showed everything correctly like described above.

What I'm stating now is that the problem is probably not the orbiter query but that UpdateMedia has a bug in populating the database. You can easily verify this by going into the media browser (web admin) and check if the album title is shown multiple times (ff you edit one of the attributes and click 'update', webadmin should ask you if you want to merge the attribute. you can do this several times, until there is only one single database entry left).

If you still think, there is another problem could you explain it further to me so I can understand? Thanks in advance.


Users / Re: Unravelling of datagrid entries in Album sort mode...
« on: January 09, 2009, 11:11:32 am »
yes, the original problem is an UpdateMedia issue but IMHO having the orbiter show all album entries in the media db is not a bug. So my suggestion is to check if you have multiple db records for the album and clean this up.

Users / Re: Unravelling of datagrid entries in Album sort mode...
« on: January 09, 2009, 08:37:57 am »

When browsing audio media in Album sort mode, albums that consist of tracks that come from more than one artist (eg compilations, dance music, classical, etc) each artist has its own Album tile in the Album sort mode

I cannot reproduce this behavior on my machine (0710) but I encountered similar problems before: UpdateMedia created separate album entries in the media database for each track (sometimes even several entries per track which ended up in >100 duplicated entries) which showed up as separate albums in the UI later. First thing I fixed was cleaning my media database, I created a patch to merge those duplicated attributes easily (can't find it on trac right now, seems I still have to submit it). You should check if the albums are there only once in webadmin->media browser. However, this does not explain, why those duplicated attributes are created by UpdateMedia...

Personally, I believe that a "bread crumbs" approach would be the most user friendly, as it would give a clear indication of the heirarchy level and aid it learning how to use sorts more efficiently - this could continue into the feature where when a track it about to be selected, you can click on one of the black attribute boxes to filter as this also obeys the heirarchy and often you need to hit back a few times to capture all of that attribute.

Sounds like a great idea to me  :P


Pages: 1 2 3 [4] 5 6 ... 10