Reply to thread

Message

<blockquote data-quote="offbyone" data-source="post: 1007610" data-attributes="member: 73415">Keeping it simple, I added two new templates at the google code project, one for a MP2-Bug and one for MP2-Enhancement.&nbsp;I am not sure if I got it already right in the MP2 code yet (probably not), but when an item is added to the queue, it will use the default quality set for that site (if option is provided) or the same chosen on the first downloaded item.&nbsp;&nbsp;I guess you are talking about the MPUrlSourceSplitter logfile here. Haven't checked it lately when running from MP2 - so it might be that it is in extreme verbose mode <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" /> This logging is the only way to find out what is going wrong when requesting files. Kudos go to georgius for this.&nbsp;&nbsp;MP1 already has the progress displayed - I didn't get so far yet on the MP2 side.A download queue manager might be an idea, but I never wanted this plugin to develop into a &quot;downloader&quot;. It's also a bit harder to implement, as the download queue lives in the second AppDomain.An additional info file of some kind could be done, it has been requested already. Well, my todo list grows and time is limited <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" /> You know the problem. Any help/patches are welcome!&nbsp;&nbsp;Somewhere an exception must have happended, I'll try to figure it out.</blockquote>

[QUOTE="offbyone, post: 1007610, member: 73415"] Keeping it simple, I added two new templates at the google code project, one for a MP2-Bug and one for MP2-Enhancement. I am not sure if I got it already right in the MP2 code yet (probably not), but when an item is added to the queue, it will use the default quality set for that site (if option is provided) or the same chosen on the first downloaded item. I guess you are talking about the MPUrlSourceSplitter logfile here. Haven't checked it lately when running from MP2 - so it might be that it is in extreme verbose mode ;) This logging is the only way to find out what is going wrong when requesting files. Kudos go to georgius for this. MP1 already has the progress displayed - I didn't get so far yet on the MP2 side. A download queue manager might be an idea, but I never wanted this plugin to develop into a "downloader". It's also a bit harder to implement, as the download queue lives in the second AppDomain. An additional info file of some kind could be done, it has been requested already. Well, my todo list grows and time is limited ;) You know the problem. Any help/patches are welcome! Somewhere an exception must have happended, I'll try to figure it out. [/QUOTE]

Verification