search

JvanKatwijk / eti-stuff

experimental software for creating and interpreting eti frames
GNU General Public License v2.0
21 stars 12 forks source link

[Suggestion] Windows version for the backend #28

Closed lars18th closed 6 years ago

lars18th commented 6 years ago

Hi,

I put this here only as an idea: create a Windows release for the backend.

It can be possible using Qt 5.0 and MinGW.

Regards.

andimik commented 6 years ago

There was a Windows version on https://www.sdr-j.tk/index.html but the latest zip-file does not contain it any more.

JvanKatwijk commented 6 years ago

There is no support for the eti-backend anymore since there is an excellent alternative with the dablin stuff. I did not look at it for a long time

2018-02-16 14:12 GMT+01:00 andimik notifications@github.com:

There was a Windows version on https://www.sdr-j.tk/index.html but the latest zip-file does not contain it any more.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/JvanKatwijk/eti-stuff/issues/28#issuecomment-366231448, or mute the thread https://github.com/notifications/unsubscribe-auth/AITzwIXFs23MaquXLkD4uVQ5XDFckxC8ks5tVX61gaJpZM4SISmZ .

-- Jan van Katwijk

+31 (0)15 3698980 +31 (0) 628260355

lars18th commented 6 years ago

There is no support for the eti-backend anymore since there is an excellent alternative with the dablin stuff

I agree! DABlin, qt-dab and javaDAB are all very good. However, with the exception of DABlin that isn't portable (Linux only) the other two lack support for ETI input from "eti-cmdline". I hope soon one of them can handle this input.

Regards!

andimik commented 6 years ago

I just tried eti backend under Windows (version from April 2017). Believe me, it's better not to have it. So even please don't ask for it.

lars18th commented 6 years ago

Hi @andimik ,

I just tried eti backend under Windows. Believe me, it's better not to have it. So even please don't ask for it.

OK. Then my objective now it's get that other tools (aka DAB players) will support natively ETI input.

JvanKatwijk commented 6 years ago

Well, the later backends run better (just ran a test under W10 with file input, works fine), but spending time/work on the ETI backend is not a priority for me, To make it into a real back-end, attention should be paid to erroneous input, and the back-end code should be made inline with that of the qt-dab program. Lots of work, and why???

2018-02-20 18:42 GMT+01:00 lars18th notifications@github.com:

Hi @andimik https://github.com/andimik ,

I just tried eti backend under Windows. Believe me, it's better not to have it. So even please don't ask for it.

OK. Then my objective now it's get that other tools (aka DAB players) will support natively ETI input.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/JvanKatwijk/eti-stuff/issues/28#issuecomment-367058070, or mute the thread https://github.com/notifications/unsubscribe-auth/AITzwB60ZtssEyIP0dcWy1CmnL_GWU5Iks5tWwPzgaJpZM4SISmZ .

-- Jan van Katwijk

+31 (0)15 3698980 +31 (0) 628260355

lars18th commented 6 years ago

Hi @JvanKatwijk ,

Lots of work, and why???

I know why not develop a lot more the ETI backed. However, it's good to work on obtain a decoupled DAB demodulator (frontend) from the DAB decoder (backend). As this will simplifies the work done by the decoder. And in this scenario the ETI bitstream can be a good interchange format.

So, the only problem now it's to expand the current DAB players for supporting the ETI input.

Thank you for all your good work! :smile: