freevo-devel — Developer's mailing list

Re: [Freevo-devel] The future of Freevo(.org)

[Dirk M. <di...@fr...>]

Hi everyone left,

On 20.01.14 19:38, Dirk Meyer wrote:
> Since we also lack someone maintaining the server we host and I do not
> want to pay for something we don't need, I will shut it down at the end
> of February. This means the SVN and the Wiki will be gone. If someone
> wants a backup of the Wiki please tell me. The code is already on github
> and will remain there. The mailing list on SF will continue and so will
> the mail server hosting freevo.org and all mail addresses will continue
> to be valid.
> 
> Maybe after some time someone resurrects Freevo. I would love to pass
> the maintainership over to someone just as I took it over from Krister
> years ago. Maybe someone takes the kaa-stuff and writes something new
> and better. I'm happy to assist and I think the same is true for Jason.
> Maybe I will release something someday based on the current code.

This post was six years ago. Now Python 2 is end-of-live and Freevo
won't run on Python 3.x.. I myself switched to kodi years ago.

Whats left are some parts of the kaa library used by Freevo. I will
start porting useful stuff from kaa to Python 3 ... or copy code from
Tack who already did it. It may be useful for others and I will need it
myself to port some private code to Python 3. kaa.metadata is still very
useful for me.

So join me at https://github.com/freevo and keep some good parts active
and create new libraries. Maybe I will create a new project for kaa.

But Freevo itself is dead. Therefore, I will not renew the freevo.org
doamin and cleanup everything on sf.net. The "new" homepage will be
freevo.sf.net again. If you need to contact me, please use the github
page since this mail address will be invalid soon.

Bye and again: it was a good time!

Dischi

Re: [Freevo-devel] Freevo with parallel recording and DVB EPG

[Dirk M. <di...@fr...>]

Hi,

On 10/10/2015 09:27 PM, Hartmut Schäfer wrote:
> before I begin, let me thank Dischi and all the people who else worked
> on this project for their great work. I am using Freevo since 2004
> (starting with version 1.5.0, later switching to 1.5.3 and not upgrading
> since then), and I am a big fan of it (and of Python). For me, there's
> no alternative in simplicity, functionality and pragmatism.

Thanks

> This work turned into a far bigger project than I initially intended,
> keeping me busy (with some interruptions) for almost two years now. I
> was lucky that there were no commits during this time, so I wouldn't
> have to address a moving target (although it's a pity that the community
> seems to have moved away from Freevo; for me it's NOT dead as the patch
> shows: it's ready now for another 10 years).
> 
> The result of my work are the attached huge patch for Freevo and the one
> for kaa (I'm not entirely sure if I crafted the kaa XML correctly
> because I wrote my config_dvbstreamer.py by hand). I initially intended
> to dissect the result of my work into separate patches for one issue
> each before submitting, but as work progressed (you will note that I
> have completely rewritten core parts of the recordserver), this became
> increasingly difficult and finally impossible. I'm sorry for that, but
> I'm sure that I have done a piece of solid work that can be taken as a
> whole and will turn Freevo into a new release everyone will embrace. The
> long development phase during which I increasingly used this
> installation for productive recording caused a fair amount of testing to
> be accomplished. I thus consider the result to be pretty stable now.
> Although, nobody knows really...

Did someone else test this and is this a good patch? Does old stuf still
work and does it break someting he does not use? I'm using the Freevo 2
trunk so I cannot test this. If the patches are good, someone could put
them into a pull request and I would merge them to github.

> I would be glad if my patches were integrated into the freevo1 and kaa
> projects. Thank you again for all your great work, and I hope you will
> enjoy mine too.

Looks like great work, too. If the 1.x users agree and create a pull
request, I will merge it.


Regards,

Dischi

-- 
Woodward's Law:
	A theory is better than its explanation.

[Freevo-devel] Freevo with parallel recording and DVB EPG

[Hartmut S. <har...@su...>]

Hi all,

before I begin, let me thank Dischi and all the people who else worked 
on this project for their great work. I am using Freevo since 2004 
(starting with version 1.5.0, later switching to 1.5.3 and not upgrading 
since then), and I am a big fan of it (and of Python). For me, there's 
no alternative in simplicity, functionality and pragmatism.

In the last three years more and more analog channels were removed from 
my cable in favor of digital TV, but when in late 2013 the analog EPG on 
my cable finally vanished, it was time to make a big switch. I had been 
short on disk space for years, and so it was time to get a bigger hard 
disk and install the newest Freevo on it. While doing this, I also 
intended to realize some wishes that had emerged when using Freevo.

This work turned into a far bigger project than I initially intended, 
keeping me busy (with some interruptions) for almost two years now. I 
was lucky that there were no commits during this time, so I wouldn't 
have to address a moving target (although it's a pity that the community 
seems to have moved away from Freevo; for me it's NOT dead as the patch 
shows: it's ready now for another 10 years).

The result of my work are the attached huge patch for Freevo and the one 
for kaa (I'm not entirely sure if I crafted the kaa XML correctly 
because I wrote my config_dvbstreamer.py by hand). I initially intended 
to dissect the result of my work into separate patches for one issue 
each before submitting, but as work progressed (you will note that I 
have completely rewritten core parts of the recordserver), this became 
increasingly difficult and finally impossible. I'm sorry for that, but 
I'm sure that I have done a piece of solid work that can be taken as a 
whole and will turn Freevo into a new release everyone will embrace. The 
long development phase during which I increasingly used this 
installation for productive recording caused a fair amount of testing to 
be accomplished. I thus consider the result to be pretty stable now. 
Although, nobody knows really...

The following are the most notable changes I made besides, of course, 
making many other small enhancements and fixing bugs:

1) Grabbing EPG from DVB tuner card (dvbstreamer). (An optional text 
dump allows to feed external mechanisms presenting it to other devices.)

2) Parallel use of recording devices of different types (e.g. analog + DVB).

3) Parallel recording on multiple devices of same type.

4) Parallel recording of multiple programs on same DVB device as long as 
they are transmitted on the same transponder channel (including parallel 
recordings of the same channel - needed when recording adjacent shows 
due to them overlapping each other with their record paddings).

5) Different video groups can use the same device, allowing to choose 
between different sets of recording and postprocessing parameters by 
defining multiple video groups ('recorders' in the new terminology) per 
device.

6) Improved manual conflict handling (recursively stacked).

7) Best-effort clean recording in presence of unresolved conflicts.

8) Improved manual scheduling, editing of scheduled recordings 
(accessible also from program guide) and favorites, manual creation of 
favorites, entering of descriptions for existing videos.

9) Favorites with keyword search alternatively to title search.

10) Allowing multiple favorites with same title; a program will always 
be scheduled by the strongest applicable favorite.

11) Favorite reordering by button press (VOL+/VOL-).

12) Automatic daily or weekly repeat of recordings.

13) Direct recording into subfolders of TV_RECORD_DIR.

14) Text input using keyboard, improved SMS-style input, input of 
international charachters.

15) Horizontal scrolling in program guide (and better vertical scrolling).

16) Improved autoshutdown plugin (autologin + quick logoff, anticipatory 
fsck feature).

17) Idlebar Alert plugin as notification channel for recording plugins. 
(The icon is a bit too prominent, maybe someone can create a more decent 
one.)

18) Command plugin again working, can be invoked now also by hotkey.

19) Avidemux plugin for direct video editing (implemented as alternative 
video player).

20) Mplayer ZOOM button, single frame step and improved manual seek.

21) Autoresume feature for playing directories.

22) New password protection mechanism, old one extended for multiple 
passwords per protected directory.

I strived to my best to ensure that existing schedules and favorites 
(missing the new attributes I introduced) will not break with my 
version, but I cannot guarantee that.

I also did my best to not break TV watching (livepause, mplayer), but I 
don't use that (I watch only recordings), so I cannot guarantee. I also 
did not test the new ivtv and vbi2srt recording (I don't have these cards).

I extended the default TV_RECORD_FILE_MASK by adding the channel id, so 
parallel recordings from different channels won't overwrite each other 
even in the case of identical titles (like 'Manual Record') and start times.

I added some comments about things I didn't understand, maybe someone 
else does and can cleanup any issues possibly present. The upsoon plugin 
may have an issue now, I don't use it and did not test.

I am using the Panorama skin. Maybe other skins could also benefit from 
similar modifications like those I did on the Panorama skin.

There are some new configuration settings, so I defined a new config 
version 5.31. In addition to that, the alert, autoshutdown and command 
plugins define the following new configuration settings:

ALERTVIEW_EVENT
AUTOSHUTDOWN_FSCK_TEST
AUTOSHUTDOWN_FSCK_LILO_CMD
AUTOSHUTDOWN_FSCK_GRUB_CMD
COMMANDS_EVENT
COMMANDS_SORT_MENU

The default values for all new configuration options were choosen so 
that existing behaviour remains unchanged (except postprocessing 
serialization, see below).

What is important when switching to the new code is to review the 
TV_CHANNELS configuration. There are a couple of possibilities for 
configuring channels to allow for backward compatibility, but you will 
probably want to use the new format if you have more than one TV card. 
Please read the explanations in local_conf.py.example. Since the 
time-dependent channels code was useless for recording (it did not work, 
see my comments), I removed this feature from the new config syntax to 
not carry around unnecessary baggage in TV_CHANNELS when the new 
features are used. I kept, however, compatibility with existing 
configurations, so you should be able to continue to use it for watching 
if you want.

Additional notes:

- When using the autoshutdown plugin, setting AUTOSHUTDOWN_TIMER_TIMEOUT 
to a negative value activates a special GUI login feature: The first 
menu navigation will implicitly deactivate the autoshutdown timer, thus 
effectively logging the user in. (So, Freevo wouldn't suddenly shutdown 
simply because you leave it alone for a while.) At the same time, the 
default action of the Shutdown menu will be changed to logging the user 
back out with a 10 seconds grace period to cancel logout, causing a 
basically immediate shutdown, provided there is nothing important 
running and no recording due shortly. (Due to the three tests performed 
to detect important processes, the grace period will actually extend up 
to a minute or so.)

- To prevent missing the start of a recording after wakeup due to a 
filesystem check done on boot, the autoshutdown plugin executes the 
command specified in AUTOSHUTDOWN_FSCK_TEST to determine if a filesystem 
check is due. If so, instead of a normal shutdown (or reboot, if nvram 
demands it), it will perform a reboot using the AUTOSHUTDOWN_FSCK_*_CMD 
to reboot into a special boot configuration you provide that has the 
parameter forcefsck added to the kernel command line and boots into 
runlevel 0 (shutdown) like so:

# normal boot configuration
label Freevo
linux /boot/vmlinuz-3.2.0-4-686-pae
append initrd=/boot/initrd.img-3.2.0-4-686-pae root=/dev/sda1 ro quiet 3

# boot into file system check followed by shutdown
label FsCheck
linux /boot/vmlinuz-3.2.0-4-686-pae
append initrd=/boot/initrd.img-3.2.0-4-686-pae root=/dev/sda1 ro quiet 
forcefsck 0

- With Freevo 1.5 I had problems with excess events when repeatedly 
pressing navigation buttons, and with the new Freevo version 
autorepeating keys (FFWD/REW) ceased to work at all (due to the repeats 
being suppressed by Freevo). Upon investigation the implementation 
appeared broken to me, so I fixed it (I think). More importantly, since 
inside Freevo the information necessary to distinguish key repeats from 
repeated key presses is not available, it's the wrong place to do this. 
The information is, however, available to LIRC, so by using the correct 
'repeat' and 'delay' settings you can accomplish the task in the correct 
place:

begin
prog = freevo
button = KEY_DOWN
config = DOWN
repeat = 1
delay = 4
end

The code built into Freevo can then be deactivated by setting in 
local_conf.py:

LIRC_KEY_REPEAT = (0.0, 0.0)

- When entering text using the great TextEntryScreen (I planted it in 
more places now), a keyboard can now be used for text input (its 
presence will be detected by the first letter entered, turning off the 
SMS-style interpretation of number key presses). SMS style input now 
provides better user feedback (cursor movement on commit as seen on cell 
phones) and national characters. The DELETE and REPEAT buttons allow 
deleting characters and cycling through the different character panels 
(first to upper case with automatic switchbackon successful commit). 
Note that for manually committing a letter RIGHT or OK has to be used 
now (the asterisk feature has been disabled for regularity, to get the 
asterisk as text).

- The new password protection feature using DIRECTORY_AUTHORIZATION 
supersedes the existing protection mechanism based on .password (the 
latter was improved too). It allows to have all password protection 
information in one central place, and especially not on the media volume 
itself. Even more important is that protected directories will be hidden 
from the user until he enters the correct password, that is he will have 
no idea what can be revealed by entering a password. (The only hint 
Freevo gives is that there _is_ something to be revealed, since 
otherwise it won't prompt for a password.) There is also no other 
feedback for the password entered than revealing the folders protected 
by it (in fact, any password will be silently accepted and will sit 
there revealing whatever is protected by it, so entering a password is 
simply like pinning an authorization token, a kind of an additional 
non-mandatory login that gives access to additional content throughout 
the menu system). Particularly, Freevo will give no hint about if there 
are more valid passwords to enter to reveal different items.

The password prompt is invoked by pressing the DISPLAY button (the 
MENU_CHANGE_STYLE event is reused when DIRECTORY_AUTHORIZATION is set), 
and the password is cleared by another press of the same button (you can 
do this already while inside the protected directory, so it will be 
invisible after leaving).

It is possible to register different passwords for the same content, so 
if several people are using Freevo, they may all have their private as 
well as shared protected content.

Passwords are no more stored in cleartext but as MD5 hashes, giving a 
minimal level of protection (basically, against accidental eavesdropping 
only - note that a brute force attack against a 6-digit PIN code will 
take only seconds to succed on today's computers).

If you continue to use .password, all your passwords stored in these 
files must be converted to MD5 hashes. As a reward, there can now be 
multiple of them in every .password file if desired (one per line).

- The FULLSCREEN_TOGGLE event in video/mplayer will cycle through 
different zoom configurations as does the corresponding button on my 
Sony TV for SCART input. The autocrop feature didn't work for me since 
the first seconds of a video are often special, causing a wrong crop, so 
I wanted to control this manually. Besides cropping vertically, a 4:3 
video on widescreen can also be stretched horizontally (some Youtube 
videos need that).

- When scheduling a recording from the program guide, there is now an 
additional context menu option "New Recording" that will present you 
with a prefilled edit screen. You will need this if you want to choose a 
different (from the default) recording device, record into a subfolder 
or change other information. A special use for this is recording two 
shows adjacent to each other on a device other than DVB: Simply set the 
start and/or end time so that the recording spans both shows. (They will 
then also both be shown in green in the program guide, and the scheduled 
recording can be accessed from both via 'Edit Recording'.)

It is also possible to create a new scheduled recording from an existing 
one by the same context menu item. So, if you know that part 2 of the 
movie you just scheduled will come next week (it's probably not on the 
EPG yet), you may just clone the recording and adapt the start date.

- When manually scheduling a recording, it is generally unnecessary to 
enter a day or month or year if the show is tonight. Freevo will 
conclude from the start and stop time when tomorrow is meant. I 
recommend you also set the new config setting TV_RECORD_MAXDAYS to 1 to 
remove the item for setting the stop day from the menu.

- When editing the title of a recording having a subtitle, the latter 
will be concatenated to the title and cleared upon save. You may want to 
use this to get more informative listings.

- For recording repeating shows there are now two options: The classic 
one of using a favorite that will schedule the recordings based on the 
EPG, and a new one of scheduling a recording with automatic (dumb) 
repeat (which does not need the EPG).

- The manual_record plugin is now obsolete. Its code has been moved to 
programitem.py, to allow existing scheduled recordings to be edited, and 
a 'Manual Record' menu item has been added the context menu of the 
'Scheduled Recordings' TV menu item.

- From the context menu of the View Favorites TV menu item it is now 
possible to manually create a new favorite. This allows to easily put 
Freevo hunting for a missed show or one read about somewhere else that 
is not present in the program guide.

- For this to work better it is now possible to record directly into 
subfolders (of course, there are more uses for this). So you might want 
to request the hunting favorites to record into a subfolder 'Inbox' 
where you regularly can check for their success and remove the 
corresponding favorites after they did their work.

- If the gap between two programs is shorter than TV_RECORD_PADDING_PRE 
+ TV_RECORD_PADDING_POST, it will be proportionally split between the 
two programs. In TV_RECORD_PADDING_CONFLICT a minimum gap greater than 
zero can be specified to cause programs that are closer to one another 
than this have a conflict.

- Conflicts between programs are now distinguished by the side of the 
conflict: The program with the higher priority (lower priority value) 
has a 'suppress' (because it prevents _another_ program from recording), 
the other program has an 'overlap' (a conflict that prevents _it_ from 
recording). A scheduled program without overlaps will always be shown in 
the EPG as green even when it has suppresses (because it will record 
cleanly). (Programs that are currently recording are shown in red, 
however.) A program with conflicts will be shown in orange. But there 
are more subtleties:

All programs enlisted in conflicts are internally stacked according to 
their priorities. The ones at the bottom are green, as already said. The 
ones one level above will never record cleanly, so they are shown in 
dark orange. Programs at the levels above might be suppressed only by 
programs that are already dark orange, but not by green ones. Since 
there is no point in preventing a (lower prioritized) program from 
recording if it could do so cleanly only to record part of an albeit 
higher prioritized program that is broken anyway, upon recording Freevo 
will ignore programs with suppresses that cannot record cleanly. The 
result is that lower prioritized programs may be selected for recording 
while higher prioritized programs are not. To indicate this fact, the 
programs that will record despite their overlaps to higher prioritized 
programs (that will not record) are shown in the Program Guide in light 
orange.

By using this strategy, Freevo maximizes the number of accomplishable 
clean recordings in the presence of unresolved conflicts at recording 
time. A program that cannot record cleanly will start recording (for the 
rest of its duration) only when it does not (that is, no more) suppress 
another program. (Programs that ARE recording will never be stopped by 
Freevo to free the recorder before their regular end, no matter how high 
prioritized another program due for recording is. But this concerns only 
favorite scheduling and automatic repeat since scheduling by the user 
will remove conflicting programs from the schedule if he chooses to 
resolve the conflict this way, thereby also stopping the recording.)

Programs scheduled by the user will always have highest priority (zero) 
as long as they don't have an automatic repeat. Following are the 
programs scheduled by favorites in their priority order. The lowest 
priority have programs with automatic (dumb) repeat, internally stacked 
by 'weekly' (highest) to 'weekdays'/'weekends' to 'daily' (lowest). On 
equal priority the program starting earlier or the longer one wins, 
further maximizing the expected clean recording time.

As it is implemented now, it is impossible to introduce conflicts into 
the schedule by the user scheduling programs. He will be immediately 
presented with a conflict resolution form presenting the programs in 
conflict. From there he can edit or delete them, search for more 
occurrences and so on, possibly stacking more conflict resolution forms 
if more conflicts are introduced. Consequently, the only way to 
introduce conflicts into the schedule are favorites and automatic repeats.

I must admit that I didn't understand the automatic conflict handling 
code I found in the record server. I don't use automatic conflict 
handling myself, especially because I'm unclear about how and if at all 
an automatism can be made intelligent enough to be helpful in situalions 
too complex to be easily resolved manually. (To be honest, it would also 
have to be extended to handle multiple recording devices now.) For this 
reason I require the user to resolve any conflicts introduced by himself 
manually and replanted this code from where it was to where favorites 
are scheduled. I'm not sure, however, how helpful it will be in this 
place. The original author will probably know better. I have left some 
comments in the code up to this topic.

- For saving space and because my ten years old Pentium 4 is too slow to 
decode HDTV in real time I have to transcode DVB recordings. (Even 
without this need, a remultiplexing step is necessary in order to 
correct the timestamps.) As I was unsuccessful to get the encodingserver 
to work for H264, I implemented a poor man's postprocessing feature 
controlled by a new VideoGroup attribute postprocess_cmd to invoke 
avconv/ffmpeg or whatever you want (you can code any shell command 
sequences here). For an example see the documentation in config.py.

- The record postprocessing threads invoking this are now serialized to 
avoid parallel running transcoding jobs to unnecessarily fragment the 
filesystem when this doesn't speed up things (by using multiple CPU 
cores for instance). (Note that there is no correct queueing, only 
serialization, so the postprocessings will not necessarily get executed 
in launch order.) A new config setting 
RECORDSERVER_PARALLEL_POSTPROCESS_TASKS can be used to control the 
number of parallel running postprocessing tasks (default: 1).

I did not entirely understand if VCR_POST_REC is (analogously to 
VCR_PRE_REC) meant for short running commands after a recording has 
finished, only changing settings or the like. If this is the case, it 
should be probably moved before the serializing 'with' block to not 
break this behaviour. If it is indeed meant for transcoding, it should 
be probably moved up in the code close to my new vg.postprocess_cmd 
stuff and before generating the snapshot. However, I didn't understand 
if the thread will at all wait for the command to finish (it should, 
because of the following TV_RECORD_REMOVE_COMMERCIALS, but I can't tell 
because I didn't understand the Popen* stuff). So I can't tell if the 
serialization will indeed work for VCR_POST_REC. I'd recommend to use 
VCR_POST_REC for settings only stuff and move it out of the 'with'.

- As I understand, the lock files the record server maintains when using 
a device are intended for the TV watching plugins (which themselves will 
NOT lock the device). I think, with my new code I maintained 
compatibility. A more elegant way for handling the dual use of capture 
devices could be to have the view plugins ask the record server if 
accessing some service on some device (video group) is possible without 
conflict. The record server would then communicate back the answer of 
the associated recording plugin. (This way a DVB device could be used 
for simultaneously recording and watching programs that are on the same 
transponder channel, which is not possible using lock files.)

- The dvbstreamer version I'm using (2.1.0-2.3 from Debian Wheezy) 
commonly experiences problems when fetching the EPG, so I restart it 
after every EPG fetch. I use an endless restart loop in conjunction with 
a named pipe /var/cache/freevo/dvbstreamer.input to feed dvbstreamer the 
'quit' command (which is often not enough, though). This code is from my 
.rc script:

case "$1" in
start)
if ! netcat -z localhost 54197; then
log_daemon_msg "Starting dvbstreamer 0"
(while true; do $DVBSTREAMER -r -u dvbstreamer -p control; sleep 2; done 
  >/tmp/dvbstreamer0.out 2>&1) </var/cache/freevo/dvbstreamer.input &
log_end_msg $?
fi
if [ -d /dev/dvb/adapter1 ] && ! netcat -z localhost 54198; then
log_daemon_msg "Starting dvbstreamer 1"
$DVBSTREAMER -dr -a 1 -u dvbstreamer -p control -L /tmp/dvbstreamer1.out
log_end_msg $?
fi
log_daemon_msg "Starting EPG Capture"
(sleep 20; $FREEVO tv_grab >/tmp/tv_grab.out 2>&1; if [ $($DVBCTRL -u 
dvbstreamer -p control lssfs | wc -l) -eq 1 ]; then pid="$(ps -C 
dvbstreamer -o 'pid=,cmd=' | grep -v -- -a)"; echo "restarting $pid" 
 >>/tmp/tv_grab.out; echo "quit"; sleep 10; if [ "$pid" = "$(ps -C 
dvbstreamer -o 'pid=,cmd=' | grep -v -- -a)" ]; then echo "KILLING $pid" 
  >>/tmp/tv_grab.out; kill ${pid%% *} >/dev/null 2>&1; sleep 10; fi; if 
[ "$pid" = "$(ps -C dvbstreamer -o 'pid=,cmd=' | grep -v -- -a)" ]; then 
echo "FORCED KILLING $pid" >>/tmp/tv_grab.out; kill -9 ${pid%% *} 
 >/dev/null 2>&1; fi; fi; while true; do sleep 10d; done) 
 >/var/cache/freevo/dvbstreamer.input &
log_end_msg $?
log_daemon_msg "Starting Freevo Record Server"
$FREEVO --daemon recordserver >/tmp/recordserver.out 2>&1
log_end_msg $?
log_daemon_msg "Starting Freevo Frontend"
/usr/bin/X11/startx $FREEVO >/tmp/freevo.out 2>&1 &
log_end_msg $?
;;
stop)
log_daemon_msg "Stopping Freevo Record Server"
$FREEVO --stop recordserver
log_end_msg $?
log_daemon_msg "Stopping Freevo Frontend"
$FREEVO --stop
log_end_msg $?
log_daemon_msg "Performing Freevo Cache Maintenance"
$FREEVO cache >/dev/null 2>&1
log_end_msg $?
;;

I have a similarly defined EPG refresh command for the command plugin:

<?xml version="1.0" ?>
<freevo>
<command title="EPG aktualisieren">
<cmd>/home/hartmut/freevo/freevo tv_grab >>/tmp/tv_grab.out 2>&amp;1; if 
[ $(/usr/bin/dvbctrl -u dvbstreamer -p control lssfs | wc -l) -eq 1 ]; 
then pid="$(ps -C dvbstreamer -o 'pid=,cmd=' | grep -v -- -a)"; echo 
"restarting $pid"; echo "quit" > /var/cache/freevo/dvbstreamer.input; 
sleep 10; if [ "$pid" = "$(ps -C dvbstreamer -o 'pid=,cmd=' | grep -v -- 
-a)" ]; then echo "KILLING $pid"; kill ${pid%% *}; sleep 10; fi; fi; 
while ! /usr/bin/dvbctrl -u dvbstreamer -p control lssfs; do if [ -n 
"$pid" ]; then echo "FORCED KILLING $pid"; kill -9 ${pid%% *}; pid=""; 
fi; sleep 10; done</cmd>
<info>
<description>Programmführer aktualisieren</description>
</info>
</command>
</freevo>

For security reasons, the EPG grabber refuses to touch dvbstreamer when 
a recording is in progress.

- When doing DVB recordings, I experienced sudden changes of service 
names (for instance adding a forgotten 'HD'). Since dvbstreamer selects 
services by name, this is fatal because the service will not be found, 
causing the recording to fail. So I let the dvbstreamer record plugin 
check on every start if the services defined in TV_CHANNELS exist on the 
cable. To salvage as many recordings as possible, I further implemented 
some fuzzy logic I am very proud of, to select for every missing service 
the most similar by name service out of the ones on the cable that are 
not used in TV_CHANNELS. (Basically, I compute a normalized vector from 
every name in the space of counts of all possible pairs of consecutive 
characters, and then select the one with the maximum dot product against 
the vector computed from the missing name.) The result of this 
substitution is then used for recording and is also communicated to the 
user via the idlebar alert plugin (so he can review his configuration 
and even do a channel scan if indicated).

- The recordserver can persist the alerts communicated to the UI to file 
if RECORDSERVER_ALERTS_LOG is set accordingly. This allows examining 
them even after a shutdown (using, e.g., the commands plugin). You may 
also want to have your transcoding commands log problems to that file 
too then.

- I have introduced some internationalized texts and obsoleted or 
corrected some others. While I strived to not break existing 
translations, there will be a need to adapt the other freevo.po files (I 
did german only). To do this, it would be probably a good idea to 
examine the modifications of i18n/de/LC_MESSAGES/freevo.po.

- I removed the EPG fetch from the cache helper because it does not 
belong there (it has its own helper). If you depend on this, please add 
another call to your shell scripts. For a possible usage see the above 
.rc script.

- The oneclick plugin contains some translations that have nothing to do 
with weather. I don't understand why, and if there should be even more, 
or less, of them. If I broke something, someone understanding this 
plugin might have a look at this.

I would be glad if my patches were integrated into the freevo1 and kaa 
projects. Thank you again for all your great work, and I hope you will 
enjoy mine too.

Hartmut

Re: [Freevo-devel] PyXML dependency

[Dirk M. <di...@fr...>]

Hi,

On 07/08/2015 11:27 PM, Ruslan Makhmatkhanov wrote:
> FreeBSD port of Freevo 1.9.0 depends on PyXML. I wasn't able to find a 
> reference to this dependency in Freevo docs and setup.py, but it looks 
> like it is used in plugins src/plugins/itv.py and src/tv/plugins/tvtime.py.
> So the questions are: is PyXML indeed required? Are this plugins, that 
> logically should involve some web-scraping still working? If it's a must 
> for a version 1.9.0, was this dependency dropped in 1.9.2b2?

I'm sure the dependency still exists. Many parts of Freevo parse XML
files and while it may work without PyXML, it is only tested with PyXML
installed. PyXML hooks into the normal Python XML handling so you may
not see the dependency.

But you can try without, PyXML was included in Freevo while Pzthon was
at version 2.3 with bad XML support.


Regards,

Dischi


-- 
Time flies... after you hit the snooze button.

[Freevo-devel] PyXML dependency

[Ruslan M. <cv...@ya...>]

Hello,

FreeBSD port of Freevo 1.9.0 depends on PyXML. I wasn't able to find a 
reference to this dependency in Freevo docs and setup.py, but it looks 
like it is used in plugins src/plugins/itv.py and src/tv/plugins/tvtime.py.
So the questions are: is PyXML indeed required? Are this plugins, that 
logically should involve some web-scraping still working? If it's a must 
for a version 1.9.0, was this dependency dropped in 1.9.2b2?

Thanks in advance.

-- 
Regards,
Ruslan

T.O.S. Of Reality

Re: [Freevo-devel] Default resolution.

[Pablo C. E. <pca...@gm...>]

El 11/01/15 10:00, Dirk Meyer escribió:
>> I see. Then, it doesn't makes much sense to set default size at 800x600
>> or, as you say: a "blue" theme at 800x600 is needed.
> I will change it to 800x450. Or should Full HD be the default?
I think 800x450 is a good start, it is a resolution that fits any pc
screen at the beginning. The user can feel how it works and view its
proportions in order to imagine them into a full HD resolution. The user
will have to deal with config file later and adjust it's resolution.


Best regards. Pablo33

[Freevo-devel] Freevo 2.0 Themes (Was: Virtual-box 3D issues and wishes from an user related to music browsing.)

[Dirk M. <di...@fr...>]

Hi,

On 05.01.2015 00:47, Pablo Casas Estévez wrote:
>>> When selected object is a folder: It makes no sense repeat the name of
>>> the album below the picture. It would be more interesting showing some
>>> other information such folder contents, total time...  instead.  (see
>>> screenshot1b.png)
>> Done
> OMG!. 8-O   I thought this change was going to take you much more time. 
> Now looks well and if you select "ramdom playlist" total of items and
> time are also shown. I like it.  :)

The information was already in Freevo, it was only a small update to the
theme XML file.

> I see. Then, it doesn't makes much sense to set default size at 800x600
> or, as you say: a "blue" theme at 800x600 is needed.

I will change it to 800x450. Or should Full HD be the default?

> Where can I find how to make a theme? is has the same rules as freevo1.9x?

Everything is in share/themes/blue. The XML syntax is different. But
IMHO it should be easy to understand the XML part. Inside the XML is a
bit of Python code for the animations because I could not find a simple
XML-way to describe them. If you have questions, just ask.

> Ok, in my case I use Freevo 1.9x with a wireless combo (keyboard and
> mouse), to manage freevo only a keyboard is needed, but sometimes I need
> to launch nautilus pe. to organize files. Will we (users) have a chance
> to launch some applications in windowed mode?  Nowadays my desktop
> environment couples very well with freevo 1.9x

Again, just add a request on github. Using the request on githib gives
me an idea what people miss from 1.9 and what not.

A commands plugin should be very simple. Just lauch the command line.
When I have some free time (maybe next weekend) I will try.

> Yes, I can access filesystem via SSH to change files, but don't expect
> "normal" users to do that. Normal users installs software from "ubuntu
> software center", launches them by clicking on an icon, and next they
> expect to find some kind of guide for the first steps, or a wonderful
> "setup" gui. So they use nautilus to copy files from pendrives and so on.

The config code is very generic internally and it should be possible to
write a config plugin to change everything in the GUI. But that is low
priority.

>>> ¿Is the Detach music player available? ¿what is the key?
>> It is not working right now. Again, please add an issue on github.
> Done, I think next time I should better post at issues track directly.  :)

It is always a good idea to discuss things here first so other people
see that Freevo 2 is working and updating. :)

Regards,

Dischi

-- 
My opinion is neither copyrighted nor trademarked, and it's price
competitive. If you like, I'll trade for one of yours.

Re: [Freevo-devel] Virtual-box 3D issues and wishes from an user related to music browsing.

[Pablo C. E. <pca...@gm...>]

El 04/01/15 20:20, Dirk Meyer escribió:
> Hi,
>
> On 04.01.2015 13:16, Pablo Casas Estévez wrote:
>> INFO stack(137): delete menu with only one item
>> ERROR client(351): Received notification from beacon server for unknown
>> query id 13
>> ================= ... but it works...more or less. Do I have to
>> configure something at config-file?
> There were several nasty bugs in Freevo and kaa.beacon when going into
> directories while the metadata is being generated. Since mine is already
> scanned, I did not see it. Update and it should work. BTW, always update
> Freevo AND all required kaa modules to be sure it works together.
Ok, now I started using git  :D   (Thank you again) . now I use this
"little" script as root.  XD

Should affect the order of installing modules to the result?

================
#!/bin/bash

cd freevo2
git pull
python setup.py install
cd ..

cd kaa-base
git pull
python setup.py install
cd ..

cd kaa-beacon
git pull
python setup.py install
cd ..

cd kaa-candy
git pull
python setup.py install
cd ..

cd kaa-imlib2
git pull
python setup.py install
cd ..

cd kaa-metadata
git pull
python setup.py install
cd ..

cd kaa-webmetadata
git pull
python setup.py install
cd ..
================

>> ## Playing music:
>> ==========
>> I would like to see the info-box song while I listen to music, now it is
>> shown when a song starts and after 2-3 seconds it fades out showing only
>> the background.
>> I've seen that if I seek forward it comes again, but after 2-3 seconds
>> it fades out again.
> It is a feature :) Today was the last vacation day for me. So to avoid
> the idea getting lost, can you add an issue on the github issue tracker.
> As a short fix, you can adjust to timeout value in the audio.xml file to
> a very high value (search for autohide=5, two matches)
Thank you, I've just posted an issue.

>
>> ## At config file: ('scan' variable)
>> ==========
>> I get this for pictures config.
>> # | The variable 'scan' is hours between automatic rescan. If
>> # | the value is 0, the directory will only be scanned if not
>> # | known to Freevo. If set to -1 the directory and all
>> # | subdirectories will be monitored for changes.
>>
>> If this is the same for audio config, it should be also next to audio
>> config in order to explain what is 'scan' variable.
> Fixed.
Nice.
>> ## Browsing audio
>> ==========
>> (see pictures "screenshot1.png" and "screenshot1b.png")
>>
>> When selected object is a folder: It makes no sense repeat the name of
>> the album below the picture. It would be more interesting showing some
>> other information such folder contents, total time...  instead.  (see
>> screenshot1b.png)
> Done
OMG!. 8-O   I thought this change was going to take you much more time. 
Now looks well and if you select "ramdom playlist" total of items and
time are also shown. I like it.  :)

>> On the other hand I can't distinguish if item is a folder or is a song.
>> Maybe songs should add its track-number (or its length) in some way (I
>> mean by retrieving them from its own metadata, an not from its file-name).
> It is confusing for audio items without a trackno. It will look like a
> directory. But I'm open for other ideas.
Ok, I'll give you some of them, give me some time to think about it.

>> ## Showing album's covers
>> ===========
>> Well, I've scaled freevo2 at 1.77777 aspect to simulate a full HD
>> (1066x600px). Square covers are not deformed, but if I change to
>> "default" size 800x600.... covers are stretched. I don't like very much
>> to see deformed images. The same happens at other resolutions that
>> aren't 1.7777 aspect. (see screenshot2.png).
> Yes. The theme is designed for 16:9. For other resolutions a different
> theme file is required. Right now the GUI will always rendered in full
> HD and scaled down to your window size.
I see. Then, it doesn't makes much sense to set default size at 800x600
or, as you say: a "blue" theme at 800x600 is needed.
Where can I find how to make a theme? is has the same rules as freevo1.9x?
>> ## Full Screen option
>> ===========
>> Although I set Full-Screen at config-file freevo2 continues in a window
>> named "python". (see screenshot3.png) and it is under dash and system
>> menu ribbon. I think it could be unity environment, but I'm not very sure.
>> Does freevo2 intended to be used in a desktop environment? or it is only
>> for dedicated machines (without desktop environment)?
> The idea is to have a media PC with Freevo always running fullscreen
> without window manager.
Ok, in my case I use Freevo 1.9x with a wireless combo (keyboard and
mouse), to manage freevo only a keyboard is needed, but sometimes I need
to launch nautilus pe. to organize files. Will we (users) have a chance
to launch some applications in windowed mode?  Nowadays my desktop
environment couples very well with freevo 1.9x

Yes, I can access filesystem via SSH to change files, but don't expect
"normal" users to do that. Normal users installs software from "ubuntu
software center", launches them by clicking on an icon, and next they
expect to find some kind of guide for the first steps, or a wonderful
"setup" gui. So they use nautilus to copy files from pendrives and so on.

On the other hand, if there is something I like from freevo that makes
the difference with others HTPC systems is just the power of launching
apps. I mean "command menu" as well as "games menu". Yes, a desktop
environment is behind, but I don't see it if I don't want to. I simply
start freevo 1.9x by adding it as an item at "start up applications"
(obviously user logging is done automatically). If I have to move a
movie from one folder to another, I just launch "nautilus" from command
menu and the work is done, it's fast and I don't have to close and
re-launch freevo again, when I close nautilus, freevo takes control of
the full screen again.

>> ## Detach player option
>> ===========
>> ¿Is the Detach music player available? ¿what is the key?
> It is not working right now. Again, please add an issue on github.
Done, I think next time I should better post at issues track directly.  :)

> Maybe I'm wishing too much. But I think these are the minimal questions
> to solve to get audio menu working fine.
> I'm happy to get feedback for 2.0. It works great for me and I would
> love to have more people using Freevo 2.0 and maybe start writing more
> plugins.
Thanks again for your effort and support.

This is the last question:
Is there a defined "set" of icons that freevo2 needs to work ?.  I've
browsed folders on code and seen Themes/blue/... icons, folders mimetype
icons....  audio.xml... video.xml....main.xml....  are those the files
that define the "blue" layout?. I think so. You said that you wanted a
better image or photo icon. Is that what I attached?

Have a nice day at work, I still have a couple of days.

Best regards. Pablo33

Re: [Freevo-devel] Virtual-box 3D issues and wishes from an user related to music browsing.

[Dirk M. <di...@fr...>]

Hi,

On 04.01.2015 13:16, Pablo Casas Estévez wrote:
> INFO stack(137): delete menu with only one item
> ERROR client(351): Received notification from beacon server for unknown
> query id 13
> ================= ... but it works...more or less. Do I have to
> configure something at config-file?

There were several nasty bugs in Freevo and kaa.beacon when going into
directories while the metadata is being generated. Since mine is already
scanned, I did not see it. Update and it should work. BTW, always update
Freevo AND all required kaa modules to be sure it works together.

> ## "Freevo2 always on top" issue
> ===================
> 
> "Freevo2 always on top" issue has gone once I have deactivated 3D
> acceleration on the virtual machine. The same has happened with the
> spontaneous ins and outs of the freevo windows and crashes on the
> screen. Now, animations go a bit slower, but it works for testing. I
> think 3D issue must not show on a real machine.

No, works fine here. I guess it is vm related.

> ## Playing music:
> ==========
> I would like to see the info-box song while I listen to music, now it is
> shown when a song starts and after 2-3 seconds it fades out showing only
> the background.
> I've seen that if I seek forward it comes again, but after 2-3 seconds
> it fades out again.

It is a feature :) Today was the last vacation day for me. So to avoid
the idea getting lost, can you add an issue on the github issue tracker.
As a short fix, you can adjust to timeout value in the audio.xml file to
a very high value (search for autohide=5, two matches)

> ## At config file: ('scan' variable)
> ==========
> I get this for pictures config.
> # | The variable 'scan' is hours between automatic rescan. If
> # | the value is 0, the directory will only be scanned if not
> # | known to Freevo. If set to -1 the directory and all
> # | subdirectories will be monitored for changes.
> 
> If this is the same for audio config, it should be also next to audio
> config in order to explain what is 'scan' variable.

Fixed.

> ## Browsing audio
> ==========
> (see pictures "screenshot1.png" and "screenshot1b.png")
> 
> When selected object is a folder: It makes no sense repeat the name of
> the album below the picture. It would be more interesting showing some
> other information such folder contents, total time...  instead.  (see
> screenshot1b.png)

Done

> On the other hand I can't distinguish if item is a folder or is a song.
> Maybe songs should add its track-number (or its length) in some way (I
> mean by retrieving them from its own metadata, an not from its file-name).

It is confusing for audio items without a trackno. It will look like a
directory. But I'm open for other ideas.

> ## Showing album's covers
> ===========
> Well, I've scaled freevo2 at 1.77777 aspect to simulate a full HD
> (1066x600px). Square covers are not deformed, but if I change to
> "default" size 800x600.... covers are stretched. I don't like very much
> to see deformed images. The same happens at other resolutions that
> aren't 1.7777 aspect. (see screenshot2.png).

Yes. The theme is designed for 16:9. For other resolutions a different
theme file is required. Right now the GUI will always rendered in full
HD and scaled down to your window size.

> ## Full Screen option
> ===========
> Although I set Full-Screen at config-file freevo2 continues in a window
> named "python". (see screenshot3.png) and it is under dash and system
> menu ribbon. I think it could be unity environment, but I'm not very sure.
> Does freevo2 intended to be used in a desktop environment? or it is only
> for dedicated machines (without desktop environment)?

The idea is to have a media PC with Freevo always running fullscreen
without window manager.

> ## Detach player option
> ===========
> ¿Is the Detach music player available? ¿what is the key?

It is not working right now. Again, please add an issue on github.

> Maybe I'm wishing too much. But I think these are the minimal questions
> to solve to get audio menu working fine.

I'm happy to get feedback for 2.0. It works great for me and I would
love to have more people using Freevo 2.0 and maybe start writing more
plugins.


Regards,

Dischi

-- 
Only Irish coffee provides in a single glass all four essential food
groups -- alcohol, caffeine, sugar, and fat.
		-- Alex Levine

Re: [Freevo-devel] Virtual-box 3D issues and wishes from an user related to music browsing.

[Pablo C. E. <pca...@gm...>]

Hi, 

El 31/12/14 14:05, Dirk Meyer escribió:
> Hi,
>
> On 30.12.2014 21:20, Pablo Casas Estévez wrote:
>> I renamed covers from cover.jpeg to jpg
>> The issue is gone.  :)
>>
>> Maybe kaa.beacon should also accept .jpeg as covers.  ;)
> Fixed. Update kaa.metadata and kaa.beacon.
Ok, I'm testing it again, it seems that you have to browse in and out to
update changes made on "covers" name (or maybe is a question of wait a
bit of time). I also noticed that "cover.JPG" or "COVER.JPG" is not
supported, but I think this point doesn't matter.

my terminal says:
=================
INFO stack(120): autoselect action
INFO stack(137): delete menu with only one item
INFO stack(120): autoselect action
ERROR client(351): Received notification from beacon server for unknown
query id 10
ERROR client(351): Received notification from beacon server for unknown
query id 10
INFO stack(137): delete menu with only one item
INFO stack(120): autoselect action
INFO directory(128): create metainfo for /home/pablo/Music/ZZ
Top/Sleeping Bag/
INFO stack(137): delete menu with only one item
ERROR client(351): Received notification from beacon server for unknown
query id 13
================= ... but it works...more or less. Do I have to
configure something at config-file?


## "Freevo2 always on top" issue
===================

"Freevo2 always on top" issue has gone once I have deactivated 3D
acceleration on the virtual machine. The same has happened with the
spontaneous ins and outs of the freevo windows and crashes on the
screen. Now, animations go a bit slower, but it works for testing. I
think 3D issue must not show on a real machine.

<> wishes <>

## Playing music:
==========
I would like to see the info-box song while I listen to music, now it is
shown when a song starts and after 2-3 seconds it fades out showing only
the background.
I've seen that if I seek forward it comes again, but after 2-3 seconds
it fades out again.


## At config file: ('scan' variable)
==========
I get this for pictures config.
# | The variable 'scan' is hours between automatic rescan. If
# | the value is 0, the directory will only be scanned if not
# | known to Freevo. If set to -1 the directory and all
# | subdirectories will be monitored for changes.

If this is the same for audio config, it should be also next to audio
config in order to explain what is 'scan' variable.


## Browsing audio
==========
(see pictures "screenshot1.png" and "screenshot1b.png")

When selected object is a folder: It makes no sense repeat the name of
the album below the picture. It would be more interesting showing some
other information such folder contents, total time...  instead.  (see
screenshot1b.png)
On the other hand I can't distinguish if item is a folder or is a song.
Maybe songs should add its track-number (or its length) in some way (I
mean by retrieving them from its own metadata, an not from its file-name).

## Showing album's covers
===========
Well, I've scaled freevo2 at 1.77777 aspect to simulate a full HD
(1066x600px). Square covers are not deformed, but if I change to
"default" size 800x600.... covers are stretched. I don't like very much
to see deformed images. The same happens at other resolutions that
aren't 1.7777 aspect. (see screenshot2.png).


## Full Screen option
===========
Although I set Full-Screen at config-file freevo2 continues in a window
named "python". (see screenshot3.png) and it is under dash and system
menu ribbon. I think it could be unity environment, but I'm not very sure.
Does freevo2 intended to be used in a desktop environment? or it is only
for dedicated machines (without desktop environment)?


## Detach player option
===========
¿Is the Detach music player available? ¿what is the key?

Maybe I'm wishing too much. But I think these are the minimal questions
to solve to get audio menu working fine.

Regards. Pablo33

Re: [Freevo-devel] testing cover, Yatse, and sending logs.

[Dirk M. <di...@fr...>]

Hi,

On 31.12.2014 14:05, Dirk Meyer wrote:
> On 30.12.2014 21:20, Pablo Casas Estévez wrote:
>> My terminal says(when I play music and press "back" on the smartphone):
>> ERROR eventserver(87): unmapped key: back
>> ERROR eventserver(87): unmapped key: back
>> ERROR eventserver(87): unmapped key: back
> 
> Yes. Right now only Menu and Video works. Image and Music is still on
> the TODO list. Give me some time.

Music playback and image viewing is now also supported with the android
remote when you update the Freevo master. If you also update kaa.candy
you get visualisation during audio playback.


Regards,

Dischi

-- 
I don't think so, therefore I'm probably not.

Re: [Freevo-devel] Vector blurrsplash.svg

[Dirk M. <di...@fr...>]

Hi,

On 31.12.2014 16:03, Pablo Casas wrote:
> Those attachment are: logo for full DH definition screen (by preserving
> original size 1:1), and 3 backgrounds for different screen-sizes, this
> time without logo. If you need the logo (or backgrounds) at some kind of
> resolution just tell me, I'll give you the work done :)

Thanks, background and main menu logo are now updated on github.


Regards,

Dischi

-- 
How can something be 'new and improved'? If it's new what was it
improving on?

Re: [Freevo-devel] Vector blurrsplash.svg

[Pablo C. <pca...@gm...>]

On 31/12/14 13:44, Dirk Meyer wrote:
> Hi,
>
> On 30.12.2014 00:03, Pablo Casas wrote:
>> It's a .svg file, 100% vector so you can scale it as you want. I
>> rendered it at some common screen-sizes.
> Thanks, but I need it without the blue background for the fade effect on
> the main screen. Opening it with inkscape does not give me a way to
> remove it.
This vector drawing is structured in 4 layers, I usually lock layers to
prevent accidental damages on them. You can unlock them at any time by
showing layers toolbox and unlocking them.
Those attachment are: logo for full DH definition screen (by preserving
original size 1:1), and 3 backgrounds for different screen-sizes, this
time without logo. If you need the logo (or backgrounds) at some kind of
resolution just tell me, I'll give you the work done :)



Regards, Pablo33

Re: [Freevo-devel] testing cover, Yatse, and sending logs.

[Dirk M. <di...@fr...>]

Hi,

On 30.12.2014 21:20, Pablo Casas Estévez wrote:
> I renamed covers from cover.jpeg to jpg
> The issue is gone.  :)
> 
> Maybe kaa.beacon should also accept .jpeg as covers.  ;)

Fixed. Update kaa.metadata and kaa.beacon.

> ....OK, installed freevo2-master (30-dic-2014)
> 
> I had to configure media-server manually IP + port 8080
> 
> It's a good start, I could switch from Movies-music-Pictures quickly.
> It's the first time I see something like that.  :)
> 
> I Played a song, I used cursors keys on the smartphone, but I couldn't
> exit from song once it is playing, although "back" works perfectly by
> browsing items and menus.  :-?
> 
> My terminal says(when I play music and press "back" on the smartphone):
> ERROR eventserver(87): unmapped key: back
> ERROR eventserver(87): unmapped key: back
> ERROR eventserver(87): unmapped key: back

Yes. Right now only Menu and Video works. Image and Music is still on
the TODO list. Give me some time.

> And that's all for today. I wish you a happy new year!

Same to you.

Regards,

Dischi

-- 
A day without sun shine is like, you know, night.

Re: [Freevo-devel] Vector blurrsplash.svg

[Dirk M. <di...@fr...>]

Hi,

On 30.12.2014 00:03, Pablo Casas wrote:
> It's a .svg file, 100% vector so you can scale it as you want. I
> rendered it at some common screen-sizes.

Thanks, but I need it without the blue background for the fade effect on
the main screen. Opening it with inkscape does not give me a way to
remove it.

>> This is a lot. I'm not sure anyone but me uses 2.0
> HEY! Does anybody actually using freevo2?!! 

No idea. I do :) Maybe your guide will help others.

>>> I think I can help on graphics, layouts, making user manuals.
>> I need a higher resolution logo (see above) and a much better directory
>> icon for the photo menu.
> Here you are. I'll have a look to this icons too.

Thanks.

Regards,

Dischi

-- 
An aquarium is just interactive television for cats.

[Freevo-devel] testing cover, Yatse, and sending logs.

[Pablo C. E. <pca...@gm...>]

2014-12-30 19:58:41,013 WARNING  [ candy] main.py 120: sync took 0.0583 sec
2014-12-30 19:58:41,119 ERROR    [ candy] __init__.py 47: disable player mplayer: No module named display
2014-12-30 19:58:41,119 WARNING  [ candy] main.py 120: sync took 0.0698 sec
2014-12-30 19:58:41,133 WARNING  [ candy] main.py 134: kaa.candy warning: sync took 0.0137 sec
2014-12-30 19:58:41,144 WARNING  [ candy] main.py 134: kaa.candy warning: sync took 0.0103 sec
2014-12-30 19:58:41,165 WARNING  [ candy] main.py 120: sync took 0.0106 sec
2014-12-30 19:58:41,217 WARNING  [ candy] main.py 120: sync took 0.0461 sec
2014-12-30 19:58:41,235 WARNING  [ candy] main.py 120: sync took 0.0179 sec
2014-12-30 19:58:41,328 WARNING  [ candy] main.py 120: sync took 0.0691 sec
2014-12-30 19:58:41,376 WARNING  [ candy] main.py 120: sync took 0.0477 sec
2014-12-30 19:58:41,398 WARNING  [ candy] main.py 120: sync took 0.0188 sec
2014-12-30 19:58:55,755 WARNING  [ candy] main.py 120: sync took 0.0161 sec
2014-12-30 19:58:55,775 ERROR    [ candy] __init__.py 47: disable player mplayer: No module named display
2014-12-30 19:58:55,778 WARNING  [ candy] main.py 120: sync took 0.0233 sec
2014-12-30 19:58:55,851 WARNING  [ candy] main.py 120: sync took 0.0364 sec
2014-12-30 19:58:55,872 WARNING  [ candy] main.py 120: sync took 0.0201 sec
2014-12-30 19:58:55,919 WARNING  [ candy] main.py 120: sync took 0.0187 sec
2014-12-30 19:58:55,950 WARNING  [ candy] main.py 120: sync took 0.0296 sec
2014-12-30 19:58:55,969 WARNING  [ candy] main.py 120: sync took 0.0184 sec
2014-12-30 19:59:01,288 ERROR    [ candy] __init__.py 47: disable player mplayer: No module named display
2014-12-30 19:59:01,289 WARNING  [ candy] main.py 120: sync took 0.0269 sec
2014-12-30 19:59:01,307 WARNING  [ candy] main.py 120: sync took 0.0122 sec
2014-12-30 19:59:01,359 WARNING  [ candy] main.py 120: sync took 0.0440 sec
2014-12-30 19:59:01,378 WARNING  [ candy] main.py 120: sync took 0.0185 sec
2014-12-30 19:59:01,455 WARNING  [ candy] main.py 120: sync took 0.0670 sec
2014-12-30 19:59:01,484 WARNING  [ candy] main.py 120: sync took 0.0116 sec
2014-12-30 19:59:08,763 ERROR    [ candy] __init__.py 47: disable player mplayer: No module named display
2014-12-30 19:59:08,764 WARNING  [ candy] main.py 120: sync took 0.0278 sec
2014-12-30 19:59:08,829 WARNING  [ candy] main.py 120: sync took 0.0452 sec
2014-12-30 19:59:08,912 WARNING  [ candy] main.py 120: sync took 0.0518 sec
2014-12-30 19:59:08,937 WARNING  [ candy] main.py 120: sync took 0.0201 sec
2014-12-30 19:59:08,955 WARNING  [ candy] main.py 120: sync took 0.0176 sec
2014-12-30 19:59:08,989 WARNING  [ candy] main.py 120: sync took 0.0106 sec
2014-12-30 19:59:17,330 WARNING  [ candy] main.py 120: sync took 0.0117 sec
2014-12-30 19:59:17,349 ERROR    [ candy] __init__.py 47: disable player mplayer: No module named display
2014-12-30 19:59:17,350 WARNING  [ candy] main.py 120: sync took 0.0191 sec
2014-12-30 19:59:17,418 WARNING  [ candy] main.py 120: sync took 0.0356 sec
2014-12-30 19:59:17,434 WARNING  [ candy] main.py 120: sync took 0.0158 sec
2014-12-30 19:59:17,476 WARNING  [ candy] main.py 120: sync took 0.0192 sec
2014-12-30 19:59:17,509 WARNING  [ candy] main.py 120: sync took 0.0261 sec
2014-12-30 19:59:17,541 WARNING  [ candy] main.py 120: sync took 0.0232 sec
2014-12-30 19:59:17,577 WARNING  [ candy] main.py 120: sync took 0.0126 sec
2014-12-30 19:59:24,261 WARNING  [ candy] main.py 120: sync took 0.0145 sec
2014-12-30 19:59:24,279 ERROR    [ candy] __init__.py 47: disable player mplayer: No module named display
2014-12-30 19:59:24,280 WARNING  [ candy] main.py 120: sync took 0.0184 sec
2014-12-30 19:59:24,342 WARNING  [ candy] main.py 120: sync took 0.0373 sec
2014-12-30 19:59:24,361 WARNING  [ candy] main.py 120: sync took 0.0182 sec
2014-12-30 19:59:24,415 WARNING  [ candy] main.py 120: sync took 0.0403 sec
2014-12-30 19:59:24,447 WARNING  [ candy] main.py 120: sync took 0.0296 sec
2014-12-30 19:59:25,269 WARNING  [ candy] main.py 120: sync took 0.0107 sec
2014-12-30 19:59:32,776 ERROR    [ candy] __init__.py 47: disable player mplayer: No module named display
2014-12-30 19:59:32,776 WARNING  [ candy] main.py 120: sync took 0.0270 sec
2014-12-30 19:59:32,843 WARNING  [ candy] main.py 120: sync took 0.0390 sec
2014-12-30 19:59:32,861 WARNING  [ candy] main.py 120: sync took 0.0178 sec
2014-12-30 19:59:32,904 WARNING  [ candy] main.py 120: sync took 0.0143 sec
2014-12-30 19:59:32,940 WARNING  [ candy] main.py 120: sync took 0.0293 sec
2014-12-30 19:59:32,962 WARNING  [ candy] main.py 120: sync took 0.0211 sec
2014-12-30 19:59:32,978 WARNING  [ candy] main.py 120: sync took 0.0158 sec
2014-12-30 19:59:33,004 WARNING  [ candy] main.py 120: sync took 0.0116 sec
2014-12-30 19:59:38,661 ERROR    [ candy] __init__.py 47: disable player mplayer: No module named display
2014-12-30 19:59:38,662 WARNING  [ candy] main.py 120: sync took 0.0299 sec
2014-12-30 19:59:38,728 WARNING  [ candy] main.py 120: sync took 0.0357 sec
2014-12-30 19:59:38,747 WARNING  [ candy] main.py 120: sync took 0.0183 sec
2014-12-30 19:59:38,789 WARNING  [ candy] main.py 120: sync took 0.0289 sec
2014-12-30 19:59:38,842 WARNING  [ candy] main.py 120: sync took 0.0392 sec
2014-12-30 19:59:38,865 WARNING  [ candy] main.py 120: sync took 0.0107 sec
2014-12-30 19:59:38,885 WARNING  [ candy] main.py 120: sync took 0.0153 sec
2014-12-30 19:59:38,899 WARNING  [ candy] main.py 120: sync took 0.0124 sec
2014-12-30 19:59:42,648 WARNING  [ candy] main.py 120: sync took 0.0134 sec
2014-12-30 19:59:50,566 ERROR    [ candy] __init__.py 47: disable player mplayer: No module named display
2014-12-30 19:59:50,567 WARNING  [ candy] main.py 120: sync took 0.0264 sec
2014-12-30 19:59:50,629 WARNING  [ candy] main.py 120: sync took 0.0365 sec
2014-12-30 19:59:50,648 WARNING  [ candy] main.py 120: sync took 0.0186 sec
2014-12-30 19:59:50,696 WARNING  [ candy] main.py 120: sync took 0.0193 sec
2014-12-30 19:59:50,728 WARNING  [ candy] main.py 120: sync took 0.0293 sec
2014-12-30 19:59:50,744 WARNING  [ candy] main.py 120: sync took 0.0155 sec
2014-12-30 19:59:52,684 WARNING  [ candy] main.py 120: sync took 0.0120 sec
2014-12-30 20:00:47,879 ERROR    [ candy] __init__.py 47: disable player mplayer: No module named display
2014-12-30 20:00:47,879 WARNING  [ candy] main.py 120: sync took 0.0239 sec
2014-12-30 20:00:47,938 WARNING  [ candy] main.py 120: sync took 0.0442 sec
2014-12-30 20:00:47,960 WARNING  [ candy] main.py 120: sync took 0.0217 sec
2014-12-30 20:00:48,059 WARNING  [ candy] main.py 120: sync took 0.0974 sec
2014-12-30 20:00:48,105 WARNING  [ candy] main.py 120: sync took 0.0263 sec
2014-12-30 20:00:48,124 WARNING  [ candy] main.py 120: sync took 0.0129 sec
2014-12-30 20:00:53,843 ERROR    [ candy] __init__.py 47: disable player mplayer: No module named display
2014-12-30 20:00:53,843 WARNING  [ candy] main.py 120: sync took 0.0233 sec
2014-12-30 20:00:53,899 WARNING  [ candy] main.py 120: sync took 0.0446 sec
2014-12-30 20:00:53,915 WARNING  [ candy] main.py 120: sync took 0.0145 sec
2014-12-30 20:00:53,964 WARNING  [ candy] main.py 120: sync took 0.0266 sec
2014-12-30 20:00:54,012 WARNING  [ candy] main.py 120: sync took 0.0383 sec
2014-12-30 20:00:54,032 WARNING  [ candy] main.py 120: sync took 0.0112 sec
2014-12-30 20:00:54,050 WARNING  [ candy] main.py 120: sync took 0.0170 sec
2014-12-30 20:00:54,061 WARNING  [ candy] main.py 120: sync took 0.0111 sec
2014-12-30 20:00:55,634 WARNING  [ candy] main.py 134: kaa.candy warning: sync took 0.0109 sec

[Freevo-devel] Vector blurrsplash.svg

[Pablo C. <pca...@gm...>]

On 29/12/14 11:02, Dirk Meyer wrote:
>> Main menu:
>> Good layout,
>> I changed resolution to 1440x900 and freevo logo looks pixelated. that's
>> not good.
> The logo is kind of old ... older than high resolution TV sets. If
> someone can provide a better image I will take it.
Ok, I think I can get some of this ready soon. XDD  This is a copy-based
on main blurrsplash.jpg
It's a .svg file, 100% vector so you can scale it as you want. I
rendered it at some common screen-sizes.
>
> I usually save one good cover next to album's song, or only inside the
> first song of the album, and do not save thumbnails into others mp3.
> With freevo2 I only can view this cover on the first song.
> Freevo (or better kaa.beacon) should detect (folder|cover).(png|jpg) in
> a directory.
Let me check this again.
>> Remote control:
>>
>> I activated as you suggested httpserver, jsonrpc,  and downloaded
>> Android-Yatse. Well, I couldn't find multimedia server with yatse (yes,
>> both of them are in the same net). On the other hand, I could test
>> httpserver (:8080), and it's great.
>> Do I need all kaa-packages installed on the system in order to get working?
> I just tested it. The latest version of Yatse uses mute/unmute to test
> the eventserver setup. This command was not supported. Please update
> freevo git master and try again. It would work now.
Give me some time to test again.
>> Well, I would like to help to the project, but I'm not a developer, my
>> python knowledge are really poor. I only can test, say my user opinion.
> This is a lot. I'm not sure anyone but me uses 2.0
HEY! Does anybody actually using freevo2?!! 
>> I think I can help on graphics, layouts, making user manuals.
> I need a higher resolution logo (see above) and a much better directory
> icon for the photo menu.
Here you are. I'll have a look to this icons too.

Regards, Pablo33

Re: [Freevo-devel] My little freevo2 review

[Dirk M. <di...@fr...>]

Hi,

On 27.12.2014 12:45, Pablo Casas wrote:
> I would like to run "freevo2 --help" to get a little help from the
> terminal. Maybe there is nothing to say, or maybe you can point to the
> config directory, or perform some utilities from command line.

There is nothing to say. Freevo just starts.

> Config file, well I have seen "freevo2.conf" and how it works. It's well
> explained, it has some examples, good, real good. I like how you advise
> at the end of the file if there has been some wrong line at
> configuration, awesome!. It has default values and even if you have
> changed it, it remains visible as a comment.

Thanks.

> Launching freevo:
> It's fast,

:)

> Main menu:
> Good layout,
> I changed resolution to 1440x900 and freevo logo looks pixelated. that's
> not good.

The logo is kind of old ... older than high resolution TV sets. If
someone can provide a better image I will take it.

> Window container system:
> I activated full screen, but freevo continues into a window and don't
> fit my screen, I can move this window. The worst thing is that this
> screen is over anything on my system, it's always up. I think it could
> be VirtualBox.

Freevo is designed to be full screen. You can set the resolution in the
config file. But for me I can also switch Freevo in the background.

> Issue: Flashes on the main window:
> When browsing up and down on menus, sometimes the main window disappears
> an instant, and recovers itself showing on another position at the
> screen. When this occurs my terminal get this:
> 
> libGL error: core dri or dri2 extension not found
> libGL error: failed to load driver: vboxvideo
> OpenGL Warning: crPixelCopy3D:  simply crMemcpy'ing from srcPtr to dstPtr

This looks like a restart. The GUI is an extra process to prevent a
whole Freevo crash if a video crashes the GUI. Freevo detects the crash
and restarts the GUI process. The question is why? Maybe it is related
to OpenGL running in a virtual machine.

> The efects navigating when you enter on a menu, or go back, are cool. I
> like them.

Thanks.

> Sometimes it crashes when moving on items: my terminal says:
> 
> #####
> ERROR io(770): some error
> Traceback (most recent call last):
>   File "/usr/local/lib/python2.7/dist-packages/kaa/base/io.py", line
> 756, in _handle_read
>     data = self._read(self._chunk_size)
>   File "/usr/local/lib/python2.7/dist-packages/kaa/base/sockets.py",
> line 708, in _read
>     return self._channel.recv(size)
> error: [Errno 104] Connection reset by peer
> ERROR stage(162): two backend errors in 5 seconds, giving up
> pablo@pablo-freevo2:~$
> #####

Like above. The GUI crashes an Freevo restarts it. But is crashes again
and Freevo gives up to avoid restarting over and over again.

Please set debug = True in the config file, maybe we can find out why.
And if it happens, please send me the last 20-30 lines in
~/.freevo/log/freevo.log and ~/.freevo/log/candy

> I usually save one good cover next to album's song, or only inside the
> first song of the album, and do not save thumbnails into others mp3.
> With freevo2 I only can view this cover on the first song.

Freevo (or better kaa.beacon) should detect (folder|cover).(png|jpg) in
a directory.

> Remote control:
> 
> I activated as you suggested httpserver, jsonrpc,  and downloaded
> Android-Yatse. Well, I couldn't find multimedia server with yatse (yes,
> both of them are in the same net). On the other hand, I could test
> httpserver (:8080), and it's great.
> Do I need all kaa-packages installed on the system in order to get working?

I just tested it. The latest version of Yatse uses mute/unmute to test
the eventserver setup. This command was not supported. Please update
freevo git master and try again. It would work now.

> Well, I would like to help to the project, but I'm not a developer, my
> python knowledge are really poor. I only can test, say my user opinion.

This is a lot. I'm not sure anyone but me uses 2.0

> I think I can help on graphics, layouts, making user manuals.

I need a higher resolution logo (see above) and a much better directory
icon for the photo menu.


Regards,

Dischi

-- 
The only problem with mornings is that they happen too early in the
day.

[Freevo-devel] My little freevo2 review

[Pablo C. <pca...@gm...>]

Hi freevo-devels. This is my review and test on freevo2.


Getting help: I miss:

I would like to run "freevo2 --help" to get a little help from the
terminal. Maybe there is nothing to say, or maybe you can point to the
config directory, or perform some utilities from command line.


Config file, well I have seen "freevo2.conf" and how it works. It's well
explained, it has some examples, good, real good. I like how you advise
at the end of the file if there has been some wrong line at
configuration, awesome!. It has default values and even if you have
changed it, it remains visible as a comment.


Launching freevo:
It's fast,


Main menu:
Good layout,
I changed resolution to 1440x900 and freevo logo looks pixelated. that's
not good.


Window container system:
I activated full screen, but freevo continues into a window and don't
fit my screen, I can move this window. The worst thing is that this
screen is over anything on my system, it's always up. I think it could
be VirtualBox.


Issue: Flashes on the main window:
When browsing up and down on menus, sometimes the main window disappears
an instant, and recovers itself showing on another position at the
screen. When this occurs my terminal get this:


#####

libGL error: core dri or dri2 extension not found
libGL error: failed to load driver: vboxvideo
OpenGL Warning: crPixelCopy3D:  simply crMemcpy'ing from srcPtr to dstPtr
WARNING candy:main(120): sync took 0.0118 sec
ERROR candy:__init__(47): disable player mplayer: No module named display
WARNING candy:main(120): sync took 0.0313 sec
WARNING candy:main(120): sync took 0.0476 sec
WARNING candy:main(120): sync took 0.0180 sec
WARNING candy:main(120): sync took 0.0627 sec
WARNING candy:main(120): sync took 0.0253 sec
WARNING candy:main(120): sync took 0.0126 sec
WARNING candy:main(120): sync took 0.0238 sec
WARNING candy:main(120): sync took 0.0126 sec
WARNING candy:main(120): sync took 0.0138 sec
#####



The efects navigating when you enter on a menu, or go back, are cool. I
like them.

Sometimes it crashes when moving on items: my terminal says:

#####
ERROR io(770): some error
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/kaa/base/io.py", line
756, in _handle_read
    data = self._read(self._chunk_size)
  File "/usr/local/lib/python2.7/dist-packages/kaa/base/sockets.py",
line 708, in _read
    return self._channel.recv(size)
error: [Errno 104] Connection reset by peer
ERROR stage(162): two backend errors in 5 seconds, giving up
pablo@pablo-freevo2:~$
#####


I like browse by artist, browse by calendar, and the way album covers
it's shown. Yes it's a nice work. Now I understand why it is called
freevo 2 an not 1.9.x.

I usually save one good cover next to album's song, or only inside the
first song of the album, and do not save thumbnails into others mp3.
With freevo2 I only can view this cover on the first song.


Remote control:

I activated as you suggested httpserver, jsonrpc,  and downloaded
Android-Yatse. Well, I couldn't find multimedia server with yatse (yes,
both of them are in the same net). On the other hand, I could test
httpserver (:8080), and it's great.
Do I need all kaa-packages installed on the system in order to get working?
My system only have installed:

    freevo2-master
    kaa-base-master
    kaa-beacon-master
    kaa-candy-master
    kaa-imlib2-master
    kaa-metadata-master
    kaa-webmetadata-master


Well, I would like to help to the project, but I'm not a developer, my
python knowledge are really poor. I only can test, say my user opinion.
I think I can help on graphics, layouts, making user manuals. Let me
know if you need something about this. I'll keep this virtual machine
for later testings.

Best regards. Pablo33.

[Freevo-devel] Android remote for Freevo 2.0

[Dirk M. <di...@fr...>]

Hi,

as I said, Freevo is only sleeping and not dead. :)

I played with XBMC some weeks ago and while I still prefer Freevo over
XBMC I kind of miss a good Android remote control. My idea was to write
one, but there are apps for XBMC out there looking better than anything
I could do.

Therefore, I added jsonrpc support for Freevo 2.0 to make look Freevo
like XBMC for these remotes. The jsonrpc plugin was just pushed to github.

Limitations:
- Only tested with yatse on Android
- Supports basic navigation
- Only the video player is detected as activate player
- Only the TV Show database works

kaa.webmetadata is required to get information and images.


Regards,

Dischi

-- 
Only Irish coffee provides in a single glass all four essential food
groups -- alcohol, caffeine, sugar, and fat.
		-- Alex Levine

Re: [Freevo-devel] fixed tv guide

[Dirk M. <di...@fr...>]

Hi,

On 02.05.2014 21:59, A Mennucc wrote:
> I fixed the www TV guide in current GIT, and sent a pull request; since
> I am a newbie at GitHub, I hope all is fine.

Since there is nobody maintaining the 1.x tree nothing will happen. :(

If there is a 2.0 request I will look at it but since I do not use 1.x
anymore, I need someone else looking at patches and merging them. Anyone?


Regards,

Dischi

-- 
I don't think so, therefore I'm probably not.

Re: [Freevo-devel] The future of Freevo(.org)

[Jason T. <ta...@ur...>]

On 14-01-21 03:33 AM, Meine, Hans wrote:
> I still admire the coroutine things in kaa, a concept I had some difficulties to get my head around, but which I really love.

You might be interested to know (and I was delighted to learn about this
a bit over a year ago now) that as of Python 3.4, the asyncio module in
Python along with PEP 3156 has implemented most of what kaa.base sought
to accomplish with its core asynchronous framework.

I'm pretty sure I'm on the record here and elsewhere in saying that
every language needs a standardized event loop and some kind of Future
object (kaa calls it InProgress) to make a proper asynchronous
ecosystem.  PEP 3156 does all that and goes further by defining
coroutines and ensuring the event loop has a built-in coroutine trampoline.

And so it's with great satisfaction that I can declare kaa.base obsoleted.

There are a few pieces of kaa.base that are still useful that haven't
been obsoleted, like the object database abstraction (which solves a
certain class of problem efficiently), and the openssl wrapper, which is
still more featureful than the batteries included module.

But the fundamental goal of the core framework [1] is now supplanted by
asyncio (aka Tulip) in Python 3.4.  I expect we will see a flourishing
community of interoperable async libraries now, and that's the best
result I could have hoped for, even if Kaa didn't have anything to do
with it (although Guido did look at Kaa in the early days to see if
there were ideas worth stealing).

As for Freevo itself, yes, I've basically moved onto xbmc, which has for
some time now sufficiently scratched the itches that brought me to
Freevo over 10 years ago.  My day job leaves me little personal hacking
time, and when I have it, there are more far more annoying itches to
scratch nowadays, given the modern landscape of open source HTPC
software available for Linux.  That too is a positive result. :)

Regards,
Jason.

[1] http://api.freevo.org/kaa-base/index.html#core-framework

[Freevo-devel] fixed tv guide

[A M. <men...@de...>]

hi,

I fixed the www TV guide in current GIT, and sent a pull request; since
I am a newbie at GitHub, I hope all is fine.

a.

Re: [Freevo-devel] How about another SKIN

[Pablo C. <pca...@gm...>]

Hi Maciej,

Ufff, finding this "branch" has been a hard work since I'm not a
programmer and it's the first time I deal with this web. But finally I
think I've downloaded the right zip.
link to branch <https://github.com/murbaniak/freevo1/tree/xbmc>

So, It is supposed that if I install this "branch" it'll work?.... well,
I'll setup a new VMachine with ubuntu 13.10 and I'll try it.

I've been seen some content and its great, there are lots of icons,  :D
  it really looks as Xbmc  ;D 

Thank-you Maciej.

Regards.



On 03/04/14 16:50, Maciej Urbaniak wrote:
> Hi Pablo,
>
> Couple of years ago I wrote the new skin mimicking xbmc. It's a high
> resolution skin meant to work in 16:9 mode. You can find it on a
> branch of 1.9.2 in GitHub. It's fully functional and mostly complete.
> I have extended the original skin rendering code to cope wuth some new
> functionalities I have introduced.
>
> You can play with it to your heart's content :-) 
>
> There are most likely bugs and some additional work can be done. 
>
> It has never been merged into the main trunk of 1.9.2
>
> Cheers,
> Maciej
>
> Sent from my iPhone
>
>
> On 02.04.2014, at 21:10, Pablo Casas <pca...@gm...
> <mailto:pca...@gm...>> wrote:
>
>> Hi, I'm Pablo33, and this is my first message.
>>
>> I know that it is no much activity in freevo, but I prefer to write
>> this than shut up forever: I have started to create a new skin.
>>
>> There are many questions rounding my head, it may be a bit late for
>> this. Well, I'll go on and if you think its a good skin you can
>> include it in later releases or may publish to other freevo 1.9 users.
>>
>>
>> I've read freevo wiki "http://www.freevo.org/wiki/1.x/Skins.html" and
>> tried to understand the structure. Even I started learning a bit of
>> python a month ago, but for my surprise skins definitions are in an
>> XML file XDD .
>>
>> I've uploaded the files into a compressed archive, so you can take a
>> look.
>> link to the file <http://ubuntuone.com/4TodYdqBziwmum0o5UIodo>
>>
>>
>> Although base resolution for skins is 800x600, the skin is intended
>> to fit only into full HD resolution, so my base resolution is 1920x1080.
>> I started to draw a set of icons, in high resolution (maybe too
>> high). (they are mixed with a set of icons that already were there)
>>
>> More or less everything it's working properly, the
>> folder_game.png-icon doesn't work (and I don't know why).
>>
>> I don't know where to change other icons, such web_radio.  No idea
>> for now, i've seen an image-file in folder "/icons/themes/" but ...
>> it shows invisible in freevo menu.
>>
>> Other issues are: I can't see other icons in action. For example:
>> CD-DVD player doesn't work for me, and I haven't TV card too. And I
>> have no idea of the "freevo-icon scope" ¿how many icons does freevo
>> use? ¿which ones? from now I've started from a theme set.
>>
>> Well, can I wait for same light or help to test and develop more
>> items? do you think it worth for this or other releases (if they
>> come)?  Does freevo skin work for freevo 2?  Is this the right place
>> to do this? Is it too late? ....
>>
>> I play freevo 1.9.2 in an Ubuntu 12.04 system. (installed from
>> repository, of course).
>>
>>
>> Regards. Pablo33
>>
>>
>>  
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Freevo-devel mailing list
>> Fre...@li...
>> <mailto:Fre...@li...>
>> https://lists.sourceforge.net/lists/listinfo/freevo-devel
>
>
> ------------------------------------------------------------------------------
>
>
> _______________________________________________
> Freevo-devel mailing list
> Fre...@li...
> https://lists.sourceforge.net/lists/listinfo/freevo-devel

Re: [Freevo-devel] How about another SKIN

[Maciej U. <ma...@ur...>]

Hi Pablo,

Couple of years ago I wrote the new skin mimicking xbmc. It's a high resolution skin meant to work in 16:9 mode. You can find it on a branch of 1.9.2 in GitHub. It's fully functional and mostly complete. I have extended the original skin rendering code to cope wuth some new functionalities I have introduced.

You can play with it to your heart's content :-) 

There are most likely bugs and some additional work can be done. 

It has never been merged into the main trunk of 1.9.2

Cheers,
Maciej

Sent from my iPhone


On 02.04.2014, at 21:10, Pablo Casas <pca...@gm...> wrote:

> Hi, I'm Pablo33, and this is my first message.
> 
> I know that it is no much activity in freevo, but I prefer to write this than shut up forever: I have started to create a new skin.
> 
> There are many questions rounding my head, it may be a bit late for this. Well, I'll go on and if you think its a good skin you can include it in later releases or may publish to other freevo 1.9 users.
> 
> 
> I've read freevo wiki "http://www.freevo.org/wiki/1.x/Skins.html" and tried to understand the structure. Even I started learning a bit     of python a month ago, but for my surprise skins definitions are in an XML file XDD .
> 
> I've uploaded the files into a compressed archive, so you can take a look.
> link to the file
> 
> 
> Although base resolution for skins is 800x600, the skin is intended to fit only into full HD resolution, so my base resolution is 1920x1080.
> I started to draw a set of icons, in high resolution (maybe too high). (they are mixed with a set of icons that already were there)
> 
> More or less everything it's working properly, the folder_game.png-icon doesn't work (and I don't know why).
> 
> I don't know where to change other icons, such web_radio.  No idea for now, i've seen an image-file in folder "/icons/themes/" but ... it shows invisible in freevo menu.
> 
> Other issues are: I can't see other icons in action. For example: CD-DVD player doesn't work for me, and I haven't TV card too. And I have no idea of the "freevo-icon scope" ¿how many icons does freevo use? ¿which ones? from now I've started from a theme set.
> 
> Well, can I wait for same light or help to test and develop more items? do you think it worth for this or other releases (if they come)?  Does freevo skin work for freevo 2?  Is this the right place to do this? Is it too late? ....
> 
> I play freevo 1.9.2 in an Ubuntu 12.04 system. (installed from repository, of course).
> 
> 
> Regards. Pablo33
> 
> 
>  
> ------------------------------------------------------------------------------
> _______________________________________________
> Freevo-devel mailing list
> Fre...@li...
> https://lists.sourceforge.net/lists/listinfo/freevo-devel