Thema: SmartDVB 0.2.5 RC 1

[Snoop]

Aaaaaaah! 
Danke! 

[SiLæncer]

Da war bestimmt die Datenbank beschädigt

[jackjavo]

hi snoop. Yes this can happen sometimes with sqlite it seems, i not sure anymore if there were internal functions to clear a corrupted db. But in any case the EIT data is always reloaded if you
just remove that file, maybe in such corruption cases i could just ask that in the future and remove those popups which i also have had and are tedious sorry...

[Snoop]

No problem, SiLæncer's tip was the solution. Now SmartDVB works really flawless! It deserves its name

[jackjavo]

hello guys. I have a latest release test here, mainly stability changes (little ones) but anways i'll send it to most here just informing..

[ritschibie]

Many thanks, jackjavo! 

Is it the 0.2.5 final?

greetings
Ritschie

[jackjavo]

Hi richibie,

No not yet i'm sorry to say as small issues keep popping up and i've been urged by let's say some to try to get as much details as possible right this time, and i agree ofcourse as in the  past i was sometimes too quick with these things out of urges to well continue, but this is not a real professional attitude ofcourse (in the past i worked for companies and well there it's obligatory, but before this smart wasn't that well known so i took things easy let's say)..

regards,
jack

[Jürgen]

My second tuner, Noxon DAB+ used for DVB-T, does not work with this last test version. but it did before, and still does with the previous version.

BTW, I've found tons of registry entries for SmartDVB transponder lists. Why is this?
SmartDVB should find those without the registry, as they are located in a given sub folder.
No other application had to know about this, nor would Windows.
Same goes for SmartDVB special .ax filters, but at least those ain't many.  

And my first installation of SmartDVB was to the default place, C:\<Program Files (x86)>\SmartDVB\Transponders\10296.ini
Uninstalled that one regularily, used C:\SmartDVB instead ever since.
But all the old registry entries are still there, along with the new ones.
Far to many to edit them out manually...

An example is to be seen on my screen shot
 

Scanning on my first position 19.2°E seems to be OK.
Having some issues on the other positions right now, but can't yet specify if those are SmartDVB related or hardware depending, as I'm busy fiddling around with the multiswitches ATM.
And I am still waiting for my 2nd hand satellite spectrum analyzer to arrive, hopefully allowing to specify and solve some nasty level and slope issues then.
Anyway, will try to find out more throughout the next few days, which way ever.

[ritschibie]

Unfortunately, jackjavo, I have to add to Jürgen's comments another one:

I tested for 90 min recording (without the scheduler, manually). After pressing the record knob I sent smartdvb to the task bar (not the tray). After a little bit more than 1 hour smartdvb went into freezing. Menue handling became impossible and clicking on the smartdvb task in the taskbar opened a second smartdvb task in the bar. Something (or something similar) Jürgen observed in an earlier version, I believe. I installed smartdvbrelease into the C:/programs/smartdvb folder.

Edit: I checked Jürgen's registry entry and found this:

[jackjavo]

morning jurgen
Well those transponder registry entries are from the installer (to uninstall i guess). I'm not sure if this can be removed, but i'll check anyways as it has been said before and it's indeed tedious, and didnt' know about those uninstall leftovers you're right you wouldn't want that, so i guess i have to check the installer too thanks for reporting this. And as mentioned before the registry entries for the .ax components are unavoidable i think as that is active-x related let's say.
Sorry about that dvb-t problem, already located that will send you an updated bda.dev and update the install too (due to some lnb-changes i'm sorry, fixes that lead to bugs damn)..
@ritchibie: oh just read your record problem, not much changed there let's hope this was something incidental? I'll test that today too just to be sure..

[Jürgen]

With the new bda device my second tuner is working  again.
Thanks a lot.

Regarding all the registry entries, please have us informed, once that was either uninstalled properly or any other solution found.
As a fat registry is supposed to be one of the main courses for ageing of a Windows installation, I would then find the time, to clean up manually.
Just not over and over again.
On ye ol' Win98, I've been using Norton System Works, to do such clean up semi automatically, but these days this would be waisting money, as that tool set lost most of it's benefits on NT based OS.
Manually doing this is more risky and a pain in the back anyway, so not an option for a frequent routine...

Again, is transponder file registration really necessary, at all? SmartDVB should know about the location anyway, best as a relative path, for possible later portable use.
 

And even filters can come with portable apps, like done on VLC and MPC, AFAIK without touching the registry. A pre defined sub folder structure and relative paths used, this should do the job.
Normally you would not want to make your special filters available system wide, except if a second of your products could use them occasionally.
However, the filters are just a side aspect with no priority, at all.

Specially for comparison of test versions, this could also prevent strange and hard to detect interference between those.

[jackjavo]

Regarding all the registry entries, please have us informed, once that was either uninstalled properly or any other solution found.

I've actually on purpose made this let's say 'permanent' in the installer so that when re-installed smartdvb over the previous version older (and perhaps changed, modified by user) .ini's are retained. But this means that if smartdvb is installed elsewhere, or first uninstalled and then re-installed elsewhere these entries remain in the registry. Simple solution is to not make them permanent for now, on uninstall older .ini registry entries (which are created by the ms installer) will be removed (and you'll also loose old lists with changes in such case as new ones will always be installed). Easy and better for now or is loosing older changed .ini's (with perhaps feeds) too much of a problem??

jj

[Jürgen]

Again, I am not talking about the ini files, just the registry entries for those.

Transponder files and settings, channel database and alike, being part of some kind of an individual profile, should normally be kept on an update, no doubt.
But AFAIK this is not depending on having them mentioned in the registry, if SnartDVB simply looks along the relative path.

However, this gave me yet another idea:
Why not create a profile subfolder system, with all the individual / changing data inside, that won't be touched on updates normally?
Similar to modern (portable) browsers and mailers...

Could even be done for transponder files.
For example, if an ini existed in the profile, this one was to be used.
Updates could then come from the web or NIT, as usual, or alternatively defaults chosen from the original transponders folder.

[jackjavo]

Again, I am not talking about the ini files, just the registry entries for those.

Oh sorry i was also actually talking about the registry entries, see i wasn't clear, but the installer kind of creates and removes those when they are installed or de-installed by the ms installer (and as i said making them permanent makes the ms installer not remove the files or registry entries.

Why not create a profile subfolder system, with all the individual / changing data inside, that won't be touched on updates normally?
Similar to modern (portable) browsers and mailers...

Yes i'll see about doing this when i move all the stuff from the program files to the normal dir in windows 7 for this (i think then we also won't need amin anymore) so i hope to do these things too in future (darn). Oh and i'll check you're right i think not all .ax need to be external right now, but i think it's just the way i made it initially, and evenso, registration/unregister could be done on the fly by the app ensuring it is portable or runnable in such cases (assuming also all vs2010 libraries etc are there on the system).

And i like this idea of a seperate usage profile where you put let's say touched .ini's without touching the original perhaps, just using that as a base, had not thought of that but seems interesting to me yes and a bit of a solution for these re-installs and changed files (also now for example the settings.ini is made permanent for the same reasons as .ini as not to loose changes and thus settings in this case)..

[ritschibie]

Hat schon jemand ausprobiert, ob die neue Version einwandfrei läuft, wenn sie während der Aufnahme in die task bar minimiert wird? Bei mir verlor sie jetzt 2x die Bedienbarkeit (nach etwa einer Stunde war nur noch der screen zu sehen, die Menues waren nicht mehr bedienbar). Das kann ja an meiner Vista task bar liegen, wäre aber interessant, ob es in anderen BS auch abschmiert.