Thema: SmartDVB 0.3.0 RC

[Snoop]

Is it possible to move this message to the into one corner of the tv screen and shrink it a bit?

[dada]

Hi Jack,
I am having a problem with the latest version (SmartDVB030RCTest). Whenever a plugin is in use (and needed, I tested 3 of these, the common ones) sdvb crashes within a short time (within 5 to 50 seconds ), independent of the codecs used. In addition, when ts is a crypted H264, there would be frequent hickups in the video before the crash.

[ritschibie]

I tested the RCtest twice. Echoing dada, I must say that trying to record with this version resulted twice in a hang up of the program (latest after 30 min). Smart was still active (according to the "taskmanager") but the program just disappeared from it's window. I'm sorry to state that due to the very intriguing outcoming of the italian elections and it's post-processing I am unable to do any further testing (I'm just watching "rai" and others) and will wait for the next candidate. In the meantime I'm using again 0.25 

[Snoop]

I had no time to test a record, but the DVB Subtitle Bug seems to be solved - did not have any crashes with "Das Erste HD".

[jackjavo]

@ritchibie: dada's issue seemed related to disabled timeshift together with crypted stations (timeshift enabled would not exhibit this problem dada). Would that also be the situation with u? I'll for sure make some time now to do some long record tst runs because this 's been reported also before by snoop etc. I won't venture to political comments, otherwise people here might need me to shut up again when i initiate with that stuff . Btw what's with the sudden radio silence from some of our repespected members here (pm if possible)..

[Jürgen]

Well, if you are referring to me, there are private reasons that keep me away from testing, still for a couple of days more.
I am extremely busy ATM, coming home almost for sleeeping only.
And for that activities I even had to interrrupt some reworking on my computers.
Typing this now on a temporal machine setup with no casing...
 
Hope things will change back to normal after this weekend.

[jackjavo]

indeed i did ok then, no rush ofcourse like mentioned before we have all the time at the world, even if all the financial european markets freeze
@richtibie: busy with those record issues, indeed i also had a window freak show after some record time, did see some issues there nd been doing tsts tonight, just had a 4-5 hour hd record without issues so seem to improve for me (seems like something that's even there with 0.2.5 but just quicker visibile with 0.3.0).

[ritschibie]

Strange thing! Yesterday late night I started a new recording with the RCtest. In between I got this message window: "String too long" after 1 hour of recording (more or less) and you're right on this issue because I seem to remember I got this message also 3 or 4 times with 0.25. Clicking them ok they disappeared and nothing happened. I stopped the recording after 2:10 hrs. No problem there.

Today I started a recording around noon. Again, after approx. 1 hour I got the message ("String too long"), tried to click it away but this time instead of the usual 3 message windows I got a whole cascade of messages and after the 9th or 10th click RCtest crashed.

Will try again tonight with the revision I received and report tomorrow.

Thx, Ritschie

[jackjavo]

Hi richtibie:
let's hope it's better wrt long records. One possible alternative compared to previous when you receive that message try to press CTRL-ALT-R to see if you're able to generate a report with that (although probably not if that message prevents the main app to receive those keys), but if possible that would allow me to see exact where that 'string too long' message is located. I'm quite sure it's some form of resource issue hence the unpredictable nature of it...
br,
jj

[dada]

Hi JJ,
I did some long test records (3-4h) during the last days. Did not encounter any problems, no matter minimized or not, encrypted or not. Looks fine to me.
br

[Jürgen]

Just had the first chance, to test the recent beta quickly here, now on a new machine.

First finding, I had to go for a full new install, as the codec related settings did not work, when I tried to re-use my old installation copied from the former machine.
Something important seems to have changed on the MS DTV/DVD codecs, and if it only were those bloody MS IDs....
Again using those codecs now, after acquiring them by opening a h.264 .ts recording in WMP.
But the existing old copies of SmartDVB kept complaining on smart filter issues.
However, right now I am still fiddling around a bit, with getting proper hardware decoding support, even though I am still using the very same graphics card.
So obviously I will have to look far deeper into all the multimedia related stuff.
This is going to take even more time, specially as the former main machine is not available anymore.
Just gave it away to a really good friend of mine, that urgently needed it for the job.
Means, I can't compare beween old and new machine directly.

And this also means, I can't provide you with proper feedback, before the new computer works 100% perfect (or ye ol' second one is restored completely).

BTW, no XP anymore, on the new #1 machine.

[jackjavo]

@dada: tx, i'll consider that matter closed then coz my tests were the same (i hope ritschibie stopped the tst already:) ).
@jurgen: good to see you're at operating order again .
ok tx for this report, some time ago i also saw sporadic smart filter connection issues with ms dtv/dvd codec, didn't really get what seemed to be the issue but since i'd been busy with the code i presumed it might be my fault, so i tried to fix it (since i also fool around with codecs a lot on the test system i presumed it might be my fault but now you mention this it might be a more generic issue).
Do you mean the recent rc tst operates better for you (opposed to previous beta versions). Still quite odd something like this which never really been a problem with ms dtv codec (for me it connected ok from the first go, so you have to wonder what could  or why something's been altered there, directshow wise).
br,
JJ
 

Just had the first chance, to test the recent beta quickly here, now on a new machine.

First finding, I had to go for a full new install, as the codec related settings did not work, when I tried to re-use my old installation copied from the former machine.
Something important seems to have changed on the MS DTV/DVD codecs, and if it only were those bloody MS IDs....
Again using those codecs now, after acquiring them by opening a h.264 .ts recording in WMP.
But the existing old copies of SmartDVB kept complaining on smart filter issues.
However, right now I am still fiddling around a bit, with getting proper hardware decoding support, even though I am still using the very same graphics card.
So obviously I will have to look far deeper into all the multimedia related stuff.
This is going to take even more time, specially as the former main machine is not available anymore.
Just gave it away to a really good friend of mine, that urgently needed it for the job.
Means, I can't compare beween old and new machine directly.

And this also means, I can't provide you with proper feedback, before the new computer works 100% perfect (or ye ol' second one is restored completely).

BTW, no XP anymore, on the new #1 machine.

[ritschibie]

Hi Jack,

I am still testing...

What appears to me to be the root for my problems (as of 6 test recordings all about 2 hrs.) is the CI. Whenever I try to record a crypted stream over CI I get (more or less after 60 min) a smartdvb window "String too long". At first I get 2 windows which disappear after clicking ok in the window, the recording then continues. The program stops when the smartdvb alert window is repeated more than 5 times. This happened during 2 recording tests over 2 hrs, the third one presented 3 times the alert window with a max. of 4 repetitions.

The other 3 recordings were with FreeTv, all of them round 2 hrs. Flawless functioning there, no alert window.

Is there something changed between the RCtest and the previous beta concerning CI embedding?

I know that there are not many people out there using CI/CAM on their dvb card so a check will be difficult. BTW, you were right telling that pressing CTRL-ALT-R when the alert window is open does not result in a report. I will continue tests...

Ritschie

[jackjavo]

ok ritchibie, tx for the report.Nothing altered specific to tt ci code, i'm quite sure. U positive this didn't occur before, even perhaps after longer period with the beta's? Quite odd, could you still try to send a report or better yet save it nd mail me the url here or pm (so i'm positive it's yours, sometimes have quite some reports daily) so i could have a look at the logs to see if somethings there (especially bda.log/smartdvb.log, so if not able to generate report send me those logs after such failure). Just browsed the ci logs, no alterations there. Just to make sure i'll send you current .exe nd especially bda.dev coz the issue might be there ofcourse (probably)..

br,
jj

[Jürgen]

Do you mean the recent rc tst operates better for you (opposed to previous beta versions)

Not really.
I have just tried to keep the former installations alive, by simply copying them over to the new machine, as they did work almost perfectly on the former one.

Before doing this, I already made sure to get MS DTV/DVD codecs for the new machine, by opening a h.264 based .ts recording in Windows Media Player.
This causes WMP to download and install the DTV/DVD codec set to the system.

Once this worked properly, I tried to reactivate my full copies of formerly working SmartDVB folders, with no success, smart filter error.
My ATI codecs also failed, even though they came with exactly the same graphics card as before, and the same catalyst version.
Perhaps something may be individual with that settings, like some nasty MS class IDs or whatever similar.
Means, I was not able, to use any of the codecs actually installed.

So probably the codec listing did not survive the system change, and it seems, there is no easy way to have it refreshed completely in SmartDVB.

This forced me to make a fresh install of the latest SmartDVB test version now.
And that did work at once, with ecactly the same (visible) codec settings as before.
 
I did not expect this to happen, as several months ago, I could change the machine without such trouble, from an AM2+ AMD770 to an AM3 AMD970 system, and then to an AM3 AMD870, all with Phenom II x4 64bit CPUs.
Though, the new one uses a AM3+ FX / Bulldozer CPU on a 990X chipset, and this may possibly be relevant here.

I will try to reconstruct the AM2+ AMD770 machine a.s.a.p., to hopefully be able to compare in deep.
Might als get an idea then, why my energy cost meter still tells me, I don't yet get full hardware decoding from the Radeon HD6670 on the new machine, the way I always had that before and also got it again properly on the freshly installed AMD870 machine (and a GeForce 520 then), before I gave it away, for emergency reasons of the new owner.

Did not re-test SmartDVB on that one in between, as the new user does not want to use it for TV reception in his office, at all.
Just played a selection of files, to check out the most popular formats and for a burn in / stress test.
Mainly CAD and O2C 3D will be used on it now, plus all the usual office and internet stuff.

And if I had learned one thing now, this would surely be, to never ever work on all my machines' hardware at the same time again.
At least one has to stay untouched in any case.

Best regards

Jürgen