Koosemose

Members
  • Content count

    45
  • Joined

  • Last visited

Community Reputation

6 Neutral

About Koosemose

  • Rank
    Advanced Member

Recent Profile Visitors

563 profile views
  1. Options for 5.1/7.1 audio , WAV file output

    As to writing audio in a separate file, Playclaw already can do that, Under encoder, there is an option called "Write audio in separate files".
  2. Recording Indicator

    I will soon be uploading an alternative version that combines this with a mute status (and hotkey), so it uses the color to indicate recording status (the same as this), but instead of record/pause/stop icons, it will instead show a microphone, or crossed out microphone depending on if you are muted or not. As a plus, you can also set a hotkey to mute your sound input (useful for microphones which don't have a hardware mute, or for users who don't want to use their hardware mute for whatever reason)
  3. File naming method

    What would the feasibility (and desirability perhaps) be on an advanced mode for file naming/save location? Basically being able to set how the files are named with a series of variables, so if I wanted to emulate the current naming scheme it would be something like "%procname% %date% %time%", but I could, for example, instead do "%day%/%procname%-%hour-%second%" putting it in a folder by month only, and leaving out the rest of the date from the folder or the filename, and then leaving the milliseconds off. I don't know how many other variables would be reasonable to include other than what's already there, and breaking the date and time up into their component parts, I don't think anything having to do with recording time would be feasible, unless maybe it could be renamed after completing, but I'm not sure that's actually that useful or worth any effort involved, maybe the month name (or at least shorthand such as Mar for March). Maybe a way to access a variable from a plugin or at least a few variables that can be written to by plugins (though now that I think of it that would again have to involve renaming afterwards, so perhaps not that useful). Maybe a sequence number would be reasonable and useful as well (so rather than having date and time it would just have a number on the end, that's one higher than the highest number file where the rest of the name matches (so if I were recording Minecraft, and if there were a Minecraft 001 through Minecraft 005, it would next do Minecraft 006, and presumably skip anything with a different rest of the name). I'm perhaps trying to get too complicated, but I know I'm always wanting my recordings to save ever so slightly differently (in my case leaving off the year, and formatting the date in the american fashion which I can parse much quicker since it's familiar to me, and leaving off the milliseconds since they're not really useful to me, and removing excess data makes it easier to mentally sort out which files are what recordings.)
  4. Main beta

    The Web Browser overlay looks very nice, much better than the hackjob I put together a while back, I see you have a bootstrap executable, imagine that's a key part of what I was missing to be able to use cef. I wonder if it might not be reasonable to hide the scrollbars by default, since they're rarely going to be what someone wants anyways. While it can be hidden by CSS, the extra step (or lack of being able to figure out how to do it) might negatively impact people's opinions on the plugin (and PlayClaw in general if the web browser overlay is important to them), even just including the CSS as a default would work fine, since that's probably the way most people would prefer it.
  5. After figuring out how to convert buffers to gdiplus bitmaps, I returned to an idea mentioned in a feature request (screenshots that show overlays that aren't rendered to recorded video), of course the particular use case was for showing timestamps on screenshots, so of course, since rendering overlays that aren't on the recorded video is, if not impossible, overwhelmingly difficult, I was attempting to use PC_CaptureFrame. These are several things that anyone attempting to make use of may wish to be aware of and/or information that Edward may find useful. It evidently takes a little bit of time for PC_StartPureCapture to start working, if I used it in the same function as PC_CaptureFrame, it wouldn't work, PC_CaptureFrame would capture a black screen, same as if PC_StartPureCapture wasn't used at all. When I was triggering it from PluginUpdateOverlay, it required using counters or flags of some sort so that PC_CaptureFrame wouldn't be used until the frame after PC_StartPureCapture. Similarly, to make use of it from a hotkey, PC_StartPureCapture had to be executed on hotkey down, with PC_CaptureFrame executing on hotkey up. This works fairly reliably. Though it should be noted that it seems to work fine while you are recording, regardless of PC_StartPureCapture, however, it may cause recording to stop from time to time, but it is also possible this is caused by a mostly unrelated bug in my testing plugin. The next notable thing has to do with the interactions between PC_CaptureFrame and gdiplus bitmaps. The screen you're capturing from needs to have a width that is a multiple of 4, as the Bitmap constructor from buffers requires a stride that is a multiple of 4 (stride is width * bytes per pixel) and since PC_CaptureFrame uses a bitdepth of RGB24 (3 bytes per pixel) it doesn't help with the stride being a multiple of 4 ( if on the other hand it used a bitdepth of 32, it would have 4 bytes per pixel, so stride would always be a multiple of 4 as the width would be multiplied by 4). So this pretty much requires whatever you're capturing from be set to fullscreen (since most (all?) definition ratios will have width a multiple of 4) or be very precisely set to a multiple of 4 width. It doesn't matter what your custom frame is set as, I assume the size of the custom frame is used in the encoder, PC_CaptureFrame will be whatever the natural size of your source is. Finally there seems to be some degree of unreliability in reallocating the buffer, if the buffers original size is smaller than the source, it will crash, seemingly not reallocating it to a proper size. There is of course always the possibility that I have misunderstood the documentation, I still haven't fully wrapped my head around reading C++ style documentation. Scratch this last point, I just realized it is supposed to return the reallocated buffer, rather than alter the passed in pointer... This seems odd, but again, I'm not familiar enough with C++ standard practices to know if this is normal or not, there's lot's in C++ that seem nonsensical coming from perl and java.
  6. Marquee Text

    View File Marquee Text This overlay simply displays text from a file, all on a single line, and if the text is too long to fit in the overlay's boundaries, the text will slowly scroll. If the file changes the text will be reloaded and the new text will replace the original. It is primarily meant for use with other programs which save your currently playing music track to a text file, such as Snip (https://github.com/dlrudie/Snip/releases/latest ), but feel free to use it for anything you wish. As there are many similarities between this and the new features of the Text Overlay, I will mention the differences which are why I still released it despite the heavy overlap. First, this is only a marquee (or ticker) and only loads from file. It will only scroll when the text loaded from the file won't fit in the available space. The last, and I feel most important, is a matter of aesthetics, rather than scrolling until the text scrolls off the side then starting the text in from the right, the text will start scrolling back in from the right before the end is fully scrolled off the left side (as can be seen in the second screenshot). Ability to change the scrolling speed should be coming in the next version (which will likely become higher on my priority list if interest is shown in this variation). Suggestions welcome. How to install Just download and copy zip file in your PlayClaw/plugins folder, unzip it, you will see Marquee Text folder with files, then start PlayClaw, new plugin should be visible in plugins list. Github Link: https://github.com/koosemose/Marquee-Text Submitter Koosemose Submitted 02/03/2016 Category Plugins
  7. Marquee Text

    Version 1.0.0

    11 downloads

    This overlay simply displays text from a file, all on a single line, and if the text is too long to fit in the overlay's boundaries, the text will slowly scroll. If the file changes the text will be reloaded and the new text will replace the original. It is primarily meant for use with other programs which save your currently playing music track to a text file, such as Snip (https://github.com/dlrudie/Snip/releases/latest ), but feel free to use it for anything you wish. As there are many similarities between this and the new features of the Text Overlay, I will mention the differences which are why I still released it despite the heavy overlap. First, this is only a marquee (or ticker) and only loads from file. It will only scroll when the text loaded from the file won't fit in the available space. The last, and I feel most important, is a matter of aesthetics, rather than scrolling until the text scrolls off the side then starting the text in from the right, the text will start scrolling back in from the right before the end is fully scrolled off the left side (as can be seen in the second screenshot). Ability to change the scrolling speed should be coming in the next version (which will likely become higher on my priority list if interest is shown in this variation). Suggestions welcome. How to install Just download and copy zip file in your PlayClaw/plugins folder, unzip it, you will see Marquee Text folder with files, then start PlayClaw, new plugin should be visible in plugins list. Github Link: https://github.com/koosemose/Marquee-Text
  8. Build 3500+

    Ahh very nice, very nice. Almost completely eliminates the need for my Text Marquee, plugin... which I've just realized I completely forgot to ever actually put on the forums, other than a random link buried in a thread. I may still see about putting it up, for the one or two differences it has, when in ticker mode it doesn't put as large a space between contents of the text file, and doesn't ticker if the contents fit in the space available.
  9. How to create hotkeys

    So it turns out my issues was I hadn't updated my Playclaw libraries and headers and all that, and apparently somehow not doing that kept the plugin from loading when I used CreateHotkey. So a bit more cleanup and I should have another functional plugin, especially for people who have mics that don't have a mute key. While there are outside tools that can do it, it seems much cleaner to be able to do it from inside Playclaw (or a plugin anyways), especially for those like myself who constantly forget rather or not they're still muted.
  10. Twitchalerts & Mic-Mute

    The only problem with my version is that it uses Awesomium (which is the only one I can figure out how to implement), which is a somewhat subpar option. It requires a hefty pile of DLLs (around 6) to be in the main program folder (if there's a way to get it to use them from the plugin folder, that would make things way better), which makes it a bit of an annoyance from a user installation perspective. And it is based on an older version of chromium, so there may be issues with rendering some webpages. I look forward to seeing a better implemented browser overlay from someone who actually knows C++ (as opposed to me who is a Java and perl programmer who knows enough C++ to gather and paste together snippets and tweak until something functional comes out the other end)
  11. Twitchalerts & Mic-Mute

    So, I've been off and on exploring html rendering for a while now, and have finally managed to get an html renderer (awesomium which is based on an older version of chromium) up and running through a Playclaw plugin, it is still in the proof of concept stage, meaning it has no configuration (I have to recompile just to change what page it loads), is ugly, and the code is unreasonably messy (it still contains the remains of most of my attempts at other renderers). But it works, and well enough that I can watch youtube videos with a reasonable frame rate (I haven't attempted actually playing any sort of demanding game, as I'm assuming most people won't be both watching a video and playing a game). So it should be smooth enough for Twitchalerts along with anything else of the sort. So at this stage, it means that it can be done, and furthermore *I* can do it. However, at a minimum I would guesstimate at least a month before I have anything usable by the general public, as I have my own Youtube channel to see after, several other programming projects (this one is not a priority since I don't stream myself and am mostly doing it as an exercise and because I can), along with the usual assortment of real life concerns. But I do want to get this to a functional point and will return to it. I just wanted to let those who are interested in such a thing (particularly for the purpose of Twitchalerts) that it is on the horizon.
  12. Show overlays in screenshots?

    I was going to suggest just such a thing if what OP wants wasn't possible. Perhaps TImestamper or something along those lines for a name? Also, is it possible for a plugin to actually access the current captured frame? So that it could save the screenshot itself rather than relying on Playclaw core to save it, and either just have the filename be the timestamp (probably less desirable) or possibly draw onto its copy of the captured frame before saving?
  13. Build 3500+

    I've been using x264 via vfw, will this change cause any issues with that? Also what, if any, advantages would this new method provide over doing it through vfw? Would it just be easier to install and/or just have simpler configuration (which I was only able to achieve via vfw thanks to another Youtuber kindly making a video with the results of testing on the best x264 settings, in his opinion, for Youtube)
  14. Issues with 4K/2160p recordings

    Whitelisting was disabled by default and the option to turn it on hidden in a config file (due to issue with a large number of users turning on whitelisting either accidentally or forgetting or not understanding and then having to go to support with issues recording since they were whitelisted and didn't know it). If you go to playclaw5_config.txt in C:\ProgramData\PlayClaw5plus, there should be a line (likely near the bottom) that says: misc.enable_whitelist = 0 change it to: misc.enable_whitelist = 1 That should take care of it for you.
  15. That's strange, it seems it does something unexpected. Best I can advice I can offer you is to either set the hotkey for enable/disable overlay and just disable when running obs, or just close playclaw. Anything beyond that Edward will have to look at.