Subsonic Forum

Dear all,

Subsonic 4.6.beta1 was released today with the following changes:

New: Simplified and improved transcoding framework.
New: Improved video quality with H.264 encoding.
New: Reimplemented jukebox. More robust and new features.
New: Share on Google+.
New: Estimate content-length for transcoded audio.
New: Updated Dutch translation, courtesy of Muiz.
New: Updated German translation, courtesy of deejay.
New: Added BUUF theme, courtesy of Fractal Systems.
New: Added UK English translation, courtesy of Brian Aust.
New: Hide dock icon on Mac.
Bugfix: Menu broken in "Settings > Shared media" when logged in as admin.
Tech: Improved security in Linux packages.
Tech: Stronger license check.
Tech: Use UTF-8 when reading playlist files.
API: Include files in root folders.
API: New jukebox features.

Thanks in advance for your feedback!
Sindre

Looks good to me. The menu's when managing Shared Media work correctly now, and the transcoding interface seems MUCH improved!

And I really dig the BUUF theme too. Good job Fractal Systems!

More later if anything comes up.

Great Job again Sindre!

Glenn

One quick suggestion: When looking at an album's details, there are "share" links at the top of the page between the "Clear Rating" button and the "Search Google, Wikipedia, etc..." links.

Now that there is a "Share on Google+" feature, there should be a "+1" button up there next to the facebook and twitter icons.

Working well so far!

Glenn

I am running this standalone on ubuntu server. Everything installed like a dream. I panicked a little when I saw the transcoding page, since I was just recently trying to get .srt subtitles working. But no worries.
Also, hopefully the File Not Found or Access Denied issue goes away...

*sigh*

Thanks Sindre for a bad ass solution!

Just did the upgrade and it fried ALL of my video transcoding.

New transcoding setup also wiped out my mp3 > ogg settings that I had for setup for better performance on Android over 3G.

Mea culpa, I guess I got a bit used to upgrades going pretty smoothly. I should have used my test site first. Big duh on my part.

EDIT: Fixed.

Looking good so far

Give it a good workout then time to put me mods back in (which seems to get harder each time - must be me age )

GJ51 wrote:Just did the upgrade and it fried ALL of my video transcoding.

Oh sorry, forgot to mention that...

4.6 comes with improved transcoding settings (for 95% of the users at least). You can however still retrieve the old transcoding settings my opening http://<yourserver>/db.view and executing "select * from transcoding".

Sindre

sindre_mehus wrote:

GJ51 wrote:Just did the upgrade and it fried ALL of my video transcoding.

Oh sorry, forgot to mention that...

4.6 comes with improved transcoding settings (for 95% of the users at least). You can however still retrieve the old transcoding settings my opening http://<yourserver>/db.view and executing "select * from transcoding".

Sindre

Thanks Sindre,

It was due to some differences in my 4.5 transcode subdirectory. I just copied a cleaner version from one of my other instances and it all worked with the exception of .wtv files that had to be readded into the mix. I'll do the ogg settings later, but I'm sure they'll be OK.

Adding new settings in the transcoding applies them to existing players. This really screws things up when trying to add transcodings only meant to be used on the Android player.

This new system is much simpler, but takes a lot of flexibility away. I'm not sure I'll be able to use it over the long run. I frequently get 70 to 80 players generated. If I add Android specific transcodings, but have no control over the setting being default or not and it applies to all existing players already in use, I'll foul up all the desktop players when I add the android specific settings.

This is exactly the opposite behavior of previous versions that allowed you to select whether or not a transcoding was a default setting and it then had to be added to any previously generated player.

Adding the default check box back in would be helpful and probably make things easier to manage. I wouldn't have an issue with default setting being updated on all exising players if new settings NOT checked as default could be added without updating all players automatically.

I'd like to have the "Enabled" checkbox back as well. This was invaluable in the past for trying different transcodings without losing previous work. Perhaps, just enabling an "Advanced Mode" on the transcoding page that reverts to the old style for us old timers. This way, new users have a simplified interface and tweakers would still be able to have the power and flexibility of the previous setup.

After upgrading to the beta I now see this in the Log:

[11/3/11 12:21:05 AM MST] WARN SettingsService License key is not valid.

Any idea why?

archrival wrote:After upgrading to the beta I now see this in the Log:

[11/3/11 12:21:05 AM MST] WARN SettingsService License key is not valid.

Any idea why?

Lately there has been an increasing problem with people using illegal license keys. This version uses a new and stronger verification that the license key is indeed valid. If you have purchased a license and still get this error, could you please contact me by PM or email so I can look into it?

Thanks,
Sindre

working fine for me

many Thanks as always...

Any chance of getting the tag manipulation issue fixed?

viewtopic.php?f=3&t=7777

Or modifying the prefix filter to work with non space delimited artist names? A_Perfect_Circle shouldn't be listed under A.

I'd love to get custom URL's added into mainline: viewtopic.php?f=8&t=7599

sindre_mehus wrote:

archrival wrote:After upgrading to the beta I now see this in the Log:

[11/3/11 12:21:05 AM MST] WARN SettingsService License key is not valid.

Any idea why?

Lately there has been an increasing problem with people using illegal license keys. This version uses a new and stronger verification that the license key is indeed valid. If you have purchased a license and still get this error, could you please contact me by PM or email so I can look into it?

Thanks,
Sindre

I believe I have identified the error and I'm working on a fix. Will keep you posted.

Sorry for the inconvenience!
Sindre