New Here
,
/t5/audition-discussions/byte-stream-type-on-audition/td-p/11705658
Dec 25, 2020
Dec 25, 2020
Copy link to clipboard
Copied
I saved a file that I was working on last night in Adobe Audition, but when I went to open it this morning (going to File -> Open Recent) an error message popped up saying «Error: Media Foundation reported an error when opening the file. The byte stream type of the given URL is unsupported.» It doesn’t seem like it should be due to an older version of Adobe, because I was just working on the file yesterday. I’d appreciate any help/suggestions people would give. Thanks — Jake
TOPICS
User interface or workspaces
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting.
Learn more
7
Replies
7
![]()
Community Expert
,
/t5/audition-discussions/byte-stream-type-on-audition/m-p/11705777#M26561
Dec 25, 2020
Dec 25, 2020
Copy link to clipboard
Copied
It might help just a little bit if we knew what file type it was… because at present we have absolutely nothing to go on at all!
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting.
Learn more
New Here
,
/t5/audition-discussions/byte-stream-type-on-audition/m-p/11705823#M26562
Dec 25, 2020
Dec 25, 2020
Copy link to clipboard
Copied
In Response To SteveG_AudioMasters_
Ah, thank you! It was a .sesx file. Happy to provide any other information that might be helpful!
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting.
Learn more
![]()
Mentor
,
/t5/audition-discussions/byte-stream-type-on-audition/m-p/11706484#M26572
Dec 26, 2020
Dec 26, 2020
Copy link to clipboard
Copied
In Response To Jake1425
email me the sesx file and I will check it for you
info at aatranslator dot com dot au
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting.
Learn more
New Here
,
/t5/audition-discussions/byte-stream-type-on-audition/m-p/11714820#M26614
Dec 29, 2020
Dec 29, 2020
Copy link to clipboard
Copied
In Response To SuiteSpot
Just sent it, thank you so much!
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting.
Learn more
![]()
Mentor
,
/t5/audition-discussions/byte-stream-type-on-audition/m-p/11715562#M26626
Dec 30, 2020
Dec 30, 2020
Copy link to clipboard
Copied
In Response To Jake1425
Unfortunately, that sesx file is completely trashed. You will need to roll back to a current backup.
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting.
Learn more
![]()
New Here
,
/t5/audition-discussions/byte-stream-type-on-audition/m-p/13010604#M32873
Jun 16, 2022
Jun 16, 2022
Copy link to clipboard
Copied
In Response To SuiteSpot
I’m having the same issue. But none of the backups work. Getting tired of losing sessions…..
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting.
Learn more
![]()
Mentor
,
/t5/audition-discussions/byte-stream-type-on-audition/m-p/13011232#M32876
Jun 16, 2022
Jun 16, 2022
Copy link to clipboard
Copied
LATEST
In Response To dougwylde
email me the sesx
info at aatranslator dot com dot au
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting.
Learn more
![]()
![]()
I am new to UWP. I am recording voice input (with MediaCapture) and then I trying to play it back.
And I am getting the following error
The byte stream type of the given URL is unsupported. (Exception from HRESULT: 0xC00D36C4)
I create is an MP3 file that can be play by double click with player. So the file is ‘ok’.
When I try to play it with MediaPlayer I get that error. I tried installing a new codec package and pointed .mp3 at it. Same error. I tried streams, StorageFile and URL methods for defining the input file but always the same error. I have microphone and webcam enabled. (my microphone is in the webcam) I am deploying to ‘Local Machine’.
Anyone know a possible reason? Here is the code. I would be interested to see if it works on another PC.
private async void RecordAndPlay()
{
string mediaFilename = "audioPRC.mp3";
StorageFile mediaFile;
StorageFolder tempFolder;
MediaCapture mediaCapture;
MediaPlayer mediaPlayer = null;
LowLagMediaRecording lowLagMediaRecording;
MediaSource mediaSource;
mediaCapture = new MediaCapture();
await mediaCapture.InitializeAsync();
mediaCapture.Failed += OnMediaCaptureFailed;
tempFolder = Windows.Storage.ApplicationData.Current.TemporaryFolder;
mediaFile = await tempFolder.CreateFileAsync(mediaFilename, CreationCollisionOption.ReplaceExisting);
MediaEncodingProfile mediaEncodingProfile = MediaEncodingProfile.CreateMp3(AudioEncodingQuality.Medium);
lowLagMediaRecording = await mediaCapture.PrepareLowLagRecordToStorageFileAsync(
mediaEncodingProfile, mediaFile);
await lowLagMediaRecording.StartAsync();
// Talk into your microphone during the 10 second wait...
await Task.Delay(10000);
await lowLagMediaRecording.StopAsync();
await lowLagMediaRecording.FinishAsync();
lowLagMediaRecording = null;
mediaPlayer = new MediaPlayer { AutoPlay = false, AudioCategory = MediaPlayerAudioCategory.Media };
mediaPlayer.MediaFailed += OnMediaPlayerFailed;
mediaPlayer.AudioCategory = Windows.Media.Playback.MediaPlayerAudioCategory.Media;
mediaSource = MediaSource.CreateFromStorageFile(mediaFile);
var mediaPlaybackItem = new MediaPlaybackItem(mediaSource);
mediaPlayer.Source = mediaPlaybackItem;
mediaPlayer.Play();
}
private void OnMediaPlayerFailed(object sender, MediaPlayerFailedEventArgs e)
{ Debug.WriteLine(e.ExtendedErrorCode.Message); }
private void OnMediaCaptureFailed(MediaCapture sender, MediaCaptureFailedEventArgs e)
{ Debug.WriteLine("Capture failed: " + e.Message); }
- Spaces
- Default
- Help Room
- META
- Moderators
-
- Topics
- Questions
- Users
- Badges
- Home /
2
I’m trying to implement video for WebGL. Since mp4 files are unsupported I’m making an exception for WebGL; trying to use a link instead:
using System.Collections;
using System.Collections.Generic;
using UnityEngine;
using UnityEngine.Video;
using UnityEngine.SceneManagement;
public class CinematicControl : MonoBehaviour
{
public Canvas canvas;
public VideoPlayer vp; //standard player
public VideoPlayer web; //one that uses a link
private VideoPlayer myPlayer; //the player we're using
int held = 0;
// Use t$$anonymous$$s for initialization
void Start ()
{
#if UNITY_WEBGL
myPlayer = web;
#else
myPlayer = vp;
}
However, when I build for WebGL I get the error: The byte stream type of the given URL is unsupported.
Does anyone know what the issue is? I’m using a generic YouTube video for testing purposes.
1 Reply
·
Add your reply
- Sort:
1
Answer by HarshadK · May 15, 2017 at 01:23 PM
A little late to the party but since @AnkitSangani has revived t$$anonymous$$s question. Here are some details about why the error The byte stream type of the given URL is unsupported is thrown when using YouTube video url.
Firstly it is important to understand how YouTube plays videos. T$$anonymous$$s article explains it pretty good. Now in order to get the actual byte array stream of video you need to use the videoplayback url (w$$anonymous$$ch looks like: videoplayback?……) w$$anonymous$$ch makes call to get the byte stream. Now if you inspect the requests to t$$anonymous$$s URL using the developer tools in browser you can see the response received by the request. The response headers include the content-type to be content-type:video/webm or content-type:audio/webm based on whether it is video file request or audio file request. T$$anonymous$$s shows that the type of byte stream returned if of webm file format type w$$anonymous$$ch is decoded using a VP9 decoder w$$anonymous$$ch Unity does not support. Hence the error. If you use a URL w$$anonymous$$ch returns a video file format supported by Unity then you would be able to play it.
Your answer
Welcome to Unity Answers
If you’re new to Unity Answers, please check our User Guide to help you navigate through our website and refer to our FAQ for more information.
Before posting, make sure to check out our Knowledge Base for commonly asked Unity questions.
Check our Moderator Guidelines if you’re a new moderator and want to work together in an effort to improve Unity Answers and support our users.
Follow this Question
Related Questions
Windows 7 Service Pack 1 Windows 7 Enterprise Windows 7 Home Basic Windows 7 Home Premium Windows 7 Professional Windows 7 Starter Windows 7 Ultimate Windows Server 2008 R2 Service Pack 1 Windows Server 2008 R2 Enterprise Windows Server 2008 R2 Datacenter Windows Server 2008 R2 Foundation Windows Server 2008 R2 Standard More…Less
Symptoms
Consider the following scenario:
-
You have a Windows 7 Service Pack 1 (SP1)-based or Windows Server 2008 R2 SP1-based computer that has Media Foundation Topology Editor installed.
-
You open the TopoEdit console by typing topoedit.exe in the Search programs and files box and then pressing Enter.
-
You try to open a certain .wmv file by clicking Add Source… on the Topology menu.
In this scenario, you receive an error message that resembles the following:
Failed to create source node — The byte stream type of the given URL is unsupported
Resolution
Hotfix information
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a «Hotfix download available» section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:
http://support.microsoft.com/contactus/?ws=supportNote The «Hotfix download available» form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Prerequisites
To apply this hotfix, you must be running Windows 7 SP1 or Windows Server 2008 R2 SP1.
For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
976932Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2
Registry information
To apply this hotfix, you do not have to make any changes to the registry.
Restart requirement
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows 7 and Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under «Windows 7/Windows Server 2008 R2» on the page. Always refer to the «Applies To» section in articles to determine the actual operating system that each hotfix applies to.
-
The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
Version
Product
Milestone
Service branch
6.1.760
1.22xxxWindows 7 and Windows Server 2008 R2
SP1
LDR
-
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the «Additional file information for Windows 7 and for Windows Server 2008 R2» section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 7
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Mf.dll |
12.0.7601.22524 |
3,207,680 |
26-Nov-2013 |
02:02 |
x86 |
|
Mferror.dll |
12.0.7600.16385 |
2,048 |
14-Jul-2009 |
01:06 |
x86 |
|
Mfpmp.exe |
12.0.7600.16385 |
23,040 |
14-Jul-2009 |
01:14 |
x86 |
|
Mfps.dll |
12.0.7601.22524 |
103,424 |
26-Nov-2013 |
02:02 |
x86 |
|
Rrinstaller.exe |
11.0.7600.16385 |
50,176 |
14-Jul-2009 |
01:14 |
x86 |
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Mf.dll |
12.0.7601.22524 |
4,120,064 |
26-Nov-2013 |
02:34 |
x64 |
|
Mferror.dll |
12.0.7600.16385 |
2,048 |
14-Jul-2009 |
01:28 |
x64 |
|
Mfpmp.exe |
12.0.7600.16385 |
24,576 |
14-Jul-2009 |
01:39 |
x64 |
|
Mfps.dll |
12.0.7601.22524 |
206,848 |
26-Nov-2013 |
02:34 |
x64 |
|
Rrinstaller.exe |
11.0.7600.16385 |
55,808 |
14-Jul-2009 |
01:39 |
x64 |
|
Mf.dll |
12.0.7601.22524 |
3,207,680 |
26-Nov-2013 |
02:02 |
x86 |
|
Mferror.dll |
12.0.7600.16385 |
2,048 |
14-Jul-2009 |
01:06 |
x86 |
|
Mfpmp.exe |
12.0.7600.16385 |
23,040 |
14-Jul-2009 |
01:14 |
x86 |
|
Mfps.dll |
12.0.7601.22524 |
103,424 |
26-Nov-2013 |
02:02 |
x86 |
|
Rrinstaller.exe |
11.0.7600.16385 |
50,176 |
14-Jul-2009 |
01:14 |
x86 |
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the «Applies to» section.
More Information
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684Description of the standard terminology that is used to describe Microsoft software updates
Additional file information for Windows 7 and for Windows Server 2008 R2
Additional files for all supported x86-based versions of Windows 7
|
File property |
Value |
|---|---|
|
File name |
X86_39c34e6acdedb67667d5e21488ec4f94_31bf3856ad364e35_6.1.7601.22524_none_222f639224ee1cf9.manifest |
|
File version |
Not applicable |
|
File size |
703 |
|
Date (UTC) |
26-Nov-2013 |
|
Time (UTC) |
06:46 |
|
File name |
X86_microsoft-windows-mediafoundation_31bf3856ad364e35_6.1.7601.22524_none_9ee54d5884299bc3.manifest |
|
File version |
Not applicable |
|
File size |
265,911 |
|
Date (UTC) |
26-Nov-2013 |
|
Time (UTC) |
06:50 |
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
|
File property |
Value |
|---|---|
|
File name |
Amd64_a8fe16b4bd03303c48b940aad550fc43_31bf3856ad364e35_6.1.7601.22524_none_63a487ac3bb20b7b.manifest |
|
File version |
Not applicable |
|
File size |
1,056 |
|
Date (UTC) |
26-Nov-2013 |
|
Time (UTC) |
06:46 |
|
File name |
Amd64_microsoft-windows-mediafoundation_31bf3856ad364e35_6.1.7601.22524_none_fb03e8dc3c870cf9.manifest |
|
File version |
Not applicable |
|
File size |
265,915 |
|
Date (UTC) |
26-Nov-2013 |
|
Time (UTC) |
06:46 |
|
File name |
Wow64_microsoft-windows-mediafoundation_31bf3856ad364e35_6.1.7601.22524_none_0558932e70e7cef4.manifest |
|
File version |
Not applicable |
|
File size |
162,389 |
|
Date (UTC) |
26-Nov-2013 |
|
Time (UTC) |
06:46 |
Need more help?
- Remove From My Forums
-
Question
-
Hi all,
I am trying to make the MF WavSource sample to work.
I can compile it with not problem and I am sure it is registred correctly.
However, when I try to load a wav file (with .xyz extension) using BasicPlayback or TopoEdit, I get the error «failed to create source node.
The byte stream type of the given URL is unsupported.»I enabled the error reports to debug and I got :
Source Resolver Context(0x7d83d70) Trying Byte Scheme Handler CLSID(«WAVE Source ByteStreamHandler»)
Source Resolver Context(0x7d83d70) Byte stream Handler Result 0x80040111 ????
Source Resolver Context(0x7d83d70) SchemeHandler Result 0xC00D36C4 (which is MF_E_UNSUPPORTED_BYTESTREAM_TYPE)I got this error either in pure C++ or in the MediaFoundation.net sample and I am on Windows 10 x64.
Any idea?
Answers
-
Found my mistake using MFTrace.exe
6416,3B3C 10:31:03.45433 COle32ExportDetours::CoCreateInstance @ Failed to create {CFF2D529-0D61-463A-9049-BD9611004E02} WAVE Source ByteStreamHandler (C:Users<username>SourcemediafoundationwavsourceReleaseWavSource.dll) hr=0x80040111 CLASS_E_CLASSNOTAVAILABLEIt look like I didn’t changed the GUID everywhere in the project 🙁 First time I create a COM object.
WavSource works now 🙂
And it was a similar problem with my custom media source in .NET.
8744,2C78 11:45:07.42117 COle32ExportDetours::CoCreateInstance @ Failed to create {B2C8B1AF-A0CC-4A47-9F4C-9764CF1CBF6E} WavSourceFilter.CWavByteStreamHandler (mscoree.dll) hr=0x80070002 ERROR_FILE_NOT_FOUNDHere I used a tool called FUSLOGVW.exe to see that CoCreateInstance try to load the assembly not where it was registered but in the Global Assembly Cache (GAC), or in the caller directory. So I copied my assembly in the topoedit folder, run regasm and it
work 🙂Thank you all,
-
Marked as answer by
Wednesday, July 6, 2016 1:05 PM
-
Marked as answer by
![]()
I am trying to query the NumFrames property of an mp4 file but am met with the error:
mp4 = VideoReader(‘2G.mp4’)
«Error using VideoReader/initReader (line 734)
Could not read file due to an unexpected error. Reason: Error Creating Source Reader Reason: The byte stream type of
the given URL is unsupported.
Error in audiovideo.internal.IVideoReader (line 136)
initReader(obj, fileName, currentTime);
Error in VideoReader (line 104)
obj@audiovideo.internal.IVideoReader(varargin{:});»
Let me know if there is any further info that I can provide. Thank you for any help.
Accepted Answer
![]()
More Answers (0)
See Also
Categories
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!
An Error Occurred
Unable to complete the action because of changes made to the page. Reload the page to see its updated state.
Hello everyone.
The Mixed Reality Forums here are no longer being used or maintained.
There are a few other places we would like to direct you to for support, both from Microsoft and from the community.
The first way we want to connect with you is our mixed reality developer program, which you can sign up for at https://aka.ms/IWantMR.
For technical questions, please use Stack Overflow, and tag your questions using either hololens or windows-mixed-reality.
If you want to join in discussions, please do so in the HoloDevelopers Slack, which you can join by going to https://aka.ms/holodevelopers, or in our Microsoft Tech Communities forums at https://techcommunity.microsoft.com/t5/mixed-reality/ct-p/MicrosoftMixedReality.
And always feel free to hit us up on Twitter @MxdRealityDev.
Hello all,
when i load video from url i got this Error in unity 5.6 videoplayer
WindowsVideoMedia error 0xc00d36c4 while reading 
Context: MFCreateSourceReaderFromURL
Error details: The byte stream type of the given URL is unsupported.
Track types:
please Help me!
0