File type info has nothing to do with the computer system itself. It is the same on all systems. It is information about the file, not the system.
Ha? Container?
Yes, container 
Shipping the import and export, export and import is loading and saving to, in cubase.
So some definitions, you can use to describe this.
A little bit offtopic, this works with what they call “namespace”
Every folder gets a lable from a container, on the hard drive, and every folder have his own namespace.
So 1 partition on a computer, with all this containers on the harddrive, the format, in windows NTFS, creates this system with the namespace.
In C++ and C# is namespace very important, because different programmers are writting a program.
Just like you can not have 2 files with the same name in 1 folder, because that is a collision.
In orher words, it was a bit off topic, but i understand what you mean.
I hope Andy can get it, so he can create his video with the good sound, i do not how much time he has, but i think he wants to have his video done as fast as possible.
(i did very much video editing the last vew years …)
That is why i can do this the other way around and are not importing video files in Cubase.
Of course, that is for everyone free, but with a good video editor, you do not need this video track in Cubase.
I’m out here …
1 Like
That is too general. Video playback is working fine for some. So it’s too easy to say it is Cubase 13. But I agree that something has changed in Cubase 13.
@Googly_Smythe has a valid point to mention the hardware acceleration for video playback. So maybe a new graphics card could solve the issue.
Yes, that can be the issue, every hardware configuration can show different behavior, and then it is driver level.
And then, it happends in Cubase, that is for sure, and people that can use this video tracks with a acceptable quality, maby they build the system with more knowledge about the things @Googly_Smythe is writting about, because if you want to be busy with that level, you must gather information about your own system.
For system information in Windows, offcourse you can see in msinfo.exe in the system32 folder.
But, i realy do not know how Andy is using computers, and what his level is, besites Cubase 13 pro, wich is a wonderfull program to, in many aspects.
If it runs stable and do what you want… but that counts for every computer program.
Maby Andy can read this site to.
Good luck.
Since I replaced my 6700 XT GPU with a 7900 XTX I haven’t been able to play videos, as extensively ranted on by moi.
Today I found a solution that works for my system: i9 12900, AMD 7900 XTX, Windows 10 (up to date), Cubase 13.
- I turned off “Resize Bar” in the BIOS.
That’s it. Now C13 plays videos.
Who’d’ve thought?
And it’s gone. sigh
Hi Googly, It’s a long shot, but, just in case you are not aware, there is a ‘resizable bar’ option in the AMD software Adrenalin edition. I’m not hopeful it will work, but thought it may be worth a mention.
2 Likes
Thanks for this. Since I turned off the Resizable BAR in the BIOS even MOV files don’t play, where they did before. I’ll try turning it back on, and using a Cubase profile in the AMD software to turn off for Cubase.
I’ll let you know if it works.
To be honest, the 1 thing that V13 has over V12 (for me!) is the “menu in every window” change. I have a 49" monitor and if I’m editing in the lower right corner I have to move the mouse a literal 4 feet to access the menus. With the menu in the window, it’s just 2 feet, tops… That’s one reason why I keep asking for underscores in the menus so I can access it via the keyboard. (I know the menu items react to keying the first letter, but it only works if there is only one item beginning with that letter.
As I say, when I had a 6700 I had no problems. When I exchanged it for a 7900, that’s when the problems started. I had the same drivers as before, nothing changed except the GPU. I’ve since installed drivers from the past year using AMD’s Clean install option and the Pro and consumer versions, Windows 10 is up to date.
My research indicates that it is a hardware acceleration problem. It seems that AMD only supports it in Win 11. Since the 6700 is on the old side and HA is fairly recent, it wasn’t affected.
It didn’t. But MOV files are playing again.
Also, Reziable BAR is not available in profiles - it’s a global setting.
So, I’ll use V13 but when I need video support I’ll use V12.
Sometimes I think it was easier when all I had was an acoustic guitar - happy daze!
1 Like
A few hours later. Now it doesn’t work.
Hello, me again.
I was re-installing an older version of VEGAS (bear with me) because I wanted to open and save an old project without it being updated which the newer versions of VEGAS do.
I also did a lot of PC tidying up (see below), which is neither here nor there. But. As you can see I was in a kind of “maintenance” mode. And I thought, What the hell, let’s re-install Cubase 13 and see if it will play videos. I removed all the other versions’ settings folders, so the install would be as clean as poss.
So I did.
And it did.
I re-booted, and it still does.
Make of that what you will.
Hopefully, this will be my last word on this subject.
Over and out.
(I deleted a lot of leftover VEGAS files, and a bunch of empty folders on the C: drive. I also used Auslogics. Registry Cleaner.)
2 Likes
I agree, I have the same issue exactly…PC, Windows 10 system …I have many previous versions of Cubase Pro still on my system (thank goodness). The video I’m trying to play in Cubase 13 plays on every version PERFECTLY!
Come back to version 13…NOTHING, black screen. I have converted this video to MOV, MPEG, MPG4 AVI etc…black screen !
go back to Cubase 12, 11, 10…all play wonderfully without hickup…
This is a CUBASE 13 problem that needs to be solved quickly as it is a major issue for those of us who need to work with video.
2 Likes
Relax, It’ll be released as a new feature in Cubase 17. 
ftr, I have an old HD7900 and do not have that resizable bar option
this has been an issue with version 13… and i think it’s very obvious that Steinberg do not have any intention of fixing…
(edit)
False alarm. Never mind
UPDATE!
just replaced the ‘videoengine’ file in main directory of CB13 with CB12 ‘videoengine’ file and it works!!!
Therefore the problem is indeed with this video engine file in CUBASE 13…which clearly shows that the problem is not with my PC.
I am not suggesting you guys do the same thing incase it breaks your prog or something so i take no responsibility, but it works for me and it it proves where the problem is.
The latest Cubase update (which was released yesterday) should fix the video issue as well.
Just updated and tried, not fixed, exactly the same.
Works with the older Cubase 12 videoengine though.