Basically I think that the quality is too low, and that the movement speed is too high
Basically I think that the quality is too low, and that the movement speed is too high
AIs this the "wobble" mode?
Nboth modes
AWhat are "both"? I lose track of what modes are available. There's about 4 in the experimental build and I rarely use the non-experimental builds.
ZIs there a way to change out the skybox to transparent png since the camera will capture pngs already?
AI don't actually know the answer to that
Zok thanks Andy!
AThere's a wobble mode and a 5 second gif capture.
The 5 second gif capture makes a really nice walk through photobox, but quality is too low to be useful on active sketches
agree that all of these would be beneficial improvements
One of the other reasons I like the gif camera is that it reacts to audio, but doesn't record audio by default.
This is important for social media sharing, as I almost always listen to music while working.
Would be nice to have that as an option on the video camera as well
The 5 second gif capture makes a really nice walk through photobox, but quality is too low to be useful on active sketches
agree that all of these would be beneficial improvements
One of the other reasons I like the gif camera is that it reacts to audio, but doesn't record audio by default.
This is important for social media sharing, as I almost always listen to music while working.
Would be nice to have that as an option on the video camera as well
AThere's actually 4 modes defined:
ABut they are disabled in non-experimental builds. There's also keyboard shortcuts to adjust some of the parameters
Athere's also this:
Awhich seems to be sub-modes for the circular gif?
ANot sure why Quest can't do mp4 video but I'm tempted to allow it to capture frame sequences as an option and leave it up to the user to compile them into video, gif or whatever. The current gif mode should just be a quick convenience mode
A
MI don't recall if we have available on the Quest, but I think output a series of frames plus a bit of documentation listing common options like should be quite useful; it offers a lot more flexibility than writing compressed video, and can fit into any workflow. If we have specific requirements for certain formats, then we can look at offering quick presets too
MI guess we don't have ffmpeg:
AI don't think android allows multiple executables in an apk? or at least they are clamping down on that kind of thing
Ai seem to remember that was the issue with LPGL code - you can to create a single signed binary
AAlthough we could release a "companion app" that made it all user friendly - but something like that probably already exists
MI don't know. We can distribute other files, including executables, using an file (or possibly an , I think it's called), but I'm not an expert on exactly how that packaging works
Agot to be aware there's people who have a quest but don't own a PC or Mac or anything separate.
MFair, but I feel like once we have an on screen keyboard and can name our sketches (and thus do things like foo.tilt -> foo_output/1/xxxx.png), it'll be much easier to output just images and have people put them together. It won't be sufficient for those with no computer... but I think for an MVP, it's definitely a higher priority than one more canned output format that may or may not align with a specific requirement
MOr maybe we can do images -> video as a hosted icosa service? 
Athere must be a dll version of ffmpeg that we can call directly from C#? I wonder how ffmpeg is being called presently.
MAssets/Scripts/Rendering/FfmpegPipe.cs 
Ahmmmm. ffmpeg must have a C API?
Aah - we might hit GPL issues
Mlibavcodec is LGPL IIRC
Aand we're back to exactly what does "linking" mean.
MOr maybe dual licensed GPL/LGPL. BRB, googling
MYep, dual licensed.
MThis looks like it might have some of the answers we need, but I'm about to head out, and don't have time to read everything. Leaving it here for later. https://stackoverflow.com/questions/63946068/how-do-i-embed-a-native-code-library-in-an-android-app-sdk-29
Stack Overflow
I have an app that uses a native code library -- a custom build of ffmpeg as it happens, though that isn't strictly relevant.
Up until now I have added the executable to my res/raw directory and th...
Up until now I have added the executable to my res/raw directory and th...
Athis is all a bit hypothetical. it's already passed my threshold of "too much effort"
Aconsidering there's a workaround
Aeven if people don't have access to a PC - there's web based mp4/gif generators
Amaking it all seamless is a nice to have that can wait until we have a team of developer elves to call upon
Aelves are hard to come by now days. they made a fortune selling pants and no longer want to program
A
Aback to the gif thing - @AncientWorlds - take a look at this object:
A
Atry adding new presets with different settings and see how you get on.
A@Zandy - can't remember if you're running from inside Unity. If so you could try this too
AIf it works and you can come up with some useful new presets we can add them to a future release
AIn terms of gif "quality" - do you mean resolution or something else? Disabling the post processing was mentioned before. That appears to have been accidentally reenabled and would hit gif quality quite badly in some cases
ZWill definitely give it a try @andybak !
A@AncientWorlds I wish we could pin down exactly when gif quality degraded. Was it bad in the first Open Brush release? Is it bad in Multibrush? I can't see what would have changed
AYou said it was fine when you compared with the last Tilt Brush release. I wonder if it was already broken in the initial open source version
MThe gif stuff wasn’t in the initial open sourcing, we had a PR put in for it using another open source library
MSo it may not be the original library used in tilt brush
Aah! that's helpful
ASo - I want to know if it is related to post processing or not. @AncientWorlds - are you pretty certain that Tilt Brush gifs had no bloom etc?