Critical Edge: XSplit Panel Writer 2 Released!

[PaPaGriM]

I'm setup to "Smaller - 100% (default)" and the DPI is set to 96 pixels per inch.

 

[Jaxel]

Give me a capture of your xsplit-input folder with properties. The size of the output images are based on the sizes of your source images. It sounds as if your computer is reporting wrong sizes for your source images.

using (FileStream output = new FileStream(outputFile, FileMode.Create))
{
    BitmapImage bitmap = new BitmapImage(new Uri(sourceFile, UriKind.Relative));
    DrawingVisual visual = new DrawingVisual();
 
    using (DrawingContext image = visual.RenderOpen())
    {
        image.DrawImage(bitmap, new Rect(0, 0, bitmap.PixelWidth, bitmap.PixelHeight));
 
        buildText(image, "event_event1", this.event_event1.Text);
        buildText(image, "event_event2", this.event_event2.Text);
        buildText(image, "event_event3", this.event_event3.Text);
    }
 
    RenderTargetBitmap target = new RenderTargetBitmap(bitmap.PixelWidth, bitmap.PixelHeight, bitmap.DpiX, bitmap.DpiY, PixelFormats.Default);
    target.Render(visual);
 
    BitmapEncoder encoder = new PngBitmapEncoder();
    encoder.Frames.Add(BitmapFrame.Create(target));
    encoder.Save(output);
}

Also, if you can contact me on AIM... we can try to debug this together.

 

[PaPaGriM]

Thanks for the prompt response. Not sure what time zone you're in, but I'll get the screen shots as soon as I get home this evening. I'll DM the AIM details then.

 

[PaPaGriM]

Jaxel,

There is no "xsplit-input" folder, so I'm assuming you meant "xsplit-images" folder. Attached is a screen cap of the "xsplit-images" folder with the properties as you requested. This was captured from a fresh install of v2 on a totally different computer running Win7.

I tried to save and it returned the same output as before.

"xsplit-images" folder (default/stock png)

 

[Jaxel]

I figured it out... it was the images I included; nothing was wrong with the program itself. For some reason, Photoshop stored the image sizes incorrectly... I have fixed the images and re-uploaded the package. But either way, if you just make your own new images, the problem shouldn't persist.