Closed Athospd closed 3 years ago
Thanks. I think you are right that we are reading data that happens to have exactly the value of what is NA_INTEGER in R.
I have added a workaround, could you confirm that this solves your issue (and doesn't introduce any new problems)?
For this particular example your workaround worked perfectly! i'll let you know if I face any other problem. Thank you very much for this package.
PS: you called it a "workaround", so I'll let you decide if this issue should be closed now or not, despite the main problem had been fixed.
OK so hopefully no major side effects :)
It seems that numeric overflow is causing NA outputs. And bit rate is not been taken into account as well (apologies for my poor English speaking skills).
Created on 2021-01-19 by the reprex package (v0.3.0)