Travel Maps almost always fails on export

matttk escrito el 17.08.AM a las 09:31 horas

I recently got Video Prox X11 from Humble Bundle and I'm pretty shocked about the state of this software. Is it even supported anymore? A program called Travel Maps came with it and seems to do exactly what I've wanted to do for a while now, so I was pretty excited to load it up. However, it doesn't work at all.

What I did is load up a GPX file of cycle route, added some manual points along the way, named everything, changed the animation rate, and set a couple custom icons. Every time I export to video, it gets stuck almost at the very end.

I tried making a fresh project with the GPX file and exporting right away - that works. So I tried doing things one by one. One time when I added all the points (no customisation and no animation change), it actually did export. Every time I added anything else, it stopped working. So I gave up and tried to just do the version with points but no further customisation - doesn't work again.

It usually gets stuck with a small sliver remaining but sometimes gets stuck anywhere between 90% and 100%. I have tried creating a new file each time, to make sure it isn't a problem with my saved file.

Does anybody know what's going on... does this software even work still?

Volver al post

Comentarios

browj2 escrito el 17.08.PM a las 18:50 horas

@johnebaker

I upped the setting to 100, making it very long as I had put durations on the intermediate stops. It, too, seems to be stuck at 95%; I'll let it run.

I'll upload the TM file after the walkies.

John CB

browj2 escrito el 17.08.PM a las 19:38 horas

@johnebaker

Hi John,

Here is the mxgeo file with 2788 points; it did not complete. With a setting of 100, it should be 1m10s, making 2100 images.

I'll reduce the number of points to get just under 2100 to see if that is the limit; number of points < number of images.

John CB

johnebaker escrito el 17.08.PM a las 20:13 horas

@browj2

Hi John

Thanks for the project file - it definitely crashes towards the end - here is my project file, using your GPX file, for you to test.

The only difference is that I did use an Avatar.

John EB

browj2 escrito el 17.08.PM a las 20:29 horas

@johnebaker

I just did three trials with 415 points: 19s29f, 11s13f, 8s16f. All three worked, so it's not a limit of points < images, as far as I can tell.

I tried the same route but with the full number of points, 5184, and it blocked (23s). Tried it again without View following path, and it worked (23s1f).

So, I don't know what exactly it is that blocks it. Perhaps there is a limit of 999 points, but the OP still had a problem.

I think that this is something for Magix to look at.

John CB

browj2 escrito el 17.08.PM a las 20:49 horas

@johnebaker

I actually used an Avatar of:

but it's with the Ultimate Traveler Package

I loaded your file and it exported fine with a duration of 32s. I added a location towards the end, no other changes, exported, froze.

Try adding a location to your file.

John CB

johnebaker escrito el 17.08.PM a las 22:04 horas

@browj2

Hi John

Adding 1 new location to the project file I posted - export froze.

I started a new project:

imported the full GPX file
added 12 locations to give a total of 14 saved the project - export fine
added another location, save, export - fine
added another location, save, export - fine
repeated adding locations 1 at a time until got to 20 in total

I could not make it freeze on export. 😡😡😡

Repeated the steps above closing TM after each export - no freeze.

Whatever it is causing the issue, once triggered the project file appears to be no good - it freezes on export, whether TM is restarted or not.

Bug report time.

John EB

matttk escrito el 18.08.AM a las 09:17 horas

Thanks a lot for looking into this, guys. I'm very impressed with the responsive community here. Do the developers read these forums or is it up to the community to somehow submit a bug report?

shgrude escrito el 18.08.AM a las 09:37 horas

@matttk

It is still up to you as a user (who discovered the error) to submit the bug report. However, when the problem are discussed and clarified here in the forum, it may end up with several users submitting a report, which might cause Magix finding the error more important to fix?

You should not expect developers to read here - it is a user-to-user forum, but I will not be supprised if there are Magix employees "lurkin around".