Hi Richard, I hope you had a nice vacation.
Yes we fixed that issue, and had a stable build for the Pi and x86 until recently. Unfortunately a bunch of recent codec2 work has broken the freedv-gui build: https://github.com/drowe67/freedv-gui/issues/57 Then we really need to test codec2/freedv-gui in the wild before considering a release. Given we are doing a lot of development in codec2, perhaps we need a system for release candidates that doesn't depend on the moving target that is codec2/master? It would also be really useful to know what codec2/lpcnetfreedv Git Hashs were used for a given freedv-gui build. I think the freedv-gui "About" dialog box stores the freedv-gui git hash, and I label the Windows installer file names like: FreeDV-1.4.1-devel-20200305-d60b0f0-win64.exe So the date and Git Hash is in the file name. Cheers, David On 27/5/20 6:07 am, Richard Shaw wrote: > Ok, so now that I'm back from vacation I'm trying to fix this. I > remember there were some commits around updating the AVX detection code. > I'm guessing I need to tag a new version? > > David, what says you? 1.4.1? Should I use current master? > > Thanks, > Richard > KF5OIM > > > _______________________________________________ > Freetel-codec2 mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/freetel-codec2 > _______________________________________________ Freetel-codec2 mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freetel-codec2
