Reply to thread

Message

<blockquote data-quote="kkendall" data-source="post: 651341" data-attributes="member: 49885">Thanks a lot! I'll try this asap.In MP this should be properly handled though. Now it's getting all souped up. Now when you try to record, the card gets occupied, a message appears saying the recording has started...but it's not. You also need to remove the recording from the schedule, restart MP and restart the tv service before the tv card is released again. Also if you schedule 3 recordings on the same time in the above case, TV server config is saying 3 cards are recording, when there is only one card in the system! Like I said, quite a mess! <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />A proper way for MP should be a popup notification that the recording cannot start because of read/write rights of the specified recording disc/folder and the recording should be cancelled. Something like that.Should I make a separate bugreport for it so it can be fixed in a next release?</blockquote>

[QUOTE="kkendall, post: 651341, member: 49885"] Thanks a lot! I'll try this asap. In MP this should be properly handled though. Now it's getting all souped up. Now when you try to record, the card gets occupied, a message appears saying the recording has started...but it's not. You also need to remove the recording from the schedule, restart MP and restart the tv service before the tv card is released again. Also if you schedule 3 recordings on the same time in the above case, TV server config is saying 3 cards are recording, when there is only one card in the system! Like I said, quite a mess! :) A proper way for MP should be a popup notification that the recording cannot start because of read/write rights of the specified recording disc/folder and the recording should be cancelled. Something like that. Should I make a separate bugreport for it so it can be fixed in a next release? [/QUOTE]

Verification