Sorry I’ve missed the formal announcement, but I found some code online that show’s a simple guitar tuner using Corona (specifically the two functions mentioned above), but when I searched the current doc’s there’s no mention of them.
Have these functions been deprecated and removed from Corona or has the functionality been replaced with some other functions.
Any pointers on this would be much appreciated.
Thanks (in advance)
Jon…
Can you post some code for us to look at? Or a link on where you got the code?
–InfiSnyp
Please post a link to the code you are talking about to give us a place to start.
i.e. This code:
I found some code online…
I hunted around and found this (old link): https://developer.coronalabs.com/node/2559
I also dug around and found this:
https://docs.coronalabs.com/daily/api/type/Recording/index.html
I think object:getSampleRate() is the equivalent of getTunerFrequency()
We no longer support the tuner feature. It had various problems. Especially Android. And the feature wasn’t popular enough to justify the large amount of work it took to maintain/resolve its various platform problems. Nor did our tech-support team know how to support it. So, unfortunately, we’ve given up on it and removed the feature. We have no plans on bringing it back. Probably not the answer you wanted. Just being upfront and honest with you.
Hi Joshua,
Thanks for the answer, you’re right not what I was hoping to hear but still at least I know.
When I saw the snippet of code, I had an idea in mind - that’ll have to go on the back burner for now
We have a game within our app that makes use of the recording:startTuner() and recording:stopTuner() function. It works well enough for our purposes.
Removing this breaks our app.
Can you leave it in as an unsupported function rather than removing it?
Thanks
Studycat
@Joshua - maybe you can get Corona to open source those functions or provide them as a plugin with the caveat that they are unsupported and dev’s should use them at their own discretion.
Why not just add it as a plugin, or keep it in but don’t offer customer service? Surely there’s a way to keep my legacy content working. I can use an older version of Corona to build today, but once some breaking change occurs for Apple or Android, I have to update to the newest version of Corona to build, and then I’m screwed.
This affects my app a lot – and it’s bad form to sell a product with a feature, and then remove it with no formal announcement. What gives? Did we do something bad to deserve this?
As I’ve posted above, the tuner APIs had a lot of cross-platform bugs/issues/problems that we were unable to adequately support. Nor was the feature popular enough for us to invest any more time into it. We’ve announced its deprecation back in 2014 in release build #2393 here…
https://developer.coronalabs.com/content/corona-sdk-release-notes-build-2014.2393
I’m sorry this negatively impacts you guys. I’m afraid your only options are to stick to an older build or try your hand at making your own tuner-like plugin yourself via Corona Enterprise.
We also have app with one million downloads and with tuner functionality, but we can’t update this app anymore… we also don’t noticed any issues with tuner functions on Android devices.
Can you post some code for us to look at? Or a link on where you got the code?
–InfiSnyp
Please post a link to the code you are talking about to give us a place to start.
i.e. This code:
I found some code online…
I hunted around and found this (old link): https://developer.coronalabs.com/node/2559
I also dug around and found this:
https://docs.coronalabs.com/daily/api/type/Recording/index.html
I think object:getSampleRate() is the equivalent of getTunerFrequency()
We no longer support the tuner feature. It had various problems. Especially Android. And the feature wasn’t popular enough to justify the large amount of work it took to maintain/resolve its various platform problems. Nor did our tech-support team know how to support it. So, unfortunately, we’ve given up on it and removed the feature. We have no plans on bringing it back. Probably not the answer you wanted. Just being upfront and honest with you.
Hi Joshua,
Thanks for the answer, you’re right not what I was hoping to hear but still at least I know.
When I saw the snippet of code, I had an idea in mind - that’ll have to go on the back burner for now
We have a game within our app that makes use of the recording:startTuner() and recording:stopTuner() function. It works well enough for our purposes.
Removing this breaks our app.
Can you leave it in as an unsupported function rather than removing it?
Thanks
Studycat
@Joshua - maybe you can get Corona to open source those functions or provide them as a plugin with the caveat that they are unsupported and dev’s should use them at their own discretion.
Why not just add it as a plugin, or keep it in but don’t offer customer service? Surely there’s a way to keep my legacy content working. I can use an older version of Corona to build today, but once some breaking change occurs for Apple or Android, I have to update to the newest version of Corona to build, and then I’m screwed.
This affects my app a lot – and it’s bad form to sell a product with a feature, and then remove it with no formal announcement. What gives? Did we do something bad to deserve this?
As I’ve posted above, the tuner APIs had a lot of cross-platform bugs/issues/problems that we were unable to adequately support. Nor was the feature popular enough for us to invest any more time into it. We’ve announced its deprecation back in 2014 in release build #2393 here…
https://developer.coronalabs.com/content/corona-sdk-release-notes-build-2014.2393
I’m sorry this negatively impacts you guys. I’m afraid your only options are to stick to an older build or try your hand at making your own tuner-like plugin yourself via Corona Enterprise.