Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error al cargar video de fondo #82

Closed
Dazmed707 opened this issue Dec 21, 2018 · 10 comments
Closed

Error al cargar video de fondo #82

Dazmed707 opened this issue Dec 21, 2018 · 10 comments

Comments

@Dazmed707
Copy link

Siempre se queda en "Espere que se copie el video", tarda demasiado y hay que cancelar, este error es en 2019.0 la última nightly

@berry120
Copy link
Member

Can you fire up Quelea, reproduce the issue then send on the debug log (https://quelea-projection.github.io/docs/Debug_log) so we can have a look?

@Dazmed707 Dazmed707 changed the title Error al cargar video de fono Error al cargar video de fondo Dec 22, 2018
@Dazmed707
Copy link
Author

bug1
siempre se queda ahí, cancelo y no aparece el video, no carga nada
quelea-debuglog.txt

@berry120
Copy link
Member

Afraid I can't seem to reproduce this. Does it happen with all video files or just some? It could be that you're trying to use a particularly large video file that's taking a long time to copy over?

@Dazmed707
Copy link
Author

Me pasa en mi laptop y en la pc de la iglesia, tuve que volver a 2018.1 para el servicio ahi el video todo bien.
este es el link de uno de los videos que trato de usar en la última noche, en 2018.1 carga normalmente.
https://drive.google.com/open?id=1MtBiBq_KZjhwxoLmHgHsX28_sroLYZyf

Al cargar el vídeo de acá, no se puede previsualizar el vídeo, nosé si sea por el formato. si reproduce en el 2 monitor pero en quelea no se puede previsualizar.
https://drive.google.com/open?id=130ZirS8J6x3ZJ0HYSptdBPQV3M_G3LR0
bugpre1
bugpre22
bug pre2

@Dazmed707
Copy link
Author

Porque no pedir al usuario si desea copiar el video o desea reproducir de la ruta original, así se ahorraría incluso espacio en disco.

@ArvidNy
Copy link
Member

ArvidNy commented Jan 4, 2019

Just tried to reproduce this and I got the following error:

java.lang.NoSuchMethodError: java.nio.ByteBuffer.flip()Ljava/nio/ByteBuffer;
	at org.quelea.windows.newsong.VideoButton.copyFile(VideoButton.java:143)
	at org.quelea.windows.newsong.VideoButton.access$300(VideoButton.java:50)
	at org.quelea.windows.newsong.VideoButton$1$1.run(VideoButton.java:87)

Just changing the copyFile method to something like the code below resolved it. Any reasons why the approach with the .flip() method is better, @berry120?

try (InputStream is = new FileInputStream(new File(in)); OutputStream os = new FileOutputStream(new File(out))) {
            byte[] buffer = new byte[4096];
            int length;
            while ((length = is.read(buffer)) > 0) {
                os.write(buffer, 0, length);
            }
        }

berry120 added a commit that referenced this issue Jan 4, 2019
@berry120
Copy link
Member

berry120 commented Jan 4, 2019

Ah, if that's the issue then it should be resolved by the above commit - see here for an identical problem: plasma-umass/doppio#497

(Long story short, it's Java 9 incompatibilities again, and I think Travis is still building with 9.)

@ArvidNy
Copy link
Member

ArvidNy commented Jan 4, 2019

That seems to have resolved it, but feel free to open it again @Cyb3rG0D7 if you still experience issues.

@ArvidNy ArvidNy closed this as completed Jan 4, 2019
@berry120
Copy link
Member

berry120 commented Jan 4, 2019

@ArvidNy To elaborate on why we're using buffers / the nio library in general - it (on all major systems) makes direct calls to the OS to copy / manipulate files. This makes it a lot faster than the old io approach, where bytes were read from a file into the VM, then back out to another file chunk by chunk.

It's just a performance increase. There's no functional difference apart from that, but I'd like to avoid slowing things down if possible 👍

@Dazmed707
Copy link
Author

Gracias amigos, en la noche actualizo y lo usaré con la corrección del error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants