Color display not working

just try to run ffprobe from the command prompt.

Also, I have added some code to cpqoi that makes it fail if you give it a movie, and it fails to extract a frame rate from it.

Command 'ffprobe' not found, but can be installed with: 
sudo apt install ffmpeg

I thought I had ffmpeg because its needed for the pqoi process. Any way, I installed it with sudo apt install ffmpeg

Here is a newly created pqf file with a new proffieos master download and ffmpeg (re?)installed.

dpqoi says this has a frame rate of 4 and loops, which seems correct.
(Not sure if you want it looping or not, but that is the default when you just give it a movie.)

I think looping works for my usage. But perhaps it would be better to not loop in the pqf, then specify loop in the scr file? Might be more versatile that way. How would you do that?

And if this is still tbd as you develop it, let me know and I will stop asking so many questions…

Specifying the looping in the scr file doesn’t really make sense for the format. However, you can stop a loop with the “time” argument.

Regardless of what the default is, you can always specify if you want a loop or not by using a pqoiml file. If you create a file like this:

file biocircuitry.mp4

call it biocircuitry.pqoiml and run cpqoi on it, you get a non-looping file.

If you want a looping file, you do this:

label start
file biocircuitry.mp4
goto start

(Which is the default.)

I could also make some sort of command-line flag for this if non-looping file is a common thing that people want.

1 Like

Ok, I have fixed a couple of bugs in the color display code.
Please try again, and let me know if something doesn’t work as expected.

PS:
I noticed that many of your SCR files are still lacking newlines after the last line.
Basically, the file reads file=biocircuitry.pqf\nrestart\nlayer, but it probably should be file=biocircuitry.pqf\nrestart\nlayer\n.

Basically, it won’t really parse the last line unless it ends in a newline. It doesn’t really matter in this case since having “layer” as the last line doesn’t do anything.

Thanks! I will try to test tonight.

Ah, you mentioned this earlier, but I didn’t understand. So, I added “layer” to the files.

So, my file(s) now are more or less this:

file=biocircuitry.pqf
restart
layer

But as you stated should be more like this:

file=biocircuitry.pqf
restart
~~ this is a blank line ~~

The tilde line text would not be there, but the code block wouldn’t show a blank line. Is that right?

This is basically right.
That “empty line at the end” is traditionally not counted as a line.

The basic idea is that a line is something followed by a newline.
So newlines are a part of the line rather than something that separates lines from each other.

Getting closer!

I remade all the pqf files, and uploaded the same config with the latest master os.

On boot, it shows the boot logo. Then goes to the idle.scr. idle.scr never turns off, so it must be looping. When I press the pow button, it does not show on.scr. the idle screen stays on. When I press pow again to turn off the saber, the screen goes black. Nothing displays with any presses.

When I cycle fonts back to this one, the screen flashes briefly showing something that may be font.scr. But its too quick to tell.

After that nothing displays again.

I ran “show” on all the scr files, and they all display what they should.

Not necessarily true, because as soon as nothing is playing there is now a call to “playdefault”, which will restart “idle”, “on” or “lockup” as needed.

Send me your new files and I’ll have another go at debugging.

pm sent, thanks!

Three more bugs bite the dust.
Hopefully soon we’ll get into “should it work this way” rather than “why doesn’t it work” territory… :slight_smile:

Well, it seems be working as expected now! At least for the 4 files I have.

When I turn it on, it shows boot.scr, then idles.scr soon after. When I press pow, it shows on.scr.

When I turn it off, it goes back to idle.scr. When I cycle fonts, it shows font.scr.

So far so good. Thanks! I guess I should test more effects…

1 Like

Color display documentation is coming along:

I still need to fix the configuration generator to handle color displays though.

1 Like