-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Concatenate melspec graph + basemodel graph #47
Comments
The recognition model fundamentally used now is built with pytorch and the export is in onnx. Therefore I am not sure if both can be merged reliably Moreover the logmelcalc.tflite has a small bug due to which the graph cannot process more than 1 sample at a time i.e batch size should be 1 Due to the same reasons both the base model and the preprocessing graphs where not merged together |
I see, thanks for the explanation! Hmm yeah I think merging the new onnx model with tflite graph will be very tricky. Do you still keep a copy of the script/weights used to convert the old Tensorflow model (e.g: in SavedModel/Keras/etc format/etc) into p/s: understand that the new pytorch/onnx model performs much better than the old tensorflow model, but the size is a bit too huge + personally inclined to use TFLite as the edge inference engine, hence still interested to play around with the old version first haha |
hi unfortunately I dont have the old tensorflow wieghts (thanks to me not keeping backups during my undergrad days), but soon I am planning to train a new tflite model with substantially smaller size and better performance, will also make sure that from training everything is reproducible, thanks for the patience |
Hi, first of all, thank you for sharing this awesome work!
I noticed that the first model version was divided into two separate graphs
logmelcalc.tflite
andbaseModel.tflite
. Wondering if there is any rationale behind this?Context: I am considering merging these two graphs into a single
.tflite
file for easier management. So wanted to check if this is feasible and if there are any potential issues I should be aware of.The text was updated successfully, but these errors were encountered: