|
|
| Author |
 Topic  |
|
|
awry
Just Posting
5 Posts |
 Posted - 01/04/2004 : 12:55:48 PM
|
Hey all -
Just got a new neuros for xmas... what a great machine! Now for that USB2 support...
Anyway, I'm trying to sync using positron under linux. I'm running Gentoo with a 2.6 kernel. I can mount neuros at /mnt/neuros, can see all the files, read and write. positron config goes smoothly. But as soon as I try positron sync, I get this:
chris@juniper-gentoo chris $ positron sync
Traceback (most recent call last):
File "/usr/bin/positron", line 175, in ?
main(sys.argv)
File "/usr/bin/positron", line 157, in main
cmd.run(config, myNeuros, remaining[1:])
File "/usr/lib/python2.2/site-packages/positron/cmd_sync.py", line 47, in run
audio_db = neuros.open_db("audio")
File "/usr/lib/python2.2/site-packages/positron/neuros.py", line 160, in open_db
self.db_formats[name]["no_flatten"])
File "/usr/lib/python2.2/site-packages/positron/db/WOID.py", line 74, in open
mdb.set_extra_format(extra_format)
File "/usr/lib/python2.2/site-packages/positron/db/MDB.py", line 134, in set_extra_format
raise Error("Number of format strings does not equal number of extra info fields.")
positron.db.util.Error: Number of format strings does not equal number of extra info fields.
I haven't tried NeurosDBM yet. That is my next step. I guess if that doesn't work, I will be trying NSM under VMWare. But I really would like to have a workable OSS solution!
|
Your quick response to this post: (0 total votes)
I agree (0%)
I disagree (0%)
|
|
|
Sean Starkey
Posting Mania
848 Posts |
Posted - 01/05/2004 : 10:04:44 AM
|
Did you create your original database under the latest NSM?
Sean Starkey - Project Manager for Neuros Database Manipulator - http://neurosdbm.sourceforge.net |
Your quick response to this post: (0 total votes)
I agree (0%)
I disagree (0%) |
 |
|
|
awry
Just Posting
5 Posts |
Posted - 01/05/2004 : 10:17:53 AM
|
| yes, I believe so. so what...? |
Your quick response to this post: (0 total votes)
I agree (0%)
I disagree (0%) |
|
|
|
Sean Starkey
Posting Mania
848 Posts |
Posted - 01/05/2004 : 10:35:54 AM
|
I have to confirm my findings, but I believe that the latest NSM makes a database that is incompatible with Positron and NDBM.
You can always wipe your database, then do a positron rebuild.
Sean Starkey - Project Manager for Neuros Database Manipulator - http://neurosdbm.sourceforge.net |
Your quick response to this post: (0 total votes)
I agree (0%)
I disagree (0%) |
|
|
|
awry
Just Posting
5 Posts |
Posted - 01/05/2004 : 12:25:49 PM
|
| ahh... sneaky of them. i will try the database rebuild now that i've backed up all the songs off the neuros. thanks for your help. also, nice work on neurosdbm. |
Your quick response to this post: (0 total votes)
I agree (0%)
I disagree (0%) |
|
|
|
Sean Starkey
Posting Mania
848 Posts |
Posted - 01/05/2004 : 5:45:59 PM
|
The latest NSM creates 3 additional extra info fields (I don't know what for) that causes incompatiblities with NDBM and Positron.
I hope to have a fix for NDBM soon.
Sean Starkey - Project Manager for Neuros Database Manipulator - http://neurosdbm.sourceforge.net |
Your quick response to this post: (0 total votes)
I agree (0%)
I disagree (0%) |
|
|
|
denials
Posting is for Closers
29 Posts |
Posted - 01/05/2004 : 5:50:21 PM
|
Probably too late, but (apart from being a good general practice) with Positron you don't really need to back up all of your songs from your Neuros before rebuilding the database.
All that "positron rebuild" does is read in all of the ID3/OGG tags from the music files on your Neuros hard drive, then build a new database. The music files themselves will stay there untouched.
Note that I used to get a similar exception when running positron sync that (from the best of my knowledge) resulted from a mutant HiSi file of 0 length. In your case, it looks like one (or all?) of your music files may contain (probably) fewer (but possibly more) ID3/OGG tags than Positron expects.
#4240 128/20 Combo :: Linux + OGG = Happiness |
Your quick response to this post: (0 total votes)
I agree (0%)
I disagree (0%) |
|
|
|
Sean Starkey
Posting Mania
848 Posts |
Posted - 01/05/2004 : 6:46:51 PM
|
quote:
Originally posted by Starkey
The latest NSM creates 3 additional extra info fields (I don't know what for) that causes incompatiblities with NDBM and Positron.
I hope to have a fix for NDBM soon.
I have a fix for NDBM. Expect a release tonight.
Sean Starkey - Project Manager for Neuros Database Manipulator - http://neurosdbm.sourceforge.net |
Your quick response to this post: (0 total votes)
I agree (0%)
I disagree (0%) |
|
|
|
Angus
Just Posting
8 Posts |
Posted - 01/25/2005 : 11:14:57 AM
|
Hi,
I'm experiencing the same problems with positron (v.1.1) and Enterprise Linux ES3A. Does someone know how to solve it (with positron)??? It's almost half an year that the question has been submitted. I wonder if someone has really solved it.
I've used a "positron rebuild" but the process hangs while scanning a directory. NeurosDBM instead works fine with it. Any idea?
Thanks,
Bye.
|
Your quick response to this post: (0 total votes)
I agree (0%)
I disagree (0%) |
|
|
|
kronin
Posting Mania
1144 Posts |
Posted - 01/25/2005 : 11:22:39 AM
|
quote:
Originally posted by Angus
Hi,
I'm experiencing the same problems with positron (v.1.1) and Enterprise Linux ES3A. Does someone know how to solve it (with positron)??? It's almost half an year that the question has been submitted. I wonder if someone has really solved it.
I've used a "positron rebuild" but the process hangs while scanning a directory. NeurosDBM instead works fine with it. Any idea?
Thanks,
Bye.
Yeah, it's been solved, don't use Positron. Seriously though, Positron isn't being developed anymore, so if you want to continue to use it you're going to need to update it. If you don't want to install a JRE, then run Sorune (assuming Perl is installed). |
Your quick response to this post: (0 total votes)
I agree (0%)
I disagree (0%) |
|
|
|
Micah Stetson
Just Posting
1 Posts |
Posted - 01/29/2005 : 1:50:40 PM
|
quote:
Originally posted by Angus
I'm experiencing the same problems with positron (v.1.1) and Enterprise Linux ES3A. Does someone know how to solve it (with positron)??? It's almost half an year that the question has been submitted. I wonder if someone has really solved it.
I've worked around that particular problem by applying this patch:
diff -rN positron-1.1/positron/neuros.py positron-new/positron/neuros.py
107,111c107,108
< "extra_format" : ("z","z","z","z","z",
< ">I",">I","z"),
< "extra_names" : ("Source", "Artist",
< "Album", "Genre", "Track Name",
< "Time", "Size", "Path") },
---
> "extra_format" : (),
> "extra_names" : () },
114,115c111,112
< "extra_format" : ("z","z"),
< "extra_names" : ("Source", "Path") }
---
> "extra_format" : (),
> "extra_names" : () }
It seems that the extra info for HiSi clips has been done away with in newer firmware/sync manager versions, and positron can't handle that. I still had to run 'positron rebuild'.
quote:
I've used a "positron rebuild" but the process hangs while scanning a directory. NeurosDBM instead works fine with it. Any idea?
One of my computers has a problem similar to this. It seems to be USB related, after transfering some files, the kernel gets the idea that the Neuros has been disconnected; the sync manager hangs waiting for a response. After a while, things time out and I get an error message, but I couldn't get the USB mass-storage driver to do anything more until after a reboot. Positron worked fine on another machine, though -- even running the same kernel.
Unless you feel like poking at the code, you probably would be better off not using Positron. The only reason I'm using it is that I do feel like poking at the code, and I'd much rather poke at Python than Perl or Java.
Micah
|
Your quick response to this post: (0 total votes)
I agree (0%)
I disagree (0%) |
|
|
| |
Topic |
|
|
|
| Neuros Forums |
|
|
|
|
|
Forum Locked
Topic Locked
