Bug 4729 – Start transcoding processes at same priority as SlimServer

Bug 4729 - Start transcoding processes at same priority as SlimServer

Summary:

Start transcoding processes at same priority as SlimServer

Status:	NEW

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Transcoding
Version:	6.5.1
Platform:	All Windows XP

Importance:	-- enhancement (vote)
Target Milestone:	Future
Assigned To:	Unassigned bug - please assign me!

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2007-02-03 11:18 UTC by Steve East
Modified:	2011-11-06 23:25 UTC (History)
CC List:	1 user (show)

See Also:
Category:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Steve East 2007-02-03 11:18:01 UTC

When starting transcoding processes (flac.exe, mov123.exe, etc), it would be nice if they were started at the same priority as SlimServer itself. I run SlimServer at Above Normal priority on XP, but my transcoding processes are run at Normal priority.

Comment 1 Blackketter Dean 2007-12-28 07:32:02 UTC

This is probably only an issue on Windows and seems reasonable, though I'd like to know if there's some specific issue that adjusting the priority fixes.

Comment 2 Jim McAtee 2008-01-13 02:42:45 UTC

Isn't there an explicit priority setting in the options for the Scanner process?  I don't know whether this is relatively new - I see it in both 6.5 and 7.0.  I would think that this request is unnecessary with that option.

Comment 3 Alan Young 2011-11-06 23:25:12 UTC

Unassigned bugs cannot have a priority.