Closed GoogleCodeExporter closed 9 years ago
seems like there are some more errors, when adding movies to a set or when
clicking
on a set
see screenshot for the error
Original comment by kvanbie...@gmail.com
on 21 Jun 2009 at 3:50
Attachments:
The second problem should be fixed in SVN (hopefully). The only way I can see
the
duplicate movies problem happening is if there are multiple entries in the
database.
Just as a test, move the database (Media.emm) out of the folder, open Ember, and
rescan media to recreate the database. See if there are multiple entries again.
I've
added some better/quicker db cleanup code to the SVN version, so this shouldn't
be
able to happen again..... if it is a problem with the db, that is. If not, I'll
have
to dig around a little more.
Original comment by jason.schnitzler
on 21 Jun 2009 at 5:33
i have moved it outside the direcory.
rescanned, it recreated the media.emm. but when going into the set manager
again, the
same movies appear double/triple/quadriple.
btw it loads the sets, but i cant alter it and i cant look in it..
will wait for later version and try again, thanks for the response
Original comment by kvanbie...@gmail.com
on 22 Jun 2009 at 4:18
is there an error log?
Original comment by jason.schnitzler
on 22 Jun 2009 at 6:48
Do they appear in the main media list only once? The only way I can see this
happening is if you have multiple entries in the db or your nfos are really
screwed
up. It's unlikely that there are dupes in the db as the table column for the
path is
a unique index (meaning it can only occur once). An easy way to test if the
nfos are
messed up is to enable "Use Title From Nfo" in settings and rescan the media.
That
should, in effect, be exactly the same as what the sets manager is doing when
loading
its list. If you get dupes in the main meida list, you'll know you have a
problem
with your nfos.... if not, we'll have to dig deeper into the sets code.
Original comment by jason.schnitzler
on 22 Jun 2009 at 7:48
no error. Enabling the show titles from nfo made it very clear...
somehome some of the nfo files were messed up (braveheart had the title from
buglife,
but info was mostly right (actors were right,description also, tagline en title
were
wrong) very weird. but i scanning trough the database and correcting the nfo's.
and
everything looks good now, even the sets manager works great now (has it
anything to
do with the duplicate titles???)
very great work guys (will keep you guys updated if i find something)
greatest soft ever made and awesome support :p
Original comment by kvanbie...@gmail.com
on 23 Jun 2009 at 5:25
The sets manager not working was probably from the sorting bug that was fixed
in the
new release.
Sorry if Ember caused the nfo problems... there was a bug in a very early
release
that caused movie data to be saved to the wrong movie. You may have used that
version
a while ago and just never noticed until now. Glad everything is worked out
with this
though. Let us know if you have any other problems or have any suggestions!
Original comment by jason.schnitzler
on 23 Jun 2009 at 5:35
ow just noticed something in the set manager..
it works fine exept some movies...I tried creating a set "Batman Collection",
but i
cant add any movies in it. when i create "The Batman Collection" it works...
Wayne's world just the same (
it always spits outs this error in the log file
--------------------------------------------------------------------------------
----
itle: Error
Message: IComparer (or the IComparable methods it relies upon) did not return
zero
when Array.Sort called x. CompareTo(x). x: '' x's type: 'Movies' The IComparer:
'System.Array+FunctorComparer`1[Ember_Media_Manager.dlgSetsManager+Movies]'.
StackTrace: at System.Collections.Generic.ArraySortHelper`1.Sort(T[] keys,
Int32
index, Int32 length, IComparer`1 comparer)
at System.Array.Sort[T](T[] array, Int32 index, Int32 length, IComparer`1 comparer)
at System.Collections.Generic.List`1.Sort(Comparison`1 comparison)
at Ember_Media_Manager.dlgSetsManager.LoadCurrSet()
Date/Time: 6/23/2009 7:51:58 PM
================================================================================
===========
Original comment by kvanbie...@gmail.com
on 23 Jun 2009 at 5:59
The last one is a duplicate of issue 193, so I mark this as verified.
Original comment by nadas.bence@gmail.com
on 24 Jun 2009 at 3:24
Original issue reported on code.google.com by
kvanbie...@gmail.com
on 21 Jun 2009 at 3:44Attachments: