3 ms·

Is there a screensaver version of this? Or a way to turn this into a screensaver?

by barbs 7y ago

egfx 7y ago
Try https://gif.com.ai https://gif.com.ai to turn it into a gif. You can set timing with a bouncing </marquee> tag to make it move from end to end. I’m not aware of any tools to turn gifs into screensavers however. I’m pretty sure they exist though. I made one a little while ago https://imgur.com/7t9svTV https://imgur.com/7t9svTV
- dylan604 7y ago
  That's got to be one of the least efficient suggestion I've read in a long time. GIFs are horrible, except they are awesome. In a 90s sense of awesome. It would be much more efficient to turn it into a proper video.
  - deleted 7y ago
    [deleted]
dylan604 7y ago
Oh my, what is wrong with people?? Or maybe it's just me. I have a PTSD like reaction instead. I was a DVD programmer for 10 years, and every where I looked would be a screen with a DVD player connected doing this. I'm so glad to not be in the shiny round disc business any more.
- lostgame 7y ago
  What was the role of ‘DVD programmer’ like? Could you tell us more?
  - dylan604 7y ago
    Depends on what year you started really. The original DVD burner cost $15k and the blank discs were $50 each but only held 3.95GB of data. The 2nd gen burner dropped to $5k and <$10 discs. The 3rd gen burners came out with the General media. These burners were less than $200 and blank media holding the full 4.95GB of data dropped to less than <$1. General media came with the +R/-R battles, and neither of these formats were compatible with a large portion of existing DVD players. The first software was painful running under NT 4.0. With specialty discs with a large number of individual assets, it was easy to create so many files in a single folder that the system would slow to a crawl, and eventually crash during the muxing stage. You'd start it up again and watch it fly by the files it had already muxed, and then slow down when it got to the new files. It was a glorious day when Win2k comes out, and the same type of project no longer crashes like it did under NT. WinXP was like a gift from heaven. Then, you'd get some challenging programming requests like make a randomized game attempting to not repeat an item until all items have been displayed once. You get it programmed and begin testing in the plethora of consumer DVD players on the market. You then discover that some of the lower cost players don't acutally have the ability to select a random number. Instead, they have a preset list of random numbers starts over every time the player is restarted making it impossible to play the game as requested. You think browser compatibility is a pain, the DVD player/media combinations were insane. Then there was MPEG-2 encoding. Early days required specialty hardware boards in your computer to do real-time encoding. These were in the $20k-$50k systems. High end encoders would allow for 2-pass encoding, but that meant playing the VTR for the first pass, rewinding the tape, and then doing the second pass in real-time. A 2 hour movie would take over 4 hours to encode. Then, if there was a problem with the encode (bitrate/buffer spikes/underflows), you'd have to figure out how to solve it and do the encode a second time. If you had the fancy encoder, you could do segment based encodes so you didn't need the full 4 hours. Mid-2000s, software encoding became viable. Now, you could run 2-pass encodes faster than real-time. Then there were the oddities to deal with like timing was based on a 27MHz clock, so when the software told you there was a problem at time 59265000000, it actually meant 6mins 35secs. No, I'm not scarred by the experience ;-) Edit: I didn't actually answer the question. The role was to take the video/stills/subtitle assets and link them together. Every button on a menu screen had to be programmed to go to a specific spot on the disc. The video/audio/subtitles had to be combined to play together, then when finished told where to go, or stop, or loop, etc. Menu elements had to be placed in the correct section of the disc to that the menu/title buttons on the remote behaved correctly. DVDs had a very defined structure. VTS_01.vob VTS_02.vob makes me shudder when I seem them now.

Is there a screensaver version of this? Or a way to turn this into a screensaver?

by barbs 7y ago

Is there a screensaver version of this? Or a way to turn this into a screensaver?

egfx 7y ago

Try https://gif.com.ai https://gif.com.ai to turn it into a gif. You can set timing with a bouncing </marquee> tag to make it move from end to end. I’m not aware of any tools to turn gifs into screensavers however. I’m pretty sure they exist though. I made one a little while ago https://imgur.com/7t9svTV https://imgur.com/7t9svTV

dylan604 7y ago
That's got to be one of the least efficient suggestion I've read in a long time. GIFs are horrible, except they are awesome. In a 90s sense of awesome. It would be much more efficient to turn it into a proper video.
- deleted 7y ago
  [deleted]

dylan604 7y ago

Oh my, what is wrong with people?? Or maybe it's just me. I have a PTSD like reaction instead. I was a DVD programmer for 10 years, and every where I looked would be a screen with a DVD player connected doing this. I'm so glad to not be in the shiny round disc business any more.

lostgame 7y ago
What was the role of ‘DVD programmer’ like? Could you tell us more?
- dylan604 7y ago
  Depends on what year you started really. The original DVD burner cost $15k and the blank discs were $50 each but only held 3.95GB of data. The 2nd gen burner dropped to $5k and <$10 discs. The 3rd gen burners came out with the General media. These burners were less than $200 and blank media holding the full 4.95GB of data dropped to less than <$1. General media came with the +R/-R battles, and neither of these formats were compatible with a large portion of existing DVD players. The first software was painful running under NT 4.0. With specialty discs with a large number of individual assets, it was easy to create so many files in a single folder that the system would slow to a crawl, and eventually crash during the muxing stage. You'd start it up again and watch it fly by the files it had already muxed, and then slow down when it got to the new files. It was a glorious day when Win2k comes out, and the same type of project no longer crashes like it did under NT. WinXP was like a gift from heaven. Then, you'd get some challenging programming requests like make a randomized game attempting to not repeat an item until all items have been displayed once. You get it programmed and begin testing in the plethora of consumer DVD players on the market. You then discover that some of the lower cost players don't acutally have the ability to select a random number. Instead, they have a preset list of random numbers starts over every time the player is restarted making it impossible to play the game as requested. You think browser compatibility is a pain, the DVD player/media combinations were insane. Then there was MPEG-2 encoding. Early days required specialty hardware boards in your computer to do real-time encoding. These were in the $20k-$50k systems. High end encoders would allow for 2-pass encoding, but that meant playing the VTR for the first pass, rewinding the tape, and then doing the second pass in real-time. A 2 hour movie would take over 4 hours to encode. Then, if there was a problem with the encode (bitrate/buffer spikes/underflows), you'd have to figure out how to solve it and do the encode a second time. If you had the fancy encoder, you could do segment based encodes so you didn't need the full 4 hours. Mid-2000s, software encoding became viable. Now, you could run 2-pass encodes faster than real-time. Then there were the oddities to deal with like timing was based on a 27MHz clock, so when the software told you there was a problem at time 59265000000, it actually meant 6mins 35secs. No, I'm not scarred by the experience ;-) Edit: I didn't actually answer the question. The role was to take the video/stills/subtitle assets and link them together. Every button on a menu screen had to be programmed to go to a specific spot on the disc. The video/audio/subtitles had to be combined to play together, then when finished told where to go, or stop, or loop, etc. Menu elements had to be placed in the correct section of the disc to that the menu/title buttons on the remote behaved correctly. DVDs had a very defined structure. VTS_01.vob VTS_02.vob makes me shudder when I seem them now.