Your Digital Media Has Never Looked So Good

 
goattee
Topic Author
Posts: 40
Joined: Thu Oct 04, 2007 4:22 pm
Location: Bangkok, Thailand
Contact:

Last "safe" version to use?

Mon Mar 24, 2008 1:36 am

Have any of the Firefly nightlies > 1696 proven to have the stability of 1586 (or Roku's "blessed" 1.0 and 1.1 versions)?

I am currently running Firefly svn-1586 on a Windows XP SP2 machine. I just added .flac to the list of extensions. On scanning, Firefly seems to complain about a large proportion of my .FLAC files. Reading the release notes and comments from more adventurous users, it seems that later nightlies cope with reading the FLAC metadata better. But I don't want to live on the bleeding edge with crashes and poor performance.

I had tried 1696 a few months back but had to back off. (Rebuffering went way up in combination with the last beta Roku firmware release and the database seemed to fail when switching from one large smart playlist to another. Ron seemed to concur with the decision to back off.)

My clients are two Roku products (R1000 and M1001) and occasionally Itunes on PC's around the house.
Last edited by goattee on Mon Mar 24, 2008 2:23 pm, edited 1 time in total.
 
stretch
Posts: 623
Joined: Fri Dec 16, 2005 12:29 am
Location: Australia

Mon Mar 24, 2008 4:48 am

svn-1696 running on a slug with an sqlite3 database works OK for me.
Avoid anything between svn-1586 and svn-1696 as they have memory leaks.

An exception in my case is with my ReadyNAS NV+. Infrant applied the memory leak fixes from svn-1696 to svn-1676.
That gave them a stable and recent version of firefly to include with the latest firmware without svn-1696's database problems (even though they use an sqlite3 database)
2 x M2000's
Infrant ReadyNAS NV+ with Firefly svn-1676
NSLU2, 500GB Maxtor One Touch III, uNSLUng 6.8, Firefly svn-1696
music library in FLAC format
 
mas
Posts: 281
Joined: Tue Dec 05, 2006 11:46 am

Thu Mar 27, 2008 4:17 pm

The svn-1696 is quite ok but not precisely as stable as the 1586, which ranks even with the totally outdated official stable versions.

Best recommendation for someone wanting a stable system is still svn-1586. There has not been any update for months on the 1696 now so dont expect something as stable as 1586 soon.
Those who sacrifice freedom over safety deserve neither.
 
mas
Posts: 281
Joined: Tue Dec 05, 2006 11:46 am

Thu Mar 27, 2008 4:19 pm

An example: Accessing the svn-1696 with winamp by manually pumping a streaming url of the share into it I was able to crash the server. 1586 survived it.

For most regular things svn-1696 works quite ok though, but the additional features in comparison to 1586 aint huge anyway, so stick to 1586 if you want a stable thing.
Those who sacrifice freedom over safety deserve neither.
 
goattee
Topic Author
Posts: 40
Joined: Thu Oct 04, 2007 4:22 pm
Location: Bangkok, Thailand
Contact:

Thanks

Fri Mar 28, 2008 2:18 am

Thanks stretch and mas for your feedback. I will stay put. While reading your comments I went back and examined the log and discovered that the flac "metadata errors" were simply because the "objectionable" .flac files had non -ASCII characters in their filenames (Brazilian and German music). So I renamed the files using ASCII and presto-- no more metadata errors.
 
cinnamonsigh
Posts: 19
Joined: Tue Feb 06, 2007 7:00 am
Location: Australia

Sat Oct 18, 2008 9:05 pm

Since upgrading to 1586, all my albums with non-ascii characters are not showing up. What can I do? Do i need to downgrade or upgrade?

Thanks
 
goattee
Topic Author
Posts: 40
Joined: Thu Oct 04, 2007 4:22 pm
Location: Bangkok, Thailand
Contact:

Sat Oct 18, 2008 9:19 pm

cinnamonsigh wrote:
Since upgrading to 1586, all my albums with non-ascii characters are not showing up. What can I do? Do i need to downgrade or upgrade?


Can you be more specific? Are the filenames non-ASCII? Or the tags? Or both?

And when you say "not showing up:" what client or other tool are you viewing the results with? (A Roku device? Itunes? Other?)

If your filenames have non-ASCII characters, please learn from my experience-- alter those filenames! I have not had any trouble with extended characters in the tags.
 
cinnamonsigh
Posts: 19
Joined: Tue Feb 06, 2007 7:00 am
Location: Australia

Sat Oct 18, 2008 9:48 pm

Sorry for supplying so little information - very thoughtless of me.
And thanks for help.

The problem lies in the tags. For example, my music by Björk is not showing up. All tags are normal characters except for the artist tag. The filename is also only normal characters. (edit: however, in this case the directory has an extended character)

This particular character ö is not in the basic ascii set, but is in the extended ascii set.

I'm accessing firefly with my Roku Soundbridge M2000, but I just checked iTunes and the problem is there too.

I recently upgraded to 1586 from an old stable release iirc.
 
goattee
Topic Author
Posts: 40
Joined: Thu Oct 04, 2007 4:22 pm
Location: Bangkok, Thailand
Contact:

Sat Oct 18, 2008 9:59 pm

OK. Now that we know that both Roku and Itunes exhibit the same problem we know that Firefly is the reason.

Also we now know that the path has extended characters. I too did not provide complete information. The PATH (including device + directory + filename) must be free of any extended characters.

Chances are that Firefly log is showing errors when attempting to read those paths. If you are using Windows, I strongly recommend download the free "Tail for Windows." You can Google for it. This simple utility will always display the bottom of a text file.

The log file is found in the same directory tree as the Firely program. You can run Tail and watch as Firefly y scans. This way you can identiry all the directories and/or filenames you need to change. Let me know how that goes. Or ask more questions.
 
cinnamonsigh
Posts: 19
Joined: Tue Feb 06, 2007 7:00 am
Location: Australia

Sat Oct 18, 2008 10:16 pm

I'm not going to change any filenames or tags, simply because I don't need to - there was no problem last week.

Anyway, here is one example from the log:
2008-10-19 13:05:09 (339c8f30): Cannot read FLAC metadata from E:\Music Directory\FLAC\Kurt Masur, Karel Ancerl\Kurt Masur, Karel Ancerl - Dvorák- Slavonic Rhapsodies & Slavonic Dances\07. Slavonic Dances, Op. 46, No. 4 in F major (Tempo di minuetto).flac
2008-10-19 13:05:09 (339c8f30): Skipping E:\Music Directory\FLAC\Kurt Masur, Karel Ancerl\Kurt Masur, Karel Ancerl - Dvorák- Slavonic Rhapsodies & Slavonic Dances\07. Slavonic Dances, Op. 46, No. 4 in F major (Tempo di minuetto).flac - scan failed


the details for that particular file are:
Artist Kurt Masur, Karel Ancerl
Title Slavonic Dances, Op. 46, No. 4 in F major (Tempo di minuetto)
Album Dvorák: Slavonic Rhapsodies & Slavonic Dances
Track 07
Disc
Genre Classical
Year 1985
Rating
Composer
Size 18.98 MB (71% Compressed)
Original Size 65.29 MB
Length 6 minutes 28 seconds
Channels 2 (stereo)
Sample Rate 44.1 KHz;
Sample Size 16 bit
Bit Rate 1,411 kbps
Encoder FLAC reference libFLAC 1.1.4 20070213
Encoder Settings
Audio Quality Perfect (Lossless)
Contains CRC, ID Tag [Vorbis Comments]
Channel Mapping
File 07. Slavonic Dances, Op. 46, No. 4 in F major (Tempo di minuetto)
Type flac File [.flac]
 
stretch
Posts: 623
Joined: Fri Dec 16, 2005 12:29 am
Location: Australia

Sat Oct 18, 2008 10:26 pm

cinnamonsigh wrote:
I'm not going to change any filenames or tags, simply because I don't need to - there was no problem last week.


Was that before or after upgrading to svn-1586?
If it was still working after the upgrade, had Firefly done a rescan at all?
2 x M2000's
Infrant ReadyNAS NV+ with Firefly svn-1676
NSLU2, 500GB Maxtor One Touch III, uNSLUng 6.8, Firefly svn-1696
music library in FLAC format
 
cinnamonsigh
Posts: 19
Joined: Tue Feb 06, 2007 7:00 am
Location: Australia

Sat Oct 18, 2008 10:40 pm

The order of events was:

1. everything was fine, but I had to format so I thought I might as well upgrade (in the hope that transcoding and streaming may be more efficient because I'm anticipating 2 more soundbridges in my house soon)

2. upgraded to 1586

3. firefly unhappy with extended characters

4. I did a full scan and it made no difference

Edit: I'm not 100% certain of what version I was using before 1586 but I think it was probably 1.1b1 available here: http://forums.rokulabs.com/viewtopic.php?t=11098
 
Iris
Posts: 33
Joined: Sun Nov 19, 2006 11:26 am
Location: Canada

Sun Oct 19, 2008 12:53 am

I've been there and v1586 won't scan filenames with extended/accented characters. The solution really is to rename the files - the tags don't need to be. I'm using MediaMonkey to manage my music and it has a feature called "Auto-Organize" that will rename the files so that there compatible with FireFly yet keep the tags as is. You really should check it out...

Iris
Roku M1001 v3.0.52 x 2 | R1000 v3.0.52
NAS: Maxtor SS+ v2.6.2-openmss1-rc2
Linux Server: Firefly svn-1586 mipsel pkg
Router: Linksys WRT54GS
VisualMR v2.0.0.28954 on iPAQ
 
cinnamonsigh
Posts: 19
Joined: Tue Feb 06, 2007 7:00 am
Location: Australia

Sun Oct 19, 2008 1:21 am

Thanks for your help iris.

I really don't want to edit any files, but I'll consider that as a final option.

Can anyone suggest a good firefly build which does support extended characters?
 
stretch
Posts: 623
Joined: Fri Dec 16, 2005 12:29 am
Location: Australia

Sun Oct 19, 2008 3:04 am

svn-1696 is also broken for extended character support.

iirc the transcoding section Firefly has been stable for some time.
My NSLU2 (133MHz processor) is capable of transcoding two different flac files to two SB M2000's so if you only upgraded for improved transcoding then you can safely revert to the older version that does support extended characters.

If you're up to compiling Firefly yourself you could try svn-1737.
2 x M2000's
Infrant ReadyNAS NV+ with Firefly svn-1676
NSLU2, 500GB Maxtor One Touch III, uNSLUng 6.8, Firefly svn-1696
music library in FLAC format

Who is online

Users browsing this forum: No registered users and 1 guest