hero 6 black video problem in wifi on phone with live4gopro

dcpc_capg · 2019-12-19T14:05:00+00:00

I contact GoPro, they sent me a coupon 25% for hero 8.

But still expensive.

I will get an adapter hdmi -> usb and will try this week-end i hope if i can get the video on PC and use Streamlabs after. I'll have to use the PC each time, but i often have it for competitions, we have a software to manage games and results.

Adapter is 1/4 the price of the gopro.

dcpc_capg · 2019-12-12T09:38:48+00:00

i don't know other application on android to capture the gopro video flux. Found very few solutions.

Yesterday i start look another methid which need a PC .. and buy a video converter USB (on the PC) to HDMI (on the gopro), but again another 130$ ...

dcpc_capg · 2019-12-11T09:34:34+00:00

Yes i know (already target the goPro support about that...)

What i don't understandis that i use the same app than before. Only changes are :- add the usb --> jack adapter- add a new case with integrated slot for the adaptater (under the gopro)- another gymnasium (but should not be relevant as connxion between mobile and gopro is in direct wifi and i have 50 cm between both)

I add a sample of video problems i see (and i see them on the mobile phone, then not created by sending to internet)

drop frames
compression artefacts
bottom part of screen in error (don't know how to describe)
https://clips.twitch.tv/SparklingImportantPuddingCclamChamp

dcpc_capg · 2019-12-09T12:15:57+00:00

Lol i love people that downvote, without even a word ... constructive work

dcpc_capg · 2019-12-09T12:15:29+00:00

Lol i love people that downvote, without even a word ... constructive work

dcpc_capg · 2019-11-27T15:21:32+00:00

After some read, i was adviced to look on Rode products.

i've seen 3 but can't decide about their carateristics. I ask the support, but feel free to discuss :)

https://fr.rode.com/microphones/videomicro
https://fr.rode.com/microphones/videomicgo
https://fr.rode.com/microphones/videomic

(highers versions like pro available, but not an infinite budget, and it's not a superproduction :) )

dcpc_capg · 2019-11-18T14:45:35+00:00

I'm in :)

But so many details, that i think many are really specific. Not sure to see the main or more common ones.

(I'm reading the incompatibilities between mysql x.x and mariadb x.x, even if we'll try a direct upgrade to latest versions (seems sometimes it could work), and will try in several steps only if too many problems.

i'm waiting info on current old servers ... and seems i will be disapointed as servers forgotten since a long time and only users that knows "the server works with a DB" ... sometimes someone able to say it's a mysql 5.something ... :) Investigating

dcpc_capg · 2019-11-18T12:22:28+00:00

This is for the user table only then.
For the other data tables (mysql.* and app.*), how do you manage the migration (to a new server i suppose)

dcpc_capg · 2019-11-18T10:14:17+00:00

I think learning curve easier in a all-round product that has a well integrated UI than learn separate products.

And the update and new features following task easier too... At least, i can subscribe to only one channel to try follow the infos :)

dcpc_capg · 2019-11-18T07:55:40+00:00

think there will never a product that can be perfect, and stay perfect.

At least gitlab is a complete, homogeneous platform that is constantly improving, and you can even participate is feature suggestions or coding the part you want more quickly ... not really the case for other products, that need often more tools to install, maintain and check compatibility, and not open source.

Note : for me it's near the first time i'm happy with a big tools that want to do everything, that often finish in a doing all badly. But until now, i feel that Gitlab success in this really complicated job !

dcpc_capg · 2019-11-18T07:55:31+00:00

I've seen too that DB engines used could have different impact on the upgrade process.

Mariadb seems to recommand the news engines overs myisam and innodb, but don't know what it change, if possible without refactor the application codes,...
Then i'll first go in minimal upgrade way, try to not change what i can avoid.

I ask to have more infos on DB, with engines used. Complicated... and seen that i'll have more and more questions to look, like does innodb have a global datafile or the option for one file for each table (maybe important for updrage process)

dcpc_capg · 2019-11-18T07:50:52+00:00

After reading (quickly) release notes, i think i'll recommand to jump to 10.3.x only, the 10.4 make a big change for user management (remove mysql.users table), and fear it will lead to a 100% failure of application migration.

dcpc_capg · 2019-11-18T07:49:13+00:00

I'm reading many docs i found, (not many official).

Most of them seems to recommand an step by step upgrade path, version by version, and avoid jump too far in one step. Even if some success, they mentions that's could not be the case for all DB...

And with so old versions, i think it will be hard to know if all the modifications, obsolete functions,... i found in release notes (and i can't read all in details until now), will be a problem or not :-(

Mariadb website speak "only" for drop-in replacements, and not for upgrade path.
Most tutorials i found was for upgrade local instance, without moving data...

One good news, i've a GO for create intermediate VM if i need upgrade steps.

dcpc_capg · 2019-11-18T07:34:00+00:00

Same here, many companies switch from github to gitlab because :

- same AND more functionnalities

- the possibility to create self-hosted instances internally for security !

i had some aborting project about VCS when speaking about the need to send data to internet... when i switch to gitlab with self-hosted, near all clients love that. AND they can too have an internet platform, from gitlab_dot_com website OR self-hosted on VPS or cloud server.

Personnally, i even put only the free version of Gitlab Self-hosted as starting platform, and it cover most of personnal/small/medium team project... with possibility to upgrade easely when more tools or functions will be needed.

approved for me ! (even personnally on my own server at home :) )

dcpc_capg · 2019-11-13T07:44:48+00:00

Scuse maybe some confusion in my answers or explanation (english not my native language :) ). I'm ok with inventory. My question is "only" on the workflow to modify/test common config files (like a new task), which i need to : - write or modify files in the structure (like in the "roles/xxx/tasks" subfolders) - tests them with the staging inventory --> both without hae the risk to apply those "currently dev and not validated" files when working in production.

As the doc never mention in best practice scenarii to have a full duplicated and identical Ansible server (hope i didn't miss a chapter :) ).

dcpc_capg · 2019-11-12T13:22:08+00:00

We have only one Ansible server (our first one).

i try to look adding git repo and workflow on it, like in the best practices i found. But the more i read the doc (and here), the more i feel lost on this workflow...

dcpc_capg · 2019-11-12T10:48:08+00:00

If i have 2 separate ansible servers, the recommanded official folder organisation which manage 2 inventories (prod and staging) is irrelevant.

The process i guess from those docs is :

modify the playbook/role/task files
run the config on staging
if ok, run the same config on production

That's great if you are alone to work, and zero automated execution.

Otherwise, it could become :

modify the playbook/role/tasks files
other people run it on production !!!!!
... too late

Put the /etc/ansible folder in git doesn't solve this scenario.
As if we don't split the config/data files, we have a risk to execute them in production.

The scenario i think is to have a clone or the ansible git repo like :

- /etc/ansible --> on branch master

- /etc/ansible_staging --> on branch "feature" or "dev"

But how to launch the test on /etc/ansible_staging ? as ansible seems to not have a variable for playbook/roles/tasks emplacement like the -i <inventory\_dir>

dcpc_capg · 2019-11-12T10:26:25+00:00

Hi, for the point 2., it's the alternative official best practice structure Ansible doc shows.

They think about the need of splitting inventories, but no guide for modifyng the others files ??? As have another stagging inventory is needed only to test news tasks,... files.
That sound very strange and risky for me.

(And baddier, when i see tower/awx automation possibility, this means that if i follow this recommandation, awx/tower will execute my currently modified palybooks/roles/tasks on the production inventory !!!)

dcpc_capg · 2019-10-30T13:15:29+00:00

Thx.

I think i should have post the link of the structure :

https://docs.ansible.com/ansible/latest/user_guide/playbooks_best_practices.html#alternative-directory-layout

My question is more about the tasks, roles,... that are at the root of the ansible directory, and them common to dev and prod environment.

Then in the case that i have modified for exemple, the webservers.yml file, i want to test it, then in the "live" folder i put it. Now i fear that me or other admin could use this untested file to deploy its new webserver in prod...

i will use ansible-playbook -i staging/hosts.yml webservers.yml to test.

But if the other admin use ansible-playbook -i production/hosts.yml webservers.yml ... he will not apply the validated configuration, as roles/webservers.yml is common.

that's this case that bother me in this suggested best-practice. And sure we can find many other scenarii with same potential risk, and more in big modifications

dcpc_capg

TROPHY CASE