Write-protecting the installation (and launch shortcut) should mitigate the problem somewhat.
+ Reply to Thread
Results 1,861 to 1,874 of 1874
I know that you have been withdrawn for some time, but unfortunately I find no reasonable replacement for their DVDslideshowGUI 0.9.5.4.
It is a program which is easy to use and delivers first-class results.
If they could eliminate 1 error and 2 things could retrofit it would be class.
The error is always noticeable when I want to process larger picture collections, then from about 3 minutes only a black screen is shown and the sound is a high fluctuating tone.
This happens to me whenever I have 50, 80 120 ... pictures in a slide show.
The file size per image is about 5-6 MB or 3000 x 4000 pixels, or more if it is a newer camera.
The two things that should perhaps be upgraded are output resolutions of 4k (4096 x x2160 pixels) and possibly 8K (7680 × 4320 pixels) support.
This should be prepared for the future.
If you are not interested in further developing this, you may need to consider the sources and documents in the web so that interested people can develop it further.
It would be too bad if this program would not be continued.
Thank you very much for your work and the hope of further development
DSG installs Avisynth, which I don't recall unfortunately.
If it creates a separate Avisynth installation under C:\Program Files[...] that is also visible in Control Panel Programs and Features, you should be able to simply upgrade that with the latest Avisynth installation.
Otherwise, you have a couple of options you could work through by trial and error:
- Install the latest Avisynth and test whether DSG picks that version up (e.g. insert/overlay/etc. the Avisynth Version() filter somewhere in a test project)
- Deleting the DSG Avisynth installation and testing that it picks up your installation
- Replacing the DSG-installed Avisynth files with the ones you installed or by manually extracting the Avisynth distribution
In the last two cases you may need to pay attention to potential DSG-specific files it may have placed in its Avisynth installation.
Hopefully someone with more recent experience of this can confirm which is the simplest route to take.
Audio File - automatic slide change beep detect
When converting an old slide show from slides and audio tape. It is a long task, to manually find all the slide change beeps, note their time. And then convert the slides to images, and match them up.
The slide conversion can be done. The audio conversion from analogue to digital can be done.
But there is a lot of time spent measuring the times that the slide change beeps happen at, figuring out the actual duration time for each slide, and then checking for cumulative errors progressively through the project time-line.
DSG (version 0.65) uses a time for each slide. It does not seem to use a time on a time-line, or "total time so far" method for a time base.
So there is no timeline for images and video, to sync with the audio, which means manual check and playing is required to make things match up.
Some questions that if not possible, are then requests for features.
A sync method that uses a timeline, would allow applying time stamps to the audio track, and then match the images with the time stamps.
Is it possible to have some way to detect the beeps in old slide show audio tracks?
And is it possible to set up tabs or time locations that slide changes or transitions can be matched/synchronised with?
Rendering the libraries for Transitions and Effects - "failure at line 1"
Using DSG version 0.9.5.4, on Wine in Ubuntu 10.04.
When rendering the libraries for Transitions and for Effects, there is a "failure at line 1" error.
This may be due to Wine on Linux, but in any case, the entire rendering process is gone through,
only to report at the end that an error happened at line 1.
If an error happens at line 1, then can the rendering process be stopped immediately at that point.
The rendering process can take quite a long time, and being able to stop at the start, rather than the end would save time.
If there are certain transitions and effects that commonly cause problems, then they might be able to be grouped, as might popular ones.
This would allow a prioritisation of transitions and effects, so that the most useful get rendered first, then then rest of the good ones, then attempt to render the more risky ones.
That way, at least some of the transitions and effects can be rendered in the libraries.
Also if there is difficulty rendering the transitions and effects, then they might also cause problems (don't know, but it may be the case) when actually rendering the project, or burning to disk.
The popular transitions and effects, could even be pre rendered and come with the program ready to use.
So there would then be the option to "Render additional " Transitions and Effects.
There could also be a method to add more, or create your own and use them.
When somebody makes a new one, they can upload it to the web site, for everybody to share.
Time Line for Audio - Vertical Presentation
The Audio could be displayed as a waveform. Normally in audio editors the waveform, is displayed horizontally from left to right. But the layout in DSG is vertical top to bottom.
So the audio waveform could also be presented vertically in this way, possibly to the left of the slides, with the timeline at the very left.
The slides can then be matched to the waveform.
If the slides are matched to the wave form in time, then slides that have short durations will have a short portion of the waveform displayed alongside them.
The slides that have long durations will have a long portion of waveform displayed along side them, so there might be a wider gap between one slide at the next.
The waveform size could have a scaling to best match the slide image size on the time line.
Another pictorial form of representing the sound is the frequency spectrum plot verses time, and this could also be an option.
The sound track could be edited by use of an external sound editor much the same as the other external applications (for example using "Audacity" sound editor, or 0thers).
The slides transition times, could be selected based on where a "tab" is placed on the timeline, with reference to the audio track, such as the appropriate point of silence, between sentences or music tracks, or on sound events (like drum beat, or sonic code, or beeps).
The sound editor, might be able to be used to automatically identify the potential suitable locations for transitions (such as silence or type of sound), and the user then needs only to chose which locations will be used.
This avoids the need to listen to the sound, and guess the time of the event at which the transition should be (then measure the error of the guess and re-correct - several times).
The timeline scale could have options say for;
a) actual time from start
b) actual frames from start
c) time of slide
d) frames of slide
e) time or frames of transition
f) In the case of synchronisation with music,
there could also be "beats per minute" tempo scale related scale, showing bars/beats.
So the duration of each slide is related to the position in the music.
This would allow an up-tempo version of a sound track to substituted in to the project, the beats automatically found and the slides automatically lined up.
It would also allow for various "takes" of a vocal commentary to be substituted, and similar simplicity of slide synchronisation to be done.
Multiple Audio Tracks
The project management could allow for more than one soundtrack, with each track having its own points of synchronisation with slides.
This would allow for "side by side" comparison of the plays, to assess the best audio visual impact of each.
It would also allow for the cut/paste/swap functions so that the user can edit the best of all audio tracks together.
Multiple slide transition tracks
In the same way as multiple audio tracks, there could also be multiple slide transition tracks.
This would allow the user to do side by side comparisons of the alternative presentations visual impact, and copy/paste/swap between tracks to compile the best compilation.
Having a time line based on the audio track, helps to allow the slides to be placed "at location", without a particular order needing to be defined beforehand.
The slides can be re-ordered anyway. Which slide is used for each sound segment can be decided in any order, but can also be decided independently of the allocation of the time location (or duration).
Sound strips/segments/clips could be associated with slides, so that when a slide is moved, the sound is moved with it, or when the sound is moved the slide is moved with it.
Last edited by MKSnMKS; 23rd Apr 2017 at 19:00. Reason: Expansion on concept
the linked video is no longer available
can you explain me how to rotate pic?
In TDD, you write your unit test first, watch it fail, and then implement code changes until the test passes. Sounds backwards, right? But the code you produce when you use this testing methodology is cleaner and less prone to breaking in the long run https://mlsdev.com.
Last edited by rickmonara; 23rd May 2022 at 03:15.