On and off we have been testing and trying out Airtime 1.6 and 1.6.1. Severals needs we have appear to be resolved in the 1.7 release, so we look forward to that.
one thing is resolution to delete files. We absolutely need that since we are limited in space. There might be solutions to that, like using dropbox or Amazon S3 somehow.
However, i have a question about the stor directory. Does it contain just the mp3's i uploaded or does it represent the shows i aired in the past?
Then there is something else. I prepared 1 hour shows in a single mp3 an ran those back to back, repeating shows every once in a while. It occurred a few times a 2 hour show was put in between, wich worked fine. Lately we had a show/mp3 with a duration of 3:38. When this was to be aired, it didn't. The on air was not lit and the stream was silent, although it showed it was processing the file. Did i run into some limit?
Well, that's it for now. Keep on truckin'.
Kind regards,
Ed
> Hi guys,
>
> On and off we have been testing and trying out Airtime 1.6 and 1.6.1.
> Severals needs we have appear to be resolved in the 1.7 release, so we look
> forward to that.
> one thing is resolution to delete files. We absolutely need that since we
> are limited in space. There might be solutions to that, like using dropbox
> or Amazon S3 somehow.
> However, i have a question about the stor directory. Does it contain just
> the mp3's i uploaded or does it represent the shows i aired in the past?
> Then there is something else. I prepared 1 hour shows in a single mp3 an
> ran those back to back, repeating shows every once in a while. It occurred a
> few times a 2 hour show was put in between, wich worked fine. Lately we had
> a show/mp3 with a duration of 3:38. When this was to be aired, it didn't.
> The on air was not lit and the stream was silent, although it showed it was
> processing the file. Did i run into some limit?
>
> Well, that's it for now. Keep on truckin'.
> Kind regards,
> Ed
>
Sorry about the long wait. The logs do not indicate any problems from that time period...is this problem still persistent in version 1.8.0 (released 2 days ago on the 19th)?