The sound recorder gizmo screenings used to take a few seconds. Now they are taking more than a day or longer. In many cases, I am recording short snippets of my own voice. Why is this taking so long?
Back when the copyright stuff first came out, I noticed occasionally one would just fail to process altogether. Usually had to redo it to get it to go through.
Upcoming Events: AMA- Getting Started with Typescript Thursday, April 17th 5 PM PT - Register Workshop - World Planning Made Simple Thursday, April 23rd 11 AM PT - Register April Programming Calendar
This is every recording that I have done for the past 7-10 days, which is around 25 of them. I don't want to have to redo all of them. The gizmo isn't working properly, so I reported it as a bug.
Well in that case I hope they get on it quick with the contest going right now.
Upcoming Events: AMA- Getting Started with Typescript Thursday, April 17th 5 PM PT - Register Workshop - World Planning Made Simple Thursday, April 23rd 11 AM PT - Register April Programming Calendar
My plans will be technically disqualified if this is not fixed quickly. Perhaps they are preparing to trust creators to only use sounds that are not under copyright opening to door to uploading .wav and .mp3 files we have created with our own two hands and not a half-brain ai (anti-intelligence) system.
Me too, BerryBerry! I wouldn't be opposed to their making way for such new features, in fact, that would be most welcome! But, the existing sound recorder option needs to be operational in the meantime. Otherwise, some of us are left disqualified, as you say. Unless we pivot to a whole other idea and start over. Not berry nice, I'd say.
@BerryBerryNice If you could please add your +1 to the bug report that I posted in the Meta Quest and Horizon Discord... maybe someone will look at it.
We have an open bug ticket internally for this, thank you for flagging.
For future issues, following the steps outlined in this bug reporting post will help get the issue to the right team in the quickest manner.
For desktop editor bugs that are build blocking, file a bug report after the problem occurs using the "Report an Issue" menu option so that editor logs are recorded and sent. Then, you can file a support ticket using Zendesk for updates and follow-ups regarding the issue. This method is the recommend way to file issues and not through the community server discord channel.
Can we talk? There is a reason that organic discussion of pressing issues takes precedence over some of the more formal “Bug Reporting” methods.
When we file bug reports we are only able to provide details of some of the issues created by the Sound Gizmo. The “pest control” agents are only able to choose from the pesticides that are on the shelves, and unable to improvise or suggest other options. The folks that are using the Meta Walled Garden have a much more hands on understanding of both the problems and in most cases, solutions for everyone.
Let’s not stifle discussion here because it might not fit into a silo.
And let’s not put guardrails on discussions in the only effective discord we are left with.
The truth is we want as many META EYES on this stuff ass possible today.
