Xiph.Org issueshttps://gitlab.xiph.org/groups/xiph/-/issues2018-01-22T04:18:38Zhttps://gitlab.xiph.org/xiph/vorbis-tools/-/issues/317Add warning when -M is below average for a specific -q2018-01-22T04:18:38ZjazAdd warning when -M is below average for a specific -q```
Using -q x -M y (for streaming purposes), when y is below the average of -q,
it is ignored, although oggenc says " using constrained VBR ( ... , max br
y ) ".
It might be useful to add a warning about this, because if not, it simp...```
Using -q x -M y (for streaming purposes), when y is below the average of -q,
it is ignored, although oggenc says " using constrained VBR ( ... , max br
y ) ".
It might be useful to add a warning about this, because if not, it simply
looks like it doesn't work.
```Michael SmithMichael Smithhttps://gitlab.xiph.org/xiph/Infrastructure/-/issues/34Allow properly linked replies in the mail archives2018-05-14T02:24:00ZDavid BalazicAllow properly linked replies in the mail archives```
Currently , when viewing a message in the xiph web mail archive, for example
http://www.xiph.org/archives/advocacy/0491.html, there is a way to reply to the
author, by clickinf the link with his name at the top , by "From:".
This a...```
Currently , when viewing a message in the xiph web mail archive, for example
http://www.xiph.org/archives/advocacy/0491.html, there is a way to reply to the
author, by clickinf the link with his name at the top , by "From:".
This automatically fill in the right subject, but does not fill in the right In-
Reply-To field, so the mail is not properly linked to the original message.
Also I miss a link for replying to the mail list. Again a proper In-Reply-To
field should be used. Otherwise the message would not be put in the right
thread in the "thread" view.
Currently I construct manually an URL for replying, like :
mailto:someone@somewhere.org&Subject=Re:Something?In-Reply-
To=<some_id.xx.yy.zzz>
I get the proper id by viweing the HTML source.
```Gitlab BotGitlab Bothttps://gitlab.xiph.org/xiph/vorbis/-/issues/328Low level residue decode pseudo code makes no sense2017-04-08T11:08:16ZjripleyLow level residue decode pseudo code makes no sense```
I can't get a direct implementation of the pseudo code to work at all. There's
obvious problems with it such as:
20. if ([classword_count] is less than [classvals_per_codeword]) AND
([partition_count] is less than [partitions_to_r...```
I can't get a direct implementation of the pseudo code to work at all. There's
obvious problems with it such as:
20. if ([classword_count] is less than [classvals_per_codeword]) AND
([partition_count] is less than [partitions_to_read) then continue at step 11
which loops to the wrong point so that classword_count is only ever used as
value 0. In the end I worked out what the implementation in vorbis/lib/res0.c
does and reimplemented it.
The handling of format 2 isn't documented well. The information is there but
it's all implied and not put into pseudo code. Subtle things like the
do_not_decode_flags specifics for format 2 aren't in code.
It's not all bad - this is actually the only part of the entire documentation
I've found unusable.
```Monty MontgomeryMonty Montgomeryhttps://gitlab.xiph.org/xiph/positron/-/issues/366attempting to overfill neuros &#34;hangs&#34; synchronization2006-06-12T11:18:58Zdbergerattempting to overfill neuros "hangs" synchronization```
I told positron to sync a directory with (links to) about 200M worth of mp3's
into the 128M neuros.
It got about 120 megs in and crashed with an uncaught exception - no space left
on device.
I had to remove the neuros from the back...```
I told positron to sync a directory with (links to) about 200M worth of mp3's
into the 128M neuros.
It got about 120 megs in and crashed with an uncaught exception - no space left
on device.
I had to remove the neuros from the backpack - it wouldn't unmount, it wouldn't
respond to the controls - it was dead.
Positron should deal with this more gracefully.
```Stan SeibertStan Seiberthttps://gitlab.xiph.org/xiph/positron/-/issues/367[PATCH] sync kills system interactive response2006-07-17T14:41:37Zdberger[PATCH] sync kills system interactive response```
This is almost certainly not positrons problem - but I'm filnig it here for two
reasons:
(1) i don't know who's problem it is, and
(2) I suspect others will encounter it - perhaps this can be the place where we
figure it out.
I'm t...```
This is almost certainly not positrons problem - but I'm filnig it here for two
reasons:
(1) i don't know who's problem it is, and
(2) I suspect others will encounter it - perhaps this can be the place where we
figure it out.
I'm typing this while positron is in the process of syncing about 200 files to
the neuros. My system (a 2x1Ghz PIII system with 512M RAM) is stuttering. A
top shows no process consuming more than 15% cpu time - but the load average is
4 and the machine is hurting. I'm running the latest RedHat 9 eratta kernel.
```Stan SeibertStan Seiberthttps://gitlab.xiph.org/xiph/positron/-/issues/371Postitron crashes during rebuild2006-06-12T11:26:58ZManuel LoraPostitron crashes during rebuild```
manuel@localhost manuel $ positron rebuild
Creating empty databases...
pcaudio
failedhisi
audio
idedhisi
unidedhisi
Finding existing audio files on the Neuros...
Traceback (most recent call last):
File "/usr/bin/positron...```
manuel@localhost manuel $ positron rebuild
Creating empty databases...
pcaudio
failedhisi
audio
idedhisi
unidedhisi
Finding existing audio files on the Neuros...
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_rebuild.py", line 91, in r
un
silent=True)]
File "/usr/lib/python2.2/site-packages/positron/add_file.py", line 60, in gen_
filelist
allowed_types, silent))
File "/usr/lib/python2.2/site-packages/positron/add_file.py", line 60, in gen_
filelist
allowed_types, silent))
File "/usr/lib/python2.2/site-packages/positron/add_file.py", line 60, in gen_
filelist
allowed_types, silent))
File "/usr/lib/python2.2/site-packages/positron/add_file.py", line 40, in gen_
filelist
metadata = audiofile.detect(fullname)
File "/usr/lib/python2.2/site-packages/positron/audiofile.py", line 28, in det
ect
metadata = detect_func(filename)
File "/usr/lib/python2.2/site-packages/positron/audiofile.py", line 44, in det
ect_mp3
mp3info = MP3Info.MP3Info(f)
File "/usr/lib/python2.2/site-packages/positron/MP3Info.py", line 485, in __in
it__
self.genre = _genres[int(self.genre[1:-1])]
ValueError: invalid literal for int(): 17)(255
```Stan SeibertStan Seiberthttps://gitlab.xiph.org/xiph/positron/-/issues/375[PATCH] Database sorter only sorts the top-level lists2009-04-19T19:18:35Zbcsmit1[PATCH] Database sorter only sorts the top-level lists```
The WOID class' sort() function only sorts the top-level lists. So, when a
song is added to the Neuros, the songs, albums, artists, and genre lists
all get sorted appropriately, but the songs in the second-level lists do
not. If I ...```
The WOID class' sort() function only sorts the top-level lists. So, when a
song is added to the Neuros, the songs, albums, artists, and genre lists
all get sorted appropriately, but the songs in the second-level lists do
not. If I browse songs by album, artist, or genre, they appear in the
order they were added to the Neuros.
I suspect this is because the PAI files aren't being sorted and rewritten
after the SAI files are.
It would be nice if songs browsed by album were sorted by the track number
provided in the metadata, but that's a wishlish item, not a bug. :)
```Stan SeibertStan Seiberthttps://gitlab.xiph.org/xiph/positron/-/issues/379Detecting changes to files for sync2006-06-12T11:31:35Zapm13Detecting changes to files for sync```
It would be very useful if positron could detect file changes. Often times I will edit ID3 tags
between syncs (change genre, etc.) and would like those changes to appear on the neuros. This
could be accomplished either by naively...```
It would be very useful if positron could detect file changes. Often times I will edit ID3 tags
between syncs (change genre, etc.) and would like those changes to appear on the neuros. This
could be accomplished either by naively comparing the mtimes of the files, or even better by
using an rsync type algorithm for the sync (perhaps using pysync
http://freshmeat.net/projects/pysync/?topic_id=251%2C71%2C42%2C912 ).
```Stan SeibertStan Seiberthttps://gitlab.xiph.org/xiph/positron/-/issues/384Positron doesn't recognize Neuros mount2006-06-12T11:42:05ZGitlab BotPositron doesn't recognize Neuros mount```
I've mounted my Neuros at /mnt/neuros, immediatly after formatting the device
completely. Since I've not synced using any software yet, the
directory "WOID_DB" doesn't exist. If I create it, Positron attempts to access
WOID_DB/aud...```
I've mounted my Neuros at /mnt/neuros, immediatly after formatting the device
completely. Since I've not synced using any software yet, the
directory "WOID_DB" doesn't exist. If I create it, Positron attempts to access
WOID_DB/audio/audio.mdb and fails (since that doesn't exist yet). I've tried
postitron rebuild and it still fails.
I've looked through the manuals and read all the bugs that seemed to be
applicable, but I can't find a way to manually create DB files without using my
Windows machine.
```Stan SeibertStan Seiberthttps://gitlab.xiph.org/xiph/positron/-/issues/394'sync' doesn't actually 'sync'2017-08-03T06:41:39Zdberger'sync' doesn't actually 'sync'```
I did some reorganization of my PC-side music archive and expected positron to
"figure it out" during a sync. It didn't - and it forced me to rebuild the
database (which in and of itself isn't bad, but takes a while).
Specifically,...```
I did some reorganization of my PC-side music archive and expected positron to
"figure it out" during a sync. It didn't - and it forced me to rebuild the
database (which in and of itself isn't bad, but takes a while).
Specifically, I had ripped two albums by the same artist which had different
attributions in the CDDB and therefor ended up in two different directories on
the PC:
tom petty/full moon fever
tom petty & the heartbreakers/greatest hits
Once I noticed this, I moved "full moon fever" to live under "tom petty & the
heartbreakers", updated the tags on the ogg files, and did a % positron sync
I ended up with the tracks duplicated on disk as well as in the database. I
tried doing a positron del of the ones I didn't want as: # positron del "tom
petty" and ran (again) into bug 385.
So it seems that sync should check for files that have been removed on the PC
side and remove them (and their database entries) from the neuros *before*
adding the database entries for newly copied files. Further, it makes sense to
remove such files before copying new files to increase the chances that there's
enough space on the device during copy.
```Stan SeibertStan Seiberthttps://gitlab.xiph.org/xiph/positron/-/issues/395how to remove then reinstall files with sync?2017-08-03T06:41:39ZMike Bursellhow to remove then reinstall files with sync?```
Currently, if you remove files with "del", you can't put them back later on, as
far as I can see from the man pages. It would be good to be able to do this.
``````
Currently, if you remove files with "del", you can't put them back later on, as
far as I can see from the man pages. It would be good to be able to do this.
```Stan SeibertStan Seiberthttps://gitlab.xiph.org/xiph/positron/-/issues/400First-time sync crashes if no data to sync.2017-08-03T06:41:39ZjvmFirst-time sync crashes if no data to sync.```
I ran positron config, configured a sync point, and a (place to download
recordings), then ran positron sync, just to see that it seemed to work, before
getting down to installing some music. Both configured directories were empty,
a...```
I ran positron config, configured a sync point, and a (place to download
recordings), then ran positron sync, just to see that it seemed to work, before
getting down to installing some music. Both configured directories were empty,
and the Neuros player was fresh out of the box.
The error message that printed out was:
boojum:~> positron sync
Synchronizing Neuros music database.
Checking for new music... None.
Checking for new recordings... None.
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
"/home/jack/src/positron/dist/positron-1.0/debian/positron/usr/lib/python2.2/site-packages/positron/cmd_sync.py",
line 165, in run
File
"/home/jack/src/positron/dist/positron-1.0/debian/positron/usr/lib/python2.2/site-packages/positron/db/WOID.py",
line 327, in count_deleted
File
"/home/jack/src/positron/dist/positron-1.0/debian/positron/usr/lib/python2.2/site-packages/positron/db/MDB.py",
line 294, in count_deleted
File
"/home/jack/src/positron/dist/positron-1.0/debian/positron/usr/lib/python2.2/site-packages/positron/db/MDB.py",
line 189, in read_record_at
File
"/home/jack/src/positron/dist/positron-1.0/debian/positron/usr/lib/python2.2/site-packages/positron/db/util.py",
line 74, in fread_wordstruct.error: unpack str size does not match format
The workaround was to add a single mp3 file to the configured sync directory and
sync again. After that, everything was ok, even after I deleted the mp3 and
re-ran sync. So, not a big deal, which is why I marked as minor, but not totally
trivial IMHO, because, well, crashes are bad. :^)
Sorry my Python skills aren't up to fixing this myself yet; hope this bug report
has enough info to reproduce and fix.
```Stan SeibertStan Seiberthttps://gitlab.xiph.org/xiph/positron/-/issues/401positron crashes after sync, before rebuilding database2017-08-03T06:41:39ZMike Bursellpositron crashes after sync, before rebuilding database```
I guess this may be related to another bug, but the stack trace is quite
different. I'd just added some more files with a "positron sync", got to the
end and received this error.
A "positron --rebuild" worked fine, but as I've now ...```
I guess this may be related to another bug, but the stack trace is quite
different. I'd just added some more files with a "positron sync", got to the
end and received this error.
A "positron --rebuild" worked fine, but as I've now got 2856 tracks on my
Neuros, this was really too slow!
Checking for new recordings...
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
"/home/jack/src/positron/dist/positron-1.0/debian/positron/usr/lib/python2.2/site-packages/positron/cmd_sync.py",
line 139, in run
File
"/home/jack/src/positron/dist/positron-1.0/debian/positron/usr/lib/python2.2/site-packages/positron/db/WOID.py",
line 154, in get_records
File
"/home/jack/src/positron/dist/positron-1.0/debian/positron/usr/lib/python2.2/site-packages/positron/db/WOID.py",
line 111, in _get_record_at
File
"/home/jack/src/positron/dist/positron-1.0/debian/positron/usr/lib/python2.2/site-packages/positron/db/MDB.py",
line 213, in read_record_at
struct.error: unpack str size does not match format
```Stan SeibertStan Seiberthttps://gitlab.xiph.org/xiph/positron/-/issues/413[PATCH] Error: /neuros does not look like a Neuros mountpoint2017-08-03T06:41:39ZGitlab Bot[PATCH] Error: /neuros does not look like a Neuros mountpoint```
positron works as expected with the 128MB flash backpack.
however when i switch to the 20GB backpack i receive the following on any
positron command:
Error: /neuros does not look like a Neuros mountpoint
what can i do?
``````
positron works as expected with the 128MB flash backpack.
however when i switch to the 20GB backpack i receive the following on any
positron command:
Error: /neuros does not look like a Neuros mountpoint
what can i do?
```Stan SeibertStan Seiberthttps://gitlab.xiph.org/xiph/vorbis-tools/-/issues/443oggenc: leaves a file after trying to encode with invalid quality setting2018-01-22T04:18:38Zccheneyoggenc: leaves a file after trying to encode with invalid quality setting```
This bug was copied from Debian BTS bug #157334:
When running oggenc with an invalid quality setting (like -3) it leaves
an empty file behind.
Example:
$ oggenc -q -3 foo.wav
Opening with wav module: WAV file reader
Encoding "foo....```
This bug was copied from Debian BTS bug #157334:
When running oggenc with an invalid quality setting (like -3) it leaves
an empty file behind.
Example:
$ oggenc -q -3 foo.wav
Opening with wav module: WAV file reader
Encoding "foo.wav" to
"foo.ogg"
at quality -3.00
Mode initialisation failed: invalid parameters for quality
$ ls -l
total 54896
-rw-r--r-- 1 caereth caereth 0 2002-08-20 02:31 foo.ogg
-rw-r--r-- 1 caereth caereth 56149340 2002-08-20 02:31 foo.wav
$
I don't think that zero-size file should be left there..
```Michael SmithMichael Smithhttps://gitlab.xiph.org/xiph/vorbis-tools/-/issues/448ogg123: input buffer drains not handled2018-01-22T04:18:38Zccheneyogg123: input buffer drains not handled```
The following bug was copied from Debian BTS bug #198765:
ogg123 don't handle input buffer drains. There should be an option to
make ogg123 prebuffer input 'til -p when the input buffer is drained (or
goes below a certain level).
T...```
The following bug was copied from Debian BTS bug #198765:
ogg123 don't handle input buffer drains. There should be an option to
make ogg123 prebuffer input 'til -p when the input buffer is drained (or
goes below a certain level).
This is needed when, for certain reasons, the input buffer reaches 0
(VBR files over network) and the output buffer becomes empty (audio
starts dropping for an undefinitely amount of time).
I actually overcome to this by scroll-locking the terminal for a certain
amount of seconds, and then unlock. This way the output buffer stops,
while the input buffer gets filled thanks to the TCP-stack queue.
```Stan SeibertStan Seiberthttps://gitlab.xiph.org/xiph/positron/-/issues/452utf-8 error on sync2017-08-03T06:41:39Znandwalsutf-8 error on sync```
when running positron sync, i occasionally (but always on the same files) get
this:
~> positron sync
Synchronizing Neuros music database.
Checking for new music...
Traceback (most recent call last):
File "/usr/bin/positron", l...```
when running positron sync, i occasionally (but always on the same files) get
this:
~> positron sync
Synchronizing Neuros music database.
Checking for new music...
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 93, in run
silent=True))
File "/usr/lib/python2.2/site-packages/positron/add_file.py", line 40, in
gen_filelist
metadata = audiofile.detect(fullname)
File "/usr/lib/python2.2/site-packages/positron/audiofile.py", line 28, in
detect
metadata = detect_func(filename)
File "/usr/lib/python2.2/site-packages/positron/audiofile.py", line 86, in
detect_oggvorbis
actual_keys = map(string.lower, vc.keys())
UnicodeError: UTF-8 decoding error: unexpected code byte
~>
so, i'm guessing here that there's some unicode characters that poitron can't
recognize, or something, yes? is there a way to fix this? without at least it
returning the file that caused the error, i have to add files manually, which is
tedious.
thanks!
nandwals
```Stan SeibertStan Seiberthttps://gitlab.xiph.org/xiph/positron/-/issues/465tracknum isn't lower cased2017-08-03T06:41:39ZGitlab Bottracknum isn't lower cased```
The code in add_file.py says tracknum.lower(), but I think it means tracknum =
tracknum.lower()
Just incase the track has letters in it.
Line 94 of add_file.
Ciao!
``````
The code in add_file.py says tracknum.lower(), but I think it means tracknum =
tracknum.lower()
Just incase the track has letters in it.
Line 94 of add_file.
Ciao!
```Stan SeibertStan Seiberthttps://gitlab.xiph.org/xiph/positron/-/issues/481positron barfs on some MP3s --- 1.0 worked on them.2017-08-03T06:41:39ZGitlab Botpositron barfs on some MP3s --- 1.0 worked on them.```
anthony@bohr:anthony$ positron sync
Synchronizing Neuros music database.
Checking for new music... assical/Beethoven/Beethoven - Vio...
Traceback (most recent call last):
File "/usr/bin/positron", line 174, in ?
main(s...```
anthony@bohr:anthony$ positron sync
Synchronizing Neuros music database.
Checking for new music... assical/Beethoven/Beethoven - Vio...
Traceback (most recent call last):
File "/usr/bin/positron", line 174, in ?
main(sys.argv)
File "/usr/bin/positron", line 156, in main
cmd.run(config, myNeuros, remaining[1:])
File "/usr/lib/python2.3/site-packages/positron/cmd_sync.py", line 93, in run
silent=True))
File "/usr/lib/python2.3/site-packages/positron/add_file.py", line 69, in
gen_filelist
allowed_types, silent))
File "/usr/lib/python2.3/site-packages/positron/add_file.py", line 69, in
gen_filelist
allowed_types, silent))
File "/usr/lib/python2.3/site-packages/positron/add_file.py", line 42, in
gen_filelist
metadata = audiofile.detect(fullname)
File "/usr/lib/python2.3/site-packages/positron/audiofile.py", line 28, in detect
metadata = detect_func(filename)
File "/usr/lib/python2.3/site-packages/positron/audiofile.py", line 44, in
detect_mp3
mp3info = MP3Info.MP3Info(f)
File "/usr/lib/python2.3/site-packages/positron/MP3Info.py", line 534, in __init__
id3v2 = ID3v2(file)
File "/usr/lib/python2.3/site-packages/positron/MP3Info.py", line 239, in __init__
frame = ID3v2Frame(file, self.major_version)
File "/usr/lib/python2.3/site-packages/positron/MP3Info.py", line 128, in __init__
self.data = _strip_zero(file.read(self.size))
MemoryError
```Stan SeibertStan Seiberthttps://gitlab.xiph.org/xiph/positron/-/issues/494Key out of bounds error while trying to delete entire /neuros/music directory2017-08-03T06:41:39ZmpmKey out of bounds error while trying to delete entire /neuros/music directory```
I need to delete about 1.7GB from the neuros (the entire database and all
music). To do this, I did:
positron del /neuros/music
After processing about 35 files, positron quits with an "out of bounds" error.
The file it quits on is...```
I need to delete about 1.7GB from the neuros (the entire database and all
music). To do this, I did:
positron del /neuros/music
After processing about 35 files, positron quits with an "out of bounds" error.
The file it quits on is not the same (I rerun the command and it quits again on
a different file--as though it had already deleted the previous 35 or so files).
There isn't anything really unique about my music or the last file positron
processes. If there is anything else that is needed I can provide it.
The error is:
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_del.py", line 116, in run
del_track(config, neuros, sourcename, sai_index)
File "/usr/lib/python2.2/site-packages/positron/cmd_del.py", line 77, in del_track
neuros_path = neuros.db["audio"].get_record(sai_index)[8].lower()
File "/usr/lib/python2.2/site-packages/positron/db/WOID.py", line 146, in
get_record
(pointer, pai_pointer) = self.sai[index]
File "/usr/lib/python2.2/site-packages/positron/db/SAI.py", line 79, in
__getitem__
raise IndexError("Key out of bounds")
IndexError: Key out of bounds
```Stan SeibertStan Seibert