I have been frustrated this weekend trying to find a solution to a problem that has only recently occurred accessing some digitised VCR tapes that had been archived on an external HDD. These are files that played back fine on my Quicksilver after I had recorded them, but now give a «Movie Not Available» message in Quicktime. However when opened in VLC I get a debug message box with the following information posted below. Any clues as to what might be the problem?
I recorded the files from my VCR using an ADVC-100 DA converter over firewire into BTV Pro which created .mov files (DV-PAL). When I try to open the files in BTV Pro, I get a message box «There was an error opening the movie. No Movie found. Error code 20,-2048» Did a search for this error and -2048 appears to be a Quicktime error, so am wondering if there is a problem with my installation of Quicktime. I have got all the usual suspects in stalled, Flip4Mac, Perian, VLC. Mpeg Streamclip but can’t get the file to open. The external HDD is Mac formatted but I found some info about problems with missing resource forks in older .mov files causing problems if copied to NTFS HDD’s.
Any ideas as to where to look next will be appreciated.
+main debug: CPU has capabilities AltiVec FPU+
+main debug: looking for memcpy module: 2 candidates+
+main debug: using memcpy module «memcpyaltivec»+
+main debug: thread started+
+main debug: thread 26421248 (Interaction control) created at priority 0 (../../src/interface/interaction.c:382)+
+main debug: Creating an input for ‘Media Library’+
+main debug: Input is a meta file: disabling unneeded options+
+main debug: `file/xspf-open:///Users/irdesigns/Library/Preferences/VLC/ml.xspf’ gives access `file’ demux `xspf-open’ path `/Users/irdesigns/Library/Preferences/VLC/ml.xspf’+
+main debug: creating access ‘file’ path=’/Users/irdesigns/Library/Preferences/VLC/ml.xspf’+
+main debug: looking for access module: 3 candidates+
+access_file debug: opening file `/Users/irdesigns/Library/Preferences/VLC/ml.xspf’+
+main debug: using access module «access_file»+
+main debug: TIMER module_Need() : 26.549 ms — Total 26.549 ms / 1 intvls (Avg 26.549 ms)+
+main debug: Using AStream*Stream+
+main debug: pre-buffering…+
+main debug: received first data for our buffer+
+main debug: creating demux: access=’file’ demux=’xspf-open’ path=’/Users/irdesigns/Library/Preferences/VLC/ml.xspf’+
+main debug: looking for demux module: 1 candidate+
+playlist debug: using XSPF playlist reader+
+main debug: using demux module «playlist»+
+main debug: TIMER module_Need() : 19.485 ms — Total 19.485 ms / 1 intvls (Avg 19.485 ms)+
+main debug: `file/xspf-open:///Users/irdesigns/Library/Preferences/VLC/ml.xspf’ successfully opened+
+main debug: looking for xml module: 2 candidates+
+main debug: using xml module «xml»+
+main debug: TIMER module_Need() : 99.281 ms — Total 99.281 ms / 1 intvls (Avg 99.281 ms)+
+playlist debug: parsed 0 tracks successfully+
+main debug: removing module «xml»+
+main debug: EOF reached+
+main debug: control type=1+
+main debug: removing module «playlist»+
+main debug: removing module «access_file»+
+main debug: TIMER input launching for ‘Media Library’ : 71.406 ms — Total 71.406 ms / 1 intvls (Avg 71.406 ms)+
+main debug: thread started+
+main debug: waiting for thread initialization+
+main debug: thread 25213440 (preparser) created at priority 0 (../../src/playlist/thread.c:79)+
+main debug: thread started+
+main debug: waiting for thread initialization+
+main debug: thread 26413056 (fetcher) created at priority 0 (../../src/playlist/thread.c:108)+
+main debug: thread started+
+main debug: waiting for thread initialization+
+main debug: rebuilding array of current — root Playlist+
+main debug: rebuild done — 0 items, index -1+
+main debug: thread 26417152 (playlist) created at priority 0 (../../src/playlist/thread.c:117)+
+main debug: looking for interface module: 1 candidate+
+main debug: using interface module «hotkeys»+
+main debug: TIMER module_Need() : 48.316 ms — Total 48.316 ms / 1 intvls (Avg 48.316 ms)+
+main debug: thread started+
+main debug: thread 25212416 (interface) created at priority 0 (../../src/interface/interface.c:168)+
+main debug: looking for interface module: 17 candidates+
+main debug: using interface module «signals»+
+main debug: TIMER module_Need() : 34.354 ms — Total 34.354 ms / 1 intvls (Avg 34.354 ms)+
+main debug: thread started+
+main debug: thread 26470400 (interface) created at priority 0 (../../src/interface/interface.c:168)+
+main: Running vlc with the default interface. Use ‘cvlc’ to use vlc without interface.+
+main debug: looking for interface module: 4 candidates+
+main debug: using interface module «macosx»+
+main debug: TIMER module_Need() : 511.368 ms — Total 511.368 ms / 1 intvls (Avg 511.368 ms)+
+main debug: thread started+
+main debug: thread 26482176 (interface) created at priority 0 (../../src/interface/interface.c:148)+
+main debug: no fetch required for Playlist (art currently (null))+
+main debug: adding item `testing.mov’ ( /Volumes/IR My Book/BTV Videos ƒ/testing.mov )+
+main debug: rebuilding array of current — root Playlist+
+main debug: rebuild done — 1 items, index -1+
+main debug: starting new item+
+main debug: processing request item testing.mov node Playlist skip 0+
+main debug: resyncing on testing.mov+
+main debug: testing.mov is at 0+
+main debug: creating new input thread+
+main debug: Creating an input for ‘testing.mov’+
+main debug: waiting for thread initialization+
+main debug: thread started+
+main debug: thread 26771456 (input) created at priority 22 (../../src/input/input.c:370)+
+main debug: `/Volumes/IR My Book/BTV Videos ƒ/testing.mov’ gives access `’ demux `’ path `/Volumes/IR My Book/BTV Videos ƒ/testing.mov’+
+main debug: creating demux: access=» demux=» path=’/Volumes/IR My Book/BTV Videos ƒ/testing.mov’+
+main debug: looking for access_demux module: 2 candidates+
+main debug: no fetch required for Playlist (art currently (null))+
+macosx debug: input has changed, refreshing interface+
+macosx debug: notification received in VLC with name VLCOSXGUIInit and object VLCEyeTVSupport+
+main debug: no fetch required for Playlist (art currently (null))+
+main debug: TIMER module_Need() : 1288.828 ms — Total 1288.828 ms / 1 intvls (Avg 1288.828 ms)+
+main debug: creating access » path=’/Volumes/IR My Book/BTV Videos ƒ/testing.mov’+
+main debug: looking for access module: 8 candidates+
+vcd debug: trying .cue file: /Volumes/IR My Book/BTV Videos ƒ/testing.cue+
+vcd debug: could not find .cue file+
+access_file debug: opening file `/Volumes/IR My Book/BTV Videos ƒ/testing.mov’+
+main debug: using access module «access_file»+
+main debug: TIMER module_Need() : 110.747 ms — Total 110.747 ms / 1 intvls (Avg 110.747 ms)+
+main debug: Using AStream*Stream+
+main debug: pre-buffering…+
+main debug: received first data for our buffer+
+main debug: pre-buffering done 1408981 bytes in 0s — 9031 kbytes/s+
+main debug: creating demux: access=» demux=» path=’/Volumes/IR My Book/BTV Videos ƒ/testing.mov’+
+main debug: looking for demux module: 59 candidates+
+mp4 debug: found Box: mdat size 32+
+mp4 debug: skip box: «mdat»+
+mp4 debug: found Box: mdat size 18891508192+
+mp4 debug: skip box: «mdat»+
+mp4 debug: dumping root Box «root»+
+mp4 debug: | + mdat size 32+
+mp4 debug: | + mdat size 1711639008+
+mp4 debug: file type box missing (assuming ISO Media file)+
+mp4 error: MP4 plugin discarded (no moov box)+
+avformat debug: detected format: mov,mp4,m4a,3gp,3g2,mj2+
+avformat error: av
uk.lua+
+lua debug: Trying Lua playlist script /Applications/VLC ƒ/VLC.app/Contents/MacOS/share/lua/playlist/break.lua+
+lua debug: Trying Lua playlist script /Applications/VLC ƒ/VLC.app/Contents/MacOS/share/lua/playlist/canalplus.lua+
+lua debug: Trying Lua playlist script /Applications/VLC ƒ/VLC.app/Contents/MacOS/share/lua/playlist/cue.lua+
+lua debug: Trying Lua playlist script /Applications/VLC ƒ/VLC.app/Contents/MacOS/share/lua/playlist/dailymotion.lua+
+lua debug: Trying Lua playlist script /Applications/VLC ƒ/VLC.app/Contents/MacOS/share/lua/playlist/france2.lua+
+lua debug: Trying Lua playlist script /Applications/VLC ƒ/VLC.app/Contents/MacOS/share/lua/playlist/googlevideo.lua+
+lua debug: Trying Lua playlist script /Applications/VLC ƒ/VLC.app/Contents/MacOS/share/lua/playlist/joox.lua+
+lua debug: Trying Lua playlist script /Applications/VLC ƒ/VLC.app/Contents/MacOS/share/lua/playlist/koreus.lua+
+lua debug: Trying Lua playlist script /Applications/VLC ƒ/VLC.app/Contents/MacOS/share/lua/playlist/lelombrik.lua+
+lua debug: Trying Lua playlist script /Applications/VLC ƒ/VLC.app/Contents/MacOS/share/lua/playlist/megavideo.lua+
+lua debug: Trying Lua playlist script /Applications/VLC ƒ/VLC.app/Contents/MacOS/share/lua/playlist/metacafe.lua+
+lua debug: Trying Lua playlist script /Applications/VLC ƒ/VLC.app/Contents/MacOS/share/lua/playlist/youtube.lua+
+lua debug: Trying Lua playlist script /Applications/VLC ƒ/VLC.app/Contents/MacOS/share/lua/playlist/youtube_homepage.lua+
+lua debug: Trying Lua scripts in /Applications/VLC ƒ/VLC.app/Contents/MacOS/share/share/lua/playlist+
+ps error: cannot peek+
+vobsub debug: could not read vobsub IDX file+
+dummy error: unknown command `/Volumes/IR My Book/BTV Videos ƒ/testing.mov’+
+subtitle debug: subtitle demux discarded+
+main warning: no demux module matching «mp4» could be loaded+
+main debug: TIMER module_Need() : 1954.294 ms — Total 1954.294 ms / 1 intvls (Avg 1954.294 ms)+
+main error: no suitable demux module for `/:///Volumes/IR My Book/BTV Videos ƒ/testing.mov’+
+main debug: finished input+
+main debug: dying input+
+main debug: removing module «access_file»+
+main debug: thread ended+
+macosx debug: input has stopped, refreshing interface+
+macosx debug: addition to non-blocking error panel received+
+main debug: dead input+
+main debug: thread 26771456 joined (../../src/playlist/engine.c:244)+
+main debug: TIMER input launching for ‘testing.mov’ : 3573.150 ms — Total 3573.150 ms / 1 intvls (Avg 3573.150 ms)+
+main debug: starting new item+
+main debug: changing item without a request (current 0/1)+
+main debug: nothing to play+
+main debug: no fetch required for Playlist (art currently (null))+
Иногда при попытке открытия каких то файлов с помощью проигрывателя QuickTime появляется ошибка 2048 QuickTime. Эта ошибка QuickTime означает что плеер не смог открыть файл потому, что он его не понимает.
Устранение ошибки 2048
Чтобы плеер смог понимать эти файлы и открывать их, нужно скачать кодеки для QuickTime player и установить их на компьютер. Все эти кодеки для QuickTime Windows есть в K lite codec pack. Скачав этот пак надо запустить установочный файл и установить его на компьютер. После завершения установки нужно перезапустить компьютер. После перезагрузки компьютера у вас на компьютере появится K lite плеер и установятся для QuickTime кодеки. Теперь плеер QuickTime будет без ошибок открывать файлы которые раньше открывались с ошибками.
Если файлы всё равно не открываются тогда это проблема в самих файлах, либо они закачены не до конца либо они были повреждены ещё при создании. В таком случае такие файлы стоит удалить и найти другие с такой же информацией на них.
Read time 7 minutes
Typically, the QuickTime error-2048 flashes on the user’s screen when they play a video file that is either corrupt or incompatible with the QuickTime media player.
Designed and developed by the Apple Corporation, QuickTime media player is very well known for its capability to handle diverse media file (videos, audios and images) formats. Apart from the native format i.e. MOV; it also supports other video containers like MP4, MP3, WAV, etc. However, it must be noted that the QuickTime media player may not necessarily supports the codecs of each of the supported file formats. Many videos have variety of codecs structured within, which makes the files playable in different platforms. It is possible that some of the video codecs are not recognized by the QuickTime player, which in turn leads us to several playback issues like the one we are discussing here. Fortunately, there are solutions to fix incompatibility and corruption issues from videos supported by the QuickTime player.
Reasons Behind QuickTime Error 2048
Not only missing codecs lead to QuickTime error 2048, many other factors also contribute to playback issues like that.
- Header corruption in MOV files
- Inappropriate ejection of external hard drives
- Virus intrusion
- Unreliable compression techniques
- Damaged firmware
- Using other media players to play MOV files
The header of a video file contains information like creation date, file size, last modification date, etc. All these information is required to share the data. If any how the header gets corrupted you will lose access to your file.
Sometimes users remove their external storage devices without ejecting them properly via the Windows controls. An abrupt removal of storage devices often leads to corruption of data.
In case your storage devices are exposed to viruses or malware threat, your files are likely to get corrupted. Virus infection can cause severe corruption issues in files irrespective of the file type or format.
Many users tend to use third-party tools to compress videos so as to reduce the file size. If you are using any random third-party software instead of an authentic one; it can degrade the quality of the file and as a consequent those files may become inaccessible.
If you are trying to access a video recorded by your smartphone’s camcorder and it shows playback issues then there is high possibility that your firmware is damaged or broken.
As we know that MOV is the native format of the QuickTime media player. If you are using other media players to load MOV files, it might make them corrupted or damaged. . Therefore, it is always recommended to use the default application to play MOV videos.
All the reasons mentioned above are the root causes of corruption to MOV files and other video formats supported by the QuickTime player. The reasons for getting “QuickTime error 2048” are quite evident so far. Now it’s time for us to look at the solutions.
Solutions to Fix QuickTime Error 2048
There are manual as well as automated techniques to fix QuickTime error 2048 provided you have the right knowledge to perform the task. In this section, we have elaborated all possible measures to fix the issue. First we will go through the manual solutions and then we will look out for a reliable third-party tool to undo the clutches of this fatal error.
- Convert the video file format
- Launch VLC, click on Media in the Menu bar and select Convert/save option
- Click the +Add button to add files you wish to convert. You can add multiple files in a single conversion cycle.
- Once the required files are added to the conversion list, click on the Convert/Save button.
- Now, in the next window you can choose the output format of your converted videos. Remember to choose only the formats supported by the QuickTime player. Select the desired format, provide a destination path to save the converted file and click Start.
- Download and install the required codecs for your MOV files
- Reinstall QuickTime to fix installation errors
- Try a third-party repair tool to quick fix the error
If you are trying to access a video other than the default one, make sure it is supported by the QuickTime player. In case you have a video that is incompatible with QuickTime, you can change the file extension via a video converter tool. Switch to a QuickTime compatible format and you can easily play you desired videos without any playback issue.
There are a bunch of video converters available online; you can choose any one of the trusted video converters to do the conversion task. However, if you are looking for a straight recommendation, then VLC media player is quite efficient in converting videos to all major file formats. To convert your videos via VLC, follow the steps given below:
Your selected videos get converted to the desired format and are saved to the specified location.
Codecs are an essential part of video files; they are responsible for encoding and decoding streams of digital data and also to make the videos playable on every media player. There is a possibility that the MOV files you are trying to play via QuickTime player lack the appropriate codecs. You need to make sure that the video file contains the appropriate codes supported by the QuickTime player. In order to do so, just right-click on the MOV file, select Properties and click on the Summary tab. Look out for the video and audio codec. Now, take help from the Google and check whether those codecs are appropriate for QuickTime. If not, look for appropriate codec packs available on the net.
If something went wrong during the installation, you might also end up with certain playback issues. Try reinstalling the QuickTime player and check whether the error still persists or not.
You can always rely on reliable third-party tools to fix corruption and bugs in your videos. Though the quest for online search takes a lot of time and effort, but getting an appropriate repair tool would definitely save the day. We have also highlighted one such tool that is used and recommended by a lot of users worldwide i.e. the Kernel Video Repair tool.
The Kernel Video Repair tool repairs your corrupt or damaged videos irrespective of the file type and size. You can repair MP4, MOV, MPEG, MKV, FLV, 3GP, F4V and many other file formats with this software. Moreover, the tool works exceptionally well in almost all versions of Windows Operating system. Here is how the default interface of Kernel Video Repair looks when you first launch the application.
Final Words
We have discussed almost every measure to tackle the QuickTime error 2048 situation. However, if the manual methods do not work, it is recommended to use third-party software like Kernel Video Repair to get the issue sorted as quickly.
I have been frustrated this weekend trying to find a solution to a problem that has only recently occurred accessing some digitised VCR tapes that had been archived on an external HDD. These are files that played back fine on my Quicksilver after I had recorded them, but now give a «Movie Not Available» message in Quicktime. However when opened in VLC I get a debug message box with the following information posted below. Any clues as to what might be the problem?
I recorded the files from my VCR using an ADVC-100 DA converter over firewire into BTV Pro which created .mov files (DV-PAL). When I try to open the files in BTV Pro, I get a message box «There was an error opening the movie. No Movie found. Error code 20,-2048» Did a search for this error and -2048 appears to be a Quicktime error, so am wondering if there is a problem with my installation of Quicktime. I have got all the usual suspects in stalled, Flip4Mac, Perian, VLC. Mpeg Streamclip but can’t get the file to open. The external HDD is Mac formatted but I found some info about problems with missing resource forks in older .mov files causing problems if copied to NTFS HDD’s.
Any ideas as to where to look next will be appreciated.
+main debug: CPU has capabilities AltiVec FPU+
+main debug: looking for memcpy module: 2 candidates+
+main debug: using memcpy module «memcpyaltivec»+
+main debug: thread started+
+main debug: thread 26421248 (Interaction control) created at priority 0 (../../src/interface/interaction.c:382)+
+main debug: Creating an input for ‘Media Library’+
+main debug: Input is a meta file: disabling unneeded options+
+main debug: `file/xspf-open:///Users/irdesigns/Library/Preferences/VLC/ml.xspf’ gives access `file’ demux `xspf-open’ path `/Users/irdesigns/Library/Preferences/VLC/ml.xspf’+
+main debug: creating access ‘file’ path=’/Users/irdesigns/Library/Preferences/VLC/ml.xspf’+
+main debug: looking for access module: 3 candidates+
+access_file debug: opening file `/Users/irdesigns/Library/Preferences/VLC/ml.xspf’+
+main debug: using access module «access_file»+
+main debug: TIMER module_Need() : 26.549 ms — Total 26.549 ms / 1 intvls (Avg 26.549 ms)+
+main debug: Using AStream*Stream+
+main debug: pre-buffering…+
+main debug: received first data for our buffer+
+main debug: creating demux: access=’file’ demux=’xspf-open’ path=’/Users/irdesigns/Library/Preferences/VLC/ml.xspf’+
+main debug: looking for demux module: 1 candidate+
+playlist debug: using XSPF playlist reader+
+main debug: using demux module «playlist»+
+main debug: TIMER module_Need() : 19.485 ms — Total 19.485 ms / 1 intvls (Avg 19.485 ms)+
+main debug: `file/xspf-open:///Users/irdesigns/Library/Preferences/VLC/ml.xspf’ successfully opened+
+main debug: looking for xml module: 2 candidates+
+main debug: using xml module «xml»+
+main debug: TIMER module_Need() : 99.281 ms — Total 99.281 ms / 1 intvls (Avg 99.281 ms)+
+playlist debug: parsed 0 tracks successfully+
+main debug: removing module «xml»+
+main debug: EOF reached+
+main debug: control type=1+
+main debug: removing module «playlist»+
+main debug: removing module «access_file»+
+main debug: TIMER input launching for ‘Media Library’ : 71.406 ms — Total 71.406 ms / 1 intvls (Avg 71.406 ms)+
+main debug: thread started+
+main debug: waiting for thread initialization+
+main debug: thread 25213440 (preparser) created at priority 0 (../../src/playlist/thread.c:79)+
+main debug: thread started+
+main debug: waiting for thread initialization+
+main debug: thread 26413056 (fetcher) created at priority 0 (../../src/playlist/thread.c:108)+
+main debug: thread started+
+main debug: waiting for thread initialization+
+main debug: rebuilding array of current — root Playlist+
+main debug: rebuild done — 0 items, index -1+
+main debug: thread 26417152 (playlist) created at priority 0 (../../src/playlist/thread.c:117)+
+main debug: looking for interface module: 1 candidate+
+main debug: using interface module «hotkeys»+
+main debug: TIMER module_Need() : 48.316 ms — Total 48.316 ms / 1 intvls (Avg 48.316 ms)+
+main debug: thread started+
+main debug: thread 25212416 (interface) created at priority 0 (../../src/interface/interface.c:168)+
+main debug: looking for interface module: 17 candidates+
+main debug: using interface module «signals»+
+main debug: TIMER module_Need() : 34.354 ms — Total 34.354 ms / 1 intvls (Avg 34.354 ms)+
+main debug: thread started+
+main debug: thread 26470400 (interface) created at priority 0 (../../src/interface/interface.c:168)+
+main: Running vlc with the default interface. Use ‘cvlc’ to use vlc without interface.+
+main debug: looking for interface module: 4 candidates+
+main debug: using interface module «macosx»+
+main debug: TIMER module_Need() : 511.368 ms — Total 511.368 ms / 1 intvls (Avg 511.368 ms)+
+main debug: thread started+
+main debug: thread 26482176 (interface) created at priority 0 (../../src/interface/interface.c:148)+
+main debug: no fetch required for Playlist (art currently (null))+
+main debug: adding item `testing.mov’ ( /Volumes/IR My Book/BTV Videos ƒ/testing.mov )+
+main debug: rebuilding array of current — root Playlist+
+main debug: rebuild done — 1 items, index -1+
+main debug: starting new item+
+main debug: processing request item testing.mov node Playlist skip 0+
+main debug: resyncing on testing.mov+
+main debug: testing.mov is at 0+
+main debug: creating new input thread+
+main debug: Creating an input for ‘testing.mov’+
+main debug: waiting for thread initialization+
+main debug: thread started+
+main debug: thread 26771456 (input) created at priority 22 (../../src/input/input.c:370)+
+main debug: `/Volumes/IR My Book/BTV Videos ƒ/testing.mov’ gives access `’ demux `’ path `/Volumes/IR My Book/BTV Videos ƒ/testing.mov’+
+main debug: creating demux: access=» demux=» path=’/Volumes/IR My Book/BTV Videos ƒ/testing.mov’+
+main debug: looking for access_demux module: 2 candidates+
+main debug: no fetch required for Playlist (art currently (null))+
+macosx debug: input has changed, refreshing interface+
+macosx debug: notification received in VLC with name VLCOSXGUIInit and object VLCEyeTVSupport+
+main debug: no fetch required for Playlist (art currently (null))+
+main debug: TIMER module_Need() : 1288.828 ms — Total 1288.828 ms / 1 intvls (Avg 1288.828 ms)+
+main debug: creating access » path=’/Volumes/IR My Book/BTV Videos ƒ/testing.mov’+
+main debug: looking for access module: 8 candidates+
+vcd debug: trying .cue file: /Volumes/IR My Book/BTV Videos ƒ/testing.cue+
+vcd debug: could not find .cue file+
+access_file debug: opening file `/Volumes/IR My Book/BTV Videos ƒ/testing.mov’+
+main debug: using access module «access_file»+
+main debug: TIMER module_Need() : 110.747 ms — Total 110.747 ms / 1 intvls (Avg 110.747 ms)+
+main debug: Using AStream*Stream+
+main debug: pre-buffering…+
+main debug: received first data for our buffer+
+main debug: pre-buffering done 1408981 bytes in 0s — 9031 kbytes/s+
+main debug: creating demux: access=» demux=» path=’/Volumes/IR My Book/BTV Videos ƒ/testing.mov’+
+main debug: looking for demux module: 59 candidates+
+mp4 debug: found Box: mdat size 32+
+mp4 debug: skip box: «mdat»+
+mp4 debug: found Box: mdat size 18891508192+
+mp4 debug: skip box: «mdat»+
+mp4 debug: dumping root Box «root»+
+mp4 debug: | + mdat size 32+
+mp4 debug: | + mdat size 1711639008+
+mp4 debug: file type box missing (assuming ISO Media file)+
+mp4 error: MP4 plugin discarded (no moov box)+
+avformat debug: detected format: mov,mp4,m4a,3gp,3g2,mj2+
+avformat error: av
open_input
stream failed+
+lua debug: Trying Lua scripts in /Users/irdesigns/Library/Preferences/VLC/lua/playlist+
+lua debug: Trying Lua scripts in /Applications/VLC ƒ/VLC.app/Contents/MacOS/share/lua/playlist+
+lua debug: Trying Lua playlist script /Applications/VLC ƒ/VLC.app/Contents/MacOS/share/lua/playlist/anevia_streams.lua+
+lua debug: Trying Lua playlist script /Applications/VLC ƒ/VLC.app/Contents/MacOS/share/lua/playlist/appletrailers.lua+
+lua debug: Trying Lua playlist script /Applications/VLC ƒ/VLC.app/Contents/MacOS/share/lua/playlist/bbc
co
uk.lua+
+lua debug: Trying Lua playlist script /Applications/VLC ƒ/VLC.app/Contents/MacOS/share/lua/playlist/break.lua+
+lua debug: Trying Lua playlist script /Applications/VLC ƒ/VLC.app/Contents/MacOS/share/lua/playlist/canalplus.lua+
+lua debug: Trying Lua playlist script /Applications/VLC ƒ/VLC.app/Contents/MacOS/share/lua/playlist/cue.lua+
+lua debug: Trying Lua playlist script /Applications/VLC ƒ/VLC.app/Contents/MacOS/share/lua/playlist/dailymotion.lua+
+lua debug: Trying Lua playlist script /Applications/VLC ƒ/VLC.app/Contents/MacOS/share/lua/playlist/france2.lua+
+lua debug: Trying Lua playlist script /Applications/VLC ƒ/VLC.app/Contents/MacOS/share/lua/playlist/googlevideo.lua+
+lua debug: Trying Lua playlist script /Applications/VLC ƒ/VLC.app/Contents/MacOS/share/lua/playlist/joox.lua+
+lua debug: Trying Lua playlist script /Applications/VLC ƒ/VLC.app/Contents/MacOS/share/lua/playlist/koreus.lua+
+lua debug: Trying Lua playlist script /Applications/VLC ƒ/VLC.app/Contents/MacOS/share/lua/playlist/lelombrik.lua+
+lua debug: Trying Lua playlist script /Applications/VLC ƒ/VLC.app/Contents/MacOS/share/lua/playlist/megavideo.lua+
+lua debug: Trying Lua playlist script /Applications/VLC ƒ/VLC.app/Contents/MacOS/share/lua/playlist/metacafe.lua+
+lua debug: Trying Lua playlist script /Applications/VLC ƒ/VLC.app/Contents/MacOS/share/lua/playlist/youtube.lua+
+lua debug: Trying Lua playlist script /Applications/VLC ƒ/VLC.app/Contents/MacOS/share/lua/playlist/youtube_homepage.lua+
+lua debug: Trying Lua scripts in /Applications/VLC ƒ/VLC.app/Contents/MacOS/share/share/lua/playlist+
+ps error: cannot peek+
+vobsub debug: could not read vobsub IDX file+
+dummy error: unknown command `/Volumes/IR My Book/BTV Videos ƒ/testing.mov’+
+subtitle debug: subtitle demux discarded+
+main warning: no demux module matching «mp4» could be loaded+
+main debug: TIMER module_Need() : 1954.294 ms — Total 1954.294 ms / 1 intvls (Avg 1954.294 ms)+
+main error: no suitable demux module for `/:///Volumes/IR My Book/BTV Videos ƒ/testing.mov’+
+main debug: finished input+
+main debug: dying input+
+main debug: removing module «access_file»+
+main debug: thread ended+
+macosx debug: input has stopped, refreshing interface+
+macosx debug: addition to non-blocking error panel received+
+main debug: dead input+
+main debug: thread 26771456 joined (../../src/playlist/engine.c:244)+
+main debug: TIMER input launching for ‘testing.mov’ : 3573.150 ms — Total 3573.150 ms / 1 intvls (Avg 3573.150 ms)+
+main debug: starting new item+
+main debug: changing item without a request (current 0/1)+
+main debug: nothing to play+
+main debug: no fetch required for Playlist (art currently (null))+
Error2048 is a pretty discouraging and disheartening message for QuickTime users. But you shouldn’t worry about it as we can help you overcome it without much trouble.
The solutions provided in this article can fix QuickTime error 2048 conveniently, and you use the application smoothly.
As you already know, QuickTime is a popular media player among macOS users, and it is developed by Apple. It can handle a large range of file formats related to videos, images, and pictures.
Because of that, many individuals tend to rely on this player as their prominent tool. So, when you come across QuickTime error 2048, that can make you frustrated a lot.
But if you follow the steps below, you can fix this issue easily and use the player as usual.
Part 1: Introduction to QuickTime Error 2048
First, let’s take a look at the nature of error 2048. That will give you a better idea about the error before finding solutions to it.
01. What is Error 2048 on QuickTime?
In fact, error2048 appears on QuickTime when it cannot locate the movie atoms on the respective media file. If the QuickTime player can locate media data but not the movie atom, error 2048 can appear. The error will appear with a message starting with the text “Error-2048…..“.
What is the Reason Behind Error 2048?
Well, there are several reasons behind this error. Listed below are those reasons for your reference.
- It can appear as a result of an incomplete or interrupted file transfer. Such instances can appear due to an unexpected shutdown, removing the storage device, or even poor network connection.
- Using the wrong set of codecs.
- Corrupted firmware on your recording device that led to a damaged video output.
- Your QuickTime Player is installed improperly, or the file is corrupted.
- Your media file header is corrupted or damaged, and the QuickTime player cannot read the file.
- Malware or virus infection on your computer.
- A wrongful conversion process.
Part 2: Possible Solutions You Can Use to Fix Error 2048
Now that you have substantial knowledge pertaining to QuickTime error 2048. let’s learn how to fix it. As we believe, at least one solution will help you address this situation successfully.
Solution 01: Use a Professional Third-party Tool to Fix It
The first solution is to try a professional tool that is designed to repair such errors. In this case, the most recommended solution is Wondershare Repairit Video Repair.
Thankfully, Wondershare Repairit can easily fix errors related to file formats, including AVI, MOV, FLV, 3GP, etc.
This special application comes with excellent user-friendliness. Even if you are a novice user, you can make use of this app without any issue. It comes with two repair modes called “Quick” and “Advanced.”
For many users, the Quick Repair mode works perfectly. However, if the videos are severely damaged, you can use “Advanced” mode.
You Can Make Use of Wondershare Repairit to Fix Videos That Relate to the Following Instances.
- The video frame and the video slider are corrupted.
- If your video has an interrupted playback possible with a jerky playback as well.
- Your video file system is badly corrupt.
- The video doesn’t play, and it doesn’t even load.
- Your videos are unacceptably blurry, grainy, or flickering.
With that said, let’s learn how to fix this error2048 issue for good using Wondershare Repairit.
● Add the Faulty Video to Wondershare Repairit.
As the first step, you should add the faulty video into the Wondershare Repairit interface.
● Proceed with Quick Repair
As the next step, you should start to repair the video. In this case, please click on the button labeled “Repair” to proceed. Repairit will begin to repair the respective video without needing your effort.
● Wait Patiently
Now, you are supposed to click on the triangular icon so you can preview the repaired video. For many videos, this method works perfectly, and it will not take much time. However, if you have a seriously corrupted video file, you are supposed to use the “Advanced Repair” mode.
● Add Your Video to Repair with the “Advanced Repair” Mode
If you have a severely damaged video, you should switch to Advanced Repair mode. All you need is to click on the option called “Advanced Repair.” It will display a popup window as well.
Then, you should browse and select the sample file for the purpose of repairing the badly damaged video. After that, please click on the option called “Repair.”
- At the completion of the process, you will be notified. You should just press the button labeled “Save” and define a location to save the file.
That’s it. This method should work with any media file with Quicktime error 2048, even if it is damaged severely.
Solution 02: Fix QuickTime Error 2048 with Perian
You are supposed to have codecs in order to play video files on the devices. Therefore, in the absence of codecs, you will experience various problems related to videos, including error2048. In this case, we suggest you use a special tool called Perian, which is an open-source plugin.
- To proceed with this solution, you should download the Perian codec.
- Then, double-click on the respective icon so the components will be installed for QuickTime.
- Drag and drop your QuickTime components from your library to Perian using its interface.
- You can now restart the programs that use QuickTime. Copy the component file from Perian and launch the faulty media file to fix the error2048 issue.
Part 3: Fix QuickTime Error 2048 by Opening Corrupt Files
There are several methods to open potentially corrupted files on the QuickTime player. Mentioned below is how to do that.
01. Scan Your System Using a Good Antivirus Program
Be sure that you have a good antivirus program installed on your system and update it regularly. Also, you must be smart enough to scan your computer regularly so the risk of viruses will be reduced.
In addition to that, you must configure your system settings so they will get updated automatically. That will save you plenty of time as well. When the system updates automatically, you don’t have to look for it manually and waste your time.
Mentioned below is how you should set the system to update automatically.
- In macOS, you should go to “Apple Menu” and choose “System Preferences” to proceed. Then, please go to the “Software Update” option.
- After that, you should tap on the box located next to “Automatically keep my Mac up to date.” If you see an antivirus program that requires an update, choose “Update Now” and install it.
02. Update Your QuickTime Player
The next option is to update your QuickTime player. In fact, an outdated QuickTime player may be incompatible with some of the files, so updating is inevitable. Please follow below simple steps and update QuickTime Player.
- First, you should launch your QuickTime player and go to the “Help” option to proceed.
- Then, choose the option called “Update Existing Software.” You will see a new window now. It says, “Apple Software updates are available for your computer. Would you like to update now?“. You can uncheck the updates for other programs and move to the next step.
- Click on the option called “Install 1 Item“. After accepting the license agreement, click OK.
- Now, you should wait for a couple of moments so the updating will take place.
- Relaunch QuickTime Player to see if the error2048 issue is gone.
03. Convert Files into a Different Format
If none of the options have worked so far, there can be something wrong with the video file format. If that’s the case, you can simply convert the respective file into a different format. You can accomplish this task simply by using the VLC media player.
- Open the VLC media player and choose “Media.”
- Then, select the “Convert/Save” option.
- Choose “Open Media” and go to the option called “Add.” You can now add the MOV file that doesn’t work with QuickTime.
- Click on the “Convert or Save” option to proceed.
- You can now go to “Settings” and choose “Convert.”
- Choose a location to save the file and click on the button labeled “Start.”
04. Restart QuickTime Player
If you are yet to succeed, it could be due to an error associated with QuickTime Player itself. In this case, you should uninstall the player and see if it works.
- Go to the “Start” menu of your computer and launch “Control Panel.”
- Go to “Programs” and choose “Uninstall a Program.”
- Perform a right-click on “QuickTime Player” and choose “Uninstall.”
- Now, you are supposed to click on “Yes” so you can confirm the uninstallation.
- That’s it. Download QuickTime player once again and see if you can play the respective file.
Part 4: What Should You Know About QuickTime Player
Now, let’s pay attention to some important points related to QuickTime Player. Also, we explain some points that can prevent videos from corrupting. Such points are essential, so you can avoid issues like QuickTime error 2048.
01. The Functionality of QuickTime Player
In general, QuickTime Player supports the MOV format. But it is compatible with other popular file formats that fall into MPEG-2 and MPEG-4 standards. Besides, QuickTime Player also supports WAV, AIFF, and several other formats.
This player can be installed on the Windows platform as well. It can even record videos from iPhones, iPads, digital cameras, etc. Moreover, it is versatile enough to record macOS screens as well.
02. Preventing Video Corruption
Here are some precautions you can consider to avoid potential video corruption.
● Compress Your Video Files Properly.
When you compress video files, be sure to use proper tools and methods so no errors will occur.
● Install an Effective Antivirus Program
Make sure that your computer system is protected with a powerful antivirus. Some of the viruses can damage video files or even the player and lead to various errors.
● Prevent from Converting Videos Unnecessarily
Make sure that you convert videos only if it is mandatory. When you convert videos, some codec-related errors can occur, so it is best not to convert them.
● Transfer the Files Properly
Make sure that you transfer the files properly without interruptions. Otherwise, files tend to get damaged and show various errors.
● Always Keep a Backup of Your Data
Backup of your video files. Even if one copy gets corrupted, you can make use of the other.
Well, just try the above solutions if you experience QuickTime error 2048. If you have other doubts related to error 2048, you may let us know.