Omg cant wait :)
Me want.
Love the work you guys are doing, would donate once my paycheck comes but it seams to be disabled :P
OBS redux
- Thread starter Lain
- Start date
Omg cant wait :)
Me want.
Love the work you guys are doing, would donate once my paycheck comes but it seams to be disabled :P
Hmm, just tried it and it works now. Nevermind, false alarm.
TheRevTastic
Member
I'm hoping the windows version will be ready by the time Destiny comes out so I can stream it easily :c
So about legato game capture compatibility for the mac release. I talked to Dakotah Bronk about it and he told me this:
Dakotah Bronk replied:
Mathias,
Thank you for your suggestion, I will forward this through the appropriate channels, so it could possibly implemented in future releases!
Dakotah Bronk replied:
Mathias,
Thank you for your suggestion, I will forward this through the appropriate channels, so it could possibly implemented in future releases!
JPL
Member
Is there a good PPA for FFmpeg to use with Linux builds yet? I ended up compiling FFmpeg from source myself, and it took some rather fiddly compiler options to make it produce something OBS-redux could build from. It's definitely a barrier for any Linux users looking to check out this awesome project.
Also unfortunately it looks like ffmpeg won't replace libav in Debian-based distros any time soon, so the problem isn't going to sort itself out upstream.
Also unfortunately it looks like ffmpeg won't replace libav in Debian-based distros any time soon, so the problem isn't going to sort itself out upstream.
Have you seen this yet? https://obsproject.com/forum/threads/ubuntu-14-04-ppa-installation-instructions.16495/
JPL
Member
I had not, thanks so much!
Julia Mortellaro
New Member
so anything new happening what about the text plugin?
paibox wrote a text plugin -- we're going to put it in next version. I'm going to try to get a new version out soon but I ended up making some big naming convention changes to the core for more consistent API, so plugin developers have an easier time working with it.
Getting an update out the door is top priority right now, even if it's only a small update, ETA is "every time someone asks me for an ETA I end up off the mark by a alot". Basically: I get text stuff complete. I've also got a regular OBS1 update I have to do as well which has been eating in to my time a slight bit at the moment.
It would be great if there would be a project tracker, and if it's just a list / Google Doc/Spreasdsheet you update, that shows what you are working on right now, what you need help with and what is prioritized next. It would help the community to understand what is going on and what to expect as well as plugin developers and potential contributors.
Also just a few tiny things that I noticed in the style guide - feel free to ignore them ;)
1. "I also use actual tabs now, instead of spaces."
This is bad. Why? Because my vim is set up to 1 tab = 4 spaces. So all my lines will be longer than your lines and the 80 character limit is off. Use spaces. Either enforce 8 colums or 4. Don't use tabs, as it implies that every developer uses the same setup / remembers to change it every time.
2. "Also, it makes for much cleaner viewing in certain editors that wrap (like vim)."
:set nowrap
#justSayin
Keep up the good work, awesome progress! I'll try to get it running on Windows soon and see if I can provide some feedback.
Also just a few tiny things that I noticed in the style guide - feel free to ignore them ;)
1. "I also use actual tabs now, instead of spaces."
This is bad. Why? Because my vim is set up to 1 tab = 4 spaces. So all my lines will be longer than your lines and the 80 character limit is off. Use spaces. Either enforce 8 colums or 4. Don't use tabs, as it implies that every developer uses the same setup / remembers to change it every time.
2. "Also, it makes for much cleaner viewing in certain editors that wrap (like vim)."
:set nowrap
#justSayin
Keep up the good work, awesome progress! I'll try to get it running on Windows soon and see if I can provide some feedback.
paibox
heros in an halfshel
Tabs are currently expected to be 8 spaces, but use an actual tab character code, so it is enforced. I'm no fan of the 80 character max line width either, or the 8 wide tabs, but if you contribute to a project, you should stick to the project's coding guidelines. It's not necessarily "bad" just because you don't like it. (Please keep in mind that I don't like it either, I personally feel that it's better to use horizontal space rather than vertical, considering that almost all monitors these days are widescreen.)
Hey,
So first, I am not saying anything is wrong or anyone should change because of me, I am just pointing out something I personally would change. I absolutely agree that when you contribute to another project, you adhere to their standards, period.
The issue is that the tab width is specified nowhere. Every editor has to set it separately. Even there are modelines, what if I use emacs or Sublime, who have no idea what I am talking about? ( See StackOverflow ) So when I open the code it looks different than it was intended to look. ( 2 or 4 spaces per tab on my settings )
Anyhow, these are super minor things, nothing to worry about, I just thought I point it out. Keep going, nothing to see here :) :)
I view KNR formatting as valuable for a number of reasons. It's not about appearance (though it's grown on me); it's about usability and a self-imposed restriction on indenting and function sizes.
The argument that something is 'bad' just because it's not the popular way of doing things I don't feel is something I can agree with. I'm not about to say 4-spaced indents are bad, I've used it and I like it somewhat as well. In fact it's preferable when used with allman style.
With 8-column indents however, it's far more superfluous to have 8 spaces in place of a single tab character. Tabs in the first place were originally meant to be 8 columns. In a 4-column indent scenario spaces work out better, but with 8 column indents it's just too many spaces - so in this situation I vastly prefer the traditional tab character.
In this case I purposely chose KNR simply for the sake of better code rather than programmer convenience or preference. Tabs and indent width should also specified in both the contributing guidelines and the readme.
The argument that something is 'bad' just because it's not the popular way of doing things I don't feel is something I can agree with. I'm not about to say 4-spaced indents are bad, I've used it and I like it somewhat as well. In fact it's preferable when used with allman style.
With 8-column indents however, it's far more superfluous to have 8 spaces in place of a single tab character. Tabs in the first place were originally meant to be 8 columns. In a 4-column indent scenario spaces work out better, but with 8 column indents it's just too many spaces - so in this situation I vastly prefer the traditional tab character.
In this case I purposely chose KNR simply for the sake of better code rather than programmer convenience or preference. Tabs and indent width should also specified in both the contributing guidelines and the readme.
carmont492
New Member
I just want to say, thank you for all the hard work the debs are putting into this project.
I think I speak for all mac streamers when I say, it is greatly appreciated!
I move house next week so won't be using it for a while, so I look forward to any updates for me to play around with!
I think I speak for all mac streamers when I say, it is greatly appreciated!
I move house next week so won't be using it for a while, so I look forward to any updates for me to play around with!